Bug#1007858: [Pkg-javascript-devel] Bug#1007858: Bug#1007858: node-lodash: FTBFS with nodejs experimental/14.19.0

[Jérémy Lal]

On Wed, Apr 6, 2022 at 6:30 PM Jonas Smedegaard  wrote:

> Quoting Yadd (2022-04-06 18:12:30)
> > On 19/03/2022 08:38, Yadd wrote:
> > > On 19/03/2022 08:11, Yadd wrote:
> > >> On 17/03/2022 19:21, Jérémy Lal wrote:
> > >>> Source: node-lodash
> > >>> Version: 4.17.21+dfsg+~cs8.31.196.20210220-2
> > >>> Severity: important
> > >>> Tags: ftbfs
> > >>>
> > >>> This package fails to rebuild. Build log is attached.
> > >>
> > >> The real problem comes from uglify-js call. Build works fine with
> > >> uglifyjs 2 (as required by node-locash/package.json) but fails with
> > >> uglify-js 3. Here is the real error:
> > >>
> > >>error: JS_Parse_Error [SyntaxError]: Invalid flags supplied to
> > >> RegExp constructor 'node'
> > >>at JS_Parse_Error.get (eval at 
> > >>
> (/build/node-lodash-wQJpO3/node-lodash-4.17.21+dfsg+~cs8.31.198.20210220/node_modules/uglify-js/tools/node.js:18:1),
>
> > >> :63:23)
> > >>at formatError (internal/util/inspect.js:1149:38)
> > >>at formatRaw (internal/util/inspect.js:919:14)
> > >>at formatValue (internal/util/inspect.js:774:10)
> > >>at formatProperty (internal/util/inspect.js:1660:11)
> > >>at formatRaw (internal/util/inspect.js:987:9)
> > >>at formatValue (internal/util/inspect.js:774:10)
> > >>at inspect (internal/util/inspect.js:319:10)
> > >>at formatWithOptionsInternal (internal/util/inspect.js:1979:40)
> > >>at formatWithOptions (internal/util/inspect.js:1861:10) {
> > >>  filename: '0',
> > >>  line: 1,
> > >>  col: 0,
> > >>  pos: 0
> > >
> > > For now, I dropped internal minifier and pushed result to
> experimental.
> > > This may break some builds: minified files have to be generated
> separately.
> > >
> > > Can someone else have a look at this ?
> >
> > I'm unable to reproduce this failure in an up-to-date schroot, but build
> > fails in salsa CI [1], that's why I reopened this issue.
> >
> > [1]: https://salsa.debian.org/js-team/node-lodash/-/jobs/2648172
>
> Maybe check if upstream has a branch or pending MR with code to upgrade
> to UglifyJS v3?
>

It's mainly useless code coming from lodash-cli.
The mistake here is that build-dist.js is actually called.
It does just copy a file and wrongly call uglifyjs, which is done in
debian/rules properly anyway.

Please someone remind us to upload the fix when build deps conflicts are
fixed...

Jérémy

Processed: Bug#1007858 marked as pending in node-lodash

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1007858 [src:node-lodash] node-lodash: FTBFS with nodejs 
experimental/14.19.0
Ignoring request to alter tags of bug #1007858 to the same tags previously set

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

Processed: Bug#1007858 marked as pending in node-lodash

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1007858 [src:node-lodash] node-lodash: FTBFS with nodejs 
experimental/14.19.0
Ignoring request to alter tags of bug #1007858 to the same tags previously set

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

Bug#1007858: marked as pending in node-lodash

[Jérémy Lal]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-lodash/-/commit/20aa56939d2ec9501e465ded28ae87cf423cc328


Patch build-dist to disable minification. Closes: #1007858.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1007858

Bug#1007858: marked as pending in node-lodash

[Jérémy Lal]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-lodash/-/commit/1879c44eba50df67ceac351f592af665384a


Revert "Port build script to uglifyjs >= 3 (Closes: #1007858)"

This reverts commit 6008df77bdd02c2112b102ebfbb85c7d38d36122.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1007858

Bug#1007858: marked as pending in node-lodash

[Jérémy Lal]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-lodash/-/commit/6008df77bdd02c2112b102ebfbb85c7d38d36122


Port build script to uglifyjs >= 3 (Closes: #1007858)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1007858

Processed: Bug#1007858 marked as pending in node-lodash

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1007858 [src:node-lodash] node-lodash: FTBFS with nodejs 
experimental/14.19.0
Added tag(s) pending.

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

Bug#1008640: marked as done (scikit-fmm: FTBFS: /usr/include/python3.10/object.h:133:33: error: lvalue required as increment operand)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 22:51:20 +
with message-id 
and subject line Bug#1008640: fixed in scikit-fmm 2019.1.30-1.1
has caused the Debian Bug report #1008640,
regarding scikit-fmm: FTBFS: /usr/include/python3.10/object.h:133:33: error: 
lvalue required as increment operand
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.)


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

scikit-fmm FTBFS:

compile options: '-I/usr/lib/python3/dist-packages/numpy/core/include 
-Ibuild/src.linux-x86_64-3.9/numpy/distutils/include -I/usr/include/python3.9 
-c'
extra options: '-msse -msse2 -msse3'
x86_64-linux-gnu-g++: skfmm/pheap.cpp
x86_64-linux-gnu-g++: skfmm/heap.cpp
In file included from /usr/include/python3.10/Python.h:74,
 from skfmm/pheap.cpp:16:
skfmm/pheap.cpp: In function ‘void 
__pyx_tp_dealloc_5skfmm_5pheap_pheap(PyObject*)’:
/usr/include/python3.10/object.h:133:33: error: lvalue required as increment 
operand
  133 | #define Py_REFCNT(ob) _Py_REFCNT(_PyObject_CAST_CONST(ob))
  |   ~~^~
skfmm/pheap.cpp:1257:7: note: in expansion of macro ‘Py_REFCNT’
 1257 | ++Py_REFCNT(o);
  |   ^
/usr/include/python3.10/object.h:133:33: error: lvalue required as decrement 
operand
  133 | #define Py_REFCNT(ob) _Py_REFCNT(_PyObject_CAST_CONST(ob))
  |   ~~^~
skfmm/pheap.cpp:1260:7: note: in expansion of macro ‘Py_REFCNT’
 1260 | --Py_REFCNT(o);
  |   ^
In file included from /usr/include/python3.10/unicodeobject.h:1046,
 from /usr/include/python3.10/Python.h:83,
 from skfmm/pheap.cpp:16:
skfmm/pheap.cpp: In function ‘int __Pyx_ParseOptionalKeywords(PyObject*, 
PyObject***, PyObject*, PyObject**, Py_ssize_t, const char*)’:
/usr/include/python3.10/cpython/unicodeobject.h:451:61: warning: ‘Py_ssize_t 
_PyUnicode_get_wstr_length(PyObject*)’ is deprecated [-Wdeprecated-declarations]
  451 | #define PyUnicode_WSTR_LENGTH(op) 
_PyUnicode_get_wstr_length((PyObject*)op)
  |   
~~^~~
/usr/include/python3.10/cpython/unicodeobject.h:261:7: note: in expansion of 
macro ‘PyUnicode_WSTR_LENGTH’
  261 |   PyUnicode_WSTR_LENGTH(op) :\
  |   ^
skfmm/pheap.cpp:1598:22: note: in expansion of macro ‘PyUnicode_GET_SIZE’
 1598 | (PyUnicode_GET_SIZE(**name) != 
PyUnicode_GET_SIZE(key)) ? 1 :
  |  ^~
/usr/include/python3.10/cpython/unicodeobject.h:446:26: note: declared here
  446 | static inline Py_ssize_t _PyUnicode_get_wstr_length(PyObject *op) {
  |  ^~
/usr/include/python3.10/cpython/unicodeobject.h:262:33: warning: ‘Py_UNICODE* 
PyUnicode_AsUnicode(PyObject*)’ is deprecated [-Wdeprecated-declarations]
  262 |   ((void)PyUnicode_AsUnicode(_PyObject_CAST(op)),\
  |  ~~~^~~~
skfmm/pheap.cpp:1598:22: note: in expansion of macro ‘PyUnicode_GET_SIZE’
 1598 | (PyUnicode_GET_SIZE(**name) != 
PyUnicode_GET_SIZE(key)) ? 1 :
  |  ^~
/usr/include/python3.10/cpython/unicodeobject.h:580:45: note: declared here
  580 | Py_DEPRECATED(3.3) PyAPI_FUNC(Py_UNICODE *) PyUnicode_AsUnicode(
  | ^~~
/usr/include/python3.10/cpython/unicodeobject.h:451:61: warning: ‘Py_ssize_t 
_PyUnicode_get_wstr_length(PyObject*)’ is deprecated [-Wdeprecated-declarations]
  451 | #define PyUnicode_WSTR_LENGTH(op) 
_PyUnicode_get_wstr_length((PyObject*)op)
  |   
~~^~~
/usr/include/python3.10/cpython/unicodeobject.h:264:8: note: in expansion of 
macro ‘PyUnicode_WSTR_LENGTH’
  264 |PyUnicode_WSTR_LENGTH(op)))
  |^
skfmm/pheap.cpp:1598:22: note: in expansion of macro ‘PyUnicode_GET_SIZE’
 1598 | (PyUnicode_GET_SIZE(**name) != 
PyUnicode_GET_SIZE(key)) ? 1 :
  |  ^~
/usr/include/python3.10/cpython/unicodeobject.h:446:26: note: declared here
  446 | static inline 

Bug#1008688: marked as done (cwiid: FTBFS with Python 3.10)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 22:50:24 +
with message-id 
and subject line Bug#1008688: fixed in cwiid 0.6.91-2.1
has caused the Debian Bug report #1008688,
regarding cwiid: FTBFS with Python 3.10
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.)


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

cwiid FTBFS:

gcc -o wmgui main.o interface.o support.o -Wl,-z,relro -L../libcwiid 
-lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 
-lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lharfbuzz -lfontconfig 
-lfreetype -lgthread-2.0 -pthread -lglib-2.0 -lm -lcwiid -lbluetooth
make[2]: Leaving directory '/<>/wmgui'
make  -C wminput
make[2]: Entering directory '/<>/wminput'
bison -y -d parser.y 
parser.y:44.1-14: warning: POSIX Yacc does not support %error-verbose [-Wyacc]
   44 | mawk -f action_enum.awk action_enum.txt > action_enum.c
%error-verbose
  | ^~
parser.y:44.1-14: warning: deprecated directive: ‘%error-verbose’, use ‘%define 
parse.error verbose’ [-Wdeprecated]
   44 | %error-verbose
  | ^~
  | %define parse.error verbose
py_plugin.c:38:10: fatal error: Python.h: No such file or directory
   38 | #include "Python.h"
  |  ^~
compilation terminated.
In file included from uinput.c:44:
conf.h:56:10: fatal error: y.tab.h: No such file or directory
   56 | #include "y.tab.h"
  |  ^
compilation terminated.
In file included from c_plugin.c:33:
conf.h:56:10: fatal error: y.tab.h: No such file or directory
   56 | #include "y.tab.h"
  |  ^
compilation terminated.
In file included from conf.c:56:
conf.h:56:10: fatal error: y.tab.h: No such file or directory
   56 | #include "y.tab.h"
  |  ^
compilation terminated.
parser.y: warning: fix-its can be applied.  Rerun with option '--update'. 
[-Wother]
mv -f y.tab.c parser.c


See
https://buildd.debian.org/status/fetch.php?pkg=cwiid=amd64=0.6.91-2%2Bb3=1648451564=0

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: cwiid
Source-Version: 0.6.91-2.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated cwiid 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, 07 Apr 2022 00:27:18 +0200
Source: cwiid
Architecture: source
Version: 0.6.91-2.1
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Sebastian Ramacher 
Closes: 1008688
Changes:
 cwiid (0.6.91-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Graham Inggs ]
   * Support Python with 2-digit minor version (Closes: #1008688)
Checksums-Sha1:
 b7a9670069f4ddf906e44472b55e0df44a112420 2189 cwiid_0.6.91-2.1.dsc
 02e1b80786f17731595122d01c36c2715a4e6f14 17244 cwiid_0.6.91-2.1.debian.tar.xz
Checksums-Sha256:
 00798726b37c59f25274200ad627af1639bb32baff711c0a38625053c276 2189 
cwiid_0.6.91-2.1.dsc
 01286886dbef68ead04b34595816cd7ce9ff327886a8187c5b6e5f11ea0ec2c3 17244 
cwiid_0.6.91-2.1.debian.tar.xz
Files:
 dcfc8e00375f1f2c2beab5f487493889 2189 utils optional cwiid_0.6.91-2.1.dsc
 8a06351f57eff5a94e6fc38d069535d2 17244 utils optional 
cwiid_0.6.91-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmJOFJQACgkQafL8UW6n
GZPGGBAAhWAjNEt/nnvNhpL1ApseTk00mnvF2P2dcGRzF6PGtwWK2zQ/flh+b5gQ
67W+DQwot+BfCfk4js8NsuJVIvU9oH2oW7BFLll1frkc8bjFAN97bMRn7FUWnxtw
F+HCmVxjdrMzvso2GSMI8ti64DBptJ0Wu9CiZTZ105Ydwju+Y9W9dxyBEpkVfVjL
J8NSE6k5ASgkG/ztqeP1Y0J42ofU0nNP9/Q58oqlRUIy589MclkAOMTxub7m6s4+
8C82Hb/H7V3Icl97rVMl3VX8lEZ2hvC55Gio5LxJV76keBljgvCI8T/74hYcYUe5
27EzlpIR2RLy9dsOmlbK4OrbXPEFqa0y47VlcxKwjNw/sF9u5KwOJgiQE86fOFwn

Bug#1008640: scikit-fmm: diff for NMU version 2019.1.30-1.1

[Sebastian Ramacher]

Dear maintainer,

since this issue is currently blocking the python3.10-default
transition, I've prepared an NMU for scikit-fmm (versioned as
2019.1.30-1.1). The diff is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru scikit-fmm-2019.1.30/debian/changelog scikit-fmm-2019.1.30/debian/changelog
--- scikit-fmm-2019.1.30/debian/changelog	2020-11-14 17:13:33.0 +0100
+++ scikit-fmm-2019.1.30/debian/changelog	2022-04-07 00:36:51.0 +0200
@@ -1,3 +1,13 @@
+scikit-fmm (2019.1.30-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Graham Inggs ]
+  * Cythonize at build time to fix FTBFS with Python 3.10 (Closes: #1008640)
+  * Call dh --with numpy3 to pick up dependency on numpy-abi
+
+ -- Sebastian Ramacher   Thu, 07 Apr 2022 00:36:51 +0200
+
 scikit-fmm (2019.1.30-1) unstable; urgency=medium
 
   * Initial release (Closes: #974160)
diff -Nru scikit-fmm-2019.1.30/debian/control scikit-fmm-2019.1.30/debian/control
--- scikit-fmm-2019.1.30/debian/control	2020-11-14 17:13:33.0 +0100
+++ scikit-fmm-2019.1.30/debian/control	2022-04-07 00:33:42.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Bdale Garbee 
 Build-Depends: debhelper (>= 13), dh-python, python3-all, python3-setuptools,
- python3-numpy, python3-dev
+ python3-numpy, python3-dev, cython3
 Standards-Version: 4.5.0
 Homepage: https://github.com/scikit-fmm/scikit-fmm/
 X-Python3-Version: >= 3.6
diff -Nru scikit-fmm-2019.1.30/debian/rules scikit-fmm-2019.1.30/debian/rules
--- scikit-fmm-2019.1.30/debian/rules	2020-11-14 17:13:33.0 +0100
+++ scikit-fmm-2019.1.30/debian/rules	2022-04-07 00:33:34.0 +0200
@@ -8,7 +8,15 @@
 export LDFLAGS+=$(shell python3-config --ldflags)
 
 %:
-	dh $@ --with python3 --buildsystem=pybuild
+	dh $@ --with python3 --with numpy3 --buildsystem=pybuild
+
+override_dh_auto_clean:
+	rm -f $(CURDIR)/skfmm/pheap.cpp
+	dh_auto_clean
+
+override_dh_auto_configure:
+	cython3 --cplus -3 $(CURDIR)/skfmm/pheap.pyx
+	dh_auto_configure
 
 
 # If you need to rebuild the Sphinx documentation


signature.asc
Description: PGP signature

Bug#1008688: cwiid: diff for NMU version 0.6.91-2.1

[Sebastian Ramacher]

Control: tags 1008688 + patch

Dear maintainer,

this bug is currently blocking the python3.10-default transition, hence
I've prepared an NMU for cwiid (versioned as 0.6.91-2.1). The diff is
attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru cwiid-0.6.91/debian/changelog cwiid-0.6.91/debian/changelog
--- cwiid-0.6.91/debian/changelog	2020-11-11 12:39:34.0 +0100
+++ cwiid-0.6.91/debian/changelog	2022-04-07 00:27:18.0 +0200
@@ -1,3 +1,12 @@
+cwiid (0.6.91-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Graham Inggs ]
+  * Support Python with 2-digit minor version (Closes: #1008688)
+
+ -- Sebastian Ramacher   Thu, 07 Apr 2022 00:27:18 +0200
+
 cwiid (0.6.91-2) unstable; urgency=medium
 
   * modified the debian patch "wminput-Makefile.in.patch", after
diff -Nru cwiid-0.6.91/debian/patches/python3.10.patch cwiid-0.6.91/debian/patches/python3.10.patch
--- cwiid-0.6.91/debian/patches/python3.10.patch	1970-01-01 01:00:00.0 +0100
+++ cwiid-0.6.91/debian/patches/python3.10.patch	2022-04-07 00:26:23.0 +0200
@@ -0,0 +1,15 @@
+Description: Support Python with 2-digit minor version
+Author: Graham Inggs 
+Last-Update: 2022-01-28
+
+--- a/configure.ac
 b/configure.ac
+@@ -67,7 +67,7 @@
+ fi
+ AC_SUBST(PYTHON)
+ if test $PYTHON; then
+-	PYTHON_VERSION=[`$PYTHON -c 'import sys; print (sys.version[:3])'`]
++	PYTHON_VERSION=[`$PYTHON -c 'import sys; print ("%d.%d" % sys.version_info[:2])'`]
+ 	AC_SUBST(PYTHON_VERSION)
+ 	AC_DEFINE([HAVE_PYTHON],1,[Define to 1 if python support is enabled])
+ fi
diff -Nru cwiid-0.6.91/debian/patches/series cwiid-0.6.91/debian/patches/series
--- cwiid-0.6.91/debian/patches/series	2020-11-11 12:39:34.0 +0100
+++ cwiid-0.6.91/debian/patches/series	2022-04-07 00:26:23.0 +0200
@@ -5,3 +5,4 @@
 fix_wiid_pc.patch
 python-setup.py.patch
 wminput-Makefile.in.patch
+python3.10.patch


signature.asc
Description: PGP signature

Processed: cwiid: diff for NMU version 0.6.91-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1008688 + patch
Bug #1008688 [src:cwiid] cwiid: FTBFS with Python 3.10
Added tag(s) patch.

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

Processed: Re: Bug#1009054: Just crashes

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed fixed-upstream upstream
Bug #1009054 [openshot-qt] Just crashes
Added tag(s) fixed-upstream, upstream, and confirmed.
> forwarded -1 https://github.com/OpenShot/openshot-qt/issues/4596
Bug #1009054 [openshot-qt] Just crashes
Set Bug forwarded-to-address to 
'https://github.com/OpenShot/openshot-qt/issues/4596'.

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

Bug#1009054: Just crashes

[Sebastian Ramacher]

Control: tags -1 confirmed fixed-upstream upstream
Control: forwarded -1 https://github.com/OpenShot/openshot-qt/issues/4596

On 2022-04-06 17:17:01 +0200, julien.pu...@gmail.com wrote:
> Package: openshot-qt
> Version: 2.6.1+dfsg1-1
> Severity: grave
> 
> I just installed the software, launched "openshot-qt" and got a crash.

Indeed, openshot-qt currently doesn't work with Python 3.10. I'll upload
the fix in the next couple of days.

Cheers

> 
> I'll put the result of "openshot-qt 2>&1 |tee /tmp/log" at the end of
> this mail.
> 
> Cheers,
> 
> J.Puydt
> 
> Here is /tmp/log:
> 
> Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
> QT_QPA_PLATFORM=wayland to run on Wayland anyway.
> INFO app: 
> INFO app: Wed Apr  6 17:13:25 2022
> INFO app:   Starting new session  
> INFO app: 
> INFO app: OpenShot (version 2.6.1)
> INFO app: 
> INFO app: openshot-qt version: 2.6.1
> INFO app: libopenshot version: 0.2.7
> INFO app: platform: Linux-5.16.0-4-amd64-x86_64-with-glibc2.33
> INFO app: processor: 
> INFO app: machine: x86_64
> INFO app: python version: 3.10.4
> INFO app: qt5 version: 5.15.2
> INFO app: pyqt5 version: 5.15.6
> INFO project_data: Setting default profile to HD 720p 30 fps
> INFO language: Qt Detected Languages: ['fr-FR']
> INFO language: LANG Environment Variable: fr_FR.UTF-8
> INFO language: LOCALE Environment Variable: 
> INFO language: OpenShot Preference Language: Default
> INFO app: Setting font to Cantarell
> INFO logger_libopenshot: Connecting to libopenshot with debug port:
> 5556
> INFO app: Setting custom dark theme
> INFO ui_util: Initializing UI for MainWindow
> INFO webkit: WebKit backend initializing
> INFO thumbnail: Starting thumbnail server listening on port 55351
> INFO transition_model: updating transitions model.
> INFO effects_model: updating effects model.
> INFO emoji_model: updating emoji model.
> INFO version: Found current version: {'error_rate_stable': 0.16,
> 'trans_rate_unstable': 0.001, 'error_rate_unstable': 0.05,
> 'trans_rate_stable': 0.01, 'openshot_version': '2.6.1'}
> INFO main_window: InitCacheSettings
> INFO main_window: cache-mode: CacheMemory
> INFO main_window: cache-limit-mb: 250
> INFO main_window: Creating CacheMemory object with 262144000 byte limit
> INFO preview_thread: QThread Start Method Invoked
> ERROR main_window: Unhandled crash detected: linux-/lib/x86_64-linux-
> gnu/libc.so.6 abort 0x112 [0x7ff285404546]
> INFO main_window: updateStatusChanged
> INFO main_window: recover_backup
> INFO project_data: Setting default profile to HD 720p 30 fps
> INFO preview_thread: player Position(): 1
> INFO video_widget: Load: Set video widget display aspect ratio to:
> 1.777910232544
> INFO video_widget: Set video widget pixel aspect ratio to: 1.0
> INFO main_window: updateStatusChanged
> INFO webkit: Registering objects with WebKit
> qt.svg: Invalid path data; path truncated.
> qt.svg: Invalid path data; path truncated.
> qt.svg: Invalid path data; path truncated.
> Unhandled Python exception
> Caught signal 6 (SIGABRT)
>  Unhandled Exception: Stack Trace 
>   /lib/x86_64-linux-gnu/libc.so.6 ( abort 
> + 0x112 )  [0x7f199f905546]
>   /lib/x86_64-linux-gnu/libQt5Core.so.5 ( 
> + 0x90b51)  [0x7f199e6d6b51]
>   /usr/lib/python3/dist-packages/PyQt5/QtCore.abi3.so (   
> + 0xb5237)  [0x7f199ec4b237]
>   /usr/lib/python3/dist-packages/PyQt5/sip.cpython-310-x86_64-linux-
> gnu.so (   + 0x11363) 
> [0x7f199c0d8363]
>   /usr/lib/python3/dist-packages/PyQt5/QtWidgets.abi3.so (
> + 0x154b1d)  [0x7f199bcc0b1d]
>   /usr/lib/python3/dist-packages/PyQt5/QtWidgets.abi3.so (
> + 0x3a581c)  [0x7f199bf1181c]
>   /lib/x86_64-linux-gnu/libQt5Widgets.so.5 ( QWidget::event(QEvent*)  
> + 0x20e )  [0x7f199b6674ce]
>   /usr/lib/python3/dist-packages/PyQt5/QtWidgets.abi3.so (
> + 0x3ac443)  [0x7f199bf18443]
>   /lib/x86_64-linux-gnu/libQt5Widgets.so.5 (
> QApplicationPrivate::notify_helper(QObject*, QEvent*)  + 0x7f  ) 
> [0x7f199b6256bf]
>   /usr/lib/python3/dist-packages/PyQt5/QtWidgets.abi3.so (
> + 0x3bd8ae)  [0x7f199bf298ae]
>   /lib/x86_64-linux-gnu/libQt5Core.so.5 (
> QCoreApplication::notifyInternal2(QObject*, QEvent*)  + 0x12a ) 
> [0x7f199e8f5aba]
>   /lib/x86_64-linux-gnu/libQt5Widgets.so.5 (
> QWidgetPrivate::sendPaintEvent(QRegion const&)  + 0x36  ) 
> [0x7f199b65f516]
>   /lib/x86_64-linux-gnu/libQt5Widgets.so.5 (
> QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint
> const&, QFlags, QPainter*,
> QWidgetRepaintManager*)  + 0x7d2 )  [0x7f199b65fd42]
>   /lib/x86_64-linux-gnu/libQt5Widgets.so.5 (
> QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList
> const&, int, 

Bug#1008956: marked as done (tex-common: Something in package "tex-common" causes dpkg to exit with exit code -1)

[Debian Bug Tracking System]

Your message dated Thu, 7 Apr 2022 00:01:50 +0200
with message-id <2f669f53-8a26-6280-566a-4ee80e97a...@web.de>
and subject line Re: Bug#1008956: tex-common: Something in package "tex-common" 
causes dpkg to exit with exit code -1
has caused the Debian Bug report #1008956,
regarding tex-common: Something in package "tex-common" causes dpkg to exit 
with exit code -1
to be marked as done.

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

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


-- 
1008956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tex-common
Version: 6.16
Severity: grave
Justification: renders package unusable

Dear Maintainer,

(This is my first foray into bug reporting on a Linux distro, so if I make any 
mistakes, let me know!)

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

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

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

Preface regarding my system:
-
My system is a Lenovo ThinkPad W530, Type 2447; but with 32 GB RAM. This is why 
I have set APT to hold any packages matching the following critieria:
1) "*nvidia*"
2) "*cuda*"
I have the "nvidia-tesla-418-driver" package(s) installed, and I don't want 
anything else breaking it, so I have this held. I'm unsure if this is a cause 
of the error or not.
=


Prompt #1: What led up to the situation?
-
I went to install Blender and all the suggested / recommended packages so I 
could have the maximum funcionality out of the program. I used "apt install 
blender --install-suggests --install-recommends" (That last switch may be 
incorrect, if so, substibute the correct one there, I can't recall right now.)
=

Prompt #2 / #3: What exactly did you do (or not do) that was effective (or 
ineffective) / What was the outcome of this action?
---
I noticed the error that dpkg reported: exit code -1, and the package 
"tex-common". I saw that it made a error report with the name "fmtutil.", but I thought that perhaps it was a fluke brought on by the mammoth 
number of packages I had it installing.

I ran "dpkg --configure tex-common" to see, and the same error happened. I 
looked in the error file it generated, and it was really long, and quite 
frankly, I couldn't follow it. 
(I don't think it'll let me attach it to this report; this is the second time 
I've typed this due to a ironic error in reportbug: it failed to write the 
header in the bug report, and the file failed to attach there.)

Oddly, neither APT or dpkg report any broken deps with this erroring package; 
they just try to reconfigure it every time any action is performed with them, 
and Blender seems to be working fine? However, I doubt it's all functioning, 
since parts of the package are not configured.
===

Prompt #4: What outcome did you expect instead?

The package to not be stuck in a limbo of installed but not configured.


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

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

Versions of packages tex-common depends on:
ii  dpkg  1.20.9
ii  ucf   3.0043

tex-common recommends no packages.

Versions of packages tex-common suggests:
pn  debhelper  

Versions of packages texlive-base depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  libpaper-utils 1.1.28+b1
ii  sensible-utils 0.0.14
ii  texlive-binaries   2020.20200327.54578-7
ii  ucf3.0043
ii  xdg-utils  1.1.3-4.1

Versions of packages texlive-base 

Bug#1008956: tex-common: Something in package "tex-common" causes dpkg to exit with exit code -1

[Ashleigh Moore]

Well, if the /tmp was full, would it have been able to generate the error 
logs in there? I did run the dpkg configure command like 4 or 5 times, and 
every time, it made a report..


Ashleigh Moore
amo...@ashleighhost.net
[Sent using Alpine for Linux]

On Wed, 6 Apr 2022, Hilmar Preuße wrote:


Date: Wed, 6 Apr 2022 16:27:21
From: Hilmar Preuße 
To: Ashleigh Moore 
Cc: 1008...@bugs.debian.org
Subject: Re: Bug#1008956: tex-common: Something in package "tex-common" causes
 dpkg to exit with exit code -1

On 4/6/22 18:49, Ashleigh Moore wrote:

Hi,


Well uh, this is embarrassing, but apparently it fixed itself overnight.
And since the machine rebooted since then, I no longer have the tmp
files it made. I suppose if I have this occur again, I'll let you guys
know?

I am so sorry if this was a waste of your time..


Maybe the /tmp file system was full. I'd close the ticket for now. Would
this be OK?

Hilmar
--
Testmail

Bug#1008956: tex-common: Something in package "tex-common" causes dpkg to exit with exit code -1

[amoore]

Oh, okay, that makes sense then. Go ahead and close it, if it happens 
again, I'll let you know.


Ashleigh Moore
amo...@ashleighhost.net
[Sent using Alpine for Linux]

On Wed, 6 Apr 2022, Hilmar Preuße wrote:


Date: Wed, 6 Apr 2022 16:38:44
From: Hilmar Preuße 
To: Ashleigh Moore 
Cc: 1008...@bugs.debian.org
Subject: Re: Bug#1008956: tex-common: Something in package "tex-common" causes
 dpkg to exit with exit code -1

On 4/6/22 23:34, Ashleigh Moore wrote:

Hi,


Well, if the /tmp was full, would it have been able to generate the
error logs in there? I did run the dpkg configure command like 4 or 5
times, and every time, it made a report..


Maybe there was enough space for the logs, but not for the format files,
which should have been generated in that step...

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

Bug#1008956: tex-common: Something in package "tex-common" causes dpkg to exit with exit code -1

[Hilmar Preuße]

On 4/6/22 23:34, Ashleigh Moore wrote:

Hi,


Well, if the /tmp was full, would it have been able to generate the
error logs in there? I did run the dpkg configure command like 4 or 5
times, and every time, it made a report..


Maybe there was enough space for the logs, but not for the format files,
which should have been generated in that step...

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

Bug#1008956: tex-common: Something in package "tex-common" causes dpkg to exit with exit code -1

[Hilmar Preuße]

On 4/6/22 23:34, Ashleigh Moore wrote:

Hi,


Well, if the /tmp was full, would it have been able to generate the
error logs in there? I did run the dpkg configure command like 4 or 5
times, and every time, it made a report..


Maybe there was enough space for the logs, but not for the format files,
which should have been generated in that step...

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

Bug#1002221: marked as done (apt-dpkg-ref: FTBFS: dvips: DVI file can't be opened: apt-dpkg-ref.dvi: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 21:29:53 +
with message-id 
and subject line Bug#1009072: Removed package(s) from unstable
has caused the Debian Bug report #1002221,
regarding apt-dpkg-ref: FTBFS: dvips: DVI file can't be opened: 
apt-dpkg-ref.dvi: No such file or directory
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.)


-- 
1002221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apt-dpkg-ref
Version: 5.3.2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> /<>/make-docs
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in 
> scripts instead.
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in 
> scripts instead.
> This is SBCL 2.1.11.debian, an implementation of ANSI Common Lisp.
> More information about SBCL is available at .
> 
> SBCL is free software, provided as is, with absolutely no warranty.
> It is mostly in the public domain; some portions are provided under
> BSD-style licenses.  See the CREDITS and COPYING files in the
> distribution for more information.
> * INTERLEAVE
> * REFERENCE-GUIDE-LATEX
> * REFERENCE-GUIDE-HTML
> * APT-DPKG-REF
> * OUTPUT-DOCUMENT
> * NIL
> * NIL
> * /usr/bin/which: this version of `which' is deprecated; use `command -v' in 
> scripts instead.
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in 
> scripts instead.
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in 
> scripts instead.
> This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian) 
> (preloaded format=latex)
>  restricted \write18 enabled.
> entering extended mode
> (./apt-dpkg-ref.tex
> LaTeX2e <2021-11-15> patch level 1
> L3 programming layer <2021-11-22>
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2021/10/04 v1.4n Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/latin1.def))
> (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-dvips.def
> ! Argument of < has an extra }.
>  
> \par 
> l.133 >
>> ~
> ? 
> ! Emergency stop.
>  
> \par 
> l.133 >
>> ~
> No pages of output.
> Transcript written on apt-dpkg-ref.log.
> This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> (./apt-dpkg-ref.tex
> LaTeX2e <2021-11-15> patch level 1
> L3 programming layer <2021-11-22>
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2021/10/04 v1.4n Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/latin1.def))
> (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def
> ! Argument of < has an extra }.
>  
> \par 
> l.167 >
>> ~
> ? 
> ! Emergency stop.
>  
> \par 
> l.167 >
>> ~
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on apt-dpkg-ref.log.
> This is dvips(k) 2021.1 (TeX Live 2022/dev)  Copyright 2021 Radical Eye 
> Software (www.radicaleye.com)
> dvips: DVI file can't be opened: apt-dpkg-ref.dvi: No such file or directory
> make[1]: *** [debian/rules:7: execute_after_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/apt-dpkg-ref_5.3.2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you 

Bug#936638: marked as done (googlefontdirectory-tools: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 21:27:28 +
with message-id 
and subject line Bug#1008804: Removed package(s) from unstable
has caused the Debian Bug report #936638,
regarding googlefontdirectory-tools: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
936638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:googlefontdirectory-tools
Version: 20120309.1-1.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

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

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

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

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + 
src:googlefontdirectory-tools

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

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

Dear submitter,

as the package googlefontdirectory-tools has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1008804

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1008791: marked as done (Should googlefontdirectory-tools be removed?)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 21:27:28 +
with message-id 
and subject line Bug#1008804: Removed package(s) from unstable
has caused the Debian Bug report #1008791,
regarding Should googlefontdirectory-tools be removed?
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.)


-- 
1008791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: googlefontdirectory-tools
Version: 20120309.1-1.1
Severity: serious

Your package came up as a candidate for removal from Debian:

- Still depends on Python 2 and thus removed from testing since 2019
- Last maintainer upload in 2015

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 20120309.1-1.1+rm

Dear submitter,

as the package googlefontdirectory-tools has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1008804

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1008956: tex-common: Something in package "tex-common" causes dpkg to exit with exit code -1

[Hilmar Preuße]

On 4/6/22 18:49, Ashleigh Moore wrote:

Hi,


Well uh, this is embarrassing, but apparently it fixed itself overnight.
And since the machine rebooted since then, I no longer have the tmp
files it made. I suppose if I have this occur again, I'll let you guys
know?

I am so sorry if this was a waste of your time..


Maybe the /tmp file system was full. I'd close the ticket for now. Would
this be OK?

Hilmar
--
Testmail

Bug#937940: marked as done (python-nemu: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 21:24:53 +
with message-id 
and subject line Bug#1008273: Removed package(s) from unstable
has caused the Debian Bug report #937940,
regarding python-nemu: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
937940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-nemu
Version: 0.3.1-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

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

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

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

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:python-nemu

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

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

Dear submitter,

as the package python-nemu has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1008273

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#966722: marked as done (broctl: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 21:26:26 +
with message-id 
and subject line Bug#1008701: Removed package(s) from unstable
has caused the Debian Bug report #936241,
regarding broctl: Unversioned Python removal in sid/bullseye
to be marked as done.

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

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


-- 
936241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:broctl
Version: 1.4-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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

Dear submitter,

as the package broctl has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1008701

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#936241: marked as done (broctl: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 21:26:26 +
with message-id 
and subject line Bug#1008701: Removed package(s) from unstable
has caused the Debian Bug report #936241,
regarding broctl: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
936241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:broctl
Version: 1.4-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

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

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

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

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:broctl

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

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

Dear submitter,

as the package broctl has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1008701

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1008543: marked as done (gnome-shell-extension-disconnect-wifi: does not declare compatibility with GNOME Shell 42)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 21:25:54 +
with message-id 
and subject line Bug#1008664: Removed package(s) from unstable
has caused the Debian Bug report #1008543,
regarding gnome-shell-extension-disconnect-wifi: does not declare compatibility 
with GNOME Shell 42
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.)


-- 
1008543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-disconnect-wifi
Version: 29-1
Severity: normal
Tags: bookworm sid fixed-upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-42

The metadata.json for this extension doesn't declare compatibility with
GNOME 42. This seems to have been fixed in upstream git (not tested).

gnome-shell 42 is in experimental and will be entering unstable soon,
at which point this will become a RC bug.

During the GNOME Shell 42 transition, this extension will be removed from
testing if it continues to be incompatible.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 29-1+rm

Dear submitter,

as the package gnome-shell-extension-disconnect-wifi has just been removed from 
the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1008664

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1009043: marked as done (dpkg-fsys-usrunmess abuses "Protected: yes" status)

[Debian Bug Tracking System]

Your message dated Wed, 6 Apr 2022 22:56:19 +0200
with message-id 
and subject line Re: Bug#1009043: dpkg-fsys-usrunmess abuses "Protected: yes" 
status
has caused the Debian Bug report #1009043,
regarding dpkg-fsys-usrunmess abuses "Protected: yes" status
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.)


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

The dpkg-fsys-usrunmess program installs a dpkg-fsys-usrunmess package 
which maliciously abuses the Protected and Conflicts/Replaces/Provides 
fields to prevent installing again the usrmerge package:

https://git.dpkg.org/cgit/dpkg/dpkg.git/commit?id=abd3a064ef8a9004e7ff2c9e5841e507487130ac

This is dpkg's own changelog about the Protected field:

This field is intended to make it possible to move several of the
current packages marked as Essential, so that they can be removed on
installations where these do not make sense being installed.

Protected packages have some of the properties of Essential, but not
all. These are intended to be used mostly for packages that are involved
in booting the system.

Which is clearly not what is happening here.

-- 
ciao,
Marco


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.21.0

On Wed, 2022-04-06 at 15:12:57 +0200, Marco d'Itri wrote:
> Package: dpkg
> Version: 1.21.0
> Severity: serious

> The dpkg-fsys-usrunmess program installs a dpkg-fsys-usrunmess package 
> which maliciously abuses the Protected and Conflicts/Replaces/Provides 
> fields to prevent installing again the usrmerge package:

… No.

  #1008780
  https://wiki.debian.org/Teams/Dpkg/Spec/ProtectedField--- End Message ---

Bug#1008747: mercurial: FTBFS with Python 3.10 as default

[Julien Cristau]

Control: tag -1 upstream

On Thu, Mar 31, 2022 at 07:27:51PM +0200, Graham Inggs wrote:
> As can be seen on reproducible builds [1], mercurial FTBFS with Python
> 3.10 as the default version.  I've copied what I hope is the relevant
> part of the log below.
> 
> This appears to be due to the following appearing in the output of some tests:
> 
> DeprecationWarning: The distutils package is deprecated and slated for
> removal in Python 3.12.
> 
That's one of them, but there's a bunch more :(
Working on it...

Cheers,
Julien

> [1] https://tests.reproducible-builds.org/debian/rb-pkg/mercurial.html
> 
> 
> Failed test-hghave.t: output changed
> Failed test-https.t: output changed
> Failed test-parseindex.t: output changed
> Failed test-patchbomb-tls.t: output changed
> Failed test-run-tests.t: output changed
> # Ran 885 tests, 80 skipped, 5 failed.

Processed: Re: Bug#1008747: mercurial: FTBFS with Python 3.10 as default

[Debian Bug Tracking System]

Processing control commands:

> tag -1 upstream
Bug #1008747 [src:mercurial] mercurial: FTBFS with Python 3.10 as default
Added tag(s) upstream.

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

Bug#999182: perforate: diff for NMU version 1.2-5.2

[Eriberto]

Em qua., 6 de abr. de 2022 às 16:09, Reuben Thomas  escreveu:
>
> On Wed, 6 Apr 2022 at 18:15, Joao Eriberto Mota Filho  
> wrote:
>>
>> Control: tags 999182 + patch
>> Control: tags 999182 + pending
>>
>> Dear maintainer,
>>
>> I've prepared an NMU for perforate (versioned as 1.2-5.2) and uploaded it
>> to DELAYED/1 (a decreased time because the package is set as LowNMU, but
>> 1 day because I prefer to put a delay time).
>
>
> Thanks for this, Eriberto!
>
> Actually, I could do with some help with perforate. I am trying to update it 
> *and* change the package name to "finddup", as a) there isn't a binary called 
> perforate, which is confusing; and b) the zum utility (which does the 
> "perforation") isn't actually that useful on modern systems. I believe most 
> users are interested in finddup. I've also added "findcore" to find core 
> files.
>
> The current version of the package upstream is at 
> https://github.com/rrthomas/finddup/
>
> I've made attempts to upload it as a new package in 2018 and 2021 and failed 
> each time (for perfectly good reasons).
>
> If there's anything you could do to help get the new upstream version into 
> Debian, that would be fantastic.
>
> --
> https://rrt.sc3d.org

Hi Reuben,

Sorry, but I don't wish to have a major link with this package. My
intention is to do a simple NMU.

Good luck.

Regards,

Eriberto

Bug#1009073: virglrenderer: CVE-2022-0135: out-of-bounds write in read_transfer_data()

[Salvatore Bonaccorso]

Source: virglrenderer
Version: 0.8.2-5
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for virglrenderer.

CVE-2022-0135[0]:
| out-of-bounds write in read_transfer_data()

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-2022-0135
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0135
[1] https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/654
[2] 
https://gitlab.freedesktop.org/virgl/virglrenderer/-/commit/95e581fd181b213c2ed7cdc63f2abc03eaaa77ec

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1008650: marked as done (python3-unbound: Cannot install because of Python dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 19:51:16 +
with message-id 
and subject line Bug#1008641: fixed in unbound 1.13.1-1.1
has caused the Debian Bug report #1008641,
regarding python3-unbound: Cannot install because of Python dependencies
to be marked as done.

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

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


-- 
1008641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-unbound
Version: 1.13.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

The following packages have unmet dependencies:
 python3-unbound : Depends: python3 (< 3.10) but 3.10.4-1 is to be installed
E: Unable to correct problems, you have held broken packages.

Indeed, Python version on sid is:

% python3 --version
Python 3.10.4

But:

% apt-cache show python3-unbound
Package: python3-unbound
Source: unbound
Version: 1.13.1-1
Installed-Size: 394
Maintainer: unbound packagers 
Architecture: armhf
Depends: python3 (<< 3.10), python3 (>= 3.9~), python3:any, libc6 (>= 2.28), 
libunbound8 (>= 1.9.0)
...

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armhf (armv7l)

Kernel: Linux 4.14.269 (SMP w/2 CPU threads)
Locale: LANG=C, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-unbound depends on:
ii  libc62.33-7
ii  libunbound8  1.13.1-1
ii  python3  3.10.4-1

python3-unbound recommends no packages.

python3-unbound suggests no packages.
--- End Message ---
--- Begin Message ---
Source: unbound
Source-Version: 1.13.1-1.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated unbound 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: Wed, 06 Apr 2022 21:37:02 +0200
Source: unbound
Architecture: source
Version: 1.13.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: unbound packagers 
Changed-By: Sebastian Ramacher 
Closes: 1008641
Changes:
 unbound (1.13.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Rico Tzschichholz ]
   * Cherry-pick upstream commits for Python 3.10 compatibility (Closes:
 #1008641)
Checksums-Sha1:
 8d1a59befa215444f1ef6870e6e9f84ba577124f 3019 unbound_1.13.1-1.1.dsc
 b15d06c475636e3e137408517bcffb0d3f2cb671 22064 unbound_1.13.1-1.1.debian.tar.xz
Checksums-Sha256:
 ae5bb96c9b75509b69dce31ab88b04eeec6659aba638eeda268dd2ee6e3181d6 3019 
unbound_1.13.1-1.1.dsc
 ee672b9e4b44f2dbd5598c2ec7c927f02d3aa12ce1f462c63767b9b38972adba 22064 
unbound_1.13.1-1.1.debian.tar.xz
Files:
 71aef8a067096b7d873a2a7190043b50 3019 net optional unbound_1.13.1-1.1.dsc
 02ca6d154ed4c9127b399abf8954b64f 22064 net optional 
unbound_1.13.1-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmJN7a4ACgkQafL8UW6n
GZOFRg//dhZ/p/z4WsA78QIgkZGfNbW/3vrRFGNQOwwqZFGJ4PHW1ki3nRiS5iHz
KfaB+0p4v1Hfjeq9tTbicYOPswzOoQPblkWHEFZdlu1wp+vjnWMpKV34QJzdx8IW
U0nVc/XDX8wagFXSKGqKKy4pvbpVeoRFcRXEjc5b/0dLy2yjTHa6zzpdRxYmRKfA
IuYRiBvrGUPVomTPcFsJdUQyWq7/ZdENuZbEjgAjh/pTO8UKkiro07zxwjSqMb/7
AHK5BsXFEPQM60ABndKtKFXmjFk8nd7SWdI8bVUrz/mjQnOtHYGRwOOna6wN+w/0
ZiwulAfQ4P6NGm7XIzij6KgNYhM1uPTsfz4clN08/q6E7a35n9GVT5/1jJzFytt+
XKcH0ZKV19/c6JRexkUqsdy43wJF1rPzPgysh1Drq1FSKC8PyS+O53FQhRC9AewY
KZfGwzgdZ2rqh3vbC9DG2SU0cCRggVJ5+z5EF6A38xyQrnTZyyOkxQfFPNlOxJLI
c9RCeFtovS8VcnCR14BeFLP7rln7Gi+gpObJKiACpxKKDQfAADHltjcEm8LMKqBy

Bug#1008641: marked as done (unbound: FTBFS: ./pythonmod/pythonmod.c:338: undefined reference to `_Py_fopen')

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 19:51:16 +
with message-id 
and subject line Bug#1008641: fixed in unbound 1.13.1-1.1
has caused the Debian Bug report #1008641,
regarding unbound: FTBFS: ./pythonmod/pythonmod.c:338: undefined reference to 
`_Py_fopen'
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.)


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

unbound FTBFS:

libtool: link: ( cd ".libs" && rm -f "libunbound.la" && ln -s 
"../libunbound.la" "libunbound.la" )
./libtool --tag=CC --mode=link gcc   -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/python3.10 -DSRCDIR=. -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -pthread -I/usr/include/google -Wl,--as-needed 
-Wl,-z,relro -Wl,-z,now -o unbound acl_list.lo cachedump.lo daemon.lo 
shm_main.lo remote.lo stats.lo unbound.lo worker.lo  dns.lo infra.lo rrset.lo 
dname.lo msgencode.lo as112.lo msgparse.lo msgreply.lo packed_rrset.lo 
iterator.lo iter_delegpt.lo iter_donotq.lo iter_fwd.lo iter_hints.lo 
iter_priv.lo iter_resptype.lo iter_scrub.lo iter_utils.lo localzone.lo mesh.lo 
modstack.lo view.lo outbound_list.lo alloc.lo config_file.lo configlexer.lo 
configparser.lo fptr_wlist.lo edns.lo locks.lo log.lo mini_event.lo module.lo 
net_help.lo random.lo rbtree.lo regional.lo rtt.lo dnstree.lo lookup3.lo 
lruhash.lo slabhash.lo tcp_conn_limit.lo timehist.lo tube.lo winsock_event.lo 
autotrust.lo val_anchor.lo rpz.lo validator.lo val_kcache.lo val_kentry.lo 
val_neg.lo val_nsec3.lo val_nsec.lo val_secalgo.lo val_sigcrypt.lo val_utils.lo 
dns64.lo cachedb.lo redis.lo authzone.lo edns-subnet.lo subnetmod.lo 
addrtree.lo subnet-whitelist.lo pythonmod.lo pythonmod_utils.lo  dnstap.lo 
dnstap.pb-c.lo dnstap_fstrm.lo dtstream.lo respip.lo netevent.lo 
listen_dnsport.lo outside_network.lo ub_event.lo keyraw.lo sbuffer.lo 
wire2str.lo parse.lo parseutil.lo rrdef.lo str2wire.lo strlcat.lo strlcpy.lo 
arc4random.lo arc4random_uniform.lo arc4_lock.lo   -lssl -lprotobuf-c -levent 
-L/usr/lib/x86_64-linux-gnu -L/usr/lib/python3.10 -lpython3.10  -lsystemd 
-lcrypto 
libtool: link: gcc -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/python3.10 -DSRCDIR=. -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I/usr/include/google -Wl,--as-needed -Wl,-z -Wl,relro 
-Wl,-z -Wl,now -o unbound .libs/acl_list.o .libs/cachedump.o .libs/daemon.o 
.libs/shm_main.o .libs/remote.o .libs/stats.o .libs/unbound.o .libs/worker.o 
.libs/dns.o .libs/infra.o .libs/rrset.o .libs/dname.o .libs/msgencode.o 
.libs/as112.o .libs/msgparse.o .libs/msgreply.o .libs/packed_rrset.o 
.libs/iterator.o .libs/iter_delegpt.o .libs/iter_donotq.o .libs/iter_fwd.o 
.libs/iter_hints.o .libs/iter_priv.o .libs/iter_resptype.o .libs/iter_scrub.o 
.libs/iter_utils.o .libs/localzone.o .libs/mesh.o .libs/modstack.o .libs/view.o 
.libs/outbound_list.o .libs/alloc.o .libs/config_file.o .libs/configlexer.o 
.libs/configparser.o .libs/fptr_wlist.o .libs/edns.o .libs/locks.o .libs/log.o 
.libs/mini_event.o .libs/module.o .libs/net_help.o .libs/random.o 
.libs/rbtree.o .libs/regional.o .libs/rtt.o .libs/dnstree.o .libs/lookup3.o 
.libs/lruhash.o .libs/slabhash.o .libs/tcp_conn_limit.o .libs/timehist.o 
.libs/tube.o .libs/winsock_event.o .libs/autotrust.o .libs/val_anchor.o 
.libs/rpz.o .libs/validator.o .libs/val_kcache.o .libs/val_kentry.o 
.libs/val_neg.o .libs/val_nsec3.o .libs/val_nsec.o .libs/val_secalgo.o 
.libs/val_sigcrypt.o .libs/val_utils.o .libs/dns64.o .libs/cachedb.o 
.libs/redis.o .libs/authzone.o .libs/edns-subnet.o .libs/subnetmod.o 
.libs/addrtree.o .libs/subnet-whitelist.o .libs/pythonmod.o 
.libs/pythonmod_utils.o .libs/dnstap.o .libs/dnstap.pb-c.o .libs/dnstap_fstrm.o 
.libs/dtstream.o .libs/respip.o .libs/netevent.o .libs/listen_dnsport.o 
.libs/outside_network.o .libs/ub_event.o .libs/keyraw.o .libs/sbuffer.o 
.libs/wire2str.o .libs/parse.o .libs/parseutil.o .libs/rrdef.o .libs/str2wire.o 
.libs/strlcat.o .libs/strlcpy.o .libs/arc4random.o .libs/arc4random_uniform.o 
.libs/arc4_lock.o  -lssl -lprotobuf-c -levent -L/usr/lib/x86_64-linux-gnu 
-L/usr/lib/python3.10 -lpython3.10 -lsystemd -lcrypto -pthread 
/usr/bin/ld: .libs/pythonmod.o: in function `pythonmod_init':
./pythonmod/pythonmod.c:338: undefined reference to `_Py_fopen'
/usr/bin/ld: 

Bug#1008641: unbound: diff for NMU version 1.13.1-1.1

[Sebastian Ramacher]

Dear maintainer,

since this bug currently blocks the python3.10-default transition, I've
prepared an NMU for unbound (versioned as 1.13.1-1.1). The diff is
attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru unbound-1.13.1/debian/changelog unbound-1.13.1/debian/changelog
--- unbound-1.13.1/debian/changelog	2021-02-09 23:53:57.0 +0100
+++ unbound-1.13.1/debian/changelog	2022-04-06 21:37:02.0 +0200
@@ -1,3 +1,13 @@
+unbound (1.13.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Rico Tzschichholz ]
+  * Cherry-pick upstream commits for Python 3.10 compatibility (Closes:
+#1008641)
+
+ -- Sebastian Ramacher   Wed, 06 Apr 2022 21:37:02 +0200
+
 unbound (1.13.1-1) unstable; urgency=medium
 
   * New upstream version 1.13.1
diff -Nru unbound-1.13.1/debian/patches/python3.10-2.patch unbound-1.13.1/debian/patches/python3.10-2.patch
--- unbound-1.13.1/debian/patches/python3.10-2.patch	1970-01-01 01:00:00.0 +0100
+++ unbound-1.13.1/debian/patches/python3.10-2.patch	2022-04-06 21:35:02.0 +0200
@@ -0,0 +1,26 @@
+From 92d01d82658ffc3992e4468472d3c8c080f8b16c Mon Sep 17 00:00:00 2001
+From: Victor Stinner 
+Date: Tue, 16 Feb 2021 11:11:06 +0100
+Subject: [PATCH] Fix #426: Replace _Py_fopen() with fopen() in pythonmod.c
+
+The private _Py_fopen() function has been removed in Python 3.10.
+
+Fix build on Python 3.10.
+---
+ doc/Changelog | 1 +
+ pythonmod/pythonmod.c | 2 +-
+ 2 files changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/pythonmod/pythonmod.c b/pythonmod/pythonmod.c
+index 040ff7051..6e60d02fe 100644
+--- a/pythonmod/pythonmod.c
 b/pythonmod/pythonmod.c
+@@ -338,7 +338,7 @@ int pythonmod_init(struct module_env* env, int id)
+PyFileObject = PyFile_FromString((char*)pe->fname, "r");
+script_py = PyFile_AsFile(PyFileObject);
+ #else
+-   script_py = _Py_fopen(pe->fname, "r");
++   script_py = fopen(pe->fname, "r");
+ #endif
+if (script_py == NULL)
+{
diff -Nru unbound-1.13.1/debian/patches/python3.10.patch unbound-1.13.1/debian/patches/python3.10.patch
--- unbound-1.13.1/debian/patches/python3.10.patch	1970-01-01 01:00:00.0 +0100
+++ unbound-1.13.1/debian/patches/python3.10.patch	2022-04-06 21:35:02.0 +0200
@@ -0,0 +1,101 @@
+From e0d426ebb10653a78bf5c4053198f6ac19bfcd3e Mon Sep 17 00:00:00 2001
+From: "W.C.A. Wijngaards" 
+Date: Tue, 9 Feb 2021 10:38:55 +0100
+Subject: [PATCH] - Fix for Python 3.9, no longer use deprecated functions of  
+ PyEval_CallObject (now PyObject_Call), PyEval_InitThreads (now   none),
+ PyParser_SimpleParseFile (now Py_CompileString).
+
+---
+ doc/Changelog  |  5 +
+ libunbound/python/libunbound.i |  6 +
+ pythonmod/pythonmod.c  | 41 ++
+ 3 files changed, 52 insertions(+)
+
+diff --git a/libunbound/python/libunbound.i b/libunbound/python/libunbound.i
+index a23c45b9c..ab244a6fb 100644
+--- a/libunbound/python/libunbound.i
 b/libunbound/python/libunbound.i
+@@ -916,7 +916,13 @@ int _ub_resolve_async(struct ub_ctx* ctx, char* name, int rrtype, int rrclass, v
+   struct cb_data* id;
+   id = (struct cb_data*) iddata;
+   arglist = Py_BuildValue("(OiO)",id->data,status, SWIG_NewPointerObj(SWIG_as_voidptr(result), SWIGTYPE_p_ub_result, 0 |  0 ));   // Build argument list
++#if PY_MAJOR_VERSION <= 2 || (PY_MAJOR_VERSION == 3 && PY_MINOR_VERSION < 9)
++  /* for python before 3.9 */
+   fresult = PyEval_CallObject(id->func,arglist); // Call Python
++#else
++  /* for python 3.9 and newer */
++  fresult = PyObject_Call(id->func,arglist,NULL);
++#endif
+   Py_DECREF(id->func);
+   Py_DECREF(id->data);
+   free(id);
+diff --git a/pythonmod/pythonmod.c b/pythonmod/pythonmod.c
+index 9006429ef..040ff7051 100644
+--- a/pythonmod/pythonmod.c
 b/pythonmod/pythonmod.c
+@@ -299,7 +299,10 @@ int pythonmod_init(struct module_env* env, int id)
+   PyImport_AppendInittab(SWIG_name, (void*)SWIG_init);
+ #endif
+   Py_Initialize();
++#if PY_MAJOR_VERSION <= 2 || (PY_MAJOR_VERSION == 3 && PY_MINOR_VERSION <= 6)
++  /* initthreads only for python 3.6 and older */
+   PyEval_InitThreads();
++#endif
+   SWIG_init();
+   mainthr = PyEval_SaveThread();
+}
+@@ -354,6 +357,8 @@ int pythonmod_init(struct module_env* env, int id)
+/* TODO: deallocation of pe->... if an error occurs */
+ 
+if (PyRun_SimpleFile(script_py, pe->fname) < 0) {
++#if PY_MAJOR_VERSION <= 2 || (PY_MAJOR_VERSION == 3 && PY_MINOR_VERSION < 9)
++  /* for python before 3.9 */
+   log_err("pythonmod: can't parse Python script %s", pe->fname);
+   /* print the error to logs too, run it again */
+   fseek(script_py, 0, SEEK_SET);
+@@ -369,9 +374,45 @@ int pythonmod_init(struct module_env* env, int id)
+   /* ignore the NULL return of _node, it is NULL due to the parse failure
+* that we are expecting */
+   (void)PyParser_SimpleParseFile(script_py, 

Bug#1008689: getfem++: diff for NMU version 5.3+dfsg1-4.1

[Sebastian Ramacher]

On 2022-04-06 20:16:53 +0200, Sebastian Ramacher wrote:
> Control: tags 1008689 + patch
> 
> Dear maintainer,
> 
> as this issues blocks the ongoing python3.10-default transition, I've
> prepared an NMU for getfem++ (versioned as 5.3+dfsg1-4.1). The diff is
> attached to this message.
> 
> Cheers
> -- 
> Sebastian Ramacher

> diff -Nru getfem++-5.3+dfsg1/debian/changelog 
> getfem++-5.3+dfsg1/debian/changelog
> --- getfem++-5.3+dfsg1/debian/changelog   2021-12-18 21:13:11.0 
> +0100
> +++ getfem++-5.3+dfsg1/debian/changelog   2022-04-06 20:02:23.0 
> +0200
> @@ -1,3 +1,13 @@
> +getfem++ (5.3+dfsg1-4.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +
> +  [ Graham Inggs ]
> +  * Check success of distutils import by return code rather
> +than by stderr to avoid FTBFS with Python 3.10 (Closes: #1008689)
> +
> + -- Sebastian Ramacher   Wed, 06 Apr 2022 20:02:23 
> +0200
> +
>  getfem++ (5.3+dfsg1-4) unstable; urgency=medium
>  
>* Team upload.
> diff -Nru getfem++-5.3+dfsg1/debian/control getfem++-5.3+dfsg1/debian/control
> --- getfem++-5.3+dfsg1/debian/control 2021-12-18 21:13:11.0 +0100
> +++ getfem++-5.3+dfsg1/debian/control 2022-04-06 20:02:19.0 +0200
> @@ -1,5 +1,6 @@
>  Source: getfem++
> -Maintainer: Debian Science Team 
> 
> +Maintainer: Ubuntu Developers 
> +XSBC-Original-Maintainer: Debian Science Team 
> 

Sorry, I missed that change when reviewing the diff. This is reverted in
-4.2.

Cheers

>  Uploaders: Konstantinos Poulios 
>  Section: libs
>  Priority: optional
> diff -Nru getfem++-5.3+dfsg1/debian/patches/python3.10.patch 
> getfem++-5.3+dfsg1/debian/patches/python3.10.patch
> --- getfem++-5.3+dfsg1/debian/patches/python3.10.patch1970-01-01 
> 01:00:00.0 +0100
> +++ getfem++-5.3+dfsg1/debian/patches/python3.10.patch2022-04-06 
> 20:02:19.0 +0200
> @@ -0,0 +1,16 @@
> +Description: check success of import by return code rather than by stderr
> +Origin: upstream, 
> https://github.com/autoconf-archive/autoconf-archive/commit/883a2abd5af5c96be894d5ef7ee6e9a2b8e64307
> +Author: Igor Gnatenko 
> +Last-Update: 2017-03-14
> +
> +--- a/m4/ac_python_devel.m4
>  b/m4/ac_python_devel.m4
> +@@ -98,7 +98,7 @@
> + #
> + AC_MSG_CHECKING([for the distutils Python package])
> + ac_distutils_result=`$PYTHON -c "import distutils" 2>&1`
> +-if test -z "$ac_distutils_result"; then
> ++if test $? -eq 0; then
> + AC_MSG_RESULT([yes])
> + else
> + AC_MSG_RESULT([no])
> diff -Nru getfem++-5.3+dfsg1/debian/patches/series 
> getfem++-5.3+dfsg1/debian/patches/series
> --- getfem++-5.3+dfsg1/debian/patches/series  2021-12-18 21:13:11.0 
> +0100
> +++ getfem++-5.3+dfsg1/debian/patches/series  2022-04-06 20:02:19.0 
> +0200
> @@ -8,3 +8,4 @@
>  fix_python3_tests_8dcd729f.patch
>  scripts_python3.patch
>  fix_blas_interface.patch
> +python3.10.patch




-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1008752: avifile: autopkgtest regression on armhf: Bus error

[Paul Gevers]

Hi,

On 06-04-2022 21:30, Paul Gevers wrote:

On 06-04-2022 21:26, Paul Gevers wrote:

but ffmpeg succeeds.


But this is interesting in its output:
[libx264 @ 0x1a181a0] using cpu capabilities: ARMv6 NEON


https://www.baeldung.com/linux/proc-cpuinfo-flags#3-neon says we 
shouldn't look for "neon", but for asimd, which indeed is in the 
features set of this CPU (we run armhf lxc on amd64 host, so the CPU is 
actually 64 bits).


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008752: avifile: autopkgtest regression on armhf: Bus error

[Paul Gevers]

Hi

On 06-04-2022 21:26, Paul Gevers wrote:

but ffmpeg succeeds.


But this is interesting in its output:
[libx264 @ 0x1a181a0] using cpu capabilities: ARMv6 NEON

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1009055: Just crashes

[Alexandru Băluț]

It has been fixed a few months ago.
https://gitlab.gnome.org/GNOME/pitivi/-/issues/2571 We should be able to do
a release soon.

On Wed, Apr 6, 2022 at 5:27 PM  wrote:

> Package: pitivi
> Version: 2021.05-1
> Severity: grave
>
>
> Just launching it after install gives:
>
> Missing soft dependency:
> - GSound not found on the system
> -> enables sound notifications when rendering is complete
> Traceback (most recent call last):
>   File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py",
> line 135, in do_startup
> loggable.init('PITIVI_DEBUG', enable_color, enable_crack_output)
>   File "/usr/lib/x86_64-linux-
> gnu/pitivi/python/pitivi/utils/loggable.py", line 651, in init
> add_limited_log_handler(print_handler)
>   File "/usr/lib/x86_64-linux-
> gnu/pitivi/python/pitivi/utils/loggable.py", line 738, in
> add_limited_log_handler
> if not isinstance(func, collections.Callable):
> AttributeError: module 'collections' has no attribute 'Callable'
> Traceback (most recent call last):
>   File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py",
> line 203, in do_activate
> self.create_main_window()
>   File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py",
> line 209, in create_main_window
> self.gui = MainWindow(self)
>   File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/mainwindow.py",
> line 108, in __init__
> self.app.settings.connect("useDarkThemeChanged",
> AttributeError: 'NoneType' object has no attribute 'connect'
>
>
> Cheers,
>
> J.Puydt
>
>

Bug#1008752: avifile: autopkgtest regression on armhf: Bus error

[Paul Gevers]

Hi,

On 06-04-2022 08:48, Ying-Chun Liu (PaulLiu) wrote:

I'm not sure if you have extra time.
But I think you are correct. We might need to report the bug to ffmpeg.

I'm not sure if we can simplify the test.
Like just run "ffplay test_raw.avi" or "ffmpeg -i test_raw.avi out.mp4" 
to see if it has the bus error as well.


ffplay fails with:
error: XDG_RUNTIME_DIR not set in the environment.
Could not initialize SDL - No available video device
(Did you set the DISPLAY variable?)

but ffmpeg succeeds. But then, I also had to install quite some packages 
to install ffmpeg. Maybe something is needed?


  libavdevice58 libcdio-cdda2 libcdio-paranoia2 libcdio19 libdc1394-25 
libdecor-0-0
  libdrm-amdgpu1 libdrm-nouveau2 libdrm-radeon1 libgbm1 libgl1 
libgl1-mesa-dri
  libglapi-mesa libglvnd0 libglx-mesa0 libglx0 libllvm13 libopenal-data 
libopenal1
  libsdl2-2.0-0 libsensors-config libsensors5 libsndio7.0 libusb-1.0-0 
libvulkan1
  libwayland-client0 libwayland-cursor0 libwayland-egl1 
libwayland-server0 libxcb-dri2-0
  libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxcb-shape0 libxcb-sync1 
libxcb-xfixes0
  libxcursor1 libxi6 libxinerama1 libxkbcommon0 libxrandr2 
libxshmfence1 libxss1 libxv1

  libz3-4 x11-common xkb-data

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008689: marked as done (getfem++: FTBFS with Python 3.10)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 19:05:54 +
with message-id 
and subject line Bug#1008689: fixed in getfem++ 5.3+dfsg1-4.1
has caused the Debian Bug report #1008689,
regarding getfem++: FTBFS with Python 3.10
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.)


-- 
1008689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: getfem++
Version: 5.3+dfsg1-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org

getfem++ FTBFS:

checking for the distutils Python package... no
configure: error: cannot import Python module "distutils".
Please check your Python installation. The error was:
:1: DeprecationWarning: The distutils package is deprecated and slated 
for removal in Python 3.12. Use setuptools or check PEP 632 for potential 
alternatives


See
https://buildd.debian.org/status/fetch.php?pkg=getfem%2B%2B=amd64=5.3%2Bdfsg1-4%2Bb1=1648454264=0

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: getfem++
Source-Version: 5.3+dfsg1-4.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated getfem++ 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: Wed, 06 Apr 2022 20:02:23 +0200
Source: getfem++
Architecture: source
Version: 5.3+dfsg1-4.1
Distribution: unstable
Urgency: medium
Maintainer: Ubuntu Developers 
Changed-By: Sebastian Ramacher 
Closes: 1008689
Changes:
 getfem++ (5.3+dfsg1-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Graham Inggs ]
   * Check success of distutils import by return code rather
 than by stderr to avoid FTBFS with Python 3.10 (Closes: #1008689)
Checksums-Sha1:
 551be931b716e55bff5e804ffa19b749e940 2458 getfem++_5.3+dfsg1-4.1.dsc
 3e2f9cf53e5425ef1c5e1d2ed46f03f415d180e5 20996 
getfem++_5.3+dfsg1-4.1.debian.tar.xz
Checksums-Sha256:
 69d883e3a49a57bc0b35f48b9964cc2cebcdbc126a42872682d94df007a11c62 2458 
getfem++_5.3+dfsg1-4.1.dsc
 21be12b59b5b7b321ae27982b56e85db470f531c72cbe11165bd65ae8e354cfe 20996 
getfem++_5.3+dfsg1-4.1.debian.tar.xz
Files:
 66963302f6f8ef254c60ab5f1ef22071 2458 libs optional getfem++_5.3+dfsg1-4.1.dsc
 2513462dc30f71cfd7b6874b9d35 20996 libs optional 
getfem++_5.3+dfsg1-4.1.debian.tar.xz
Original-Maintainer: Debian Science Team 


-BEGIN PGP SIGNATURE-

iQIyBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmJN2SMACgkQafL8UW6n
GZOdyw/4srRDb0+puKo20+FOgnie8wctsC/zosN9b/WmKlFBQU89uRKtt/UZZKQc
fyJur+r3rZZFugX2DH49rfaV3gOw9bK5ilbTurJTHRWjOkLwsvaBIEQprlsQElOV
pZSI7YgLpYuJoP0+PV6WqmtdgyZSeNx1MpHpQF0Ka3DxWQ4m7BE7EW1obV0Sdjm3
lFg1PLKt/8cwKhnXyZsUK6Rq1mkpt6L51CqpoZJ1/qQJRLuaKUK0qpV8MRmk0gsP
kyoa+XPT6wc+RGBdzIZpOFqePyapQdDpsYUbOiGLJ8eGIMluljLk/VCcHt/gX8Y4
brIser3uAEXQ4SkBSoZs1vfBk62VA8f/ua/56Il4C8lQP0M/kl+D5rT6B/l5kFmF
mSkpyMZg/lgHp3aS4X8SfLGNM3qJIgfw/WzUVhSAC/siseCHmgABMU/eFNbjw+Z3
LpbML3tuQAnKXuTkwFnMtKAnaa6zfJkt1a34ia+TFzp1mPd/gp5e0E5sIhO8oLTC
rRR54rwQIGDPxlCAtSyM2lxNKFBtHbEvxsWD5ZDQxvIwodAxYI7l+tiQp5Epogfj
Rh52XTlcSnCboMmH+c3Ydl/pkFDZb/FF4QnQkA2V61JtlQ5U1/fQozF9ruWHIOjy
OcOU7zXXrlq9mxUVOChAeGiovv/wLoEQo3bFwjcSxPSAMQzRBA==
=2ssg
-END PGP SIGNATURE End Message ---

Bug#1009063: src:gst-plugins-bad1.0-contrib: fails to migrate to testing for too long: doesn't build on buildds

[Paul Gevers]

Source: gst-plugins-bad1.0-contrib
Version: 1.18.4-3
Severity: serious
Control: close -1 1.20.0-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:gst-plugins-bad1.0-contrib has been trying 
to migrate for 61 days [2]. Hence, I am filing this bug. As this package 
is in contrib, it probably can't be build on the buildds (I forgot the 
details) and this package has never been build there. For migration, I 
think the binaries need to be uploaded manually (however sad that is).


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=gst-plugins-bad1.0-contrib



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:gst-plugins-bad1.0-contrib: fails to migrate to testing for too long: doesn't build on buildds

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.20.0-1
Bug #1009063 [src:gst-plugins-bad1.0-contrib] src:gst-plugins-bad1.0-contrib: 
fails to migrate to testing for too long: doesn't build on buildds
The source 'gst-plugins-bad1.0-contrib' and version '1.20.0-1' do not appear to 
match any binary packages
Marked as fixed in versions gst-plugins-bad1.0-contrib/1.20.0-1.
Bug #1009063 [src:gst-plugins-bad1.0-contrib] src:gst-plugins-bad1.0-contrib: 
fails to migrate to testing for too long: doesn't build on buildds
Marked Bug as done

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

Processed: getfem++: diff for NMU version 5.3+dfsg1-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1008689 + patch
Bug #1008689 [src:getfem++] getfem++: FTBFS with Python 3.10
Added tag(s) patch.

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

Bug#1008689: getfem++: diff for NMU version 5.3+dfsg1-4.1

[Sebastian Ramacher]

Control: tags 1008689 + patch

Dear maintainer,

as this issues blocks the ongoing python3.10-default transition, I've
prepared an NMU for getfem++ (versioned as 5.3+dfsg1-4.1). The diff is
attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru getfem++-5.3+dfsg1/debian/changelog getfem++-5.3+dfsg1/debian/changelog
--- getfem++-5.3+dfsg1/debian/changelog	2021-12-18 21:13:11.0 +0100
+++ getfem++-5.3+dfsg1/debian/changelog	2022-04-06 20:02:23.0 +0200
@@ -1,3 +1,13 @@
+getfem++ (5.3+dfsg1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Graham Inggs ]
+  * Check success of distutils import by return code rather
+than by stderr to avoid FTBFS with Python 3.10 (Closes: #1008689)
+
+ -- Sebastian Ramacher   Wed, 06 Apr 2022 20:02:23 +0200
+
 getfem++ (5.3+dfsg1-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru getfem++-5.3+dfsg1/debian/control getfem++-5.3+dfsg1/debian/control
--- getfem++-5.3+dfsg1/debian/control	2021-12-18 21:13:11.0 +0100
+++ getfem++-5.3+dfsg1/debian/control	2022-04-06 20:02:19.0 +0200
@@ -1,5 +1,6 @@
 Source: getfem++
-Maintainer: Debian Science Team 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: Debian Science Team 
 Uploaders: Konstantinos Poulios 
 Section: libs
 Priority: optional
diff -Nru getfem++-5.3+dfsg1/debian/patches/python3.10.patch getfem++-5.3+dfsg1/debian/patches/python3.10.patch
--- getfem++-5.3+dfsg1/debian/patches/python3.10.patch	1970-01-01 01:00:00.0 +0100
+++ getfem++-5.3+dfsg1/debian/patches/python3.10.patch	2022-04-06 20:02:19.0 +0200
@@ -0,0 +1,16 @@
+Description: check success of import by return code rather than by stderr
+Origin: upstream, https://github.com/autoconf-archive/autoconf-archive/commit/883a2abd5af5c96be894d5ef7ee6e9a2b8e64307
+Author: Igor Gnatenko 
+Last-Update: 2017-03-14
+
+--- a/m4/ac_python_devel.m4
 b/m4/ac_python_devel.m4
+@@ -98,7 +98,7 @@
+ 	#
+ 	AC_MSG_CHECKING([for the distutils Python package])
+ 	ac_distutils_result=`$PYTHON -c "import distutils" 2>&1`
+-	if test -z "$ac_distutils_result"; then
++	if test $? -eq 0; then
+ 		AC_MSG_RESULT([yes])
+ 	else
+ 		AC_MSG_RESULT([no])
diff -Nru getfem++-5.3+dfsg1/debian/patches/series getfem++-5.3+dfsg1/debian/patches/series
--- getfem++-5.3+dfsg1/debian/patches/series	2021-12-18 21:13:11.0 +0100
+++ getfem++-5.3+dfsg1/debian/patches/series	2022-04-06 20:02:19.0 +0200
@@ -8,3 +8,4 @@
 fix_python3_tests_8dcd729f.patch
 scripts_python3.patch
 fix_blas_interface.patch
+python3.10.patch


signature.asc
Description: PGP signature

Bug#1008956: tex-common: Something in package "tex-common" causes dpkg to exit with exit code -1

[Ashleigh Moore]

Well uh, this is embarrassing, but apparently it fixed itself overnight. 
And since the machine rebooted since then, I no longer have the tmp 
files it made. I suppose if I have this occur again, I'll let you guys know?


I am so sorry if this was a waste of your time..

--
Ashleigh / Victor Moore
+1 (205)-747-7958
amo...@ashleighhost.net

Bug#998484: marked as done (schleuder: FTBFS: ERROR: Test "ruby3.0" failed: # GPGME::Error::NoSecretKey:)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 17:21:15 +
with message-id 
and subject line Bug#998484: fixed in schleuder 4.0.2-1
has caused the Debian Bug report #998484,
regarding schleuder: FTBFS: ERROR: Test "ruby3.0" failed:   # 
GPGME::Error::NoSecretKey:
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.)


-- 
998484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: schleuder
Version: 3.6.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>   # GPGME::Error::NoSecretKey:
>   #   No secret key
>   #   ./lib/schleuder/mail/message.rb:29:in `setup'
> 
> Finished in 3 minutes 25.6 seconds (files took 1.3 seconds to load)
> 487 examples, 32 failures
> 
> Failed examples:
> 
> rspec ./spec/schleuder/integration/keywords_spec.rb:1560 # user sends keyword 
> x-fetch-key with URL
> rspec ./spec/schleuder/integration/keywords_spec.rb:3025 # user sends keyword 
> x-delete-key with not distinctly matching argument
> rspec ./spec/schleuder/integration/keywords_spec.rb:1678 # user sends keyword 
> x-fetch-key with fingerprint
> rspec ./spec/schleuder/integration/keywords_spec.rb:1717 # user sends keyword 
> x-fetch-key with fingerprint of unchanged key
> rspec ./spec/schleuder/integration/keywords_spec.rb:1482 # user sends keyword 
> x-fetch-key with email address
> rspec ./spec/schleuder/errors_spec.rb:46 # Errors ::KeywordAdminOnly shows 
> sensible string in response to to_s()
> rspec ./spec/schleuder/errors_spec.rb:55 # Errors ::ListdirProblem shows 
> sensible string in response to to_s()
> rspec ./spec/schleuder/errors_spec.rb:37 # Errors ::KeyAdduidFailed shows 
> sensible string in response to to_s()
> rspec ./spec/schleuder/errors_spec.rb:32 # Errors ::DecryptionFailed shows 
> sensible string in response to to_s()
> rspec ./spec/schleuder/errors_spec.rb:65 # Errors ::MessageTooBig shows 
> sensible string in response to to_s()
> rspec ./spec/schleuder/errors_spec.rb:28 # Errors ::LoadingListSettingsFailed 
> shows sensible string in response to to_s()
> rspec ./spec/schleuder/errors_spec.rb:41 # Errors ::KeyGenerationFailed shows 
> sensible string in response to to_s()
> rspec ./spec/schleuder/errors_spec.rb:50 # Errors ::ListNotFound shows 
> sensible string in response to to_s()
> rspec ./spec/schleuder/errors_spec.rb:70 # Errors ::TooManyKeys shows 
> sensible string in response to to_s()
> rspec ./spec/schleuder/errors_spec.rb:60 # Errors ::MessageEmpty shows 
> sensible string in response to to_s()
> rspec ./spec/schleuder/integration/filters_spec.rb:5 # running filters 
> .max_message_size bounces to big mails
> rspec ./spec/schleuder-api-daemon/requests/keys_spec.rb:26 # keys via api 
> check does check keys with authorization
> rspec ./spec/schleuder/unit/list_spec.rb:512 # Schleuder::List#fetch_keys 
> fetches one key by fingerprint
> rspec ./spec/schleuder/unit/list_spec.rb:529 # Schleuder::List#fetch_keys 
> fetches one key by URL
> rspec ./spec/schleuder/unit/list_spec.rb:546 # Schleuder::List#fetch_keys 
> fetches one key by email address
> rspec ./spec/schleuder/unit/list_spec.rb:563 # Schleuder::List#fetch_keys 
> does not import non-self-signatures if gpg >= 2.1.15; or else sends a warning
> rspec ./spec/schleuder/unit/list_spec.rb:447 # Schleuder::List#check_keys 
> adds a message if a key is invalid
> rspec ./spec/schleuder/unit/list_spec.rb:440 # Schleuder::List#check_keys 
> adds a message if a key is disabled
> rspec ./spec/schleuder/unit/list_spec.rb:433 # Schleuder::List#check_keys 
> adds a message if a key is revoked
> rspec ./spec/schleuder/unit/list_spec.rb:412 # Schleuder::List#check_keys 
> adds a message if a key expires in two weeks or less
> rspec ./spec/schleuder/integration/cli_spec.rb:220 # cli #refresh_keys warns 
> about file system permissions if it was run as root
> rspec ./spec/schleuder/integration/cli_spec.rb:152 # cli #refresh_keys 
> updates keys from the keyserver
> rspec ./spec/schleuder/integration/cli_spec.rb:175 # cli #refresh_keys 
> updates keys from the keyserver for only a specific list
> rspec ./spec/schleuder/integration/cli_spec.rb:201 # cli #refresh_keys 
> reports errors from refreshing keys
> rspec ./spec/schleuder/runner_spec.rb:238 # Schleuder::Runner#run mails not 
> encrypted to the list key handles a mail which was encrypted to a passphrase 
> and returns 

Bug#999182: perforate: diff for NMU version 1.2-5.2

[Joao Eriberto Mota Filho]

Control: tags 999182 + patch
Control: tags 999182 + pending

Dear maintainer,

I've prepared an NMU for perforate (versioned as 1.2-5.2) and uploaded it
to DELAYED/1 (a decreased time because the package is set as LowNMU, but
1 day because I prefer to put a delay time).

Regards,

Eriberto

diff -u perforate-1.2/debian/changelog perforate-1.2/debian/changelog
--- perforate-1.2/debian/changelog
+++ perforate-1.2/debian/changelog
@@ -1,3 +1,11 @@
+perforate (1.2-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: added missing targets build-arch and build-indep.
+(Closes: #999182)
+
+ -- Joao Eriberto Mota Filho   Wed, 06 Apr 2022 13:52:52 
-0300
+
 perforate (1.2-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u perforate-1.2/debian/rules perforate-1.2/debian/rules
--- perforate-1.2/debian/rules
+++ perforate-1.2/debian/rules
@@ -45,4 +45,6 @@
 
 binary-indep: build
 
-.PHONY: clean build binary binary-arch binary-indep
+build-arch: build
+build-indep: build
+.PHONY: clean build build-arch build-indep binary binary-arch binary-indep

Processed: perforate: diff for NMU version 1.2-5.2

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#965400: aa3d: diff for NMU version 1.0-8.1

[Marcos Talau]

Control: tags 965400 + patch
Control: tags 965400 + pending

Dear maintainer,

I've prepared an NMU for aa3d (versioned as 1.0-8.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -u aa3d-1.0/debian/control aa3d-1.0/debian/control
--- aa3d-1.0/debian/control
+++ aa3d-1.0/debian/control
@@ -2,7 +2,7 @@
 Section: graphics
 Priority: optional
 Maintainer: Uwe Hermann 
-Build-Depends: cdbs, debhelper (>= 5)
+Build-Depends: debhelper-compat (= 13)
 Standards-Version: 3.8.0
 Homepage: http://aa-project.sourceforge.net/aa3d/
 
diff -u aa3d-1.0/debian/rules aa3d-1.0/debian/rules
--- aa3d-1.0/debian/rules
+++ aa3d-1.0/debian/rules
@@ -1,12 +1,15 @@
 #!/usr/bin/make -f
 
-DEB_INSTALL_MANPAGES_aa3d := debian/aa3d.1
+PACKAGE = aa3d
 
-include /usr/share/cdbs/1/class/makefile.mk
-include /usr/share/cdbs/1/rules/debhelper.mk
-include /usr/share/cdbs/1/rules/simple-patchsys.mk
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
-install/aa3d::
-	install aa3d $(CURDIR)/debian/aa3d/usr/bin
-	install -m 0644 logo pyramid $(CURDIR)/debian/aa3d/usr/share/aa3d
+%:
+	dh $@
 
+execute_after_dh_auto_install:
+	install $(PACKAGE) debian/$(PACKAGE)/usr/bin
+	install -m 0644 logo pyramid debian/$(PACKAGE)/usr/share/$(PACKAGE)
+
+override_dh_installman:
+	dh_installman debian/$(PACKAGE).1
diff -u aa3d-1.0/debian/changelog aa3d-1.0/debian/changelog
--- aa3d-1.0/debian/changelog
+++ aa3d-1.0/debian/changelog
@@ -1,3 +1,18 @@
+aa3d (1.0-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Using new DH level format. Consequently:
+- debian/compat: Remove.
+- debian/control: Change from 'debhelper' to 'debhelper-compat' in
+  Build-Depends field and bump level to 13.
+- Closes: #965400.
+  * Drop CDBS in favor of the debhelper to allow the build system to use
+DH level greater than 11. Consequently:
+- debian/control: Remove no longer need cdbs from Build-Depends field.
+- debian/rules: Change from CDBS to DH.
+
+ -- Marcos Talau   Tue, 05 Apr 2022 22:51:33 -0300
+
 aa3d (1.0-8) unstable; urgency=low
 
   * Add 'Depends: ${misc:Depends}' (lintian).
reverted:
--- aa3d-1.0/debian/compat
+++ aa3d-1.0.orig/debian/compat
@@ -1 +0,0 @@
-5

Processed: aa3d: diff for NMU version 1.0-8.1

[Debian Bug Tracking System]

Processing control commands:

> tags 965400 + patch
Bug #965400 [src:aa3d] aa3d: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
Bug #965401 [src:aa3d] aa3d: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
Added tag(s) patch.
Added tag(s) patch.
> tags 965400 + pending
Bug #965400 [src:aa3d] aa3d: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
Bug #965401 [src:aa3d] aa3d: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
Added tag(s) pending.
Added tag(s) pending.

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

Bug#1007858: [Pkg-javascript-devel] Bug#1007858: Bug#1007858: node-lodash: FTBFS with nodejs experimental/14.19.0

[Jonas Smedegaard]

Quoting Yadd (2022-04-06 18:12:30)
> On 19/03/2022 08:38, Yadd wrote:
> > On 19/03/2022 08:11, Yadd wrote:
> >> On 17/03/2022 19:21, Jérémy Lal wrote:
> >>> Source: node-lodash
> >>> Version: 4.17.21+dfsg+~cs8.31.196.20210220-2
> >>> Severity: important
> >>> Tags: ftbfs
> >>>
> >>> This package fails to rebuild. Build log is attached.
> >>
> >> The real problem comes from uglify-js call. Build works fine with 
> >> uglifyjs 2 (as required by node-locash/package.json) but fails with 
> >> uglify-js 3. Here is the real error:
> >>
> >>    error: JS_Parse_Error [SyntaxError]: Invalid flags supplied to 
> >> RegExp constructor 'node'
> >>    at JS_Parse_Error.get (eval at  
> >> (/build/node-lodash-wQJpO3/node-lodash-4.17.21+dfsg+~cs8.31.198.20210220/node_modules/uglify-js/tools/node.js:18:1),
> >>  
> >> :63:23)
> >>    at formatError (internal/util/inspect.js:1149:38)
> >>    at formatRaw (internal/util/inspect.js:919:14)
> >>    at formatValue (internal/util/inspect.js:774:10)
> >>    at formatProperty (internal/util/inspect.js:1660:11)
> >>    at formatRaw (internal/util/inspect.js:987:9)
> >>    at formatValue (internal/util/inspect.js:774:10)
> >>    at inspect (internal/util/inspect.js:319:10)
> >>    at formatWithOptionsInternal (internal/util/inspect.js:1979:40)
> >>    at formatWithOptions (internal/util/inspect.js:1861:10) {
> >>  filename: '0',
> >>  line: 1,
> >>  col: 0,
> >>  pos: 0
> > 
> > For now, I dropped internal minifier and pushed result to experimental. 
> > This may break some builds: minified files have to be generated separately.
> > 
> > Can someone else have a look at this ?
> 
> I'm unable to reproduce this failure in an up-to-date schroot, but build 
> fails in salsa CI [1], that's why I reopened this issue.
> 
> [1]: https://salsa.debian.org/js-team/node-lodash/-/jobs/2648172

Maybe check if upstream has a branch or pending MR with code to upgrade 
to UglifyJS v3?

If not, then maybe report the issue upstream?  UglifyJS v2 is pretty 
dead!


 - Jonas

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

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

signature.asc
Description: signature

Bug#1007858: [Pkg-javascript-devel] Bug#1007858: node-lodash: FTBFS with nodejs experimental/14.19.0

[Yadd]

On 19/03/2022 08:38, Yadd wrote:

On 19/03/2022 08:11, Yadd wrote:

On 17/03/2022 19:21, Jérémy Lal wrote:

Source: node-lodash
Version: 4.17.21+dfsg+~cs8.31.196.20210220-2
Severity: important
Tags: ftbfs

This package fails to rebuild. Build log is attached.


The real problem comes from uglify-js call. Build works fine with 
uglifyjs 2 (as required by node-locash/package.json) but fails with 
uglify-js 3. Here is the real error:


   error: JS_Parse_Error [SyntaxError]: Invalid flags supplied to 
RegExp constructor 'node'
   at JS_Parse_Error.get (eval at  
(/build/node-lodash-wQJpO3/node-lodash-4.17.21+dfsg+~cs8.31.198.20210220/node_modules/uglify-js/tools/node.js:18:1), 
:63:23)

   at formatError (internal/util/inspect.js:1149:38)
   at formatRaw (internal/util/inspect.js:919:14)
   at formatValue (internal/util/inspect.js:774:10)
   at formatProperty (internal/util/inspect.js:1660:11)
   at formatRaw (internal/util/inspect.js:987:9)
   at formatValue (internal/util/inspect.js:774:10)
   at inspect (internal/util/inspect.js:319:10)
   at formatWithOptionsInternal (internal/util/inspect.js:1979:40)
   at formatWithOptions (internal/util/inspect.js:1861:10) {
 filename: '0',
 line: 1,
 col: 0,
 pos: 0


For now, I dropped internal minifier and pushed result to experimental. 
This may break some builds: minified files have to be generated separately.


Can someone else have a look at this ?


I'm unable to reproduce this failure in an up-to-date schroot, but build 
fails in salsa CI [1], that's why I reopened this issue.


[1]: https://salsa.debian.org/js-team/node-lodash/-/jobs/2648172

Processed: tagging 1007858

[Debian Bug Tracking System]

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

> tags 1007858 + help
Bug #1007858 [src:node-lodash] node-lodash: FTBFS with nodejs 
experimental/14.19.0
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#1007829: [pkg-netfilter-team] Bug#1007829: arptables - Fails to install: Too many levels of symbolic links

[Alberto Molina Coballes]

Hi Thomas and thanks for resolving the bug.

A few days ago I tried to upload a new version fixing the bug, but it
was silently ignored. At the moment I'm very busy and I don't have
time to debug the problem by uploading packages to the archive, so
your help to solve the bug with a NMU is welcome :)

Alberto

Processed: found 1007858 in 4.17.21+dfsg+~cs8.31.198.20210220-2

[Debian Bug Tracking System]

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

> found 1007858 4.17.21+dfsg+~cs8.31.198.20210220-2
Bug #1007858 [src:node-lodash] node-lodash: FTBFS with nodejs 
experimental/14.19.0
Marked as found in versions node-lodash/4.17.21+dfsg+~cs8.31.198.20210220-2.
> thanks
Stopping processing here.

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

Bug#900821: Read aloud website and eBook with AI Website Reader app

[AI Website Reader]

How is it going?
We have just released AI Website Reader app to read aloud website/ebook with AI voice control 
Please check it out here:

Google Play: https://play.google.com/store/apps/details?id=com.aiwebsitereader

Thank you!
Sorry for any inconvenience. Please reply "Quit" to remove your email from our list.
P/S: Bonus Email Scanner app to hunt emails from phone: https://play.google.com/store/apps/details?id=com.emailscanner

Processed: severity of 1007858 is serious

[Debian Bug Tracking System]

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

> severity 1007858 serious
Bug #1007858 [src:node-lodash] node-lodash: FTBFS with nodejs 
experimental/14.19.0
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1005470: marked as done (pyparsing: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 15:38:34 +
with message-id 
and subject line Bug#1005470: fixed in pyparsing 3.0.7-2
has caused the Debian Bug report #1005470,
regarding pyparsing: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.10 3.9" returned exit code 13
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.)


-- 
1005470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyparsing
Version: 3.0.7-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> Running Sphinx v4.3.2
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 6 source files that are out of date
> updating environment: [new config] 6 added, 0 changed, 0 removed
> reading sources... [ 16%] CODE_OF_CONDUCT
> reading sources... [ 33%] HowToUsePyparsing
> reading sources... [ 50%] index
> reading sources... [ 66%] modules
> reading sources... [ 83%] pyparsing
> reading sources... [100%] whats_new_in_3_0_0
> 
> WARNING: invalid signature for autoclass 
> ('pyparsing::pyparsing_unicode.עִברִית')
> WARNING: don't know which module to import for autodocumenting 
> 'pyparsing::pyparsing_unicode.עִברִית' (try placing a "module" or 
> "currentmodule" directive in the document, or giving an explicit module name)
> WARNING: invalid signature for autoclass 
> ('pyparsing::pyparsing_unicode.देवनागरी')
> WARNING: don't know which module to import for autodocumenting 
> 'pyparsing::pyparsing_unicode.देवनागरी' (try placing a "module" or 
> "currentmodule" directive in the document, or giving an explicit module name)
> /<>/pyparsing/core.py:docstring of pyparsing.core.OneOrMore:6: 
> WARNING: Unexpected indentation.
> /<>/pyparsing/results.py:docstring of 
> pyparsing.results.ParseResults.List:11: WARNING: Unexpected indentation.
> /<>/pyparsing/results.py:docstring of 
> pyparsing.results.ParseResults.List:12: WARNING: Block quote ends without a 
> blank line; unexpected unindent.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.ParserElement.__add__:1: WARNING: Inline interpreted text or 
> phrase reference start-string without end-string.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.ParserElement.__call__:6: WARNING: Inline literal start-string 
> without end-string.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.ParserElement.__mul__:6: WARNING: Unexpected indentation.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.ParserElement.__mul__:8: WARNING: Block quote ends without a 
> blank line; unexpected unindent.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.ParserElement.create_diagram:5: WARNING: Unexpected 
> indentation.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.ParserElement.create_diagram:6: WARNING: Block quote ends 
> without a blank line; unexpected unindent.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.ParserElement.parse_string:11: WARNING: Inline interpreted 
> text or phrase reference start-string without end-string.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.ParserElement.parse_string:11: WARNING: Inline interpreted 
> text or phrase reference start-string without end-string.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.ParserElement.run_tests:9: WARNING: Unexpected indentation.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.ParserElement.run_tests:10: WARNING: Block quote ends without 
> a blank line; unexpected unindent.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.ParserElement.run_tests:9: WARNING: Unexpected indentation.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.ParserElement.run_tests:10: WARNING: Block quote ends without 
> a blank line; unexpected unindent.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.ParserElement.set_name:3: WARNING: Unexpected indentation.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.ParserElement.set_name:3: WARNING: Unexpected indentation.
> /<>/pyparsing/core.py:docstring of pyparsing.core.SkipTo:7: 
> WARNING: Unexpected indentation.
> /<>/pyparsing/core.py:docstring of pyparsing.core.SkipTo:9: 
> WARNING: Block quote ends without a blank line; unexpected unindent.
> /<>/pyparsing/core.py:docstring of 
> pyparsing.core.Suppress.__add__:1: WARNING: Inline interpreted text or 

Bug#1006004: marked as done (pyparsing: autopkgtest regression: can't open file '/tmp/autopkgtest-lxc.yvh1lz7q/downtmp/build.0Qk/src/unitTests.py)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 15:38:34 +
with message-id 
and subject line Bug#1006004: fixed in pyparsing 3.0.7-2
has caused the Debian Bug report #1006004,
regarding pyparsing: autopkgtest regression: can't open file 
'/tmp/autopkgtest-lxc.yvh1lz7q/downtmp/build.0Qk/src/unitTests.py
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.)


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

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


   passfail
pyparsing  from testing3.0.7-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=pyparsing

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyparsing/19310150/log.gz

python3: can't open file 
'/tmp/autopkgtest-lxc.yvh1lz7q/downtmp/build.0Qk/src/unitTests.py': 
[Errno 2] No such file or directory

autopkgtest [18:10:16]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pyparsing
Source-Version: 3.0.7-2
Done: Stuart Prescott 

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

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated pyparsing 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, 07 Apr 2022 01:23:34 +1000
Source: pyparsing
Architecture: source
Version: 3.0.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Stuart Prescott 
Closes: 1005470 1006004
Changes:
 pyparsing (3.0.7-2) unstable; urgency=medium
 .
   * Team upload.
   * Fix build time tests:
 - Fix missing Build-Depends on python3-pytest.
 - Copy files needed for tests into test location using pybuild
   (Closes: #1005470).
   * Fix autopkgtest tests:
 - Run the correct test command (Closes: #1006004).
 - Test against all supported interpreters.
 - Copy files needed for tests into test location.
   * Declare Breaks against old versions of translate-toolkit that are broken
 by new upstream version of pyparsing so they migrate together.
Checksums-Sha1:
 7c924f3cfbc7cc9adc66f8517674bae4fb64f0d8 2233 pyparsing_3.0.7-2.dsc
 f4a25e6526c9f2485fb9ed366dcbf21211b41abd 8392 pyparsing_3.0.7-2.debian.tar.xz
 82835666df8db99638beea61021737055e3241fe 8254 pyparsing_3.0.7-2_amd64.buildinfo
Checksums-Sha256:
 f30034e424f328eaf65d6b7c182808f9d95808184383af204c4ab7e8982b3831 2233 
pyparsing_3.0.7-2.dsc
 9f6ed6b3f9177ad00833777534226a40f9b57e229afc896e5b4d2fc8fe823d2f 8392 
pyparsing_3.0.7-2.debian.tar.xz
 72e89ac50ea4b358a8f209712b081f7af97b2adc91a28314a8fd21e0983fc946 8254 
pyparsing_3.0.7-2_amd64.buildinfo
Files:
 6c65a2e607a15343e9a7caee2aa4d8fd 2233 python optional pyparsing_3.0.7-2.dsc
 03fb7579b4016a9fc9d560c6ebbe485e 8392 python optional 
pyparsing_3.0.7-2.debian.tar.xz
 64e1d60d351aa3f59fd61b56f5821d10 8254 python optional 
pyparsing_3.0.7-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAmJNsU4ACgkQu8F+uxOW
8vcc0RAAi3+Yodhu/q/p/vqnEIevpTWjPN/L3ZhiTiYsU2cOk5mhx3LSCzr3lfkn
0vkQiotGsJ4FRWGYbekamLQXGXLHR1bsRwvaSbdx87CZpIKSJ9u2Jc1oqfQBhtm4
xi7PjYK/CFDwkITLbEJqswNw0DSP1tLMObaNmkbrr87c18S7+JZ1OCis7iKlqXRQ

Bug#1008799: marked as done (fife: FTBFS on mipsel)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 15:36:11 +
with message-id 
and subject line Bug#1008799: fixed in fife 0.4.2-4
has caused the Debian Bug report #1008799,
regarding fife: FTBFS on mipsel
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.)


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

fife FTBFS on mipsel:

make[3]: Entering directory '/<>/obj-mipsel-linux-gnu'
[  1%] Building CXX object 
CMakeFiles/_fife.dir/CMakeFiles/_fife.dir/fifePYTHON_wrap.cxx.o
/usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_FILESYSTEM_DYN_LINK 
-DBOOST_SYSTEM_DYN_LINK -DHAVE_OPENGL -DLOG_ENABLED -DTIXML_USE_STL 
-D_fife_EXPORTS -I/<>/obj-mipsel-linux-gnu 
-I/<>/engine/core -I/<> -I/usr/include/SDL2 
-I/usr/include/AL -I/usr/include/python3.10 -std=c++11 -fPIC -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g1 -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -Wno-error -O3 
-DNDEBUG -fPIC -MD -MT 
CMakeFiles/_fife.dir/CMakeFiles/_fife.dir/fifePYTHON_wrap.cxx.o -MF 
CMakeFiles/_fife.dir/CMakeFiles/_fife.dir/fifePYTHON_wrap.cxx.o.d -o 
CMakeFiles/_fife.dir/CMakeFiles/_fife.dir/fifePYTHON_wrap.cxx.o -c 
/<>/obj-mipsel-linux-gnu/CMakeFiles/_fife.dir/fifePYTHON_wrap.cxx
virtual memory exhausted: Cannot allocate memory
make[3]: *** [CMakeFiles/_fife.dir/build.make:79: 
CMakeFiles/_fife.dir/CMakeFiles/_fife.dir/fifePYTHON_wrap.cxx.o] Error 1

See
https://buildd.debian.org/status/fetch.php?pkg=fife=mipsel=0.4.2-3%2Bb1=1648798473=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: fife
Source-Version: 0.4.2-4
Done: Markus Koschany 

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated fife 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: Wed, 06 Apr 2022 16:24:36 +0200
Source: fife
Architecture: source
Version: 0.4.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Closes: 1008799
Changes:
 fife (0.4.2-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Adrian Bunk ]
   * debian/rules: Set CMAKE_CXX_FLAGS_RELEASE to avoid forcing -O3 on non-i386
 32bit
   * debian/rules: Disable all C++ debug info on mipsel
   * debian/rules: Don't force non-parallel building on non-i386 32bit.
 Available RAM is not an issue (2/3/4 GB address space limitation is).
 (Closes: #1008799)
 .
   [ Markus Koschany ]
   * Declare compliance with Debian Policy 4.6.0.
Checksums-Sha1:
 c443a85c31b34c20295e7d3f086839842164 2377 fife_0.4.2-4.dsc
 521c7f398b234c5ef8ff789d2b716d8b83df1f97 9512 fife_0.4.2-4.debian.tar.xz
 432531c64233117c1986752dda4918148f0ffe87 13423 fife_0.4.2-4_amd64.buildinfo
Checksums-Sha256:
 40514f6e5ae73e5859884a0270397a7234bb16ea73e09dfe01aaffe2d54f59f1 2377 
fife_0.4.2-4.dsc
 1bad441764dce52404d200f8abe70150184894531dfa2eaa02386521d5146ce8 9512 
fife_0.4.2-4.debian.tar.xz
 64bcac19c5022b57a823fcaa8f672fcd9c6cda1c82416337afd2cb4231b7394c 13423 
fife_0.4.2-4_amd64.buildinfo
Files:
 9e4e90f56eb4e971e7d836c9827f9593 2377 libdevel optional fife_0.4.2-4.dsc
 bf71742b386a636861d3204ca7682510 9512 libdevel optional 
fife_0.4.2-4.debian.tar.xz
 d8c7e8e7392cc802547a559efd4c87cc 13423 libdevel optional 
fife_0.4.2-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmJNrFZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkoU4QAIvqjvoGKSdJfIEIu/8LWn4KGo7BmXUXUrYc
vL4Yogs9MEmUfDqoUTlMZQfz0p65HvpDhGc1GFa5GKs7QEF1G5E2bDaa24i22CJg
ZKTETuILs11sceXj8xbdgEzcyc0BB7ZCJuREwF/iS2Jip/TWHxeWi3SskVgEeAaC

Processed: Bug#1006004 marked as pending in pyparsing

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1006004 [src:pyparsing] pyparsing: autopkgtest regression: can't open file 
'/tmp/autopkgtest-lxc.yvh1lz7q/downtmp/build.0Qk/src/unitTests.py
Added tag(s) pending.

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

Processed: Bug#1005470 marked as pending in pyparsing

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1005470 [src:pyparsing] pyparsing: FTBFS: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) pending.

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

Bug#1006004: marked as pending in pyparsing

[Stuart Prescott]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/pyparsing/-/commit/ec80583abcff6c6361d635624775a37e30ab61c2


Fix autopkgtest tests

- Use correct test command
- Exclude tests that need unpacakged 'railroad' module
- Test against all supported python interpreters

(Closes: #1006004)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1006004

Bug#1005470: marked as pending in pyparsing

[Stuart Prescott]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/pyparsing/-/commit/a6d1858b90f3f24e0c78f26d62cc68988fe5d87e


Fix build-time tests

- use pytest, consistent with upstream
- ensure that test data is available
- exclude 'diagrams' tests that require unpackaged railroad module

(Closes: #1005470)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005470

Bug#1005471: translate-toolkit: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[Stuart Prescott]

A fixed pyparsing has now been uploaded which should 
let pyparsing and translate-toolkit both migrate together. 
Hopefully.

-- 
Stuart Prescotthttp://www.nanonanonano.net/   
stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ 
stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 
7EBB 1396 F2F7

Bug#1009055: Just crashes

[julien . puydt]

Package: pitivi
Version: 2021.05-1
Severity: grave


Just launching it after install gives:

Missing soft dependency:
- GSound not found on the system
-> enables sound notifications when rendering is complete
Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py",
line 135, in do_startup
loggable.init('PITIVI_DEBUG', enable_color, enable_crack_output)
  File "/usr/lib/x86_64-linux-
gnu/pitivi/python/pitivi/utils/loggable.py", line 651, in init
add_limited_log_handler(print_handler)
  File "/usr/lib/x86_64-linux-
gnu/pitivi/python/pitivi/utils/loggable.py", line 738, in
add_limited_log_handler
if not isinstance(func, collections.Callable):
AttributeError: module 'collections' has no attribute 'Callable'
Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py",
line 203, in do_activate
self.create_main_window()
  File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py",
line 209, in create_main_window
self.gui = MainWindow(self)
  File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/mainwindow.py",
line 108, in __init__
self.app.settings.connect("useDarkThemeChanged",
AttributeError: 'NoneType' object has no attribute 'connect'


Cheers,

J.Puydt

Bug#1009054: Just crashes

[julien . puydt]

Package: openshot-qt
Version: 2.6.1+dfsg1-1
Severity: grave

I just installed the software, launched "openshot-qt" and got a crash.

I'll put the result of "openshot-qt 2>&1 |tee /tmp/log" at the end of
this mail.

Cheers,

J.Puydt

Here is /tmp/log:

Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
INFO app: 
INFO app: Wed Apr  6 17:13:25 2022
INFO app:   Starting new session  
INFO app: 
INFO app: OpenShot (version 2.6.1)
INFO app: 
INFO app: openshot-qt version: 2.6.1
INFO app: libopenshot version: 0.2.7
INFO app: platform: Linux-5.16.0-4-amd64-x86_64-with-glibc2.33
INFO app: processor: 
INFO app: machine: x86_64
INFO app: python version: 3.10.4
INFO app: qt5 version: 5.15.2
INFO app: pyqt5 version: 5.15.6
INFO project_data: Setting default profile to HD 720p 30 fps
INFO language: Qt Detected Languages: ['fr-FR']
INFO language: LANG Environment Variable: fr_FR.UTF-8
INFO language: LOCALE Environment Variable: 
INFO language: OpenShot Preference Language: Default
INFO app: Setting font to Cantarell
INFO logger_libopenshot: Connecting to libopenshot with debug port:
5556
INFO app: Setting custom dark theme
INFO ui_util: Initializing UI for MainWindow
INFO webkit: WebKit backend initializing
INFO thumbnail: Starting thumbnail server listening on port 55351
INFO transition_model: updating transitions model.
INFO effects_model: updating effects model.
INFO emoji_model: updating emoji model.
INFO version: Found current version: {'error_rate_stable': 0.16,
'trans_rate_unstable': 0.001, 'error_rate_unstable': 0.05,
'trans_rate_stable': 0.01, 'openshot_version': '2.6.1'}
INFO main_window: InitCacheSettings
INFO main_window: cache-mode: CacheMemory
INFO main_window: cache-limit-mb: 250
INFO main_window: Creating CacheMemory object with 262144000 byte limit
INFO preview_thread: QThread Start Method Invoked
ERROR main_window: Unhandled crash detected: linux-/lib/x86_64-linux-
gnu/libc.so.6 abort 0x112 [0x7ff285404546]
INFO main_window: updateStatusChanged
INFO main_window: recover_backup
INFO project_data: Setting default profile to HD 720p 30 fps
INFO preview_thread: player Position(): 1
INFO video_widget: Load: Set video widget display aspect ratio to:
1.777910232544
INFO video_widget: Set video widget pixel aspect ratio to: 1.0
INFO main_window: updateStatusChanged
INFO webkit: Registering objects with WebKit
qt.svg: Invalid path data; path truncated.
qt.svg: Invalid path data; path truncated.
qt.svg: Invalid path data; path truncated.
Unhandled Python exception
Caught signal 6 (SIGABRT)
 Unhandled Exception: Stack Trace 
  /lib/x86_64-linux-gnu/libc.so.6 ( abort 
+ 0x112 )  [0x7f199f905546]
  /lib/x86_64-linux-gnu/libQt5Core.so.5 ( 
+ 0x90b51)  [0x7f199e6d6b51]
  /usr/lib/python3/dist-packages/PyQt5/QtCore.abi3.so (   
+ 0xb5237)  [0x7f199ec4b237]
  /usr/lib/python3/dist-packages/PyQt5/sip.cpython-310-x86_64-linux-
gnu.so (   + 0x11363) 
[0x7f199c0d8363]
  /usr/lib/python3/dist-packages/PyQt5/QtWidgets.abi3.so (
+ 0x154b1d)  [0x7f199bcc0b1d]
  /usr/lib/python3/dist-packages/PyQt5/QtWidgets.abi3.so (
+ 0x3a581c)  [0x7f199bf1181c]
  /lib/x86_64-linux-gnu/libQt5Widgets.so.5 ( QWidget::event(QEvent*)  
+ 0x20e )  [0x7f199b6674ce]
  /usr/lib/python3/dist-packages/PyQt5/QtWidgets.abi3.so (
+ 0x3ac443)  [0x7f199bf18443]
  /lib/x86_64-linux-gnu/libQt5Widgets.so.5 (
QApplicationPrivate::notify_helper(QObject*, QEvent*)  + 0x7f  ) 
[0x7f199b6256bf]
  /usr/lib/python3/dist-packages/PyQt5/QtWidgets.abi3.so (
+ 0x3bd8ae)  [0x7f199bf298ae]
  /lib/x86_64-linux-gnu/libQt5Core.so.5 (
QCoreApplication::notifyInternal2(QObject*, QEvent*)  + 0x12a ) 
[0x7f199e8f5aba]
  /lib/x86_64-linux-gnu/libQt5Widgets.so.5 (
QWidgetPrivate::sendPaintEvent(QRegion const&)  + 0x36  ) 
[0x7f199b65f516]
  /lib/x86_64-linux-gnu/libQt5Widgets.so.5 (
QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint
const&, QFlags, QPainter*,
QWidgetRepaintManager*)  + 0x7d2 )  [0x7f199b65fd42]
  /lib/x86_64-linux-gnu/libQt5Widgets.so.5 (
QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList
const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*,
QWidgetRepaintManager*)  + 0x4f0 )  [0x7f199b661180]
  /lib/x86_64-linux-gnu/libQt5Widgets.so.5 (
QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint
const&, QFlags, QPainter*,
QWidgetRepaintManager*)  + 0x4ec )  [0x7f199b65fa5c]
  /lib/x86_64-linux-gnu/libQt5Widgets.so.5 (
QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList
const&, int, QRegion const&, QPoint const&,
QFlags, QPainter*,
QWidgetRepaintManager*)  + 0x4f0 )  [0x7f199b661180]
  

Bug#1004092: marked as done (swayidle FTBFS on 32bit)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 15:07:27 +
with message-id 
and subject line Bug#1004092: fixed in swayidle 1.7.1-2
has caused the Debian Bug report #1004092,
regarding swayidle FTBFS on 32bit
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.)


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

https://buildd.debian.org/status/logs.php?pkg=swayidle=1.7.1-1

...
FAILED: swayidle.p/main.c.o
cc -Iswayidle.p -I. -I.. -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 
-Wall -Winvalid-pch -Wextra -Werror -std=c11 -Wno-unused-parameter 
-Wno-unused-result -Wundef -Wvla '-DSYSCONFDIR="/etc"' -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MQ 
swayidle.p/main.c.o -MF swayidle.p/main.c.o.d -o swayidle.p/main.c.o -c 
../main.c
In file included from ../main.c:19:
../main.c: In function ‘load_config’:
../log.h:28:25: error: format ‘%lu’ expects argument of type ‘long unsigned 
int’, but argument 5 has type ‘size_t’ {aka ‘unsigned int’} [-Werror=format=]
   28 | _swayidle_log(verb, "[Line %d] " fmt, __LINE__, ##__VA_ARGS__)
  | ^~~~
../main.c:1007:25: note: in expansion of macro ‘swayidle_log’
 1007 | swayidle_log(LOG_ERROR, "Unexpected keyword 
\"%s\" in line %lu", line, lineno);
  | ^~~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
dh_auto_build: error: cd obj-i686-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v 
returned exit code 1
make: *** [debian/rules:11: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: swayidle
Source-Version: 1.7.1-2
Done: Birger Schacht 

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

Debian distribution maintenance software
pp.
Birger Schacht  (supplier of updated swayidle 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: Wed, 06 Apr 2022 16:37:30 +0200
Source: swayidle
Architecture: source
Version: 1.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Sway and related packages team 
Changed-By: Birger Schacht 
Closes: 1004092
Changes:
 swayidle (1.7.1-2) unstable; urgency=medium
 .
   * d/rules: Set -Wno-error=format (Closes: #1004092)
   * Drop filenamemangle option from d/watch
Checksums-Sha1:
 85eca29802065e594f5377ecadd82e47b85ad485 2046 swayidle_1.7.1-2.dsc
 c3c85e923a8b2827e5c802a7319e7f73848957ea 5056 swayidle_1.7.1-2.debian.tar.xz
 e0c6988f6c681f5758d9e4abfda5475ecb288ba2 6885 swayidle_1.7.1-2_amd64.buildinfo
Checksums-Sha256:
 fa0d0cb35bc699a333ab10b132ccbe6c451b8d12c48b0381be030183a947bd60 2046 
swayidle_1.7.1-2.dsc
 0d4f79c55a4eda4824d231d75b6e5d39c5b04fce91b3b72c3fe2e3e5b19574d0 5056 
swayidle_1.7.1-2.debian.tar.xz
 ec9f76a1d1d60aadbdcd0496c040f917e3d66be5b3f835e957d58cb26d434ca6 6885 
swayidle_1.7.1-2_amd64.buildinfo
Files:
 615637117bb7775dd7a091c7cb363b67 2046 x11 optional swayidle_1.7.1-2.dsc
 6aeb5893af014d7b5fbed6dea5dca623 5056 x11 optional 
swayidle_1.7.1-2.debian.tar.xz
 025175228867daae66fb2c58d0ccf6c1 6885 x11 optional 
swayidle_1.7.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEOvC8tnwmrEjOtOW8KgxdYPIEvbAFAmJNpskSHGJpcmdlckBk
ZWJpYW4ub3JnAAoJECoMXWDyBL2ww/MP/3lQ3wp6mJFtV72bPyAvRQPPGmG+WHjw
Zv4/y5NwcEMdkZcVJI62GRVDAyN8COX8WzBB2UczBqpAFEchPiQY/JME7IJfIKLD
ZPCdNG/2a+sRT9Ykg0WJ1VugfhafauZAds7ciit442Hu6UG6WgSEGjR054m06ds4
lWgoJJxNlQo1tIGiyLzwBv6WpQPjVFGgWenBvtfS/NP7vIapRp7AFVnJhTiyEKaY
UyD2IOqGiV3GcFDw2Ih3eCOCxbI75qUjVJBV+2HfdHAoECOxbC5EEkLOsIEjoB30
dkQfph3lQsSltu3+VZXY8uq4H1sqlc/UoL9XMUaVYTFgAXfy9PbnjFnNmkWrTQrv
vjmY3Boc6rbw428m/VxzcZfL12C+3bFxS/x1OuNiu+LF819kC7iGXwng5MGHSy5Q
HUoU1pYwXQL8WdyhHIddhA2JmppMEhBelja2Rj4lyja3dGts3dNaXCghQ3ApcCpJ
u0R0I17qrBvR14RVssyPBnsd1KRp0/bL6quXxf1q+eiKN6kEJy6XPKZ37eueA8rV
D9eNVF6VwVE/QtC4htbkRil5FN9nSkAYj5Qw0lfMmvOPyWZRBshWb09zHUMzLXbf

Bug#1006381: python3-mistune0: missing Conflicts+Replaces: python3-mistune or Breaks+Replaces: python3-mistune (<< 2.0.0-1+really2.0.0)

[Jonas Smedegaard]

Hi Pierre-Elliott,

Here's a friendly notice in case you were unaware of this bug#1006381 
blocking mistune0 from entering testing.


Kind regards,

 - Jonas

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

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

signature.asc
Description: signature

Bug#1009010: slop: maim: error while loading shared libraries: libslopy.so.7.5: cannot open shared object file: No such file or directory

[Antoine Beaupré]

On 2022-04-05 22:36:30, Axel Beckert wrote:
> Package: slop
> Version: 7.6-1
> Severity: serious
> Control: affects -1 maim
>
> Slop seems to provide a shared library without having a proper SONAME or
> ABI in the package name and bumping the library made at least "maim" to
> fail to work:
>
> maim: error while loading shared libraries: libslopy.so.7.5: cannot open 
> shared object file: No such file or directory
>
> From my point of view, it is an error of slop to provide a shared
> library but not having a proper library package with proper SONAME or
> ABI version in the package name.
>
> In case you disagree, please do not provide a shared library at all and
> do compile this library directly into the binary "slop".

I agree, this is a long-standing bug in the package, and a lintian
warning I have consistently (and incorrectly) ignored.

I would be happy to take whatever fix you think is best for this. The
package is in salsa.debian.org/debian and i'm LowNMU.

I think my main blocker is fixing this is that I am not super familiar
with shared libs packages. It also seems a little silly to have a shared
lib for something that's essentially called by other packages (although
now it seems that maim does use it as a shared lib).

The other problem is introducing a shared lib would make us go through a
round trip in NEW, but hopefully that should be trivial enough to be
fast.

Anyways, thanks for the bug report, and definitely something that needs
fixing. In the meantime I think a binNMU might fix this on maim's side,
right?

a.

-- 
The steel horse fills a gap in modern life, it is an answer not only to
its needs, but also to its aspirations.  It's quite certainly here to
stay.
 - Le Vélocipède Illustré, 1869

Bug#1009043: dpkg-fsys-usrunmess abuses "Protected: yes" status

[Marco d'Itri]

Package: dpkg
Version: 1.21.0
Severity: serious

The dpkg-fsys-usrunmess program installs a dpkg-fsys-usrunmess package 
which maliciously abuses the Protected and Conflicts/Replaces/Provides 
fields to prevent installing again the usrmerge package:

https://git.dpkg.org/cgit/dpkg/dpkg.git/commit?id=abd3a064ef8a9004e7ff2c9e5841e507487130ac

This is dpkg's own changelog about the Protected field:

This field is intended to make it possible to move several of the
current packages marked as Essential, so that they can be removed on
installations where these do not make sense being installed.

Protected packages have some of the properties of Essential, but not
all. These are intended to be used mostly for packages that are involved
in booting the system.

Which is clearly not what is happening here.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1009042: libtraceevent: FTBFS race condition on parallel build

[Felix Moessbauer]

Source: libtraceevent
Version: 1:1.5.1-1
Severity: serious
Tags: ftbfs upstream
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

the upstream version 1.5.1 has a race condition in the src/Makefile
which breaks the build sporadically.

This bug is hard to reproduce, but when running with sbuilder on a
machine with 16 cores, it appears quite consistently.

Attached a log from a failed build using sbuilder (from an internal
build server, not the official debian ones).
Please note, that the symbols that are missing vary from run to run.
A similar bug has already been reported for libtracefs (#1008722).
The root-cause might be the same, as the Makefiles of both projects
look quite similar.

Best regards,
Felix Moessbauer
Siemens AG

dh_makeshlibs -a
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libtraceevent1/DEBIAN/symbols doesn't match 
completely debian/libtraceevent1.symbols
--- debian/libtraceevent1.symbols (libtraceevent1_1:1.5.1-1_amd64)
+++ dpkg-gensymbolsJfsqcz   2022-04-01 12:59:36.848775612 +
@@ -146,15 +146,15 @@
tep_vprint@Base 1:1.3.0
tep_vwarning@Base 1:1.2.1
tep_warning@Base 1:1.2.1
- trace_seq_destroy@Base 5.4
- trace_seq_do_fprintf@Base 5.4
- trace_seq_do_printf@Base 5.4
- trace_seq_init@Base 5.4
- trace_seq_printf@Base 5.4
- trace_seq_putc@Base 5.4
- trace_seq_puts@Base 5.4
- trace_seq_reset@Base 5.4
- trace_seq_terminate@Base 5.4
- trace_seq_vprintf@Base 5.4
+#MISSING: 1:1.5.1-1# trace_seq_destroy@Base 5.4
+#MISSING: 1:1.5.1-1# trace_seq_do_fprintf@Base 5.4
+#MISSING: 1:1.5.1-1# trace_seq_do_printf@Base 5.4
+#MISSING: 1:1.5.1-1# trace_seq_init@Base 5.4
+#MISSING: 1:1.5.1-1# trace_seq_printf@Base 5.4
+#MISSING: 1:1.5.1-1# trace_seq_putc@Base 5.4
+#MISSING: 1:1.5.1-1# trace_seq_puts@Base 5.4
+#MISSING: 1:1.5.1-1# trace_seq_reset@Base 5.4
+#MISSING: 1:1.5.1-1# trace_seq_terminate@Base 5.4
+#MISSING: 1:1.5.1-1# trace_seq_vprintf@Base 5.4
vpr_stat@Base 5.4
#MISSING: 1:1.2.1-1# warning@Base 5.4
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:14: binary] Error 25

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, x32

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

Bug#965485: marked as done (dia2code: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 12:34:14 +
with message-id 
and subject line Bug#965485: fixed in dia2code 0.8.3-4.2
has caused the Debian Bug report #965485,
regarding dia2code: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dia2code
Version: 0.8.3-4
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package dia2code uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: dia2code
Source-Version: 0.8.3-4.2
Done: Hugh McMaster 

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

Debian distribution maintenance software
pp.
Hugh McMaster  (supplier of updated dia2code package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Apr 2022 17:55:21 +1000
Source: dia2code
Architecture: source
Version: 0.8.3-4.2
Distribution: unstable
Urgency: medium
Maintainer: Francesco Aloe 
Changed-By: Hugh McMaster 
Closes: 878587 949091 965485
Changes:
 dia2code (0.8.3-4.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Use package format 3.0 (quilt).
   * Use debhelper-compat v13 (Closes: #965485).
   * Switch from 'cdbs' to 'dh' format.
   * debian/changelog: Trim trailing whitespace.
   * debian/control:
 - Drop versioned dependency on libxml2.
 - Drop cdbs, autotools-dev and patchutils from the Build-Depends list.
 - Build-Depend on pkg-config.
 - Raise Standards-Version to 4.6.0 from 3.7.3 (no changes needed).
 - Declare Rules-Requires-Root: no.
 - Add Homepage field.
 - Remove alternative recommends on dia-gnome (Closes: #878587).
 - Add ${misc:Depends} to the binary package Depends list.
   * debian/copyright: Use DEP-5 format and update for 2022.
   * debian/patches: Add descriptions and other metadata.
   * debian/rules: Add hardening flags to DEB_BUILD_MAINT_OPTIONS.
   * Use pkg-config to find libxml2 (Closes: #949091).
   * Update debian/watch file.
Checksums-Sha1:
 9b5dbff17341144dd3e866ddbb3526ab597ac309 1631 dia2code_0.8.3-4.2.dsc
 5acb09b05c330b26982c5b83e2088edf745d2974 6892 dia2code_0.8.3-4.2.debian.tar.xz
 2cebd94a5ed6284e18d9fe4ee082b6dfb62b0886 5539 
dia2code_0.8.3-4.2_source.buildinfo
Checksums-Sha256:
 3f34625dc6bd51571b0f38eab6f570f538ca80d7078de91c7a7d43645a944bc8 1631 
dia2code_0.8.3-4.2.dsc
 0f05070168f00aa5bf8396ef2b45ec15885a06d3b4bc1c9be6ad14c709b091f1 6892 
dia2code_0.8.3-4.2.debian.tar.xz
 e7a5a2006b834768824d9f52628afcc9467d52f94bbc7fd5a2fb7f443fe85f16 5539 
dia2code_0.8.3-4.2_source.buildinfo
Files:
 c4f52bba7a1cd656c891c2ecfd0fd24d 1631 devel optional dia2code_0.8.3-4.2.dsc
 ca5021ed7b155ae139260346338207fb 6892 devel optional 
dia2code_0.8.3-4.2.debian.tar.xz
 8bc811ee6e2baa9a6633b51721cd9053 5539 devel optional 
dia2code_0.8.3-4.2_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1007829: [pkg-netfilter-team] Bug#1007829: arptables - Fails to install: Too many levels of symbolic links: debdiff for NMU in DELAYED/2

[Arturo Borrero Gonzalez]

On 4/6/22 13:29, Thomas Goirand wrote:

Hi,

As per discussion on IRC and check of the existing prerm, arptables 
already has the logic in prerm to clean-up old symlinks, so I didn't 
touch it.


Discussing on #debian-devel, it was agreed we need to clean-up eventual 
remainings of the symlink, if they point to /usr/sbin/*, so that's what 
I've done in the attached patch.


I have attached the debdiff for the NMU that I've uploaded to delayed-2. 
Let me know if that's fine, or if you would like me to "dcut rm" the 
upload.




Works for me, thanks!

Bug#1008722: Possible bugfix

[Moessbauer, Felix]

Hi Sudip,

Unfortunately I found more races in the build.
There has to be something more general to be wrong with these Makefiles:
2022-04-06 12:14:27 - ERROR - --- debian/libtracefs1.symbols 
(libtracefs1_1.3.0-1_amd64)
2022-04-06 12:14:27 - ERROR - +++ dpkg-gensymbolsyDWb5y 2022-04-06 
12:14:15.730437201 +
2022-04-06 12:14:27 - ERROR - @@ -114,7 +114,7 @@
2022-04-06 12:14:27 - ERROR - tracefs_printf@Base 1.1.1
2022-04-06 12:14:27 - ERROR - tracefs_put_tracing_file@Base 
0.0~git20201211.ca6a929
2022-04-06 12:14:27 - ERROR - tracefs_set_loglevel@Base 1.2.0
2022-04-06 12:14:27 - ERROR - - tracefs_sql@Base 1.3.0
2022-04-06 12:14:27 - ERROR - +#MISSING: 1.3.0-1# tracefs_sql@Base 1.3.0
2022-04-06 12:14:27 - ERROR - tracefs_synth_add_compare_field@Base 1.3.0
2022-04-06 12:14:27 - ERROR - tracefs_synth_add_end_field@Base 1.3.0
2022-04-06 12:14:27 - ERROR - tracefs_synth_add_match_field@Base 1.3.0

2022-04-06 12:14:27 - ERROR - dh_makeshlibs: error: failing due to earlier 
errors

Also found similar issues for libtraceevent.
To keep things maintainable, I'll add a dedicated bug report.

Best regards,
Felix
--
Siemens AG, Technology, T CED SES-DE
Otto-Hahn-Ring 6, 81739 München, Germany

Processed: your mail

[Debian Bug Tracking System]

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

> tags 1006543 fixed-upstream
Bug #1006543 [imv] imv-wayland segfaults on latest wlroots/sway, fixed in 4.3.1
Added tag(s) fixed-upstream.
>
End of message, stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 1006543 patch
Bug #1006543 [imv] imv-wayland segfaults on latest wlroots/sway, fixed in 4.3.1
Added tag(s) patch.
>
End of message, stopping processing here.

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

Bug#1006543: Patch

[Gard Spreemann]

I've made an MR on Salsa with a patch that I have verified fixes the
bug[1].

Although, as has been mentioned, the best thing is probably just to
package upstream's 4.3.1. But since this bug has been around for a
while, I will do an NMU to DELAYED/5 with the fix from the MR if I don't
hear back in the next few days.


[1] https://salsa.debian.org/debian-phototools-team/imv/-/merge_requests/2

 Best,
 Gard

Bug#1007829: [pkg-netfilter-team] Bug#1007829: arptables - Fails to install: Too many levels of symbolic links: debdiff for NMU in DELAYED/2

[Thomas Goirand]

Hi,

As per discussion on IRC and check of the existing prerm, arptables 
already has the logic in prerm to clean-up old symlinks, so I didn't 
touch it.


Discussing on #debian-devel, it was agreed we need to clean-up eventual 
remainings of the symlink, if they point to /usr/sbin/*, so that's what 
I've done in the attached patch.


I have attached the debdiff for the NMU that I've uploaded to delayed-2. 
Let me know if that's fine, or if you would like me to "dcut rm" the upload.


Cheers,

Thomas Goirand (zigo)diff -Nru arptables-0.0.5/debian/arptables.postinst 
arptables-0.0.5/debian/arptables.postinst
--- arptables-0.0.5/debian/arptables.postinst   2020-05-15 12:14:42.0 
+0200
+++ arptables-0.0.5/debian/arptables.postinst   2022-04-06 10:30:56.0 
+0200
@@ -5,14 +5,14 @@
 
 set -e
 
-# compat symlinks for /sbin -> /usr/sbin move, to be dropped in buster+1
+# Clean-up the old compat symlinks for /sbin -> /usr/sbin
 
 if [ "$1" = "configure" ]; then
LIST="arptables arptables-save arptables-restore"
 
for i in $LIST; do
-   if [ ! -e "/sbin/$i" ]; then
-  ln -sf /usr/sbin/$i /sbin/$i
+   if [ -e "/sbin/$i" ] && [ $(readlink /sbin/$i) = /usr/sbin/$i ] ; then
+  rm /sbin/$i
fi
done
 fi
diff -Nru arptables-0.0.5/debian/changelog arptables-0.0.5/debian/changelog
--- arptables-0.0.5/debian/changelog2020-06-09 17:47:38.0 +0200
+++ arptables-0.0.5/debian/changelog2022-04-06 10:31:00.0 +0200
@@ -1,3 +1,11 @@
+arptables (0.0.5-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Do not install /sbin/* compat symlink, cleans them if they are still
+present (Closes: #1007829).
+
+ -- Thomas Goirand   Wed, 06 Apr 2022 10:31:00 +0200
+
 arptables (0.0.5-3) unstable; urgency=medium
 
   * [9e68e1c] d/tests/control: add isolation-machine restriction to tests

Bug#1009040: esys-particle: build-depends on removed libltdl7-dev

[Graham Inggs]

Source: esys-particle
Version: 2.3.5+dfsg2-4
Severity: serious
Tags: ftbfs

Hi Maintainer

Since the upload of libtool 2.4.7-2, the Provides: libltdl7-dev was
removed, causing esys-particle to FTBFS.  Please switch the
build-depends to the unversioned libltdl-dev.

Regards
Graham

Bug#1009039: dico: build-depends on removed libltdl7-dev

[Graham Inggs]

Source: dico
Version: 2.10-1
Severity: serious
Tags: ftbfs bookworm sid

Hi Maintainer

Since the upload of libtool 2.4.7-2, the Provides: libltdl7-dev was
removed, causing dico to FTBFS.  Please switch the build-depends to
the unversioned libltdl-dev.

Regards
Graham

Bug#1009038: newmat: build-depends on removed libltdl7-dev

[Graham Inggs]

Source: newmat
Version: 1.10.4-8
Severity: serious
Tags: ftbfs bookworm sid

Hi Maintainer

Since the upload of libtool 2.4.7-2, the Provides: libltdl7-dev was
removed, causing newmat to FTBFS.  Please switch the build-depends to
the unversioned libltdl-dev.

Regards
Graham

Processed: your mail

[Debian Bug Tracking System]

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

> severity 1006543 grave
Bug #1006543 [imv] imv-wayland segfaults on latest wlroots/sway, fixed in 4.3.1
Severity set to 'grave' from 'normal'
>
End of message, stopping processing here.

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

Bug#1006788: Bug#1006788: bagel: autopkgtest failure with new mpich.

[Michael Banck]

severity 1006788 important
thanks

On Sun, Apr 03, 2022 at 07:42:42PM +0200, Michael Banck wrote:
> On Sun, Apr 03, 2022 at 02:30:14PM +0200, Michael Banck wrote:
> > On Fri, Mar 04, 2022 at 11:36:24PM +, peter green wrote:
> > > Package: bagel
> > > Version: 1.2.2-3
> > > Severity: serious
> > > x-debbugs-cc: mp...@packages.debian.org
> > > 
> > > bagel's autopkgtest is failing on amd64 with mpich 4.0.1-1 and hence
> > > blocking it's migration to testing and hence blocking the finalisation
> > > of the slurm-wlm transition.
> > > 
> > > https://ci.debian.net/data/autopkgtest/testing/amd64/b/bagel/19726694/log.gz
> > > 
> > > > running test case 'he3_svp_asd-dmrg'... FAILED.
> > 
> > For the record, the error in the .out file is:
> > 
> > |  ERROR: EXCEPTION RAISED:  dsyev/pdsyevd failed in Matrix
> 
> Hrm, it seems that test case passed now on the latest upload:
> https://ci.debian.net/data/autopkgtest/unstable/amd64/b/bagel/20573831/log.gz
> 
> |Get:14 http://deb.debian.org/debian unstable/main amd64 libmpich12 amd64 
> 4.0.1-1 [4,924 kB]
> [...]
> |running test case 'he3_svp_asd-dmrg'... PASSED.
> 
> So I'm a bit at a loss about what's going on here, perhaps that test
> case really is just flakey.
 
Downgrading this as ci.debian.net seems to be happy about it now.


Michael

Processed: Re: Bug#1006788: Bug#1006788: bagel: autopkgtest failure with new mpich.

[Debian Bug Tracking System]

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

> severity 1006788 important
Bug #1006788 [bagel] bagel: autopkgtest failure with new mpich.
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1008423: marked as pending in golang-github-streadway-amqp

[Anthony Fok]

Control: tag -1 pending

Hello,

Bug #1008423 in golang-github-streadway-amqp 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-streadway-amqp/-/commit/65653584e960099902cba77a0b4e68fbe170a98c


Regenerate certs with SHA256 to fix test with Go 1.18+

This fixes "x509: cannot verify signature: insecure algorithm SHA1-RSA"
error with Go 1.18 and up in TestTLSHandshake which led to FTBFS.

See https://github.com/streadway/amqp/pull/525

Thanks: Lucas Nussbaum for the bug report!
Closes: #1008423


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008423

Processed: Bug#1008423 marked as pending in golang-github-streadway-amqp

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008423 [src:golang-github-streadway-amqp] golang-github-streadway-amqp: 
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
github.com/streadway/amqp returned exit code 1
Added tag(s) pending.

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

Processed: The Provides is back at least temporarily

[Debian Bug Tracking System]

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

> severity 1008765 normal
Bug #1008765 [claws-mail] claws-mail: build-depends on unavailable package 
libltdl3-dev
Severity set to 'normal' from 'grave'
> severity 1008889 normal
Bug #1008889 [cluster-glue] FTBFS: Build-depends libltdl3-dev which is no 
longer available
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1007829: [pkg-netfilter-team] Bug#1007829: Bug#1007829: arptables - Fails to install: Too many levels of symbolic links

[Arturo Borrero Gonzalez]

On 4/6/22 10:36, Thomas Goirand wrote:

Hi,

Please find attached debdiff to fix this bug.

I'll be uploading this to DELAYED/2 queue, as this is affecting a lot of 
people/packages and we need a fix fast. Please let me know if you prefer 
to fix it yourself and you wish me to "dcut rm" my upload.




I was wondering if a similar fix was required in iptables & ebtables.

In the case of iptables:

https://salsa.debian.org/pkg-netfilter-team/pkg-iptables/-/commit/5b0b40839fbc18eb71130947ed76527b7caccdd1

That code was dropped a few years ago.

However, in the case of ebtables:

https://salsa.debian.org/pkg-netfilter-team/pkg-ebtables/-/blob/master/debian/ebtables.postinst#L20

The same code is present.

In all cases, we need a similar fix for prerm as well, see:

https://salsa.debian.org/pkg-netfilter-team/pkg-ebtables/-/commit/5dbd22d1a2c8848d40596524a73d3c3f5e272734

Bug#1008886: marked as done (python-demgengeo build depends on the removed libltdl7-dev provides)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 08:49:15 +
with message-id 
and subject line Bug#1008886: fixed in python-demgengeo 1.4-4.1
has caused the Debian Bug report #1008886,
regarding python-demgengeo build depends on the removed libltdl7-dev provides
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.)


-- 
1008886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-demgengeo
Version: 1.4-4
Severity: serious
Tags: ftbfs

The following packages have unmet dependencies:
 builddeps:python-demgengeo : Depends: libltdl7-dev

This was provides dropped by libtool, changing the build dependency
to libltdl-dev fixes the build.
--- End Message ---
--- Begin Message ---
Source: python-demgengeo
Source-Version: 1.4-4.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated python-demgengeo 
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: Wed, 06 Apr 2022 10:22:59 +0200
Source: python-demgengeo
Architecture: source
Version: 1.4-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Sebastian Ramacher 
Closes: 1008886
Changes:
 python-demgengeo (1.4-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Switch to libltdl-dev (Closes: #1008886)
Checksums-Sha1:
 568b6269f451b33b926555863d036a85b64d114d 2195 python-demgengeo_1.4-4.1.dsc
 1a55dcc92a4fabb457fe41d7a9dab22e0a3dee39 9016 
python-demgengeo_1.4-4.1.debian.tar.xz
Checksums-Sha256:
 67787635093816bb7be9bddca79a966380ade6fb96375527e797caa146af75e3 2195 
python-demgengeo_1.4-4.1.dsc
 d778b39619b10c2d4e9b9d9f8f86e21d5e81e5f0a5c8165fab48b56220e65e9e 9016 
python-demgengeo_1.4-4.1.debian.tar.xz
Files:
 10415297123fd100fffcd8b6cbbd6ef8 2195 python optional 
python-demgengeo_1.4-4.1.dsc
 406223ab85f69b8107fd6e279b630548 9016 python optional 
python-demgengeo_1.4-4.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmJNT/4ACgkQafL8UW6n
GZM2vhAAxfiI/qsblxTPUZu0lMO8xqa+MUqBVypOSYStaiCH+9dX871S1ua1xG3T
2ZKIsdEMmw+OhBTFMPj0FYa9XctuhTBpzbDMjYQgyULfMGZP0ZVywP7hGx0lmW4U
4Q/DEu9VxiQ1QA1YBLDvjsDWTnmmkWROlxmXSjunD084aKcb45xqX8clm1D6+QWb
y7Q2pGg8vhUvIT3Ag9MUcN8Ou8iAcXpILINWU95MaRLYWhgKIEX7Fd8VLYcJEIyl
Q760wUqN6LlB6ghrPvMzZEnl8/S7UgVeNsKGcO9KShi+nTqlNMdx3yF2WFqVKAP6
OVDQJGg6dLWylPp54+pMEdCe8/qlbwGpdClBLlxg6ayttoPvBtIhnWEuF9qGVcHO
uTJ5Unzo9X0Q7OUGHkQjhHCURX1xQSd3R6Q1JKd323kl9Y89F+cLJ4cTKx8shwg5
eNBRm2Ic3j2MDaY50C3SYaDmo4degADVumTpyVdyOLqPibhacoAruVgzGpNou4Yc
yXKQLccFTZV0OWItMV2sYF4CkOlUFJ/p3bSOpQOnvISagPVzZJfcm4PUzOVFgZ7I
dQBrtL0kIoXZ/MtgQDh/NerhlQ9zDkAOKO8B4eGWodPfeqIAsfkeGHwJlg7sNRMA
b7PeSN5unzf9KZdUHMfkNvjwqBAyAXOMCY1iqSGvsBbe3z2f0mM=
=T+s1
-END PGP SIGNATURE End Message ---

Processed: severity of 1008701 is normal

[Debian Bug Tracking System]

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

> severity 1008701 normal
Bug #1008701 [src:broctl] Should broctl be removed?
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1007829: [pkg-netfilter-team] Bug#1007829: arptables - Fails to install: Too many levels of symbolic links

[Thomas Goirand]

Hi,

Please find attached debdiff to fix this bug.

I'll be uploading this to DELAYED/2 queue, as this is affecting a lot of 
people/packages and we need a fix fast. Please let me know if you prefer 
to fix it yourself and you wish me to "dcut rm" my upload.


Cheers,

Thomas Goirand (zigo)diff -Nru arptables-0.0.5/debian/arptables.postinst 
arptables-0.0.5/debian/arptables.postinst
--- arptables-0.0.5/debian/arptables.postinst   2020-05-15 12:14:42.0 
+0200
+++ arptables-0.0.5/debian/arptables.postinst   2022-04-06 10:30:56.0 
+0200
@@ -5,14 +5,14 @@
 
 set -e
 
-# compat symlinks for /sbin -> /usr/sbin move, to be dropped in buster+1
+# Clean-up the old compat symlinks for /sbin -> /usr/sbin
 
 if [ "$1" = "configure" ]; then
LIST="arptables arptables-save arptables-restore"
 
for i in $LIST; do
-   if [ ! -e "/sbin/$i" ]; then
-  ln -sf /usr/sbin/$i /sbin/$i
+   if [ -e "/sbin/$i" ] && [ $(readlink /sbin/$i) = /usr/sbin/$i ] ; then
+  rm /sbin/$i
fi
done
 fi
diff -Nru arptables-0.0.5/debian/changelog arptables-0.0.5/debian/changelog
--- arptables-0.0.5/debian/changelog2020-06-09 17:47:38.0 +0200
+++ arptables-0.0.5/debian/changelog2022-04-06 10:31:00.0 +0200
@@ -1,3 +1,11 @@
+arptables (0.0.5-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Do not install /sbin/* compat symlink, cleans them if they are still
+present (Closes: #1007829).
+
+ -- Thomas Goirand   Wed, 06 Apr 2022 10:31:00 +0200
+
 arptables (0.0.5-3) unstable; urgency=medium
 
   * [9e68e1c] d/tests/control: add isolation-machine restriction to tests

Processed: python-demgengeo: diff for NMU version 1.4-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1008886 + patch
Bug #1008886 [src:python-demgengeo] python-demgengeo build depends on the 
removed libltdl7-dev provides
Added tag(s) patch.

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

Bug#1008886: python-demgengeo: diff for NMU version 1.4-4.1

[Sebastian Ramacher]

Control: tags 1008886 + patch

Dear maintainer,

since this issue is blocking the ongoing python3.10 as default
transition, I've prepared an NMU for python-demgengeo (versioned as
1.4-4.1). The diff is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru python-demgengeo-1.4/debian/changelog python-demgengeo-1.4/debian/changelog
--- python-demgengeo-1.4/debian/changelog	2022-01-17 13:56:57.0 +0100
+++ python-demgengeo-1.4/debian/changelog	2022-04-06 10:22:59.0 +0200
@@ -1,3 +1,10 @@
+python-demgengeo (1.4-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Switch to libltdl-dev (Closes: #1008886)
+
+ -- Sebastian Ramacher   Wed, 06 Apr 2022 10:22:59 +0200
+
 python-demgengeo (1.4-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru python-demgengeo-1.4/debian/control python-demgengeo-1.4/debian/control
--- python-demgengeo-1.4/debian/control	2022-01-17 11:49:31.0 +0100
+++ python-demgengeo-1.4/debian/control	2022-04-06 10:22:52.0 +0200
@@ -13,7 +13,7 @@
libboost-iostreams-dev,
libboost-python-dev,
libcppunit-dev,
-   libltdl7-dev,
+   libltdl-dev,
libtool,
python3-dev,
 Standards-Version: 4.4.1


signature.asc
Description: PGP signature

Bug#1008976: marked as done (Wordpress editor shows empty screen)

[Debian Bug Tracking System]

Your message dated Wed, 06 Apr 2022 07:49:19 +
with message-id 
and subject line Bug#1008976: fixed in wordpress 5.9.2+dfsg1-2
has caused the Debian Bug report #1008976,
regarding Wordpress editor shows empty screen
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.)


-- 
1008976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wordpress
Version: 5.9.2+dfsg1-1
Severity: normal

Hello,

when editing a post with the actual wordpress version only a blank screen is 
shown.
For fixing that you have to copy the files

wp-includes/js/dist/blocks.js
wp-includes/js/dist/blocks.min.js

from the actual upstream version (tested under bullseye).

Kind Regards
Katharina
-- 
--- End Message ---
--- Begin Message ---
Source: wordpress
Source-Version: 5.9.2+dfsg1-2
Done: Craig Small 

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated wordpress 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: Wed, 06 Apr 2022 17:20:47 +1000
Source: wordpress
Architecture: source
Version: 5.9.2+dfsg1-2
Distribution: unstable
Urgency: high
Maintainer: Craig Small 
Changed-By: Craig Small 
Closes: 1008976
Changes:
 wordpress (5.9.2+dfsg1-2) unstable; urgency=high
 .
   * Fix emoji patch Closes: #1008976
Checksums-Sha1:
 25520d6728db41948da21f18e939e7dac550c8ba 2394 wordpress_5.9.2+dfsg1-2.dsc
 84b04a5135c24bac9fd1158ea87452e79c2acdd8 6825036 
wordpress_5.9.2+dfsg1-2.debian.tar.xz
 cbb904380825c4076781dbf3a0e43b1a5b5d6f27 7633 
wordpress_5.9.2+dfsg1-2_amd64.buildinfo
Checksums-Sha256:
 70e706ff1b4e4d357b9f6043f2725c8fad434269918bb49e1f7a49f8044dc605 2394 
wordpress_5.9.2+dfsg1-2.dsc
 ee417f4e3614fb333b7dd91e862af0f621bfe84903fa9773f1bbc75186059ff8 6825036 
wordpress_5.9.2+dfsg1-2.debian.tar.xz
 547ecb31ca541990b451e749a8624824ab95d30ec7697f948978011906221081 7633 
wordpress_5.9.2+dfsg1-2_amd64.buildinfo
Files:
 99e3d9cf5bff5c1b417cdce32409ecb6 2394 web optional wordpress_5.9.2+dfsg1-2.dsc
 771716224481e5a1c7f83bfe974553e5 6825036 web optional 
wordpress_5.9.2+dfsg1-2.debian.tar.xz
 9a66dc6798243a4b2668bc8e5969a700 7633 web optional 
wordpress_5.9.2+dfsg1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAmJNQH4ACgkQAiFmwP88
hON8yw/9EsOQd19by/DnBAo36EqJXw1TJQ+CXKocFX9ptBMJiwm9H+eTfvYr1FBK
TZ4Bho8AwM9OnAx2C3kN5ry4fqSpEdzNchXVDOCoUO56gbnPnJneM3oCJtFBdC6S
KfejaH48pU9nQPcdGf0z6HwqU1pzwjk1I8EHgpk9Z1A6jMXawyy9lfa1XMqTiRPK
rj9RZ8pa0ErMUDeKqRRzZnK+6/vzEvg31Y5REWM6Yo/6k51u/BLJysqPZ/CpEwWn
SkzWagAat5kd5ItCu+hQZifjKueXwymLbL0yR72mB3/9/HYcH3++gfzIPHqJq14C
00WAxkmsWjdUYmkpuzACPGr2zKTVTpar0W0nMH/IxyuWZy5ddBjyEL9pPBdhk0Ol
6Fd9SYWlpqPoB9RTYsVc8PZQZv8d4Le386Cw/81W6fMfHpXNhw+XUlh8kuBDU/32
D7ZOwe8oklM27R6Zv0M9dq7CJnXtyhiC2604gs+ZDY2UyzM4G8HFl+yerdvi0aHi
Q1vjj2mMkbQq9LF0JqMeiiqfLNV9bUWbq++RjpvxonkDrc3BtlizBxaIDNlYWdWJ
Cjx3d0yXkNY73Mly0uYWAe7IO6IbNqqGngDO8Vx63nPISqsO9POOnvDfNSPgPwC+
L5XLptgf6KAPF0rHTJVHGgJeziDMawNvgxX7+XXh6VDaiUZqHTI=
=ei6U
-END PGP SIGNATURE End Message ---

Bug#1008776: intel-media-va-driver: Segmentation fault with gstreamer based applications

[Kai Weber]

* Sebastian Ramacher :

> That could be another case of the driver expecting to have a kernel
> available which in fact is disabled in the open source build. If
> 22.3.1+dfsg1-1 doesn't fix the issue for you, please let my know your
> CPU/GPU so that the issue can be reported upstream.

Unfortunately it does not solve the issue. Here are my CPU/GPU types:

CPU: Intel® Core™ i7-8550U CPU @ 1.80GHz × 8
GPU: Mesa Intel® UHD Graphics 620 (KBL GT2)

Bug#1008976: marked as pending in wordpress

[Craig Small]

Control: tag -1 pending

Hello,

Bug #1008976 in wordpress 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/debian/wordpress/-/commit/75557b1cdfd1cf9d27841abd3cf7d266631b046d


Fix emoji patch Closes: #1008976


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008976

Processed: Bug#1008976 marked as pending in wordpress

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008976 [wordpress] Wordpress editor shows empty screen
Added tag(s) pending.

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

Processed: severity of 1008976 is grave

[Debian Bug Tracking System]

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

> severity 1008976 grave
Bug #1008976 [wordpress] Wordpress editor shows empty screen
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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