Bug#902901: FTBFS: Tests fail

[Sean Whitton]

Hello,

On Tue 16 Jun 2020 at 07:53PM +03, Ilias Tsitsimpis wrote:

> This package is still unbuildable after 2 years, with no response from
> upstream. Since there are no rev dependencies for this package, I intend
> to remove it from Debian.

Please go ahead, since secret-sharing no longer depends on it. Thank you
for your efforts!

-- 
Sean Whitton


signature.asc
Description: PGP signature

Processed: your mail

[Debian Bug Tracking System]

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

> forcemerge 963548 964362
Bug #963548 [chromium] Received signal 11 SEGV_MAPERR
Bug #964334 [chromium] segfault repeatedly
Bug #964362 [chromium] chromium crash frequently, SEGV_MAPERR
Severity set to 'grave' from 'important'
Marked as found in versions chromium/83.0.4103.106-1, chromium/81.0.4044.92-1, 
and chromium/83.0.4103.116-1~deb10u2.
Added tag(s) moreinfo.
Bug #964334 [chromium] segfault repeatedly
Merged 963548 964334 964362
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> forcemerge 964334 963548
Bug #964334 [chromium] segfault repeatedly
Bug #963548 [chromium] Received signal 11 SEGV_MAPERR
Severity set to 'grave' from 'normal'
Marked as found in versions chromium/83.0.4103.116-2.
Bug #964334 [chromium] segfault repeatedly
Marked as found in versions chromium/81.0.4044.92-1 and 
chromium/83.0.4103.106-1.
Added tag(s) moreinfo.
Merged 963548 964334
> thanks
Stopping processing here.

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

Processed: unarchiving 867436

[Debian Bug Tracking System]

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

> unarchive 867436
Bug #867436 {Done: Scott Kitterman } [python3-icalendar] 
python3-icalendar: missing dependencies
Unarchived Bug 867436
> thanks
Stopping processing here.

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

Processed: unarchiving 879224

[Debian Bug Tracking System]

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

> unarchive 879224
Bug #879224 {Done: Thomas Goirand } [websockify] websockify: 
missing dependency on python-pkg-resources
Unarchived Bug 879224
> thanks
Stopping processing here.

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

Processed: unarchiving 879170

[Debian Bug Tracking System]

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

> unarchive 879170
Bug #879170 {Done: Adrian Bunk } [libswt-webkit-gtk-3-jni] 
libswt-webkit-gtk-3-jni: Needs libwebkitgtk-1.0-0 dep
Unarchived Bug 879170
> thanks
Stopping processing here.

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

Bug#961377: raspi3-firmware: recent stable update causes non-booting systems

[Gunnar Wolf]

tags 961377 + pending
thanks

I have uploaded the fix and mailed the Stable Release Managers, this
should be fixed soon.

Thanks!

Processed: Re: Bug#961377: raspi3-firmware: recent stable update causes non-booting systems

[Debian Bug Tracking System]

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

> tags 961377 + pending
Bug #961377 [raspi3-firmware] raspi3-firmware: recent stable update causes 
non-booting systems
Ignoring request to alter tags of bug #961377 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 962755 https://github.com/libexif/exif/issues/2
Bug #962755 [src:exif] exif: FTBFS on s390x: test failure
Set Bug forwarded-to-address to 'https://github.com/libexif/exif/issues/2'.
> stop
Stopping processing here.

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

Processed: Bug#963933 marked as pending in glib2.0

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #963933 [src:glib2.0,src:util-linux] glib2.0: autopkgtext: ld: cannot find 
-lcryptsetup
Added tag(s) pending.

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

Bug#963933: marked as pending in glib2.0

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #963933 in glib2.0 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/gnome-team/glib/-/commit/5d5d4e5405b6a5e32c7c0133df2d984bd25a83b2


d/tests/build: Don't exercise static linking for GIO

libmount will no longer support being linked statically from 2.35.2-8
onwards. For now I'm continuing to test that the other libraries can
still be statically linked, but please consider them to be "at risk".

Closes: #963933


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/963933

Processed: tagging 964399

[Debian Bug Tracking System]

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

> tags 964399 + bullseye sid
Bug #964399 [src:ganglia] Should ganglia be removed?
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Bug#963933: glib2.0: autopkgtext: ld: cannot find -lcryptsetup

[Simon McVittie]

On Mon, 06 Jul 2020 at 18:50:01 +0200, Chris Hofstaedtler wrote:
> src:util-linux will drop most static libraries in the 2.35.2-8 upload.
> Please change the glib2.0 autopkgtest (by dropping the static test)
> to allow this.

libmount support in glib2.0 is temporarily disabled as a workaround
for the crashes, so you can go ahead with this whenever you want. I'll
disable the test for static linking of at least GIO (which is the part
that uses libmount) before re-enabling the libmount dependency.

smcv

Processed: Re: skales: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags 943273 patch
Bug #943273 [src:skales] skales: Python2 removal in sid/bullseye
Added tag(s) patch.

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

Bug#943273: skales: Python2 removal in sid/bullseye

[Vagrant Cascadian]

Control: tags 943273 patch

The attached patch simply switches to python3.

The code seems at a glance to be python3 compatible(e.g. 2to3 didn't
have anything interesting to say), and is sufficient enough for help2man
to work running with python3. But I haven't tested more extensively than
that.

Maybe it is too easy to be true!


live well,
  vagrant
From 620fec8b161bb56cd48b00f6c5449f9783bd66b7 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Mon, 6 Jul 2020 14:12:22 -0700
Subject: [PATCH] Switch to python3 (Closes: #943273).

---
 debian/control |  4 ++--
 debian/patches/python3 | 24 
 debian/patches/series  |  1 +
 3 files changed, 27 insertions(+), 2 deletions(-)
 create mode 100644 debian/patches/python3

diff --git a/debian/control b/debian/control
index d3eba62..4273080 100644
--- a/debian/control
+++ b/debian/control
@@ -2,14 +2,14 @@ Source: skales
 Section: admin
 Priority: optional
 Maintainer: Riku Voipio 
-Build-Depends: debhelper (>=9), help2man, libfdt1, python
+Build-Depends: debhelper (>=9), help2man, libfdt1, python3
 Standards-Version: 4.1.3
 Vcs-Git: https://salsa.debian.org/debian/skales.git
 Vcs-Browser: https://salsa.debian.org/debian/skales
 
 Package: skales
 Architecture: any
-Depends: device-tree-compiler, python, ${misc:Depends}
+Depends: device-tree-compiler, python3, ${misc:Depends}
 Description: Boot image creation tools for qualcomm boards
  Scripts and tools used to build kernel images for some Qualcomm SoC
  based boards, such as DragonBoard 410c. Tools included in the package
diff --git a/debian/patches/python3 b/debian/patches/python3
new file mode 100644
index 000..d5bbaa7
--- /dev/null
+++ b/debian/patches/python3
@@ -0,0 +1,24 @@
+From: Vagrant Cascadian 
+Debian-bug: https://bugs.debian.org/943273
+Comment: Switch to using python3.
+
+Index: skales/dtbTool
+===
+--- skales.orig/dtbTool
 skales/dtbTool
+@@ -1,4 +1,4 @@
+-#! /usr/bin/env python
++#! /usr/bin/env python3
+ #
+ #  Copyright (c) 2015-2016, The Linux Foundation. All rights reserved.
+ #
+Index: skales/mkbootimg
+===
+--- skales.orig/mkbootimg
 skales/mkbootimg
+@@ -1,4 +1,4 @@
+-#! /usr/bin/env python
++#! /usr/bin/env python3
+ #
+ #  Copyright (c) 2013, The Linux Foundation. All rights reserved.
+ #
diff --git a/debian/patches/series b/debian/patches/series
index a7c8b03..6cc5f27 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 dtbtoo-soname
+python3
-- 
2.20.1



signature.asc
Description: PGP signature

Bug#962221: Fixes for CVE-2020-13696 (#962221)

[Vasyl Gello]

Hi Mattia!

July 6, 2020 6:58:05 PM UTC, Mattia Rizzolo  написав(-ла):
>but could either of you do a bunch of housekeeping work as well, like:
> * bumping dh compat
> * drop --dbgsym-migration
> * drop the .menu files
> * would be awesome to have the copyright file rewrote using dep-5
> * 

I pushed the modernized package however if you check resulting Lintian report,
there are two errors claiming two libs are not compiled against libc and several
others missing requured prerequisites. I have not figured yet how to fix these,
maybe you know?


-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com

Skype: vasek.gello
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

signature.asc
Description: PGP signature

Processed: tagging 962813

[Debian Bug Tracking System]

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

> tags 962813 + bullseye sid
Bug #962813 [src:haskell-tree-monad] does not build with ghc 8.8
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Bug#964252: marked as done (libbluray: FTBFS if texlive is installed in non-minimal build environment)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jul 2020 20:28:22 +
with message-id 
and subject line Bug#964252: fixed in libbluray 1:1.2.0-2
has caused the Debian Bug report #964252,
regarding libbluray: FTBFS if texlive is installed in non-minimal build 
environment
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.)


-- 
964252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbluray
Version: 1.1.0-1
Severity: serious
Tags: ftbfs

Hi,

Building from source fails on buster (amd64) while trying to create pdf docs.
Relevant log excerpt at end of mail, full log available here:
  https://oneric.de/public/libbluray-1.1.0-1_ftbfs.log
It seems like that, while no tex files are produced, doxygen still tries to 
build pdf docs.

I retrieved the source with
  apt-get source libbluray/buster
and tried building both with
  apt-get source -b libbluray/buster
and
 debuild -us -uc -b
Build dependencies were installed with mk-build-deps.

System: Debian Buster amd64
 libc6   2.28-10
 doxygen 1.8.13-10
 texlive 2018.20190227-2


Either dropping patch 0004-Disable-PDF-documentation or adding

confflags += --disable-doxygen-pdf
confflags += --disable-doxygen-ps

to debian/rules resolved this for me.

Regards
Nils König


---

[…]
Generating file index...
Generating file member index...
Generating example index...
finalizing index lists...
writing tag file...
lookup cache used 359/65536 hits=1092 misses=366
finished...
cd doc/doxygen/latex; \
rm -f *.aux *.toc *.idx *.ind *.ilg *.log *.out; \
/usr/bin/latex refman.tex; \
 refman.idx; \
/usr/bin/latex refman.tex; \
countdown=5; \
while /usr/bin/egrep 'Rerun (LaTeX|to get cross-references right)' \
refman.log > /dev/null 2>&1 \
&& test $countdown -gt 0; do \
/usr/bin/latex refman.tex; \
countdown=`expr $countdown - 1`; \
done; \
/usr/bin/dvips -o ../libbluray.ps refman.dvi
/bin/bash: line 0: cd: doc/doxygen/latex: No such file or directory
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
! I can't find file `refman.tex'.
<*> refman.tex
  
(Press Enter to retry, or Control-D to exit)
Please type another input file name:
--- End Message ---
--- Begin Message ---
Source: libbluray
Source-Version: 1:1.2.0-2
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
libbluray, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated libbluray 
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: Mon, 06 Jul 2020 21:57:01 +0200
Source: libbluray
Architecture: source
Version: 1:1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 964252
Changes:
 libbluray (1:1.2.0-2) unstable; urgency=medium
 .
   * Build with --disable-doxygen-{pdf,ps} to fix build in non-minimal build
 environments (Closes: #964252)
   * debian/: Bump debhelper compat to 13
Checksums-Sha1:
 11a1feb97b86045bdfd0af87fa323c391e636051 2420 libbluray_1.2.0-2.dsc
 63c6aaa1a084187921a8a54fc7d94277ad5ff712 16912 libbluray_1.2.0-2.debian.tar.xz
Checksums-Sha256:
 195e616dca9e696a071ed0afced22ba1b2a82fde6ce4b04396bf65acc108e4d8 2420 
libbluray_1.2.0-2.dsc
 5771523b26888df06d8b5f340ff845ce3401f955041f65ef668d6b6e4f14b7cb 16912 
libbluray_1.2.0-2.debian.tar.xz
Files:
 dc449bc07d7795ab8a5bde97c0761e91 2420 libs optional libbluray_1.2.0-2.dsc
 a55223d0152490e94c1c75123d2e7111 16912 libs optional 
libbluray_1.2.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl8DgsgACgkQafL8UW6n
GZOV/hAAx/U+DCigDCIcdqc8kvMjmMFRhfUazjklQQmqja6yIgYrRsnEhh69K7v+
AKffhcH0C7AqiSjyTBWNarIBTUFEdfHWw7ID4gnKUajDdYMXywPXwsV2izb069Hp
AjY7ig4UhVXSvUfN9dk2jFbyN5DBHt7+EizgAPLyujm/6h/0/q9vE5qVBEaMFzqs
hy7/FqOYCCAKh53jNe41nyV3w9nHGIitlnjqGWwUQJlvOec8nHO2ZDZpwcSNk9gw

Processed: Re: fixed

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.0.0-1
Bug #955080 {Done: Michal Arbet } 
[src:python-ceilometermiddleware] python-ceilometermiddleware: FTBFS with 
Sphinx 2.4: AttributeError: 'Sphinx' object has no attribute 'info'
Marked as fixed in versions python-ceilometermiddleware/2.0.0-1.

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

Bug#955080: fixed

[Paul Gevers]

Control: fixed -1 2.0.0-1

Dear Thomas,

On Mon, 25 May 2020 09:44:09 +0200 Thomas Goirand  wrote:
> fixed

Your package version 2.0.0-1 was not based (changelog entries) on
version 1.5.0-3, which closed this bug. Hence, the BTS and the migration
software don't know that the version currently in unstable is actually
fixed. I am fixing that with the information above, after I checked that
the package built recently on reproducible-build infra.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#956285: Problems identified in debian/copyright

[Petter Reinholdtsen]

[Michael Lustfield]
> I noticed that this package appears to have some issues with debian/copyright.

Hi.  Any hope to have a fix for this in time for the next stable release?

-- 
Happy hacking
Petter Reinholdtsen

Bug#964405: marked as pending in lintian

[Felix Lechner]

Control: tag -1 pending

Hello,

Bug #964405 in lintian 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/lintian/lintian/-/commit/69fdf8a8c68044bea8edef1b527cf2e044694ac8


Use new path to test recipes in autopkgtest. (Closes: #964405)

The path to the test specifications changed in commit 29ac0192. That
commit totally ignores the use of the path in autopkgtest, which is
fixed here.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964405

Processed: Bug#964405 marked as pending in lintian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #964405 [src:lintian] lintian: autopkgtest regression: No tests were 
selected by your filter:
Added tag(s) pending.

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

Bug#964408: python-redisearch-py: autopkgtest failure: No module named 'redisearch_py'

[Paul Gevers]

Source: python-redisearch-py
Version: 0.9.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package python-redisearch-py,
great. However, it fails. Currently this failure is blocking the
migration to testing [1]. Can you please investigate the situation and
fix it?

I copied some of the output at the bottom of this report. You're using
autodep8 to test your python package. You probably need to tell it that
your module is named differently.

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

Paul

[1] https://qa.debian.org/excuses.php?package=python-redisearch-py

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-redisearch-py/6046207/log.gz

autopkgtest [16:49:00]: test autodep8-python3: set -e ; for py in
$(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing
with $py:" ; $py -c "import redisearch_py; print(redisearch_py)" ; done
autopkgtest [16:49:00]: test autodep8-python3: [---
Testing with python3.8:
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named 'redisearch_py'
autopkgtest [16:49:00]: test autodep8-python3: ---]



signature.asc
Description: OpenPGP digital signature

Bug#964407: ocaml-odoc: autopkgtest failure: Unknown tag '@raises'.

[Paul Gevers]

Source: ocaml-odoc
Version: 1.5.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s), Ralf,

You recently added an autopkgtest to your package ocaml-odoc, great.
However, it fails. Currently this failure is blocking the migration to
testing [1]. Can you please investigate the situation and fix it?

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/o/ocaml-odoc/6036411/log.gz

autopkgtest [20:54:33]: test odoc-on-odoc: [---
Error: Rule failed to generate the following targets:
- _doc/_html/highlight.pack.js
File "src/odoc/fs.mli", line 37, characters 6-13:
Unknown tag '@raises'.
File "src/odoc/depends.mli", line 30, characters 15-17:
'{i' should be followed by space, a tab, or a new line.
File "src/odoc/compile.mli", line 19, characters 35-37:
'{i' should be followed by space, a tab, or a new line.
autopkgtest [20:54:43]: test odoc-on-odoc: ---]



signature.asc
Description: OpenPGP digital signature

Bug#964334: segfault repeatedly

[Daniil Shchadny]

Package: chromium
Version: 83.0.4103.116-2
Followup-For: Bug #964334

Also like said before, chromium crashes very soon after starting, usually
in few minutes.

System is up-to-date, no proprietary software.

-- Stacktrace:
daniil@apollopc:~$ chromium
[34138:34138:0706/222408.794943:ERROR:vaapi_wrapper.cc(480)] vaInitialize
failed: unknown libva error
[34138:34138:0706/222408.809049:ERROR:sandbox_linux.cc(374)]
InitializeSandbox() called with multiple threads in process gpu-process.
[34098:34098:0706/222408.882023:ERROR:pref_model_associator.cc(121)] Failed
to deserialize value of preference 'sync.demographics': Line: 1, column: 1,
Unexpected token.
[34098:34147:0706/222409.320236:ERROR:device_id_linux.cc(88)] Could not
find appropriate disk uuid.
[34098:34147:0706/222409.320264:ERROR:device_id_linux.cc(91)]
DeviceID=sdc1, uuid=CD4F-2D7E
[34098:34147:0706/222409.320270:ERROR:device_id_linux.cc(91)]
DeviceID=sdc2, uuid=f41eb688-1f97-4a0e-a86e-862e2e173fc3
Fontconfig error: Cannot load default config file
Received signal 11 SEGV_MAPERR 7f01ac174707
#0 0x556fb4dfec69 (/usr/lib/chromium/chromium+0x52b3c68)
#1 0x556fb4d5def3 (/usr/lib/chromium/chromium+0x5212ef2)
#2 0x556fb4dfe7f1 (/usr/lib/chromium/chromium+0x52b37f0)
#3 0x7fbece752110 (/usr/lib/x86_64-linux-gnu/libpthread-2.30.so+0x1410f)
#4 0x7fbec983dd3c (/usr/lib/x86_64-linux-gnu/libc-2.30.so+0x85d3b)
#5 0x7fbec983ff33 (/usr/lib/x86_64-linux-gnu/libc-2.30.so+0x87f32)
#6 0x7fbec9841bf9 __libc_malloc
#7 0x556fb4e169be operator new()
#8 0x7fbec9ac8a2c std::__cxx11::basic_string<>::reserve()
#9 0x7fbec9abe498 std::__cxx11::basic_stringbuf<>::overflow()
#10 0x7fbec9ac704a std::basic_streambuf<>::xsputn()
#11 0x7fbec9ab9714 std::__ostream_insert<>()
#12 0x556fb4dfed39 (/usr/lib/chromium/chromium+0x52b3d38)
#13 0x556fb4dff054 (/usr/lib/chromium/chromium+0x52b4053)
#14 0x556fb4d70412 (/usr/lib/chromium/chromium+0x5225411)
#15 0x556fb4d72548 (/usr/lib/chromium/chromium+0x5227547)
#16 0x556fb34b812a (/usr/lib/chromium/chromium+0x396d129)
#17 0x556fb34b817e (/usr/lib/chromium/chromium+0x396d17d)
#18 0x556fb2b0d387 (/usr/lib/chromium/chromium+0x2fc2386)
#19 0x556fb34713d9 (/usr/lib/chromium/chromium+0x39263d8)
#20 0x556fb347161e (/usr/lib/chromium/chromium+0x392661d)
#21 0x556fb34bb967 (/usr/lib/chromium/chromium+0x3970966)
#22 0x556fb34e74c7 (/usr/lib/chromium/chromium+0x399c4c6)
#23 0x556fb34e777e (/usr/lib/chromium/chromium+0x399c77d)
#24 0x556fb34b813f (/usr/lib/chromium/chromium+0x396d13e)
#25 0x556fb34b817e (/usr/lib/chromium/chromium+0x396d17d)
#26 0x556fb2b0d387 (/usr/lib/chromium/chromium+0x2fc2386)
#27 0x556fb2dd07a3 (/usr/lib/chromium/chromium+0x32857a2)
#28 0x556fb313f0bc (/usr/lib/chromium/chromium+0x35f40bb)
#29 0x556fb4f3045f (/usr/lib/chromium/chromium+0x53e545e)
#30 0x556fb4f36a24 (/usr/lib/chromium/chromium+0x53eba23)
#31 0x556fb4f34b62 (/usr/lib/chromium/chromium+0x53e9b61)
#32 0x556fb4f3382d (/usr/lib/chromium/chromium+0x53e882c)
#33 0x556fb4f2c213 (/usr/lib/chromium/chromium+0x53e1212)
#34 0x556fb4f47abb (/usr/lib/chromium/chromium+0x53fcaba)
#35 0x556fb4f47de0 (/usr/lib/chromium/chromium+0x53fcddf)
#36 0x556fb4f47370 (/usr/lib/chromium/chromium+0x53fc36f)
#37 0x556fb2db9c46 (/usr/lib/chromium/chromium+0x326ec45)
#38 0x556fb2db976c (/usr/lib/chromium/chromium+0x326e76b)
#39 0x556fb2db5eed (/usr/lib/chromium/chromium+0x326aeec)
#40 0x556fb2dac74b (/usr/lib/chromium/chromium+0x326174a)
#41 0x556fb2d9f044 (/usr/lib/chromium/chromium+0x3254043)
#42 0x556fb2d9ed75 (/usr/lib/chromium/chromium+0x3253d74)
#43 0x556fb2dbd426 (/usr/lib/chromium/chromium+0x3272425)
#44 0x556fb4e1c0e0 (/usr/lib/chromium/chromium+0x52d10df)
#45 0x7fbecd507b0f (/usr/lib/x86_64-linux-gnu/libevent-2.1.so.7.0.0+0x23b0e)
#46 0x7fbecd50824f event_base_loop
#47 0x556fb4e1c38e (/usr/lib/chromium/chromium+0x52d138d)
#48 0x556fb4dbc5d5 (/usr/lib/chromium/chromium+0x52715d4)
#49 0x556fb4d94670 (/usr/lib/chromium/chromium+0x524966f)
#50 0x556fb30da3b3 (/usr/lib/chromium/chromium+0x358f3b2)
#51 0x556fb4dd22a9 (/usr/lib/chromium/chromium+0x52872a8)
#52 0x556fb4e0ec9e (/usr/lib/chromium/chromium+0x52c3c9d)
#53 0x7fbece746f27 start_thread
#54 0x7fbec98b531f clone
  r8: 0077  r9: 0050 r10: 0004 r11:
007c
 r12: 7fbeac20 r13: 7fbeac30 r14: 7fbeac2fc090 r15:
0030
  di: 0021  si: 0004  bp: 0020  bx:
7f01ac1746ff
  dx: 7fbeac80  ax: 7fbeac149870  cx: 7f01ac1746ff  sp:
7fbebaff9440
  ip: 7fbec983dd3c efl: 00010206 cgf: 002b0033 erf:
0004
 trp: 000e msk:  cr2: 7f01ac174707
[end of stack trace]
Calling _exit(1). Core file will not be generated.


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

Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,

Bug#964406: onionbalance: autopkgtest regression: debian/tests/upstream does not exist

[Paul Gevers]

Source: onionbalance
Version: 0.2.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of onionbalance the autopkgtest of onionbalance
fails in testing when that autopkgtest is run with the binary packages
of onionbalance from unstable. It didn't fail when run with only
packages from testing. In tabular form:

   no-fail fail
onionbalance   from testing0.2.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems that
your test never had a working autopkgtest, but at least it didn't fail
like it does now. Please check the specification:
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

[1] https://qa.debian.org/excuses.php?package=onionbalance

https://ci.debian.net/data/autopkgtest/testing/amd64/o/onionbalance/6151679/log.gz

blame: onionbalance
badpkg: debian/tests/upstream does not exist



signature.asc
Description: OpenPGP digital signature

Bug#963855: marked as done (capnproto: FTBFS on IPv6-only environments)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jul 2020 19:34:01 +
with message-id 
and subject line Bug#963855: fixed in capnproto 0.7.0-7
has caused the Debian Bug report #963855,
regarding capnproto: FTBFS on IPv6-only environments
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.)


-- 
963855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: capnproto
Version: 0.7.0-6
Severity: serious
Justification: FTBFS (when it built before)

During archive-wide test rebuilding of an IPv6-only environment (which
appears on some normal buildds)[1] we noticed that this package fails:

  kj/async-io-test.c++:126: failed: expected ("1.2.3.4:80") == (tryParse(w, 
network, "1.2.3.4:http", 5678)); 1.2.3.4:80; tryParse(w, network, 
"1.2.3.4:http", 5678) = [:::1.2.3.4]:80
  stack: 55872da0b7fc 55872d9e5546 7f1351d2c60f 7f1351ccef9a 7f1351d2d7f5 
7f1351d2ea31 7f1351d035ba 7f1351ccef9a 7f1351d03c11 7f1351d2b59c 7f13518f5e0a 
55872d8438d9
  [ FAIL ] kj/async-io-test.c++:107: legacy test: AsyncIo/AddressParsing (71960 
μs)

The full log is available at 
http://perl.debian.net/rebuild-logs/sid-v6only/capnproto_0.7.0-6/capnproto_0.7.0-6_amd64-2020-06-28T02:01:53Z.build

One way to replicate this environment is like so:

  # unshare -n
  # ip li set lo up
  # ip li add dummy0 type dummy
  # ip li set dummy0 up

Cheers
Dominic

[1] this test showed approximately 100 packages in the archive failing,
but nearly all of them were due to the behaviour of libio-socket-ip-perl,
so will be fixed centrally. I'm filing bugs about the small number of
unrelated cases.
--- End Message ---
--- Begin Message ---
Source: capnproto
Source-Version: 0.7.0-7
Done: tony mancill 

We believe that the bug you reported is fixed in the latest version of
capnproto, 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 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated capnproto 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: Mon, 06 Jul 2020 11:52:29 -0700
Source: capnproto
Architecture: source
Version: 0.7.0-7
Distribution: unstable
Urgency: medium
Maintainer: Tom Lee 
Changed-By: tony mancill 
Closes: 963855
Changes:
 capnproto (0.7.0-7) unstable; urgency=medium
 .
   * Disable failing test when interface is IPv6-only (Closes: #963855)
 Thank you to Dominic Hargreaves for the bug report and instructions
 for how to reproduce the bug.
Checksums-Sha1:
 0d9bc5e2c3a9c905bf674d563cec4fc0903a0a92 2201 capnproto_0.7.0-7.dsc
 ed5c2210b05eb53fcc1b907a570d65a73a378f6a 10244 capnproto_0.7.0-7.debian.tar.xz
 c07fb6abea089704c994daa3cfea7a69118b6963 8487 capnproto_0.7.0-7_amd64.buildinfo
Checksums-Sha256:
 68ed0366ebb54cd6509d5c4de26f76cf30743d8efb42e6d320fc374970fa2c8b 2201 
capnproto_0.7.0-7.dsc
 a3b310973f7c688057355dc24accb325cb1ab3419c1b1a38b74df3cf123f1d15 10244 
capnproto_0.7.0-7.debian.tar.xz
 8d277b668cdb5aa87ac709c4b039c4ca3b1be39bfa5eddb10f62059ef1906097 8487 
capnproto_0.7.0-7_amd64.buildinfo
Files:
 5e7985d5c09f4a14da503fa30073040a 2201 devel optional capnproto_0.7.0-7.dsc
 d6480139ed35574449e175792d4924b6 10244 devel optional 
capnproto_0.7.0-7.debian.tar.xz
 63b091522bcc56efbb4af3b1bd1792c2 8487 devel optional 
capnproto_0.7.0-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl8Dd/4UHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpY2hhAAyXSFv+bPntD7G1XIkQT7i4AsqsbD
qdvmBw1qLpWgJa7esmrL3EQba+29wHX8ImJCtG01R2HUG7C1N2wQ+jGPDxYy+VJU
aL6P/sN3Ut9l8n9Lu3JuUrHqYG1DRm0iQBoho4voOJ7iPnthp2xvwhfJHMvNEMVx
9ur4XpXKcD/9BTrXY5Yz8krKOaKTG7UOCGLpiJfsB1Ta4gnvqG9SHJ5bnyMI/9dw
H/WNV4treJQ8ZOYSitceHBgAy7T1NFjYdWS+1ug2KfWBSYI5CTwOGno7EHF1khxG
t8gOe38/SaLGxKGteBIkP7PzxKARZiP4AKPgVexMihGdNJFvXw7314dEplR2Kaiy
/0ErXKXHjo04kx+BivDG55zYVdx89rP76rd3O4+KUfZmKdFoNqfXndi2SUKeXey3
7P3NTGYJKMVu8qGM+RDgmacvkbvQ3gu0ctcjzCd+UDGW9iH/ruEP60f90GDT5saB
WX5fTkd3v68s6yb6VkzABtUwt7Y5sp6SJHTvpP6hzhNZ/wtw1UMPvDfFCD4q7f0Y
Hq2sf59xor0tmkE3XIHJ0OSp7rHZv0DzHYLas5B/hacWgnCBOV2Q+ZD74nhp8aim
lM2jX/djEq064lDhQ9KdDZrpjVFqqPyECXhGFqcE4i5sAHpE9Di0l+YW6NF7oT9h

Bug#964405: lintian: autopkgtest regression: No tests were selected by your filter:

[Paul Gevers]

Source: lintian
Version: 2.82.0
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of lintian the autopkgtest of lintian fails in
testing when that autopkgtest is run with the binary packages of lintian
from unstable. It passes when run with only packages from testing. In
tabular form:

   passfail
lintianfrom testing2.82.0
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

[1] https://qa.debian.org/excuses.php?package=lintian

https://ci.debian.net/data/autopkgtest/testing/amd64/l/lintian/6153561/log.gz


Running selected and required Perl test scripts.


Files=0, Tests=0,  0 wallclock secs ( 0.26 usr +  0.07 sys =  0.33 CPU)
Result: NOTESTS


No tests were selected by your filter:

suite:tags

To select your tests, please use an appropriate argument with a
selector like:

'suite:', 'test:', 'check:', 'tag:', or 'script:'

You can also use 'minimal:', which runs only the tests that cannot
be turned off, such as the internal tests for the harness.



signature.asc
Description: OpenPGP digital signature

Processed: tagging 952009

[Debian Bug Tracking System]

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

> tags 952009 - bullseye sid
Bug #952009 {Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= 
} [src:c-icap-modules] c-icap-modules: FTBFS: 
clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant
Removed tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Processed: unarchiving 952009

[Debian Bug Tracking System]

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

> unarchive 952009
Bug #952009 {Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= 
} [src:c-icap-modules] c-icap-modules: FTBFS: 
clamav_mod.c:108:13: error: expected identifier or ‘(’ before string constant
Unarchived Bug 952009
> thanks
Stopping processing here.

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

Bug#964404: quagga is replaced by frr

[Adrian Bunk]

Source: quagga
Version: 1.2.4-4
Severity: serious

The maintained fork from quagga that continues the zebra codebase is frr,
which is already in buster:
https://tracker.debian.org/pkg/frr

Additionally shipping quagga in bullseye might bring more confusion
than benefits.

Bug#962221: Fixes for CVE-2020-13696 (#962221)

[Vasyl Gello]

Hi Mattia!

By partial I understood that upstream fixed the core part but the Debian patch 
sjould have been adapted to reflect new changes.
Jeremy, can you please correct me if I am wrong?
-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com

Skype: vasek.gello
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

July 6, 2020 6:58:05 PM UTC, Mattia Rizzolo  написав(-ла):
>On Mon, Jul 06, 2020 at 05:10:30AM +, Vasyl Gello wrote:
>> Thanks for contributing the security release! I checked your changes and 
>> pushed them to the team repo.
>> I do not have an upload rights, so CCing Sebastian and Mattia.
>
>Sure,
>
>but could either of you do a bunch of housekeeping work as well, like:
> * bumping dh compat
> * drop --dbgsym-migration
> * drop the .menu files
> * would be awesome to have the copyright file rewrote using dep-5
> * 
>
>Also, the commit adding the CVE patch mentions "partial fix", as does
>the sec-tracker page.  Can anybody explain shortly what's with that,
>where is the full fix (if there is), and how come the LTS upload claims
>this to be fully fixed instead (CCing the LTS team and the uploader for
>this).
>
>-- 
>regards,
>Mattia Rizzolo
>
>GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
>More about me:  https://mapreri.org : :'  :
>Launchpad user: https://launchpad.net/~mapreri  `. `'`
>Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: tagging 964293

[Debian Bug Tracking System]

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

> tags 964293 + moreinfo
Bug #964293 [hubicfuse] hubicfuse: error while loading libssl.so.1.0.0
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#963583: sysdig: sysdig segfaults on start

[Adrian Bunk]

Control: reassign -1 libgrpc++1 1.26.0-3
Control: retitle -1 libgrpc++1 changes ABI without changing soname
Control: forwarded -1 https://github.com/grpc/grpc/issues/23205
Control: affects -1 src:sysdig

On Tue, Jun 23, 2020 at 06:59:25PM -0700, Dima Kogan wrote:
>...
>   $ sudo sysdig ...
>   sysdig: symbol lookup error: sysdig: undefined symbol: 
> _ZN9grpc_impl23CreateCustomChannelImplERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKSt10shared_ptrINS_18ChannelCredentialsEERKNS_16ChannelArgumentsE
> 
> This sounds like #955279, but even if it is, there should be a
> Conflicts, or something, to prevent me from getting into that state.
>...

The root problem is that libgrpc++ changes ABI without changing soname.

sysdig in unstable/testing is the only package in Debian that currently 
uses libgrpc++, which explains why the problem is not reported more often.

Anyone compiling own code against libgrpc++ in buster will run into
the same problem when upgrading to bullseye.

cu
Adrian

Bug#962221: Fixes for CVE-2020-13696 (#962221)

[Mattia Rizzolo]

On Mon, Jul 06, 2020 at 05:10:30AM +, Vasyl Gello wrote:
> Thanks for contributing the security release! I checked your changes and 
> pushed them to the team repo.
> I do not have an upload rights, so CCing Sebastian and Mattia.

Sure,

but could either of you do a bunch of housekeeping work as well, like:
 * bumping dh compat
 * drop --dbgsym-migration
 * drop the .menu files
 * would be awesome to have the copyright file rewrote using dep-5
 * 

Also, the commit adding the CVE patch mentions "partial fix", as does
the sec-tracker page.  Can anybody explain shortly what's with that,
where is the full fix (if there is), and how come the LTS upload claims
this to be fully fixed instead (CCing the LTS team and the uploader for
this).

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Processed: Re: Bug#963583: sysdig: sysdig segfaults on start

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libgrpc++1 1.26.0-3
Bug #963583 [sysdig] sysdig: sysdig segfaults on start
Bug reassigned from package 'sysdig' to 'libgrpc++1'.
No longer marked as found in versions sysdig/0.26.7-2.
Ignoring request to alter fixed versions of bug #963583 to the same values 
previously set
Bug #963583 [libgrpc++1] sysdig: sysdig segfaults on start
Marked as found in versions grpc/1.26.0-3.
> retitle -1 libgrpc++1 changes ABI without changing soname
Bug #963583 [libgrpc++1] sysdig: sysdig segfaults on start
Changed Bug title to 'libgrpc++1 changes ABI without changing soname' from 
'sysdig: sysdig segfaults on start'.
> forwarded -1 https://github.com/grpc/grpc/issues/23205
Bug #963583 [libgrpc++1] libgrpc++1 changes ABI without changing soname
Set Bug forwarded-to-address to 'https://github.com/grpc/grpc/issues/23205'.
> affects -1 src:sysdig
Bug #963583 [libgrpc++1] libgrpc++1 changes ABI without changing soname
Added indication that 963583 affects src:sysdig

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

Bug#964403: goxel FTBFS on armel: Must be linked with libatomic

[Adrian Bunk]

Source: goxel
Version: 0.10.6-1
Severity: serious
Tags: ftbfs patch

https://buildd.debian.org/status/fetch.php?pkg=goxel=armel=0.10.6-1=1592688053=0

...
g++ -o goxel -fsanitize=address -fsanitize=undefined -pthread -Wl,-z,relro 
src/yocto.o src/xxhash.o src/utils.o src/tools.o src/theme.o src/tests.o 
src/system.o src/shape.o src/shader_cache.o src/script.o src/render.o 
src/quantization.o src/procedural.o src/pathtracer.o src/palette.o 
src/model3d.o src/meta.o src/mesh_utils.o src/mesh_to_vertices.o src/mesh.o 
src/material.o src/marchingcube.o src/main.o src/luagoxel.o src/layer.o 
src/imgui.o src/image.o src/gui.o src/goxel.o src/gesture3d.o src/gesture.o 
src/camera.o src/box_edit.o src/assets.o src/action.o src/utils/vec.o 
src/utils/texture.o src/utils/sound.o src/utils/mustache.o src/utils/json.o 
src/utils/ini.o src/utils/img.o src/utils/gl.o src/utils/color.o 
src/utils/cache.o src/utils/box.o src/utils/b64.o src/tools/shape.o 
src/tools/selection.o src/tools/procedural.o src/tools/plane.o src/tools/move.o 
src/tools/line.o src/tools/laser.o src/tools/fuzzy_select.o src/tools/extrude.o 
src/tools/color_picker.o src/tools/brush.o src/gui/view_panel.o 
src/gui/topbar.o src/gui/tools_panel.o src/gui/settings.o 
src/gui/render_panel.o src/gui/palette_panel.o src/gui/menu.o 
src/gui/material_panel.o src/gui/light_panel.o src/gui/layers_panel.o 
src/gui/image_panel.o src/gui/export_panel.o src/gui/debug_panel.o 
src/gui/cameras_panel.o src/gui/app.o src/gui/about.o src/formats/wavefront.o 
src/formats/vxl.o src/formats/voxlap.o src/formats/vox.o src/formats/txt.o 
src/formats/qubicle.o src/formats/povray.o src/formats/png_slices.o 
src/formats/png.o src/formats/gox.o src/formats/gltf.o src/formats/dicom.o 
-lasan -lubsan -lpng -lGL -lm -lglfw -lgtk-3 -lgdk-3 -lpangocairo-1.0 
-lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 
-lgio-2.0 -lgobject-2.0 -lglib-2.0
/usr/bin/ld: src/yocto.o: in function `std::__atomic_base::operator+=(unsigned long long)':
/usr/include/c++/9/bits/atomic_base.h:335: undefined reference to 
`__atomic_fetch_add_8'
/usr/bin/ld: src/yocto.o: in function `std::__atomic_base::store(unsigned long long, std::memory_order)':
/usr/include/c++/9/bits/atomic_base.h:397: undefined reference to 
`__atomic_store_8'
/usr/bin/ld: src/yocto.o: in function `std::__atomic_base::load(std::memory_order) const':
/usr/include/c++/9/bits/atomic_base.h:419: undefined reference to 
`__atomic_load_8'
collect2: error: ld returned 1 exit status
scons: *** [goxel] Error 1


Fix/Workaround:

--- debian/rules.old2020-07-05 21:59:58.246217695 +
+++ debian/rules2020-07-05 22:00:26.841963922 +
@@ -2,6 +2,11 @@
 export DH_VERBOSE = 1
 NUMJOBS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
 
+ifneq (,$(filter $(DEB_HOST_ARCH), armel mipsel))
+  export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic 
-Wl,--as-needed
+endif
+
+
 include /usr/share/dpkg/default.mk  # provides DEB_VERSION
 
 %:

Processed: Re: Bug#964377: bumblebee: please runtime depend on pciutils

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #964377 [src:bumblebee] bumblebee: please runtime depend on pciutils
Severity set to 'important' from 'serious'

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

Bug#964377: bumblebee: please runtime depend on pciutils

[Adrian Bunk]

Control: severity -1 important

On Mon, Jul 06, 2020 at 02:40:37PM +0200, Andreas Beckmann wrote:
> On 7/6/20 1:14 PM, Gianfranco Costamagna wrote:
> > Hello, bumblebee and bumblebee-nvidia (in Ubuntu) use lspci in their 
> > postinst files, without
> > a dependency on it
> 
> Good catch!
> Should there be a lintian test for it? I remember fixing the same thing in
> firmware-b43-installer recently.

In bumblebee this seems to be an Ubuntu-only problem:

debian/bumblebee-nvidia.postinst.Ubuntu:
  busid=$(lspci -d10de: -nn | grep '\[030[02]\]' | cut -d' ' -f1 | tr . : | 
head -1)

debian/bumblebee.postinst:
# Raring specific issue
# Also, do not rely solely on dpkg-vendor (see LP: #1061769)
if (which dpkg-vendor >/dev/null && dpkg-vendor --derives-from Ubuntu) || \
  [ -e /etc/dpkg/origins/ubuntu ]; then
# assume first device to be discrete in nvidia/nvidia
busid=$(lspci -d10de: -nn | grep '\[030[02]\]' | cut -d' ' -f1 | tr . : 
| head -1)


> Andreas

cu
Adrian

Processed: tagging 963745

[Debian Bug Tracking System]

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

> tags 963745 + ftbfs
Bug #963745 [src:haskell-regex-tdfa-text] haskell-regex-tdfa-text: Removal 
notice: Deprecated
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 963499

[Debian Bug Tracking System]

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

> tags 963499 + ftbfs
Bug #963499 [src:haskell-wl-pprint-extras] haskell-wl-pprint-extras: Removal 
notice: broken and unmaintained
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 962959

[Debian Bug Tracking System]

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

> tags 962959 + ftbfs
Bug #962959 [src:haskell-edison-api] haskell-edison-api: Removal notice: broken 
and unuseful
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> # turns this bug into non-RC, as I can't reproduce the actual crash
> retitle 959885 inkscape: unnecessary error messages when called without X 
> server
Bug #959885 [inkscape] inkscape: crashes when called without X server
Changed Bug title to 'inkscape: unnecessary error messages when called without 
X server' from 'inkscape: crashes when called without X server'.
> severity 959885 minor
Bug #959885 [inkscape] inkscape: unnecessary error messages when called without 
X server
Severity set to 'minor' from 'serious'
> tags 959885 = upstream
Bug #959885 [inkscape] inkscape: unnecessary error messages when called without 
X server
Removed tag(s) unreproducible and moreinfo.
> --
Stopping processing here.

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

Processed: tagging 963072

[Debian Bug Tracking System]

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

> tags 963072 + ftbfs
Bug #963072 [src:haskell-easytest] haskell-easytest: Does not build with 
hedgehog 1.x
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 962964

[Debian Bug Tracking System]

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

> tags 962964 + ftbfs
Bug #962964 [src:haskell-io-choice] haskell-io-choice: Removal notice: broken 
and obsolete
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 962890

[Debian Bug Tracking System]

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

> tags 962890 + ftbfs
Bug #962890 [src:haskell-bytestring-show] haskell-bytestring-show: Removal 
notice: broken and unmaintained
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 962813

[Debian Bug Tracking System]

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

> tags 962813 + ftbfs
Bug #962813 [src:haskell-tree-monad] does not build with ghc 8.8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 962962

[Debian Bug Tracking System]

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

> tags 962962 + ftbfs
Bug #962962 [src:haskell-hstatsd] haskell-hstatsd: Removal notice: broken and 
unmaintained
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#964401: sight FTBFS on i386: error: conversion from ‘long long unsigned int’ to ‘size_t’ {aka ‘unsigned int’} may change value

[Adrian Bunk]

Source: sight
Version: 20.0.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=sight=i386=20.0.0-1=1593349313=0

...
/<>/libs/core/fwData/src/fwData/Mesh.cpp: In member function 
‘size_t fwData::Mesh::getDataSizeInBytes() const’:
/<>/libs/core/fwData/src/fwData/Mesh.cpp:470:61: error: conversion 
from ‘long long unsigned int’ to ‘size_t’ {aka ‘unsigned int’} may change value 
[-Werror=conversion]
  470 | m_points&& (size += m_points->getElementSizeInBytes() * m_nbPoints);
  | ^~
/<>/libs/core/fwData/src/fwData/Mesh.cpp:471:67: error: conversion 
from ‘long long unsigned int’ to ‘size_t’ {aka ‘unsigned int’} may change value 
[-Werror=conversion]
  471 | m_cellTypes&& (size += m_cellTypes->getElementSizeInBytes() * 
m_nbCells );
  |   
^
/<>/libs/core/fwData/src/fwData/Mesh.cpp:472:65: error: conversion 
from ‘long long unsigned int’ to ‘size_t’ {aka ‘unsigned int’} may change value 
[-Werror=conversion]
  472 | m_cellData&& (size += m_cellData->getElementSizeInBytes() * 
m_cellsDataSize);
  | 
^~~
...

Processed: owner 963855

[Debian Bug Tracking System]

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

> owner 963855 tmanc...@debian.org
Bug #963855 [src:capnproto] capnproto: FTBFS on IPv6-only environments
Owner recorded as tmanc...@debian.org.
> thanks
Stopping processing here.

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

Bug#964400: haskell-yesod-core: build fails on IPv6-only buildds

[Adrian Bunk]

Source: haskell-yesod-core
Version: 1.6.18-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=haskell-yesod-core=i386=1.6.18-1=1593282031=0

...
Failures:

  test/YesodCoreTest/RawResponse.hs:63:9: 
  1) RawResponse works
   uncaught exception: IOException of type NoSuchThing
   Network.Socket.getAddrInfo (called with preferred socket type/protocol: 
AddrInfo {addrFlags = [AI_PASSIVE,AI_ADDRCONFIG], addrFamily = AF_UNSPEC, 
addrSocketType = Stream, addrProtocol = 0, addrAddress = , addrCanonName = }, host name: Just 
"127.0.0.1", service name: Just "0"): does not exist (Address family for 
hostname not supported)

  To rerun use: --match "/RawResponse/works/"

  test/YesodCoreTest/RawResponse.hs:89:5: 
  2) sendWaiResponse + responseStream
   uncaught exception: IOException of type NoSuchThing
   Network.Socket.getAddrInfo (called with preferred socket type/protocol: 
AddrInfo {addrFlags = [AI_PASSIVE,AI_ADDRCONFIG], addrFamily = AF_UNSPEC, 
addrSocketType = Stream, addrProtocol = 0, addrAddress = , addrCanonName = }, host name: Just 
"127.0.0.1", service name: Just "0"): does not exist (Address family for 
hostname not supported)

  To rerun use: --match "/sendWaiResponse + responseStream/"

  test/YesodCoreTest/RawResponse.hs:91:5: 
  3) sendWaiApplication + responseStream
   uncaught exception: IOException of type NoSuchThing
   Network.Socket.getAddrInfo (called with preferred socket type/protocol: 
AddrInfo {addrFlags = [AI_PASSIVE,AI_ADDRCONFIG], addrFamily = AF_UNSPEC, 
addrSocketType = Stream, addrProtocol = 0, addrAddress = , addrCanonName = }, host name: Just 
"127.0.0.1", service name: Just "0"): does not exist (Address family for 
hostname not supported)

  To rerun use: --match "/sendWaiApplication + responseStream/"

Randomized with seed 920512437

Finished in 0.0724 seconds
157 examples, 3 failures
Test suite tests: FAIL
Test suite logged to: dist-ghc/test/yesod-core-1.6.18-tests.log
1 of 2 test suites (1 of 2 test cases) passed.
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:154: check-ghc-stamp] Error 1


See #962019 for a discussion of a similar bug.

Bug#964399: Should ganglia be removed?

[Moritz Muehlenhoff]

Source: ganglia
Severity: serious

Should ganglia be removed? It's dead upstream (last commits from over three 
years ago,
last release from 2015), is now orphaned (last active maintainer is no longer a 
DD, but
wasn't very actively maintained to begin with, the current packaged version is 
from 2013),
most of the plugins depend on Python 2, there's unfixed security issues dating 
back to
2013 and doesn't even support ipv6 (730257).

Unless anyone steps up for maintenance (and partly becomes upstream), it should 
better
be removed.

Cheers,
Moritz

Processed: tagging 963184

[Debian Bug Tracking System]

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

> tags 963184 + ftbfs
Bug #963184 [src:ftphs] ftphs: Removal notice: broken and unmaintained
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#937378: purity-ng: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Sun, Jun 07, 2020 at 01:03:15AM +0200, Moritz Mühlenhoff wrote:
> On Fri, Aug 30, 2019 at 07:32:38AM +, Matthias Klose wrote:
> > Package: src:purity-ng
> > Version: 0.2.0-2.1
> > Severity: normal
> > Tags: sid bullseye
> > User: debian-pyt...@lists.debian.org
> > Usertags: py2removal
> > 
> > Python2 becomes end-of-live upstream, and Debian aims to remove
> > Python2 from the distribution, as discussed in
> > https://lists.debian.org/debian-python/2019/07/msg00080.html
> 
> Hi Luke/Simon,
> the last commits for purity-ng are from 2011, are you still interested
> in this? Let's remove?

I filed an RM bug now.

Cheers,
Moritz

Processed: [bts-link] source package src:libieee1284

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:libieee1284
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #936875 (http://bugs.debian.org/936875)
> # Bug title: libieee1284: Python2 removal in sid/bullseye
> #  * https://github.com/twaugh/libieee1284/issues/4
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 936875 + fixed-upstream
Bug #936875 [src:libieee1284] libieee1284: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> usertags 936875 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 936875 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#936783: kcachegrind: Python2 removal in sid/bullseye

[John Scott]

Python 3 doesn't include hotshot, so the hotshot2calltree script should be 
dropped. Upstream still includes it but it doesn't appear to have seen any 
maintenance:
https://invent.kde.org/sdk/kcachegrind/-/tree/master/converters

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

Bug#963713: [Pkg-net-snmp-devel] Bug#963713: net-snmp: CVE-2019-20892

[Sylvain Beucler]

Hi,

Do we have definite info on what versions are affected?

I cannot reproduce the issue in jessie/stretch/buster (5.7.x).

Incidentally Salvatore's test now yields an error in bullseye
(5.8dfsg-3), though I suspect the issue is at the client's level:
# snmpbulkget -v3 -Cn1 -Cr1472 -l authPriv -u testuser -a SHA -A
testpass -x AES -X testpass 127.0.0.1 1.3.6.1.2.1.1.5 1.3.6.1.2.1.1.7
Error in packet.
Reason: (genError) A general failure occured

Cheers!
Sylvain Beucler
Debian LTS Team

Bug#964339: marked as done (node-expat: autopkgtest regression: Cannot find module 'iconv')

[Debian Bug Tracking System]

Your message dated Mon, 06 Jul 2020 17:19:16 +
with message-id 
and subject line Bug#964339: fixed in node-expat 2.3.18+ds-2
has caused the Debian Bug report #964339,
regarding node-expat: autopkgtest regression: Cannot find module 'iconv'
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.)


-- 
964339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-expat
Version: 2.3.18+ds-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Thank you for fixing bug #963060, however with the upload fixing that
issued the autopkgtest of node-expat fails in testing when that
autopkgtest is run with the binary packages of node-expat from unstable.
It passes when run with only packages from testing. In tabular form:

   passfail
node-expat from testing2.3.18+ds-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-expat/6151675/log.gz

autopkgtest [16:26:52]: test command2: vows --spec ./test/**/*.js
autopkgtest [16:26:52]: test command2: [---
internal/modules/cjs/loader.js:969
  throw err;
  ^

Error: Cannot find module 'iconv'
Require stack:
- /tmp/autopkgtest-lxc.wq1g4b2f/downtmp/build.zVe/src/test/index.js
- /usr/share/nodejs/vows/bin/vows
at Function.Module._resolveFilename
(internal/modules/cjs/loader.js:966:15)
at Function.Module._load (internal/modules/cjs/loader.js:842:27)
at Module.require (internal/modules/cjs/loader.js:1026:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object.
(/tmp/autopkgtest-lxc.wq1g4b2f/downtmp/build.zVe/src/test/index.js:4:13)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions..js
(internal/modules/cjs/loader.js:1158:10)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Module.require (internal/modules/cjs/loader.js:1026:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
'/tmp/autopkgtest-lxc.wq1g4b2f/downtmp/build.zVe/src/test/index.js',
'/usr/share/nodejs/vows/bin/vows'
  ]
}
autopkgtest [16:26:52]: test command2: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-expat
Source-Version: 2.3.18+ds-2
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
node-expat, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated node-expat 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: Mon, 06 Jul 2020 19:12:53 +0200
Source: node-expat
Architecture: source
Version: 2.3.18+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Closes: 964339
Changes:
 node-expat (2.3.18+ds-2) unstable; urgency=medium
 .
   * fix hae autopkgtest depend on node-debug node-iconv;
 closes: bug#964339, thanks to Paul Gevers
Checksums-Sha1:
 48a9def1f1f914aa5e1d81bb1781641c10de4982 2282 node-expat_2.3.18+ds-2.dsc
 73717db6b29de91f008dcf68c79f0f6eb6e99b71 7432 
node-expat_2.3.18+ds-2.debian.tar.xz
 6488f14459dcbbe0af3a4378e30d1e5bf1ac0783 9653 
node-expat_2.3.18+ds-2_amd64.buildinfo
Checksums-Sha256:
 6ed2643a8eb693ee62b72decba9d4d3429352a0ddb8b0533c5becbbd2e1da7fb 2282 
node-expat_2.3.18+ds-2.dsc
 a63380944f7a36bcdacd4ea8a834226029290bd2752ac4e535683c9a060661ad 7432 
node-expat_2.3.18+ds-2.debian.tar.xz
 

Bug#964339: marked as pending in node-expat

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

Bug #964339 in node-expat 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/js-team/node-expat/-/commit/c204682242adce493e2e96920bd5672bab5de5e1


fix hae autopkgtest depend on node-debug node-iconv; closes: bug#964339, thanks 
to Paul Gevers


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/964339

Processed: Bug#964339 marked as pending in node-expat

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #964339 [src:node-expat] node-expat: autopkgtest regression: Cannot find 
module 'iconv'
Added tag(s) pending.

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

Bug#964377: bumblebee: please runtime depend on pciutils

[Gianfranco Costamagna]

Hello,

> Good catch!
> Should there be a lintian test for it? I remember fixing the same thing 
> in firmware-b43-installer recently.
> 
it would probably help a lot, yes :)

but a quick and incomplete look shows...
https://codesearch.debian.net/search?q=lspci+path%3Apostinst%24=0

only two packages affected?

G.

Bug#964384: [Debian-iot-maintainers] Bug#964384: ulfius: FTBFS with recent libmicrohttpd

[Gianfranco Costamagna]

Hello,
> This test fails while getting "http://[::1]:8080/empty;, maybe there's
> an ipv6 issue in ubuntu autopkgtest environment?
> 

they might not have ipv6 capability, or that port being already allocated? not 
sure.

> The last 2 errors will probably tell us more after the release since the
> error message will be fixed in ulfius_send_smtp_rich_email, thanks to you!
> 

thanks!

the error now with that patch is:
2020-07-06T15:19:23Z - Ulfius ERROR: Ulfius - Error sending smtp message, error 
message Couldn't connect to server
2020-07-06T15:19:23Z - Ulfius ERROR: Ulfius - Error sending smtp message, error 
message Couldn't connect to server
2020-07-06T15:19:23Z - Ulfius ERROR: Ulfius - Error sending smtp message, error 
message Couldn't connect to server

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/u/ulfius/20200706_151935_d3556@/log.gz

I honestly don't think using 8080 is a nice thing to do, probably such ports 
might be already opened

let me know if you need some more testing!

G.

Bug#963933: glib2.0: autopkgtext: ld: cannot find -lcryptsetup

[Chris Hofstaedtler]

Hi Simon,

src:util-linux will drop most static libraries in the 2.35.2-8 upload.
Please change the glib2.0 autopkgtest (by dropping the static test)
to allow this.

Many thanks,
Chris

Bug#964242: marked as done (bsdmainutils: depends on non-existing version of bsdextrautils)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jul 2020 16:06:52 +
with message-id 
and subject line Bug#964242: fixed in util-linux 2.35.2-7
has caused the Debian Bug report #964242,
regarding bsdmainutils: depends on non-existing version of bsdextrautils
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.)


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

Dear Maintainer,

# apt-cache show bsdmainutils
Package: bsdmainutils
Version: 12.1.3
Installed-Size: 22
Maintainer: Debian Bsdmainutils Team 
Architecture: all
Depends: bsdutils (>= 3.0-0), debianutils (>= 1.8), bsdextrautils (>= 
2.35.2-7), calendar, ncal
Suggests: whois, vacation, mailutils
Description: collection of more utilities from FreeBSD
Description-md5: cfee02792cc28085e80d876f62fd3b3e
Tag: implemented-in::c, interface::commandline, interface::text-mode,
 role::program, suite::bsd, uitoolkit::ncurses
Section: utils
Priority: important
Filename: pool/main/b/bsdmainutils/bsdmainutils_12.1.3_all.deb
Size: 15052
MD5sum: a60e4a237d46511e83f2e392320a94c3
SHA256: 6481904cd1a05278da5e79c08cabbca4d847f0096dfe40aa94cc635226a50fc3

But that bsdextrautils (>= 2.35.2-7) doesn't exist:

$ rmadison -s unstable bsdmainutils bsdextrautils
bsdextrautils | 2.35.2-6  | unstable   | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x
bsdmainutils  | 12.1.2| unstable   | source
bsdmainutils  | 12.1.3| unstable   | source, all

Regards,

Rene
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.35.2-7
Done: Chris Hofstaedtler 

We believe that the bug you reported is fixed in the latest version of
util-linux, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated util-linux 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: Mon, 06 Jul 2020 15:22:50 +
Source: util-linux
Architecture: source
Version: 2.35.2-7
Distribution: unstable
Urgency: medium
Maintainer: util-linux packagers 
Changed-By: Chris Hofstaedtler 
Closes: 964242
Changes:
 util-linux (2.35.2-7) unstable; urgency=medium
 .
   [ Simon McVittie ]
   * d/tests: Add a compile/link/run autopkgtest for each library
 .
   [ Chris Hofstaedtler ]
   * Build-Conflict with libcryptsetup-dev.
 Building with libcryptsetup-dev enables Verity support, but also makes
 all programs using libmount1 pull in libcryptsetup12 and libjansson.
 However, libjansson and libjson-c (used in many other "core" libraries)
 export conflicting symbols today, causing various crashes. See Debian
 bug #963932.
 Also, libcryptsetup12 pulls in libssl1.1, which causes some
 not-from-Debian software to crash (because of conflicting libssl
 symbols).
 Unfortunately this disables Verity support again, see Debian bug
  #951048.
   * Remove Important: yes from mount
   * Take over look and write from bsdmainutils (Closes: #964242)
 .
   [ jan krcmar ]
   * Update util-linux.su.pam
Checksums-Sha1:
 7324ad32db276de0f6246cd0228106d5d9897898 4337 util-linux_2.35.2-7.dsc
 5f8b6667322e85ac008684ee1a00f7225190d715 95500 
util-linux_2.35.2-7.debian.tar.xz
 bb0725e71407994e4f49a57b66e7c3866479e873 6562 
util-linux_2.35.2-7_source.buildinfo
Checksums-Sha256:
 f530383c7d6d7fd8e4b96f9f1814b4adb54b2bd0a172e0dd54ff819e829a5612 4337 
util-linux_2.35.2-7.dsc
 808bfb2918e245476f044a328d1567cb5eff219438f2be8ffd0c66b99d544f4e 95500 
util-linux_2.35.2-7.debian.tar.xz
 b39afe47cddeb34bfb57bebe4e1e1fb03a6956f73a5d3f9c267480f50919ba16 6562 
util-linux_2.35.2-7_source.buildinfo
Files:
 1d9df617367ea189ecdc2f676b814c45 4337 base required util-linux_2.35.2-7.dsc
 3aa54b7dcd756dbcbc3300281bcc29cd 95500 base required 
util-linux_2.35.2-7.debian.tar.xz
 ac6d3e8dc7092279d4420c71497fd31c 6562 base required 
util-linux_2.35.2-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAl8DROEACgkQXBPW25MF

Processed: tagging 964242

[Debian Bug Tracking System]

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

> tags 964242 + pending
Bug #964242 [bsdmainutils] bsdmainutils: depends on non-existing version of 
bsdextrautils
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#964384: [Debian-iot-maintainers] Bug#964384: ulfius: FTBFS with recent libmicrohttpd

[Nicolas Mora]

> Hello, can you please apply the two patches below to fix the build failure 
> with new libmicrohttpd and to give a more useful error message in case curl 
> fails?
> (I don't know yet why, but the autopkgtest is failing in Ubuntu)
> 
Since I'm also the upstream author, I'll fix the ftbfs in the next
release, very soon. But I must package new releases orcania and yder
first. This should be done in a few days.

> 
> also, help to track down the ubuntu failure is appreciated
> http://autopkgtest.ubuntu.com/packages/u/ulfius/groovy/amd64
> 
In the log, the first error tells us that:
framework.c:667:F:test_ulfius_framework:test_ulfius_net_type_endpoint:0:
Assertion 'response.status == 200' failed: response.status == 503, 200
== 200
This test fails while getting "http://[::1]:8080/empty;, maybe there's
an ipv6 issue in ubuntu autopkgtest environment?

The last 2 errors will probably tell us more after the release since the
error message will be fixed in ulfius_send_smtp_rich_email, thanks to you!

/Nicolas



signature.asc
Description: OpenPGP digital signature

Bug#964245: patch from pull request

[Edward Shornock]

>From dab0c1f9abda5b17cc7488f89a6fe08be7bc56a0 Mon Sep 17 00:00:00 2001
From: wisp3rwind <17089248+wisp3rw...@users.noreply.github.com>
Date: Tue, 9 Jun 2020 19:34:31 +0200
Subject: [PATCH] compatibility with breaking changes to the ast module

new in 3.10, also backported to 3.8 and 3.9: https://github.com/python/cpython/pull/20649
In fact, our generation of some Literals has been invalid since Python
3.4, fix that too.
---
 beets/util/functemplate.py | 29 -
 1 files changed, 20 insertions(+), 9 deletions(-)

Index: beets-1.4.9/beets/util/functemplate.py
===
--- beets-1.4.9.orig/beets/util/functemplate.py
+++ beets-1.4.9/beets/util/functemplate.py
@@ -73,15 +73,26 @@ def ex_literal(val):
 """An int, float, long, bool, string, or None literal with the given
 value.
 """
-if val is None:
-return ast.Name('None', ast.Load())
-elif isinstance(val, six.integer_types):
-return ast.Num(val)
-elif isinstance(val, bool):
-return ast.Name(bytes(val), ast.Load())
-elif isinstance(val, six.string_types):
-return ast.Str(val)
-raise TypeError(u'no literal for {0}'.format(type(val)))
+if sys.version_info[:2] < (3, 4):
+if val is None:
+return ast.Name('None', ast.Load())
+elif isinstance(val, six.integer_types):
+return ast.Num(val)
+elif isinstance(val, bool):
+return ast.Name(bytes(val), ast.Load())
+elif isinstance(val, six.string_types):
+return ast.Str(val)
+raise TypeError(u'no literal for {0}'.format(type(val)))
+elif sys.version_info[:2] < (3, 6):
+if val in [None, True, False]:
+return ast.NameConstant(val)
+elif isinstance(val, six.integer_types):
+return ast.Num(val)
+elif isinstance(val, six.string_types):
+return ast.Str(val)
+raise TypeError(u'no literal for {0}'.format(type(val)))
+else:
+return ast.Constant(val)
 
 
 def ex_varassign(name, expr):

Processed: unarchiving 863567, unarchiving 873978, unarchiving 887064, unarchiving 893424, unarchiving 894535

[Debian Bug Tracking System]

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

> unarchive 863567
Bug #863567 {Done: Andreas Beckmann } [rmail] rmail: unable to 
install because of unmet dependency
Unarchived Bug 863567
> unarchive 873978
Bug #873978 {Done: Andreas Beckmann } [sendmail-base] 
sendmail-base: Please check for /usr/share/sendmail/dynamic before sourcing it
Unarchived Bug 873978
> unarchive 887064
Bug #887064 {Done: Andreas Beckmann } [sendmail-bin] 
[sendmail] persistent queue runners in split daemon mode missed by 
/etc/init.d/sendmail
Unarchived Bug 887064
> unarchive 893424
Bug #893424 {Done: Andreas Beckmann } [sendmail-base] Cannot 
uninstall package
Unarchived Bug 893424
> unarchive 894535
Bug #894535 {Done: Andreas Beckmann } [sendmail] sendmail: 
Typo in apt show sendmail
Unarchived Bug 894535
> thanks
Stopping processing here.

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

Bug#964245: (no subject)

[Edward Shornock]

It looks like this was fixed in https://github.com/beetbox/beets/pull/3621

Bug#964384: ulfius: FTBFS with recent libmicrohttpd

[Gianfranco Costamagna]

Source: ulfius
Version: 2.6.7-4
Severity: serious
tags: patch

Hello, can you please apply the two patches below to fix the build failure with 
new libmicrohttpd and to give a more useful error message in case curl fails?
(I don't know yet why, but the autopkgtest is failing in Ubuntu)



https://github.com/babelouest/ulfius/pull/168

and

https://github.com/babelouest/ulfius/commit/fa157b1bf14fd1aa0bf998f1f3f9c55d15a13a3b
(updating to 2.6.8 grabs automagically this commit, while my pull request is 
not yet merged)

thanks!

also, help to track down the ubuntu failure is appreciated
http://autopkgtest.ubuntu.com/packages/u/ulfius/groovy/amd64


Gianfranco

Bug#963713: [Pkg-net-snmp-devel] Bug#963713: net-snmp: CVE-2019-20892

[Sergio Durigan Junior]

On Monday, June 29 2020, Craig Small wrote:

> Hi All
>   There's a few goes of the required patches but I think I've got them all.
> There was the v3doublefree2.patch, a format patch and then the first git
> reference in the tracker where they have re-arranged the free function so
> it tracks the reference count.
>
> The result does compile and build packages and it is not too terrible about
> the lintian warnings, but  I haven't installed or tested it yet; that's a
> job for tomorrow (which is only an hour away, but it will be much longer
> than that). If anyone is keen in the meantime go ahead and see if it works
> for you.

Hey Craig,

Thanks for the work on the patches; I've had to do the same for Ubuntu,
so I understand the complexity...  :-)

I'd like to propose an improvement on the current fix.  While doing the
backports on Ubuntu, I noticed a few other patches that were needed in
order to guarantee that the existing memory leaks were addressed.
Unfortunately, the very first upstream commit that tried to fix the CVE
ended up introducing some leaks, and in the end it was necessary to
reorganize the code a little bit to solve them all.  The commits are
scattered over the history, sometimes without much context, so it takes
a little time until we have a proper set of them to be backported.

Anyway, I took the liberty to open an MR here:

  https://salsa.debian.org/debian/net-snmp/-/merge_requests/3

This MR adds the extra patches from upstream, performs some renames, and
brings the Debian package closer to the Ubuntu version.

Let me know what you think.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

Bug#954604: Mailman 3.3.1

[Wilfried Klaebe]

Hi,

on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954604 I read that
Mailman 3.3.1 should enter debian as soon as it is released.

Mailman 3.3.1 has been released on 19 Apr 2020, according to
https://list.org/

Are there any problems left to be solved?

Regards,

Wilfried

Bug#964203: marked as done (libnginx-mod-nchan distributes old/incompatible module)

[Debian Bug Tracking System]

Your message dated Mon, 6 Jul 2020 15:26:29 +0200
with message-id 

and subject line 
has caused the Debian Bug report #964203,
regarding libnginx-mod-nchan distributes old/incompatible module
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.)


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

Severity: serious

Version: 1.18.0-3

Copied from Downstream bug in Ubuntu on Launchpad
(https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1874831)
post-merge (where we merged from Debian into Ubuntu):

---

The libnginx-mod-nchan package which is built from the nginx source
package distributes an old nchan module. The nginx source package has
bundled nchan 1.0.8 which has known issues when running with nginx >=
1.13.10

The upstream issue documents that nginx has had some changes that break
nchan < v1.2.0
https://github.com/slact/nchan/issues/460


Suggestion, update nchan to >= v1.2.0 (best v1.2.7).

this is the error I get when using the
`nchan_publisher_upstream_request` directive:

2020/04/24 01:00:35 [error] 9#9: *6 nchan: unexpected publisher message
request body buffer location. please report this to the nchan
developers. while sending to client, client: 127.0.0.1, server: _,
request: "POST /publish?topic=one HTTP/1.1", subrequest:
"/authorize_pub", upstream: "http://127.0.0.1:5000/authorize_pub
", host: "127.0.0.1"

---

You may want to include the latest stable version of nchan in the
package.  As is, nchan is broken.
--- End Message ---
--- Begin Message ---
Version: 1.18.0-1

nchan has already been upgraded in 1.18.0-1 version.

See: https://salsa.debian.org/nginx-team/nginx/-/issues/2

-- 
Best regards
 Ondřej Nový
--- End Message ---

Bug#964366: [aristocratos/bashtop] [BUG] insecure use of /tmp (#161)

[Dylan Aïssi]

Hi Jakub,

Le lun. 6 juil. 2020 à 13:29, aristocratos  a écrit :
>
> pytmpdir=$(mktemp -d "${TMPDIR:-/tmp}"/)
> pywrapper=$(mktemp "${pytmpdir}"/bashtop.psutil.)
>
> Should fix the issue.
>

Does the proposed fix by upstream look good to you?

Best,
Dylan

Processed: tagging 964309

[Debian Bug Tracking System]

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

> tags 964309 + pending
Bug #964309 [bsdmainutils] bsdmainutils: FTBFS because of missing 
libncurses-dev dependency
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug is also in stretch and buster

[Debian Bug Tracking System]

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

> unarchive 941926
Bug #941926 {Done: gregor herrmann } [src:libembperl-perl] 
FTBFS: test failure in #238 EmbperlObject/epobase.htm
Unarchived Bug 941926
> found 941926 2.5.0-10
Bug #941926 {Done: gregor herrmann } [src:libembperl-perl] 
FTBFS: test failure in #238 EmbperlObject/epobase.htm
Marked as found in versions libembperl-perl/2.5.0-10.
> tags 941926 - bullseye sid
Bug #941926 {Done: gregor herrmann } [src:libembperl-perl] 
FTBFS: test failure in #238 EmbperlObject/epobase.htm
Removed tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Bug#964377: bumblebee: please runtime depend on pciutils

[Andreas Beckmann]

On 7/6/20 1:14 PM, Gianfranco Costamagna wrote:

Hello, bumblebee and bumblebee-nvidia (in Ubuntu) use lspci in their postinst 
files, without
a dependency on it


Good catch!
Should there be a lintian test for it? I remember fixing the same thing 
in firmware-b43-installer recently.



Andreas

Processed: python-sievelib: diff for NMU version 1.1.1-3.2

[Debian Bug Tracking System]

Processing control commands:

> tags 960577 + patch
Bug #960577 [src:python-sievelib] python-sievelib FTBFS with python3-pip 20.1
Bug #96 [src:python-sievelib] python-sievelib: FTBFS: AttributeError: 
'ParsedRequirement' object has no attribute 'match_markers'
Added tag(s) patch.
Added tag(s) patch.
> tags 960577 + pending
Bug #960577 [src:python-sievelib] python-sievelib FTBFS with python3-pip 20.1
Bug #96 [src:python-sievelib] python-sievelib: FTBFS: AttributeError: 
'ParsedRequirement' object has no attribute 'match_markers'
Added tag(s) pending.
Added tag(s) pending.

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

Bug#960577: python-sievelib: diff for NMU version 1.1.1-3.2

[Adrian Bunk]

Control: tags 960577 + patch
Control: tags 960577 + pending

Dear maintainer,

I've prepared an NMU for python-sievelib (versioned as 1.1.1-3.2) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru python-sievelib-1.1.1/debian/changelog python-sievelib-1.1.1/debian/changelog
--- python-sievelib-1.1.1/debian/changelog	2020-03-07 20:52:38.0 +0200
+++ python-sievelib-1.1.1/debian/changelog	2020-07-06 14:47:15.0 +0300
@@ -1,3 +1,10 @@
+python-sievelib (1.1.1-3.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Backport upstream build fixes. (Closes: #960577)
+
+ -- Adrian Bunk   Mon, 06 Jul 2020 14:47:15 +0300
+
 python-sievelib (1.1.1-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru python-sievelib-1.1.1/debian/patches/0001-Fix-import-of-req-module-from-pip-10.patch python-sievelib-1.1.1/debian/patches/0001-Fix-import-of-req-module-from-pip-10.patch
--- python-sievelib-1.1.1/debian/patches/0001-Fix-import-of-req-module-from-pip-10.patch	2020-03-07 20:52:38.0 +0200
+++ python-sievelib-1.1.1/debian/patches/0001-Fix-import-of-req-module-from-pip-10.patch	2020-07-06 14:44:06.0 +0300
@@ -1,28 +1,33 @@
-From: Michael Fladischer 
-Date: Thu, 7 Feb 2019 10:47:07 +0100
-Subject: Fix import of req module from pip (>= 10).
+From 1deef0e2bf039a0e817ea6f19aaf1947dc9fafbc Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Fernando=20Tricas=20Garc=C3=ADa?=
+ 
+Date: Fri, 31 Aug 2018 17:11:58 +0200
+Subject: Problems with pip >=10 and pip.req (#72)
 
+Hello,
+
+it seems that pip 10 does not allow the use of pip.req (https://stackoverflow.com/questions/25192794/no-module-named-pip-req).
+I've tested with this workaround and it seems to work well.
 ---
- setup.py | 7 ++-
- 1 file changed, 6 insertions(+), 1 deletion(-)
+ setup.py | 5 -
+ 1 file changed, 4 insertions(+), 1 deletion(-)
 
 diff --git a/setup.py b/setup.py
-index 0d28fed..4fb9794 100644
+index 0d28fed..784608d 100644
 --- a/setup.py
 +++ b/setup.py
-@@ -12,9 +12,14 @@ from __future__ import unicode_literals
+@@ -12,7 +12,10 @@ from __future__ import unicode_literals
  
  import io
  from os import path
 -from pip.req import parse_requirements
- from setuptools import setup, find_packages
- 
-+# From https://stackoverflow.com/a/49867265
-+try: # for pip >= 10
++try: # for pip >= 10 (From: https://stackoverflow.com/questions/25192794/no-module-named-pip-req)
 +from pip._internal.req import parse_requirements
 +except ImportError: # for pip <= 9.0.3
 +from pip.req import parse_requirements
-+
+ from setuptools import setup, find_packages
+ 
  
- def get_requirements(requirements_file):
- """Use pip to parse requirements file."""
+-- 
+2.20.1
+
diff -Nru python-sievelib-1.1.1/debian/patches/0001-Put-the-list-of-requirements-in-setup.py.patch python-sievelib-1.1.1/debian/patches/0001-Put-the-list-of-requirements-in-setup.py.patch
--- python-sievelib-1.1.1/debian/patches/0001-Put-the-list-of-requirements-in-setup.py.patch	1970-01-01 02:00:00.0 +0200
+++ python-sievelib-1.1.1/debian/patches/0001-Put-the-list-of-requirements-in-setup.py.patch	2020-07-06 14:42:50.0 +0300
@@ -0,0 +1,63 @@
+From 91f40ec226ea288e98379da01672a46dabd89fc9 Mon Sep 17 00:00:00 2001
+From: Petr Viktorin 
+Date: Fri, 12 Oct 2018 14:32:18 +0200
+Subject: Put the list of requirements in setup.py
+
+Pip's internal API is unstable and might actually change more often
+than the list of requirements.
+
+Put the requirements in setup.py, and refer there from requirements.txt
+---
+ requirements.txt |  5 +++--
+ setup.py | 19 +--
+ 2 files changed, 4 insertions(+), 20 deletions(-)
+
+diff --git a/requirements.txt b/requirements.txt
+index dd68eb2..a10e857 100644
+--- a/requirements.txt
 b/requirements.txt
+@@ -1,2 +1,3 @@
+-future
+-six
++# Requirements are listed in setup.py. The dot on the next line refers to
++# the current directory, instructing installers to use this package's setup.py
++.
+diff --git a/setup.py b/setup.py
+index 784608d..e266fcb 100644
+--- a/setup.py
 b/setup.py
+@@ -12,30 +12,13 @@ from __future__ import unicode_literals
+ 
+ import io
+ from os import path
+-try: # for pip >= 10 (From: https://stackoverflow.com/questions/25192794/no-module-named-pip-req)
+-from pip._internal.req import parse_requirements
+-except ImportError: # for pip <= 9.0.3
+-from pip.req import parse_requirements
+ from setuptools import setup, find_packages
+ 
+ 
+-def get_requirements(requirements_file):
+-"""Use pip to parse requirements file."""
+-requirements = []
+-if path.isfile(requirements_file):
+-for req in parse_requirements(requirements_file, session="hack"):
+-# check markers, such as
+-#
+-# rope_py3k; python_version >= '3.0'
+-#
+-if req.match_markers():
+-requirements.append(str(req.req))
+-return 

Bug#964377: bumblebee: please runtime depend on pciutils

[Gianfranco Costamagna]

Source: bumblebee
Version: 3.2.1-23
Severity: serious

Hello, bumblebee and bumblebee-nvidia (in Ubuntu) use lspci in their postinst 
files, without
a dependency on it

./debian/bumblebee.postinst:busid=$(lspci -d10de: -nn | grep 
'\[030[02]\]' | cut -d' ' -f1 | tr . : | head -1)
./debian/bumblebee-nvidia.postinst.Ubuntu:  busid=$(lspci -d10de: -nn | 
grep '\[030[02]\]' | cut -d' ' -f1 | tr . : | head -1)

I think depending on pciutils might be a sane thing to do!
(I think the severity is RC, but feel free to downgrade, I don't know what is 
the severity for this bug)

cheers,

Gianfranco

Bug#959579: adapta-gtk-theme: FTBFS: make[2]: *** [Makefile:1040: all] Error 1

[Sudip Mukherjee]

On Mon, Jul 6, 2020 at 11:19 AM Samuel Henrique  wrote:
>
> Hello Sudip,
>
> Just a quick update, I spoke to Franciscarlos (he will reply back here
> soon) and he intends to keep the package, so your patch will be
> accepted, he just wants to confirm that the package is working fine
> with the latest version of gnome.

thats great.

>
> Meanwhile, can you push your changes to the git repo?

Sure, I have raised a merge request after changing the release to
"UNRELEASED", so that you can accept it after Franciscarlos has tested
it.
Kept it UNRELEASED as I assumed you might want to update the
Standards-Version and debhelper also (which I should not do as part of
NMU).


-- 
Regards
Sudip

Bug#950772: marked as done (swupdate: FTBFS during separate arch/indep builds)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jul 2020 11:00:10 +
with message-id 
and subject line Bug#950772: fixed in swupdate 2020.04-1
has caused the Debian Bug report #950772,
regarding swupdate: FTBFS during separate arch/indep builds
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.)


-- 
950772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swupdate
Version: 2019.04+git20190903.c3ef374-1~exp1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

swupdate/experimental FTBFS during separate arch and indep builds (as
done on the buildds). But it builds fine if both are being done within
one build process.

binary-arch fails with:

   dh_installman -a
dh_installman: error: Cannot find (any matches for) "doc/build/man/swupdate.1" 
(tried in ., debian/tmp)

dh_installman: error: Aborting due to earlier error
make: *** [debian/rules:28: binary-arch] Error 25


binary-indep fails with:

   dh_auto_test -i
make -j3 test
make[1]: Entering directory '/build/swupdate-2019.04+git20190903.c3ef374'
  CC  test/test_crypt.o
make[2]: *** No rule to make target 'test/test_crypt.lnk', needed by 'tests'.  
Stop.
make[2]: *** Waiting for unfinished jobs
  CC  test/test_hash.o
make[1]: *** [Makefile:481: test] Error 2
make[1]: Leaving directory '/build/swupdate-2019.04+git20190903.c3ef374'
dh_auto_test: error: make -j3 test returned exit code 2
make: *** [debian/rules:28: build-indep] Error 25


Andreas


swupdate_2019.04+git20190903.c3ef374-1~exp1_arch.log.gz
Description: application/gzip


swupdate_2019.04+git20190903.c3ef374-1~exp1_indep.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: swupdate
Source-Version: 2020.04-1
Done: =?utf-8?b?U1ogTGluICjmnpfkuIrmmbop?= 

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

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

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

Debian distribution maintenance software
pp.
SZ Lin (林上智)  (supplier of updated swupdate 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: Sun, 05 Jul 2020 20:01:25 +0800
Source: swupdate
Binary: lua-swupdate lua-swupdate-dbgsym swupdate swupdate-dev swupdate-doc
Architecture: source amd64 all
Version: 2020.04-1
Distribution: unstable
Urgency: medium
Maintainer: Stefano Babic 
Changed-By: SZ Lin (林上智) 
Description:
 lua-swupdate - swupdate bindings for the Lua language
 swupdate   - Software update framework for embedded systems
 swupdate-dev - Development files for swupdate framework
 swupdate-doc - Documentation for swupdate framework
Closes: 948673 950772
Changes:
 swupdate (2020.04-1) unstable; urgency=medium
 .
   [ Nobuhiro Iwamatsu ]
   * Add d/missing-sources
 .
   [ SZ Lin (林上智) ]
   * Bump Standards-Version to 4.5.0
   * Bump debhelper-compat to 13
   * Add configuration setting of Salsa CI
   * Add a dependency package for CI testing
   * Fix autopkgtest error
 .
   [ Bastian Germann ]
   * Fix nodoc usage (Closes: #950772)
   * Introduce lua package and nolua profile
   * Remove file filter
   * defconfig: Activate CONFIG_SIGALG_CMS
   * defconfig: Set Debian's default grubenv path
   * defconfig: Save suricatta state in grubenv
   * defconfig: Enable rdiff handler
   * defconfig: Enable zstd compression
   * Update signing key for version 2020.04
   * Remove upstream patches
   * lintian: debian-rules-uses-as-needed-linker-flag
   * d/copyright: suricatta test files were moved
   * Add new handlers
   * Enable cross compilation
   * Add a backports profile
   * New upstream version 2020.04 (Closes: #948673)
Checksums-Sha1:
 250f18ff1108352a5966ed5167371973b2b466ff 2756 swupdate_2020.04-1.dsc
 860f10dedee76ad8f1eb842791338557d4ae702f 5595840 swupdate_2020.04.orig.tar.xz
 d721485a45e379ec703b54bf4e101bd43c49a57d 129572 
swupdate_2020.04-1.debian.tar.xz
 b8ac859812c417f9e55b4034a74f11ee4b4b964b 22064 
lua-swupdate-dbgsym_2020.04-1_amd64.deb
 1cb11e8fa084a628f52b2a3f53f923e247f5 17952 lua-swupdate_2020.04-1_amd64.deb
 bd50d004c4aebfc297b283e9a29e18e7462666ef 17348 

Bug#963346: marked as done (golang-github-openshift-api: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/openshift/api github.com/openshift/api/annotations github.com/open

[Debian Bug Tracking System]

Your message dated Mon, 06 Jul 2020 10:49:50 +
with message-id 
and subject line Bug#963346: fixed in golang-github-openshift-api 
4.0+git20190508.81d064c-4
has caused the Debian Bug report #963346,
regarding golang-github-openshift-api: FTBFS: dh_auto_test: error: cd _build && 
go test -vet=off -v -p 4 github.com/openshift/api 
github.com/openshift/api/annotations github.com/openshift/api/apps 
github.com/openshift/api/apps/v1 github.com/openshift/api/authorization 
github.com/openshift/api/authorization/v1 github.com/openshift/api/build 
github.com/openshift/api/build/v1 github.com/openshift/api/config 
github.com/openshift/api/config/v1 github.com/openshift/api/image 
github.com/openshift/api/image/docker10 
github.com/openshift/api/image/dockerpre012 github.com/openshift/api/image/v1 
github.com/openshift/api/kubecontrolplane 
github.com/openshift/api/kubecontrolplane/v1 
github.com/openshift/api/legacyconfig/v1 github.com/openshift/api/network 
github.com/openshift/api/network/v1 github.com/openshift/api/oauth 
github.com/openshift/api/oauth/v1 
github.com/openshift/api/openshiftcontrolplane 
github.com/openshift/api/openshiftcontrolplane/v1 
github.com/openshift/api/operator github.com/openshift/api/operator/v1 
github.com/openshift/api/operator/v1alpha1 github.com/openshift/api/osin 
github.com/openshift/api/osin/v1 github.com/openshift/api/pkg/serialization 
github.com/openshift/api/project github.com/openshift/api/project/v1 
github.com/openshift/api/quota github.com/openshift/api/quota/v1 
github.com/openshift/api/route github.com/openshift/api/route/v1 
github.com/openshift/api/security github.com/openshift/api/security/v1 
github.com/openshift/api/servicecertsigner 
github.com/openshift/api/servicecertsigner/v1alpha1 
github.com/openshift/api/template github.com/openshift/api/template/v1 
github.com/openshift/api/tools/genswaggertypedocs github.com/openshift/api/user 
github.com/openshift/api/user/v1 github.com/openshift/api/webconsole 
github.com/openshift/api/webconsole/v1 returned exit code 1
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.)


-- 
963346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-openshift-api
Version: 4.0+git20190508.81d064c-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package golang-github-openshift-api
> dpkg-buildpackage: info: source version 4.0+git20190508.81d064c-3
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Dmitry Smirnov 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --builddirectory=_build --buildsystem=golang --with=golang
>dh_auto_clean -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf_clean -O--builddirectory=_build -O--buildsystem=golang
>dh_clean -O--builddirectory=_build -O--buildsystem=golang
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building golang-github-openshift-api using existing 
> ./golang-github-openshift-api_4.0+git20190508.81d064c.orig.tar.xz
> dpkg-source: info: building golang-github-openshift-api in 
> golang-github-openshift-api_4.0+git20190508.81d064c-3.debian.tar.xz
> dpkg-source: info: building golang-github-openshift-api in 
> golang-github-openshift-api_4.0+git20190508.81d064c-3.dsc
>  debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go generate -v github.com/openshift/api 
> github.com/openshift/api/annotations github.com/openshift/api/apps 
> github.com/openshift/api/apps/v1 github.com/openshift/api/authorization 
> github.com/openshift/api/authorization/v1 github.com/openshift/api/build 
> github.com/openshift/api/build/v1 github.com/openshift/api/config 
> github.com/openshift/api/config/v1 github.com/openshift/api/image 
> github.com/openshift/api/image/docker10 
> 

Bug#959579: adapta-gtk-theme: FTBFS: make[2]: *** [Makefile:1040: all] Error 1

[Samuel Henrique]

Hello Sudip,

Just a quick update, I spoke to Franciscarlos (he will reply back here
soon) and he intends to keep the package, so your patch will be
accepted, he just wants to confirm that the package is working fine
with the latest version of gnome.

Meanwhile, can you push your changes to the git repo?

Thanks,

-- 
Samuel Henrique 

Bug#962653: marked as done (davical build depends on rst2pdf that might not be in bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jul 2020 09:48:35 +
with message-id 
and subject line Bug#962653: fixed in davical 1.1.9.3-1.1
has caused the Debian Bug report #962653,
regarding davical build depends on rst2pdf that might not be in bullseye
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.)


-- 
962653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: davical
Version: 1.1.9.3-1
Severity: serious
Control: block 962651 by -1

davical build depends on rst2pdf that might not be in bullseye
due to #962651.
--- End Message ---
--- Begin Message ---
Source: davical
Source-Version: 1.1.9.3-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
davical, 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 962...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated davical 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: Sun, 05 Jul 2020 12:34:48 +0300
Source: davical
Architecture: source
Version: 1.1.9.3-1.1
Distribution: unstable
Urgency: high
Maintainer: Davical Development Team 
Changed-By: Adrian Bunk 
Closes: 962653
Changes:
 davical (1.1.9.3-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Stop using rst2pdf that might not be in bullseye. (Closes: #962653)
Checksums-Sha1:
 90d7613a629e3e96a7d97af97eeedd7b3b6bff15 2099 davical_1.1.9.3-1.1.dsc
 cdc7d4f6bb8d536a49a85df6e19e3bab939913bd 12860 
davical_1.1.9.3-1.1.debian.tar.xz
Checksums-Sha256:
 c10e9926b78a9e11677027573a092aafb5181fe3ca961452da7773be47434507 2099 
davical_1.1.9.3-1.1.dsc
 8ec48ea7fdde65148414321f087260295fe96516376c4f6da9b9f18227ad0d9f 12860 
davical_1.1.9.3-1.1.debian.tar.xz
Files:
 040b67e6b43225571bfb89ac9f61c1a9 2099 web optional davical_1.1.9.3-1.1.dsc
 20d4ba7fa2df84dc6648ed7bc871efa7 12860 web optional 
davical_1.1.9.3-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8Bn1cACgkQiNJCh6LY
mLHY0hAAzQTb8CYpRfKT4JS6L1qxBDZmCwHUjAFUW3HlF1KTl95+l8LPeeiH6ChG
mWCrKzd3T7ODWNPH2quh3xVIsgU9goOb5YXvosRyuBgpbrduM8ZoymDg1GkeSokB
+28/5RnVYGb2vi3iv01eORfWAq2lTxU4B8sOrQtYu9j92TFr51ltEeK8woYJpZ5i
PDVZk5505gocP/0czGWxM0vKuc9pvVkvOtiYd9jHooEcTI9w/bvNApYNsUDd28Gu
MHM392WhclT5/UWeLzDfqj3kChhNZGAtrFGYgVMIsd1wt5I5ce6OBF9ToqJzLtQZ
lbU1pvNxesVH7gAlXD+aqP4hqOyydiZ9bjohqDylLxehcDhBERTPlKixdSlWaW+9
e1cvyaUP+MNTleZKBv8zFsoD/sxH11r9slO8KknfkCe3ZMqrJH8gyTAED31Z+jvw
ct8ipY1oP3WiTjjD4MgQg4FGceq+826yh4lT8TfNTZCsDCMeond/koeM6xUDdRHv
80yEeXZZoV5NgRlHHx9XBsoZ/lrJuKerEeHQrlMJDv1VRK43h8O3jvG1OiK7UEVn
/BqjYUXp8pYHNnXvj7i0hMBWqbdxKlOzAsA3cgFtLYrLNd8hdJGptt0mjw4JwveA
F3Eogd1rLyoUub1XtkxyfSm0YArvpFjUom4QNL9/voUgZoAuU14=
=sxFz
-END PGP SIGNATURE End Message ---

Bug#962653: [DAViCal-devel] Bug#962653: davical: diff for NMU version 1.1.9.3-1.1

[Adrian Bunk]

On Mon, Jul 06, 2020 at 08:34:12AM +0200, Florian Schlichting wrote:
> On Sun, Jul 05, 2020 at 12:46:52PM +0300, Adrian Bunk wrote:
> > I've prepared an NMU for davical (versioned as 1.1.9.3-1.1) and uploaded 
> > it to DELAYED/3. Please feel free to tell me if I should cancel it.
> 
> ACK
> 
> I've been waiting for the pdfrw maintainer to say something about the
> expected future of his package, but I guess no answer is also an answer,
> and rst2pdf has no bearing at all on the functioning of davical. So
> thanks for going ahead with this.

Thanks, rescheduled for immediate upload.

> Florian

cu
Adrian

Bug#964356: marked as done (libcoarrays-{mpich,openmpi}-dev: not co-installable due to usr/lib/x86_64-linux-gnu/libcaf_mpi.a)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jul 2020 09:18:59 +
with message-id 
and subject line Bug#964356: fixed in open-coarrays 2.9.0-2
has caused the Debian Bug report #964356,
regarding libcoarrays-{mpich,openmpi}-dev: not co-installable due to 
usr/lib/x86_64-linux-gnu/libcaf_mpi.a
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.)


-- 
964356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcoarrays-mpich-dev,libcoarrays-openmpi-dev
Version: 2.9.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files ...

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

  Selecting previously unselected package libcoarrays-openmpi-dev:amd64.
  Preparing to unpack .../38-libcoarrays-openmpi-dev_2.9.0-1_amd64.deb ...
  Unpacking libcoarrays-openmpi-dev:amd64 (2.9.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-wpbcvq/38-libcoarrays-openmpi-dev_2.9.0-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libcaf_mpi.a', which is also 
in package libcoarrays-mpich-dev:amd64 2.9.0-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-wpbcvq/38-libcoarrays-openmpi-dev_2.9.0-1_amd64.deb
 

cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: open-coarrays
Source-Version: 2.9.0-2
Done: Alastair McKinstry 

We believe that the bug you reported is fixed in the latest version of
open-coarrays, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated open-coarrays 
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: Mon, 06 Jul 2020 09:50:30 +0100
Source: open-coarrays
Architecture: source
Version: 2.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 964356
Changes:
 open-coarrays (2.9.0-2) unstable; urgency=medium
 .
   * Fix symlinks for libcaf_mpi.a to be in $libdir/open-coarrays/$mpi/lib only.
 Closes: #964356
Checksums-Sha1:
 7d5fc3b48dc23596ded87acecbae6e8580887298 2330 open-coarrays_2.9.0-2.dsc
 1b85780abcae1cd8d454c7a95f8913fd725a2e3d 9500 
open-coarrays_2.9.0-2.debian.tar.xz
Checksums-Sha256:
 9fd09c44fce1de80aa60b5426ae9ca7616d4a91230b9f47f1b41e929f854fe3c 2330 
open-coarrays_2.9.0-2.dsc
 8da6319de19c4559972506941f82d309547632e5bb5cfbbf7e45cf671bf2d696 9500 
open-coarrays_2.9.0-2.debian.tar.xz
Files:
 345058c632c29345684cc8d4b5428d53 2330 utils optional open-coarrays_2.9.0-2.dsc
 bfaca735de8d0be9fefe2a1f236ef39c 9500 utils optional 
open-coarrays_2.9.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl8C5ycACgkQy+a7Tl2a
06W1gw//VH6/hc1Ppwvwzs5Ruy2Jgm/Kc0ougafe8tVMIHl6FoskSHNOx+a2JxyP
kHIEg7+bleiregBI1UdUrkpmTFJPzkZfScWOE/vTkUGL9YLogfdo7s/+vnCjwDxo
ZTggik/xkBkpyoNxPtsUbYS1E5cXpr6wzDcTNaMczWW2/GvPaMwd3lSIEGOGbTKz
cjRed2/Q8O+OdUHVdIWlgZONSMbSqHVu3ftJY+GY9K8BgUCtd6zRT6Y486Lx0QiP
rCegYvS4RgzBzkLKQEffhalSf4BsNXz9XFu7TF1l82TiyMjASriyOXYZMTgSdQWz
QG8eOIvO7t4+a4mwUlwmxyOnxB32/+MXLLFjbger9tZt4Sce9UscmUZSLYsapOl3
1/kymmwesfO/XMWQPPQBK8zqIc9wjgnctkzDvw+Nch4JunjrodiVbE8eYWpPsKOc
hDzyQ0KernMCblkldMUFjh45ArmLDukzSIF56cyXudCVlPpM+KmMsT0FsVU3f/E5
ygDfiPs71633f7pAEolMGYzxWz9QCpRfiTbIcp+MldZEblvt7mZHaY6hTRlyVyAl
lICSpZjhHIJhgx8R2HuvZ0ETpDzSKRUk7irjJ7p9ZgmFll2/81f+2dXkCkelaoj0
FKl2GmLu1Pa/0owyiV2a1wlwPYa5BJRe5UvafZFsHbzkNyMlMtI=
=/xEm
-END PGP SIGNATURE End Message ---

Processed: affects 964242 javahelper

[Debian Bug Tracking System]

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

> affects 964242 javahelper
Bug #964242 [bsdmainutils] bsdmainutils: depends on non-existing version of 
bsdextrautils
Added indication that 964242 affects javahelper
> thanks
Stopping processing here.

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

Processed: Re: Bug#962553: gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #962553 {Done: Adrian Bunk } [src:gff2aplot] gffread: 
autopkgtest needs update for new version of gff2aplot: warning on stderr
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gff2aplot/2.0-13.

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

Bug#962553: gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr

[Adrian Bunk]

Control: reopen -1

On Mon, Jul 06, 2020 at 01:07:22AM +0200, Graham Inggs wrote:
> Hi Adrian
> 
> On Sun, 5 Jul 2020 at 19:02, Adrian Bunk  wrote:
> > This is #962550.
> 
> Are you sure?
> 
> The failing test was with ligclib1 0.11.8-1 from testing and gff2aplot
> 2.0-13 from unstable.

Right you are, thanks for noticing my mistake.

The actual problem is:
Due to the dh compat bump in gff2aplot the gffread autopkgtest runs
additional tests, and on two of these gffread is segfaulting.

> Regards
> Graham

cu
Adrian

Bug#964242: bsdmainutils: depends on non-existing version of bsdextrautils

[Markus Koschany]

affects 964242 javahelper
thanks

This also affects javahelper which depends on bsdmainutils and breaks a
lot of Java packages in Debian currently.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#962275: snort: Failed to start LSB

[Javier Fernandez-Sanguino]

Dear Thorsten,

Indeed I have found two issues in the Snort package related to this bug
report:

1.- The location of the libraries in /etc/snort.conf is not correct for
different architectures. I need to find a way to ammend this value when the
package gets compiled (or find a way to locate this libraries in a common
place for all architectures)
2.- There are some symbols missing in
/usr/lib/x86_64-linux-gnu/libsfbpf.so.0

I have not yet found a way to fix either 1 or 2, and will continue
investigating.

Best regards

Javier

Bug#925749: omit the problematic test to fix this bug

[zhao feng]

I have opened a merge request
https://salsa.debian.org/med-team/liblemon/-/merge_requests/3
to fix this bug.

I think it is acceptable to omit the lgf_reader_writer_test. This test
deals with IO part of the library. and it had minor influence on the
whole.

This merge request can be successfully run:
https://salsa.debian.org/zhaofeng-shu33-guest/liblemon/-/jobs/849082

Bug#946915: marked as done (espresso FTBFS on archs where it build in the past)

[Debian Bug Tracking System]

Your message dated Mon, 6 Jul 2020 10:56:36 +0300
with message-id <20200706075636.GA6674@localhost>
and subject line Re: Bug#946915: espresso FTBFS on archs where it build in the 
past
has caused the Debian Bug report #946915,
regarding espresso FTBFS on archs where it build in the past
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.)


-- 
946915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: espresso
Version: 6.4.1-1
Severity: serious
Tags: ftbfs
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package is part of the "scalapack mumps petsc slepc" transition and I want
to schedule binNMU's. However, your last upload of the package FTBFS on every
arch except i386 (amd64 was uploaded by you).

Can you please fix your package? If it remains in the current state for too
long, I'll probably remove it from testing as otherwise the transition can't
finish.

Paul

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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl35PzgACgkQnFyZ6wW9
dQqYzQf+M7VDuLIXA9ltDOjdvTC0Vj0HWbKNsw9GlOLkUN8MlITVqfeyTxtFJBWS
cHggwbdcPADWzJohDmXi4YB2sadC//KclvBlL2q/RNpHd3ir3MH+9z604dM5rI0T
D/557OYjzAVKPHh5sGPnoCbYSqNp3oUQF3x9XOUbOWtQRVUqXOkyYpybSL/XQovi
ubquLK3SyVurd+U5UEvJoJg3uVJ5DtAt0KnihnVEp4elfTSQwAccRiwoJDKBgU2j
yJcO0irwBJD4w9USpjNWr660xVgZJflotlzIPebA81bXwQzBiRzkdrUBCouM/e/I
o6q0LZXzgVICSC7lM+dUQz1wk3opnw==
=h0tf
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 6.5-1

On Tue, Dec 17, 2019 at 09:48:56PM +0100, Paul Gevers wrote:
>...
> Your package is part of the "scalapack mumps petsc slepc" transition and I 
> want
> to schedule binNMU's. However, your last upload of the package FTBFS on every
> arch except i386 (amd64 was uploaded by you).
>...

https://buildd.debian.org/status/logs.php?pkg=espresso=6.5-1

armel is #818432.

cu
Adrian--- End Message ---

Processed: tagging 956680

[Debian Bug Tracking System]

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

> tags 956680 + fixed-upstream
Bug #956680 [src:xneur] xneur: Please migrate to enchant-2
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: tagging 964360

[Debian Bug Tracking System]

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

> tags 964360 + bullseye sid
Bug #964360 [libghc-doctemplates-doc] libghc-doctemplates-doc: depends on 
unavailable haddock-interface-33
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Processed: found 964366 in 0.9.18-1

[Debian Bug Tracking System]

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

> found 964366 0.9.18-1
Bug #964366 [bashtop] bashtop: insecure use of /tmp
Marked as found in versions bashtop/0.9.18-1.
> thanks
Stopping processing here.

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

Bug#960073: Package:python-pyqt5 Run the example code with Trace and crash (SIGABRT)【请注意，邮件由mity...@gmail.com代发】

[pengzon...@uniontech.com]

Hi!

Sorry for my late reply. I preload libGLX_mesa.so.0 , and then run  the code on 
the arm machine is ok.
I tried to debug it, and then I found something different. The parameter of 
__glXLookupVendorByName is NVIDIA instead of mesa, it will dlopen 
libGLX_nvidia.so.0,
but my Graphics Card is AMD, only IibGLX_mesa.so.0 can be found locally, so 
__glXLookupVendorByName failed.

(gdb) b libglxmapping.c:574
Breakpoint 4 at 0xf3a993d0: file ../../../src/GLX/libglxmapping.c, line 574.
(gdb) r
[...]
Thread 1 "python" hit Breakpoint 4, __glXLookupVendorByScreen 
(dpy=dpy@entry=0xab1f8de0, screen=screen@entry=0) at 
../../../src/GLX/libglxmapping.c:574
(gdb) p name
$11 = 0xe0006330 "nvidia"

(gdb) b libglxmapping.c:430
Breakpoint 5 at 0xf3a97f74: file ../../../src/GLX/libglxmapping.c, line 430.
(gdb) r
[...]
Thread 1 "python" hit Breakpoint 5, __glXLookupVendorByName 
(vendorName=0xe0006110 "nvidia") at ../../../src/GLX/libglxmapping.c:430
(gdb) p filename
$12 = 0xab1ecc40 "libGLX_nvidia.so.0"
(gdb) 

I tried to continue debug, but I didn't find why filename is nvidia. 
 If you could please shed some light on this topic, I would really appreciate 
it.
Thank you in advance.

BRs
//Zongli

Bug#951059: marked as done (mariadb-server-10.3: lc_messages=fr_FR leads to upgrade crash with apt)

[Debian Bug Tracking System]

Your message dated Mon, 06 Jul 2020 06:48:43 +
with message-id 
and subject line Bug#951059: fixed in mariadb-10.3 1:10.3.23-1
has caused the Debian Bug report #951059,
regarding mariadb-server-10.3: lc_messages=fr_FR leads to upgrade crash with apt
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.)


-- 
951059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mariadb-server-10.3
Version: 1:10.3.22-0+deb10u1
Severity: grave
Tags: l10n d-i
Justification: renders package unusable

Dear Maintainer,

when upgrading to latest stable release of mariadb-server, with apt-get upgrade,
the installation failed, the server does not start again, and I find on syslog:

mariadb-server-10.3.postinst[23690]: 2020-02-10 14:36:06 0 [ERROR] Aborting
mariadb-server-10.3.postinst[23690]: Installation of system tables failed!  
Examine the logs in
mariadb-server-10.3.postinst[23690]: /var/lib/mysql for more information.
mariadb-server-10.3.postinst[23690]:
mariadb-server-10.3.postinst[23690]: The problem could be conflicting 
information in an external
mariadb-server-10.3.postinst[23690]: my.cnf files. You can ignore these by 
doing:
mariadb-server-10.3.postinst[23690]:
mariadb-server-10.3.postinst[23690]: shell> /usr/bin/mysql_install_db 
--defaults-file=~/.my.cnf
mariadb-server-10.3.postinst[23690]:
mariadb-server-10.3.postinst[23690]: You can also try to start the mysqld 
daemon with:
mariadb-server-10.3.postinst[23690]:
mariadb-server-10.3.postinst[23690]: shell> /usr/sbin/mysqld 
--skip-grant-tables --general-log &
mariadb-server-10.3.postinst[23690]:
mariadb-server-10.3.postinst[23690]: and use the command line tool 
/usr/bin/mysql
mariadb-server-10.3.postinst[23690]: to connect to the mysql database and look 
at the grant tables:
mariadb-server-10.3.postinst[23690]:
mariadb-server-10.3.postinst[23690]: shell> /usr/bin/mysql -u root mysql
mariadb-server-10.3.postinst[23690]: mysql> show tables;
mariadb-server-10.3.postinst[23690]:
mariadb-server-10.3.postinst[23690]: Try 'mysqld --help' if you have problems 
with paths.  Using
mariadb-server-10.3.postinst[23690]: --general-log gives you a log in 
/var/lib/mysql that may be helpful.
mariadb-server-10.3.postinst[23690]:
mariadb-server-10.3.postinst[23690]: The latest information about 
mysql_install_db is available at
mariadb-server-10.3.postinst[23690]: 
https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
mariadb-server-10.3.postinst[23690]: You can find the latest source at 
https://downloads.mariadb.org and
mariadb-server-10.3.postinst[23690]: the maria-discuss email list at 
https://launchpad.net/~maria-discuss
mariadb-server-10.3.postinst[23690]:
mariadb-server-10.3.postinst[23690]: Please check all of the above before 
submitting a bug report
mariadb-server-10.3.postinst[23690]: at http://mariadb.org/jira
...
mysqld[23967]: 2020-02-10 14:36:07 0 [ERROR] Aborting
systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: mariadb.service: Failed with result 'exit-code'.
systemd[1]: Failed to start MariaDB 10.3.22 database server.

No error written in /var/log/mysql/error.log
This is just that the upgrade script failed to complete.

It crashed my 3 servers with MariaDB on it.
After searching for a while (doing the 'apt-get upgrade' again and again, 
restoring my VMs snapshots each time),
I found that removing the following line in my config before doing the upgrade 
resolved the issue:
lc_messages = fr_FR

This is the only way I managed to fix the error.

I also tested the 'testing' version of the package, with the same error at the 
end.


Best regards,
Jeremie LEGRAND


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

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

Versions of packages mariadb-server-10.3 depends on:
ii  adduser   3.118
ii  debconf [debconf-2.0] 1.5.71
ii  galera-3  25.3.25-2
ii  gawk  1:4.2.1+dfsg-1
ii  iproute2  4.20.0-2
ii  libc6 2.28-10
ii  libdbi-perl   1.642-1+b1
ii  libgnutls30   3.6.7-4+deb10u2
ii  libpam0g  1.3.1-5
ii  libstdc++68.3.0-6
ii  lsb-base