Bug#1001827: minder FTBFS: error: lvalue required as unary ‘&’ operand

[Helmut Grohne]

Source: minder
Version: 1.13.1-1
Severity: serious
Tags: ftbfs

minder fails to build from source in unstable. A non-parallel build now
ends as follows:

| FAILED: com.github.phase1geo.minder.p/meson-generated_src_DrawArea.c.o
| cc -Icom.github.phase1geo.minder.p -I. -I.. -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/gee-0.8 -I/usr/include/granite 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gio-unix-2.0 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/x86_64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/libxml2 -I/usr/include/gtksourceview-4 -I/usr/include/libhandy-1 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -w 
'-DGETTEXT_PACKAGE="com.github.phase1geo.minder"' -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -include 
config.h -MD -MQ com.github.phase1geo.minder.p/meson-generated_src_DrawArea.c.o 
-MF com.github.phase1geo.minder.p/meson-generated_src_DrawArea.c.o.d -o 
com.github.phase1geo.minder.p/meson-generated_src_DrawArea.c.o -c 
com.github.phase1geo.minder.p/src/DrawArea.c
| com.github.phase1geo.minder.p/src/DrawArea.c: In function 
‘draw_area_set_node_mode’:
| com.github.phase1geo.minder.p/src/DrawArea.c:6007:53: error: lvalue required 
as unary ‘&’ operand
|  6007 | draw_area_set_cursor (self, 
_AREA_text_cursor);
|   | ^
| com.github.phase1geo.minder.p/src/DrawArea.c: In function 
‘draw_area_set_connection_mode’:
| com.github.phase1geo.minder.p/src/DrawArea.c:6137:53: error: lvalue required 
as unary ‘&’ operand
|  6137 | draw_area_set_cursor (self, 
_AREA_text_cursor);
|   | ^
| com.github.phase1geo.minder.p/src/DrawArea.c: In function 
‘draw_area_on_motion’:
| com.github.phase1geo.minder.p/src/DrawArea.c:11162:149: error: lvalue 
required as unary ‘&’ operand
| 11162 |   
  draw_area_set_cursor (self, 
_AREA_url_cursor);
|   |   
  ^
| com.github.phase1geo.minder.p/src/DrawArea.c:11174:149: error: lvalue 
required as unary ‘&’ operand
| 11174 |   
  draw_area_set_cursor (self, 
_AREA_text_cursor);
|   |   
  ^
| com.github.phase1geo.minder.p/src/DrawArea.c: In function 
‘draw_area_handle_control’:
| com.github.phase1geo.minder.p/src/DrawArea.c:19241:85: error: lvalue required 
as unary ‘&’ operand
| 19241 | 
draw_area_set_cursor (self, _AREA_url_cursor);
|   |   
  ^
| ninja: build stopped: subcommand failed.
| dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 -v 
returned exit code 1
| make: *** [debian/rules:12: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

Helmut

Bug#1001734: marked as done (golang-github-rogpeppe-go-internal: autopkgtest regression: Reversed (or previously applied) patch detected!)

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 04:48:27 +
with message-id 
and subject line Bug#1001734: fixed in golang-github-rogpeppe-go-internal 
1.8.0-4
has caused the Debian Bug report #1001734,
regarding golang-github-rogpeppe-go-internal: autopkgtest regression: Reversed 
(or previously applied) patch detected!
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.)


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

Source: golang-github-rogpeppe-go-internal
Version: 1.8.0-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of golang-github-rogpeppe-go-internal the 
autopkgtest of golang-github-rogpeppe-go-internal fails in testing when 
that autopkgtest is run with the binary packages of 
golang-github-rogpeppe-go-internal from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
golang-github-rogpeppe-go-internal from testing1.8.0-3
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=golang-github-rogpeppe-go-internal


https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-rogpeppe-go-internal/17556363/log.gz

   debian/rules override_dh_auto_test
make[1]: Entering directory 
'/tmp/autopkgtest-lxc.k67h7x0n/downtmp/autopkgtest_tmp'

patch -N -p1 -i debian/0001-Allow-TestSimple-cover-to-PASS.patch
patching file 
_build/src/github.com/rogpeppe/go-internal/testscript/testscript.go

Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file 
_build/src/github.com/rogpeppe/go-internal/testscript/testscript.go.rej
make[1]: Leaving directory 
'/tmp/autopkgtest-lxc.k67h7x0n/downtmp/autopkgtest_tmp'

make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1
make: *** [debian/rules:4: build] Error 2
autopkgtest [06:12:32]: test dh-golang-autopkgtest



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: golang-github-rogpeppe-go-internal
Source-Version: 1.8.0-4
Done: Anthony Fok 

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

Debian distribution maintenance software
pp.
Anthony Fok  (supplier of updated 
golang-github-rogpeppe-go-internal package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 16 Dec 2021 21:31:18 -0700
Source: golang-github-rogpeppe-go-internal
Architecture: source
Version: 1.8.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Anthony Fok 
Closes: 1001734
Changes:
 golang-github-rogpeppe-go-internal (1.8.0-4) unstable; urgency=medium
 .
   * Unapply 0001-Allow-TestSimple-cover-to-PASS.patch after tests.
 It turns out that changes to files under _build/src, such as
 _build/src/github.com/rogpeppe/go-internal/testscript/testscript.go
 do end up in the final .deb binary package, causing autopkgtest to fail
 with "Reversed (or previously applied) patch detected!" error.
 Thanks to Paul Gevers for reporting the autopkgtest regression!
 (Closes: #1001734)
Checksums-Sha1:
 54cb6ef1daf94db768d4ac4fdf36a59c4243ed39 2513 
golang-github-rogpeppe-go-internal_1.8.0-4.dsc
 95d4259200885b6e4a09a14a18613af26cbae00e 4272 
golang-github-rogpeppe-go-internal_1.8.0-4.debian.tar.xz
 63affbeeea54fe2e3450244c230f4a8b97dc8156 6908 
golang-github-rogpeppe-go-internal_1.8.0-4_amd64.buildinfo
Checksums-Sha256:
 

Processed: bug 1001824 is forwarded to https://trac.ietf.org/trac/xml2rfc/ticket/696

[Debian Bug Tracking System]

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

> forwarded 1001824 https://trac.ietf.org/trac/xml2rfc/ticket/696
Bug #1001824 [xml2rfc] xml2rfc: Incompatible with current weaseyprint
Set Bug forwarded-to-address to 'https://trac.ietf.org/trac/xml2rfc/ticket/696'.
> thanks
Stopping processing here.

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

Bug#1001734: marked as pending in golang-github-rogpeppe-go-internal

[Anthony Fok]

Control: tag -1 pending

Hello,

Bug #1001734 in golang-github-rogpeppe-go-internal 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/go-team/packages/golang-github-rogpeppe-go-internal/-/commit/15dc05314ba7b57ce78c9686e71b9090c651ab74


Unapply 0001-Allow-TestSimple-cover-to-PASS.patch after tests

It turns out that changes to files under _build/src, such as
_build/src/github.com/rogpeppe/go-internal/testscript/testscript.go
do end up in the final .deb binary package, causing autopkgtest to fail
with "Reversed (or previously applied) patch detected!" error.

Thanks: Paul Gevers for reporting the autopkgtest regression!
Closes: #1001734


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001734

Processed: Bug#1001734 marked as pending in golang-github-rogpeppe-go-internal

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1001734 [src:golang-github-rogpeppe-go-internal] 
golang-github-rogpeppe-go-internal: autopkgtest regression: Reversed (or 
previously applied) patch detected!
Added tag(s) pending.

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

Bug#1001824: xml2rfc: Incompatible with current weaseyprint

[Scott Kitterman]

Package: xml2rfc
Version: 3.12.0-1
Severity: serious
Tags: ftbfs upstream patch
Justification: fails to build from source

Note: Using ftbfs because that's the closest thing we have to an
autopkgtest failure.

The new version of weasyprint no longer uses the same PDF generation
libraries and as a result, xml2rfc's detection mechanism for if it is
capable of making a PDF is not working (see attached patch).

Once the detection mechanism is patched, PDF generation works fine,
which leads me to believe the test failure is bogus:

==
FAIL: test_text_content (__main__.PdfWriterTests)
--
Traceback (most recent call last):
  File "/home/xml2rfc-3.12.0/test.py", line 510, in test_text_content
self.assertIn(t, text)
AssertionError: 'RFC' not found in 'l- WN –&,ÛžÆ TNDQ&·sX l-%Zñ¢<³ WN P½RÔ n®>Ø 
%˜oh l† .µ ¬( .µ=N'

--

If things were really that garbled, I don't see how it could make a PDF.

Reported upstream:

https://trac.ietf.org/trac/xml2rfc/ticket/696

In the interim, I think it might make sense to apply the attached patch
and get rid of the failing test.  If we go down this path, then this
will also need fixing (get rid of HAVE_CAIRO and HAVE_PANGO):

xml2rfc-3.12.0/test.py", line 513, in test_included_fonts
if xml2rfc.HAVE_WEASYPRINT and xml2rfc.HAVE_PYCAIRO and xml2rfc.HAVE_CAIRO 
and xml2rfc.HAVE_PANGO:

Scott K
diff -ruN a/xml2rfc/__init__.py b/xml2rfc/__init__.py
--- a/xml2rfc/__init__.py   2021-12-16 10:31:27.857538775 -0500
+++ b/xml2rfc/__init__.py   2021-12-16 22:56:51.310061387 -0500
@@ -40,21 +40,6 @@
 except (ImportError, OSError):
 cairo = False
 HAVE_PYCAIRO = False
-try:
-from weasyprint.text import cairo
-HAVE_CAIRO = True
-CAIRO_VERSION = cairo.cairo_version()
-except (ImportError, OSError):
-HAVE_CAIRO = False
-CAIRO_VERSION = None
-try:
-from weasyprint.text import pango
-HAVE_PANGO = True
-PANGO_VERSION = pango.pango_version
-except (ImportError, OSError, AttributeError):
-HAVE_PANGO = False
-PANGO_VERSION = None
-
 
 def get_versions():
 import sys
diff -ruN a/xml2rfc/run.py b/xml2rfc/run.py
--- a/xml2rfc/run.py2021-12-16 10:31:27.861538832 -0500
+++ b/xml2rfc/run.py2021-12-16 23:00:12.948957766 -0500
@@ -35,10 +35,6 @@
 missing += "\nCould not import weasyprint"
 if not xml2rfc.HAVE_PYCAIRO:
 missing += "\nCould not import pycairo"
-if not xml2rfc.HAVE_CAIRO:
-missing += "\nCould not find the cairo lib"
-if not xml2rfc.HAVE_PANGO:
-missing += "\nCould not find the pango lib"
 return missing
 
 
@@ -212,7 +208,7 @@
help='outputs formatted HTML to file')
 formatgroup.add_argument('--nroff', action='store_true',
help='outputs formatted nroff to file (only v2 
input)')
-if xml2rfc.HAVE_CAIRO and xml2rfc.HAVE_PANGO:
+if xml2rfc.HAVE_PYCAIRO and xml2rfc.HAVE_WEASYPRINT:
 formatgroup.add_argument('--pdf', action='store_true',
help='outputs formatted PDF to file')
 else:

Bug#1001722: marked as done (python3.10: autopkgtest needs update for new version of setuptools: deprecation warning on stderr)

[Debian Bug Tracking System]

Your message dated Fri, 17 Dec 2021 03:48:42 +
with message-id 
and subject line Bug#1001722: fixed in python3.10 3.10.1-2
has caused the Debian Bug report #1001722,
regarding python3.10: autopkgtest needs update for new version of setuptools: 
deprecation warning on stderr
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.)


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

Source: python3.10
Version: 3.10.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, setupto...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:setuptools

Dear maintainer(s),

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


   passfail
setuptools from testing59.4.0-1
python3.10 from testing3.10.1-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. The test fails 
because there is a deprecation warning on stderr and the allow-stderr 
restriction is not set on the autopkgtest.


Currently this regression is blocking the migration of setuptools to 
testing [1]. Of course, setuptools shouldn't just break your autopkgtest 
(or even worse, your package), but it seems to me that the change in 
setuptools was intended and your package needs to update to the new 
situation.


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=setuptools

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python3.10/17559467/log.gz

testFibPy
running install
/usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build 
and pip and other standards-based tools.

  warnings.warn(
/usr/lib/python3/dist-packages/setuptools/command/easy_install.py:158: 
EasyInstallDeprecationWarning: easy_install command is deprecated. Use 
build and pip and other standards-based tools.

  warnings.warn(
running bdist_egg
running egg_info
creating fibpy.egg-info
writing fibpy.egg-info/PKG-INFO
writing dependency_links to fibpy.egg-info/dependency_links.txt
writing top-level names to fibpy.egg-info/top_level.txt
writing manifest file 'fibpy.egg-info/SOURCES.txt'
reading manifest file 'fibpy.egg-info/SOURCES.txt'
writing manifest file 'fibpy.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build
creating build/lib
copying fibpy.py -> build/lib
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/egg
copying build/lib/fibpy.py -> build/bdist.linux-x86_64/egg
byte-compiling build/bdist.linux-x86_64/egg/fibpy.py to 
fibpy.cpython-310.pyc

creating build/bdist.linux-x86_64/egg/EGG-INFO
copying fibpy.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying fibpy.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying fibpy.egg-info/dependency_links.txt -> 
build/bdist.linux-x86_64/egg/EGG-INFO
copying fibpy.egg-info/top_level.txt -> 
build/bdist.linux-x86_64/egg/EGG-INFO

copying fibpy.egg-info/zip-safe -> build/bdist.linux-x86_64/egg/EGG-INFO
creating dist
creating 'dist/fibpy-42.0.0-py3.10.egg' and adding 
'build/bdist.linux-x86_64/egg' to it

removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing fibpy-42.0.0-py3.10.egg
Copying fibpy-42.0.0-py3.10.egg to /usr/lib/python3.10/dist-packages
Adding fibpy 42.0.0 to easy-install.pth file



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python3.10
Source-Version: 3.10.1-2
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3.10 package)

(This message was generated 

Bug#1001823: Ardentryst near-unplayable after Python3 port

[Jens Rottmann]

Package: ardentryst
Version: 1.71-8
Severity: grave
Tags: patch

After Ardentryst was ported to Python 3 it appearently hasn't been play-tested 
well, several common actions don't work or crash the game, making it 
near-unplayable.

Start a new game, playing as "Nyx". Enter the 1st level. Try to cast "Ice" by pressing 
[D], [S]. Game crashes, printing a backtrace. Ice is Nyx's starting spell, the tutorial even instructs the 
player to try it, so it's quite hard to get through the game without it. Especially as her higher level spell 
"Implosion" insta-crashes, too.

For 2 more bugs, see below. Patch follows:

--X8-X8
Python 3 port caused several severe bugs.

* Customizing action keys via Control Options no longer works, changed
  keys aren't saved. Also a deprecation warning is printed. (controls.py)
* Playing as Nyx and casting Ice ([D][S]) or Implosion ([D][W]) instantly
  crashes the game with an exception. (magic.py)
* Playing as Pyralis and using Spin-slash ([C][S]) hangs gameplay, you have
  to abort the current level to be able to move again. (play_level.py)

Signed-off-by: Jens Rottmann

--- ardentryst/controls.py
+++ py2-3fixes/controls.py
@@ -35,7 +35,7 @@
 class SET2:
 def __init__(self, keycodes, x, y, set):
 self.set = set
-self.keys = [Key(keycodes[c], x + ((8-c)%3) * 32, y + (c/3)*30, "B-" + 
str(((11-c)/3)*3 - (11-c)%3), set) for c in range(9)]
+self.keys = [Key(keycodes[c], x + ((8-c)%3) * 32, y + (c//3)*30, "B-" 
+ str(((11-c)//3)*3 - (11-c)%3), set) for c in range(9)]

 class Key:
 def __init__(self, keycode, x, y, binding, set):
--- ardentryst/magic.py
+++ py2-3fixes/magic.py
@@ -236,7 +236,7 @@
 def s_init(self):
 global DATA
 self.affected = []
-self.cant = self.caster.mp < 4
+self.cant = self.caster.mp[0] < 4
 def s_blit(self, surf, ALT_X, ALT_Y):
 global DATA
 if not self.affected:
@@ -441,7 +441,7 @@
 def s_init(self):
 global DATA
 self.affected = []
-self.cant = self.caster.mp < 15
+self.cant = self.caster.mp[0] < 15
 def s_blit(self, surf, ALT_X, ALT_Y):
 global DATA
 pic = DATA.mag_images["bubble.png"][0]
@@ -472,7 +472,7 @@
 if self.caster.mp[0] >= 15:
 self.affected.append(monster)

-self.affected.sort(lambda x, y: cmp(y.maxhp, x.maxhp))
+self.affected.sort(key=lambda x: -x.maxhp)

 if len(self.affected):
 self.affected = self.affected[:1]
--- ardentryst/play_level.py
+++ py2-3fixes/play_level.py
@@ -4727,7 +4727,7 @@
 self.mycombotime -= 1
 if self.chainmove[1] and self.chainmove[1] > 0:
 self.chainmove[1] -= 1
-if self.chainmove[1] and self.chainmove[1] == 0:
+if self.chainmove[1] == 0:
 cm = self.chainmove[:]
 self.chainmove = [None, None]
 getattr(self, cm[0])()
--

Bug#1001822: sway FTBFS with libwlroots-dev 0.14.1

[Adrian Bunk]

Source: sway
Version: 1.5.1-2
Severity: serious
Tags: ftbfs
Control: close -1 1.6.1-1

https://buildd.debian.org/status/logs.php?pkg=sway=1.5.1-2%2Bb1

...
Dependency wlroots found: NO found 0.14.1 but need: '<0.13.0' ; matched: 
'>=0.12.0'
Run-time dependency wlroots found: NO 

../meson.build:75:1: ERROR: Invalid version of dependency, need 'wlroots' 
['<0.13.0'] found '0.14.1'.
...


This is already fixed in the version in experimental.

Processed: sway FTBFS with libwlroots-dev 0.14.1

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.6.1-1
Bug #1001822 [src:sway] sway FTBFS with libwlroots-dev 0.14.1
Marked as fixed in versions sway/1.6.1-1.
Bug #1001822 [src:sway] sway FTBFS with libwlroots-dev 0.14.1
Marked Bug as done

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

Bug#1001821: phoc FTBFS with libwlroots-dev 0.14.1

[Adrian Bunk]

Source: phoc
Version: 0.9.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=phoc=0.9.0-1%2Bb1

...
FAILED: src/libphoc.a.p/desktop.c.o 
cc -Isrc/libphoc.a.p -Isrc -I../src -Iprotocols -I/usr/include/libdrm 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gnome-desktop-3.0 
-I/usr/include/libxml2 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu 
-I/usr/include/gsettings-desktop-schemas 
-I/<>/obj-x86_64-linux-gnu -fdiagnostics-color=always 
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -DWLR_USE_UNSTABLE 
-Wcast-align -Wdate-time -Werror=format-security -Werror=format=2 
-Wendif-labels -Werror=incompatible-pointer-types -Werror=missing-declarations 
-Werror=overflow -Werror=return-type -Werror=shift-count-overflow 
-Werror=shift-overflow=2 -Werror=implicit-fallthrough=3 -Wformat-nonliteral 
-Wformat-security -Winit-self -Wmaybe-uninitialized 
-Wmissing-field-initializers -Wmissing-include-dirs -Wmissing-noreturn 
-Wnested-externs -Wno-missing-field-initializers -Wno-sign-compare 
-Wno-strict-aliasing -Wno-unused-parameter -Wold-style-definition 
-Wpointer-arith -Wredundant-decls -Wshadow -Wstrict-prototypes -Wtype-limits 
-Wundef -Wunused-function -Wswitch-default -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ 
src/libphoc.a.p/desktop.c.o -MF src/libphoc.a.p/desktop.c.o.d -o 
src/libphoc.a.p/desktop.c.o -c ../src/desktop.c
../src/desktop.c:16:10: fatal error: wlr/types/wlr_gtk_primary_selection.h: No 
such file or directory
   16 | #include 
  |  ^~~
compilation terminated.

Processed: severity of 984058 is serious

[Debian Bug Tracking System]

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

> # ftbfs is a serious bug
> severity 984058 serious
Bug #984058 [src:igraph] igraph: ftbfs with GCC-11
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1001729: marked as done (apache-log4j2: CVE-2021-45046: Incomplete fix for CVE-2021-44228 in certain non-default configurations)

[Debian Bug Tracking System]

Your message dated Thu, 16 Dec 2021 22:32:07 +
with message-id 
and subject line Bug#1001729: fixed in apache-log4j2 2.16.0-1~deb11u1
has caused the Debian Bug report #1001729,
regarding apache-log4j2: CVE-2021-45046: Incomplete fix for CVE-2021-44228 in 
certain non-default configurations
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.)


-- 
1001729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apache-log4j2
Version: 2.15.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://issues.apache.org/jira/browse/LOG4J2-3221
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2.15.0-1~deb11u1
Control: found -1 2.15.0-1~deb10u1

Hi,

The following vulnerability was published for apache-log4j2. Strictly
speaking it's less severe as CVE-2021-44228 as it is an incomplete fix
for the former CVE in certain non-default configurations.

CVE-2021-45046[0]:
| It was found that the fix to address CVE-2021-44228 in Apache Log4j
| 2.15.0 was incomplete in certain non-default configurations. This
| could allows attackers with control over Thread Context Map (MDC)
| input data when the logging configuration uses a non-default Pattern
| Layout with either a Context Lookup (for example, $${ctx:loginId}) or
| a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious
| input data using a JNDI Lookup pattern resulting in a denial of
| service (DOS) attack. Log4j 2.15.0 restricts JNDI LDAP lookups to
| localhost by default. Note that previous mitigations involving
| configuration such as to set the system property
| `log4j2.noFormatMsgLookup` to `true` do NOT mitigate this specific
| vulnerability. Log4j 2.16.0 fixes this issue by removing support for
| message lookup patterns and disabling JNDI functionality by default.
| This issue can be mitigated in prior releases (2.16.0) by removing
| the JndiLookup class from the classpath (example: zip -q -d
| log4j-core-*.jar
| org/apache/logging/log4j/core/lookup/JndiLookup.class).


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-45046
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046
[1] https://issues.apache.org/jira/browse/LOG4J2-3221
[2] https://logging.apache.org/log4j/2.x/security.html#CVE-2021-45046
[3] https://www.openwall.com/lists/oss-security/2021/12/14/4

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: apache-log4j2
Source-Version: 2.16.0-1~deb11u1
Done: Markus Koschany 

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated apache-log4j2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Dec 2021 00:48:17 +0100
Source: apache-log4j2
Architecture: source
Version: 2.16.0-1~deb11u1
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Closes: 1001729
Changes:
 apache-log4j2 (2.16.0-1~deb11u1) bullseye-security; urgency=high
 .
   * Team upload.
   * Backport version 2.16.0 to Bullseye and fix CVE-2021-45046.
 (Closes: #1001729)
Checksums-Sha1:
 26cba39fd38c8586a43d22d10370f45868f8c4d2 3051 
apache-log4j2_2.16.0-1~deb11u1.dsc
 29ed458aa60e1821908564fd66438c6e9206e282 1285464 
apache-log4j2_2.16.0.orig.tar.xz
 6559785b1402c6431a1d236a1edb4d03ea141c55 7472 
apache-log4j2_2.16.0-1~deb11u1.debian.tar.xz
 f609cb71c1417eaa8f3c1fc86ac82c63c9d3d511 9100 
apache-log4j2_2.16.0-1~deb11u1_source.buildinfo
Checksums-Sha256:
 70b8dbfb9721dd2fb212f1dd080e331152e5154c6b6a78451504fe42d1935be3 3051 
apache-log4j2_2.16.0-1~deb11u1.dsc
 d36a7556e7027819aaceef02838dcfaa3dd368f74f92b9585b2b6a442eb2194f 1285464 
apache-log4j2_2.16.0.orig.tar.xz
 

Processed: tagging 998904, reassign 1001801 to src:dogtag-pki, reassign 1001779 to wnpp ..., tagging 1001773

[Debian Bug Tracking System]

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

> tags 998904 + experimental
Bug #998904 {Done: Paul Gevers } [src:python-django] 
src:python-django: fails to migrate to testing for too long: autopkgtest 
regressions and unresolved RC bugs
Added tag(s) experimental.
> reassign 1001801 src:dogtag-pki 11.0.0-1
Bug #1001801 [src:dogtag-pk] dogtag-pki: hits autopkgtest timeout on powerful 
workers
Warning: Unknown package 'src:dogtag-pk'
Bug reassigned from package 'src:dogtag-pk' to 'src:dogtag-pki'.
No longer marked as found in versions dogtag-pk/11.0.0-1.
Ignoring request to alter fixed versions of bug #1001801 to the same values 
previously set
Bug #1001801 [src:dogtag-pki] dogtag-pki: hits autopkgtest timeout on powerful 
workers
Marked as found in versions dogtag-pki/11.0.0-1.
> reassign 1001779 wnpp
Bug #1001779 [hurl] Package: hurl / Add new hurl package (https://hurl.dev) to 
official Debian repository / https://bugs.debian.org/wnpp
Warning: Unknown package 'hurl'
Bug reassigned from package 'hurl' to 'wnpp'.
Ignoring request to alter found versions of bug #1001779 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1001779 to the same values 
previously set
> retitle 1001779 RFP: hurl
Bug #1001779 [wnpp] Package: hurl / Add new hurl package (https://hurl.dev) to 
official Debian repository / https://bugs.debian.org/wnpp
Changed Bug title to 'RFP: hurl' from 'Package: hurl / Add new hurl package 
(https://hurl.dev) to official Debian repository / 
https://bugs.debian.org/wnpp'.
> tags 1001773 + sid bookworm
Bug #1001773 [src:dcontainers] dcontainers: FTBFS on s390x in sid
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#999216: marked as done (lpr: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Thu, 16 Dec 2021 19:48:43 +
with message-id 
and subject line Bug#999216: fixed in lpr 1:2008.05.17.3+nmu1
has caused the Debian Bug report #999216,
regarding lpr: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lpr
Version: 1:2008.05.17.3
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: lpr
Source-Version: 1:2008.05.17.3+nmu1
Done: Damyan Ivanov 

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated lpr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 16 Dec 2021 08:35:18 +
Source: lpr
Architecture: source
Version: 1:2008.05.17.3+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Adam Majer 
Changed-By: Damyan Ivanov 
Closes: 999216
Changes:
 lpr (1:2008.05.17.3+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * add build-arch and build-indep targets to debian/rules
 (Closes: #999216)
Checksums-Sha1: 
 a91ce6fca631f1c99db14431c069a4100c949b52 1526 lpr_2008.05.17.3+nmu1.dsc
 f7adc9fc371bb29165ee091b32405829bcc02067 107701 lpr_2008.05.17.3+nmu1.tar.gz
Checksums-Sha256: 
 fec3ec8af527ab8ef7db7dd42543ae54b2961d33b6b06a3898cfb53a56cd9936 1526 
lpr_2008.05.17.3+nmu1.dsc
 8b442ef2362911ba2ec2bc4e4f0cc1ea34f5886662fb7009757f244e275b563e 107701 
lpr_2008.05.17.3+nmu1.tar.gz
Files: 
 92e2133f048e1a4e093a8dadcb4984f2 1526 net optional lpr_2008.05.17.3+nmu1.dsc
 02559d7ae1772a0e56d716ec17690ab7 107701 net optional 
lpr_2008.05.17.3+nmu1.tar.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAmG6+wEACgkQ276dTZnS
oAR9hw//fb71S4kfFk+UyFj22ODOiG2E7Hu3Cf6ejfis4C+F7CaMxmIPvG0kaL+/
5gp3e/2DU9umv2JShu7QYSQORUWf6KmE6a0fq3dxgnJNNfRlKQUFM54xSJEFnOfr
KLe8gjFG5WmEanbp0msjWV2U2Dcl88kJE8zbHXkTD4rU2qUNF4InaCjI0Zm8vXLL
1XR5d9smORqfio+AohT5HJ8hWkJImAKoJCXnmB6dAwkT7VqQ/djEbB26k51JOHU0
ErS4yjC0MI5hh4hvG2xhpLhTL31Asm7e6cwdqPGFd/23m2L/tk2sRV5QHvqjKMJs
EE/iyUFUk1/LINFeRgW+pKzoCodJHz+knnWS7wqrjwp/yZUytdHHzleyCzvwAty9
XQ7AqXOYuT6FL3S/gWYvRZjAW1kuqPXRywlxtx6FjsT06or3Qi+jvYFaVdERSVUa
vOeKM/YX5s+BAkxfRMuuHuk/bQgwH3QpPDS/njehTXbKWME1i4nfmtuR/ykpTDAP
BI18LDDRYN6GuY01/xWRV+KTycNn6A9246Z+OtTfycw9dHmaXD1VX8JP5vBUoPAK
y2xolL6byLWQ9oduChfHrkXW0Hp+fprElTovlMLeMmv92jixbyXWZ0nhZW+nkS1k
Yk3Qt+1c8BNGtmopnfDv3cH1l87iOW5er5C7uiHjE+oRg148hik=
=ktKh
-END PGP SIGNATURE End Message ---

Bug#999021: marked as done (libexpect-perl: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Thu, 16 Dec 2021 19:48:39 +
with message-id 
and subject line Bug#999021: fixed in libexpect-perl 1.21-1.2
has caused the Debian Bug report #999021,
regarding libexpect-perl: missing required debian/rules targets build-arch 
and/or build-indep
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.)


-- 
999021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libexpect-perl
Version: 1.21-1.1
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: libexpect-perl
Source-Version: 1.21-1.2
Done: Damyan Ivanov 

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated libexpect-perl 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: Wed, 15 Dec 2021 19:58:42 +
Source: libexpect-perl
Architecture: source
Version: 1.21-1.2
Distribution: unstable
Urgency: medium
Maintainer: Jörgen Hägg 
Changed-By: Damyan Ivanov 
Closes: 999021
Changes:
 libexpect-perl (1.21-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Provide 'build-arch' and 'build-indep' targets in debian/rules
 Closes: #999021
Checksums-Sha1: 
 6f2f2d5524942d4e4c9ad66337966bc9bcacd165 1683 libexpect-perl_1.21-1.2.dsc
 470d03c8b600c5d68b3ea23497af1b9a4b79cc57 5228 libexpect-perl_1.21-1.2.diff.gz
Checksums-Sha256: 
 73846dedba3519282da5576c72586254879a815238d8a4307dc28a4f64095591 1683 
libexpect-perl_1.21-1.2.dsc
 f5bb242b3e4fef81d4ccc8bb014eafb5051765d51807ebf42ea7ce368772 5228 
libexpect-perl_1.21-1.2.diff.gz
Files: 
 293be6bbe69f5378a5a81d42a6bca5d8 1683 perl optional libexpect-perl_1.21-1.2.dsc
 0c9b1ee1b46c38dbb43bdb21cb0bce76 5228 perl optional 
libexpect-perl_1.21-1.2.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAmG6ST8ACgkQ276dTZnS
oATsWQ//Y1S9BN/hUcpkrEzRsNl6AAOYploWwbVguUszfx7nU87wF1adaDZI5AAM
xQkAMrrsi4MDNnBaHIIgO1jNrJW9swQ5URninpU1BYzrR+f7h8aPiKRvcvMzVGRL
iO4GWABpvyne0a2ZOoaDPxg4YTVGjHWoKgh0+nOhGJW7XTiUAtm2Xd+suP4cXZEX
bBkwFngZfkLfhUmGnGW2sbdlZIGjm4HrQ00Y7HVtvFWQZm2VBNAFir1CUgWJ4fhU
vLrNzM7lKcOQoRX2Vj5ljP+cjoqVwEDd4/iE4qUP+BrLrwO0CoEepfgfSKBZwgTg
cQkq/RXuNEUxfzaSIb0whyLdboquQz2nWjli9PWGUWSoeN/kEigE1Cm4iaKW69qQ
ogV7yFtsJDSz9q9uIuKLgZugpGB857vJyI7aaPeHigIrRwHN70qDf9bZeVsfUyuU
99CydXO6CsUGpju6CIU8plgBZxVlGh0GWu/lBNy0/67WryraivJmW7cVWGeRUTtM
DxlZ5eJuZ4kYZDUCd7A74MRx1zRO0dHeRoNPaFd7bDomT8xBXUbZCNej/Bu21WQO
fdhbOIOGLZzQhNR+0AAETNR/QXyXp0i2/8RKW7hSS+QdbWHgglfMItf1FchHf7Uu
PacPawsLTfzBwOLkjQVyReR1jcZaIhLUzBtl/0BnnnirkwGvYB8=
=Ufqs
-END PGP SIGNATURE End Message ---

Bug#999216: lpr: diff for NMU version 1:2008.05.17.3+nmu1

[Damyan Ivanov]

-=| Adam Majer, 16.12.2021 18:16:23 +0100 |=-
> On 12/16/21 9:37 AM, Damyan Ivanov wrote:
> > Dear maintainer,
> > 
> > I've prepared an NMU for lpr (versioned as 1:2008.05.17.3+nmu1) and
> > uploaded it to DELAYED/7. Please feel free to tell me if I
> > should delay it longer.
> > 
> > Regards.
> > 
> 
> Thank you! The upload is appreciated.

Great! Upload re-scheduled to DELAYED/0 and should enter the archive 
within a day.

-- dam

Bug#1001811: postgresql-mysql-fdw: autopkgtest regression on armhf and i386: failed to look up symbol "evalexpr_19_0"

[Paul Gevers]

Source: postgresql-mysql-fdw
Version: 2.7.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 postgresql-mysql-fdw the autopkgtest of 
postgresql-mysql-fdw fails in testing when that autopkgtest is run with 
the binary packages of postgresql-mysql-fdw from unstable. It passes 
when run with only packages from testing. In tabular form:


   passfail
postgresql-mysql-fdw   from testing2.7.0-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=postgresql-mysql-fdw

https://ci.debian.net/data/autopkgtest/testing/i386/p/postgresql-mysql-fdw/17609222/log.gz

== creating the MySQL test database
--
CREATE DATABASE mysql_fdw_regress
--

--
CREATE DATABASE mysql_fdw_regress1
--

--
CREATE USER 'edb'@'localhost' IDENTIFIED BY 'edb'
--

--
GRANT ALL PRIVILEGES ON mysql_fdw_regress.* TO 'edb'@'localhost'
--

--
GRANT ALL PRIVILEGES ON mysql_fdw_regress1.* TO 'edb'@'localhost'
--

### PostgreSQL 14 installcheck ###
Creating new PostgreSQL cluster 14/regress ...
/usr/lib/postgresql/14/lib/pgxs/src/makefiles/../../src/test/regress/pg_regress 
--inputdir=./ --bindir='/usr/lib/postgresql/14/bin' 
--dbname=contrib_regression server_options connection_validation dml 
select pushdown join_pushdown aggregate_pushdown

(using postmaster on localhost, port 5433)
== dropping database "contrib_regression" ==
NOTICE:  database "contrib_regression" does not exist, skipping
DROP DATABASE
== creating database "contrib_regression" ==
CREATE DATABASE
ALTER DATABASE
== running regression test queries==
test server_options   ... ok  107 ms
test connection_validation... ok   70 ms
test dml  ... ok  132 ms
test select   ... ok  555 ms
test pushdown ... ok  123 ms
test join_pushdown... ok 1620 ms
test aggregate_pushdown   ... FAILED 2824 ms

==
 1 of 7 tests failed. ==

The differences that caused some tests to fail can be viewed in the
file 
"/tmp/autopkgtest-lxc.r_7rxru0/downtmp/build.z8H/src/regression.diffs". 
 A copy of the test summary that you see
above is saved in the file 
"/tmp/autopkgtest-lxc.r_7rxru0/downtmp/build.z8H/src/regression.out".


make: *** [/usr/lib/postgresql/14/lib/pgxs/src/makefiles/pgxs.mk:433: 
installcheck] Error 1
*** /tmp/pg_virtualenv.joAylJ/log/postgresql-14-regress.log (last 100 
lines) ***
2021-12-16 10:13:48.401 UTC [4153] LOG:  starting PostgreSQL 14.1 
(Debian 14.1-1) on i686-pc-linux-gnu, compiled by gcc (Debian 11.2.0-10) 
11.2.0, 32-bit
2021-12-16 10:13:48.402 UTC [4153] LOG:  listening on IPv6 address 
"::1", port 5433
2021-12-16 10:13:48.402 UTC [4153] LOG:  listening on IPv4 address 
"127.0.0.1", port 5433
2021-12-16 10:13:48.402 UTC [4153] LOG:  listening on Unix socket 
"/var/run/postgresql/.s.PGSQL.5433"
2021-12-16 10:13:48.403 UTC [4154] LOG:  database system was shut down 
at 2021-12-16 10:13:48 UTC
2021-12-16 10:13:48.407 UTC [4153] LOG:  database system is ready to 
accept connections
2021-12-16 10:13:50.785 UTC [4205] postgres@contrib_regression WARNING: 
 MySQL secure authentication is off
2021-12-16 10:13:50.791 UTC [4205] postgres@contrib_regression ERROR: 
"fetch_size" requires an integer value between 1 to 4294967295
2021-12-16 10:13:50.791 UTC [4205] postgres@contrib_regression 
STATEMENT:  ALTER FOREIGN TABLE table3 OPTIONS ( SET fetch_size 
'-6');
2021-12-16 10:13:50.792 UTC [4205] postgres@contrib_regression ERROR: 
"fetch_size" requires an integer value between 1 to 4294967295
2021-12-16 10:13:50.792 UTC [4205] postgres@contrib_regression 
STATEMENT:  ALTER FOREIGN TABLE table3 OPTIONS ( SET fetch_size 
'123abc');
2021-12-16 10:13:50.792 UTC [4205] postgres@contrib_regression ERROR: 
"fetch_size" requires an integer value between 1 to 4294967295
2021-12-16 10:13:50.792 UTC [4205] postgres@contrib_regression 
STATEMENT:  ALTER FOREIGN TABLE table3 OPTIONS ( SET fetch_size 
'9');
2021-12-16 10:13:50.794 UTC [4205] postgres@contrib_regression ERROR: 
reconnect requires a Boolean value
2021-12-16 10:13:50.794 UTC [4205] postgres@contrib_regression 
STATEMENT:  ALTER SERVER reconnect1 OPTIONS ( SET reconnect 'abc1' );
2021-12-16 

Processed: seems to break quite some packages: uncoordinated transition?

[Debian Bug Tracking System]

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

> retitle 1001591 drops attributes used by reverse dependencies
Bug #1001591 [python3-mistune] python3-mistune: latest upgrade breaks 
matrix-mirage package
Changed Bug title to 'drops attributes used by reverse dependencies' from 
'python3-mistune: latest upgrade breaks matrix-mirage package'.
> affects 1001591 matrix-mirage src:python-m2r src:python-schema-salad
Bug #1001591 [python3-mistune] drops attributes used by reverse dependencies
Added indication that 1001591 affects matrix-mirage, src:python-m2r, and 
src:python-schema-salad
> affects 1001591 src:nbconvert
Bug #1001591 [python3-mistune] drops attributes used by reverse dependencies
Added indication that 1001591 affects src:nbconvert
> block 1001283 by 1001591
Bug #1001283 [python3-nbconvert] python3-nbconvert: nbconvert Depends: 
python3-mistune (<< 2)
1001283 was not blocked by any bugs.
1001283 was not blocking any bugs.
Added blocking bug(s) of 1001283: 1001591
> thanks
Stopping processing here.

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

Processed: libsdl2/2.0.18 breaks osk-sdl autopkgtest: Testing osk toggle button and 'mouse' key input

[Debian Bug Tracking System]

Processing control commands:

> found -1 libsdl2/2.0.18-3
Bug #1001809 [src:osk-sdl, src:libsdl2] libsdl2/2.0.18 breaks osk-sdl 
autopkgtest: Testing osk toggle button and 'mouse' key input
The source libsdl2 and version 2.0.18-3 do not appear to match any binary 
packages
Marked as found in versions libsdl2/2.0.18-3.
> found -1 osk-sdl/0.66-2
Bug #1001809 [src:osk-sdl, src:libsdl2] libsdl2/2.0.18 breaks osk-sdl 
autopkgtest: Testing osk toggle button and 'mouse' key input
Marked as found in versions osk-sdl/0.66-2.

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

Bug#1001809: libsdl2/2.0.18 breaks osk-sdl autopkgtest: Testing osk toggle button and 'mouse' key input

[Simon McVittie]

Source: osk-sdl, libsdl2
Control: found -1 libsdl2/2.0.18-3
Control: found -1 osk-sdl/0.66-2
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks

The osk-sdl autopkgtest on ci.debian.net seems to show a regression when
run with libsdl2 (>= 2.0.18):

 passfail
libsdl2  from testing2.0.18-3
osk-sdl  from testingfrom testing
all others   from testingfrom testing

The test output is:

> ** Testing osk toggle button and 'mouse' key input
> ERROR: Unexpected result!
>   got:
>   expected:   qwerty

This could be either a regression in libsdl2, or a pre-existing bug
in osk-sdl. I don't use osk-sdl myself, so I don't really have a reference
for what it's doing here. When someone works out what is going on, this
bug should be reassigned to either libsdl2 or osk-sdl as appropriate.

(The previous stage of the autopkgtest, involving
test_keyscript_no_keyboard_phys, already failed but the failure was
ignored; I've reported that as a non-RC bug in the osk-sdl source package,
but it is not a regression.)

smcv

Bug#1001614: marked as done (odil: FTBFS on armhf: 91 - MoveSCU_Move (Failed))

[Debian Bug Tracking System]

Your message dated Thu, 16 Dec 2021 17:48:29 +
with message-id 
and subject line Bug#1001614: fixed in odil 0.12.1-3
has caused the Debian Bug report #1001614,
regarding odil: FTBFS on armhf:  91 - MoveSCU_Move (Failed)
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.)


-- 
1001614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: odil
Version: 0.12.1-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

| The following tests FAILED:
|91 - MoveSCU_Move (Failed)
| Errors while running CTest
| R1=$?
|
| ${PYTHON} -m unittest discover -s ${WORKSPACE}/tests/wrappers/
| 
E: 
Move Presentation Context but no Find (accepting for now)
| .E: Move Presentation Context but no Find (accepting for now)
| .E: Move Presentation Context but no Find (accepting for now)
| .E: Move Presentation Context but no Find (accepting for now)
| .E: Move Presentation Context but no Find (accepting for now)
| E: moveSCP: Sub-Association Request Failed: 0006:031a DUL network read timeout
| E: moveSCP: Sub-Association Release Failed: 0006:0106 ASC Caller passed in a 
NULL key
| E: Build killed with signal TERM after 300 minutes of inactivity

See
https://buildd.debian.org/status/fetch.php?pkg=odil=armhf=0.12.1-2%2Bb2=1639270465=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: odil
Source-Version: 0.12.1-3
Done: Julien Lamy 

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

Debian distribution maintenance software
pp.
Julien Lamy  (supplier of updated odil package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Dec 2021 11:54:07 +0100
Source: odil
Architecture: source
Version: 0.12.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Julien Lamy 
Closes: 1001614
Changes:
 odil (0.12.1-3) unstable; urgency=medium
 .
   * Remove network-related unit tests (Closes: #1001614)
Checksums-Sha1:
 2cb5f04f64a1eebe9adc02b71cc3b5c67513e9d3 2761 odil_0.12.1-3.dsc
 fbe935153daa4b320d4c923dd03088459484d593 18060 odil_0.12.1-3.debian.tar.xz
 a9948e81d429fe23a5f2b423cd654bbd46b33fc6 12419 odil_0.12.1-3_amd64.buildinfo
Checksums-Sha256:
 ab38dcf056cf7e66f6d44ee66780ac9df637a5109c75852614566792b308441f 2761 
odil_0.12.1-3.dsc
 cafca20772b13d4b4ceb8c0c10009262a0c28e4579f2c582882e0bd9aca89e96 18060 
odil_0.12.1-3.debian.tar.xz
 b55148073a291d8e1d4baa8f9b1fb8294baa3f665be4372dd17fe62f4cb43225 12419 
odil_0.12.1-3_amd64.buildinfo
Files:
 23bbc21425c393310906c0021327f73a 2761 science optional odil_0.12.1-3.dsc
 22e65ed7134cb7f9721eb29125330a64 18060 science optional 
odil_0.12.1-3.debian.tar.xz
 9f4776db9c9ed05831d2a05569760667 12419 science optional 
odil_0.12.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmG7eggSHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nxZwcQAJ6XnyDpfXyQTws9GNN8ek9InPWTlvyR
lU/WbNTKJTah3fhnmzBmQa60dhuYG2l0n244GW+BYIv2s9OUlIQK6eA4O6qMubTn
Etk+RGhO3ePM5zfVWDgfaLfL9T2oXWUXPdnWhEmorPASAPB+SJRb2h7USqEpcBfT
Jg7B0Q2z+cljY+gRQxOnkR20d0UCPLRSEDYaO6t2GUZFEgp5ooGslCjupbvUgxZx
MoiKZQb27hRWbHKsBexJbIQql81PjTgi2ZBITEWBlNCF81f00QLcR5LjzDWmjt0c
9v5oxspOacXxl/pzJlpty0dtGpkWJq4awT6ZTIXPuimqNpSTovvU+87rNiNSHQuC
aLyZIpKeWYoXAl1o+U7xQWS1zTb5RcPKTZr4itnbYYSS3pbJOuLlRspio9C59qYC
XNVY41iLNZpaBu2nc8z16sQpC1ptcY951rnr3bBWYVURdOP2wQcbSs9QanQUB8/W
7rFGFJ77cYf83Bdw+o4fZPnY3job6D/JlHJZuaYzCPYyZeLIOZN3z8LuRdWFMFb5
rz1HSfKW3hTntMce9N9mBVtVn3ucJ3jR2nZYyvcw/D8xUbjGjIpOovS6Xd7ncxzB
RBtBxsJj5bs4F3Z3z38GdI/OGxE2/DBWHMF7wg/cwg/Hzzywe556wiQgvTr0teaN
sZTwJFLfD6M1
=xNha
-END PGP SIGNATURE End Message ---

Bug#999216: lpr: diff for NMU version 1:2008.05.17.3+nmu1

[Adam Majer]

On 12/16/21 9:37 AM, Damyan Ivanov wrote:

Dear maintainer,

I've prepared an NMU for lpr (versioned as 1:2008.05.17.3+nmu1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.



Thank you! The upload is appreciated.

- Adam

Processed: [bts-link] source package src:python-transitions

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:python-transitions
> # 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 #1001479 (http://bugs.debian.org/1001479)
> # Bug title: python-transitions: (autopkgtest) needs update for python3.10: 
> There is no current event loop
> #  * https://github.com/pytransitions/transitions/issues/559
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1001479 + fixed-upstream
Bug #1001479 [src:python-transitions] python-transitions: (autopkgtest) needs 
update for python3.10: There is no current event loop
Added tag(s) fixed-upstream.
> usertags 1001479 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#1001799: marked as done (dh-python: python_version marker parsed incorrectly, adds a dependency that should be skipped)

[Debian Bug Tracking System]

Your message dated Thu, 16 Dec 2021 17:04:49 +
with message-id 
and subject line Bug#1001799: fixed in dh-python 5.20211216
has caused the Debian Bug report #1001799,
regarding dh-python: python_version marker parsed incorrectly, adds a 
dependency that should be skipped
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.)


-- 
1001799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-python
Version: 5.20211214
Severity: serious
Justification: causes FTBFS in reverse deps

Hi,

With the following in setup.py's install_requires:

"pathlib2;python_version<'3.0'",

dh-python does not skip the line, but tries to find the python3 module
providing path2lib, which of course does not exist, and thus fails the
build:

I: dh_python3 pydist:304: Cannot find package that provides pathlib2.
Please add package that provides it to Build-Depends or add "pathlib2
python3-pathlib2" line to debian/py3dist-overrides or add proper
dependency to Depends by hand and ignore this info.
Traceback (most recent call last):
  File "/usr/bin/dh_python3", line 280, in 
main()
  File "/usr/bin/dh_python3", line 201, in main
dependencies.parse(stats, options)
  File "/usr/share/dh-python/dhpython/depends.py", line 242, in parse
deps = parse_pydep(self.impl, fn, bdep=self.bdep,
**section_options)
  File "/usr/share/dh-python/dhpython/pydist.py", line 496, in
parse_pydep
for part in dependency.split(','))
AttributeError: 'NoneType' object has no attribute 'split'
make: *** [debian/rules:8: binary] Error 1

This does not happen on previous versions of dh-python, so I imagine it
could be a regression from:

https://salsa.debian.org/python-team/tools/dh-python/-/commit/832f01c9c7da22a1d00887d8ce0e6be9893bdf3e

Found while rebuilding:

https://salsa.debian.org/python-team/packages/microsoft-authentication-extensions-for-python/-/jobs/2284212

As far as I understand the usage of python_version in this format is
legitimate, and the change causes reverse deps to FTBFS, hence the
severity. Feel free to downgrade if that's not the case.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: dh-python
Source-Version: 5.20211216
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated dh-python package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Dec 2021 12:39:55 -0400
Source: dh-python
Architecture: source
Version: 5.20211216
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Stefano Rivera 
Closes: 1001799
Changes:
 dh-python (5.20211216) unstable; urgency=medium
 .
   * Use a consistent distribution name regexp to handle dashed names
 correctly, thanks Nicolas Dandrimont.
   * Un-constrain python_version constraints where the minimum version is < 3.
   * Ignore python_version constraints where the maximum version is < 3.
 (closes: 1001799)
Checksums-Sha1:
 e5bd1928986b4f83d9c844cca4ce02ca85417c6b 1515 dh-python_5.20211216.dsc
 ade62de6d64af05e13df32a63d0669a1dd4d795f 110344 dh-python_5.20211216.tar.xz
 2fd16133f0731e39223d31c83871154a4976b32d 6419 
dh-python_5.20211216_source.buildinfo
Checksums-Sha256:
 a0f295fc4de1cd4bda2785d30cafaea0c9fef53cc1fc887d301c5ea88bc393bf 1515 
dh-python_5.20211216.dsc
 733e9d60e208a0d5bde93bffcc2d36dc05465212f18eb1942640a0f80444db9e 110344 
dh-python_5.20211216.tar.xz
 540a75fd26fc822e9f5e38bc417dac10633e8f78071f9b0278e5bec1a9aeec04 6419 
dh-python_5.20211216_source.buildinfo
Files:
 ffe51f67d0df0c7ae964d9e20419fb8e 1515 python optional dh-python_5.20211216.dsc
 f6f5b4e5ccfd88f33a5396e20fae1816 110344 python optional 
dh-python_5.20211216.tar.xz
 0d460d0cf9ec53cdce845509ec42a990 6419 python optional 
dh-python_5.20211216_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1001237: marked as done (ptl: autopkgtest regression on armhf: Floating point exception)

[Debian Bug Tracking System]

Your message dated Thu, 16 Dec 2021 17:04:59 +
with message-id 
and subject line Bug#1001237: fixed in ptl 2.3.1-1
has caused the Debian Bug report #1001237,
regarding ptl: autopkgtest regression on armhf: Floating point exception
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.)


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

Source: ptl
Version: 2.3.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 ptl the autopkgtest of ptl fails in testing when 
that autopkgtest is run with the binary packages of ptl from unstable. 
It passes when run with only packages from testing. In tabular form:


   passfail
ptlfrom testing2.3.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Maybe the test 
gets a bit confused by the fact that this host has 160 cores?


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=ptl

https://ci.debian.net/data/autopkgtest/testing/armhf/p/ptl/17288801/log.gz

/usr/include/c++/11/bits/stl_algobase.h:527:5: note: parameter passing 
for argument of type ‘__gnu_cxx::__normal_iteratorstd::vector >’ changed in GCC 7.1

In file included from /usr/include/c++/11/bits/stl_algobase.h:67,
 from /usr/include/c++/11/algorithm:61,
 from /usr/include/PTL/Globals.hh:30,
 from /usr/include/PTL/Task.hh:33,
 from 
/tmp/autopkgtest-lxc.48w05yr2/downtmp/autopkgtest_tmp/common/utils.hh:25,
 from 
/tmp/autopkgtest-lxc.48w05yr2/downtmp/autopkgtest_tmp/basic/recursive_tasking.cc:26:
/usr/include/c++/11/bits/stl_iterator.h: In function ‘_Iterator 
std::__niter_base(__gnu_cxx::__normal_iterator<_Iterator, _Container>) 
[with _Iterator = const long long int*; _Container = std::vectorlong int>]’:
/usr/include/c++/11/bits/stl_iterator.h:1257:5: note: parameter passing 
for argument of type ‘__gnu_cxx::__normal_iteratorstd::vector >’ changed in GCC 7.1
 1257 | __niter_base(__gnu_cxx::__normal_iterator<_Iterator, 
_Container> __it)

  | ^~~~
[100%] Linking CXX executable recursive_tbb_tasking
[100%] Built target recursive_tbb_tasking


  ##
  !!! Backtrace is activated !!!
  ##

[ptl-minimal]> Number of threads: 160
[PTL::ThreadPool] Starting thread 1...
bash: line 1:  2328 Floating point 
exception/tmp/autopkgtest-lxc.48w05yr2/downtmp/build.SOP/src/debian/tests/examples 
2> >(tee -a /tmp/autopkgtest-lxc.48w05yr2/downtmp/examples-stderr >&2) > 
>(tee -a /tmp/autopkgtest-lxc.48w05yr2/downtmp/examples-stdout)

autopkgtest [16:13:41]: test examples



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ptl
Source-Version: 2.3.1-1
Done: Stephan Lachnit 

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

Debian distribution maintenance software
pp.
Stephan Lachnit  (supplier of updated ptl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Dec 2021 17:32:19 +0100
Source: ptl
Architecture: source
Version: 2.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Stephan Lachnit 
Closes: 1001237
Changes:
 ptl (2.3.1-1) unstable; urgency=medium
 .
   * New upstream version 2.3.1
   * fix autopkgtest failure on armhf (Closes: #1001237)
Checksums-Sha1:
 08fa49c208dffb0aed2b95a9bbe2620411ce7f9c 2026 ptl_2.3.1-1.dsc
 091f0a6cdbf7cf83173bd8c3f24d743c19463db2 302703 ptl_2.3.1.orig.tar.gz
 

Bug#1001237: ptl: autopkgtest regression on armhf: Floating point exception

[Stephan Lachnit]

Control: forwarded -1 https://github.com/jrmadsen/PTL/issues/25

Hi Lukas,

On Mon, 13 Dec 2021 15:39:18 +0100 =?utf-8?q?Lukas_M=C3=A4rdian?=
 wrote:
> I can observe the same issue with 2.3.0-1 on Ubuntu and filed an upstream bug
> at https://github.com/jrmadsen/PTL/issues/25
>
> The intmax_t division seems to be the root-cause here, replacing the division
> in the minimal.cc example with a constant is a (temporary) way to mitigate 
> this
> problem.

Thanks for looking into this! I didn't have the time to do it.

Since I saw you fixed this upstream and 2.3.1 was released after that,
I have uploaded the new version instead of adding the patch.

Thanks again,
Stephan

Processed: Re: ptl: autopkgtest regression on armhf: Floating point exception

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/jrmadsen/PTL/issues/25
Bug #1001237 [src:ptl] ptl: autopkgtest regression on armhf: Floating point 
exception
Set Bug forwarded-to-address to 'https://github.com/jrmadsen/PTL/issues/25'.

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

Bug#1001801: dogtag-pki: hits autopkgtest timeout on powerful workers

[Paul Gevers]

Source: dogtag-pk
Version: 11.0.0-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky timeout

Dear maintainer(s),

Your package has an autopkgtest, great. However, because of some failure
"caused" by another package, I looked into the history of your 
autopkgtest [1] and I noticed it fails regularly on amd64 and armhf 
because it hits the autopkgtest timeout after 2:47 hours.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

In this case I noticed that at least the failures on amd64 that I looked 
at all happened on ci-worker13, which is our 48 core, 256 GB machine, 
while the test on other amd64 workers passed (as far as I checked). 
Similar, our armhf worker is also powerful: 160 core, 255 GB. Is there 
anything in the test that you can think of that can't handle so much 
resources?


The last entry in one of the amd64 logs is this (maybe add at least a 
timeout on calls like that):

INFO: Creating /etc/pki/pki-tomcat/Catalina/localhost/kra.xml
INFO: Waiting for web application to start

If you need help to investigate this on the workers in question, don't 
hesitate to reach out.


Paul

[1] https://ci.debian.net/packages/d/dogtag-pki/


OpenPGP_signature
Description: OpenPGP digital signature

Processed: fixed 1000567 in 2.0.4-1

[Debian Bug Tracking System]

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

> fixed 1000567 2.0.4-1
Bug #1000567 {Done: Paul Gevers } [src:libtorrent-rasterbar] 
src:libtorrent-rasterbar: fails to migrate to testing for too long: unresolved 
RC bug and uploader built arch:all
Marked as fixed in versions libtorrent-rasterbar/2.0.4-1.
> thanks
Stopping processing here.

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

Bug#1001799: dh-python: python_version marker parsed incorrectly, adds a dependency that should be skipped

[stefanor]

Hi Luca (2021.12.16_13:15:58_+)

Agreed, this is a regression, thanks.

I meant to explicitly deal with <3, but forgot.

SR

> Package: dh-python
> Version: 5.20211214
> Severity: serious
> Justification: causes FTBFS in reverse deps
> 
> Hi,
> 
> With the following in setup.py's install_requires:
> 
> "pathlib2;python_version<'3.0'",
> 
> dh-python does not skip the line, but tries to find the python3 module
> providing path2lib, which of course does not exist, and thus fails the
> build:
> 
> I: dh_python3 pydist:304: Cannot find package that provides pathlib2.
> Please add package that provides it to Build-Depends or add "pathlib2
> python3-pathlib2" line to debian/py3dist-overrides or add proper
> dependency to Depends by hand and ignore this info.
> Traceback (most recent call last):
>   File "/usr/bin/dh_python3", line 280, in 
> main()
>   File "/usr/bin/dh_python3", line 201, in main
> dependencies.parse(stats, options)
>   File "/usr/share/dh-python/dhpython/depends.py", line 242, in parse
> deps = parse_pydep(self.impl, fn, bdep=self.bdep,
> **section_options)
>   File "/usr/share/dh-python/dhpython/pydist.py", line 496, in
> parse_pydep
> for part in dependency.split(','))
> AttributeError: 'NoneType' object has no attribute 'split'
> make: *** [debian/rules:8: binary] Error 1
> 
> This does not happen on previous versions of dh-python, so I imagine it
> could be a regression from:
> 
> https://salsa.debian.org/python-team/tools/dh-python/-/commit/832f01c9c7da22a1d00887d8ce0e6be9893bdf3e
> 
> Found while rebuilding:
> 
> https://salsa.debian.org/python-team/packages/microsoft-authentication-extensions-for-python/-/jobs/2284212
> 
> As far as I understand the usage of python_version in this format is
> legitimate, and the change causes reverse deps to FTBFS, hence the
> severity. Feel free to downgrade if that's not the case.
> 
> -- 
> Kind regards,
> Luca Boccassi



-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1001273: Bug#932989: gcc-avr: Package version severely outdated compared to main gcc-toolchain

[Hakan Ardo]

I believe your right, and I would support any such efforts. I've orphaned
these packages quite some time ago as I've not been able to find the time
to implement this myself though.

On Thu, Dec 16, 2021 at 2:03 PM Gregor Riepl  wrote:

>
> >> Switching back to use upstream source would be one option. But will
> >> that mean we'll have to dropp support for newer devices?
>
> > Unfortunately I don’t know too much about the development history of
> > this package @Debian and the related decisions. It would be helpful
> > though to have other developers and maintainers to have their say on
> > this to help find a common solution. At first one should find out if
> > support for newer devices would suffer from such an approach. I have
> > not come across that topic yet...
>
> To be honest, I don't think newer device support is a big issue any
> more. While Microchip is still releasing new AVR MCUs, they are usually
> not that different from existing devices. Even if Debian is lagging
> behind, I think developers targeting older devices will benefit greatly
> from an updated gcc. If they must, they can always rely on the binary
> releases provided by Microchip.
>
> It's also not that hard to feed in support for new devices:
> https://gcc.gnu.org/wiki/avr-gcc#Supporting_.22unsupported.22_Devices
>
> And last but not least, upstream has kept pace with new AVR devices, as
> can be seen in the gcc release notes:
>
> https://gcc.gnu.org/gcc-7/changes.html#avr
> https://gcc.gnu.org/gcc-8/changes.html#avr
> https://gcc.gnu.org/gcc-10/changes.html#avr
>
> I believe it's time to make the switch - same for binutils-avr and
> avr-libc.
>


-- 
Håkan Ardö

Bug#1001797: marked as done (python-duckpy: autopkgtest tests all supported python3 versions but doesn't ensure they are installed)

[Debian Bug Tracking System]

Your message dated Thu, 16 Dec 2021 13:49:27 +
with message-id 
and subject line Bug#1001797: fixed in python-duckpy 3.2.0-2
has caused the Debian Bug report #1001797,
regarding python-duckpy: autopkgtest tests all supported python3 versions but 
doesn't ensure they are installed
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.)


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

Source: python-duckpy
Version: 3.2.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of python-duckpy fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
python-duckpy  from testing3.2.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems the 
test tries to test for all supported Python3 versions, but fails to 
ensure all those versions are actually installed during the test. E.g. a 
test dependency on python3-all (or one of its siblings).


Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-duckpy/17574738/log.gz

Testing with python3.10 in 
/tmp/autopkgtest-lxc.hmzefuht/downtmp/autopkgtest_tmp:
/tmp/autopkgtest-lxc.hmzefuht/downtmp/build.d02/src/debian/tests/run-unit-test: 
line 19: python3.10: command not found

autopkgtest [06:11:09]: test run-unit-test



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-duckpy
Source-Version: 3.2.0-2
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-duckpy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Dec 2021 14:26:14 +0100
Source: python-duckpy
Architecture: source
Version: 3.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1001797
Changes:
 python-duckpy (3.2.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Standards-Version: 4.6.0 (routine-update)
   * Test-Depends: python3-all
 Closes: #1001797
Checksums-Sha1:
 3e4867f67963cde80a6467a6c48ea4e5c98fc654 2204 python-duckpy_3.2.0-2.dsc
 9a483e502616156caee6669c858c5f2639a906fa 3024 
python-duckpy_3.2.0-2.debian.tar.xz
 93d45c1f869e1e09933424f135e71d5413a2aadc 7461 
python-duckpy_3.2.0-2_amd64.buildinfo
Checksums-Sha256:
 e02d7f7ebf3cfd715e8c812fdeffe048de895494bce5786c027a0f324b7b83cd 2204 
python-duckpy_3.2.0-2.dsc
 55d497eaffab77946ad8c4845e3e5012db6e8a2949efe26cab876dfb9720bb0b 3024 
python-duckpy_3.2.0-2.debian.tar.xz
 ee236c3e2aaf1ec14340dbffc62a8176751f2546adaa6612732b5d5e6dd2a40c 7461 
python-duckpy_3.2.0-2_amd64.buildinfo
Files:
 e55f26f1ee7e4062275da628bf25e37e 2204 science optional 
python-duckpy_3.2.0-2.dsc
 61274b5f1255723525327a13fd857af5 3024 science optional 
python-duckpy_3.2.0-2.debian.tar.xz
 52a0d27aabd53451a13fdc99f2003435 7461 science optional 

Processed: fixed 997363 in 2.0.4-1

[Debian Bug Tracking System]

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

> fixed 997363 2.0.4-1
Bug #997363 {Done: Sergio Durigan Junior } 
[src:libtorrent-rasterbar] libtorrent-rasterbar: FTBFS: configure: error: *** A 
compiler with support for C++17 language features is required.
Marked as fixed in versions libtorrent-rasterbar/2.0.4-1.
> thanks
Stopping processing here.

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

Processed: fixed 992575 in 2.0.4-1

[Debian Bug Tracking System]

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

> fixed 992575 2.0.4-1
Bug #992575 [libtorrent-rasterbar10] libtorrent-rasterbar10: import fails on 
Raspberry Pi 3b
Bug #999422 [libtorrent-rasterbar10] Deluge fails with ModuleNotFoundError
There is no source info for the package 'libtorrent-rasterbar10' at version 
'2.0.4-1' with architecture ''
Unable to make a source version for version '2.0.4-1'
Marked as fixed in versions 2.0.4-1.
Marked as fixed in versions 2.0.4-1.
> thanks
Stopping processing here.

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

Bug#1001799: dh-python: python_version marker parsed incorrectly, adds a dependency that should be skipped

[Luca Boccassi]

Package: dh-python
Version: 5.20211214
Severity: serious
Justification: causes FTBFS in reverse deps

Hi,

With the following in setup.py's install_requires:

"pathlib2;python_version<'3.0'",

dh-python does not skip the line, but tries to find the python3 module
providing path2lib, which of course does not exist, and thus fails the
build:

I: dh_python3 pydist:304: Cannot find package that provides pathlib2.
Please add package that provides it to Build-Depends or add "pathlib2
python3-pathlib2" line to debian/py3dist-overrides or add proper
dependency to Depends by hand and ignore this info.
Traceback (most recent call last):
  File "/usr/bin/dh_python3", line 280, in 
main()
  File "/usr/bin/dh_python3", line 201, in main
dependencies.parse(stats, options)
  File "/usr/share/dh-python/dhpython/depends.py", line 242, in parse
deps = parse_pydep(self.impl, fn, bdep=self.bdep,
**section_options)
  File "/usr/share/dh-python/dhpython/pydist.py", line 496, in
parse_pydep
for part in dependency.split(','))
AttributeError: 'NoneType' object has no attribute 'split'
make: *** [debian/rules:8: binary] Error 1

This does not happen on previous versions of dh-python, so I imagine it
could be a regression from:

https://salsa.debian.org/python-team/tools/dh-python/-/commit/832f01c9c7da22a1d00887d8ce0e6be9893bdf3e

Found while rebuilding:

https://salsa.debian.org/python-team/packages/microsoft-authentication-extensions-for-python/-/jobs/2284212

As far as I understand the usage of python_version in this format is
legitimate, and the change causes reverse deps to FTBFS, hence the
severity. Feel free to downgrade if that's not the case.

-- 
Kind regards,
Luca Boccassi


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

Bug#1001797: python-duckpy: autopkgtest tests all supported python3 versions but doesn't ensure they are installed

[Paul Gevers]

Source: python-duckpy
Version: 3.2.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of python-duckpy fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
python-duckpy  from testing3.2.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems the 
test tries to test for all supported Python3 versions, but fails to 
ensure all those versions are actually installed during the test. E.g. a 
test dependency on python3-all (or one of its siblings).


Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python3.10, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/996584
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-duckpy/17574738/log.gz

Testing with python3.10 in 
/tmp/autopkgtest-lxc.hmzefuht/downtmp/autopkgtest_tmp:
/tmp/autopkgtest-lxc.hmzefuht/downtmp/build.d02/src/debian/tests/run-unit-test: 
line 19: python3.10: command not found

autopkgtest [06:11:09]: test run-unit-test



OpenPGP_signature
Description: OpenPGP digital signature

Processed: python-duckpy: autopkgtest tests all supported python3 versions but doesn't ensure they are installed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:python3-defaults
Bug #1001797 [src:python-duckpy] python-duckpy: autopkgtest tests all supported 
python3 versions but doesn't ensure they are installed
Added indication that 1001797 affects src:python3-defaults

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

Bug#1001273: gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*

[Gregor Riepl]

> Here is a list of files that are known to be shared by both packages
> (according to the Contents file for sid/amd64, which may be
> slightly out of sync):
> 
>   /usr/lib/libcc1.so
>   /usr/lib/libcc1.so.0
>   /usr/lib/libcc1.so.0.0.0

To be honest, this sounds like a packaging issue.
libcc1.so should not be installed by a specific cross compiler at all,
at least not for the host architecture and certainly not into /usr/lib.

If the libcc1 versions used by gcc-avr and/or gcc-sh-elf are
incompatible with what's provided by libcc1-0, then these two packages
should either be linked statically or their own versions be installed
into /usr/lib//lib (or something similar)

FWIW, this is likely caused by these two cross compilers being based on
very old gcc versions.

At least gcc-avr should be fixed by upgrading it to something newer than
the Atmel/Microchip-patched version.
Related bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932989

Bug#997253: closing 997253

[Laurent Bigonville]

close 997253 
thanks

I cannot reproduce the FTBFS with that exact error

15.0+dfsg1-3 that I just uploaded also builds fine on the buildd

I'm closing this bug

Processed: closing 997253

[Debian Bug Tracking System]

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

> close 997253
Bug #997253 [src:pulseaudio] pulseaudio: FTBFS: 
./obj-x86_64-linux-gnu/meson-private/tmpp5n2633i/testfile.c:17: undefined 
reference to `lrintf'
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1001014: marked as done (burp: Incompatible with openssl 3.0)

[Debian Bug Tracking System]

Your message dated Thu, 16 Dec 2021 13:00:57 +0100
with message-id <9d3b7a59-b89c-903c-195f-d5647ad4a...@nerdrug.org>
and subject line Re: burp: Incompatible with openssl 3.0
has caused the Debian Bug report #1001014,
regarding burp: Incompatible with openssl 3.0
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.)


-- 
1001014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: burp
Version: 2.4.0-3
Severity: serious
Tags: patch experimental
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch

Dear maintainers,

Ubuntu has begun the transition to OpenSSL 3.  While there are a good number
of packages that will need fixes in order to be buildable against libssl3,
burp builds successfully but then fails its test suite because its v1
protocol depends on the use of ciphers that are unavailable with the default
provider in OpenSSL 3.

The attached patch has been applied in Ubuntu for this issue.  Please
consider including it in Debian as well and forwarding it upstream.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru burp-2.4.0/debian/patches/openssl3-compat.patch 
burp-2.4.0/debian/patches/openssl3-compat.patch
--- burp-2.4.0/debian/patches/openssl3-compat.patch 1969-12-31 
16:00:00.0 -0800
+++ burp-2.4.0/debian/patches/openssl3-compat.patch 2021-12-02 
09:43:02.0 -0800
@@ -0,0 +1,79 @@
+Description: Fix compatibility with OpenSSL 3
+ burp's legacy protocol depends on algorithms that are no longer available
+ in the default provider.
+ .
+ we also need to invoke EVP_CipherInit_ex differently.
+Author: Steve Langasek 
+Last-Update: 2021-12-02
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1952959
+Forwarded: no
+
+Index: burp-2.4.0/src/protocol1/handy.c
+===
+--- burp-2.4.0.orig/src/protocol1/handy.c
 burp-2.4.0/src/protocol1/handy.c
+@@ -10,6 +10,10 @@
+ #include "../log.h"
+ #include "handy.h"
+ 
++#if OPENSSL_VERSION_NUMBER >= 0x3000L
++#include 
++#endif
++
+ static int do_encryption(struct asfd *asfd, EVP_CIPHER_CTX *ctx,
+   uint8_t *inbuf, int inlen, uint8_t *outbuf, int *outlen,
+   MD5_CTX *md5)
+@@ -41,9 +45,42 @@
+   uint8_t enc_iv[9];
+   uint8_t enc_key[256];
+   EVP_CIPHER_CTX *ctx=NULL;
+-  const EVP_CIPHER *cipher=EVP_bf_cbc();
++
++  const EVP_CIPHER *cipher;
+   int key_len;
+-  
++
++#if OPENSSL_VERSION_NUMBER >= 0x3000L
++  static OSSL_PROVIDER *legacy_provider = NULL;
++  static OSSL_PROVIDER *default_provider = NULL;
++  static OSSL_LIB_CTX *ossl_ctx = NULL;
++
++  if (!ossl_ctx)
++  ossl_ctx = OSSL_LIB_CTX_new();
++  if (!ossl_ctx)
++  {
++  logp("OSSL_LIB_CTX_new failed\n");
++  goto error;
++  }
++
++  if (!legacy_provider)
++  legacy_provider = OSSL_PROVIDER_load(ossl_ctx, "legacy");
++  if (!legacy_provider) {
++  logp("OSSL_PROVIDER_load(legacy) failed\n");
++  goto error;
++  }
++
++  if (!default_provider)
++  default_provider = OSSL_PROVIDER_load(ossl_ctx, "default");
++  if (!default_provider) {
++  logp("OSSL_PROVIDER_load(default) failed\n");
++  goto error;
++  }
++
++  cipher = EVP_CIPHER_fetch(ossl_ctx, "BF-CBC", NULL);
++#else
++  cipher = EVP_bf_cbc();
++#endif
++
+   if(!encryption_password)
+   {
+   logp("No encryption password in %s()\n", __func__);
+@@ -84,7 +121,7 @@
+ 
+   // Don't set key or IV because we will modify the parameters.
+   EVP_CIPHER_CTX_init(ctx);
+-  if(!(EVP_CipherInit_ex(ctx, cipher, NULL, NULL, NULL, encrypt)))
++  if(!(EVP_CipherInit_ex(ctx, cipher, NULL, enc_key, enc_iv, encrypt)))
+   {
+   logp("EVP_CipherInit_ex failed\n");
+   goto error;
diff -Nru burp-2.4.0/debian/patches/series burp-2.4.0/debian/patches/series
--- burp-2.4.0/debian/patches/series2021-11-09 03:17:59.0 -0800
+++ burp-2.4.0/debian/patches/series2021-12-02 09:41:44.0 -0800
@@ -1,2 +1,3 @@
 increase_attribs_test_timeout.diff
 fix_ncurses_warning.diff
+openssl3-compat.patch
--- End Message ---
--- Begin Message ---

Thank 

Processed: tagging 996335

[Debian Bug Tracking System]

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

> tags 996335 + ftbfs
Bug #996335 {Done: Laurent Bigonville } [pulseaudio] 
pulseaudio FTBFS, doxygen not found.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#996335: marked as done (pulseaudio FTBFS, doxygen not found.)

[Debian Bug Tracking System]

Your message dated Thu, 16 Dec 2021 11:49:00 +
with message-id 
and subject line Bug#996335: fixed in pulseaudio 15.0+dfsg1-3
has caused the Debian Bug report #996335,
regarding pulseaudio FTBFS, doxygen not found.
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.)


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

Package: pulseaudio
Version: 15.0+dfsg1-2

The new version of pulseaudio failed to build when we pulled it into 
raspbian bookworm-staging.



Run-time dependency check found: YES 0.15.2
Configuring doxygen.conf using configuration
Program doxygen found: NO


Checking reproducible builds shows this is not a raspbian specific issue 
with failures in bookworm on
amd64, arm64 and armhf and a failures in sid on i386. Tests in sid on 
amd64, arm64 and armhf are
showing as a pass but were last tested some time ago. The latest version 
has not been tested in

bookworm on i386.

I initially thought this would be a case of a missing build-dependency 
that was previously pulled in
indirectly, but that does not appear to be the case. The successful 
older builds do not seem to have

pulled in doxygen either.

Nevertheless I needed to get this built for raspbian, so I decided to 
add a build-dependency on doxygen

and in doing so was able to perform a succesful build.

--- End Message ---
--- Begin Message ---
Source: pulseaudio
Source-Version: 15.0+dfsg1-3
Done: Laurent Bigonville 

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated pulseaudio package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 16 Dec 2021 12:33:25 +0100
Source: pulseaudio
Architecture: source
Version: 15.0+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Pulseaudio maintenance team 

Changed-By: Laurent Bigonville 
Closes: 993095 996335
Changes:
 pulseaudio (15.0+dfsg1-3) unstable; urgency=medium
 .
   * Team upload.
   [ Sebastien Bacher ]
   * debian/rules:
 - fix a typo in the glib build option
 .
   [ Laurent Bigonville ]
   * debian/rules: Explicitly disable building doxygen documentation
 (Closes: #996335)
   * debian/control: Move libpulse-mainloop-glib0 and libpulsedsp to libs
   * debian/control: Bump Standards-Version to 4.6.0 (no further changes)
 .
   [ Helmut Grohne ]
   * Fix nocheck FTBFS: Disable tests. (Closes: #993095)
Checksums-Sha1:
 d0b064d97ebafcc177257664ce1f11f695edb9bc 3360 pulseaudio_15.0+dfsg1-3.dsc
 0682fe838c2cee8c8114aaa0e4d8676381580b28 36096 
pulseaudio_15.0+dfsg1-3.debian.tar.xz
 4170bf613cf57432b6742887a8ac706d812e5042 15193 
pulseaudio_15.0+dfsg1-3_source.buildinfo
Checksums-Sha256:
 574b443475518dc6a148417eb9cb29db0275c1e787911c4b822eab1f6a425643 3360 
pulseaudio_15.0+dfsg1-3.dsc
 afc289e9a210fe5d90ec5a46f996c0ca527a849837d7c7a77ff7048caad13c3c 36096 
pulseaudio_15.0+dfsg1-3.debian.tar.xz
 05c38da479e9a77049e5824a30025babc7946df69f6ee7f119441aa9caa83d62 15193 
pulseaudio_15.0+dfsg1-3_source.buildinfo
Files:
 6f91b29f0ea0c4aa88518ab33227a65a 3360 sound optional 
pulseaudio_15.0+dfsg1-3.dsc
 7e461776d649b0776da423919239952d 36096 sound optional 
pulseaudio_15.0+dfsg1-3.debian.tar.xz
 2c58282d3d008f2afdea259bee184f97 15193 sound optional 
pulseaudio_15.0+dfsg1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAmG7JMoRHGJpZ29uQGRl
Ymlhbi5vcmcACgkQH8WJHrqwQ9WqJQf/SstBAObQs+wT8ajd7EfimBjApeCfljWH
x6/QnMz8xr6CgNN7HOFrCdvmVHjJ6ce0dkRb73Du9V12XLQ/Mz5HBN988ycomiVd
nJ5SCpgee3LV+czN9rS/VLNmLBHXUI2IekFR2KSrBBGJKlTazUTSQ0/yxrgyUXOs
Yb5aKComi+zfM9ht3Q74H5yFtQQQFmZ5JQ4JudxSmsJIN5HwClXNbvR+lW9SW5CS
6TmDiTpXz/bBitaLGwQ8GoSu3y/WOTMf5yEw/Bd9Nn7hUwFumHubSB0O9BV5tiXs
1mZ4OeGryCn+8w+WWQyRwCHTz+ihlieAF+cLO00pTe94ZEP3BQixiQ==
=YNa4
-END PGP SIGNATURE End Message ---

Processed: closing 962323

[Debian Bug Tracking System]

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

> close 962323
Bug #962323 [python-django] python-django: CVE-2020-13254 CVE-2020-13596
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1001791: fonts-cantarell: Renders system hardly usable

[Fabian Greffrath]

Hi,

Am 16.12.2021 11:22, schrieb G. Heine:
this version displays only letters a-z correctly thus making the system 
hardly
usable, unless you change to a different font. The problem is best 
shown with

the attached screen-shot.


this seems to be a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788791

Have you restarted your desktop session after the fonts have been 
upgraded?


 - Fabian

Bug#995212: ungoogled-chromium? [was: Re: Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)]

[Jeff Blake]

On Wed, 15 Dec 2021 21:08:28 +0100 Stephen Kitt  wrote:
> Hi Jeff,
> 
> On Tue, 14 Dec 2021 09:13:42 +, Jeff Blake  wrote:
> [...]
> > Inspector and convertutf are the worst offenders in terms of being
> > unnecessary and complex. The disable/catapult.patch could also be dropped,
> > since profiling might be desirable to some users.
> 
> convertutf at least is required for licensing reasons — it replaces code
> which is stripped from the upstream tarball because it’s not DFSG-free. See
> https://lintian.debian.org/tags/license-problem-convert-utf-code for details.
> 
> Regards,
> 
> Stephen


Hi Stephen,

That's a good point, however upstream Chromium currently requires version 69 of 
icu 
which only exists in Debian Experimental (via icu70). Stable and Unstable both 
have 
icu67 available.

I'm not sure what the solution would be. I suppose patching chromium to work 
with 
icu67, trying to get icu69/70 into unstable (and backporting this to 
stable/dropping 
chromium from stable) or even moving chromium to non-free would be among the 
options.


Best wishes,

Jeff

Bug#1001791: fonts-cantarell: Renders system hardly usable

[G. Heine]

Package: fonts-cantarell
Version: 0.303-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: g...@safe-mail.net

Dear Maintainer,

this version displays only letters a-z correctly thus making the system hardly
usable, unless you change to a different font. The problem is best shown with
the attached screen-shot.

An earlier bug report seems not to have reached Debian's bug tracking system.
If it has, please delete one or merge.

Yours
G. Heine


-- Package-specific info:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description
+++-==-=--=
ii  fontconfig 2.13.1-4.2amd64generic font configuration 
library - support binaries
ii  libfreetype6:amd64 2.11.0+dfsg-1 amd64FreeType 2 font engine, 
shared library files
ii  libxft2:amd64  2.3.2-2   amd64FreeType-based font drawing 
library for X

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

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

Versions of packages fonts-cantarell depends on:
ii  fontconfig  2.13.1-4.2

fonts-cantarell recommends no packages.

fonts-cantarell suggests no packages.

-- no debconf information

Bug#1001789: r-cran-gplots: package 'gplots' was installed before R 4.0.0: please re-install it

[Andreas Tille]

Package: r-cran-gplots
Version: 3.1.1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debia...@lists.debian.org

Hi,

seems r-cran-gplots has sliped trough in the Transition r-base for 4.0.0
(bug #955211).  This is strange since current r-cran-gplots was uploaded
at 2020-11-29 while the transition bug was closed 2020-10-31 - but anyway
gplots claims to be installed "installed before R 4.0.0" when running on
stable=bullseye (not on testing / unstable):

$ R -e 'library(gplots)'

R version 4.0.4 (2021-02-15) -- "Lost Library Book"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

  Natural language support but running in an English locale

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> library(gplots)
Error: package or namespace load failed for 'gplots':
 package 'gplots' was installed before R 4.0.0: please re-install it
Execution halted


Kind regards

 Andreas.


-- System Information:
Debian Release: 11.1
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable'), (50, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages r-cran-gplots depends on:
ii  r-base-core [r-api-4.0]  4.0.4-1
ii  r-cran-catools   1.18.1-1
ii  r-cran-gdata 2.18.0-3
ii  r-cran-gtools3.8.2-1+b1
ii  r-cran-kernsmooth2.23-18-1

r-cran-gplots recommends no packages.

r-cran-gplots suggests no packages.

-- no debconf information

Bug#1001714: update 1

[Andy Smith]

Hi Detlev,

On Thu, Dec 16, 2021 at 09:05:07AM +0100, detlev schmidtke wrote:
> I read in the Debian Wiki
> (https://wiki.debian.org/UEFI#RAID_for_the_EFI_System_Partition): 
> 
> "But for software RAID systems there is currently no support for
> putting the ESP on two separate disks in RAID."
> 
> I interpret that as "it cannot work", so, the Debian Installer should
> refuse to install EFI on a Software RAID with an appropriate message,
> instead of running into this error.

It's a bit more complicated than that.

By default, md uses version 1.2 superblock which lives near the start
of the device. Software with no concept of md RAID will read a
member device and see an MD superblock at the start instead of the
filesystem format they expect. So, this will not work and I would
tend to agree that the installer should not allow a device with such
a superblock to be used as an ESP.

Metadata versions 0.9 and 1.0 can instead be used; these have the
data near the end of the device. As a consequence, the beginning of
RAID-1 member devices are indistinguishable from the below
filesystem being directly on the device. This trick was used to get
grub to boot RAID-1 before it had support for md RAID: grub couldn't
tell that it wasn't just reading a normal filesystem.

An MD RAID-1 array with superblock version 0.9 or 1.0 will very
likely work as an ESP and many people do this. The installer should
probably not prohibit it.

This strategy can still fail. It relies upon nothing except the OS
itself writing to that member device. I have not seen it but some
people say that there are firmwares and bootloaders that will write
to the ESP. Since they would not be aware of md, they would change
one member device and not another. When you booted with such a setup
MD would complain and not assemble the array. You'd have to choose
which member device "won" and have the other overwrite it.

Due to that, some people instead have multiple ESPs and come up with
elaborate schemes to sync them in user space.

That was the state of things when I last asked on debian-user in
November 2020:

https://lists.debian.org/debian-user/2020/11/msg00455.html

Here's a script I use to sync ESPs:

https://gist.github.com/grifferz/f262591f59e4f8c199a8b0619bc6a667

But again, I don't think it's a good idea to ban ESP on MD array as
this is a working configuration for many.

Cheers,
Andy

Bug#999291: xfsdump: diff for NMU version 3.1.9+0+nmu1

[Damyan Ivanov]

Control: tags 999291 + patch
Control: tags 999291 + pending

Dear maintainer,

I've prepared an NMU for xfsdump (versioned as 3.1.9+0+nmu1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru xfsdump-3.1.9+0/debian/changelog xfsdump-3.1.9+0+nmu1/debian/changelog
--- xfsdump-3.1.9+0/debian/changelog	2020-07-11 03:48:32.0 +0300
+++ xfsdump-3.1.9+0+nmu1/debian/changelog	2021-12-16 10:44:12.0 +0200
@@ -1,3 +1,11 @@
+xfsdump (3.1.9+0+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * add build-arch and build-indep targets to debian/rules
+Closes: #999291
+
+ -- Damyan Ivanov   Thu, 16 Dec 2021 08:44:12 +
+
 xfsdump (3.1.9+0) unstable; urgency=medium
 
   * In postinst, create as needed the xfsdump and xfsrestore symlinks
diff -Nru xfsdump-3.1.9+0/debian/rules xfsdump-3.1.9+0+nmu1/debian/rules
--- xfsdump-3.1.9+0/debian/rules	2020-01-31 19:30:58.0 +0200
+++ xfsdump-3.1.9+0+nmu1/debian/rules	2021-12-16 10:43:03.0 +0200
@@ -12,12 +12,16 @@
 	  INSTALL_USER=root INSTALL_GROUP=root ;
 checkdir = test -f debian/rules
 
-build: built
+build: build-arch build-indep
+
+build-arch: built
 built: config
 	@echo "== dpkg-buildpackage: build" 1>&2
 	$(MAKE) default
 	touch built
 
+build-indep:
+
 config: .census
 .census:
 	@echo "== dpkg-buildpackage: configure" 1>&2

Processed: xfsdump: diff for NMU version 3.1.9+0+nmu1

[Debian Bug Tracking System]

Processing control commands:

> tags 999291 + patch
Bug #999291 [src:xfsdump] xfsdump: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999291 + pending
Bug #999291 [src:xfsdump] xfsdump: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999216: lpr: diff for NMU version 1:2008.05.17.3+nmu1

[Damyan Ivanov]

Control: tags 999216 + patch
Control: tags 999216 + pending

Dear maintainer,

I've prepared an NMU for lpr (versioned as 1:2008.05.17.3+nmu1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru lpr-2008.05.17.3/debian/changelog lpr-2008.05.17.3+nmu1/debian/changelog
--- lpr-2008.05.17.3/debian/changelog	2019-01-11 22:06:54.0 +0200
+++ lpr-2008.05.17.3+nmu1/debian/changelog	2021-12-16 10:35:18.0 +0200
@@ -1,3 +1,11 @@
+lpr (1:2008.05.17.3+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * add build-arch and build-indep targets to debian/rules
+(Closes: #999216)
+
+ -- Damyan Ivanov   Thu, 16 Dec 2021 08:35:18 +
+
 lpr (1:2008.05.17.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru lpr-2008.05.17.3/debian/rules lpr-2008.05.17.3+nmu1/debian/rules
--- lpr-2008.05.17.3/debian/rules	2019-01-11 22:06:54.0 +0200
+++ lpr-2008.05.17.3+nmu1/debian/rules	2021-12-16 10:33:03.0 +0200
@@ -9,20 +9,24 @@
 CPPFLAGS = -Wall -g -O2 -D_GNU_SOURCE -D__KAME__ -I../common_source
 # -D_BSD_SOURCE
 
-build: build-stamp
-build-stamp:
+build: build-arch build-indep
+build-arch: build-arch-stamp
+build-arch-stamp:
 	dh_testdir
 	make -W CFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)"
-	touch build-stamp
+	touch $@
+
+build-indep:
+# nothing to do here
 
 clean: 
 	dh_testdir
 	dh_testroot
-	rm -f build-stamp install-stamp
+	rm -f build-arch-stamp install-stamp
 	-make clean
 	dh_clean
 
-install: build-stamp
+install: build
 	dh_testdir
 	dh_testroot
 	dh_clean -k
@@ -69,4 +73,4 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install

Processed: lpr: diff for NMU version 1:2008.05.17.3+nmu1

[Debian Bug Tracking System]

Processing control commands:

> tags 999216 + patch
Bug #999216 [src:lpr] lpr: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) patch.
> tags 999216 + pending
Bug #999216 [src:lpr] lpr: missing required debian/rules targets build-arch 
and/or build-indep
Added tag(s) pending.

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

Bug#1001785: texlive-extra affected by log4j CVEs

[Sven Mueller]

Package: texlive-extra-utils
Severity: grave
Version: 2021.20211127-1
Tags: security

texlive-extra-utils contains arara (https://github.com/islandoftex/arara)
which was updated two days ago via TeX Live (https://www.tug.org/texlive/)
which was updated slightly after that. Please update to the newest TeX Live
ASAP, as arara in unstable and testing (also stable?) currently bundles a
vulnerable apache-log4j2 version.

The alternative would be to remove the JndiLookup.class file from the
relevant .jar - This causes a warning but otherwise doesn't affect
execution and seems to properly avoid the vulnerabilities in CVE-2021-45046
and CVE-2021-44228

Bug#984410: marked as done (zeromq3: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Thu, 16 Dec 2021 08:33:42 +
with message-id 
and subject line Bug#984410: fixed in zeromq3 4.3.4-2
has caused the Debian Bug report #984410,
regarding zeromq3: ftbfs with GCC-11
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.)


-- 
984410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:zeromq3
Version: 4.3.4-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/zeromq3_4.3.4-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
Note: Writing zmq.7
xmlto man zmq_ipc.xml
Note: Writing zmq_tcp.7
xmlto man zmq_null.xml
Note: Writing zmq_inproc.7
Note: Writing zmq_pgm.7
xmlto man zmq_plain.xml
xmlto man zmq_curve.xml
Note: Writing zmq_ipc.7
xmlto man zmq_tipc.xml
Note: Writing zmq_null.7
xmlto man zmq_vmci.xml
Note: Writing zmq_plain.7
xmlto man zmq_udp.xml
Note: Writing zmq_curve.7
xmlto man zmq_gssapi.xml
Note: Writing zmq_tipc.7
Note: Writing zmq_vmci.7
Note: Writing zmq_udp.7
Note: Writing zmq_gssapi.7
rm zmq_timers.xml zmq_disconnect.xml zmq_msg_move.xml zmq_udp.xml 
zmq_atomic_counter_set.xml zmq_ctx_set.xml zmq_ipc.xml zmq_msg_routing_id.xml 
zmq_z85_encode.xml zmq_ctx_shutdown.xml zmq_msg_send.xml 
zmq_atomic_counter_new.xml zmq.xml zmq_atomic_counter_destroy.xml 
zmq_sendmsg.xml zmq_msg_gets.xml zmq_msg_init_buffer.xml zmq_msg_more.xml 
zmq_msg_set.xml zmq_poll.xml zmq_atomic_counter_value.xml zmq_socket.xml 
zmq_ctx_get.xml zmq_close.xml zmq_curve.xml zmq_recvmsg.xml zmq_inproc.xml 
zmq_msg_recv.xml zmq_strerror.xml zmq_getsockopt.xml zmq_setsockopt.xml 
zmq_errno.xml zmq_recv.xml zmq_curve_keypair.xml zmq_vmci.xml 
zmq_z85_decode.xml zmq_socket_monitor_versioned.xml zmq_atomic_counter_dec.xml 
zmq_msg_close.xml zmq_bind.xml zmq_send_const.xml zmq_unbind.xml zmq_send.xml 
zmq_version.xml zmq_msg_get.xml zmq_socket_monitor.xml zmq_connect.xml 
zmq_msg_size.xml zmq_msg_copy.xml zmq_curve_public.xml zmq_null.xml 
zmq_ctx_new.xml zmq_gssapi.xml zmq_ctx_term.xml zmq_msg_init_data.xml zmq_atomi
 c_counter_inc.xml zmq_msg_data.xml zmq_msg_init_size.xml zmq_pgm.xml 
zmq_proxy_steerable.xml zmq_poller.xml zmq_msg_set_routing_id.xml 
zmq_msg_init.xml zmq_tcp.xml zmq_proxy.xml zmq_tipc.xml zmq_has.xml 
zmq_connect_peer.xml zmq_plain.xml
make[2]: Leaving directory '/<>/doc'
make[2]: Entering directory '/<>'
g++ -DHAVE_CONFIG_H -I. -I./src  -I./include -I./include -D_GNU_SOURCE 
-D_REENTRANT -D_THREAD_SAFE -Wdate-time -D_FORTIFY_SOURCE=2  -pedantic -Werror 
-Wall -Wno-long-long -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -ffat-lto-objects -c 
-o tools/curve_keygen.o tools/curve_keygen.cpp
/bin/bash ./libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I./src 
   -I/usr/include/pgm-5.3 -I/usr/include/libxml2 -isystem 
/usr/include/mit-krb5 -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -Wdate-time 
-D_FORTIFY_SOURCE=2 -fvisibility=hidden -pedantic -Werror -Wall 
-Wno-long-long -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -ffat-lto-objects -c 
-o src/libzmq_la-address.lo `test -f 

Bug#1001657: Ball fails its autopkgtest - how to properly deal with sip files?

[Nilesh Patra]

On 12/16/21 1:24 PM, Andreas Tille wrote:

Hi Étienne,

Am Wed, Dec 15, 2021 at 11:23:17PM +0100 schrieb Étienne Mollier:


I pushed my changes leading to these errors, but getting the
other bugs affecting ball fixed before Christmas might involve
undoing the setting of SIP_LIBRARIES in d/rules.


Thanks a lot for your investigations.  I do not think we have a real
time limit for ball - but this is a good time to do some polishing in
BTW and if we delay the solution it might become forgotten again.
That's why I'm asking whether the effort to solve the issue is worth
doing compared to simply droping the Python3 package which I consider a
valid solution of the problem.


Only my opinion:

Just do this, IMO i.e. drop package. I don't think it is worth spending so much
time to fix this when we have no real users.
There is a "possibility" that the popcon score (2) would have come from our us 
installing it in
own machines only for testing purposes.
Upstream is dead as well, so this gives me several green flags to
proceed with a removal.

Regards,
Nilesh



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001714: update 1

[detlev schmidtke]

I read in the Debian Wiki
(https://wiki.debian.org/UEFI#RAID_for_the_EFI_System_Partition): 

"But for software RAID systems there is currently no support for
putting the ESP on two separate disks in RAID."

I interpret that as "it cannot work", so, the Debian Installer should
refuse to install EFI on a Software RAID with an appropriate message,
instead of running into this error.

Processed: swish-e: diff for NMU version 2.4.7-6.1

[Debian Bug Tracking System]

Processing control commands:

> tags 999279 + patch
Bug #999279 [src:swish-e] swish-e: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999279 + pending
Bug #999279 [src:swish-e] swish-e: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999279: swish-e: diff for NMU version 2.4.7-6.1

[Damyan Ivanov]

Control: tags 999279 + patch
Control: tags 999279 + pending

Dear maintainer,

I've prepared an NMU for swish-e (versioned as 2.4.7-6.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -u swish-e-2.4.7/debian/changelog swish-e-2.4.7/debian/changelog
--- swish-e-2.4.7/debian/changelog
+++ swish-e-2.4.7/debian/changelog
@@ -1,3 +1,10 @@
+swish-e (2.4.7-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * add build-arch and build-inde targets to debian/rules (Closes: #999279)
+
+ -- Damyan Ivanov   Thu, 16 Dec 2021 07:52:44 +
+
 swish-e (2.4.7-6) unstable; urgency=medium
 
   * Fixed the zlib related build problem. Closes: #869860
diff -u swish-e-2.4.7/debian/rules swish-e-2.4.7/debian/rules
--- swish-e-2.4.7/debian/rules
+++ swish-e-2.4.7/debian/rules
@@ -26,6 +26,11 @@
 	rm -f html/search.cgi debian/files
 	rm -f SWISH-Stemmer-0.05.tar.gz
 
+build-indep:
+	# nothing
+
+build-arch: build
+
 build: build.stamp
 build.stamp:
 	dh_testdir
@@ -89,4 +94,4 @@
 
 binary-indep: build
 
-.PHONY: clean build binary binary-arch binary-indep
+.PHONY: clean build build-arch build-indep binary binary-arch binary-indep

Processed: Re: libapache2-mod-encoding: missing required debian/rules targets build-arch and/or build-indep

[Debian Bug Tracking System]

Processing control commands:

> tags 999264 pending
Bug #999264 [src:libapache2-mod-encoding] libapache2-mod-encoding: missing 
required debian/rules targets build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999323: libapache-mod-encoding: missing required debian/rules targets build-arch and/or build-indep

[Christoph Biedl]

Control: tags 999323 pending

Lucas Nussbaum wrote...

> Source: libapache-mod-encoding
> Justification: Debian Policy section 4.9

In the past I already did an NMU for this package, will do it again.

Just in the unlikely case somebody wants to adopt the package: Let me
knowt so duplicated work is avoided.

Christoph


signature.asc
Description: PGP signature

Processed: Re: Bug#999323: libapache-mod-encoding: missing required debian/rules targets build-arch and/or build-indep

[Debian Bug Tracking System]

Processing control commands:

> tags 999323 pending
Bug #999323 [src:libapache-mod-encoding] libapache-mod-encoding: missing 
required debian/rules targets build-arch and/or build-indep
Added tag(s) pending.

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

Bug#999264: libapache2-mod-encoding: missing required debian/rules targets build-arch and/or build-indep

[Christoph Biedl]

Control: tags 999264 pending

Lucas Nussbaum wrote...

> Source: libapache2-mod-encoding
> Justification: Debian Policy section 4.9

In the past I already did an NMU for this package, will do it again.

Just in the unlikely case somebody wants to adopt the package: Let me
knowt so duplicated work is avoided.

Christoph


signature.asc
Description: PGP signature