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

2022-10-14 Thread Debian Bug Tracking System 
Your message dated Sat, 15 Oct 2022 05:34:52 +
with message-id 
and subject line Bug#1013540: fixed in sklearn-pandas 2.2.0-1.1
has caused the Debian Bug report #1013540,
regarding sklearn-pandas: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.9 3.10" 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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>   install -d /<>/debian/.debhelper/generated/_source/home
>   pybuild --configure -i python{version} -p "3.9 3.10"
> I: pybuild base:239: python3.9 setup.py config 
> running config
> I: pybuild base:239: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
>   pybuild --build -i python{version} -p "3.9 3.10"
> I: pybuild base:239: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.9_sklearn-pandas/build/sklearn_pandas
> copying sklearn_pandas/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_sklearn-pandas/build/sklearn_pandas
> copying sklearn_pandas/pipeline.py -> 
> /<>/.pybuild/cpython3_3.9_sklearn-pandas/build/sklearn_pandas
> copying sklearn_pandas/features_generator.py -> 
> /<>/.pybuild/cpython3_3.9_sklearn-pandas/build/sklearn_pandas
> copying sklearn_pandas/cross_validation.py -> 
> /<>/.pybuild/cpython3_3.9_sklearn-pandas/build/sklearn_pandas
> copying sklearn_pandas/transformers.py -> 
> /<>/.pybuild/cpython3_3.9_sklearn-pandas/build/sklearn_pandas
> copying sklearn_pandas/dataframe_mapper.py -> 
> /<>/.pybuild/cpython3_3.9_sklearn-pandas/build/sklearn_pandas
> I: pybuild base:239: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.10_sklearn-pandas/build/sklearn_pandas
> copying sklearn_pandas/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_sklearn-pandas/build/sklearn_pandas
> copying sklearn_pandas/pipeline.py -> 
> /<>/.pybuild/cpython3_3.10_sklearn-pandas/build/sklearn_pandas
> copying sklearn_pandas/features_generator.py -> 
> /<>/.pybuild/cpython3_3.10_sklearn-pandas/build/sklearn_pandas
> copying sklearn_pandas/cross_validation.py -> 
> /<>/.pybuild/cpython3_3.10_sklearn-pandas/build/sklearn_pandas
> copying sklearn_pandas/transformers.py -> 
> /<>/.pybuild/cpython3_3.10_sklearn-pandas/build/sklearn_pandas
> copying sklearn_pandas/dataframe_mapper.py -> 
> /<>/.pybuild/cpython3_3.10_sklearn-pandas/build/sklearn_pandas
>dh_auto_test -O--buildsystem=pybuild
>   pybuild --test --test-pytest -i python{version} -p "3.9 3.10"
> I: pybuild base:239: cd 
> /<>/.pybuild/cpython3_3.9_sklearn-pandas/build; python3.9 -m 
> pytest ; cd /<>; python3.9 -m doctest -v README.rst
> = test session starts 
> ==
> platform linux -- Python 3.9.13, pytest-6.2.5, py-1.10.0, pluggy-1.0.0
> rootdir: /<>, configfile: pytest.ini
> collected 69 items
> 
> tests/test_dataframe_mapper.py . [ 
> 59%]
> ..   [ 
> 85%]
> tests/test_features_generator.py [ 
> 91%]
> tests/test_pipeline.py   [ 
> 97%]
> tests/test_transformers.py ..
> [100%]
> 
> === warnings summary 
> ===
> .pybuild/cpython3_3.9_sklearn-pandas/build/tests/test_dataframe_mapper.py: 13 
> warnings
>   /usr/lib/python3/dist-packages/sklearn/utils/deprecation.py:87: 
> FutureWarning: Function get_feature_names is deprecated; get_feature_names is 
> deprecated in 1.0 and will be removed in 1.2. Please use 
> get_feature_names_out instead.
> warnings.warn(msg, category=FutureWarning)
> 
> .pybuild/cpython3_3.9_sklearn-pandas/build/tests/test_dataframe_mapper.py::test_sparse_features
>   
> /<>/.pybuild/cpython3_3.9_sklearn-pandas/build/tests/test_dataframe_mapper.py:820:
>

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

2022-10-14 Thread Debian Bug Tracking System 
Your message dated Sat, 15 Oct 2022 04:33:51 +
with message-id 
and subject line Bug#1002367: fixed in python-pygal 2.4.0-2.3
has caused the Debian Bug report #1002367,
regarding python-pygal: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -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.)


-- 
1002367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pygal
Version: 2.4.0-2.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):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
> I: pybuild base:237: python3.10 setup.py config 
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'test_requires'
>   warnings.warn(msg)
> running config
> I: pybuild base:237: python3.9 setup.py config 
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'test_requires'
>   warnings.warn(msg)
> running config
>dh_auto_build -O--buildsystem=pybuild
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:237: /usr/bin/python3.10 setup.py build 
> /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'test_requires'
>   warnings.warn(msg)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/util.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/interpolate.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/etree.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/colors.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/__about__.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/table.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/view.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/_compat.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/svg.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/formatters.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/state.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/config.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/serie.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/adapters.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/stats.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> copying pygal/style.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal
> creating /<>/.pybuild/cpython3_3.10_pygal/build/pygal/maps
> copying pygal/maps/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal/maps
> creating /<>/.pybuild/cpython3_3.10_pygal/build/pygal/test
> copying pygal/test/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal/test
> copying pygal/test/test_pie.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal/test
> copying pygal/test/test_serie_config.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal/test
> copying pygal/test/test_stacked.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal/test
> copying pygal/test/test_line.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal/test
> copying pygal/test/test_bar.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal/test
> copying pygal/test/test_maps.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal/test
> copying pygal/test/test_style.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal/test
> copying pygal/test/test_line_log_none_max_solved.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal/test
> copying pygal/test/test_date.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal/test
> copying pygal/test/test_config.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal/test
> copying pygal/test/test_sparktext.py -> 
> /<>/.pybuild/cpython3_3.10_pygal/build/pygal/test
> copying

Processed: fixed 1018787 in 3:23.0.0-3

2022-10-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> fixed 1018787 3:23.0.0-3
Bug #1018787 {Done: Thomas Goirand } [src:horizon] horizon: 
autopkgtest failure: horizon.test.unit.test_base.RbacHorizonTests
Marked as fixed in versions horizon/3:23.0.0-3.
> thanks
Stopping processing here.

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

Processed: notfound 1002548 in 2.0-2

2022-10-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> notfound 1002548 2.0-2
Bug #1002548 {Done: Thorsten Alteholz } [libfli2,indi-fli] 
libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules
There is no source info for the package 'indi-fli' at version '2.0-2' with 
architecture ''
No longer marked as found in versions libfli/2.0-2.
> thanks
Stopping processing here.

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

Processed: closing 1020111

2022-10-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> close 1020111
Bug #1020111 [src:streamex] streamex: FTBFS: dh_auto_test: error: 
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode test 
returned exit code 1
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: python-dlt: diff for NMU version 2.0-3.1

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> tags 1020093 + patch
Bug #1020093 [src:python-dlt] python-dlt: FTBFS: AssertionError: 1 != 0 : 
Stdout: dlt/dlt_broker_handlers.py:65:24: E275 missing whitespace after keyword
Added tag(s) patch.
> tags 1020093 + pending
Bug #1020093 [src:python-dlt] python-dlt: FTBFS: AssertionError: 1 != 0 : 
Stdout: dlt/dlt_broker_handlers.py:65:24: E275 missing whitespace after keyword
Added tag(s) pending.

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

Bug#1020093: python-dlt: diff for NMU version 2.0-3.1

2022-10-14 Thread Adrian Bunk 
Control: tags 1020093 + patch
Control: tags 1020093 + pending

Dear maintainer,

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

cu
Adrian
diff -Nru python-dlt-2.0/debian/changelog python-dlt-2.0/debian/changelog
--- python-dlt-2.0/debian/changelog	2021-02-11 00:22:19.0 +0200
+++ python-dlt-2.0/debian/changelog	2022-10-15 06:54:00.0 +0300
@@ -1,3 +1,10 @@
+python-dlt (2.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Backport E275 codestyle fixes. (Closes: #1020093)
+
+ -- Adrian Bunk   Sat, 15 Oct 2022 06:54:00 +0300
+
 python-dlt (2.0-3) unstable; urgency=medium
 
   * Tighteen the dependency on dlt-daemon version 2.18.6
diff -Nru python-dlt-2.0/debian/patches/e275.patch python-dlt-2.0/debian/patches/e275.patch
--- python-dlt-2.0/debian/patches/e275.patch	1970-01-01 02:00:00.0 +0200
+++ python-dlt-2.0/debian/patches/e275.patch	2022-10-15 06:54:00.0 +0300
@@ -0,0 +1,24 @@
+Description: Backport E275 codestyle fixes
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/1020093
+
+--- python-dlt-2.0.orig/dlt/dlt_broker_handlers.py
 python-dlt-2.0/dlt/dlt_broker_handlers.py
+@@ -62,7 +62,7 @@ class DLTContextHandler(Thread):
+ if filters:
+ with self.lock:
+ try:
+-del(self.context_map[queue_id])
++del self.context_map[queue_id]
+ except KeyError:
+ pass
+ 
+@@ -149,7 +149,7 @@ class DLTMessageHandler(Process):
+ for apid_ctid in filters:
+ self.context_map[apid_ctid].remove(queue_id)
+ if not self.context_map[apid_ctid]:
+-del(self.context_map[apid_ctid])
++del self.context_map[apid_ctid]
+ except (KeyError, ValueError):
+ # - queue_id already removed or not inserted
+ pass
diff -Nru python-dlt-2.0/debian/patches/series python-dlt-2.0/debian/patches/series
--- python-dlt-2.0/debian/patches/series	2021-02-11 00:20:39.0 +0200
+++ python-dlt-2.0/debian/patches/series	2022-10-15 06:54:00.0 +0300
@@ -2,3 +2,4 @@
 ignore_pylint_file.diff
 git-updates.patch
 27.patch
+e275.patch

Processed: Merge duplicates

2022-10-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 1020086 dh-python
Bug #1020086 [src:bup] bup: FTBFS: AttributeError: 're.Pattern' object has no 
attribute 'replace'
Bug reassigned from package 'src:bup' to 'dh-python'.
No longer marked as found in versions bup/0.32-3.
Ignoring request to alter fixed versions of bug #1020086 to the same values 
previously set
> forcemerge 1020041 1020086
Bug #1020041 {Done: Stefano Rivera } [dh-python] 
zope.testrunner: FTBFS: AttributeError: 're.Pattern' object has no attribute 
'replace'
Bug #1020086 [dh-python] bup: FTBFS: AttributeError: 're.Pattern' object has no 
attribute 'replace'
Marked Bug as done
Marked as fixed in versions dh-python/5.20221001.
Marked as found in versions dh-python/5.20220924.
Merged 1020041 1020086
> affects 1020041 src:bup
Bug #1020041 {Done: Stefano Rivera } [dh-python] 
zope.testrunner: FTBFS: AttributeError: 're.Pattern' object has no attribute 
'replace'
Bug #1020086 {Done: Stefano Rivera } [dh-python] bup: 
FTBFS: AttributeError: 're.Pattern' object has no attribute 'replace'
Added indication that 1020041 affects src:bup
Added indication that 1020086 affects src:bup
> thanks
Stopping processing here.

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

Processed: ukui-screensaver: diff for NMU version 3.0.3-1.1

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> tags 1020068 + patch
Bug #1020068 [src:ukui-screensaver] ukui-screensaver: FTBFS: giodbus.cpp:22:10: 
fatal error: gio-unix-2.0/gio/gunixfdlist.h: No such file or directory
Added tag(s) patch.
> tags 1020068 + pending
Bug #1020068 [src:ukui-screensaver] ukui-screensaver: FTBFS: giodbus.cpp:22:10: 
fatal error: gio-unix-2.0/gio/gunixfdlist.h: No such file or directory
Added tag(s) pending.

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

Bug#1020068: ukui-screensaver: diff for NMU version 3.0.3-1.1

2022-10-14 Thread Adrian Bunk 
Control: tags 1020068 + patch
Control: tags 1020068 + pending

Dear maintainer,

I've prepared an NMU for ukui-screensaver (versioned as 3.0.3-1.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru ukui-screensaver-3.0.3/debian/changelog ukui-screensaver-3.0.3/debian/changelog
--- ukui-screensaver-3.0.3/debian/changelog	2022-02-22 08:20:17.0 +0200
+++ ukui-screensaver-3.0.3/debian/changelog	2022-10-15 06:29:20.0 +0300
@@ -1,3 +1,10 @@
+ukui-screensaver (3.0.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with new glib. (Closes: #1020068)
+
+ -- Adrian Bunk   Sat, 15 Oct 2022 06:29:20 +0300
+
 ukui-screensaver (3.0.3-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru ukui-screensaver-3.0.3/debian/patches/glib.patch ukui-screensaver-3.0.3/debian/patches/glib.patch
--- ukui-screensaver-3.0.3/debian/patches/glib.patch	1970-01-01 02:00:00.0 +0200
+++ ukui-screensaver-3.0.3/debian/patches/glib.patch	2022-10-15 06:29:20.0 +0300
@@ -0,0 +1,15 @@
+Description: Fix FTBFS with new glib
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/1020068
+
+--- ukui-screensaver-3.0.3.orig/BiometricAuth/giodbus.cpp
 ukui-screensaver-3.0.3/BiometricAuth/giodbus.cpp
+@@ -19,7 +19,7 @@
+ 
+ #include "giodbus.h"
+ #include 
+-#include 
++#include 
+ #include 
+ 
+ int get_server_gvariant_stdout (int drvid)
diff -Nru ukui-screensaver-3.0.3/debian/patches/series ukui-screensaver-3.0.3/debian/patches/series
--- ukui-screensaver-3.0.3/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ ukui-screensaver-3.0.3/debian/patches/series	2022-10-15 06:29:20.0 +0300
@@ -0,0 +1 @@
+glib.patch

Processed: gnuserv FTBFS with emacs 28

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> block 1020050 by -1
Bug #1020050 {Done: Alexander Zangerl } [src:gnuserv] gnuserv: 
FTBFS: gnuserv-compat.el:203:1: Error: Wrong number of arguments: (3 . 4), 2
1020050 was not blocked by any bugs.
1020050 was not blocking any bugs.
Added blocking bug(s) of 1020050: 1021803

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

Bug#1021803: gnuserv FTBFS with emacs 28

2022-10-14 Thread Adrian Bunk 
Source: gnuserv
Version: 3.12.8-8
Severity: serious
Tags: ftbfs
Control: block 1020050 by -1

https://buildd.debian.org/status/logs.php?pkg=gnuserv=3.12.8-8

...
emacs --no-site-file -batch \
--eval "(add-to-list 'load-path \".\")" \
-l gnuserv-compat -f batch-byte-compile gnuserv.el
Package cl is deprecated
Debugger entered--Lisp error: (error "Cannot find suitable directory for output 
in ‘nati...")
  error("Cannot find suitable directory for output in `nati...")
  comp-trampoline-compile(delete-frame)
  comp-subr-trampoline-install(delete-frame)
  ad-add-advice(delete-frame (gnuserv-compat-delete-frame nil t (advice lambda 
nil (run-hook-with-args 'delete-device-hook frame))) before first)
  
byte-code("\300\301!\210\302\303!\204\17\0\304\303\305\"\210\302\306!\204\32\0\304\306\307\"\210\302\310!\204%\0\304\310\311\"\210\312\313!\2045\0\314\315\316!\2063\0..."
 [require cl fboundp define-obsolete-variable-alias defalias 
make-obsolete-variable functionp #f(compiled-function (object) #) add-minor-mode #f(compiled-function (toggle name) 
#) boundp temporary-file-directory (lambda 
(def-tmp-var) (defvar temporary-file-directory def-tmp-var)) getenv "TMPDIR" 
"/tmp" temp-directory #f(compiled-function () #) 
string-match "XEmacs" emacs-version ad-add-advice make-frame 
(gnuserv-compat-make-frame nil t (advice lambda ( parameters device) 
(if (and device (frame-live-p device)) (progn (if parameters 
(modify-frame-parameters device parameters)) (setq ad-return-value device)) 
ad-do-it))) around first ad-activate nil delete-frame 
(gnuserv-compat-delete-frame nil t (advice lambda nil (run-hook-with-args 
'delete-device-hook frame))) before filtered-frame-list 
(gnuserv-compat-filtered-frame-list nil t (advice lambda (predicate  
device) ad-do-it)) devices device-list frame-list selected-device 
selected-frame device-frame-list #f(compiled-function ( device) 
#) frame-iconified-p #f(compiled-function (frame) 
#) deiconify-frame make-frame-visible 
frame-totally-visible-p #f(compiled-function (frame) #) (error) custom featurep custom-declare-variable ...] 5)
  command-line-1(("--eval" "(add-to-list 'load-path \".\")" "-l" 
"gnuserv-compat" "-f" "batch-byte-compile" "gnuserv.el"))
  command-line()
  normal-top-level()

make[1]: *** [Makefile:250: gnuserv.elc] Error 255

Bug#994348: python-apt: Removal of the python3-*-dbg packages in sid/bookworm

2022-10-14 Thread Micha Lenk 

Hi there,

Just for the records, I started working on this bug. A first fix attempt 
is available on [1]salsa -- but unfortunately it causes the package to 
fail to build from source. I'll continue tomorrow.


 [1]. 
https://salsa.debian.org/micha/python-apt/-/compare/main...remove-python3-apt-dbg-package


Regards,
Micha

Bug#1020034: marked as pending in dgedit

2022-10-14 Thread Adrian Bunk 
On Sun, Sep 18, 2022 at 08:50:44PM +, Dennis Braun wrote:
> Control: tag -1 pending
> 
> Hello,
> 
> Bug #1020034 in dgedit 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/multimedia-team/dgedit/-/commit/f03c1fdeeab9a5392ced54f21b7ff90b1d3ed3e2
> 
> 
> Add pkg-config to B-Ds (Closes: #1020034)
> 
>...

This fix is still missing in unstable.

Thanks
Adrian

Processed: ukui-control-center: diff for NMU version 3.0.5-1.1

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> tags 1020030 + patch
Bug #1020030 [src:ukui-control-center] ukui-control-center: FTBFS: 
giodbus.cpp:21:10: fatal error: gio-unix-2.0/gio/gunixfdlist.h: No such file or 
directory
Added tag(s) patch.
> tags 1020030 + pending
Bug #1020030 [src:ukui-control-center] ukui-control-center: FTBFS: 
giodbus.cpp:21:10: fatal error: gio-unix-2.0/gio/gunixfdlist.h: No such file or 
directory
Added tag(s) pending.

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

Bug#1020030: ukui-control-center: diff for NMU version 3.0.5-1.1

2022-10-14 Thread Adrian Bunk 
Control: tags 1020030 + patch
Control: tags 1020030 + pending

Dear maintainer,

I've prepared an NMU for ukui-control-center (versioned as 3.0.5-1.1) 
and uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru ukui-control-center-3.0.5/debian/changelog ukui-control-center-3.0.5/debian/changelog
--- ukui-control-center-3.0.5/debian/changelog	2022-02-23 05:41:56.0 +0200
+++ ukui-control-center-3.0.5/debian/changelog	2022-10-14 23:57:13.0 +0300
@@ -1,3 +1,10 @@
+ukui-control-center (3.0.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with new glib. (Closes: #1020030)
+
+ -- Adrian Bunk   Fri, 14 Oct 2022 23:57:13 +0300
+
 ukui-control-center (3.0.5-1) unstable; urgency=medium
 
   * New upstream releaes.
diff -Nru ukui-control-center-3.0.5/debian/patches/glib.patch ukui-control-center-3.0.5/debian/patches/glib.patch
--- ukui-control-center-3.0.5/debian/patches/glib.patch	1970-01-01 02:00:00.0 +0200
+++ ukui-control-center-3.0.5/debian/patches/glib.patch	2022-10-14 23:57:13.0 +0300
@@ -0,0 +1,15 @@
+Description: Fix FTBFS with new glib
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/1020030
+
+--- ukui-control-center-3.0.5.orig/plugins/account/userinfo/giodbus.cpp
 ukui-control-center-3.0.5/plugins/account/userinfo/giodbus.cpp
+@@ -18,7 +18,7 @@
+ 
+ #include "giodbus.h"
+ #include 
+-#include 
++#include 
+ #include 
+ 
+ int get_server_gvariant_stdout (int drvid)
diff -Nru ukui-control-center-3.0.5/debian/patches/series ukui-control-center-3.0.5/debian/patches/series
--- ukui-control-center-3.0.5/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ ukui-control-center-3.0.5/debian/patches/series	2022-10-14 23:57:13.0 +0300
@@ -0,0 +1 @@
+glib.patch

Bug#1021798: crowdsec: FTBFS: FAIL: TestCreateMachineWithForwardedFor

2022-10-14 Thread Cyril Brulebois 
Hi,

Andreas Beckmann  (2022-10-14):
> Source: crowdsec
> Version: 1.0.9-3
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> 
> Hi,
> 
> crowdsec in sid (and experimental) recently started to FTBFS:
> 
> === RUN   TestCreateMachineWithForwardedFor
> time="2022-10-14T20:21:20Z" level=info msg="Creating new API server"
>  - [Fri, 14 Oct 2022 20:21:20 UTC] "POST /v1/watchers HTTP/1.1 201 
> 56.31ms "crowdsec-test/" "
> machines_test.go:81:
> Error Trace:
> /build/crowdsec-1.0.9/_build/src/github.com/crowdsecurity/crowdsec/pkg/apiserver/machines_test.go:81
> Error:  Not equal:
> expected: "1.1.1.1"
> actual  : ""
> 
> Diff:
> --- Expected
> +++ Actual
> @@ -1 +1 @@
> -1.1.1.1
> +
> Test:   TestCreateMachineWithForwardedFor
> --- FAIL: TestCreateMachineWithForwardedFor (0.06s)

This should be fixed in the upcoming 1.4.x versions, the test suite
doesn't fail there. There are a bunch of dependencies that need to go in
before that can be uploaded though:
  https://lists.debian.org/debian-go/2022/10/msg00018.html


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature

Processed: dnstap-ldns: diff for NMU version 0.2.0-5.1

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> tags 1020002 + patch
Bug #1020002 [src:dnstap-ldns] dnstap-ldns: FTBFS: configure: error: Package 
requirements (libldns) were not met
Added tag(s) patch.
> tags 1020002 + pending
Bug #1020002 [src:dnstap-ldns] dnstap-ldns: FTBFS: configure: error: Package 
requirements (libldns) were not met
Added tag(s) pending.

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

Bug#1020002: dnstap-ldns: diff for NMU version 0.2.0-5.1

2022-10-14 Thread Adrian Bunk 
Control: tags 1020002 + patch
Control: tags 1020002 + pending

Dear maintainer,

I've prepared an NMU for dnstap-ldns (versioned as 0.2.0-5.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru dnstap-ldns-0.2.0/debian/changelog dnstap-ldns-0.2.0/debian/changelog
--- dnstap-ldns-0.2.0/debian/changelog	2020-12-13 09:53:45.0 +0200
+++ dnstap-ldns-0.2.0/debian/changelog	2022-10-14 23:17:32.0 +0300
@@ -1,3 +1,10 @@
+dnstap-ldns (0.2.0-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Adapt to ldns 1.8.3-1 dropping libldns.pc. (Closes: #1020002)
+
+ -- Adrian Bunk   Fri, 14 Oct 2022 23:17:32 +0300
+
 dnstap-ldns (0.2.0-5) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru dnstap-ldns-0.2.0/debian/patches/ldns-pc.patch dnstap-ldns-0.2.0/debian/patches/ldns-pc.patch
--- dnstap-ldns-0.2.0/debian/patches/ldns-pc.patch	1970-01-01 02:00:00.0 +0200
+++ dnstap-ldns-0.2.0/debian/patches/ldns-pc.patch	2022-10-14 23:17:32.0 +0300
@@ -0,0 +1,15 @@
+Description: Adapt to ldns 1.8.3-1 dropping libldns.pc
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/1020002
+
+--- dnstap-ldns-0.2.0.orig/configure.ac
 dnstap-ldns-0.2.0/configure.ac
+@@ -26,7 +26,7 @@ AC_SUBST([my_CFLAGS])
+ AC_CONFIG_HEADERS(config.h)
+ AC_CONFIG_FILES([Makefile])
+ 
+-PKG_CHECK_MODULES([libldns], [libldns])
++PKG_CHECK_MODULES([libldns], [ldns])
+ 
+ PKG_CHECK_MODULES([libfstrm], [libfstrm >= 0.2.0])
+ 
diff -Nru dnstap-ldns-0.2.0/debian/patches/series dnstap-ldns-0.2.0/debian/patches/series
--- dnstap-ldns-0.2.0/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ dnstap-ldns-0.2.0/debian/patches/series	2022-10-14 23:17:32.0 +0300
@@ -0,0 +1 @@
+ldns-pc.patch

Bug#1021798: crowdsec: FTBFS: FAIL: TestCreateMachineWithForwardedFor

2022-10-14 Thread Andreas Beckmann 
Source: crowdsec
Version: 1.0.9-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

crowdsec in sid (and experimental) recently started to FTBFS:

=== RUN   TestCreateMachineWithForwardedFor
time="2022-10-14T20:21:20Z" level=info msg="Creating new API server"
 - [Fri, 14 Oct 2022 20:21:20 UTC] "POST /v1/watchers HTTP/1.1 201 56.31ms 
"crowdsec-test/" "
machines_test.go:81:
Error Trace:
/build/crowdsec-1.0.9/_build/src/github.com/crowdsecurity/crowdsec/pkg/apiserver/machines_test.go:81
Error:  Not equal:
expected: "1.1.1.1"
actual  : ""

Diff:
--- Expected
+++ Actual
@@ -1 +1 @@
-1.1.1.1
+
Test:   TestCreateMachineWithForwardedFor
--- FAIL: TestCreateMachineWithForwardedFor (0.06s)

Full log attached.


Andreas


crowdsec.sid.build.gz
Description: application/gzip

Bug#1021796: silver-platter: workspace.py: ImportError: cannot import name 'NoColocatedBranchSupport' from 'breezy.errors'

2022-10-14 Thread Andreas Beckmann 
Package: silver-platter
Version: 0.4.5-1
Severity: serious
Control: affects -1 src:janitor

Hi,

src:janitor recently started to FTBFS with some test failures
that seem to originate in silver-platter:

==
ERROR: test_debdiff (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_debdiff
Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/loader.py", line 154, in loadTestsFromName
module = __import__(module_name)
  File "/build/janitor-0.1~git20220702/janitor/tests/test_debdiff.py", line 18, 
in 
from janitor.debian.debdiff import iter_sections, filter_boring
  File "/build/janitor-0.1~git20220702/janitor/debian/__init__.py", line 47, in 

from silver_platter.debian import (
  File "/usr/lib/python3/dist-packages/silver_platter/debian/__init__.py", line 
55, in 
from .. import workspace as _mod_workspace
  File "/usr/lib/python3/dist-packages/silver_platter/workspace.py", line 25, 
in 
from breezy.errors import (
ImportError: cannot import name 'NoColocatedBranchSupport' from 'breezy.errors' 
(/usr/lib/python3/dist-packages/breezy/errors.py)


==
ERROR: test_worker (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_worker
Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/loader.py", line 154, in loadTestsFromName
module = __import__(module_name)
  File "/build/janitor-0.1~git20220702/janitor/tests/test_worker.py", line 18, 
in 
from janitor.worker import bundle_results
  File "/build/janitor-0.1~git20220702/janitor/worker.py", line 55, in 
from silver_platter.workspace import Workspace
  File "/usr/lib/python3/dist-packages/silver_platter/workspace.py", line 25, 
in 
from breezy.errors import (
ImportError: cannot import name 'NoColocatedBranchSupport' from 'breezy.errors' 
(/usr/lib/python3/dist-packages/breezy/errors.py)


Andreas


janitor_0.1~git20220702-1.log.gz
Description: application/gzip

Processed: silver-platter: workspace.py: ImportError: cannot import name 'NoColocatedBranchSupport' from 'breezy.errors'

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> affects -1 src:janitor
Bug #1021796 [silver-platter] silver-platter: workspace.py: ImportError: cannot 
import name 'NoColocatedBranchSupport' from 'breezy.errors'
Added indication that 1021796 affects src:janitor

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

Processed: retitle 1019991 to ovn: ovn-controller incremental processing FAILED

2022-10-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> retitle 1019991 ovn: ovn-controller incremental processing FAILED
Bug #1019991 [src:ovn] ovn: FTBFS: | ./conftest.c:48: undefined reference to 
`pow'
Changed Bug title to 'ovn: ovn-controller incremental processing FAILED' from 
'ovn: FTBFS: | ./conftest.c:48: undefined reference to `pow''.
> thanks
Stopping processing here.

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

Bug#1021790: src:graphicsmagick: fails to migrate to testing for too long: FTBFS on mips64el

2022-10-14 Thread Paul Gevers 

Hi László,

On 14-10-2022 21:33, László Böszörményi (GCS) wrote:

Your package src:graphicsmagick has been trying to migrate
for 61 days [2].

  It's 'only' 37 days, but that's long enough even.


Hmm, [1] says your package was accepted on 14 August 2022; no sure where 
that weird count in the britney output comes from. Maybe because it took 
so long before the first binaries were built?



Then of course I've already gone on and investigated
this issue with its upstream developer.


It's good to have that documented. Thanks for being pro-active.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1020011: ukui-biometric-manager: diff for NMU version 1.0.3-1.1

2022-10-14 Thread Adrian Bunk 
Control: tags 1020011 + patch
Control: tags 1020011 + pending

Dear maintainer,

I've prepared an NMU for ukui-biometric-manager (versioned as 1.0.3-1.1) 
and uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru ukui-biometric-manager-1.0.3/debian/changelog ukui-biometric-manager-1.0.3/debian/changelog
--- ukui-biometric-manager-1.0.3/debian/changelog	2022-03-15 14:47:59.0 +0200
+++ ukui-biometric-manager-1.0.3/debian/changelog	2022-10-14 22:35:45.0 +0300
@@ -1,3 +1,10 @@
+ukui-biometric-manager (1.0.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with new glib. (Closes: #1020011)
+
+ -- Adrian Bunk   Fri, 14 Oct 2022 22:35:45 +0300
+
 ukui-biometric-manager (1.0.3-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru ukui-biometric-manager-1.0.3/debian/patches/glib.patch ukui-biometric-manager-1.0.3/debian/patches/glib.patch
--- ukui-biometric-manager-1.0.3/debian/patches/glib.patch	1970-01-01 02:00:00.0 +0200
+++ ukui-biometric-manager-1.0.3/debian/patches/glib.patch	2022-10-14 22:35:45.0 +0300
@@ -0,0 +1,15 @@
+Description: Fix FTBFS with new glib
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/1020011
+
+--- ukui-biometric-manager-1.0.3.orig/src/giodbus.cpp
 ukui-biometric-manager-1.0.3/src/giodbus.cpp
+@@ -18,7 +18,7 @@
+ 
+ #include "giodbus.h"
+ #include 
+-#include 
++#include 
+ #include 
+ 
+ int get_server_gvariant_stdout (int drvid)
diff -Nru ukui-biometric-manager-1.0.3/debian/patches/series ukui-biometric-manager-1.0.3/debian/patches/series
--- ukui-biometric-manager-1.0.3/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ ukui-biometric-manager-1.0.3/debian/patches/series	2022-10-14 22:35:45.0 +0300
@@ -0,0 +1 @@
+glib.patch

Processed: ukui-biometric-manager: diff for NMU version 1.0.3-1.1

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> tags 1020011 + patch
Bug #1020011 [src:ukui-biometric-manager] ukui-biometric-manager: FTBFS: 
src/giodbus.cpp:21:10: fatal error: gio-unix-2.0/gio/gunixfdlist.h: No such 
file or directory
Added tag(s) patch.
> tags 1020011 + pending
Bug #1020011 [src:ukui-biometric-manager] ukui-biometric-manager: FTBFS: 
src/giodbus.cpp:21:10: fatal error: gio-unix-2.0/gio/gunixfdlist.h: No such 
file or directory
Added tag(s) pending.

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

Bug#1021791: Testsuite needs updated permissions with PostgreSQL 15

2022-10-14 Thread Christoph Berg 
Re: To Debian Bug Tracking System
> redmine needs updating for this; one workaround for the testsuite
> would be to "grant create on schema public to public;" to revert to
> the old default.

It's not the testsuite failing; it's already the postinst failing to
install redmine.

Christoph

Bug#1021790: src:graphicsmagick: fails to migrate to testing for too long: FTBFS on mips64el

2022-10-14 Thread GCS 
Hi Paul, Marti,

On Fri, Oct 14, 2022 at 9:09 PM Paul Gevers  wrote:
> 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:graphicsmagick has been trying to migrate
> for 61 days [2]. Hence, I am filing this bug. Your package failed to
> build from source on mip64el while it built successfully there in the past.
 It's 'only' 37 days, but that's long enough even.

> 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.
 I totally agree. Then of course I've already gone on and investigated
this issue with its upstream developer. Turns out it's a regression in
src:lcms2 and already fixed in its Git HEAD. Its upstream developer
(Cc-d) noted there might be a new release soon.
How do you see it now Marti? Do you know which commit might it be so I
can ask the lcms2 maintainer to backport it to the Debian package
instead?

Thanks,
Laszlo/GCS

Processed: mayavi2: diff for NMU version 4.8.0-1.1

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> tags 1016599 + patch
Bug #1016599 [src:mayavi2] mayavi2: vtk[6,7] removal
Added tag(s) patch.
> tags 1016599 + pending
Bug #1016599 [src:mayavi2] mayavi2: vtk[6,7] removal
Added tag(s) pending.

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

Bug#1016599: mayavi2: diff for NMU version 4.8.0-1.1

2022-10-14 Thread Adrian Bunk 
Control: tags 1016599 + patch
Control: tags 1016599 + pending

Dear maintainer,

I've prepared an NMU for mayavi2 (versioned as 4.8.0-1.1) and uploaded 
it to DELAYED/15. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru mayavi2-4.8.0/debian/changelog mayavi2-4.8.0/debian/changelog
--- mayavi2-4.8.0/debian/changelog	2022-07-23 08:27:58.0 +0300
+++ mayavi2-4.8.0/debian/changelog	2022-10-14 22:16:53.0 +0300
@@ -1,3 +1,10 @@
+mayavi2 (4.8.0-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/control: python3-vtk7 -> python3-vtk9 (Closes: #1016599)
+
+ -- Adrian Bunk   Fri, 14 Oct 2022 22:16:53 +0300
+
 mayavi2 (4.8.0-1) unstable; urgency=medium
 
   * New upstream release (Closes: #997856)
diff -Nru mayavi2-4.8.0/debian/control mayavi2-4.8.0/debian/control
--- mayavi2-4.8.0/debian/control	2022-07-23 08:27:58.0 +0300
+++ mayavi2-4.8.0/debian/control	2022-10-14 22:16:53.0 +0300
@@ -16,7 +16,7 @@
python3-setuptools,
python3-traits (>= 6.3.2) ,
python3-traitsui (>= 7.2.1) ,
-   python3-vtk7,
+   python3-vtk9,
xauth,
xvfb,
 Standards-Version: 4.6.0
@@ -40,7 +40,7 @@
  python3-pygments,
  python3-traits (>= 6.3.2),
  python3-traitsui (>= 7.2.1),
- python3-vtk7,
+ python3-vtk9,
 Suggests: python3-scipy,
   ipython3
 Description: scientific visualization package for 2-D and 3-D data

Bug#1021791: Testsuite needs updated permissions with PostgreSQL 15

2022-10-14 Thread Christoph Berg 
Source: redmine
Version: 5.0.2-2
Severity: serious

PostgreSQL 15 restricts the CREATE privilege on the default "public"
schema in each database to the database owner; previous all users were
allowed to create new objects.

redmine needs updating for this; one workaround for the testsuite
would be to "grant create on schema public to public;" to revert to
the old default.

https://ci.debian.net/data/autopkgtest/testing/arm64/r/redmine/27072176/log.gz

Setting up redmine (5.0.2-2) ...
Don't run Bundler as root. Bundler can ask for sudo if it is needed, and
installing your bundle as root will break this application for all non-root
users on this machine.
dbconfig-common: writing config to 
/etc/dbconfig-common/redmine/instances/default.conf
creating postgres user redmine/instances/default:  already exists.
resetting password:  success.
creating database redmine_default: already exists.
dbconfig-common: flushing administrative password
rake aborted!
ActiveRecord::StatementInvalid: PG::InsufficientPrivilege: ERROR:  permission 
denied for schema public
LINE 1: CREATE TABLE "schema_migrations" ("version" character varyin...
 ^
/usr/share/rubygems-integration/all/gems/activerecord-6.1.7/lib/active_record/connection_adapters/postgresql/database_statements.rb:49:in
 `exec'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.7/lib/active_record/connection_adapters/postgresql/database_statements.rb:49:in
 `block (2 levels) in execute'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies/interlock.rb:48:in
 `block in permit_concurrent_loads'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/concurrency/share_lock.rb:187:in
 `yield_shares'

(Possibly this might need fixing in dbconfig-common.)

Christoph

Processed: src:graphicsmagick: fails to migrate to testing for too long: FTBFS on mips64el

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> close -1 1.4+really1.3.38+hg16739-1
Bug #1021790 [src:graphicsmagick] src:graphicsmagick: fails to migrate to 
testing for too long: FTBFS on mips64el
Marked as fixed in versions graphicsmagick/1.4+really1.3.38+hg16739-1.
Bug #1021790 [src:graphicsmagick] src:graphicsmagick: fails to migrate to 
testing for too long: FTBFS on mips64el
Marked Bug as done

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

Bug#1021790: src:graphicsmagick: fails to migrate to testing for too long: FTBFS on mips64el

2022-10-14 Thread Paul Gevers 

Source: graphicsmagick
Version: 1.4+really1.3.38-1
Severity: serious
Control: close -1 1.4+really1.3.38+hg16739-1
Tags: sid bookworm ftbfs
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:graphicsmagick has been trying to migrate 
for 61 days [2]. Hence, I am filing this bug. Your package failed to 
build from source on mip64el while it built successfully there in the past.


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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1017829: elpa-ess: emacs-gtk 28.1 install fails with installed elpa-ess

2022-10-14 Thread Dirk Eddelbuettel 


Salut Seb,

On 14 October 2022 at 20:10, Sébastien Villemot wrote:
| Hi Dirk!
| 
| Le dimanche 21 août 2022 à 09:17 -0500, Dirk Eddelbuettel a écrit :
| > That is a problem, and it is somewhat know.  ESS used to release every six 
or
| > so months, now we are many years behind with no official release.  Your best
| > bet may be to install directly from melpa and removing the package.
| > 
| > I will bring this to the ESS list but last time this was brought up 
everybody
| > more or less agreed but no release tarball was made because "it's 
complicated".
| 
| Would you be willing to consider shipping a snapshot of the git
| repository (as is available on MELPA)? This would be a temporary
| solution until upstream finally makes a formal release. Otherwise it
| looks like ESS will not be part of bookworm…

Correct.

See https://stat.ethz.ch/pipermail/ess-help/2022-September/thread.html
and _many_ earlier threads over the years bemoaning (in more polite words)
the irritating stale mate among that team and the inability to make a release
for four years now. (Mailmain archives are a pain to search but you know how
to condition a search engine to a site etc.)
 
| Shipping a git snapshot is established practice in Debian, especially
| for situations like the present one.
| 
| I am willing to help if needed.

I don't actually speak (e)lisp so I cannot help, and I have no appetite
getting into issues with upstream.

If you want to take over the package, I would welcome that and happily pass
it on to you. I was care taker for a while, but it may be time to pass that
torch on.

Amicalement,  Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1015860: libxalan2-java: CVE-2022-34169

2022-10-14 Thread Moritz Mühlenhoff 
Am Thu, Oct 13, 2022 at 09:36:09PM +0200 schrieb Markus Koschany:
> Hi,
> 
> I just had a go at this issue and I discovered that libxalan2-java in Debian 
> is
> not affected but rather bcel.
> 
> https://tracker.debian.org/pkg/bcel
> 
> The fixing commit in OpenJDK addresses the same code which is nowhere to be
> found in libxalan2-java but is present in bcel. The bcel upstream commit can 
> be
> found at
> 
> https://github.com/apache/commons-bcel/commit/f3267cbcc900f80851d561bdd16b239d936947f5
> 
> 
> I suggest to reassign the bug to bcel. I agree that libxalan2-java should be
> retired eventually. It is required by quite some reverse-dependencies though
> and it may take some time to achieve that. In theory everything should work
> without the library, because the code is in OpenJDK already?

Nice find!

> I am not sure if we should request to clarify the CVE description or at least
> post on oss-security to make other people aware of it. I assume the official
> xalan2 release ships an internal copy of bcel and that might be the reason for
> the confusion.

Yeah, I think it would be best if you were to post to oss-security about this,
then this can be picked up as a public reference to other distros (and the
URL in the list archives could be used to challenge/update the CVE ID).

Cheers,
Moritz

Bug#1021787: commons-text: CVE-2022-42889

2022-10-14 Thread Moritz Mühlenhoff 
Source: commons-text
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for commons-text.

CVE-2022-42889[0]:
| Apache Commons Text performs variable interpolation, allowing
| properties to be dynamically evaluated and expanded. The standard
| format for interpolation is "${prefix:name}", where "prefix" is used
| to locate an instance of org.apache.commons.text.lookup.StringLookup
| that performs the interpolation. Starting with version 1.5 and
| continuing through 1.9, the set of default Lookup instances included
| interpolators that could result in arbitrary code execution or contact
| with remote servers. These lookups are: - "script" - execute
| expressions using the JVM script execution engine (javax.script) -
| "dns" - resolve dns records - "url" - load values from urls, including
| from remote servers Applications using the interpolation defaults in
| the affected versions may be vulnerable to remote code execution or
| unintentional contact with remote servers if untrusted configuration
| values are used. Users are recommended to upgrade to Apache Commons
| Text 1.10.0, which disables the problematic interpolators by default.

https://www.openwall.com/lists/oss-security/2022/10/13/4

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-42889
https://www.cve.org/CVERecord?id=CVE-2022-42889

Please adjust the affected versions in the BTS as needed.

Bug#1017829: elpa-ess: emacs-gtk 28.1 install fails with installed elpa-ess

2022-10-14 Thread Sébastien Villemot 
Hi Dirk!

Le dimanche 21 août 2022 à 09:17 -0500, Dirk Eddelbuettel a écrit :
> That is a problem, and it is somewhat know.  ESS used to release every six or
> so months, now we are many years behind with no official release.  Your best
> bet may be to install directly from melpa and removing the package.
> 
> I will bring this to the ESS list but last time this was brought up everybody
> more or less agreed but no release tarball was made because "it's 
> complicated".

Would you be willing to consider shipping a snapshot of the git
repository (as is available on MELPA)? This would be a temporary
solution until upstream finally makes a formal release. Otherwise it
looks like ESS will not be part of bookworm…

Shipping a git snapshot is established practice in Debian, especially
for situations like the present one.

I am willing to help if needed.

Best wishes,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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

Processed: tagging 1013011

2022-10-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 1013011 + patch
Bug #1013011 [src:opensc] opensc: ftbfs with GCC-12
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1013011: opensc: ftbfs with GCC-12

2022-10-14 Thread Reiner Herrmann 
user debian-rele...@lists.debian.org
usertags -1 + bsp-2022-10-de-karlsruhe
thankyou

Hi,

the attached patch imported from the upstream repository fixes the FTBFS.

Kind regards,
  Reiner
From bdca5c7fe4d6f3a23287f62e0be044bef3de1974 Mon Sep 17 00:00:00 2001
From: Reiner Herrmann 
Date: Fri, 14 Oct 2022 19:27:01 +0200
Subject: [PATCH] Import upstream patch to fix pointer usage after realloc

Closes: #1013011
---
 debian/patches/gcc12.patch | 31 +++
 debian/patches/series  |  1 +
 2 files changed, 32 insertions(+)
 create mode 100644 debian/patches/gcc12.patch

diff --git a/debian/patches/gcc12.patch b/debian/patches/gcc12.patch
new file mode 100644
index ..029da4af
--- /dev/null
+++ b/debian/patches/gcc12.patch
@@ -0,0 +1,31 @@
+From 0f7082ea46562b15221f428860b993e0519c6cbd Mon Sep 17 00:00:00 2001
+From: Veronika Hanulikova 
+Date: Wed, 16 Feb 2022 11:59:27 +0100
+Bug-Debian: https://bugs.debian.org/1013011
+Subject: [PATCH] Fix usage of pointer after realloc
+
+---
+ src/sm/sm-iso.c | 5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)
+
+diff --git a/src/sm/sm-iso.c b/src/sm/sm-iso.c
+index 5baded77c6..2c3f6bcabd 100644
+--- a/src/sm/sm-iso.c
 b/src/sm/sm-iso.c
+@@ -181,13 +181,14 @@ static int format_le(size_t le, struct sc_asn1_entry *le_entry,
+ 
+ static int prefix_buf(u8 prefix, u8 *buf, size_t buflen, u8 **cat)
+ {
+-	u8 *p;
++	u8 *p = NULL;
++	int ptr_same = *cat == buf;
+ 
+ 	p = realloc(*cat, buflen + 1);
+ 	if (!p)
+ 		return SC_ERROR_OUT_OF_MEMORY;
+ 
+-	if (*cat == buf) {
++	if (ptr_same) {
+ 		memmove(p + 1, p, buflen);
+ 	} else {
+ 		/* Flawfinder: ignore */
diff --git a/debian/patches/series b/debian/patches/series
index b5adf2fc..a583014f 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 0001-Use-sysconfdir-opensc-for-opensc.conf.patch
+gcc12.patch
-- 
2.37.2

Bug#993515: bullseye is not affected

2022-10-14 Thread Timo Röhling 

Control: tags -1 + bookworm sid

As bullseye is not affected as it will never upgrade to glibc
2.34, I'm setting release tags to exclude this bug from stable
and allow the bug to be archived.

Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

Processed: bullseye is not affected

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + bookworm sid
Bug #993515 {Done: Timo Röhling } [src:catch] catch: FTBFS 
with glibc 2.34
Added tag(s) sid and bookworm.

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

Processed: tagging 1021616

2022-10-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 1021616 + sid bookworm
Bug #1021616 [obs-text-slideshow] obs-text-slideshow: FTBFS with OBS 28
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#1020108: quilt: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

2022-10-14 Thread Christoph Biedl 
Control: tags 1020108 patch

Martin Quinson wrote...

> Thanks for any help that could be provided.

Greetings from the Karlsruhe BSP.

As mentioned earlier, the build failure is a result of grep's new
warning messages. Digging closer I realized the current quote_bre()
function can no longer used that way: quilt uses the result both for
grep (now triggering the messages) and sed's search and replace (where
quoting the forward slash is crucial).

The patch attached replaces quote_bre() with two new functions
quote_bre_grep() and quote_bre_sed(), and adjusts all invocations
according to the respective need.

Test suite passes now.

Cheers,
Christoph
--- a/quilt/diff.in
+++ b/quilt/diff.in
@@ -260,7 +260,7 @@
 	# Add all files in the snapshot into the file list (they may all
 	# have changed).
 	files=( $(find $QUILT_PC/$snap_subdir -type f \
-		  | sed -e "s/^$(quote_bre $QUILT_PC/$snap_subdir/)//" \
+		  | sed -e "s/^$(quote_bre_sed $QUILT_PC/$snap_subdir/)//" \
 		  | sort) )
 	printf "%s\n" "${files[@]}" >&4
 	unset files
--- a/quilt/patches.in
+++ b/quilt/patches.in
@@ -71,7 +71,7 @@
 	# Quote each file name only once
 	for file in "${opt_files[@]}"
 	do
-		files_bre[${#files_bre[@]}]=$(quote_bre "$file")
+		files_bre[${#files_bre[@]}]=$(quote_bre_grep "$file")
 	done
 
 	# "Or" all files in a single pattern
--- a/quilt/scripts/patchfns.in
+++ b/quilt/scripts/patchfns.in
@@ -91,7 +91,15 @@
 }
 
 # Quote a string for use in a basic regular expression.
-quote_bre()
+# For use with grep.
+quote_bre_grep()
+{
+	echo "$1" | sed -e 's:\([][^$.*\\]\):\\\1:g'
+}
+
+# Quote a string for use in a basic regular expression.
+# For use with sed's search and replace.
+quote_bre_sed()
 {
 	echo "$1" | sed -e 's:\([][^$/.*\\]\):\\\1:g'
 }
@@ -227,7 +235,7 @@
 
 	if [ -e "$SERIES" ]
 	then
-		grep -q "^$(quote_bre $patch)\([ \t]\|$\)" "$SERIES"
+		grep -q "^$(quote_bre_grep $patch)\([ \t]\|$\)" "$SERIES"
 	else
 		return 1
 	fi
@@ -377,7 +385,7 @@
 {
 	local patch=$1
 	[ -e $DB ] || return 1
-	grep -q "^$(quote_bre $patch)\$" $DB
+	grep -q "^$(quote_bre_grep $patch)\$" $DB
 }
 
 applied_patches()
@@ -477,7 +485,7 @@
 	local tmpfile
 	if tmpfile=$(gen_tempfile)
 	then
-		grep -v "^$(quote_bre $patch)\$" $DB > $tmpfile
+		grep -v "^$(quote_bre_grep $patch)\$" $DB > $tmpfile
 		cat $tmpfile > $DB
 		rm -f $tmpfile
 		[ -s $DB ] || rm -f $DB
@@ -542,7 +550,7 @@
 		fi
 
 		local patch=${1#$SUBDIR_DOWN$QUILT_PATCHES/}
-		local bre=$(quote_bre "$patch")
+		local bre=$(quote_bre_sed "$patch")
 		set -- $(sed -e "/^$bre\(\|\.patch\|\.diff\?\)\(\|\.gz\|\.bz2\|\.xz\|\.lzma\|\.lz\)\([ "$'\t'"]\|$\)/!d" \
 			   -e 's/[ '$'\t''].*//' "$SERIES")
 		if [ $# -eq 1 ]
@@ -653,7 +661,7 @@
 	then
 		find "$path" -type f \
 			   -a ! -path "$(quote_glob "$path")/.timestamp" |
-		sed -e "s/$(quote_bre "$path")\///"
+		sed -e "s/$(quote_bre_sed "$path")\///"
 	fi
 }
 
--- a/quilt/upgrade.in
+++ b/quilt/upgrade.in
@@ -76,7 +76,7 @@
 
 for patch in $(applied_patches)
 do
-	proper_name="$(grep "^$(quote_bre $patch)"'\(\|\.patch\|\.diff?\)\(\|\.gz\|\.bz2\)\([ \t]\|$\)' $SERIES)"
+	proper_name="$(grep "^$(quote_bre_grep $patch)"'\(\|\.patch\|\.diff?\)\(\|\.gz\|\.bz2\)\([ \t]\|$\)' $SERIES)"
 	proper_name=${proper_name#$QUILT_PATCHES/}
 	proper_name=${proper_name%% *}
 	if [ -z "$proper_name" ]
@@ -86,7 +86,7 @@
 	fi
 
 	if [ "$patch" != "$proper_name" -a -d $QUILT_PC/$patch ] \
-	   && grep -q "^$(quote_bre $patch)\$" \
+	   && grep -q "^$(quote_bre_grep $patch)\$" \
 		   $QUILT_PC/applied-patches
 	then
 		mv $QUILT_PC/$patch $QUILT_PC/$proper_name \

Processed: Re: Bug#1020108: quilt: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> tags 1020108 patch
Bug #1020108 [src:quilt] quilt: FTBFS: dh_auto_test: error: make -j8 check 
"TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Added tag(s) patch.

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

Bug#1013510: marked as done (django-maintenancemode: FTBFS: TypeError: cannot unpack non-iterable function object)

2022-10-14 Thread Debian Bug Tracking System 
Your message dated Fri, 14 Oct 2022 15:49:05 +
with message-id 
and subject line Bug#1013510: fixed in django-maintenancemode 0.11.7+git221001-1
has caused the Debian Bug report #1013510,
regarding django-maintenancemode: FTBFS: TypeError: cannot unpack non-iterable 
function object
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.)


-- 
1013510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-maintenancemode
Version: 0.11.7-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 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 '/<>'
> dh_auto_test -- --system=custom --test-args="PYTHONPATH=. {interpreter} -m 
> pytest"
> I: pybuild base:239: PYTHONPATH=. python3.9 -m pytest
> = test session starts 
> ==
> platform linux -- Python 3.9.13, pytest-6.2.5, py-1.10.0, pluggy-1.0.0
> Django settings: maintenancemode.tests.settings (from ini file)
> rootdir: /<>, configfile: setup.cfg
> plugins: django-3.5.1
> collected 13 items
> 
> maintenancemode/tests/test_middleware.py ..FF.F..F.F.F   
> [100%]
> 
> === FAILURES 
> ===
> ___ MaintenanceModeMiddlewareTestCase.test_enabled_middleware_with_template 
> 
> 
> self = 
>  testMethod=test_enabled_middleware_with_template>
> 
> def test_enabled_middleware_with_template(self):
> # Enabling the middleware having a ``503.html`` in any of the
> # template locations should return the rendered template"
> with self.settings(MAINTENANCE_MODE=True):
> >   response = self.client.get("/")
> 
> maintenancemode/tests/test_middleware.py:52: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> /usr/lib/python3/dist-packages/django/test/client.py:836: in get
> response = super().get(path, data=data, secure=secure, **extra)
> /usr/lib/python3/dist-packages/django/test/client.py:424: in get
> return self.generic(
> /usr/lib/python3/dist-packages/django/test/client.py:541: in generic
> return self.request(**r)
> /usr/lib/python3/dist-packages/django/test/client.py:810: in request
> self.check_exception(response)
> /usr/lib/python3/dist-packages/django/test/client.py:663: in check_exception
> raise exc_value
> /usr/lib/python3/dist-packages/django/core/handlers/exception.py:55: in inner
> response = get_response(request)
> /usr/lib/python3/dist-packages/django/utils/deprecation.py:133: in __call__
> response = self.process_request(request)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> self = 
> request = 
> 
> def process_request(self, request):
> # Allow access if middleware is not activated
> allow_staff = getattr(settings, "MAINTENANCE_ALLOW_STAFF", True)
> allow_superuser = getattr(settings, "MAINTENANCE_ALLOW_SUPERUSER", 
> True)
> 
> if not (settings.MAINTENANCE_MODE or maintenance.status()):
> return None
> 
> INTERNAL_IPS = maintenance.IPList(settings.INTERNAL_IPS)
> 
> # Preferentially check HTTP_X_FORWARDED_FOR b/c a proxy
> # server might have obscured REMOTE_ADDR
> for ip in request.META.get("HTTP_X_FORWARDED_FOR", "").split(","):
> if ip.strip() in INTERNAL_IPS:
> return None
> 
> # Allow access if remote ip is in INTERNAL_IPS
> if request.META.get("REMOTE_ADDR") in INTERNAL_IPS:
> return None
> 
> # Allow access if the user doing the request is logged in and a
> # staff member.
> if hasattr(request, "user"):
> if allow_staff and request.user.is_staff:
> return None
> 
> if allow_superuser and request.user.is_superuser:
> return None
> 
> # Check if a path is explicitly excluded from maintenance mode
> for url in IGNORE_URLS:
> if url.match(request.path_info):
> return None
> # Otherwise show the user the 503 page
> 
> if DJANGO_VERSION_MAJOR >= 3 and DJANGO_VERSION_MINOR >= 2:
> # Checks if DJANGO version is great than 3.2.0 for breaking change
> resolver = resolvers.get_resolver(None)
> resolve =

Bug#1015024: marked as done (device-tree-compiler: FTBFS: LookupError: setuptools-scm was unable to detect version for /<>.)

2022-10-14 Thread Debian Bug Tracking System 
Your message dated Fri, 14 Oct 2022 15:48:56 +
with message-id 
and subject line Bug#1015024: fixed in device-tree-compiler 1.6.1-3
has caused the Debian Bug report #1015024,
regarding device-tree-compiler: FTBFS: LookupError: setuptools-scm was unable 
to detect version for /<>.
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.)


-- 
1015024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: device-tree-compiler
Version: 1.6.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> make[3]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
> rule.
> x86_64-linux-gnu-gcc -g -Os -fPIC -Werror -Wall -Wpointer-arith -Wcast-qual 
> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls 
> -Wshadow -Wno-error -I/usr/include/valgrind  -Wdate-time -D_FORTIFY_SOURCE=2 
> -I libfdt -I . -Wl,-z,relro -Wl,-z,now  -o convert-dtsv0 srcpos.o util.o 
> convert-dtsv0-lexer.lex.o
> set -e; echo 'CHK version_gen.h'; mkdir -p ./;(echo "#define 
> DTC_VERSION \"DTC 1.6.1\""; ) < Makefile > version_gen.h.tmp; if [ -r 
> version_gen.h ] && cmp -s version_gen.h version_gen.h.tmp; then rm -f 
> version_gen.h.tmp; else echo '   UPD version_gen.h'; mv -f 
> version_gen.h.tmp version_gen.h; fi;
>   CHK version_gen.h
> x86_64-linux-gnu-gcc -g -Os -fPIC -Werror -Wall -Wpointer-arith -Wcast-qual 
> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls 
> -Wshadow -Wno-error -I/usr/include/valgrind  -Wdate-time -D_FORTIFY_SOURCE=2 
> -I libfdt -I . -Wl,-z,relro -Wl,-z,now  -o fdtdump fdtdump.o util.o 
> x86_64-linux-gnu-gcc -Wdate-time -D_FORTIFY_SOURCE=2 -I libfdt -I . -g -Os 
> -fPIC -Werror -Wall -Wpointer-arith -Wcast-qual -Wnested-externs 
> -Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls -Wshadow 
> -Wno-error -I/usr/include/valgrind  -o libfdt/fdt_overlay.o -c 
> libfdt/fdt_overlay.c
> x86_64-linux-gnu-gcc -Wl,-z,relro -Wl,-z,now -fPIC -shared 
> -Wl,--version-script=libfdt/version.lds -Wl,-soname,libfdt.so.1 -o 
> libfdt/libfdt-1.6.1.so \
>   libfdt/fdt.o libfdt/fdt_ro.o libfdt/fdt_wip.o libfdt/fdt_sw.o 
> libfdt/fdt_rw.o libfdt/fdt_strerror.o libfdt/fdt_empty_tree.o 
> libfdt/fdt_addresses.o libfdt/fdt_overlay.o libfdt/fdt_check.o
> ar rv libfdt/libfdt.a libfdt/fdt.o libfdt/fdt_ro.o libfdt/fdt_wip.o 
> libfdt/fdt_sw.o libfdt/fdt_rw.o libfdt/fdt_strerror.o libfdt/fdt_empty_tree.o 
> libfdt/fdt_addresses.o libfdt/fdt_overlay.o libfdt/fdt_check.o
> ar: creating libfdt/libfdt.a
> a - libfdt/fdt.o
> a - libfdt/fdt_ro.o
> a - libfdt/fdt_wip.o
> a - libfdt/fdt_sw.o
> a - libfdt/fdt_rw.o
> a - libfdt/fdt_strerror.o
> a - libfdt/fdt_empty_tree.o
> a - libfdt/fdt_addresses.o
> a - libfdt/fdt_overlay.o
> a - libfdt/fdt_check.o
> ln -sf libfdt-1.6.1.so libfdt/libfdt.so.1
> x86_64-linux-gnu-gcc -g -Os -fPIC -Werror -Wall -Wpointer-arith -Wcast-qual 
> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls 
> -Wshadow -Wno-error -I/usr/include/valgrind  -Wdate-time -D_FORTIFY_SOURCE=2 
> -I libfdt -I . -Wl,-z,relro -Wl,-z,now  -o fdtget fdtget.o util.o 
> libfdt/libfdt-1.6.1.so 
> x86_64-linux-gnu-gcc -g -Os -fPIC -Werror -Wall -Wpointer-arith -Wcast-qual 
> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls 
> -Wshadow -Wno-error -I/usr/include/valgrind  -Wdate-time -D_FORTIFY_SOURCE=2 
> -I libfdt -I . -Wl,-z,relro -Wl,-z,now  -o fdtoverlay fdtoverlay.o util.o 
> libfdt/libfdt-1.6.1.so 
> x86_64-linux-gnu-gcc -g -Os -fPIC -Werror -Wall -Wpointer-arith -Wcast-qual 
> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls 
> -Wshadow -Wno-error -I/usr/include/valgrind  -Wdate-time -D_FORTIFY_SOURCE=2 
> -I libfdt -I . -Wl,-z,relro -Wl,-z,now  -o dtc dtc.o checks.o data.o 
> flattree.o fstree.o livetree.o srcpos.o treesource.o util.o yamltree.o 
> dtc-lexer.lex.o dtc-parser.tab.o -lyaml
> ar rv libfdt/libfdt.a libfdt/fdt.o libfdt/fdt_ro.o libfdt/fdt_wip.o 
> libfdt/fdt_sw.o libfdt/fdt_rw.o libfdt/fdt_strerror.o libfdt/fdt_empty_tree.o 
> libfdt/fdt_addresses.o libfdt/fdt_overlay.o libfdt/fdt_check.o
> x86_64-linux-gnu-gcc -g -Os -fPIC -Werror -Wall -Wpointer-arith -Wcast-qual 
> -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls 
> -Wshadow -Wno-error

Bug#1013510: marked as pending in django-maintenancemode

2022-10-14 Thread Scott Kitterman 
Control: tag -1 pending

Hello,

Bug #1013510 in django-maintenancemode 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/django-maintenancemode/-/commit/4a0af6b90f769d79aab16c0167e9555f17552d43


New upstream git snapshot (Closes: #1013510)

* New upstream git snapshot (Closes: #1013510)
* Delete debian/patches,
  0001-Fix-deprecation-warning-for-django.conf.urls.url.patch and
  0002-Adjust-test-setup-to-work-with-Django-3.patch incorporated upstream


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013510

Processed: Bug#1013510 marked as pending in django-maintenancemode

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #1013510 [src:django-maintenancemode] django-maintenancemode: FTBFS: 
TypeError: cannot unpack non-iterable function object
Added tag(s) pending.

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

Processed: Bug#1013510 marked as pending in django-maintenancemode

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #1013510 [src:django-maintenancemode] django-maintenancemode: FTBFS: 
TypeError: cannot unpack non-iterable function object
Ignoring request to alter tags of bug #1013510 to the same tags previously set

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

Bug#1013510: marked as pending in django-maintenancemode

2022-10-14 Thread Scott Kitterman 
Control: tag -1 pending

Hello,

Bug #1013510 in django-maintenancemode 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/django-maintenancemode/-/commit/4a0af6b90f769d79aab16c0167e9555f17552d43


New upstream git snapshot (Closes: #1013510)

* New upstream git snapshot (Closes: #1013510)
* Delete debian/patches,
  0001-Fix-deprecation-warning-for-django.conf.urls.url.patch and
  0002-Adjust-test-setup-to-work-with-Django-3.patch incorporated upstream


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013510

Bug#1017845: Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-.el

2022-10-14 Thread Axel Beckert 
Hi again,

Axel Beckert wrote:
> And just for the record: This only happens on some of my hosts. I have
> several hosts (also with a lot of elpa plugins, but probably still not
> as many as on the host where it happens reproducibly) where the
> upgrade from 27.x to 28.x worked fine on the first run.
> 
> It seems that those hosts with this issue are desktops or laptops with
> emacs-gtk installed while others are VMs or Raspberry Pi based servers
> where I only install emacs-lucid or emacs-nox and also no unnecessary
> desktop bloat like dbus, etc.

One counter argument: I have one Thinkpad which has emacs-gtk, dbus
and systemd and there it doesn't happen either.

So maybe that desktop criteria was a red herring.

If I find time, I'll try to figure out if there are elpa package which
are solely installed on those boxes where it happens. Maybe we find
the culprit that way.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#1021736: marked as done (rake-compiler: autopkgtest regression: cannot load such file -- rspec/core/rake_task)

2022-10-14 Thread Debian Bug Tracking System 
Your message dated Fri, 14 Oct 2022 14:46:56 +
with message-id 
and subject line Bug#1021736: fixed in rake-compiler 1.2.0-3
has caused the Debian Bug report #1021736,
regarding rake-compiler: autopkgtest regression: cannot load such file -- 
rspec/core/rake_task
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.)


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

Source: rake-compiler
Version: 1.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
rake-compiler  from testing1.2.0-2
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=rake-compiler

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rake-compiler/27031948/log.gz


┌──┐
│ Run tests for ruby3.0 from debian/ruby-tests.rake 
  │

└──┘

RUBYLIB=. GEM_PATH= ruby3.0 -S rake -f debian/ruby-tests.rake
mv lib ./.gem2deb.lib
rake aborted!
LoadError: cannot load such file -- rspec/core/rake_task
:85:in 
`require'
:85:in 
`require'
:85:in 
`require'
:85:in 
`require'
/tmp/autopkgtest-lxc.0998j3a0/downtmp/build.P4x/src/debian/ruby-tests.rake:1:in 
`'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in 
`'

(See full trace by running task with --trace)
mv ./.gem2deb.lib lib
autopkgtest [15:16:58]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: rake-compiler
Source-Version: 1.2.0-3
Done: Cédric Boutillier 

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated rake-compiler 
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: Fri, 14 Oct 2022 15:58:23 +0200
Source: rake-compiler
Architecture: source
Version: 1.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Cédric Boutillier 
Closes: 1021736
Changes:
 rake-compiler (1.2.0-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Debian Janitor ]
   * Bump debhelper from old 12 to 13.
   * Update standards version to 4.6.1, no changes needed.
 .
   [ Cédric Boutillier ]
   * Add build-deps to packages needed for autopkgtest (Closes: #1021736)
Checksums-Sha1:
 b0f35f068ace353b48d72ab7a15e4b0754b0b787 1561 rake-compiler_1.2.0-3.dsc
 4d8708a9dc549c797d98bdaffb40284a4ed634f5 5044 
rake-compiler_1.2.0-3.debian.tar.xz
 4ccb408f1d891bbea28462de24fe497c7649dfab 9303 
rake-compiler_1.2.0-3_amd64.buildinfo
Checksums-Sha256:
 55590465cbbe070a2bf2edb58caf0bad864f3f28e9ba6597120900ddc7fa718b 1561 
rake-compiler_1.2.0-3.dsc
 548c7bdd65c4148305a189a29a122872d823f33d70017328012f9ae005f362bd 5044 
rake-compiler_1.2.0-3.debian.tar.xz
 d9757b8e137c62d7760a90abf02e0eaf27c223b1b3cc813dd3305be18c54a4ef 9303 
rake-compiler_1.2.0-3_amd64.buildinfo
Files:
 b6ff3d9c825bfdfd31e1669d7e79e8c0 1561 ruby optional rake-compiler_1.2.0-3.dsc
 e93d450d35e95f874790b58d5c8b0a53 5044 ruby optional 
rake-compiler_1.2.0-3.debian.tar.xz
 c643e08266f4d4b8ce257f89467f1a2c 9303 ruby optional 
rake-compiler_1.2.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1013492: marked as pending in nanoc

2022-10-14 Thread Cédric Boutillier 
Control: tag -1 pending

Hello,

Bug #1013492 in nanoc 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/ruby-team/nanoc/-/commit/305891baf59313fefeb4c9fd76e776596a4dec8e


Do not run tests with ruby-coffeescript (Closes: #1013492)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013492

Processed: Bug#1013492 marked as pending in nanoc

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #1013492 [src:nanoc] nanoc: FTBFS: ERROR: Test "ruby3.0" failed. Exiting.
Added tag(s) pending.

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

Bug#1021774: cross-toolchain-base-mipsen: duplicated ld.so.1 in multiple packages

2022-10-14 Thread Andreas Beckmann 
Source: cross-toolchain-base-mipsen
Version: 20
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

several ld.so.1 variants are shipped by two packages that are not
conflicting with each other:

libc6-mips32-mips64-cross=2.35-3cross1
libc6-mips64-cross=2.35-3cross1
usr/mips64-linux-gnuabi64/lib/ld.so.1
libc6-mips32-mips64el-cross=2.35-3cross1
libc6-mips64el-cross=2.35-3cross1
usr/mips64el-linux-gnuabi64/lib/ld.so.1
libc6-mips32-mips64r6-cross=2.35-3cross1
libc6-mips64r6-cross=2.35-3cross1
usr/mipsisa64r6-linux-gnuabi64/lib/ld-linux-mipsn8.so.1
libc6-mips32-mips64r6el-cross=2.35-3cross1
libc6-mips64r6el-cross=2.35-3cross1
usr/mipsisa64r6el-linux-gnuabi64/lib/ld-linux-mipsn8.so.1
libc6-mips32-mipsn32-cross=2.35-3cross1
libc6-mipsn32-cross=2.35-3cross1
usr/mips64-linux-gnuabin32/lib/ld.so.1
libc6-mips32-mipsn32el-cross=2.35-3cross1
libc6-mipsn32el-cross=2.35-3cross1
usr/mips64el-linux-gnuabin32/lib/ld.so.1
libc6-mips32-mipsn32r6-cross=2.35-3cross1
libc6-mipsn32r6-cross=2.35-3cross1
usr/mipsisa64r6-linux-gnuabin32/lib/ld-linux-mipsn8.so.1
libc6-mips32-mipsn32r6el-cross=2.35-3cross1
libc6-mipsn32r6el-cross=2.35-3cross1
usr/mipsisa64r6el-linux-gnuabin32/lib/ld-linux-mipsn8.so.1


Andreas

Bug#962650: libcamera now maintaines proper sonames

2022-10-14 Thread Rafael Diniz 
Upstream libcamera now properly sets soname version and bumps it for ABI 
changes.


Relevant commits in upstream:

utils: Provide a release script
https://git.libcamera.org/libcamera/libcamera.git/commit/?id=fc46d091231e22f47e2056fb854ddf4a999d606a

utils: semver: Add version helper
https://git.libcamera.org/libcamera/libcamera.git/commit/?id=1bd14fc8954425ac310d24876c6257f0b80c4880

meson: Shared Object version handling
https://git.libcamera.org/libcamera/libcamera.git/commit/?id=0aac297afd0cf2748c20f919bdd8d5e390b8d9a8

Kind regards,
Rafael Diniz



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1015125: marked as done (trove-dashboard: FTBFS: ImportError: cannot import name 'ugettext_lazy' from 'django.utils.translation' (/usr/lib/python3/dist-packages/django/utils/translation/__init__.p

2022-10-14 Thread Debian Bug Tracking System 
Your message dated Fri, 14 Oct 2022 14:45:35 +0200
with message-id <78a3aa9e-f321-251b-41d6-78781908b...@debian.org>
and subject line This was fixed
has caused the Debian Bug report #1015125,
regarding trove-dashboard: FTBFS: ImportError: cannot import name 
'ugettext_lazy' from 'django.utils.translation' 
(/usr/lib/python3/dist-packages/django/utils/translation/__init__.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.)


-- 
1015125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trove-dashboard
Version: 18.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 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[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e ; for i in 3.9 3.10 ; do \
>   NOSE_WITH_OPENSTACK=1 \
>   NOSE_OPENSTACK_COLOR=1 \
>   NOSE_OPENSTACK_RED=0.05 \
>   NOSE_OPENSTACK_YELLOW=0.025 \
>   NOSE_OPENSTACK_SHOW_ELAPSED=1 \
>   DJANGO_SETTINGS_MODULE=trove_dashboard.test.settings \
>   python3 -m coverage run \
>   /<>/manage.py test -v 2 trove_dashboard 
> --settings=trove_dashboard.test.settings ; \
> done
> Creating test database for alias 'default' 
> ('file:memorydb_default?mode=memory=shared')...
> Found 17 test(s).
> Operations to perform:
>   Synchronize unmigrated apps: admin, compressor, database_backups, 
> database_clusters, database_configurations, databases, horizon, humanize, 
> identity, messages, openstack_auth, openstack_dashboard, project, settings, 
> staticfiles
>   Apply all migrations: auth, contenttypes, sessions
> Synchronizing apps without migrations:
>   Creating tables...
> Creating table openstack_auth_user
> Running deferred SQL...
> Running migrations:
>   Applying contenttypes.0001_initial... OK
>   Applying contenttypes.0002_remove_content_type_name... OK
>   Applying auth.0001_initial... OK
>   Applying auth.0002_alter_permission_name_max_length... OK
>   Applying auth.0003_alter_user_email_max_length... OK
>   Applying auth.0004_alter_user_username_opts... OK
>   Applying auth.0005_alter_user_last_login_null... OK
>   Applying auth.0006_require_contenttypes_0002... OK
>   Applying auth.0007_alter_validators_add_error_messages... OK
>   Applying auth.0008_alter_user_username_max_length... OK
>   Applying auth.0009_alter_user_last_name_max_length... OK
>   Applying auth.0010_alter_group_name_max_length... OK
>   Applying auth.0011_update_proxy_permissions... OK
>   Applying auth.0012_alter_user_first_name_max_length... OK
>   Applying sessions.0001_initial... OK
> Destroying test database for alias 'default' 
> ('file:memorydb_default?mode=memory=shared')...
> Traceback (most recent call last):
>   File "/<>/manage.py", line 23, in 
> execute_from_command_line(sys.argv)
>   File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
> line 446, in execute_from_command_line
> utility.execute()
>   File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
> line 440, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File 
> "/usr/lib/python3/dist-packages/django/core/management/commands/test.py", 
> line 24, in run_from_argv
> super().run_from_argv(argv)
>   File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
> 414, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
> 460, in execute
> output = self.handle(*args, **options)
>   File 
> "/usr/lib/python3/dist-packages/django/core/management/commands/test.py", 
> line 68, in handle
> failures = test_runner.run_tests(test_labels)
>   File "/usr/lib/python3/dist-packages/django/test/runner.py", line 1006, in 
> run_tests
> self.run_checks(databases)
>   File "/usr/lib/python3/dist-packages/django/test/runner.py", line 925, in 
> run_checks
> call_command("check", verbosity=self.verbosity, databases=databases)
>   File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
> line 198, in call_command
> return command.execute(*args, **defaults)
>   File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
> 460, in execute
> output =

Processed: Re: Bug#1017845: Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> found -1 1:28.2+1-1
Bug #1017845 [emacs-common] emacs-common: Endless fork loop at installation and 
at run time: /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-_{scroll_other_window,delete_frame}_0-.el
Bug #1017817 [emacs-common] emacs: new release seems to have funny ideas about 
byte-compiling process
Marked as found in versions emacs/1:28.2+1-1.
Marked as found in versions emacs/1:28.2+1-1.

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

Bug#1017845: Endless fork loop at installation time: /usr/bin/emacs --batch -l /tmp/emacs-int-comp-subr--trampoline-7363726f6c6c2d6f746865722d77696e646f77_scroll_other_window_0-.el

2022-10-14 Thread Axel Beckert 
Control: found -1 1:28.2+1-1

Hi Sean,

Sean Whitton wrote:
> On Sun 21 Aug 2022 at 02:46PM +02, Axel Beckert wrote:
> > Version: 1:28.1+1-2
[…]
> > upgrading emacs respectively emacs-gtk from 27.1 to 28.1 causes an
> > endless fork loops during package configuration time:
> 
> Are you able to reproduce this with what's in sid at present?

Oh, a new upstream release! Let's try… :-)

Nothing obvious in the output of apt:

Setting up emacs-el (1:28.2+1-1) ...
Setting up emacs-common (1:28.2+1-1) ...
Setting up emacs-bin-common (1:28.2+1-1) ...
Setting up emacs-gtk (1:28.2+1-1) ...
Deep recursion on subroutine 
"main::generate_relevant_tsort_dependencies_internals" at 
/usr/lib/emacsen-common/lib.pl line 127.
Install a2ps for emacs
Install develock-el for emacs
Install ecb for emacs
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
Install haml-elisp for emacs
Skipping byte-compilation for emacs: Not supported
Install post-el for emacs
Install pylint for emacs
Install quilt-el for emacs
Install ratpoison for emacs
Install rdtool-elisp for emacs
Install sawfish for emacs
Install whizzytex for emacs
Install elpa-gitignore-mode for emacs
install/gitignore-mode-1.4.0: Handling install of emacsen flavor emacs
install/gitignore-mode-1.4.0: byte-compiling for emacs

But unfortunately, it's still reproducible:

11054 root20   0  2724   960   864 S   0.0  0.0  0:00.00 │  │ │  └─ 
/bin/sh /var/lib/dpkg/info/emacs-gtk.postinst configure 1:27.1+1-3.1+b1 

   
11058 root20   0 20372 14448  4916 S   0.0  0.0  0:00.29 │  │ │ 
└─ /usr/bin/perl -w /usr/lib/emacsen-common/emacs-install emacs
11377 root20   0 0 0 0 Z   0.0  0.0  0:00.00 │  │ │ 
   ├─ emacs-install
11438 root20   0  2724   960   864 S   0.0  0.0  0:00.00 │  │ │ 
   └─ /bin/sh /usr/lib/emacsen-common/packages/install/elpa-gitignore-mode emacs
11439 root20   0  2724   956   864 S   0.0  0.0  0:00.00 │  │ │ 
  └─ /bin/sh /usr/lib/dh-elpa/helper/install emacs gitignore-mode 1.4.0
11442 root20   0  2724   112 0 S   0.0  0.0  0:00.00 │  │ │ 
 └─ /bin/sh /usr/lib/dh-elpa/helper/install emacs gitignore-mode 1.4.0
11443 root20   0  168M 58500 36544 S   0.0  0.1  0:00.58 │  │ │ 
└─ emacs --quick --batch -l package --eval (setq package-user-dir 
"/nonexistent") --eval (add-to-list 'package-directory-list 
"/usr/share/emacs/site-lisp/elpa-src") -f package-initialize -f 
batch-byte-compile gitignore-mode-aut
11444 root20   0  170M 61168 36708 S   0.0  0.1  0:02.24 │  │ │ 
   └─ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-63616c6c2d696e7465726163746976656c79_call_interactively_0-VtJDks.el
11448 root20   0  170M 60524 36284 S   0.0  0.1  0:01.97 │  │ │ 
  └─ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-Wu7AW4.el
11449 root20   0  170M 61244 36792 S   0.0  0.1  0:02.01 │  │ │ 
 └─ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-XKbTq1.el
11450 root20   0  170M 61200 36744 S   0.0  0.1  0:02.07 │  │ │ 
└─ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-2Zc2GB.el
11453 root20   0  170M 61176 36728 S   0.0  0.1  0:02.02 │  │ │ 
   └─ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-Ro5jje.el
11454 root20   0  170M 61308 36852 S   0.0  0.1  0:02.14 │  │ │ 
  └─ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-2uNzTS.el
11461 root20   0  170M 61192 36736 S   0.0  0.1  0:02.01 │  │ │ 
 └─ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-Ex5VpA.el
11462 root20   0  170M 60696 36456 S   0.0  0.1  0:02.03 │  │ │ 
└─ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-Q91LV9.el
11463 root20   0  170M 61228 36776 S   0.0  0.1  0:02.01 │  │ │ 
   └─ /usr/bin/emacs --batch -l 
/tmp/emacs-int-comp-subr--trampoline-64656c6574652d6672616d65_delete_frame_0-boXgPR.el
11469 root20   0  170M 61184 36724 S   0.0  0.1  0:02.00 │  │ │ 
  └─ /usr/bin/emacs --batch -l

Processed: Re: Bug#1017711: emacs-gtk: terminated with signal SIGABRT, 137 MB coredump

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> found -1 1:28.2+1-1
Bug #1017711 [emacs-gtk] emacs-gtk: terminated with signal SIGABRT, 137 MB 
coredump
Marked as found in versions emacs/1:28.2+1-1.

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

Bug#1017711: emacs-gtk: terminated with signal SIGABRT, 137 MB coredump

2022-10-14 Thread Vincent Lefevre 
Control: found -1 1:28.2+1-1

Hi,

On 2022-10-13 22:28:24 -0700, Sean Whitton wrote:
> Can you reproduce this with what's in sid now?

Yes, this still occurs:

zira% ls -lh
total 41M
-rw--- 1 vinc17 vinc17 43M 2022-10-14 12:49:40 core

Core was generated by `/usr/bin/emacs --batch -l 
/tmp/emacs-async-comp-url-cookie.el-A86dRV.el'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7f59efe8957c in ?? () from /lib/x86_64-linux-gnu/libc.so.6

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1020987: marked as done (barrier FTBFS with nocheck: missing gtest)

2022-10-14 Thread Debian Bug Tracking System 
Your message dated Fri, 14 Oct 2022 10:49:15 +
with message-id 
and subject line Bug#1020987: fixed in barrier 2.4.0+dfsg-3
has caused the Debian Bug report #1020987,
regarding barrier FTBFS with nocheck: missing gtest
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.)


-- 
1020987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: barrier
Version: 2.4.0+dfsg-2
Tags: ftbfs
Severity: serious
Justification: last RT meeting, elbrus and ginggs said nocheck FTBFS should be 
serious
X-Debbugs-Cc: elb...@debian.org

Hi,

barrier fails to build from source when enabling the nocheck build
profile. The cmake stuff fails hard when it misses gtest, which happens
to be annotated . There probably is some flag involved for
actually removing this requirement. Failing that, the annotation on
gtest should be reverted.

Helmut
--- End Message ---
--- Begin Message ---
Source: barrier
Source-Version: 2.4.0+dfsg-3
Done: Unit 193 

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

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated barrier 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: SHA384

Format: 1.8
Date: Fri, 14 Oct 2022 06:00:18 -0400
Source: barrier
Architecture: source
Version: 2.4.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Unit 193 
Changed-By: Unit 193 
Closes: 1020987
Changes:
 barrier (2.4.0+dfsg-3) unstable; urgency=medium
 .
   * d/p/allow_gtest_exclusion.patch:
 - Allow exclusion of gtest if not building tests. (Closes: #1020987)
Checksums-Sha1:
 8bac2f7e0e84966156700727add54af1d0ffea73 2441 barrier_2.4.0+dfsg-3.dsc
 71951a99e2e218eb1519b76f9d3e032e773a6259 138560 
barrier_2.4.0+dfsg.orig-gulrak-filesystem.tar.xz
 aaf21f275d759929fc223c0cce23ff19f707098e 890764 barrier_2.4.0+dfsg.orig.tar.xz
 7a66abbb715d5fb71a577f23d4936603e3c8b10b 5456 
barrier_2.4.0+dfsg-3.debian.tar.xz
 d988a1ab0de0f958dd80464466b11b1008c3eeb9 11651 
barrier_2.4.0+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 9fd610fc09ae01abe4f5966573f749a4c457329d3f571be09c1b9d23fa343b6e 2441 
barrier_2.4.0+dfsg-3.dsc
 22b9f4243707f65dbbb10055a6d2a905d03847953d1497e753b38841d7bc0996 138560 
barrier_2.4.0+dfsg.orig-gulrak-filesystem.tar.xz
 ee54524fc9530248fbd7289adc05de15a4fac756c2c38dd9779f2451a9924bf3 890764 
barrier_2.4.0+dfsg.orig.tar.xz
 30b6e943e8c260e491596cd4337ee322fd1aa1b447238fcf574cf30e9bc770d2 5456 
barrier_2.4.0+dfsg-3.debian.tar.xz
 46bd0e2de6ca8d4d6ebfdd57e0315d172b1b0e51c596b0eff42b79da07721d88 11651 
barrier_2.4.0+dfsg-3_amd64.buildinfo
Files:
 9d2f6ef2cfd4474dbbe7d145f98e6689 2441 x11 optional barrier_2.4.0+dfsg-3.dsc
 11896572037f29c94c476dc448889d0c 138560 x11 optional 
barrier_2.4.0+dfsg.orig-gulrak-filesystem.tar.xz
 dcd26c7df58ac8f3454eba8870f88bc0 890764 x11 optional 
barrier_2.4.0+dfsg.orig.tar.xz
 6203a590fa5df7ef3fa9fd9e5f9733c6 5456 x11 optional 
barrier_2.4.0+dfsg-3.debian.tar.xz
 9b80563054347819609832d632a6faf0 11651 x11 optional 
barrier_2.4.0+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCQAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmNJOS4ACgkQUAHhsJqj
dEvY6BAA63wu/JKjN1qDZbGe40592ptbhWb8DnfTA/uCIFC/Cs4/1NJ6b/H46wfp
D0rETwlFklyS79FG66zxzucUveWsUp+ip6GadFNwWCdVgyn5raJ9XJb2vdkDU7ND
dZ+LuoPX8PSV8bKe5Vi3cnnSvkZjHPY/EkAzMrG+Re05TfjSf/3WYRpMDi4RG1DI
P+cxkUIDZxEgiuhy4abqpV7Xsvk94te7EZcPmiZmCW7pyZvymZI92rmwMP0TGSyP
NgZNx1OjjJaRJnW9wmG2LhmBFHROG3L7YExJvsNGUotYtcSmEBNqXJJDnut2cduT
dOn3mHFy2RLFE1DqIz+EA+mH9VDuPZ98htSMLPZ/OKAzcGK9KvjgcMc0pvNuR3s+
X5SfAKKlJTYZFuRhm6LDdzLKNzCz5yri0eN1Xy9q5FWR6nHJqWB5fbOcVR90RDFk
dpKIkIFrrVy9T6zJq1lvR2+sE03lvRVR36vy1gXjS/MA2TF5MLMTzj1iq92zZ5Gv
4Gk5kp1TfXZytnLsvAX7gxnyCCx5NrSJPDK1QdFihX0r44OsIVUXJH+COWhJKjRP
rLtohH34JOgN1BrhjI8bn4e1QtizNXR0+Z1QhYYGtsKtJtPOk42XsKXYD7OAzOM7
/JlPcsSNs3OolBI2QLh+2Z6syV5kdhANbj1vHVNFidiUQ36SASY=
=cnPJ
-END PGP SIGNATURE End Message ---

Processed: reassign 1021732 to mat2

2022-10-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 1021732 mat2 0.13.0-1
Bug #1021732 [src:libimage-exiftool-perl, src:mat2] libimage-exiftool-perl 
breaks mat2 autopkgtest: 'ColorProfiles' not found in ...
Bug reassigned from package 'src:libimage-exiftool-perl, src:mat2' to 'mat2'.
No longer marked as found in versions libimage-exiftool-perl/12.47+dfsg-1 and 
mat2/0.13.0-1.
Ignoring request to alter fixed versions of bug #1021732 to the same values 
previously set
Bug #1021732 [mat2] libimage-exiftool-perl breaks mat2 autopkgtest: 
'ColorProfiles' not found in ...
Marked as found in versions mat2/0.13.0-1.
> thanks
Stopping processing here.

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

Bug#1021732: [Pkg-privacy-maintainers] Bug#1021732: libimage-exiftool-perl breaks mat2 autopkgtest: 'ColorProfiles' not found in ...

2022-10-14 Thread Georg Faerber 
Control: forwarded -1 https://0xacab.org/jvoisin/mat2/-/issues/178
Control: tags -1 + fixed-upstream upstream

Hi Paul,

On 22-10-13 19:52:35, Paul Gevers wrote:
> With a recent upload of libimage-exiftool-perl the autopkgtest of mat2
> fails in testing when that autopkgtest is run with the binary packages
> of libimage-exiftool-perl from unstable.

Thanks for your report.

Cheers,
Georg

Processed: Re: [Pkg-privacy-maintainers] Bug#1021732: libimage-exiftool-perl breaks mat2 autopkgtest: 'ColorProfiles' not found in ...

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> forwarded -1 https://0xacab.org/jvoisin/mat2/-/issues/178
Bug #1021732 [src:libimage-exiftool-perl, src:mat2] libimage-exiftool-perl 
breaks mat2 autopkgtest: 'ColorProfiles' not found in ...
Set Bug forwarded-to-address to 'https://0xacab.org/jvoisin/mat2/-/issues/178'.
> tags -1 + fixed-upstream upstream
Bug #1021732 [src:libimage-exiftool-perl, src:mat2] libimage-exiftool-perl 
breaks mat2 autopkgtest: 'ColorProfiles' not found in ...
Added tag(s) upstream and fixed-upstream.

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

Bug#1021769: osmo-sgsn: FTBFS if systemd is in build environment

2022-10-14 Thread Gianfranco Costamagna 

Source: osmo-sgsn
Version: 1.9.0+dfsg1-2
Severity: serious

Hello, as already seen in #1010578 this package suffers of a similar issue when 
systemd is in build environment.

Can you please also apply the patch on this package?
I can trigger an rb build to show the failure there too if needed.

Thanks!

Gianfranco

diff -Nru osmo-sgsn-1.9.0+dfsg1/debian/changelog 
osmo-sgsn-1.9.0+dfsg1/debian/changelog
--- osmo-sgsn-1.9.0+dfsg1/debian/changelog  2022-10-13 22:27:32.0 
+0200
+++ osmo-sgsn-1.9.0+dfsg1/debian/changelog  2022-10-14 11:11:17.0 
+0200
@@ -1,3 +1,9 @@
+osmo-sgsn (1.9.0+dfsg1-3) unstable; urgency=medium
+
+  * Fix build failure with installed systemd (Closes: #-1)
+
+ -- Gianfranco Costamagna   Fri, 14 Oct 2022 
11:11:17 +0200
+
 osmo-sgsn (1.9.0+dfsg1-2) unstable; urgency=medium
 
   * upload to unstable

diff -Nru osmo-sgsn-1.9.0+dfsg1/debian/rules osmo-sgsn-1.9.0+dfsg1/debian/rules
--- osmo-sgsn-1.9.0+dfsg1/debian/rules  2022-10-13 22:27:32.0 +0200
+++ osmo-sgsn-1.9.0+dfsg1/debian/rules  2022-10-14 11:11:16.0 +0200
@@ -33,6 +33,10 @@
 override_dh_auto_test:
dh_auto_test || (find . -name testsuite.log -exec cat {} \; ; false)
 
+override_dh_auto_configure:

+   # Use the packaging-provided systemd unit file
+   dh_auto_configure -- --with-systemdsystemunitdir=no
+
 override_dh_installsystemd:
dh_installsystemd --no-enable --no-start
 


OpenPGP_signature
Description: OpenPGP digital signature

Processed: [ROM] racon: Please remove for 32 bit architectures (armel, armhf, i386, mipsel, hppa, m68k, powerpc, sh4, x32) (Was: Bug#1021755: racon: build-dependencies unsatisfiable on 32-bit.)

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> retitle -1 [ROM] racon: Please remove for 32 bit architectures (armel, armhf, 
> i386, mipsel, hppa, m68k, powerpc, sh4, x32)
Bug #1021755 [racon] racon: build-dependencies unsatisfiable on 32-bit.
Changed Bug title to '[ROM] racon: Please remove for 32 bit architectures 
(armel, armhf, i386, mipsel, hppa, m68k, powerpc, sh4, x32)' from 'racon: 
build-dependencies unsatisfiable on 32-bit.'.
> reassign -1 ftp.debian.org
Bug #1021755 [racon] [ROM] racon: Please remove for 32 bit architectures 
(armel, armhf, i386, mipsel, hppa, m68k, powerpc, sh4, x32)
Bug reassigned from package 'racon' to 'ftp.debian.org'.
No longer marked as found in versions racon/1.5.0-2.
Ignoring request to alter fixed versions of bug #1021755 to the same values 
previously set

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

Bug#1021755: [ROM] racon: Please remove for 32 bit architectures (armel, armhf, i386, mipsel, hppa, m68k, powerpc, sh4, x32) (Was: Bug#1021755: racon: build-dependencies unsatisfiable on 32-bit.)

2022-10-14 Thread Andreas Tille 
Control: retitle -1 [ROM] racon: Please remove for 32 bit architectures (armel, 
armhf, i386, mipsel, hppa, m68k, powerpc, sh4, x32)
Control: reassign -1 ftp.debian.org

Hi ftpmasters,

we have to chose option 3 mentioned below - asking for removal of
32 bit architectures.

Kind regards and thanks for working as ftpmaster

  Andreas.

Am Fri, Oct 14, 2022 at 04:54:27AM +0100 schrieb Peter Green:
> Package: racon
> Version: 1.5.0-2
> Severity: serious
> 
> racon build-depends on libthread-pool-dev which is no longer available on 
> 32-bit
> architectures, this means that the package can no longer be built on those
> architectures but the binaries are still in testing/unstable.
> 
> In general there are three possible avenues for fixing these kinds of issues,
> in roughly descending order of preference.
> 
> 1. Fix libthread-pool-dev to build on 32-bit architectures.
> 2. Eliminate the build-dependency (either generally or on those architectures)
> 3. Declare your package unsupportable on 32-bit architectures and file a 
> removal
>request with the ftpmasters.
> 
> Which of these are possible in the case of your specific package I do not 
> know.
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de

Bug#1021767: osmo-bsc: FTBFS if systemd is in build environment

2022-10-14 Thread Gianfranco Costamagna 

Source: osmo-bsc
Version: 1.9.0-2
Severity: serious

Hello, as already seen in #1010578 this package suffers of a similar issue when 
systemd is in build environment.

Can you please also apply the patch on this package?
I can trigger an rb build to show the failure there too if needed.

Thanks!

Gianfranco

--- osmo-bsc-1.9.0/debian/changelog 2022-10-13 22:44:11.0 +0200
+++ osmo-bsc-1.9.0/debian/changelog 2022-10-14 10:34:42.0 +0200
@@ -1,3 +1,9 @@
+osmo-bsc (1.9.0-3) unstable; urgency=medium
+
+  * Fix build failure with installed systemd (Closes: #-1)
+
+ -- Gianfranco Costamagna   Fri, 14 Oct 2022 
10:34:42 +0200
+
 osmo-bsc (1.9.0-2) unstable; urgency=medium
 
   * upload to unstable

diff -Nru osmo-bsc-1.9.0/debian/rules osmo-bsc-1.9.0/debian/rules
--- osmo-bsc-1.9.0/debian/rules 2022-10-13 22:44:11.0 +0200
+++ osmo-bsc-1.9.0/debian/rules 2022-10-14 10:34:42.0 +0200
@@ -32,5 +32,9 @@
 override_dh_auto_test:
dh_auto_test || (find . -name testsuite.log -exec cat {} \; ; false)
 
+override_dh_auto_configure:

+   # Use the packaging-provided systemd unit file
+   dh_auto_configure -- --with-systemdsystemunitdir=no
+
 override_dh_installsystemd:
dh_installsystemd --no-enable --no-start


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021765: libosmo-sccp: FTBFS if systemd is in build environment

2022-10-14 Thread Gianfranco Costamagna 

Source: libosmo-sccp
Version: 1.6.0+dfsg1-2
Severity: serious


Hello, as already seen in #1010578 this package suffers of a similar issue when 
systemd is in build environment.

Can you please also apply the patch on this package?
I can trigger an rb build to show the failure there too if needed.

Thanks!

Gianfranco

diff -Nru libosmo-sccp-1.6.0+dfsg1/debian/changelog 
libosmo-sccp-1.6.0+dfsg1/debian/changelog
--- libosmo-sccp-1.6.0+dfsg1/debian/changelog   2022-10-13 21:50:04.0 
+0200
+++ libosmo-sccp-1.6.0+dfsg1/debian/changelog   2022-10-14 10:16:17.0 
+0200
@@ -1,3 +1,9 @@
+libosmo-sccp (1.6.0+dfsg1-3) unstable; urgency=medium
+
+  * Fix build failure with installed systemd (Closes: #-1)
+
+ -- Gianfranco Costamagna   Fri, 14 Oct 2022 
10:16:17 +0200
+
 libosmo-sccp (1.6.0+dfsg1-2) unstable; urgency=medium
 
   * upload to unstable

diff -Nru libosmo-sccp-1.6.0+dfsg1/debian/rules 
libosmo-sccp-1.6.0+dfsg1/debian/rules
--- libosmo-sccp-1.6.0+dfsg1/debian/rules   2022-10-13 21:50:04.0 
+0200
+++ libosmo-sccp-1.6.0+dfsg1/debian/rules   2022-10-14 10:16:15.0 
+0200
@@ -28,6 +28,9 @@
   dh_auto_test || (find . -name testsuite.log -exec cat {} \; ; false) 
\
fi
 
+override_dh_auto_configure:

+   # Use the packaging-provided systemd unit file
+   dh_auto_configure -- --with-systemdsystemunitdir=no
 
 override_dh_installsystemd:

dh_installsystemd --no-enable --no-start



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021763: osmo-hlr: FTBFS if systemd is in build environment

2022-10-14 Thread Gianfranco Costamagna 

Source: osmo-hlr
Version: 1.5.0+dfsg1-2
Severity: serious

Hello, as already seen in #1010578 this package suffers of a similar issue when 
systemd is in build environment.

Can you please also apply the patch on this package?
I can trigger an rb build to show the failure there too if needed.

Thanks!

Gianfranco
--- osmo-hlr-1.5.0+dfsg1/debian/changelog   2022-10-13 20:53:42.0 
+0200
+++ osmo-hlr-1.5.0+dfsg1/debian/changelog   2022-10-14 10:14:39.0 
+0200
@@ -1,3 +1,9 @@
+osmo-hlr (1.5.0+dfsg1-3) unstable; urgency=medium
+
+  * Fix build failure with installed systemd (Closes: #-1)
+
+ -- Gianfranco Costamagna   Fri, 14 Oct 2022 
10:14:39 +0200
+
 osmo-hlr (1.5.0+dfsg1-2) unstable; urgency=medium
 
   * upload to unstable

diff -Nru osmo-hlr-1.5.0+dfsg1/debian/rules osmo-hlr-1.5.0+dfsg1/debian/rules
--- osmo-hlr-1.5.0+dfsg1/debian/rules   2022-10-13 20:53:42.0 +0200
+++ osmo-hlr-1.5.0+dfsg1/debian/rules   2022-10-14 10:14:38.0 +0200
@@ -22,6 +22,10 @@
$(RM) tests/package.m4
$(RM) tests/testsuite
 
+override_dh_auto_configure:

+   # Use the packaging-provided systemd unit file
+   dh_auto_configure -- --with-systemdsystemunitdir=no
+
 override_dh_installsystemd:
dh_installsystemd --no-enable --no-start
 



OpenPGP_signature
Description: OpenPGP digital signature

Processed: severity of 1013157 is serious

2022-10-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> # blocks removal of vtk7
> severity 1013157 serious
Bug #1013157 [nifti2dicom] nifti2dicom: vtk[6,7] removal
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1021762: osmo-ggsn: FTBFS if systemd is in build environment

2022-10-14 Thread Gianfranco Costamagna 

Source: osmo-ggsn
Version: 1.9.0-2
Severity: serious

Hello, as already seen in #1010578 this package suffers of a similar issue when 
systemd is in build environment.

Can you please also apply the patch on this package?
I can trigger an rb build to show the failure there too if needed.

Thanks!

Gianfranco

diff -Nru osmo-ggsn-1.9.0/debian/changelog osmo-ggsn-1.9.0/debian/changelog
--- osmo-ggsn-1.9.0/debian/changelog2022-10-10 16:07:17.0 +
+++ osmo-ggsn-1.9.0/debian/changelog2022-10-14 07:20:20.0 +
@@ -1,3 +1,9 @@
+osmo-ggsn (1.9.0-3) unstable; urgency=medium
+
+  * Fix build failure with installed systemd (Closes: #-1)
+
+ -- Gianfranco Costamagna   Fri, 14 Oct 2022 
09:20:20 +0200
+
 osmo-ggsn (1.9.0-2) unstable; urgency=medium
 
   * upload to unstable

diff -Nru osmo-ggsn-1.9.0/debian/rules osmo-ggsn-1.9.0/debian/rules
--- osmo-ggsn-1.9.0/debian/rules2022-10-10 16:07:17.0 +
+++ osmo-ggsn-1.9.0/debian/rules2022-10-14 07:20:18.0 +
@@ -13,6 +13,10 @@
 %:
dh $@ --with autoreconf
 
+override_dh_auto_configure:

+   # Use the packaging-provided systemd unit file
+   dh_auto_configure -- --with-systemdsystemunitdir=no
+
 override_dh_clean:
dh_clean
$(RM) .tarball-version


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016234: marked as done (feynmf: FTBFS: ! LaTeX Error: File `hypdoc.sty' not found.)

2022-10-14 Thread Debian Bug Tracking System 
Your message dated Fri, 14 Oct 2022 09:35:41 +0200
with message-id <455ace8c-8460-d68f-4486-b1df5c79f...@web.de>
and subject line Re: Bug#1016234: feynmf: FTBFS: ! LaTeX Error: File 
`hypdoc.sty' not found.
has caused the Debian Bug report #1016234,
regarding feynmf: FTBFS: ! LaTeX Error: File `hypdoc.sty' not found.
to be marked as done.

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

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


-- 
1016234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: feynmf
Version: 1.08-13
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 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 '/<>'
> latex feynmf.ins
> This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) 
> (preloaded format=latex)
>  restricted \write18 enabled.
> entering extended mode
> (./feynmf.ins
> LaTeX2e <2022-06-01> patch level 5
> L3 programming layer <2022-07-15>
> (/usr/share/texlive/texmf-dist/tex/latex/base/docstrip.tex
> Utility: `docstrip' v2.6a <2020-11-23>
> English documentation<2020-11-23>
> 
> **
> * This program converts documented macro-files into fast *
> * loadable files by stripping off (nearly) all comments! *
> **
> 
> 
> * No Configuration file found, using default settings. *
> 
> 
> (./feynmf.ins
> Generating style file feynmf.sty for the feynmf package:
> 
> Generating file(s) ./feynmf.sty 
> 
> Processing file feynmf.dtx (style) -> feynmf.sty
> File feynmf.dtx ended by \endinput.
> Lines  processed: 7793
> Comments removed: 5055
> Comments  passed: 19
> Codelines passed: 2521
> 
> Generating Metafont base feynmf.mf:
> 
> Generating file(s) ./feynmf.mf 
> 
> Processing file feynmf.dtx (base) -> feynmf.mf
> File feynmf.dtx ended by \endinput.
> Lines  processed: 7793
> Comments removed: 5055
> Comments  passed: 19
> Codelines passed: 2521
> 
> Generating style file feynmp.sty for the MetaPost version:
> 
> Generating file(s) ./feynmp.sty 
> 
> Processing file feynmf.dtx (style,mp) -> feynmp.sty
> File feynmf.dtx ended by \endinput.
> Lines  processed: 7793
> Comments removed: 5055
> Comments  passed: 19
> Codelines passed: 2521
> 
> Generating MetaPost base feynmp.mp:
> 
> Generating file(s) ./feynmp.mp 
> 
> Processing file feynmf.dtx (base,mp) -> feynmp.mp
> File feynmf.dtx ended by \endinput.
> Lines  processed: 7793
> Comments removed: 5055
> Comments  passed: 19
> Codelines passed: 2521
> 
> Generating driver file for manual fmfman.drv:
> 
> Generating file(s) ./fmfman.drv 
> 
> Processing file feynmf.dtx (driver,manual) -> fmfman.drv
> File feynmf.dtx ended by \endinput.
> Lines  processed: 7793
> Comments removed: 5055
> Comments  passed: 19
> Codelines passed: 2521
> 
> Generating alternate MetaPost driver file fmfmanps.drv:
> 
> Generating file(s) ./fmfmanps.drv 
> 
> Processing file feynmf.dtx (driver,manual,mp) -> fmfmanps.drv
> File feynmf.dtx ended by \endinput.
> Lines  processed: 7793
> Comments removed: 5055
> Comments  passed: 19
> Codelines passed: 2521
> 
> Generating driver file for documentation feynmf.drv:
> 
> Generating file(s) ./feynmf.drv 
> 
> Processing file feynmf.dtx (driver) -> feynmf.drv
> File feynmf.dtx ended by \endinput.
> Lines  processed: 7793
> Comments removed: 5055
> Comments  passed: 19
> Codelines passed: 2521
> 
> Generating alternate MetaPost driver file feynmp.drv:
> 
> Generating file(s) ./feynmp.drv 
> 
> Processing file feynmf.dtx (driver,mp) -> feynmp.drv
> File feynmf.dtx ended by \endinput.
> Lines  processed: 7793
> Comments removed: 5055
> Comments  passed: 19
> Codelines passed: 2521
> 
> ***
> *
> * To finish the installation you have to move the files
> *
> *  o feynmf.sty into a directory searched by TeX
> *  o feynmf.mf into a directory searched by Metafont
> *  o feynmp.sty into a directory searched by TeX
> *  o feynmp.mp into a directory searched by MetaPost
> *
> * You can remove the latter two if you don't have
> * John Hobby's MetaPost system. Optionally you can copy the
> * files fmfman.dtx and fmfmanps.drv into a directory searched by
> * TeX, so that users can print a copy of the documentation.
> *
>

Bug#1016234: feynmf: FTBFS: ! LaTeX Error: File `hypdoc.sty' not found.

2022-10-14 Thread Hilmar Preusse 
Control: reassign -1 texlive-latex-base

On 29.07.22 Lucas Nussbaum (lu...@debian.org) wrote:

Hi,

this happened due to a change in doc package. Reassign to
texlive-latex-base for now, will close shortly.

Hilmar

> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):

> > Writing glossary file fmfmanps.glo 
> > Writing index file fmfmanps.idx
> > 
> > ! LaTeX Error: File `hypdoc.sty' not found.
> > 
> > Type X to quit or  to proceed,
> > or enter new name. (Default extension: sty)
> > 
> > Enter file name: 
> > ! Emergency stop.
> >  
> >  
> 
> The full build log is available from:
> http://qa-logs.debian.net/2022/07/28/feynmf_1.08-13_unstable.log
> 
> All bugs filed during this archive rebuild are listed at:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
> or:
> https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results
> 
> 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 fail to reproduce this, please provide a build log and diff it with 
> mine
> so that we can identify if something relevant changed in the meantime.

-- 
sigmentation fault


signature.asc
Description: PGP signature

Processed: Re: Bug#1016234: feynmf: FTBFS: ! LaTeX Error: File `hypdoc.sty' not found.

2022-10-14 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 texlive-latex-base
Bug #1016234 [src:feynmf] feynmf: FTBFS: ! LaTeX Error: File `hypdoc.sty' not 
found.
Bug reassigned from package 'src:feynmf' to 'texlive-latex-base'.
No longer marked as found in versions feynmf/1.08-13.
Ignoring request to alter fixed versions of bug #1016234 to the same values 
previously set

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

Processed: tagging 1020046 ...

2022-10-14 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 1020046 + fixed-upstream patch
Bug #1020046 [src:slimit] slimit: FTBFS: ModuleNotFoundError: No module named 
'minifier'
Added tag(s) fixed-upstream and patch.
> forwarded 1020046 
> https://github.com/rspivak/slimit/commit/40956e7fc6e954b3e6d7b629faeb3303f5efb7ea
>  https://github.com/rspivak/slimit/pull/102
Bug #1020046 [src:slimit] slimit: FTBFS: ModuleNotFoundError: No module named 
'minifier'
Set Bug forwarded-to-address to 
'https://github.com/rspivak/slimit/commit/40956e7fc6e954b3e6d7b629faeb3303f5efb7ea
 https://github.com/rspivak/slimit/pull/102'.
> thanks
Stopping processing here.

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