Processed: severity of 1031379 is important, tagging 1031379

[Debian Bug Tracking System]

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

> severity 1031379 important
Bug #1031379 [kaffeine] kaffeine: does not work
Severity set to 'important' from 'grave'
> tags 1031379 = moreinfo
Bug #1031379 [kaffeine] kaffeine: does not work
Removed tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Bug#1031460: marked as done (enlighten: FTBFS: AssertionError: '1.00[31 chars]0.00 s/B | 128.00 KiB | 896.00 KiB | 512.00 K[105 chars] s/B' != '1.00[31 chars]0.00 s/B | 128.00 KiB | 896.00 KiB | 512.

[Debian Bug Tracking System]

Your message dated Sun, 26 Feb 2023 07:19:06 +
with message-id 
and subject line Bug#1031460: fixed in enlighten 1.11.2-1
has caused the Debian Bug report #1031460,
regarding enlighten: FTBFS: AssertionError: '1.00[31 chars]0.00  s/B | 128.00 
KiB | 896.00 KiB | 512.00 K[105 chars] s/B' != '1.00[31 chars]0.00 s/B | 128.00 
KiB | 896.00 KiB | 512.00 Ki[101 chars] s/B'
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.)


-- 
1031460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: enlighten
Version: 1.11.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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_build
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:515: 
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use 
> license_files instead.
>   warnings.warn(msg, warning_class)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/counter.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/manager.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_counter.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_basemanager.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_statusbar.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_basecounter.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_util.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_notebook_manager.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> copying enlighten/_manager.py -> 
> /<>/.pybuild/cpython3_3.11/build/enlighten
> PYTHONPATH=. python3 -m sphinx -N -bhtml doc/ build/html # HTML generator
> Running Sphinx v5.3.0
> Initializing Spelling Checker 7.7.0
> making output directory... done
> loading intersphinx inventory from https://docs.python.org/3/objects.inv...
> loading intersphinx inventory from 
> https://prefixed.readthedocs.io/en/stable/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable 
> due to : 
> HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded 
> with url: /3/objects.inv (Caused by ProxyError('Cannot connect to proxy.', 
> NewConnectionError(' 0x7f8203179b50>: Failed to establish a new connection: [Errno 111] Connection 
> refused')))
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://prefixed.readthedocs.io/en/stable/objects.inv' 
> not fetchable due to : 
> HTTPSConnectionPool(host='prefixed.readthedocs.io', port=443): Max retries 
> exceeded with url: /en/stable/objects.inv (Caused by ProxyError('Cannot 
> connect to proxy.', NewConnectionError(' object at 0x7f820317a190>: Failed to establish a new connection: [Errno 111] 
> Connection refused')))
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 6 source files that are out of date
> updating environment: [new config] 6 added, 0 changed, 0 removed
> reading sources... [ 16%] api
> direct use of the spelling directive is deprecated, replace ".. spelling::" 
> with ".. spelling:word-list::"
> reading sources... [ 33%] examples
> reading sources... [ 50%] faq
> direct use of the spelling directive is deprecated, replace ".. spelling::" 
> with ".. spelling:word-list::"
> reading sources... [ 66%] index
> reading sources... [ 83%] install
> reading sources... [100%] patterns
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 16%] api
> writing output... [ 33%] examples
> writing output... [ 50%] faq
> writing output... [ 66%] index
> writing output... [ 83%] install
> writing output... [100%] patterns
> 
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager.Manager:1: WARNING: term not in glossary: 'file object'
> /<>/enlighten/_manager.py:docstring of 
> enlighten._manager.Manager:1: WARNING: term not in glossary: 'class'
> /<>/enlighten/_manager.py:docstring of 
> 

Bug#1031974: python3-pydle: import fails: AttributeError: module 'asyncio' has no attribute 'coroutine'

[s3v]

Package: python3-pydle
Version: 0.9.4
Severity: serious

Dear Maintainer,

This import fails in a Sid chroot:

Python 3.11.2 (main, Feb 12 2023, 00:48:52) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pydle
Traceback (most recent call last):
  File "", line 1, in 
  File "/build/pydle-0.9.4/pydle/__init__.py", line 1, in 
    from . import connection, protocol, client, features
  File "/build/pydle-0.9.4/pydle/features/__init__.py", line 1, in 
    from . import rfc1459, account, ctcp, tls, isupport, whox, ircv3
  File "/build/pydle-0.9.4/pydle/features/account.py", line 6, in 
    class AccountSupport(rfc1459.RFC1459Support):
  File "/build/pydle-0.9.4/pydle/features/account.py", line 25, in 
AccountSupport
    @asyncio.coroutine
 ^
AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you mean: 
'coroutines'?
>>>

Kind Regards

Bug#1031971: libxfce4panel-2.0-dev fails to build with valac installed

[Arthur Demchenkov]

Package: libxfce4panel-2.0-dev
Version: 4.18.1-1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

To reproduce the problem please follow these steps:

$ sudo apt install valac
$ apt-get source libxfce4panel-2.0-dev
$ cd xfce4-panel-4.18.1
$ sudo apt-get build-dep .
$ dpkg-buildpackage -j`nproc`

Output:

...
   dh_compress
   dh_fixperms
   debian/rules override_dh_missing
make[1]: Entering directory '/home/spinal/tmp/xfce4-panel-4.18.1'
dh_missing --fail-missing -X .la
dh_missing: warning: usr/share/vala/vapi/libxfce4panel-2.0.deps exists in 
debian/tmp but is not installed to anywhere
dh_missing: warning: usr/share/vala/vapi/libxfce4panel-2.0.vapi exists in 
debian/tmp but is not installed to anywhere
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: gir1.2-libxfce4panel-2.0 (1), libxfce4panel-2.0-4 (3), 
libxfce4panel-2.0-dev (5), xfce4-panel (18)
 * dh_installdocs: gir1.2-libxfce4panel-2.0 (0), libxfce4panel-2.0-4 
(0), libxfce4panel-2.0-dev (0), xfce4-panel (1)
 * dh_installman: gir1.2-libxfce4panel-2.0 (0), libxfce4panel-2.0-4 
(0), libxfce4panel-2.0-dev (0), xfce4-panel (1)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
dh_missing: error: missing files, aborting
make[1]: *** [debian/rules:16: override_dh_missing] Error 255
make[1]: Leaving directory '/home/spinal/tmp/xfce4-panel-4.18.1'
make: *** [debian/rules:7: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



To fix the issue I propose including valac to package build dependencies
and include vala api files to libxfce4panel-2.0-dev.

These vala api files are useful when you wish to build some xfce plugins
from vala sources. One example is xfce4-notes-plugin which I was trying
to build and found that vala api files are missing in Debian distribution.

Please keep in mind that building libxfce4panel-2.0-dev will also fail if
you didn't install libxfce4util-1.0 with vala api files. It means that
Debian bug #1031967 should be resolved first to satisfy vala api deps of
this package.

For possible fix check the following patch.


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

Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU:ru
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libxfce4panel-2.0-dev depends on:
ii  gir1.2-libxfce4panel-2.0  4.18.1-1
ii  libglib2.0-dev2.74.5-1
ii  libgtk-3-dev  3.24.36-4
ii  libxfce4panel-2.0-4   4.18.1-1
ii  libxfce4util-dev  4.18.1-1

libxfce4panel-2.0-dev recommends no packages.

libxfce4panel-2.0-dev suggests no packages.

-- no debconf information
diff -Naur xfce4-panel-4.18.1-orig/debian/control 
xfce4-panel-4.18.1/debian/control
--- xfce4-panel-4.18.1-orig/debian/control  2023-01-12 10:55:51.0 
+0300
+++ xfce4-panel-4.18.1/debian/control   2023-02-26 05:33:54.816823882 +0300
@@ -19,6 +19,7 @@
libxfce4ui-2-dev (>= 4.17.1),
libxfce4util-dev (>= 4.17.2),
libxfconf-0-dev,
+   valac,
xfce4-dev-tools
 Rules-Requires-Root: no
 Standards-Version: 4.6.2
diff -Naur xfce4-panel-4.18.1-orig/debian/libxfce4panel-2.0-dev.install 
xfce4-panel-4.18.1/debian/libxfce4panel-2.0-dev.install
--- xfce4-panel-4.18.1-orig/debian/libxfce4panel-2.0-dev.install
2022-08-29 02:22:07.0 +0300
+++ xfce4-panel-4.18.1/debian/libxfce4panel-2.0-dev.install 2023-02-26 
05:34:23.929239264 +0300
@@ -3,3 +3,4 @@
 usr/lib/*/pkgconfig/libxfce4panel-2.0.pc
 usr/share/gtk-doc/html/libxfce4panel-2.0
 usr/share/gir-1.0/*
+usr/share/vala/vapi/*

Bug#1031888: emacs-nox: bullseye-security update fails to install on mips64el

[Adrian Bunk]

On Fri, Feb 24, 2023 at 06:32:46PM +, Adam D. Barratt wrote:
> Source: emacs
> Version: 1:27.1+1-3.1+deb11u2
> Severity: grave
> Control: affects -1 + security.debian.org
> Control: affects -1 + release.debian.org
> X-Debbugs-Cc: t...@security.debian.org
> X-Debbugs-Cc: debian-ad...@lists.debian.org
> 
> Hi,
> 
> Upgrading emacs-nox on a bullseye mips64el system to the latest
> security update fails:
> 
> Setting up emacs-nox (1:27.1+1-3.1+deb11u2) ...
> update-alternatives: using /usr/bin/emacs-nox to provide /usr/bin/emacs 
> (emacs) in auto mode
> Install emacsen-common for emacs
> emacsen-common: Handling install of emacsen flavor emacs
> emacs: could not load dump file 
> "/usr/lib/emacs/27.1/mips64el-linux-gnuabi64/emacs.pdmp": out of memory
> ERROR: install script from emacsen-common package failed
> dpkg: error processing package emacs-nox (--configure):
>  installed emacs-nox package post-installation script subprocess returned 
> error exit status 1
> 
> Downgrading to +deb11u1 on the same system works fine. Removing the
> emacs packages and installing +deb11u2 directly fails in the same way.
>...

In the upstream bug for CVE-2022-48337 there was originally[1]
+  free (new_real_name);
+  free (new_tmp_name);
in the fix that later disappeared (by accident?).

I would say the CVE-2022-48337 fix introduced a memory leak,
which might or might not be related to the mips64el problem.

> Regards,
> 
> Adam

cu
Adrian

[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=59817#23

Bug#1031968: libxfconf-0-dev fails to build with valac installed

[Arthur Demchenkov]

Package: libxfconf-0-dev
Version: 4.18.0-1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

To reproduce the problem please follow these steps:

$ sudo apt install valac
$ apt-get source libxfconf-0-dev
$ cd xfconf-4.18.0
$ dpkg-buildpackage -j`nproc`

Output:

...
   dh_compress
   dh_fixperms
   dh_missing
dh_missing: warning: usr/share/vala/vapi/libxfconf-0.deps exists in debian/tmp 
but is not installed to anywhere
dh_missing: warning: usr/share/vala/vapi/libxfconf-0.vapi exists in debian/tmp 
but is not installed to anywhere
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: gir1.2-xfconf-0 (1), libxfconf-0-3 (2), libxfconf-0-dev 
(5), xfconf (5)
 * dh_installdocs: gir1.2-xfconf-0 (0), libxfconf-0-3 (0), 
libxfconf-0-dev (1), xfconf (0)
 * dh_installman: gir1.2-xfconf-0 (0), libxfconf-0-3 (0), 
libxfconf-0-dev (0), xfconf (1)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
dh_missing: error: missing files, aborting
make: *** [debian/rules:7: binary] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


To fix the issue I propose including valac to package build dependencies
and include vala api files to libxfconf-0-dev.

This vala api files are useful when you wish to build some xfce plugins
from vala sources. One example is xfce4-notes-plugin which I was trying
to build and found that some vala api files are missing in Debian
distribution.

Possible fix follows (check the patch).


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

Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU:ru
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libxfconf-0-dev depends on:
ii  gir1.2-xfconf-0   4.18.0-1
ii  libglib2.0-dev2.74.5-1
ii  libxfconf-0-3 4.18.0-1
ii  pkg-config1.8.1-1
ii  pkgconf [pkg-config]  1.8.1-1

libxfconf-0-dev recommends no packages.

libxfconf-0-dev suggests no packages.

-- no debconf information
diff -Naur xfconf-4.18.0-orig/debian/control xfconf-4.18.0/debian/control
--- xfconf-4.18.0-orig/debian/control   2022-12-10 10:48:30.0 +0300
+++ xfconf-4.18.0/debian/control2023-02-26 05:03:43.079063926 +0300
@@ -9,6 +9,7 @@
intltool,
libgirepository1.0-dev,
libxfce4util-dev (>= 4.17.3),
+   valac,
xfce4-dev-tools (>= 4.16)
 Rules-Requires-Root: no
 Standards-Version: 4.6.1
diff -Naur xfconf-4.18.0-orig/debian/libxfconf-0-dev.install 
xfconf-4.18.0/debian/libxfconf-0-dev.install
--- xfconf-4.18.0-orig/debian/libxfconf-0-dev.install   2020-11-14 
13:01:16.0 +0300
+++ xfconf-4.18.0/debian/libxfconf-0-dev.install2023-02-26 
05:02:28.854000853 +0300
@@ -3,3 +3,4 @@
 usr/lib/*/pkgconfig
 usr/share/gir-1.0/*
 usr/share/gtk-doc
+usr/share/vala/vapi/*

Bug#1031967: libxfce4util-dev fails to build with valac installed

[Arthur Demchenkov]

Package: libxfce4util-dev
Version: 4.18.1-1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

to repeat the problem, please follow these steps:

$ sudo apt install valac
$ apt-get source libxfce4util-dev
$ cd libxfce4util-4.18.1/
$ dpkg-buildpackage -j`nproc`

Output:
===
...
   dh_missing
dh_missing: warning: usr/share/vala/vapi/libxfce4util-1.0.vapi exists in 
debian/tmp but is not installed to anywhere 
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: gir1.2-libxfce4util-1.0 (1), libxfce4util-bin (1), 
libxfce4util-common (1), libxfce4util-dev (38), libxfce4util7 (2)
 * dh_installdocs: gir1.2-libxfce4util-1.0 (0), libxfce4util-bin (0), 
libxfce4util-common (0), libxfce4util-dev (1), libxfce4util7 (0)
 * dh_installman: gir1.2-libxfce4util-1.0 (0), libxfce4util-bin (1), 
libxfce4util-common (0), libxfce4util-dev (0), libxfce4util7 (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
dh_missing: error: missing files, aborting
make: *** [debian/rules:22: binary] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
===

To fix the issue I propose including valac to package build dependencies
and include vala api file to libxfce4util-dev.

This vala api file is useful when you wish to build some xfce plugins
from vala sources. One example is xfce4-notes-plugin which I was trying
to build and found that some vala api files are missing in Debian
distribution.

Possible fix follows.
===
diff -Naur libxfce4util-4.18.1-orig/debian/control 
libxfce4util-4.18.1/debian/control
--- libxfce4util-4.18.1-orig/debian/control 2023-01-12 10:28:40.0 +0300
+++ libxfce4util-4.18.1/debian/control  2023-02-26 04:31:58.179657805 +0300
@@ -9,6 +9,7 @@
intltool,
libgirepository1.0-dev,
libglib2.0-dev,
+   valac,
xfce4-dev-tools
 Rules-Requires-Root: no
 Standards-Version: 4.6.2
diff -Naur libxfce4util-4.18.1-orig/debian/libxfce4util-dev.install 
libxfce4util-4.18.1/debian/libxfce4util-dev.install
--- libxfce4util-4.18.1-orig/debian/libxfce4util-dev.install2022-12-05 
09:48:34.0 +0300
+++ libxfce4util-4.18.1/debian/libxfce4util-dev.install 2023-02-26 
04:27:37.163908152 +0300
@@ -3,3 +3,4 @@
 usr/lib/*/pkgconfig/*
 usr/share/gir-1.0/*
 usr/share/gtk-doc/html/libxfce4util/*
+usr/share/vala/vapi/*
===

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

Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU:ru
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libxfce4util-dev depends on:
ii  gir1.2-libxfce4util-1.0  4.18.1-1
ii  libglib2.0-dev   2.74.5-1
ii  libxfce4util74.18.1-1

libxfce4util-dev recommends no packages.

Versions of packages libxfce4util-dev suggests:
pn  devhelp  

-- no debconf information

Bug#1031966: python-pydata-sphinx-theme-doc is empty

[Adrian Bunk]

Package: python-pydata-sphinx-theme-doc
Version: 0.7.2-2
Severity: serious

/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/python-pydata-sphinx-theme-doc
/usr/share/doc/python-pydata-sphinx-theme-doc/changelog.Debian.gz
/usr/share/doc/python-pydata-sphinx-theme-doc/changelog.gz

Bug#1031965: python3-pyodc-docs is empty

[Adrian Bunk]

Package: python3-pyodc-docs
Version: 1.1.2-1
Severity: serious

/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/python3-pyodc-docs
/usr/share/doc/python3-pyodc-docs/changelog.Debian.gz
/usr/share/doc/python3-pyodc-docs/changelog.gz
/usr/share/doc/python3-pyodc-docs/copyright

Processed: libtrilinos-{globi,opti}pack-{13.2,dev} are empty

[Debian Bug Tracking System]

Processing control commands:

> affects -1 libtrilinos-globipack-13.2 libtrilinos-optipack-13.2 
> libtrilinos-globipack-dev libtrilinos-optipack-dev
Bug #1031964 [src:trilinos] libtrilinos-{globi,opti}pack-{13.2,dev} are empty
Added indication that 1031964 affects libtrilinos-globipack-13.2, 
libtrilinos-optipack-13.2, libtrilinos-globipack-dev, and 
libtrilinos-optipack-dev

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

Bug#1031964: libtrilinos-{globi,opti}pack-{13.2,dev} are empty

[Adrian Bunk]

Source: trilinos
Version: 13.2.0-3
Severity: serious
Control: affects -1 libtrilinos-globipack-13.2 libtrilinos-optipack-13.2 
libtrilinos-globipack-dev libtrilinos-optipack-dev

/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libtrilinos-globipack-13.2
/usr/share/doc/libtrilinos-globipack-13.2/changelog.Debian.amd64.gz
/usr/share/doc/libtrilinos-globipack-13.2/changelog.Debian.gz
/usr/share/doc/libtrilinos-globipack-13.2/copyright
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libtrilinos-optipack-13.2
/usr/share/doc/libtrilinos-optipack-13.2/changelog.Debian.amd64.gz
/usr/share/doc/libtrilinos-optipack-13.2/changelog.Debian.gz
/usr/share/doc/libtrilinos-optipack-13.2/copyright
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libtrilinos-globipack-dev
/usr/share/doc/libtrilinos-globipack-dev/changelog.Debian.amd64.gz
/usr/share/doc/libtrilinos-globipack-dev/changelog.Debian.gz
/usr/share/doc/libtrilinos-globipack-dev/copyright
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libtrilinos-optipack-dev
/usr/share/doc/libtrilinos-optipack-dev/changelog.Debian.amd64.gz
/usr/share/doc/libtrilinos-optipack-dev/changelog.Debian.gz
/usr/share/doc/libtrilinos-optipack-dev/copyright

Bug#1031961: qtmir FTBFS on several architectures: symbol differences

[Adrian Bunk]

Source: qtmir
Version: 0.8.0~git20230223.bd21224-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=qtmir=0.8.0%7Egit20230223.bd21224-1

Bug#1031960: cpufetch FTBFS on ppc64/ppc64el

[Adrian Bunk]

Source: cpufetch
Version: 1.03-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=cpufetch=1.03-2

...
src/common/printer.c: In function ‘print_ascii_generic’:
src/common/printer.c:487:23: error: ‘ATTRIBUTE_CPU_NUM’ undeclared (first use 
in this function); did you mean ‘ATTRIBUTE_PEAK’?
  487 |   if(attr_type == ATTRIBUTE_CPU_NUM) {
  |   ^
  |   ATTRIBUTE_PEAK
src/common/printer.c:487:23: note: each undeclared identifier is reported only 
once for each function it appears in
src/common/printer.c: In function ‘print_cpufetch_ppc’:
src/common/printer.c:693:3: error: too few arguments to function 
‘print_ascii_generic’
  693 |   print_ascii_generic(art, longest_attribute, term->w, 
attribute_fields);
  |   ^~~
src/common/printer.c:433:6: note: declared here
  433 | void print_ascii_generic(struct ascii* art, uint32_t la, int32_t termw, 
const char** attribute_fields, bool hybrid_architecture) {
  |  ^~~
At top level:
cc1: note: unrecognized command-line option ‘-Wno-language-extension-token’ may 
have been intended to silence earlier diagnostics
make[1]: *** [Makefile:83: cpufetch] Error 1

Processed: vdr: diff for NMU version 2.6.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1026310 + pending
Bug #1026310 [vdr-dev] vdr-dev: dh_vdrplugin_depends fail with "error: Bug in 
helper:"
Bug #1026475 [vdr-dev] vdr-plugin-remote: FTBFS: make: *** [debian/rules:7: 
binary] Error 25
Bug #1026533 [vdr-dev] vdr-plugin-femon: FTBFS: make: *** [debian/rules:7: 
binary] Error 25
Bug #1027498 [vdr-dev] vdr-plugin-streamdev: FTBFS: make: *** [debian/rules:9: 
binary] Error 25
Bug #1027499 [vdr-dev] vdr-plugin-svdrposd: FTBFS: make: *** [debian/rules:7: 
binary] Error 25
Bug #1027532 [vdr-dev] vdr-plugin-dvd: FTBFS: make: *** [debian/rules:7: 
binary] Error 25
Bug #1027543 [vdr-dev] vdr-plugin-osdserver: FTBFS: make: *** [debian/rules:10: 
binary] Error 25
Bug #1027568 [vdr-dev] vdr-plugin-fritzbox: FTBFS: make: *** [debian/rules:9: 
binary] Error 25
Bug #1027575 [vdr-dev] vdr-plugin-epgsearch: FTBFS: make: *** [debian/rules:7: 
binary] Error 25
Bug #1027609 [vdr-dev] vdr-plugin-xineliboutput: FTBFS: make: *** 
[debian/rules:13: binary] Error 25
Bug #1027627 [vdr-dev] vdr-plugin-osdteletext: FTBFS: make: *** 
[debian/rules:7: binary] Error 25
Bug #1027630 [vdr-dev] vdr-plugin-satip: FTBFS: make: *** [debian/rules:11: 
binary] Error 25
Bug #1027631 [vdr-dev] vdr-plugin-epgsync: FTBFS: make: *** [debian/rules:7: 
binary] Error 25
Bug #1027645 [vdr-dev] vdr-plugin-dvbsddevice: FTBFS: make: *** 
[debian/rules:7: binary] Error 25
Bug #1027646 [vdr-dev] vdr-plugin-vnsiserver: FTBFS: make: *** 
[debian/rules:16: binary] Error 25
Bug #1027659 [vdr-dev] vdr-plugin-dvbhddevice: FTBFS: make: *** 
[debian/rules:7: binary] Error 25
Bug #1027660 [vdr-dev] vdr-plugin-svdrpservice: FTBFS: make: *** 
[debian/rules:9: binary] Error 25
Bug #1027663 [vdr-dev] vdr-plugin-skinenigmang: FTBFS: make: *** 
[debian/rules:11: binary] Error 25
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.

-- 
1026310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026310
1026475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026475
1026533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026533
1027498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027498
1027499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027499
1027532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027532
1027543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027543
1027568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027568
1027575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027575
1027609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027609
1027627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027627
1027630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027630
1027631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027631
1027645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027645
1027646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027646
1027659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027659
1027660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027660
1027663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1026310: vdr: diff for NMU version 2.6.0-1.1

[Adrian Bunk]

Control: tags 1026310 + pending

Dear maintainer,

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

cu
Adrian
diff -Nru vdr-2.6.0/debian/changelog vdr-2.6.0/debian/changelog
--- vdr-2.6.0/debian/changelog	2022-01-04 22:55:39.0 +0200
+++ vdr-2.6.0/debian/changelog	2023-02-26 01:32:03.0 +0200
@@ -1,3 +1,11 @@
+vdr (2.6.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply patch from Rogo to remove trailing newline from abiversion.
+(Closes: #1026310)
+
+ -- Adrian Bunk   Sun, 26 Feb 2023 01:32:03 +0200
+
 vdr (2.6.0-1) unstable; urgency=medium
 
   * New upstream version 2.6.0 and drop patches fixed upstream
diff -Nru vdr-2.6.0/debian/dh-addon-vdrplugin/dh_vdrplugin_depends vdr-2.6.0/debian/dh-addon-vdrplugin/dh_vdrplugin_depends
--- vdr-2.6.0/debian/dh-addon-vdrplugin/dh_vdrplugin_depends	2022-01-04 22:55:39.0 +0200
+++ vdr-2.6.0/debian/dh-addon-vdrplugin/dh_vdrplugin_depends	2023-02-26 01:32:00.0 +0200
@@ -43,6 +43,8 @@
 open(my $abiversion_file, ";
 close($abiversion_file);
+# remove trailing newline
+chomp($abiversion[-1]);
 
 verbose_print("Setting vdr:Depends=@abiversion");
 

Bug#1024589: dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory

[Adrian Bunk]

On Tue, Feb 07, 2023 at 03:10:27PM +0100, Santiago Vila wrote:
> severity 1024589 serious
> thanks
> 
> Hi. I can reproduce this, and I believe everybody who will try
> to build the package using sbuild right now in unstable should also
> be able to reproduce it.
> 
> (If you still can't reproduce it and need a test machine,
> please contact me privately, I can offer ssh access to a machine
> where it always happens).
> 
> Regarding the bug itself. this seems to happen because
> dh_install now puts the stuff in debian/tmp/lib64 while
> debian/rules does this:
> 
> dh_install
> mv $(TEMPDEB)/usr/lib/libdislocker* \
>$(DESTDIRLIB)/usr/lib/
> 
> i.e. expecting stuff to be in usr/lib/libdislocker*,
> but it's no longer there. Maybe because of ruby3.1,
> maybe because usr-merge,
>...

The Ubuntu diff has a fix for this issue caused by merged /usr
(untested).

> Thanks.

cu
Adrian

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: Bug#1031896: Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

[Scott Kitterman]

It's too late for a trip through New and Bookworm.  We probably should have 
done it before, but not now.  I think setting a minimum version of the current 
package will be sufficient and about all we can do now anyway.

Scott K

On February 25, 2023 10:26:50 PM UTC, Sebastian Andrzej Siewior 
 wrote:
>On 25 February 2023 16:20:45 UTC, Scott Kitterman  wrote:
>>True.
>>
>>I'm not a C programmer, so I may be unduly concerned about the maintenance 
>>load.  I'll defer to your judgement.
>
>I'm going to throw this on my machine to get more testing - more than just the 
>test suite.
>What about going through NEW with tfm? I would make it provide libtfm1-4k and  
>clamav would need a binnmu to pick up the change. 
>
>>
>>I do wonder if we should make a stab at switching the rust bits to using 
>>Debian packages instead of the embedded copies.  If we could manage it, then 
>>any security issues in the rust libraries can be fixed in clamav with a 
>>binNMU, no upload needed.
>
>That sounds good. I need to educate myself about rust to figure out how that 
>works. Right now it is all magic. I just hope that they did not adapt any 
>packages to their needs and that they don't rely on a newer version of 
>something than what we have in the archive.
>>
>>Scott K
>
>

Processed: Re: Bug#1030829: mmc-utils: FTBFS on ppc64el with error: ‘cnt’ may be used uninitialized

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1030829 [mmc-utils] mmc-utils: FTBFS on ppc64el with error: ‘cnt’ may be 
used uninitialized
Severity set to 'normal' from 'serious'

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

Bug#1030829: mmc-utils: FTBFS on ppc64el with error: ‘cnt’ may be used uninitialized

[Adrian Bunk]

Control: severity -1 normal

On Tue, Feb 07, 2023 at 04:38:20PM -0500, Nick Rosbrook wrote:
> Package: mmc-utils
> Severity: serious
> Tags: patch ftbfs
> Justification: fails to build from source (but built successfully in the past)
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu lunar ubuntu-patch
> 
> Dear Maintainer,
> 
> In Ubuntu, mcc-utils FTBFS[1] on ppc64el with the following:

Note that this is an Ubuntu-only FTBFS.

For some reason Canonical has chosen to make ppc64el in Ubuntu different 
from all other architectures in Ubuntu and all architectures in Debian
(including ppc64el) by defaulting to build with -O3 instead of -O2.

>  In file included from /usr/include/endian.h:35,
>   from /usr/include/powerpc64le-linux-gnu/sys/types.h:176,
>   from /usr/include/stdlib.h:395,
>   from mmc_cmds.c:21:
>  In function ‘__bswap_32’,
>  inlined from ‘do_rpmb_write_block’ at mmc_cmds.c:2462:27:
>  /usr/include/powerpc64le-linux-gnu/bits/byteswap.h:52:10: error: ‘cnt’ may 
> be used uninitialized [-Werror=maybe-uninitialized]
> 52 |   return __builtin_bswap32 (__bsx);
>|  ^
>...

The fix is not wrong, but I don't think there is an actual bug:
cnt is uninitialized only in the ret != 0 case,
that does already exit(1) two lines earlier.

cu
Adrian

Bug#1031904: marked as done (firmware-ath9k-htc: insufficient coordination around moving files between packages)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 23:43:04 +0100
with message-id <0955c399-3144-fd25-40c5-d5a42a82d...@debian.org>
and subject line Re: Bug#1031904: firmware-ath9k-htc: insufficient coordination 
around moving files between packages
has caused the Debian Bug report #1031904,
regarding firmware-ath9k-htc: insufficient coordination around moving files 
between packages
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.)


-- 
1031904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-ath9k-htc
Version: 1.4.0-108-gd856466+dfsg1-1.2
Severity: grave
Tags: d-i
X-Debbugs-Cc: b...@debian.org, debian-b...@lists.debian.org, 
debian-ker...@lists.debian.org

Hi,

While there have been some efforts around moving files between packages,
that's still insufficient coordination: files haven't removed from the
existing firmware-atheros package yet[1]! That means that any further
upload of firmware-atheros will be (relationship-wise) co-installable
with firmware-ath9k-htc (because its version will be higher than the one
in Replaces/Breaks), while that's actually not the case!

 1. 
https://salsa.debian.org/kernel-team/firmware-nonfree/-/merge_requests/54?commit_id=48af82f195e4ad5736d753b375442996915e244a#note_384526

Such move should have been handled by (1) making sure the existing
package drops files, and then (2) declaring Replaces/Breaks against all
versions strictly lower than this version.

Given modalias information, both firmware packages would be pulled at
the same time during installation, breaking dpkg in the target system.


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

Such move should have been handled by (1) making sure the existing
package drops files, and then (2) declaring Replaces/Breaks against all
versions strictly lower than this version.


The Replaces/Breaks versions can be kept because firmware-nonfree managed to
remove the two firmware files with the next version after the marked version.--- End Message ---

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: Bug#1031896: Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

[Sebastian Andrzej Siewior]

On 25 February 2023 16:20:45 UTC, Scott Kitterman  wrote:
>True.
>
>I'm not a C programmer, so I may be unduly concerned about the maintenance 
>load.  I'll defer to your judgement.

I'm going to throw this on my machine to get more testing - more than just the 
test suite.
What about going through NEW with tfm? I would make it provide libtfm1-4k and  
clamav would need a binnmu to pick up the change. 

>
>I do wonder if we should make a stab at switching the rust bits to using 
>Debian packages instead of the embedded copies.  If we could manage it, then 
>any security issues in the rust libraries can be fixed in clamav with a 
>binNMU, no upload needed.

That sounds good. I need to educate myself about rust to figure out how that 
works. Right now it is all magic. I just hope that they did not adapt any 
packages to their needs and that they don't rely on a newer version of 
something than what we have in the archive.
>
>Scott K


-- 
Sebastian

Bug#1031952: marked as forwarded (gettext: Missing source for an installed windows binary)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 23:21:34 +0100
with message-id <76103372-aecb-81e3-6e1a-dd89f7fdd...@debian.org>
has caused the   report #1031952,
regarding gettext: Missing source for an installed windows binary
to be marked as having been forwarded to the upstream software
author(s) bug-gett...@gnu.org

(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.)


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

Hello.

I've received the following report from the Debian bug system.

Summary: There is no source for gettext-tools/m4/csharpexec-test.exe.

Note: The Debian package disabled the mono stuff in version 0.17-7 (dated 
2009-08-17),
so I guess this file is one without which we could live, but I have not checked
yet how building the package fails if such file is not present. I guess it might
need some Makefile adjustments.

Thanks.

 Mensaje reenviado 
Asunto: Bug#1031952: gettext: Missing source for an installed windows binary
Fecha: Sat, 25 Feb 2023 21:46:05 +
De: Bastien Roucariès 
Responder a: Bastien Roucariès , 1031...@bugs.debian.org
Para: Debian Bug Tracking System 

Package: gettext
Version: 0.21-11
Severity: serious
Tags: ftbfs upstream
Justification: DFSG #2
User: lintian-ma...@debian.org
Usertags: source-is-missing
X-Debbugs-Cc: ftpmas...@debian.org

Hi,

your package includes some files that seem to lack sources
in preferred forms of modification:
gettext-tools/m4/csharpexec-test.exe

According to Debian Free Software Guidelines [1] (DFSG) #2:
 "The program must include source code, and must allow distribution
  in source code as well as compiled form."

In some cases this could also constitute a license violation for some
copyleft licenses such as the GNU GPL. (While sometimes the licence
allows not to ship the source, the DFSG always mandates source code.)

In order to solve this problem, you could:
1. add the source files to "debian/missing-sources" directory.
2. repack the origin tarball and add the missing source files to it.

Both ways satisfy the requirement to ship all source code. The second option
might be preferable due to the following reasons [2]:
 - Upstream can do it too and you could even supply a patch to them, thus
   fulfilling our social contract [3], see particularly §2.
 - If source and non-source are in different locations, ftpmasters may
   miss the source and (needlessly) reject the package.
 - The source isn't duplicated in every .diff.gz/.debian.tar.* (though
   this only really matters for larger sources).

You could also ask debian...@lists.debian.org or #debian-qa for more
guidance.


[1] https://www.debian.org/social_contract.en.html#guidelines
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8
[3] https://www.debian.org/social_contract--- End Message ---

Bug#1031952: Fwd: Bug#1031952: gettext: Missing source for an installed windows binary

[Santiago Vila]

Hello.

I've received the following report from the Debian bug system.

Summary: There is no source for gettext-tools/m4/csharpexec-test.exe.

Note: The Debian package disabled the mono stuff in version 0.17-7 (dated 
2009-08-17),
so I guess this file is one without which we could live, but I have not checked
yet how building the package fails if such file is not present. I guess it might
need some Makefile adjustments.

Thanks.

 Mensaje reenviado 
Asunto: Bug#1031952: gettext: Missing source for an installed windows binary
Fecha: Sat, 25 Feb 2023 21:46:05 +
De: Bastien Roucariès 
Responder a: Bastien Roucariès , 1031...@bugs.debian.org
Para: Debian Bug Tracking System 

Package: gettext
Version: 0.21-11
Severity: serious
Tags: ftbfs upstream
Justification: DFSG #2
User: lintian-ma...@debian.org
Usertags: source-is-missing
X-Debbugs-Cc: ftpmas...@debian.org

Hi,

your package includes some files that seem to lack sources
in preferred forms of modification:
gettext-tools/m4/csharpexec-test.exe

According to Debian Free Software Guidelines [1] (DFSG) #2:
 "The program must include source code, and must allow distribution
  in source code as well as compiled form."

In some cases this could also constitute a license violation for some
copyleft licenses such as the GNU GPL. (While sometimes the licence
allows not to ship the source, the DFSG always mandates source code.)

In order to solve this problem, you could:
1. add the source files to "debian/missing-sources" directory.
2. repack the origin tarball and add the missing source files to it.

Both ways satisfy the requirement to ship all source code. The second option
might be preferable due to the following reasons [2]:
 - Upstream can do it too and you could even supply a patch to them, thus
   fulfilling our social contract [3], see particularly §2.
 - If source and non-source are in different locations, ftpmasters may
   miss the source and (needlessly) reject the package.
 - The source isn't duplicated in every .diff.gz/.debian.tar.* (though
   this only really matters for larger sources).

You could also ask debian...@lists.debian.org or #debian-qa for more
guidance.


[1] https://www.debian.org/social_contract.en.html#guidelines
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8
[3] https://www.debian.org/social_contract

Bug#1028680: libzypp: diff for NMU version 17.25.7-2.4

[Mike Gabriel]

On  Sa 25 Feb 2023 21:59:19 CET, Adrian Bunk wrote:


Control: tags 1028680 + patch
Control: tags 1028680 + pending

Dear maintainer,

I've prepared an NMU for libzypp (versioned as 17.25.7-2.4) and uploaded
it to DELAYED/5. Please feel free to tell me if I should cancel it.

cu
Adrian


Thanks for doing this. I am unsure how to proceed with libzypp. I am  
not using / needing it anymore and I will likely orphan it after the  
release of Debian 12.


Thanks for the NMU!
Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgp1h13VBIPMS.pgp
Description: Digitale PGP-Signatur

Bug#1031950: libgeo-distance-perl should add Breaks and Replaces on libgeo-distance-xs-perl

[gregor herrmann]

On Sat, 25 Feb 2023 23:13:12 +0200, Adrian Bunk wrote:

> Package: libgeo-distance-perl
> Version: 0.25-2
> Severity: serious
> 
> Upgrading libgeo-distance-perl from bullseye to bookworm should
> remove libgeo-distance-xs-perl since it is now useless.

Good point, thank you.

I just don't understand the "Replaces" part in the subject, as
Geo::Distance::XS is not shipped (or is this need for the removal?
This part tends to confuse me).

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Processed: drslib: diff for NMU version 0.3.1.p3-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1030456 + patch
Bug #1030456 [src:drslib] drslib: FTBFS: 
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.3.1p3'
Added tag(s) patch.
> tags 1030456 + pending
Bug #1030456 [src:drslib] drslib: FTBFS: 
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.3.1p3'
Added tag(s) pending.

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

Bug#1030456: drslib: diff for NMU version 0.3.1.p3-2.1

[Adrian Bunk]

Control: tags 1030456 + patch
Control: tags 1030456 + pending

Dear maintainer,

I've prepared an NMU for drslib (versioned as 0.3.1.p3-2.1) and uploaded 
it to DELAYED/5. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru drslib-0.3.1.p3/debian/changelog drslib-0.3.1.p3/debian/changelog
--- drslib-0.3.1.p3/debian/changelog	2019-09-02 12:01:07.0 +0300
+++ drslib-0.3.1.p3/debian/changelog	2023-02-25 23:47:55.0 +0200
@@ -1,3 +1,10 @@
+drslib (0.3.1.p3-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * setup.py: Use a valid version. (Closes: #1030456)
+
+ -- Adrian Bunk   Sat, 25 Feb 2023 23:47:55 +0200
+
 drslib (0.3.1.p3-2) unstable; urgency=medium
 
   * Drop python2 support as EOL. Closes: #936446
diff -Nru drslib-0.3.1.p3/debian/patches/series drslib-0.3.1.p3/debian/patches/series
--- drslib-0.3.1.p3/debian/patches/series	2019-09-02 12:01:07.0 +0300
+++ drslib-0.3.1.p3/debian/patches/series	2023-02-25 23:47:55.0 +0200
@@ -1,2 +1,3 @@
 deb-config.patch
 python3.patch
+version.patch
diff -Nru drslib-0.3.1.p3/debian/patches/version.patch drslib-0.3.1.p3/debian/patches/version.patch
--- drslib-0.3.1.p3/debian/patches/version.patch	1970-01-01 02:00:00.0 +0200
+++ drslib-0.3.1.p3/debian/patches/version.patch	2023-02-25 23:47:55.0 +0200
@@ -0,0 +1,15 @@
+Description: setup.py: Use a valid version
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/1030456
+
+--- drslib-0.3.1.p3.orig/setup.py
 drslib-0.3.1.p3/setup.py
+@@ -8,7 +8,7 @@
+ from setuptools import setup, find_packages
+ import sys, os
+ 
+-version = '0.3.1p3'
++version = '0.3.1'
+ drs_version = '0.28'
+ 
+ setup(name='drslib',

Bug#1031952: gettext: Missing source for an installed windows binary

[Bastien Roucariès]

Package: gettext
Version: 0.21-11
Severity: serious
Tags: ftbfs upstream
Justification: DFSG #2
User: lintian-ma...@debian.org
Usertags: source-is-missing
X-Debbugs-Cc: ftpmas...@debian.org

Hi,

your package includes some files that seem to lack sources
in preferred forms of modification:
gettext-tools/m4/csharpexec-test.exe

According to Debian Free Software Guidelines [1] (DFSG) #2:
 "The program must include source code, and must allow distribution 
  in source code as well as compiled form."

In some cases this could also constitute a license violation for some
copyleft licenses such as the GNU GPL. (While sometimes the licence
allows not to ship the source, the DFSG always mandates source code.)

In order to solve this problem, you could:
1. add the source files to "debian/missing-sources" directory.
2. repack the origin tarball and add the missing source files to it.

Both ways satisfy the requirement to ship all source code. The second option
might be preferable due to the following reasons [2]:
 - Upstream can do it too and you could even supply a patch to them, thus
   fulfilling our social contract [3], see particularly §2.
 - If source and non-source are in different locations, ftpmasters may
   miss the source and (needlessly) reject the package.
 - The source isn't duplicated in every .diff.gz/.debian.tar.* (though
   this only really matters for larger sources).

You could also ask debian...@lists.debian.org or #debian-qa for more
guidance.


[1] https://www.debian.org/social_contract.en.html#guidelines
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8
[3] https://www.debian.org/social_contract

Bug#1028743: python-bottle: FTBFS: AssertionError: b'OK' != "URLError(ConnectionRefusedError(111, 'Connection refused'))"

[Gabriel Filion]

Hello!

Just wanted to chime in to confirm that James' patch does make the 
package compile.

Processed: twms: diff for NMU version 0.07z+git20201202+bb7c3f8-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1030449 + patch
Bug #1030449 [src:twms] twms: FTBFS: 
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '0.06y'
Added tag(s) patch.
> tags 1030449 + pending
Bug #1030449 [src:twms] twms: FTBFS: 
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '0.06y'
Added tag(s) pending.

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

Bug#1030449: twms: diff for NMU version 0.07z+git20201202+bb7c3f8-1.2

[Adrian Bunk]

Control: tags 1030449 + patch
Control: tags 1030449 + pending

Dear maintainer,

I've prepared an NMU for twms (versioned as 0.07z+git20201202+bb7c3f8-1.2)
and uploaded it to DELAYED/5. Please feel free to tell me if I should 
cancel it.

cu
Adrian
diff -Nru twms-0.07z+git20201202+bb7c3f8/debian/changelog twms-0.07z+git20201202+bb7c3f8/debian/changelog
--- twms-0.07z+git20201202+bb7c3f8/debian/changelog	2022-10-15 13:54:10.0 +0300
+++ twms-0.07z+git20201202+bb7c3f8/debian/changelog	2023-02-25 23:20:55.0 +0200
@@ -1,3 +1,10 @@
+twms (0.07z+git20201202+bb7c3f8-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * setup.py: Use a valid version. (Closes: #1030449)
+
+ -- Adrian Bunk   Sat, 25 Feb 2023 23:20:55 +0200
+
 twms (0.07z+git20201202+bb7c3f8-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru twms-0.07z+git20201202+bb7c3f8/debian/patches/series twms-0.07z+git20201202+bb7c3f8/debian/patches/series
--- twms-0.07z+git20201202+bb7c3f8/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ twms-0.07z+git20201202+bb7c3f8/debian/patches/series	2023-02-25 23:20:55.0 +0200
@@ -0,0 +1 @@
+version.patch
diff -Nru twms-0.07z+git20201202+bb7c3f8/debian/patches/version.patch twms-0.07z+git20201202+bb7c3f8/debian/patches/version.patch
--- twms-0.07z+git20201202+bb7c3f8/debian/patches/version.patch	1970-01-01 02:00:00.0 +0200
+++ twms-0.07z+git20201202+bb7c3f8/debian/patches/version.patch	2023-02-25 23:20:55.0 +0200
@@ -0,0 +1,15 @@
+Description: setup.py: Use a valid version
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/1030449
+
+--- twms-0.07z+git20201202+bb7c3f8.orig/setup.py
 twms-0.07z+git20201202+bb7c3f8/setup.py
+@@ -55,7 +55,7 @@ sdist.sdist = sdist_new
+ 
+ setup(
+ name = __name__,
+-version = "0.06y",
++version = "0.07",
+ author = 'Darafei Praliaskoiski',
+ author_email = 'm...@komzpa.net',
+ url = 'https://github.com/komzpa/twms',

Bug#1013594: insubstantial: FTBFS: Caused by: : java.lang.VerifyError: Expecting a stackmap frame at branch target 33

[Jerome Charaoui]

Control: user debian-rele...@lists.debian.org
Control: usertag -1 + bsp-2023-02-ca-montreal

Hello,

I've worked on this today: I can confirm the FTBFS issue occurs
consistently, but I wasn't able to find a solution.

Upstream isn't much help here: 7.3 is the latest release and was tagged
in 2014 (9 years ago) and the project is now archived/read-only on
GitHub.

If we removed this from Debian, notable packages affected would be
include triplea and scilab.

Thanks,

-- Jérôme

Bug#901245: Handling of -e violates policy for x-terminal-emulator

[Louis-Philippe Véronneau]

Ok, so pushing further.

-e does seem to work fine with terminator 2.1.2-1. At least, these 
commands works fine:


x-terminal-emulator -e 'if test -x /bin/ss ; then watch -t ss -putsw; 
else netstat -c; fi'


x-terminal-emulator -e 'watch /'

Adding "sh -c" fails though:


$ x-terminal-emulator -e bash -c 'watch /'

(x-terminal-emulator:98199): dbind-WARNING **: 14:48:34.964: AT-SPI: 
Error retrieving accessibility bus address: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not 
provided by any .service files


usage: x-terminal-emulator [-h] [-v] [-m] [-M] [-f] [-b] [-H] [-T 
FORCEDTITLE]

   [--geometry GEOMETRY] [--command COMMAND]
   [-e EXECUTE] [-g CONFIG] [-j CONFIGJSON]
   [-x EXECUTE] [--working-directory DIR]
   [-i FORCEDICON] [-r ROLE] [-l LAYOUT] [-s]
   [-p PROFILE] [-u] [-d]
   [--debug-classes DEBUG_CLASSES]
   [--debug-methods DEBUG_METHODS] [--new-tab]
   [--unhide] [--list-profiles] [--list-layouts]


This error does seem to be caused by the issue John pointed out.

Applying the upstream patch, calling this command doesn't error out 
anymore, but now replicates the "the window comes up and disappears 
immediately." issue:


x-terminal-emulator -e bash -c 'watch /'

This command still works fine though:

x-terminal-emulator -e 'watch /'

All this to say, I'm not sure this bug is serious? It seems the -e 
option does work?


I'll try to see what to do with this bug tomorrow.

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

Bug#1016732: [Pkg-javascript-devel] Bug#1016732: Please help to reproduce (Was: shiny-server: server-function? don't run)

[Pirate Praveen]

On ഞാ, ഫെബ്രു 26 2023 at 02:33:31 രാവിലെ 
+05:30:00 +05:30:00, Pirate Praveen  wrote:



On ഞാ, ഫെബ്രു 26 2023 at 02:24:00 രാവിലെ 
+05:30:00 +05:30:00, Nilesh Patra  wrote:

On Sun, Feb 26, 2023 at 12:46:15AM +0530, Pirate Praveen wrote:
Thanks for the pointer. However, unfortunately even after propagating
the "-t" flag with coffee, the generated code does not work to fine 
(the

UI is not functional).

For now I have vendored coffee1 generated code itself. Do you have 
any

other ideas?


I can see we are using rollup to generate iife format files, which 
may not be what npm dist tarball ships.


https://salsa.debian.org/js-team/node-sockjs/-/blob/master/debian/rules#L8

Upstream directly uses the output from coffee 
https://salsa.debian.org/js-team/node-sockjs/-/blob/master/Makefile#L9


You could play around with rollup output format options I think. Try 
umd format or try using webpack. You will have to inspect the npm 
dist tarball to see what format it has. Copying Akshay if he has some 
ideas.


Since we are using only lib directory in node, ignore the rollup part 
above. In sockjs 0.4 rc1 they removed coffee script dependency, so one 
thing we can try is to see if sockjs 0.4 rc1 works with shiny-server, 
though getting a new upstream version to bookworm may be a hard thing, 
but it may be a better option that vendoring what we have right now.

Bug#997179: marked as done (tty-clock: FTBFS: ttyclock.c:278:73: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 21:13:03 +
with message-id 
and subject line Bug#997179: fixed in tty-clock 2.3-2
has caused the Debian Bug report #997179,
regarding tty-clock: FTBFS: ttyclock.c:278:73: error: format not a string 
literal and no format arguments [-Werror=format-security]
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.)


-- 
997179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tty-clock
Version: 2.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -g $(ncurses5-config --cflags) 
> ttyclock.c -o tty-clock -Wl,-z,relro -Wl,-z,now $(ncurses5-config --libs)
> ttyclock.c: In function ‘draw_clock’:
> ttyclock.c:278:73: error: format not a string literal and no format arguments 
> [-Werror=format-security]
>   278 |   mvwprintw(ttyclock->datewin, (DATEWINH / 2), 1, 
> ttyclock->date.datestr);
>   |   
> ~~^~~~
> cc1: some warnings being treated as errors
> make[1]: *** [Makefile:26: tty-clock] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/tty-clock_2.3-1_unstable.log

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

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

If you 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.
--- End Message ---
--- Begin Message ---
Source: tty-clock
Source-Version: 2.3-2
Done: Antoine Beaupré 

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated tty-clock package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 25 Feb 2023 14:05:47 -0500
Source: tty-clock
Architecture: source
Version: 2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Closes: 997179
Changes:
 tty-clock (2.3-2) unstable; urgency=medium
 .
   * fix FTBFS (Closes: #997179)
Checksums-Sha1:
 836d8f3cc0835d6bd0f729f8676c185cf8daa25b 1507 tty-clock_2.3-2.dsc
 2f896bcf22edba0e56f704d5cb82169002393e9d 4052 tty-clock_2.3-2.debian.tar.xz
 ac8a07652d99370e6723e507a4b542423e1d25ea 5855 tty-clock_2.3-2_amd64.buildinfo
Checksums-Sha256:
 cf8b898ac7d345fedaa87579ced66d434e0747ff41adad0d802a71902477d7c6 1507 
tty-clock_2.3-2.dsc
 ad877c02f5c2d68a1193243f4d2f345909951eda3eecb749e09cb8064bcbf524 4052 
tty-clock_2.3-2.debian.tar.xz
 8a5ff3ed58261428b27c6d20d283e92029a48129c203e4227a5e78b0dad2a35f 5855 
tty-clock_2.3-2_amd64.buildinfo
Files:
 8dfe5ea0cb5de980e06644bb2d7c6f6c 1507 utils optional tty-clock_2.3-2.dsc
 aee2beac61c76d155d443de219b52ca2 4052 utils optional 
tty-clock_2.3-2.debian.tar.xz
 01fde41ec4a2b22869719fce3b68c063 5855 utils optional 
tty-clock_2.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAmP6XpQACgkQPqHd3bJh
2XvXMgf+Ib7gpjZ0xaEMtxPc8r5Du0BpHSCvJpV7ZeEfwZqx78nFvaQJ09473F47
sYEVviOtz4V7GbR2PyOQEPu0A107WO+hHpyF0f8Z/ZtVOeLhI8ePvln6F8Re8Bpn
OOO2Va2tlZXeQ/2/omSoqiLldc2Z2DuwUdMVDkL5ZoqfZuiWoScC3w/D8kqhzA0l
ZxBoRko1T8hwrFOiuHPb5F8CA8ffIEH9wLQr/8EnyAeYDHeEzJYUupIigdt8mKhF
TyxhF6TQORkJ07zSLro6GJEe0Qmw1QKkHkVH4UzXT0Ls+HcnyhW5VhU8GWwvPlEJ
znyMCC3pSgFKVp0+XZ4n+3oq4ozKQw==
=F4CH
-END PGP SIGNATURE End Message ---

Bug#1031935: marked as done (firmware-ath9k-htc: missing hardware identifiers in dep-11 metadata)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 21:10:44 +
with message-id 
and subject line Bug#1031935: fixed in open-ath9k-htc-firmware 
1.4.0-108-gd856466+dfsg1-1.3
has caused the Debian Bug report #1031935,
regarding firmware-ath9k-htc: missing hardware identifiers in dep-11 metadata
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.)


-- 
1031935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-ath9k-htc
Version: 1.4.0-108-gd856466+dfsg1-1.2
Severity: serious
Justification: regression in hardware support
X-Debbugs-Cc: b...@debian.org, debian-ker...@lists.debian.org, 
debian-b...@lists.debian.org

Hi,

Here's another thing that was totally overlooked while forcing the
switch from firmware-atheros to firmware-ath9k-htc in an uncoordinated
manner: the dep-11 metadata are (1) hardcoded in the firmware-ath9k-htc
package, and (2) out-of-date.

This means we're actively losing support for hardware by switching from
the non-free package to the one in main!

Right now, the following entries are missing:
 - AirTies AR9271
 - Altai WA1011N-GU

Those date back to v4.12-rc1 (2017) and v4.16-rc1 (2018) respectively:
 - 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=16ff1fb0e32f76a5d285a6f23b82d21aa52813c6
 - 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4e12d654ba068df06c5e4c8322d7dcced41e48ee


Surely checking feature parity should have been the very first step?
 
 
Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: open-ath9k-htc-firmware
Source-Version: 1.4.0-108-gd856466+dfsg1-1.3
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated open-ath9k-htc-firmware 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 25 Feb 2023 20:37:02 +0100
Source: open-ath9k-htc-firmware
Architecture: source
Version: 1.4.0-108-gd856466+dfsg1-1.3
Distribution: unstable
Urgency: medium
Maintainer: John Scott 
Changed-By: Bastian Germann 
Closes: 1031935
Changes:
 open-ath9k-htc-firmware (1.4.0-108-gd856466+dfsg1-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * DEP-11: Add AirTies and Altai WA1011N-GU. (Closes: #1031935)
   * DEP-11: Add firmware provides.
Checksums-Sha1:
 98c030bbba1edf39336ffb81960019917430d2d2 2067 
open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.3.dsc
 daa650aa0bba7e76bd8aa072f3795e6545674e43 14884 
open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.3.debian.tar.xz
 0dff122415eea9f9171b78081042112ede068bc3 7465 
open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.3_source.buildinfo
Checksums-Sha256:
 6539e2541575cf24ab41e6b567e6e679f034e1dbeb79539eccd0304acce7fc5a 2067 
open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.3.dsc
 6284f727928c67f5af1b0b8fe06494c1a4b0d275d073659eed8600fedcb8286a 14884 
open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.3.debian.tar.xz
 c8c4fd50911b18a984839448fa7f3bc575b65365ef9c1400d461f13efd4509ca 7465 
open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.3_source.buildinfo
Files:
 3b06f7855e98c0d83a1d747d72fefca5 2067 kernel optional 
open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.3.dsc
 78ab3bfa50c51cbd795ab9c7f5c83060 14884 kernel optional 
open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.3.debian.tar.xz
 6f0eb57407832d5316909bfbd1679e1b 7465 kernel optional 
open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmP6ZGIQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFKhWDADHEFkvcNQrMqMmJ6rqAy6bACfotrMSpoyy
Te0Oj8ItxKw0Qk6qqna5GjV9EnFB7M3ST9r7tWlKMLI16Ipe8MBp0RHOV0L+zokm
ajpoR9iYR2c3DytVd0x+ElL7VgJk9ukakZZ6MCEbAHZsH+n7T9OQs6ncYvagDU1F

Bug#1028625: marked as done (src:x-loader: fails to migrate to testing for too long: FTBFS)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 21:13:18 +
with message-id 
and subject line Bug#1028625: fixed in x-loader 1.5.1+git20110715+fca7cd2-4
has caused the Debian Bug report #1028625,
regarding src:x-loader: fails to migrate to testing for too long: FTBFS
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.)


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

Source: x-loader
Version: 1.5.1+git20110715+fca7cd2-2
Severity: serious
Control: close -1 1.5.1+git20110715+fca7cd2-3
X-Debbugs-CC: Marcos Talau 
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1026364

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:x-loader has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. The package failed to build from 
source, which was reported in bug 1026364.


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=x-loader



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: x-loader
Source-Version: 1.5.1+git20110715+fca7cd2-4
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated x-loader package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 25 Feb 2023 21:06:34 +0200
Source: x-loader
Architecture: source
Version: 1.5.1+git20110715+fca7cd2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 1026364 1028625
Changes:
 x-loader (1.5.1+git20110715+fca7cd2-4) unstable; urgency=medium
 .
   * QA upload.
   * Don't build with -Werror. (Closes: #1028625, #1026364)
Checksums-Sha1:
 b7449c644f453f5399ff22563a2bde197395ee6d 2164 
x-loader_1.5.1+git20110715+fca7cd2-4.dsc
 0f9d969f627e6eafd11b0739db949d155b72106d 4248 
x-loader_1.5.1+git20110715+fca7cd2-4.debian.tar.xz
Checksums-Sha256:
 60015b7b532d9bb5589af24bb1a7e3f5f7480523ba1a887aa8b068af5d81c7a3 2164 
x-loader_1.5.1+git20110715+fca7cd2-4.dsc
 e9d93bca32003b9c2659aa7c48314bdb689251ee6d311ea3572d710c0858a981 4248 
x-loader_1.5.1+git20110715+fca7cd2-4.debian.tar.xz
Files:
 e06f50a0247b5bf924e66dbbeef38a85 2164 misc optional 
x-loader_1.5.1+git20110715+fca7cd2-4.dsc
 9f42fe009deda5e78140f47e27f035c7 4248 misc optional 
x-loader_1.5.1+git20110715+fca7cd2-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmP6XYYACgkQiNJCh6LY
mLETKw//XMbiqSbw//zWpz/TEPkmBg4oSiaq73+F7JtZREztvDt5fyLSW+7Q6KOg
HPVnb2aQ77KhVOKlc0kEqMqviC5ZxNqauDqK+pnwEP6oItCTR+5oT4If/LjCcrRl
8eoTadLZqFwzQTZpOBJe6Fgs9ZkfL+RZM38FySbj81RTzZ/cb8VANwdAZmTeRNgm
R+jL44PU15VG3bevIxe3lSP1lsgGoR+3lmdGsIdT29O7yUp8reDeOeJs+jZ4iOQ1

Bug#1026364: marked as done (FTBFS: error: dangling pointer ‘dentptr’ to ‘dent’ may be used)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 21:13:18 +
with message-id 
and subject line Bug#1026364: fixed in x-loader 1.5.1+git20110715+fca7cd2-4
has caused the Debian Bug report #1026364,
regarding FTBFS: error: dangling pointer ‘dentptr’ to ‘dent’ may be used
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.)


-- 
1026364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: x-loader
Version: 1.5.1+git20110715+fca7cd2-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Dear QA Group,

the package x-loader was recently gifted to you, but it FTBFS:


gcc -g  -Os  -fno-strict-aliasing  -fno-common -ffixed-r8 -msoft-float -Werror  
-D__KERNEL__ -DTEXT_BASE=0x40304350 
-I/<>/debian/build/omap4430panda/include 
-I/<>/include -fno-builtin -ffreestanding -nostdinc -isystem 
/usr/lib/gcc/arm-linux-gnueabi/12/include -pipe -DCONFIG_ARM -D__ARM__ 
-march=armv7-a -mabi=apcs-gnu -Wall -Wstrict-prototypes -marm 
-fno-stack-protector -g  -Os  -fno-strict-aliasing  -fno-common -ffixed-r8 
-msoft-float -Werror  -D__KERNEL__ -DTEXT_BASE=0x40304350 
-I/<>/debian/build/omap4430panda/include 
-I/<>/include -fno-builtin -ffreestanding -nostdinc -isystem 
/usr/lib/gcc/arm-linux-gnueabi/12/include -pipe -DCONFIG_ARM -D__ARM__ 
-march=armv7-a -mabi=apcs-gnu -Wall -Wstrict-prototypes -marm 
-fno-stack-protector -c -o 
/<>/debian/build/omap4430panda/fs/fat/fat.o fat.c
fat.c: In function ‘do_fat_read’:
fat.c:848:11: error: dangling pointer ‘dentptr’ to ‘dent’ may be used 
[-Werror=dangling-pointer=]
  848 | ret = get_contents (mydata, dentptr, buffer, maxsize);
  |   ^~~
fat.c:813:19: note: ‘dent’ declared here
  813 | dir_entry dent;
  |   ^~~~


Error looks the same on both armel and armhf.

Maybe removal would have been a better idea.

Best,
Chris
--- End Message ---
--- Begin Message ---
Source: x-loader
Source-Version: 1.5.1+git20110715+fca7cd2-4
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated x-loader package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 25 Feb 2023 21:06:34 +0200
Source: x-loader
Architecture: source
Version: 1.5.1+git20110715+fca7cd2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 1026364 1028625
Changes:
 x-loader (1.5.1+git20110715+fca7cd2-4) unstable; urgency=medium
 .
   * QA upload.
   * Don't build with -Werror. (Closes: #1028625, #1026364)
Checksums-Sha1:
 b7449c644f453f5399ff22563a2bde197395ee6d 2164 
x-loader_1.5.1+git20110715+fca7cd2-4.dsc
 0f9d969f627e6eafd11b0739db949d155b72106d 4248 
x-loader_1.5.1+git20110715+fca7cd2-4.debian.tar.xz
Checksums-Sha256:
 60015b7b532d9bb5589af24bb1a7e3f5f7480523ba1a887aa8b068af5d81c7a3 2164 
x-loader_1.5.1+git20110715+fca7cd2-4.dsc
 e9d93bca32003b9c2659aa7c48314bdb689251ee6d311ea3572d710c0858a981 4248 
x-loader_1.5.1+git20110715+fca7cd2-4.debian.tar.xz
Files:
 e06f50a0247b5bf924e66dbbeef38a85 2164 misc optional 
x-loader_1.5.1+git20110715+fca7cd2-4.dsc
 9f42fe009deda5e78140f47e27f035c7 4248 misc optional 
x-loader_1.5.1+git20110715+fca7cd2-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmP6XYYACgkQiNJCh6LY
mLETKw//XMbiqSbw//zWpz/TEPkmBg4oSiaq73+F7JtZREztvDt5fyLSW+7Q6KOg
HPVnb2aQ77KhVOKlc0kEqMqviC5ZxNqauDqK+pnwEP6oItCTR+5oT4If/LjCcrRl
8eoTadLZqFwzQTZpOBJe6Fgs9ZkfL+RZM38FySbj81RTzZ/cb8VANwdAZmTeRNgm
R+jL44PU15VG3bevIxe3lSP1lsgGoR+3lmdGsIdT29O7yUp8reDeOeJs+jZ4iOQ1
LjsdhflTJrMwCk+jb5mIVWRl70A2tLpqRqH4pE3La/InQH3lbrTN8Q4yBKG11Een
DFzrJnm/hYp3F93z8p5delFMApI0tddAT9ep/543m+o1BCmVHcO3UYpPm6kUTjh7
Agd1AZ2xHMwK9JBTHFkhEMav5OAN68sBItvECfVae2o/RRuhqtnuuC5+C4HXQh84
UdUYgDareU9PbyJtuivgT6nwwyc7MZwBDqMYKEcWV9DKxsE9N2WE5wOCeUJciDIi
QxsGO/RNCvEWsO6ySH2k2VM6gtX5ybK+YaMAK2c0eNSwZS5eLhUy+Yi3EzkTUhuP

Bug#1031950: libgeo-distance-perl should add Breaks and Replaces on libgeo-distance-xs-perl

[Adrian Bunk]

Package: libgeo-distance-perl
Version: 0.25-2
Severity: serious

Upgrading libgeo-distance-perl from bullseye to bookworm should
remove libgeo-distance-xs-perl since it is now useless.

Bug#1016732: Please help to reproduce (Was: shiny-server: server-function? don't run)

[Pirate Praveen]

On ഞാ, ഫെബ്രു 26 2023 at 02:24:00 രാവിലെ 
+05:30:00 +05:30:00, Nilesh Patra  wrote:

On Sun, Feb 26, 2023 at 12:46:15AM +0530, Pirate Praveen wrote:
Thanks for the pointer. However, unfortunately even after propagating
the "-t" flag with coffee, the generated code does not work to fine 
(the

UI is not functional).

For now I have vendored coffee1 generated code itself. Do you have any
other ideas?


I can see we are using rollup to generate iife format files, which may 
not be what npm dist tarball ships.


https://salsa.debian.org/js-team/node-sockjs/-/blob/master/debian/rules#L8

Upstream directly uses the output from coffee 
https://salsa.debian.org/js-team/node-sockjs/-/blob/master/Makefile#L9


You could play around with rollup output format options I think. Try 
umd format or try using webpack. You will have to inspect the npm dist 
tarball to see what format it has. Copying Akshay if he has some ideas.

Processed: libzypp: diff for NMU version 17.25.7-2.4

[Debian Bug Tracking System]

Processing control commands:

> tags 1028680 + patch
Bug #1028680 [src:libzypp] libzypp: FTBFS: RpmHeader.cc:41:16: error: ‘strcmp’ 
was not declared in this scope
Added tag(s) patch.
> tags 1028680 + pending
Bug #1028680 [src:libzypp] libzypp: FTBFS: RpmHeader.cc:41:16: error: ‘strcmp’ 
was not declared in this scope
Added tag(s) pending.

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

Bug#1028680: libzypp: diff for NMU version 17.25.7-2.4

[Adrian Bunk]

Control: tags 1028680 + patch
Control: tags 1028680 + pending

Dear maintainer,

I've prepared an NMU for libzypp (versioned as 17.25.7-2.4) and uploaded 
it to DELAYED/5. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru libzypp-17.25.7/debian/changelog libzypp-17.25.7/debian/changelog
--- libzypp-17.25.7/debian/changelog	2022-12-08 13:07:05.0 +0200
+++ libzypp-17.25.7/debian/changelog	2023-02-25 22:30:40.0 +0200
@@ -1,3 +1,10 @@
+libzypp (17.25.7-2.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS due to missing #include. (Closes: #1028680)
+
+ -- Adrian Bunk   Sat, 25 Feb 2023 22:30:40 +0200
+
 libzypp (17.25.7-2.3) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru libzypp-17.25.7/debian/patches/RpmHeader-include.patch libzypp-17.25.7/debian/patches/RpmHeader-include.patch
--- libzypp-17.25.7/debian/patches/RpmHeader-include.patch	1970-01-01 02:00:00.0 +0200
+++ libzypp-17.25.7/debian/patches/RpmHeader-include.patch	2023-02-25 22:30:40.0 +0200
@@ -0,0 +1,15 @@
+Description: Fix FTBFS due to missing #include
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/1028680
+
+--- libzypp-17.25.7.orig/zypp/target/rpm/RpmHeader.cc
 libzypp-17.25.7/zypp/target/rpm/RpmHeader.cc
+@@ -11,6 +11,8 @@
+ */
+ #include "librpm.h"
+ 
++#include 
++
+ 
+ // unameToUid and gnameToGid are shamelessly stolen from rpm-4.4.
+ // (rpmio/ugid.c) Those functions were dropped in RPM_4_7
diff -Nru libzypp-17.25.7/debian/patches/series libzypp-17.25.7/debian/patches/series
--- libzypp-17.25.7/debian/patches/series	2022-12-08 13:01:08.0 +0200
+++ libzypp-17.25.7/debian/patches/series	2023-02-25 22:30:40.0 +0200
@@ -4,3 +4,4 @@
 0001-Add-missing-includes-for-GCC-11-bsc-1181874.patch
 0001-Fix-building-with-GCC-12.x-release.patch
 1010_gpgme-pkg_search_module.diff
+RpmHeader-include.patch

Bug#1031947: marked as done (eos-sdk: FTBFS everywhere)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 20:54:51 +
with message-id 
and subject line Bug#1031947: fixed in eos-sdk 0~git20230107+ds-2
has caused the Debian Bug report #1031947,
regarding eos-sdk: FTBFS everywhere
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.)


-- 
1031947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eos-sdk
Version: 0~git20230107+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/package.php?p=eos-sdk=sid

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: eos-sdk
Source-Version: 0~git20230107+ds-2
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated eos-sdk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 25 Feb 2023 21:06:31 +0100
Source: eos-sdk
Architecture: source
Version: 0~git20230107+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 1031947
Changes:
 eos-sdk (0~git20230107+ds-2) unstable; urgency=medium
 .
   * Fix FTBFS by installing files from libexec (Closes: #1031947).
Checksums-Sha1:
 ccf7d82acf0172308ede2725a0880351f54f685c 1907 eos-sdk_0~git20230107+ds-2.dsc
 4e59cef1f88e0f5866d4546586359b4507b6df1b 3500 
eos-sdk_0~git20230107+ds-2.debian.tar.xz
Checksums-Sha256:
 8b4c74150f54466ba01a3de4276aa4e2d5a5df39ced0a304650e569c0cbcb4ce 1907 
eos-sdk_0~git20230107+ds-2.dsc
 fa2551d26b38d5e1bdb2d2764e2d5966a789802a212553cfd5a79d48f788cbc9 3500 
eos-sdk_0~git20230107+ds-2.debian.tar.xz
Files:
 891fa960db41cd3653b0e3ecc3dd1c97 1907 libs optional 
eos-sdk_0~git20230107+ds-2.dsc
 83c8939b8092c4ea53a176a7c7fb079e 3500 libs optional 
eos-sdk_0~git20230107+ds-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSD3NF/RLIsyDZW7aHoRGtKyMdyYQUCY/pqZgAKCRDoRGtKyMdy
YS2SAQC3bH5VaX2UkK6ope7dq9Of5ENchetXGWvE4iZs+vjPYwD+Pz8HQ5ddTdEE
qvW/Z1uZuvZLpItEJN57mTrBPK2CdAk=
=noKN
-END PGP SIGNATURE End Message ---

Bug#1016732: Please help to reproduce (Was: shiny-server: server-function? don't run)

[Nilesh Patra]

On Sun, Feb 26, 2023 at 12:46:15AM +0530, Pirate Praveen wrote:
> On Sun, 12 Feb 2023 23:16:06 +0530 Nilesh Patra  wrote:
> > Sorry for pinging you again, but would you be able to take a look at this
> please?
> > I don't know enough coffeescript to be able to check this and it'd be
> > awesome if you could consider taking a look.
> 
> Coffeescript 2 creates ESM format js by default, adding -t option to coffee
> command should give you the old ES5 javascript like coffeescript 1.x
> 
> See https://salsa.debian.org/js-team/node-sockjs/-/blob/master/Makefile#L11

Thanks for the pointer. However, unfortunately even after propagating
the "-t" flag with coffee, the generated code does not work to fine (the
UI is not functional).

For now I have vendored coffee1 generated code itself. Do you have any
other ideas?

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1028398: snapd: both Telegram-desktop and Skype cannot load and save files

[Gabriel Filion]

Hi there,

This could be happening for many reasons. Just to investigate one 
possiblity: in your syslog do you see messages from apparmor when you 
try to load a file?

Processed: Re: nodejs: [arm64] RangeError: Maximum call stack size exceeded

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/nodejs/node/issues/41163
Bug #1030284 [nodejs] nodejs: [arm64] RangeError: Maximum call stack size 
exceeded
Set Bug forwarded-to-address to 'https://github.com/nodejs/node/issues/41163'.

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

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

[James Addison]

Package: nodejs
Followup-For: Bug #1030284
Control: forwarded -1 https://github.com/nodejs/node/issues/41163

Processed: owner 987008

[Debian Bug Tracking System]

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

> owner 987008 anar...@debian.org
Bug #987008 [grub2] Grub fails to find LVM volume after previous LV rename
Owner recorded as anar...@debian.org.
> thanks
Stopping processing here.

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

Bug#987008: working on this bug

[Antoine Beaupré]

owner 987008 anar...@debian.org
thanks

Hi,

I've ported the submitted patch here into the package and plan to upload
an NMU shortly.

To quote the actual patch file I ended up with:

Description: fix renamed LV detection
  It looks like the detection of the LVM logical volumes fails in
  certain edge conditions. In particular, it was reported that
  renaming an LV will make grub fail to boot from the system as it
  cannot properly detect it anymore.
  .
  I have looked at the code surrounding the patch and cannot claim to
  understand the entire function here, as it is huge and quite
  cryptic. But it seems sane: the `ptr` we're inspecting here starts
  at the `rlocn->offset`, but we were adding `mda_size` to the
  (somewhat) unrelated metadatabuf instead. Now we're marking the
  `mda_end` correctly, based on the rlocn->offsite and ->size.
  .
  I have not tested this myself as the test setup is quite involved,
  but it seems others (e.g. "Hoyer, David" )
  have tested the patch and confirmed it worked.

A.

-- 
Never be deceived that the rich will allow you to vote away their wealth.
- Lucy Parsons

Bug#1028725: flycheck: FTBFS: make: *** [debian/rules:4: binary] Error 25

[Sergio Durigan Junior]

On Monday, February 20 2023, David Bremner wrote:

> David Bremner  writes:
>
>> I don't think these are the same as previously encountered
>> native-compilation related failures. I get the same / similar failures
>> when running
>>
>> EMACS_INHIBIT_AUTOMATIC_NATIVE_COMPILATION=t emacs -q -batch -L . -l 
>> buttercup -f buttercup-run-discover
>>
>> as a non-root user with a defined home directory. Log is attached (there
>> is one more failure in the log, iiuc related to gpg missing in the
>> chroot).
>
> With the latest upstream master (32-182-g5561440) which contains the
> merge of PR 2002, this is down to 2 failures, both trampoline related.

Very similar failures are also affecting emacs-web-server:

  
https://ci.debian.net/data/autopkgtest/unstable/amd64/e/emacs-web-server/31076037/log.gz

I suspected the problem could be related to emacs-buttercup, so I
updated it locally to the latest upstream version and rebuilt flycheck
with it, to no avail.

Thanks,

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


signature.asc
Description: PGP signature

Bug#1031880: unattended-upgrades: requires on_ac_power from package powermgmt-base to function at all

[Steve Lane]

Hi Jochen,

Thanks very much for looking into this so quickly. On a machine with root's
$PATH set to the default value:

/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Without powermgmt-base installed, I am seeing the following:

root# which -a on_ac_power
root#

(i.e. an executable on_ac_power is not found anywhere in root's $PATH), and;

root# for p in $( echo $PATH | sed 's/:/ /g' ) ; do ls -l ${p}/on_ac_power
; done
ls: cannot access '/usr/local/sbin/on_ac_power': No such file or directory
ls: cannot access '/usr/local/bin/on_ac_power': No such file or directory
ls: cannot access '/usr/sbin/on_ac_power': No such file or directory
ls: cannot access '/usr/bin/on_ac_power': No such file or directory
ls: cannot access '/sbin/on_ac_power': No such file or directory
ls: cannot access '/bin/on_ac_power': No such file or directory
root#

(i.e. as far as I am able to determine, there is no on_ac_power file in root's
$PATH without powermgmt-base installed on this machine).

Note that, in this situation, I am seeing the following:

root# which unattended-upgrade
/usr/bin/unattended-upgrade
root# unattended-upgrade
root#

(i.e. normal / expected behavior from unattended-upgrade).

After installing powermgmt-base, I see the following:

root# which -a on_ac_power
/usr/sbin/on_ac_power
/usr/bin/on_ac_power
/sbin/on_ac_power
/bin/on_ac_power
root# for p in $( echo $PATH | sed 's/:/ /g' ) ; do ls -l ${p}/on_ac_power
; done
ls: cannot access '/usr/local/sbin/on_ac_power': No such file or directory
ls: cannot access '/usr/local/bin/on_ac_power': No such file or directory
-rwxr-xr-x 1 root root 2228 Jul 20  2019 /usr/sbin/on_ac_power
lrwxrwxrwx 1 root root 17 Jul 20  2019 /usr/bin/on_ac_power ->
/sbin/on_ac_power
-rwxr-xr-x 1 root root 2228 Jul 20  2019 /sbin/on_ac_power
lrwxrwxrwx 1 root root 17 Jul 20  2019 /bin/on_ac_power -> /sbin/on_ac_power

and unattended-upgrade continues to behave normally.

I suspect that what happened was, on the machines I was testing on,
incomplete uninstalls of powermgmt-base resulted in the executables being
removed, but the links in /usr/bin and/or /bin to remain, creating the
problem I was seeing.

(I have a very slight idea how this might have happened, but that is a
separate issue.)

I think your recommended solution under these circumstances is the right
one. Thanks again very much for looking into this. Please feel free to
close this ticket (if you have not done so already).

Best,
--
Steve Lane

On Sat, Feb 25, 2023 at 12:21 AM Jochen Sprickerhof 
wrote:

> Hi Steve,
>
> * Steve Lane  [2023-02-24 09:23]:
> >Currently unattended-upgrades marks the powermgmt-base package
> >as Suggested. powermgmt-base provides the /sbin/on_ac_power and
> >/usr/sbin/on_ac_power script(s), which unattended-upgrades requires to
> >function at all, because of this check in /usr/bin/unattended-upgrade
> >at line 676:
> >
> >if apt_pkg.config.find_b("Unattended-Upgrade::OnlyOnACPower", True) \
> >   and subprocess.call("on_ac_power") == 1:
> >
> >The absence of the powermgmt-base package, and thus the on_ac_power
> >script, results in the following error:
> >
> >root# /usr/bin/unattended-upgrade
> >Traceback (most recent call last):
> >  File "/usr/bin/unattended-upgrade", line 2522, in 
> >sys.exit(main(options))
> >  File "/usr/bin/unattended-upgrade", line 1993, in main
> >res = run(options, rootdir, mem_log, logfile_dpkg,
> >  File "/usr/bin/unattended-upgrade", line 2061, in run
> >if should_stop():
> >  File "/usr/bin/unattended-upgrade", line 676, in should_stop
> >and subprocess.call("on_ac_power") == 1:
> >  File "/usr/lib/python3.9/subprocess.py", line 349, in call
> >with Popen(*popenargs, **kwargs) as p:
> >  File "/usr/lib/python3.9/subprocess.py", line 951, in __init__
> >self._execute_child(args, executable, preexec_fn, close_fds,
> >  File "/usr/lib/python3.9/subprocess.py", line 1823, in _execute_child
> >raise child_exception_type(errno_num, err_msg, err_filename)
> >PermissionError: [Errno 13] Permission denied: 'on_ac_power'
>
> I can't reproduce this error on a fresh stable nor unstable VM without
> powermgmt-base installed.
>
> >(Note that it's not clear to me why this is a PermissionError, since
> >the script doesn't actually exist, but that is a secondary point.)
>
> But this makes it reproducible:
>
> touch /usr/bin/on_ac_power
>
> So I guess you have a non executable on_ac_power in your $PATH.
>
> >The powermgmt-base package needs to be installed in order for
> >unattended-upgrades to function at all. Thus, the powermgmt-base package
> >needs to be marked as Depends for unattended-upgrades.
>
> I disagree and propose this patch instead:
>
> https://github.com/mvo5/unattended-upgrades/pull/341
>
> Cheers Jochen
>

Processed: bookworm-ignore

[Debian Bug Tracking System]

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

> # tzdata change got reverted for now
> tag 1031442 bookworm-ignore
Bug #1031442 {Done: Adrian Bunk } [src:gnustep-base] 
gnustep-base: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 
--verbose" VERBOSE=1 messages=yes returned exit code 2
Added tag(s) bookworm-ignore.
> thanks
Stopping processing here.

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

Processed: Re: Bug#997179: tty-clock: FTBFS: ttyclock.c:278:73: error: format not a string literal and no format arguments [-Werror=format-security]

[Debian Bug Tracking System]

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

> tag 997179 +pending
Bug #997179 [src:tty-clock] tty-clock: FTBFS: ttyclock.c:278:73: error: format 
not a string literal and no format arguments [-Werror=format-security]
Added tag(s) pending.
> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was anar...@debian.org).
> usertag 997179 + bsp-2023-02-ca-montreal
Usertags were: bsp-2023-02-ca-montreal.
Usertags are now: bsp-2023-02-ca-montreal.
> thanks
Stopping processing here.

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

Bug#997179: tty-clock: FTBFS: ttyclock.c:278:73: error: format not a string literal and no format arguments [-Werror=format-security]

[Antoine Beaupré]

tag 997179 +pending
user debian-rele...@lists.debian.org
usertag 997179 + bsp-2023-02-ca-montreal
thanks

I've orphaned this package (#1031941) but I figured I could at least fix
this bug before I go.
-- 
When the power of love overcomes love of power the world will know peace.
- Jimi Hendrix

Bug#1031947: eos-sdk: FTBFS everywhere

[Sebastian Ramacher]

Source: eos-sdk
Version: 0~git20230107+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/package.php?p=eos-sdk=sid

Cheers
-- 
Sebastian Ramacher

Bug#1000209: Bug #1000209

[Charles Flèche]

Hi, I'm working with Gabriel on this as part of a BSP. Problems experienced
earlier were caused by us trying to build the package in bullseye. We tried
again from bookworm and were able to build the package again.

We've been able to install the package using the attached patch that
doesn't hack around the migration to timidity-daemon. Does this approach
looks OK ?
diff --git a/debian/timidity-daemon.postinst b/debian/timidity-daemon.postinst
index a3610f9..573bc09 100644
--- a/debian/timidity-daemon.postinst
+++ b/debian/timidity-daemon.postinst
@@ -53,14 +53,6 @@ esac
 
 rm -f /etc/timidity/timidity.daemon
 
-# make sure we really stop, because packaging system doesn't
-# understand what we're trying to do with migration to timidity-daemon
-[ -f "/etc/init.d/timidity" ] && if which invoke-rc.d >/dev/null 2>&1; then
-  invoke-rc.d timidity stop
-else
-  /etc/init.d/timidity stop
-fi
-
 #DEBHELPER#
 
 exit 0

Processed: tagging 1025884

[Debian Bug Tracking System]

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

> tags 1025884 + fixed
Bug #1025884 {Done: Paul Gevers } [src:ddnet] src:ddnet: 
fails to migrate to testing for too long: FTBFS on s390x
Added tag(s) fixed.
> thanks
Stopping processing here.

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

Bug#1019273: package built and lintian passed

[Znoteer]

I forgot to mention, that I added the COPYING file to and built apt 2.5.6, and 
not apt 2.5.2 against which the bug was reported. It was against 2.5.6 that 
lintian was run.

-- 
Znoteer
znot...@mailbox.org

Bug#1019273: package built and lintian passed

[Znoteer]

I built the package with the new copyright file, and ran the resulting .changes 
file through lintian. 

There were no errors reported by lintian, so the COPYING file provided appears 
to have correct systax.

-- 
Znoteer
znot...@mailbox.org

Bug#1016732: Please help to reproduce (Was: shiny-server: server-function don't run)

[Pirate Praveen]

On Sun, 12 Feb 2023 23:16:06 +0530 Nilesh Patra  
wrote:
> Sorry for pinging you again, but would you be able to take a look at 
this please?

> I don't know enough coffeescript to be able to check this and it'd be
> awesome if you could consider taking a look.

Coffeescript 2 creates ESM format js by default, adding -t option to 
coffee command should give you the old ES5 javascript like coffeescript 
1.x


See 
https://salsa.debian.org/js-team/node-sockjs/-/blob/master/Makefile#L11

Bug#901245: Handling of -e violates policy for x-terminal-emulator

[Louis-Philippe Véronneau]

user debian-rele...@lists.debian.org 


usertag 901245 + bsp-2023-02-ca-montreal
thank you

Thanks for the excellent debugging session :)

I've tried to apply the patch [1] but it does not seem to fix the bug 
itself.


I'll try to dig further during the Montreal BSP.

Cheers,

[1]: 
https://github.com/gnome-terminator/terminator/commit/91cc928f0de1f9d6d51136cf50f06c35b5faca62.patch


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

Processed: ltrace: diff for NMU version 0.7.3-6.4

[Debian Bug Tracking System]

Processing control commands:

> tags 1023436 + patch
Bug #1023436 [ltrace] unusable on mipsel: unexpected breakpoint at 0x...
Added tag(s) patch.
> tags 1023436 + pending
Bug #1023436 [ltrace] unusable on mipsel: unexpected breakpoint at 0x...
Added tag(s) pending.

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

Bug#1023436: ltrace: diff for NMU version 0.7.3-6.4

[Adrian Bunk]

Control: tags 1023436 + patch
Control: tags 1023436 + pending

Dear maintainer,

I've prepared an NMU for ltrace (versioned as 0.7.3-6.4) and uploaded
it to DELAYED/5. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru ltrace-0.7.3/debian/changelog ltrace-0.7.3/debian/changelog
--- ltrace-0.7.3/debian/changelog	2022-05-03 02:51:56.0 +0300
+++ ltrace-0.7.3/debian/changelog	2023-02-25 20:40:34.0 +0200
@@ -1,3 +1,11 @@
+ltrace (0.7.3-6.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Stop building for MIPS, ltrace no longer works there.
+(Closes: #1023436)
+
+ -- Adrian Bunk   Sat, 25 Feb 2023 20:40:34 +0200
+
 ltrace (0.7.3-6.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ltrace-0.7.3/debian/control ltrace-0.7.3/debian/control
--- ltrace-0.7.3/debian/control	2022-03-31 02:48:13.0 +0300
+++ ltrace-0.7.3/debian/control	2023-02-25 20:22:06.0 +0200
@@ -6,7 +6,7 @@
 Build-Depends: debhelper-compat (= 13), libiberty-dev, libelf-dev, libselinux1-dev
 
 Package: ltrace
-Architecture: alpha amd64 ia64 i386 mips mipsel powerpc powerpcspe ppc64 s390 s390x sparc
+Architecture: alpha amd64 ia64 i386 powerpc powerpcspe ppc64 s390 s390x sparc
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: Tracks runtime library calls in dynamically linked programs
  ltrace is a debugging program which runs a specified command until it

Bug#916596: marked as done (iptables.postinst failure on link creation)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 20:17:15 +0200
with message-id 
and subject line Re: Bug#916596: iptables.postinst failure on link creation
has caused the Debian Bug report #916596,
regarding iptables.postinst failure on link creation
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.)


-- 
916596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iptables
Version: 1.8.2-2+b1
Severity: important

Dear Maintainer,

Issue occure during iptables:i386 1.8.2-2 -> 1.8.2-2+b1 upgrade.

/var/lib/dpkg/info/iptables.postinst fail with message:

ln: failed to create symbolic link ''$'\t''  /sbin/iptables-save': No such 
file or directory

The root cause is here :


LIST="/sbin/iptables
  /sbin/iptables-save
  /sbin/iptables-restore
  /sbin/ip6tables
  /sbin/ip6tables-save
  /sbin/ip6tables-restore"

for i in $LIST ; do


There are tabs before "/sbin/", so this cause "for i in $LIST" issue (tabs are 
used as a file name)

Workaround: Remove tabs:


LIST="/sbin/iptables
/sbin/iptables-save
/sbin/iptables-restore
/sbin/ip6tables
/sbin/ip6tables-save
/sbin/ip6tables-restore"


Issue are similar with #914074 and #914129, but not exactly the sames.

Thanks for your help.

Best regards,
Olivier

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (90, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.18.0-2-686-pae (SMP w/4 CPU cores)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages iptables depends on:
ii  libc62.28-2
ii  libip4tc01.8.2-2+b1
ii  libip6tc01.8.2-2+b1
ii  libiptc0 1.8.2-2+b1
ii  libmnl0  1.0.4-2
ii  libnetfilter-conntrack3  1.0.7-1
ii  libnfnetlink01.0.1-3+b1
ii  libnftnl11   1.1.2-2
ii  libxtables12 1.8.2-2+b1

iptables recommends no packages.

Versions of packages iptables suggests:
ii  kmod  25-2

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "fr_FR.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

-- debsums errors found:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "fr_FR.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
--- End Message ---
--- Begin Message ---
Version: 1.8.4-1

On Sun, Feb 05, 2023 at 02:27:47PM +, Jeremy Sowden wrote:
>...
> 
> That sym-link code was removed in 1.8.4-1, which was uploaded at the end
> of 2019.

Sorry for the confusion, debugging my issue it seems to be a problem in 
ebtables that I'll report there.

> J.

cu
Adrian--- End Message ---

Bug#1031942: marked as done (sphinxbase: Please drop the ltrace build dependency on mipsel)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 18:20:19 +
with message-id 
and subject line Bug#1031942: fixed in sphinxbase 0.8+5prealpha+1-16
has caused the Debian Bug report #1031942,
regarding sphinxbase: Please drop the ltrace build dependency on mipsel
to be marked as done.

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

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


-- 
1031942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinxbase
Version: 0.8+5prealpha+1-15
Severity: serious
Control: block 1023436 by -1

I am planning to fix #1023436 by dropping the broken mipsel binary,
and sphinxbase is the only user.

sphinxbase uses ltrace only for debugging in case of test failure,
checking the logfile that is not shown with the current non-failing
tests the ltrace output on mipsel looks like #1023436.
--- End Message ---
--- Begin Message ---
Source: sphinxbase
Source-Version: 0.8+5prealpha+1-16
Done: Samuel Thibault 

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated sphinxbase package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 25 Feb 2023 19:13:43 +0100
Source: sphinxbase
Architecture: source
Version: 0.8+5prealpha+1-16
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Closes: 1031942
Changes:
 sphinxbase (0.8+5prealpha+1-16) unstable; urgency=medium
 .
   * control: Drop ltrace dependency on mipsel (Closes: Bug#1031942)
Checksums-Sha1:
 cfbca8bb644aeadead1c147359260c18c9d7ad5d 2685 sphinxbase_0.8+5prealpha+1-16.dsc
 c45707c636b340b858411e64037acdc38de5028e 16168 
sphinxbase_0.8+5prealpha+1-16.debian.tar.xz
 d51dad20485a0f95ad3271543f97cdd1d19001a0 10447 
sphinxbase_0.8+5prealpha+1-16_source.buildinfo
Checksums-Sha256:
 d48cbbec8151f8c36ec5270f51f8c0f5971b6285fb47d1638ade2437a6885980 2685 
sphinxbase_0.8+5prealpha+1-16.dsc
 3f754cac04ae963262b7d8dfb28eb704ad0aaf906495a6f112b93186eb2f1ab6 16168 
sphinxbase_0.8+5prealpha+1-16.debian.tar.xz
 2cae8792c9c10d4b13d662e4d8cec95e6f681bdc85c619821fdc812ad4611e41 10447 
sphinxbase_0.8+5prealpha+1-16_source.buildinfo
Files:
 4556ea37b120f2351cd9aeef1757d4df 2685 sound optional 
sphinxbase_0.8+5prealpha+1-16.dsc
 eedd4d749c15d6a6fbc6d3c7e6f45d54 16168 sound optional 
sphinxbase_0.8+5prealpha+1-16.debian.tar.xz
 8c318cf1680c83fb2387dbc69a74640a 10447 sound optional 
sphinxbase_0.8+5prealpha+1-16_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEZTSF1IMOAGwT71n/aHTOWK4tfj8FAmP6T/IVHHN0aGliYXVs
dEBkZWJpYW4ub3JnAAoJEGh0zliuLX4/MCIP/2Bl+UzbAd15bGqWUmpEiUjh0r0l
zXWiZ6C4qVyUMy5DqGA1jzC59Usj4EfsufB2NrAHYY1w4xLcxS3Bde92MJMzdxui
Xa6D7qrP5Ml/vJXJH4pMuqBXRM3L0ZX+Iz7J7Ae8v/zrDvLHecGYS2A5F7kSqyFR
0pHNgxdEPe3/99+D77d8V/95OltNfvp18BHzPAjNVY3xDg0sdrMnm318HuMa/75z
w1NPtzXfHHlPo05wdKpd3nUAexAOP5GkmibBStNp1VJrR9MplbyvEQxo7JSpYjdX
/z/dp6G5sYPmuY+kh7uwvQkEaBe6SExfhQ+hzYQlhS1W4GYZjQw7b+VJ3qDb4BIM
3TU5l1dk+SN5LJ0rHoCOr2jCo+X1utJUnCFvRentvB3W7QPTNwMn6q8tr6P17srm
WRRmvqlM4xMCCcGVD9X5tCuD/7C2ftmlABvlTRPtDNTxDNItFm72ZUodp7mzuddy
Umc2YhOXxIhHcHVzrtFp/KcSFJPLOHlmRb1lHfNEImRuU0UHjNZ3Unqrd841ID7q
EEpbZ+10vYffOzgcsxMlEy86c8HltfW18pSnNfhlk3IW45xKTNrF7fWNf1GP8rsI
GKToAnpuFK4mHGlTLVVlbSSEJznU+5ZXj1A0fuNkwb85ffOTNJBCWf5mH96/UWY1
Sin8lT1McrxqP9TM
=+4ld
-END PGP SIGNATURE End Message ---

Bug#1031943: ebtables: symlink removal removal code in the postinst does not seem to be working

[Adrian Bunk]

Package: ebtables
Version: 2.0.11-5
Severity: serious

...
Setting up ebtables (2.0.11-5) ...
update-alternatives: using /usr/sbin/ebtables-legacy to provide 
/usr/sbin/ebtables (ebtables) in auto mode
update-alternatives: error: cannot stat file '/usr/sbin/ebtables': Too many 
levels of symbolic links
dpkg: error processing package ebtables (--configure):
...


This is due to (with merged /usr):
lrwxrwxrwx 1 root root 18 Apr  6  2022 /sbin/ebtables -> /usr/sbin/ebtables
lrwxrwxrwx 1 root root 26 Apr  6  2022 /sbin/ebtables-restore -> 
/usr/sbin/ebtables-restore
lrwxrwxrwx 1 root root 23 Apr  6  2022 /sbin/ebtables-save -> 
/usr/sbin/ebtables-save


Adding "set -x" in /var/lib/dpkg/info/ebtables.postinst shows:
...
+ LIST=ebtables ebtables-save ebtables-restore
+ [ -e /sbin/ebtables ]
+ [ -e /sbin/ebtables-save ]
+ [ -e /sbin/ebtables-restore ]
+ [ configure = configure ]
...


Using -h instead of -e works:
...
+ LIST=ebtables ebtables-save ebtables-restore
+ [ -h /sbin/ebtables ]
+ readlink /sbin/ebtables
+ [ /usr/sbin/ebtables = /usr/sbin/ebtables ]
+ rm /sbin/ebtables
+ [ -h /sbin/ebtables-save ]
+ readlink /sbin/ebtables-save
+ [ /usr/sbin/ebtables-save = /usr/sbin/ebtables-save ]
+ rm /sbin/ebtables-save
+ [ -h /sbin/ebtables-restore ]
+ readlink /sbin/ebtables-restore
+ [ /usr/sbin/ebtables-restore = /usr/sbin/ebtables-restore ]
+ rm /sbin/ebtables-restore
+ [ configure = configure ]
...

Processed: tagging 1031942

[Debian Bug Tracking System]

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

> tags 1031942 + pending
Bug #1031942 [src:sphinxbase] sphinxbase: Please drop the ltrace build 
dependency on mipsel
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1000209: Not able to build the package: multiple patches fail to apply

[Gabriel Filion]

Hi,

I've just taken a look at this issue together with someone else during 
the Montreal BSP and we think that the init script is possibly the 
source of the problem:


the stop action fails if it is called when the service is not running, 
which is the case when you install the package on a new system.


the init script should rather exit cleanly if start-stop-daemon --stop 
reports that it failed because the daemon is not running, e.g. ignore 
exit code 1 from start-stop-daemon.



however, when we tried to apply a modification to the init script, we 
tried to build the package to verify that our solution works but we were 
unable to even build it. there are multiple patches in debian/patches/ 
that currently do not apply cleanly.


e.g.

$ dpkg-buildpackage
dpkg-buildpackage: info: source package timidity
dpkg-buildpackage: info: source version 2.14.0-9
dpkg-buildpackage: info: source distribution UNRELEASED
dpkg-buildpackage: info: source changed by Bastien Roucariès 


dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 
0001-don-t-url_unexpand_home_dir-when-opening-a-file.patch

dpkg-source: info: applying 0002-improve-error-message.patch
patching file timidity/timidity.c
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored
dpkg-source: info: the patch has fuzz which is not allowed, or is malformed
dpkg-source: info: if patch '0002-improve-error-message.patch' is 
correctly applied by quilt, use 'quilt refresh' to update it
dpkg-source: info: if the file is present in the unpacked source, make 
sure it is also present in the orig tarball
dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B 
.pc/0002-improve-error-message.patch/ --reject-file=- < 
timidity/debian/patches/0002-improve-error-message.patch subprocess 
returned exit status 1
dpkg-buildpackage: error: dpkg-source --before-build . subprocess 
returned exit status 2

Processed: sphinxbase: Please drop the ltrace build dependency on mipsel

[Debian Bug Tracking System]

Processing control commands:

> block 1023436 by -1
Bug #1023436 [ltrace] unusable on mipsel: unexpected breakpoint at 0x...
1023436 was not blocked by any bugs.
1023436 was not blocking any bugs.
Added blocking bug(s) of 1023436: 1031942

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

Bug#1031942: sphinxbase: Please drop the ltrace build dependency on mipsel

[Adrian Bunk]

Source: sphinxbase
Version: 0.8+5prealpha+1-15
Severity: serious
Control: block 1023436 by -1

I am planning to fix #1023436 by dropping the broken mipsel binary,
and sphinxbase is the only user.

sphinxbase uses ltrace only for debugging in case of test failure,
checking the logfile that is not shown with the current non-failing
tests the ltrace output on mipsel looks like #1023436.

Processed: tagging 1031832

[Debian Bug Tracking System]

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

> tags 1031832 + upstream fixed-upstream
Bug #1031832 [python3-vispy] python3-vispy: import fails: AttributeError: 
module 'numpy' has no attribute 'bool'
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

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

Bug#1031895: marked as done (zoph fails to purge when mariadb-client is not installed)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 17:59:25 +
with message-id 
and subject line Bug#1031895: fixed in zoph 1.0.1-3
has caused the Debian Bug report #1031895,
regarding zoph fails to purge when mariadb-client is not installed
to be marked as done.

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

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


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

https://piuparts.debian.org/sid/fail/zoph_1.0.1-2.log

...
  (Reading database ... 8056 files and directories currently installed.)
  Purging configuration files for zoph (1.0.1-2) ...
  /var/lib/dpkg/info/zoph.postrm: 61: mysqladmin: not found
  dpkg: error processing package zoph (--purge):
   installed zoph package post-removal script subprocess returned error exit 
status 127
  Errors were encountered while processing:
   zoph


Similar to #1031748, but for a different command.

   mysqladmin --defaults-file=/etc/mysql/debian.cnf -f drop zoph || true
should work
--- End Message ---
--- Begin Message ---
Source: zoph
Source-Version: 1.0.1-3
Done: John Lines 

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

Debian distribution maintenance software
pp.
John Lines  (supplier of updated zoph package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 25 Feb 2023 16:36:15 +
Source: zoph
Architecture: source
Version: 1.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: John Lines 
Changed-By: John Lines 
Closes: 1031895
Changes:
 zoph (1.0.1-3) unstable; urgency=medium
 .
   * Add | true to mysqladmin drop zoph in postrm to allow for
mysql having been removed before zoph (Closes: #1031895)
Checksums-Sha1:
 f87d00268626f4fa7819c1145da71d654655cbbb 1713 zoph_1.0.1-3.dsc
 c13f5336c5725f70e8188e921ba914fec438ec95 16020 zoph_1.0.1-3.debian.tar.xz
 f4961dfbd94a964e612b48ee8ac75b186fc0b812 6274 zoph_1.0.1-3_source.buildinfo
Checksums-Sha256:
 f97eba6e0ba067c6ece8755d7034be62d525b01e6c9c93e3390ff92f21ef9ea5 1713 
zoph_1.0.1-3.dsc
 7a113f87a8691ec86074ac1de367f2104f5d6f1368e2558cf13db3487e1ec299 16020 
zoph_1.0.1-3.debian.tar.xz
 d99b42eca18637fda1d67f03b023d60044ad38fa42f2568b247de9c364b0eebc 6274 
zoph_1.0.1-3_source.buildinfo
Files:
 d63a66f87606481c20603817f8d2e196 1713 web optional zoph_1.0.1-3.dsc
 1442bf8cdbc0c64f0671dd0de1dd7db0 16020 web optional zoph_1.0.1-3.debian.tar.xz
 a694c611d5bb1e8be1354f387dcd742b 6274 web optional 
zoph_1.0.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEqH8J6LTFSJCxem30HxJlOZZGhecFAmP6OVARHGpvaG5AcGFs
YWR5bi5vcmcACgkQHxJlOZZGhecTZw//ZVrZ6mWsAH/ozhO3F2DFTBPDLmpF+R/u
RlA+Ha3LT+A5lWzP7IdlMrdz0ozazoQmLIRSq11UjOMGTC+F4xd0hvQWvoqQOe3N
Aa+De3UJslHuEY3gCXnHBrxuRhcg91esm3u3jL2CfI5MsdbOVaDxkjymgo+6F0ck
tr+PVjAUCjij9vCtx4GfsxrWhNj82Vf/h2ySHHjo6JE3Hv8Hysn0qIZOO69ZsEBp
vydJr654nr028wMAtDydPzH5pTtqbF4IEOlfc4DtCZpRkzrd5h9nkX5NaJqEt/3F
lRbm/mlS5K8JT7UlMaB7GAZHGyF/o4YyX7Fs1S2/DpZ5WL8rKxu5TscqjdYOgMmJ
StiNapEjQYIESuK1peTbHSdv2XVlMAjANoX9Bc6IQviagtZq1IL7D4hxyRFTTKHi
mECbPE+eDcFhAlQJPRrPZw8TjowEzuA8kc4vzjTGHxSCpY3yITdfYNWuJ6qJeeY9
V1TG1c2G8BzqSimwyJdBUgO8yv/lFj/akAXm4EzRMzxHlCtun00rQNSfvi+EELTt
AraNYDyr52gdcHAcQFvr2HUTpEDE3iYL3gWZmcq2nKgY9sg1RjgY8AJGVR6+JxL1
r3u8Ii8OArjz/DS5NsQPh0g4WJepCXpq4Ubm2lBjlovTF9Nx9Dd5RQ7psJ7LL8r0
CCroZpy+Bkw=
=70Qf
-END PGP SIGNATURE End Message ---

Bug#1031436: marked as done (ubuntu-dev-tools: FTBFS because of ./run-linters during build)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 17:55:00 +
with message-id 
and subject line Bug#1031436: fixed in ubuntu-dev-tools 0.193
has caused the Debian Bug report #1031436,
regarding ubuntu-dev-tools: FTBFS because of ./run-linters during build
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.)


-- 
1031436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ubuntu-dev-tools
Version: 0.192
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>'
> ./run-linters
> Running black...
> --- build/scripts-3.11/grep-merges2023-02-17 01:30:48.860507 +
> +++ build/scripts-3.11/grep-merges2023-02-17 01:30:49.805230 +
> @@ -52,11 +52,10 @@
>  "universe",
>  "universe-manual",
>  "multiverse",
>  "multiverse-manual",
>  ):
> -
>  url = f"https://merges.ubuntu.com/{component}.json;
>  try:
>  headers, page = Http().request(url)
>  except HttpLib2Error as e:
>  Logger.exception(e)
> would reformat build/scripts-3.11/grep-merges
> --- /<>/ubuntutools/misc.py  2023-02-01 11:45:15 +
> +++ /<>/ubuntutools/misc.py  2023-02-17 01:30:49.837949 +
> @@ -242,11 +242,11 @@
>  filesize = path.stat().st_size
>  if size and size != filesize:
>  Logger.error("File %s incorrect size, got %s expected %s", path, 
> filesize, size)
>  return False
>  
> -for (alg, checksum) in checksums.items():
> +for alg, checksum in checksums.items():
>  hash_ = hashlib.new(alg)
>  with path.open("rb") as f:
>  while True:
>  block = f.read(hash_.block_size)
>  if len(block) == 0:
> would reformat /<>/ubuntutools/misc.py
> --- grep-merges   2023-02-01 11:45:15 +
> +++ grep-merges   2023-02-17 01:30:50.160956 +
> @@ -52,11 +52,10 @@
>  "universe",
>  "universe-manual",
>  "multiverse",
>  "multiverse-manual",
>  ):
> -
>  url = f"https://merges.ubuntu.com/{component}.json;
>  try:
>  headers, page = Http().request(url)
>  except HttpLib2Error as e:
>  Logger.exception(e)
> would reformat grep-merges
> --- build/scripts-3.11/ubuntu-upload-permission   2023-02-17 
> 01:30:48.864507 +
> +++ build/scripts-3.11/ubuntu-upload-permission   2023-02-17 
> 01:30:50.219040 +
> @@ -89,11 +89,10 @@
>  component = spph.getComponent()
>  if args.list_uploaders and (
>  pocket != "Release"
>  or series.status in ("Experimental", "Active Development", 
> "Pre-release Freeze")
>  ):
> -
>  component_uploader = 
> archive.getUploadersForComponent(component_name=component)[0]
>  Logger.info("All upload permissions for %s:", args.package)
>  Logger.info("")
>  Logger.info("Component (%s)", component)
>  Logger.info("%s", "=" * len(component))
> would reformat build/scripts-3.11/ubuntu-upload-permission
> --- ubuntu-upload-permission  2023-02-01 11:45:15 +
> +++ ubuntu-upload-permission  2023-02-17 01:30:50.476410 +
> @@ -89,11 +89,10 @@
>  component = spph.getComponent()
>  if args.list_uploaders and (
>  pocket != "Release"
>  or series.status in ("Experimental", "Active Development", 
> "Pre-release Freeze")
>  ):
> -
>  component_uploader = 
> archive.getUploadersForComponent(component_name=component)[0]
>  Logger.info("All upload permissions for %s:", args.package)
>  Logger.info("")
>  Logger.info("Component (%s)", component)
>  Logger.info("%s", "=" * len(component))
> would reformat ubuntu-upload-permission
> --- /<>/ubuntutools/lp/lpapicache.py 2023-02-01 11:45:15 
> +
> +++ /<>/ubuntutools/lp/lpapicache.py 2023-02-17 
> 01:30:50.905615 +
> @@ -410,11 +410,11 @@
>  def binaryFileProperties(self, filename_or_url):
>  if not self._binary_prop_dict:
>  urls = self.binaryFileUrls()
>  props = self.getBinaryProperties()
>  self._binary_prop_dict = dict(zip(urls, props))
> -for (key, value) in copy(self._binary_prop_dict).items():
> +for key, value in copy(self._binary_prop_dict).items():
>  

Bug#963433: marked as done (libcolor-calc-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 17:52:14 +
with message-id 
and subject line Bug#961147: fixed in libcolor-calc-perl 1.074-3
has caused the Debian Bug report #961147,
regarding libcolor-calc-perl: FTBFS: dh_auto_test: error: perl Build test 
--verbose 1 returned exit code 2
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.)


-- 
961147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcolor-calc-perl
Version: 1.074-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
> dh: warning: Compatibility levels before 10 are deprecated (level 8 in use)
>dh_update_autotools_config
>dh_auto_configure
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 8 in use)
>   perl -I. Build.PL --installdirs vendor
> Checking prerequisites...
>   requires:
> !  Graphics::ColorNames::HTML is not installed
> 
> Checking optional features...
> color_object_supportdisabled
>   requires:
> ! Color::Object is not installed
> 
> ERRORS/WARNINGS FOUND IN PREREQUISITES.  You may wish to install the versions
> of the modules indicated above before proceeding with this installation
> 
> Run 'Build installdeps' to install missing prerequisites.
> 
> Created MYMETA.yml and MYMETA.json
> Creating new 'Build' script for 'Color-Calc' version '1.074'
>dh_auto_build
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 8 in use)
>   perl Build
> Building Color-Calc
>dh_auto_test
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 8 
> in use)
>   perl Build test --verbose 1
> 
> #   Failed test 'use Color::Calc;'
> #   at t/00basic.t line 4.
> # Tried to use 'Color::Calc'.
> # Error:  Can't locate Graphics/ColorNames/HTML.pm in @INC (you may need 
> to install the Graphics::ColorNames::HTML module) (@INC contains: 
> /<>/blib/lib /<>/blib/arch . /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.30.3 /usr/local/share/perl/5.30.3 
> /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.30 
> /usr/share/perl/5.30 /usr/local/lib/site_perl .) at 
> /<>/blib/lib/Color/Calc.pm line 17.
> # BEGIN failed--compilation aborted at 
> /<>/blib/lib/Color/Calc.pm line 17.
> # Compilation failed in require at t/00basic.t line 4.
> # BEGIN failed--compilation aborted at t/00basic.t line 4.
> Can't locate object method "new" via package "Color::Calc" at t/00basic.t 
> line 6.
> # Looks like your test exited with 255 just after 2.
> t/00basic.t  
> 1..3
> not ok 1 - use Color::Calc;
> ok 2 - no warnings
> Dubious, test returned 255 (wstat 65280, 0xff00)
> Failed 2/3 subtests 
> t/10pod.t .. 
> 1..3
> ok 1 - POD test for blib/lib/Color/Calc.pm
> ok 2 - POD test for blib/lib/Color/Calc/ConfigData.pm
> ok 3 - POD test for blib/lib/Color/Calc/WWW.pm
> ok
> 
> #   Failed test 'Color::Calc is covered by POD'
> #   at t/11pod_cover.t line 9.
> # Color::Calc: requiring 'Color::Calc' failed
> 
> #   Failed test 'Color::Calc::WWW is covered by POD'
> #   at t/11pod_cover.t line 13.
> # Color::Calc::WWW: requiring 'Color::Calc::WWW' failed
> # Looks like you failed 2 tests of 2.
> t/11pod_cover.t  
> 1..2
> not ok 1 - Color::Calc is covered by POD
> not ok 2 - Color::Calc::WWW is covered by POD
> Dubious, test returned 2 (wstat 512, 0x200)
> Failed 2/2 subtests 
> Can't locate Graphics/ColorNames/HTML.pm in @INC (you may need to install the 
> Graphics::ColorNames::HTML module) (@INC contains: /<>/blib/lib 
> /<>/blib/arch . /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.30.3 /usr/local/share/perl/5.30.3 
> /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.30 
> /usr/share/perl/5.30 /usr/local/lib/site_perl .) at 
> /<>/blib/lib/Color/Calc.pm line 17.
> BEGIN failed--compilation aborted at /<>/blib/lib/Color/Calc.pm 
> line 17.
> Compilation failed in require at t/DEPRECATED_import_MODEval.t line 3.
> BEGIN failed--compilation aborted at t/DEPRECATED_import_MODEval.t line 3.
> # Looks like your test exited with 2 just after 1.
> t/DEPRECATED_import_MODEval.t .. 
> 1..53
> ok 1 - no warnings
> Dubious, test returned 2 

Bug#961147: marked as done (libcolor-calc-perl: broken by new libgraphics-colornames-perl)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 17:52:14 +
with message-id 
and subject line Bug#961147: fixed in libcolor-calc-perl 1.074-3
has caused the Debian Bug report #961147,
regarding libcolor-calc-perl: broken by new libgraphics-colornames-perl
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.)


-- 
961147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcolor-calc-perl
Version: 1.074-2
Severity: grave
Tags: bullseye sid
X-Debbugs-Cc: libgraphics-colornames-p...@packages.debian.org

Color::Calc uses Graphics::ColorNames::HTML, which was recently dropped
from the libgraphics-colornames-perl package in Debian.

Graphics::ColorNames::HTML is now available separately on CPAN, with a
deprecation notice pointing users to Graphics::ColorNames::WWW (packaged
in Debian as libgraphics-colornames-www-perl) instead.

So Color::Calc needs to adapt, or Graphics::ColorNames::HTML needs to be
packaged separately despite the deprecation.

Also, libgraphics-colornames-perl should add a Breaks entry for the
versions of libcolor-calc-perl it broke.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libcolor-calc-perl
Source-Version: 1.074-3
Done: Mason James 

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

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

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

Debian distribution maintenance software
pp.
Mason James  (supplier of updated libcolor-calc-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 25 Feb 2023 22:17:24 +1300
Source: libcolor-calc-perl
Architecture: source
Version: 1.074-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Mason James 
Closes: 961147
Changes:
 libcolor-calc-perl (1.074-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * Remove Jonathan Yu from Uploaders. Thanks for your work!
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ Laurent Baillet ]
   * fix lintian file-contains-trailing-whitespace warning
 .
   [ gregor herrmann ]
   * debian/watch: use uscan version 4.
 .
   [ Debian Janitor ]
   * Bump debhelper from deprecated 8 to 12.
   * Set debhelper-compat version in Build-Depends.
 .
   [ Damyan Ivanov ]
   * Deprecate Graphics::ColorNames::HTML, switch to ::WWW.
 .
   [ mason james ]
   * fix color_safe.t test (Closes: #961147)
   * add Rules-Requires-Root: no
   * bump to Standards-Version: 4.6.2
   * bump debhelper-compat to 13
   * add nocheck to B-D-I
   * add header to debian/patches/html-to-www.patch
   * update copyrights
Checksums-Sha1:
 612991c968015c6cfb06a148153d35934f9da224 2659 libcolor-calc-perl_1.074-3.dsc
 403cac26d0dd3d9978b3cdc861500f76f0fefb61 4952 
libcolor-calc-perl_1.074-3.debian.tar.xz
Checksums-Sha256:
 46917cd5e0e55ffa91471b69fe002108642dd91a3acbc78712ef5232c2e2d185 2659 
libcolor-calc-perl_1.074-3.dsc
 2066dbf18109fa68da4457f0f4c309b8ba733a9eaad22ade6daa099cbdaadd7a 4952 
libcolor-calc-perl_1.074-3.debian.tar.xz
Files:
 a76852f6e14e5ea4b8e9d8602ac58073 2659 perl optional 
libcolor-calc-perl_1.074-3.dsc
 bdf99ba455f81611b4e7058a912133ce 4952 perl optional 
libcolor-calc-perl_1.074-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmP6Q/tfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgY6Wg//bkda+qXKiKY/RtLwp/++C+rJWAxpOITkc9tURnC3wFNbvqx1zXS+wsMc
KheeoNz1xF3m/aUxiKRmsUqHuTFD5uB1jcYSYCBo13m0FXvEUdOLtmYW5anBU1LO
ogBonRig8n8/nlVkA6u7BBtAWrILdNL8Gw7pISjzzp5cRaR5l1iaFcV+ozksxNUz
wUatB1fqtDVzhaL4k4mdp6CEgIuNvTxPEvHmxro7IS89ZLk2RBnGP1ZJ4FJyyIKA
f4MSlzAvYlOcMTKvvDEFmdnUV9aHtvJYBk+dGXfRuup991ZVSXpyT6zw99H4dqMN
RSfAeETmc6TZLTLt1CPu9vHSqRLmHy8V9S5YdIhCSR+t5ANHUyTsBjddi3yW9Vk9

Bug#1031744: marked as done (httpdirfs: usage of ubsan might introduce vulnerabilities)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 17:51:09 +
with message-id 
and subject line Bug#1031744: fixed in httpdirfs-fuse 1.2.5-1
has caused the Debian Bug report #1031744,
regarding httpdirfs: usage of ubsan might introduce vulnerabilities
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.)


-- 
1031744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: httpdirfs
Version: 1.2.4-1
Severity: serious
Tags: security
X-Debbugs-Cc: Debian Security Team 

Package: httpdirfs
Version: 1.2.4-2
Depends: ..., libubsan1 (>= 8), ...


This is a bad idea not only due to slower execution,
but might even introduce vulnerabilities:
https://www.openwall.com/lists/oss-security/2016/02/17/9

While there are safe usages of ubsan, httpdirfs being the
only package in the archive that uses ubsan but not asan
is something that sounds wrong and underreviewed.
--- End Message ---
--- Begin Message ---
Source: httpdirfs-fuse
Source-Version: 1.2.5-1
Done: Jérôme Charaoui 

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

Debian distribution maintenance software
pp.
Jérôme Charaoui  (supplier of updated httpdirfs-fuse package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 25 Feb 2023 12:29:09 -0500
Source: httpdirfs-fuse
Architecture: source
Version: 1.2.5-1
Distribution: unstable
Urgency: medium
Maintainer: Jérôme Charaoui 
Changed-By: Jérôme Charaoui 
Closes: 1031744
Changes:
 httpdirfs-fuse (1.2.5-1) unstable; urgency=medium
 .
   * New upstream version 1.2.5 (Closes: #1031744)
   * d/control: bump debhelper-compat to 13
   * d/rules: ubsan is not used anymore
   * d/watch: fix filenamemangle
Checksums-Sha1:
 f50cc469848b3d0ba3f62a9f89a864ce94d3897a 1498 httpdirfs-fuse_1.2.5-1.dsc
 ee080d40573c2826a42cedb49359929364d58cc8 76724 httpdirfs-fuse_1.2.5.orig.tar.gz
 bb83029e865619c18b46e7fd448dded27d904ae6 3164 
httpdirfs-fuse_1.2.5-1.debian.tar.xz
 a6bc4a993d3bdc5eb6705ce353e995fe7a76cb10 6631 
httpdirfs-fuse_1.2.5-1_amd64.buildinfo
Checksums-Sha256:
 7b62d902cd2ded82ab5fccde7037ed9b8b75460fb56f35b7dec0d8ab238dd67a 1498 
httpdirfs-fuse_1.2.5-1.dsc
 d0a85600c3813064ba3cad9491b66fcf458151a49d3926818f5458ab6f615038 76724 
httpdirfs-fuse_1.2.5.orig.tar.gz
 3a133df3665835e9b693b7a84e47178a89a2311822c282e4884e52a818640ffe 3164 
httpdirfs-fuse_1.2.5-1.debian.tar.xz
 8ced794a367f9ca4a6a934e1639bef7cc7069073195e3c92892e2eea8d7dd5eb 6631 
httpdirfs-fuse_1.2.5-1_amd64.buildinfo
Files:
 1384d81aad29d81f2c845d5505fc649a 1498 utils optional httpdirfs-fuse_1.2.5-1.dsc
 77910de057b196ed7b3714f7a0698203 76724 utils optional 
httpdirfs-fuse_1.2.5.orig.tar.gz
 1c293662fb568f6020195eac9e02a2a4 3164 utils optional 
httpdirfs-fuse_1.2.5-1.debian.tar.xz
 6ff3deebdf13565511504846ff6557b7 6631 utils optional 
httpdirfs-fuse_1.2.5-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQTAq04Rv2xblqv/eu5pxS9ljpiFQgUCY/pGgQAKCRBpxS9ljpiF
Qmr+AQCHMo2obL61fedl/kc7/3WYwuw3MchnU0jmFRhWM3kkpgD9H+pxB96em72q
I5sN5X7EBF2IsHQ4Cxdkws7u2DqUtg0=
=ahf7
-END PGP SIGNATURE End Message ---

Bug#1019273: actual patch for debian/copyright file

[Znoteer]

user debian-rele...@lists.debian.org 

usertags -1 + bsp-2023-02-ca-montreal
Thank you

The original file offered was not a patch. Here is a patch. You can now see the 
EXPAT and BSD licences in the patch.

-- 
Znoteer
znot...@mailbox.org
diff --git a/COPYING b/COPYING
index 2f9ab10e8..d518ef5d4 100644
--- a/COPYING
+++ b/COPYING
@@ -1,22 +1,174 @@
-Apt is copyright 1997, 1998, 1999 Jason Gunthorpe and others.
-Apt is currently developed by APT Development Team .
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: apt
+Upstream-Contact: APT Development Team 
+Source: https://salsa.debian.org/apt-team/apt
 
-License: GPLv2+
+Files: *
+Copyright: 1997-1999 Jason Gunthorpe and others
+License: GPL-2+
 
-This program is free software; you can redistribute it and/or modify
-it under the terms of the GNU General Public License as published by
-the Free Software Foundation; either version 2 of the License, or
-(at your option) any later version.
+Files: apt-pkg/cachefilter-patterns.*
+   apt-private/private-json-hooks.*
+   test/libapt/pattern_test.cc
+Copyright: 2018, 2019 Canonical Ltd
+License: GPL-2+
 
-This program is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-GNU General Public License for more details.
+Files: po/lt.po
+Copyright: 2006 Canonical Ltd, and Rosetta Contributors 2006
+License: GPL-2+
 
-You should have received a copy of the GNU General Public License
-along with this program; if not, write to the Free Software
-Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.
+Files: apt-pkg/contrib/weakptr.h
+   apt-pkg/contrib/string_view.h
+   CMakeLists.txt
+Copyright: 2009, 2010, 2015, 2016 Julian Andres Klode 
+License: GPL-2+
 
-See /usr/share/common-licenses/GPL-2, or
- for the terms of the latest version
-of the GNU General Public License.
+Files: debian/apt.postrm
+Copyright: 1998, Ben Gertzfield 
+License: GPL-2+
+
+Files: doc/po/pt.po
+   po/bg.po
+   po/it.po
+   po/sv.po
+   po/th.po
+Copyright: 2002-2019 Free Software Foundation, Inc.
+License: GPL-2+
+
+Files: doc/po/es.po
+   po/tl.po
+Copyright: 2003, 2004, 2005, 2009, 2010, 2012 Software in the Public Interest
+License: GPL-2+
+
+Files: po/nb.po
+Copyright: 2002-2003 Lars Bahner 
+   2003-2004 Axel Bojer 
+   2004 Klaus Ade Johnstad 
+   2004 Bjorn Steensrud 
+   2003, 2005-2010 Hans Fredrik Nordhaug 
+   2016, 2018 Petter Reinholdtsen 
+License: GPL-2
+
+Files: po/tr.po
+Copyright: 2009 Rosetta Contributors and Canonical Ltd 2009
+   2013 Debian L10n Turkish 2013
+   2013-2018 Mert Dirik 
+License: GPL-2+
+
+Files: doc/po/pl.po
+Copyright: 2004 Krzysztof Fiertek 
+   2000-2004, 2010, 2012  Robert Luberda 
+License: GPL-2+
+
+Files: doc/po/it.po
+Copyright: 2000-2017 Debian Italian l10n team 
+License: GPL-2+
+
+Files: doc/po/ja.po
+Copyright: 2003-2017 Debian Japanese List 
+License: GPL-2+
+
+Files: doc/po/fr.po
+Copyright: 2000-2018 Debian French l10n team 
+License: GPL-2+
+
+Files: doc/design.dbk
+Copyright: 1997 Manoj Srivastava
+License: GPL-2+
+
+Files: doc/dpkg-tech.dbk
+Copyright: 1997 Tom Lees
+License: GPL-2+
+
+Files: methods/rred.cc
+Copyright: 2014 Anthony Towns
+License: GPL-2+
+
+Files: methods/rsh.cc
+Copyright: 2000 Ben Collins 
+License: GPL-2
+
+Files: CMake/FindBerkeley.cmake
+Copyright: 2006, Alexander Dymo, 
+   2016, Julian Andres Klode 
+License: BSD-3-clause
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ .
+ 1. Redistributions of source code must retain the copyright
+notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the copyright
+notice, this list of conditions and the following disclaimer in the
+documentation and/or other materials provided with the distribution.
+ 3. The name of the author may not be used to endorse or promote products
+derived from this software without specific prior written permission.
+ .
+ THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+ IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+ OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+ IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+ INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+ NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+ DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE 

Bug#1031442: marked as done (gnustep-base: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 messages=yes returned exit code 2)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 19:01:09 +0200
with message-id 
and subject line Re: Bug#1031442: gnustep-base: FTBFS: dh_auto_test: error: 
make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 messages=yes returned 
exit code 2
has caused the Debian Bug report #1031442,
regarding gnustep-base: FTBFS: dh_auto_test: error: make -j8 check 
"TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 messages=yes returned exit code 2
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.)


-- 
1031442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnustep-base
Version: 1.28.1+really1.28.0-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230216 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 '/<>/Tests'
> (\
> GNUSTEP_LOCAL_ADDITIONAL_MAKEFILES="/<>/base.make";\
> ADDITIONAL_INCLUDE_DIRS="-I/<>/Headers 
> -I/<>/Source/.";\
> ADDITIONAL_LIB_DIRS="-L/<>/Source/./obj";\
> ADDITIONAL_LDFLAGS="-Wl,-rpath,/<>/Source/./obj";\
> LD_LIBRARY_PATH="/<>/Source/./obj:";\
> PATH="/<>/Tools/./obj:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games";\
> export GNUSTEP_LOCAL_ADDITIONAL_MAKEFILES;\
> export ADDITIONAL_INCLUDE_DIRS;\
> export ADDITIONAL_LDFLAGS;\
> export ADDITIONAL_LIB_DIRS;\
> export LD_LIBRARY_PATH;\
> export PATH;\
> if [ "no" = "yes" ]; then \
>   gnustep-tests --debug 'base/';\
> else \
>   gnustep-tests 'base/';\
> fi; \
> )
> --- Running tests in base/Functions ---
> --- Running tests in base/GSMime ---
> --- Running tests in base/GSTLS ---
> --- Running tests in base/GSXML ---
> --- Running tests in base/GarbageCollection ---
> --- Running tests in base/KVC ---
> --- Running tests in base/NSAffineTransform ---
> --- Running tests in base/NSArchiver ---
> --- Running tests in base/NSArray ---
> 
> base/NSArray/basic.m:
> Skipped set:   basic.m 46 ... No collection subscripting support in the 
> compiler.
> 
> base/NSArray/blocks.m:
> Skipped set:   blocks.m 76 ... No Blocks support in the compiler.
> --- Running tests in base/NSAttributedString ---
> --- Running tests in base/NSAutoreleasePool ---
> --- Running tests in base/NSBundle ---
> 
> base/NSBundle/general.m:
> Skipped set: general.m 25 ... it looks like GNUstep-base is not yet 
> installed
> 
> base/NSBundle/resources.m:
> Skipped set:   resources.m 48 ... it looks like GNUstep-base is not yet 
> installed
> --- Running tests in base/NSCache ---
> --- Running tests in base/NSCalendar ---
> --- Running tests in base/NSCalendarDate ---
> 
> base/NSCalendarDate/test00.m:
> Failed file: test00.m aborted without running all tests!
> --- Running tests in base/NSCharacterSet ---
> --- Running tests in base/NSConnection ---
> --- Running tests in base/NSCountedSet ---
> --- Running tests in base/NSData ---
> 
> base/NSData/general.m:
> Skipped set:   general.m 128 ... No Blocks support in the compiler.
> --- Running tests in base/NSDate ---
> --- Running tests in base/NSDateFormatter ---
> --- Running tests in base/NSDictionary ---
> 
> base/NSDictionary/basic.m:
> Skipped set:   basic.m 41 ... No dictionary subscripting support in the 
> compiler.
> 
> base/NSDictionary/blocks.m:
> Skipped set:   blocks.m 49 ... No Blocks support in the compiler.
> 
> base/NSDictionary/sort.m:
> Skipped set:   sort.m 54 ... No Blocks support in the compiler.
> --- Running tests in base/NSDistributedLock ---
> --- Running tests in base/NSException ---
> --- Running tests in base/NSFileHandle ---
> --- Running tests in base/NSFileManager ---
> --- Running tests in base/NSHTTPCookie ---
> --- Running tests in base/NSHashTable ---
> 
> base/NSHashTable/weakObjects.m:
> Skipped set:   weakObjects.m 15 ... ARC support unavailable
> --- Running tests in base/NSHost ---
> --- Running tests in base/NSIndexPath ---
> --- Running tests in base/NSInvocation ---
> --- Running tests in base/NSInvocationOperation ---
> --- Running tests in base/NSJSONSerialization ---
> --- Running tests in base/NSKeyedArchiver ---
> --- Running tests in base/NSLocale ---
> --- Running tests in base/NSLock ---
> --- Running tests in base/NSMapTable ---
> 
> base/NSMapTable/weakObjects.m:
> Skipped set:   weakObjects.m 15 ... ARC support unavailable
> --- Running tests in base/NSMethodSignature ---
> --- Running tests in base/NSMutableArray ---
> --- Running tests in 

Bug#1031438: marked as done (qca2: FTBFS: dh_auto_test: error: cd build && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 16:34:07 +
with message-id 
and subject line Bug#1031438: fixed in qca2 2.3.5-2
has caused the Debian Bug report #1031438,
regarding qca2: FTBFS: dh_auto_test: error: cd build && make -j8 test 
ARGS\+=--verbose ARGS\+=-j8 returned exit code 2
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.)


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/build'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --verbose -j8
> UpdateCTestConfiguration  from :/<>/build/DartConfiguration.tcl
> UpdateCTestConfiguration  from :/<>/build/DartConfiguration.tcl
> Test project /<>/build
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 1
>   Start  1: Base64
> 
> 1: Test command: /<>/build/bin/base64unittest
> 1: Working Directory: /<>/build/bin
> 1: Test timeout computed to be: 1000
> test 2
>   Start  2: BigInteger
> 
> 2: Test command: /<>/build/bin/bigintunittest
> 2: Working Directory: /<>/build/bin
> 2: Test timeout computed to be: 1000
> test 3
>   Start  3: Certificate
> 
> 3: Test command: /<>/build/bin/certunittest
> 3: Working Directory: /<>/build/bin
> 3: Test timeout computed to be: 1000
> test 4
>   Start  4: SymmetricCipher
> 
> 4: Test command: /<>/build/bin/cipherunittest
> 4: Working Directory: /<>/build/bin
> 4: Test timeout computed to be: 1000
> test 5
>   Start  5: ClientSidePlugin
> 
> 5: Test command: /<>/build/bin/clientplugin
> 5: Working Directory: /<>/build/bin
> 5: Test timeout computed to be: 1000
> test 6
>   Start  6: DigitalSignatureAlgorithm
> 
> 6: Test command: /<>/build/bin/dsaunittest
> 6: Working Directory: /<>/build/bin
> 6: Test timeout computed to be: 1000
> test 7
>   Start  7: FileWatch
> 
> 7: Test command: /<>/build/bin/filewatchunittest
> 7: Working Directory: /<>/build/bin
> 7: Test timeout computed to be: 1000
> test 8
>   Start  8: Hashing
> 
> 8: Test command: /<>/build/bin/hashunittest
> 8: Working Directory: /<>/build/bin
> 8: Test timeout computed to be: 1000
> 1: * Start testing of Base64UnitTest *
> 1: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 1: PASS   : Base64UnitTest::initTestCase()
> 1: PASS   : Base64UnitTest::test1(31)
> 1: PASS   : Base64UnitTest::test1(235c91)
> 1: PASS   : Base64UnitTest::test1(414)
> 1: PASS   : Base64UnitTest::test1(241)
> 1: PASS   : Base64UnitTest::test1(313)
> 1: PASS   : Base64UnitTest::test1(60e)
> 1: PASS   : Base64UnitTest::test1(3134)
> 1: PASS   : Base64UnitTest::test2(www.python.org)
> 1: PASS   : Base64UnitTest::test2(a)
> 1: PASS   : Base64UnitTest::test2(ab)
> 1: PASS   : Base64UnitTest::test2(abc)
> 1: PASS   : Base64UnitTest::test2(empty)
> 1: PASS   : Base64UnitTest::test2(a-Z)
> 1: PASS   : Base64UnitTest::test2(31)
> 1: PASS   : Base64UnitTest::test2(QCA_2.0)
> 1: PASS   : Base64UnitTest::test2(j-0)
> 1: PASS   : Base64UnitTest::cleanupTestCase()
> 1: Totals: 18 passed, 0 failed, 0 skipped, 0 blacklisted, 1ms
> 1: * Finished testing of Base64UnitTest *
> 2: * Start testing of BigIntUnitTest *
> 2: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 2: PASS   : BigIntUnitTest::initTestCase()
> 3: * Start testing of CertUnitTest *
> 3: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 3: PASS   : CertUnitTest::initTestCase()
> 4: * Start testing of CipherUnitTest *
> 4: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 12.2.0), debian unknown
> 4: PASS   : CipherUnitTest::initTestCase()
> 5: * Start testing of ClientPlugin *
> 5: Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
> shared (dynamic) 

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

[Scott Kitterman]

True.

I'm not a C programmer, so I may be unduly concerned about the maintenance 
load.  I'll defer to your judgement.

I do wonder if we should make a stab at switching the rust bits to using Debian 
packages instead of the embedded copies.  If we could manage it, then any 
security issues in the rust libraries can be fixed in clamav with a binNMU, no 
upload needed.

Scott K

On February 25, 2023 4:11:01 PM UTC, Sebastian Andrzej Siewior 
 wrote:
>On 25 February 2023 14:57:28 UTC, Scott Kitterman  wrote:
>>Generally favorably, but I'd rather wait for upstream to agree on it, 
>>otherwise it may be a patch we have to maintain forever. 
>
>Now we maintain the tfm bits.
>
>>What's their reaction to the change?
>
>No reply so far. The first few patches from early January got the response "it 
>was a chaotic week, we get to it soon" and the tfm patch got no response since 
>I posted it last week.
>Maybe you need to walk around their office and throw a stone with pull request 
>number written on it :-)
>
>>
>>It's also late in the release cycle to do it (not definitely a problem, but 
>>calls for caution).
>>
>>Scott K
>

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

[Sebastian Andrzej Siewior]

On 25 February 2023 14:57:28 UTC, Scott Kitterman  wrote:
>Generally favorably, but I'd rather wait for upstream to agree on it, 
>otherwise it may be a patch we have to maintain forever. 

Now we maintain the tfm bits.

>What's their reaction to the change?

No reply so far. The first few patches from early January got the response "it 
was a chaotic week, we get to it soon" and the tfm patch got no response since 
I posted it last week.
Maybe you need to walk around their office and throw a stone with pull request 
number written on it :-)

>
>It's also late in the release cycle to do it (not definitely a problem, but 
>calls for caution).
>
>Scott K

-- 
Sebastian

Bug#1031649: wine: /usr/bin/wine64 still required

[Jens Reyer]

On 20.02.23 01:17, Austin English wrote:
On Sun, Feb 19, 2023, 17:33 Jens Reyer > wrote:
Yes, it's arguably a bug in winetricks. Film what I gather upstream, 
it's also not yet fully supported.


I would advise reverting for now. At least until upstream fully supports it.


ftr: I just uploaded a new winetricks 20230212-1 to unstable which 
should migrate to bookworm before the hard freeze. It workarounds a 
missing /usr/bin/wine64. The fix is quite late in Winetricks logic to 
figure out wine64, so it should work just fine with both setups.  Tested 
against wine 8.0~repack-2, 8.0~repack-4 and winehq-staging 8.2~bookworm-1.

Bug#1031895: zoph fails to purge when mariadb-client is not installed

[John Lines]

I have made this change, although on my system piuparts (1.1.7) does
not give me this result - I still get a piuparts failure due to

9m55.8s ERROR: FAIL: Package purging left files on system:
  /etc/dbconfig-common/  owned by: dbconfig-common
  /etc/mysql/owned by: mariadb-server, mysql-common, mariadb-
common, mariadb-client
  /etc/mysql/debian.cnf  not owned
  /var/lib/mysql/not owned
  /var/lib/mysql/aria_log.0001   not owned
  /var/lib/mysql/aria_log_controlnot owned
  /var/lib/mysql/debian-10.11.flag   not owned
...

which is different from the piuparts server result, and from manual
install and purge on a test virtual bookworm VM


> 
> Similar to #1031748, but for a different command.
> 
>    mysqladmin --defaults-file=/etc/mysql/debian.cnf -f drop zoph ||
> true
> should work

Bug#1031931: youtube-dl: All binaries missing in youtube-dl 2021.12.17-2

[Andreas Tille]

Control: severity -1 important

Am Sat, Feb 25, 2023 at 03:39:19PM +0100 schrieb Michael Stoeger:
> Package: youtube-dl
> Version: 2021.12.17-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> it looks like the whole binary part is missing in the current version of
> youtube-dl in Debian testing and unstable. Of course, the program is not 
> usable
> with /usr/bin/youtube-dl missing.
> 
> The package youtube-dl_2021.12.17-2_all.deb is quite small (75KB) compared to
> the prior version youtube-dl_2021.12.17-1~bpo11+1_all.deb (1.1MB).
> I checked the deb package and the data.tar.xz contains only the directory
> ./usr/share/doc/youtube-dl/, nothing else:

I admit I did not do the change and I'm not involved into the discussion
about this but the change was perfectly intended as per


youtube-dl (2021.12.17-2) unstable; urgency=low

  [ Andres Salomon ]
  ...
  * Depend upon the yt-dlp package, and stop actually building youtube-dl.
Youtube-dl is in maintenance mode upstream, and active development is
happening with the yt-dlp fork (closes: #994151).
  * Document the above in a NEWS entry.
  ...

 -- Andres Salomon   Tue, 03 Jan 2023 17:21:53 -0500


Thus at least lowering severity of this bug report to important.

Kind regard
   Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#1031931: youtube-dl: All binaries missing in youtube-dl 2021.12.17-2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1031931 [youtube-dl] youtube-dl: All binaries missing in youtube-dl 
2021.12.17-2
Severity set to 'important' from 'grave'

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

Processed: flashrom: diff for NMU version 1.3.0-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1031448 + patch
Bug #1031448 [libflashrom-dev] libfrashrom-dev missing dependency on pkg-config 
required libraries
Added tag(s) patch.
> tags 1031448 + pending
Bug #1031448 [libflashrom-dev] libfrashrom-dev missing dependency on pkg-config 
required libraries
Added tag(s) pending.

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

Bug#1031448: flashrom: diff for NMU version 1.3.0-2.1

[Adrian Bunk]

Control: tags 1031448 + patch
Control: tags 1031448 + pending

Dear maintainer,

I've prepared an NMU for flashrom (versioned as 1.3.0-2.1) and uploaded 
it to DELAYED/5. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru flashrom-1.3.0/debian/changelog flashrom-1.3.0/debian/changelog
--- flashrom-1.3.0/debian/changelog	2023-02-06 12:32:07.0 +0200
+++ flashrom-1.3.0/debian/changelog	2023-02-25 17:13:29.0 +0200
@@ -1,3 +1,13 @@
+flashrom (1.3.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove no longer used debian/flashrom.pc
+(pkg-config file is now generated during the build).
+  * libflashrom-dev: Remove the unnecessary Requires.private
+from flashrom.pc. (Closes: #1031448)
+
+ -- Adrian Bunk   Sat, 25 Feb 2023 17:13:29 +0200
+
 flashrom (1.3.0-2) unstable; urgency=medium
 
   * d/rules:
diff -Nru flashrom-1.3.0/debian/flashrom.pc flashrom-1.3.0/debian/flashrom.pc
--- flashrom-1.3.0/debian/flashrom.pc	2020-03-05 02:45:52.0 +0200
+++ flashrom-1.3.0/debian/flashrom.pc	1970-01-01 02:00:00.0 +0200
@@ -1,9 +0,0 @@
-prefix=/usr
-libdir=${prefix}/lib/x86_64-linux-gnu
-includedir=${prefix}/include/flashrom
-
-Name: flashrom
-Description: library to interact with flashrom
-Version: 1.2
-Libs: -L${libdir} -lflashrom
-Cflags: -I${includedir}
diff -Nru flashrom-1.3.0/debian/rules flashrom-1.3.0/debian/rules
--- flashrom-1.3.0/debian/rules	2023-02-06 12:32:07.0 +0200
+++ flashrom-1.3.0/debian/rules	2023-02-25 17:13:29.0 +0200
@@ -44,3 +44,4 @@
 
 override_dh_auto_install:
 	dh_auto_install -Smeson
+	perl -ni -e '/Requires.private.*/ or print' debian/tmp/usr/lib/*/pkgconfig/flashrom.pc

Bug#1031935: firmware-ath9k-htc: missing hardware identifiers in dep-11 metadata

[Cyril Brulebois]

Package: firmware-ath9k-htc
Version: 1.4.0-108-gd856466+dfsg1-1.2
Severity: serious
Justification: regression in hardware support
X-Debbugs-Cc: b...@debian.org, debian-ker...@lists.debian.org, 
debian-b...@lists.debian.org

Hi,

Here's another thing that was totally overlooked while forcing the
switch from firmware-atheros to firmware-ath9k-htc in an uncoordinated
manner: the dep-11 metadata are (1) hardcoded in the firmware-ath9k-htc
package, and (2) out-of-date.

This means we're actively losing support for hardware by switching from
the non-free package to the one in main!

Right now, the following entries are missing:
 - AirTies AR9271
 - Altai WA1011N-GU

Those date back to v4.12-rc1 (2017) and v4.16-rc1 (2018) respectively:
 - 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=16ff1fb0e32f76a5d285a6f23b82d21aa52813c6
 - 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4e12d654ba068df06c5e4c8322d7dcced41e48ee


Surely checking feature parity should have been the very first step?
 
 
Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant

Bug#1031706: marked as done (optuna: test_create_new_trial randomly fails on s390x)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 15:49:16 +
with message-id 
and subject line Bug#1031706: fixed in optuna 3.1.0-4
has caused the Debian Bug report #1031706,
regarding optuna: test_create_new_trial randomly fails on s390x
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.)


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

Package: python3-optuna
Severity: serious
Control: affects -1 python3-pandas

test_create_new_trial (both parts) sometimes fails on s390x, failing the 
autopkgtest.


It might make sense to remove this package on s390x, if it isn't 
reasonable to actually fix this.
--- End Message ---
--- Begin Message ---
Source: optuna
Source-Version: 3.1.0-4
Done: Gard Spreemann 

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

Debian distribution maintenance software
pp.
Gard Spreemann  (supplier of updated optuna package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 25 Feb 2023 16:25:29 +0100
Source: optuna
Architecture: source
Version: 3.1.0-4
Distribution: unstable
Urgency: medium
Maintainer: Gard Spreemann 
Changed-By: Gard Spreemann 
Closes: 1031706
Changes:
 optuna (3.1.0-4) unstable; urgency=medium
 .
   * Add hacky patch to work around flaky tests due to timing issues. The
 patch does not fix upstream's incorrect assumptions about wall time,
 but does significantly lower the probability of autopkgtests
 incorrectly failing. (Closes: #1031706)
Checksums-Sha1:
 1c7ec9e06f0206135c5630741b2b3567736cc6de 2174 optuna_3.1.0-4.dsc
 1d26410772c7156d8f6292302d5606dbdc57a0d2 4624 optuna_3.1.0-4.debian.tar.xz
 e28e060ed30393fc9bcc8d1f59bd43e4d4544772 7912 optuna_3.1.0-4_source.buildinfo
Checksums-Sha256:
 51707ac67b139f414f406ea25f250c92d6a2db26e2b76f4560ac5f6b3b338e63 2174 
optuna_3.1.0-4.dsc
 7125d188a7f300b0bbb1d2e6865a96b02b5b46b812beced6367208af0031cef9 4624 
optuna_3.1.0-4.debian.tar.xz
 958e6ffa757eb0f44a11a878aa5bbb38dc27efd4e4fbf8e55ea5e55d924a491e 7912 
optuna_3.1.0-4_source.buildinfo
Files:
 64620f2fa2ccd25b50b11b169539e2d9 2174 python optional optuna_3.1.0-4.dsc
 01e89671223d975a9b68050d8829ca7f 4624 python optional 
optuna_3.1.0-4.debian.tar.xz
 54a37204073c4998532926459a1bc148 7912 python optional 
optuna_3.1.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEz8XvhRCFHnNVtV6AnRFYKv1UjPoFAmP6KYgSHGdzcHJAbm9u
ZW1wdHkub3JnAAoJEJ0RWCr9VIz6aBUQAI7RXld695PB8+YtvL9sUdTGFYCfTSs8
jAiyW9TcEJqTot1TZJM0X78abi8lTsCJGj3G2DkH8vK2/0evpt0z7s3BQ7NHyvw2
DJBDvaMGhauaZ7G8xD7eancJZvcjuyk4H9Hhn62FRrjn9GzQXCuvf4NHcaxQUbpc
omRk3I+3DERjPTLUjTnG0mNqA1BqyBXd58aoIgU1aQoH38mWUs04YfL+l8y91wjU
FE7UXG/KKSlJTgeLf+2iC18QoXYZYrKSHQBUyEMgl0mutgNGO0OMc7mtvwVEOI57
mkhBHaTLiAXMl47KnE5HUum/LGUHuEMbh8lz+Y8MqC2fKGEfoQBaT/ROLzA/NhIP
gbO6zXQjL6tmZmd3pYz8bH2yn13L6DpopQNVem3i6zlGd+hZu8EmeMCbmyh0FvBj
cTIae6cXGtPspc7paf5ZuQqmYYTHOOxmB6TDXJ10oaIVcLm++TGZO0bsaR4sFk31
2t13BieKTWjAxIPbVwleIFe97SJn3SlRBCqJhBlQgkjuez3zbNk7aaWuPX9lhQgg
UY9zvCU1OZlVh/w04avZSUqVfNqJ+rEAqhBY41b9fhQos7lgxcZpLngh58dqoRqS
DRNy+Xaay1eJstUPXXQwX3knIV6/nwsEmo6IAE11fxfVWBa3vuqKJAwkioCPXU34
IfBaNNIumpvf
=d57j
-END PGP SIGNATURE End Message ---

Bug#1031231: tries to overwrite /etc/cron.yearly/.placeholder from systemd-cron

[Alexandre Detiste]

Hi,

I was not explicit enough.

It's the "cron-daemon-common" binary package that needs this
Conflicts: / Breaks,
not the "cron" binary package

Le mar. 14 févr. 2023 à 22:41, Alexandre Detiste
 a écrit :
>
> To be explicit: on your side you'd need yet another upload with a
>
>Conflicts: systemd-cron (<<1.15.19-5~)
>
> (and/or a Breaks?)

Processed: reopening 1031231

[Debian Bug Tracking System]

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

> reopen 1031231
Bug #1031231 {Done: Georges Khaznadar } 
[cron-daemon-common] tries to overwrite /etc/cron.yearly/.placeholder from 
systemd-cron
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions cron/3.0pl1-161.
> thanks
Stopping processing here.

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

Bug#1026501: marked as done (request-tracker4: FTBFS: make[1]: *** [Makefile:381: test-parallel] Error 1)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 15:20:59 +
with message-id 
and subject line Bug#1026501: fixed in request-tracker4 4.4.6+dfsg-1.1
has caused the Debian Bug report #1026501,
regarding request-tracker4: FTBFS: make[1]: *** [Makefile:381: test-parallel] 
Error 1
to be marked as done.

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

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


-- 
1026501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: request-tracker4
Version: 4.4.6+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 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 '/<>'
> RT_TEST_PARALLEL=1 /usr/bin/perl "-MApp::Prove" -e 'my $p = 
> App::Prove->new(); $p->process_args("-wlrj3","--state=slow,save", "t"); exit( 
> $p->run() ? 0 : 1 )'
> No saved state, selection will be empty
> t/00-compile.t . ok
> t/00-mason-syntax.t  ok
> t/api/action-createtickets.t ... ok
> t/api/attachment_filename.t  ok
> t/api/attachment.t . ok
> t/api/attribute-tests.t  ok
> t/api/attribute.t .. ok
> t/api/canonical_charset.t .. ok
> t/api/bookmarks.t .. ok
> t/api/cf_render_type.t . ok
> t/api/cf_rights.t .. ok
> t/api/cfsearch.t ... ok
> t/api/condition-ownerchange.t .. ok
> t/api/condition-reject.t ... ok
> t/api/config.t . ok
> t/api/currentuser.t  ok
> t/api/cron.t ... ok
> 
> #   Failed test 'LocalizedDateTime format with defaults'
> #   at t/api/date.t line 100.
> #  got: 'Thu, Jan 1, 1970 12:00:00 AM'
> # expected: 'Thu, Jan 1, 1970 12:00:00 AM'
> 
> #   Failed test 'LocalizedDateTime format without date part'
> #   at t/api/date.t line 126.
> #  got: '12:00:00 AM'
> # expected: '12:00:00 AM'
> 
> #   Failed test 'LocalizedDateTime format without abbreviation of day'
> #   at t/api/date.t line 147.
> #  got: 'Thursday, Jan 1, 1970 12:00:00 AM'
> # expected: 'Thursday, Jan 1, 1970 12:00:00 AM'
> 
> #   Failed test 'LocalizedDateTime format without abbreviation of month'
> #   at t/api/date.t line 150.
> #  got: 'Thu, January 1, 1970 12:00:00 AM'
> # expected: 'Thu, January 1, 1970 12:00:00 AM'
> 
> #   Failed test 'LocalizedDateTime format with non default DateFormat'
> #   at t/api/date.t line 153.
> #  got: '1/1/70 12:00:00 AM'
> # expected: '1/1/70 12:00:00 AM'
> 
> #   Failed test 'LocalizedDateTime format with non default TimeFormat'
> #   at t/api/date.t line 156.
> #  got: 'Thu, Jan 1, 1970 12:00 AM'
> # expected: 'Thu, Jan 1, 1970 12:00 AM'
> 
> #   Failed test 'LocalizedDateTime'
> #   at t/api/date.t line 215.
> #  got: 'Sat, Jan 1, 2005 6:10:00 PM'
> # expected: 'Sat, Jan 1, 2005 6:10:00 PM'
> 
> #   Failed test 'LocalizedDateTime'
> #   at t/api/date.t line 223.
> #  got: 'Fri, Jul 1, 2005 7:10:00 PM'
> # expected: 'Fri, Jul 1, 2005 7:10:00 PM'
> 
> #   Failed test 'LocalizedDateTime'
> #   at t/api/date.t line 233.
> #  got: 'Sat, Jan 1, 2005 10:10:00 AM'
> # expected: 'Sat, Jan 1, 2005 10:10:00 AM'
> 
> #   Failed test 'LocalizedDateTime'
> #   at t/api/date.t line 241.
> #  got: 'Fri, Jul 1, 2005 11:10:00 AM'
> # expected: 'Fri, Jul 1, 2005 11:10:00 AM'
> # Some tests failed or we bailed out, tmp directory 
> '/<>/t/tmp/api-date.t-yAiaxCZo' is not cleaned
> # Looks like you failed 10 tests of 231.
> t/api/date.t ... 
> Dubious, test returned 10 (wstat 2560, 0xa00)
> Failed 10/231 subtests 
> t/api/customfield.t  ok
> t/api/db_indexes.t . ok
> t/api/db_multiple_connections.t  ok
> t/api/emailparser.t  ok
> t/api/group-rights.t ... ok
> t/api/execute-code.t ... ok
> t/api/groups.t 

Bug#1031923: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

[Cyril Brulebois]

Hi,

Andrew, please use reply-all, to reply to the bug and to the bug
submitter. A list-only reply doesn't quite help…

Andrew M.A. Cater  (2023-02-25):
> > I have installed Debian testing (bookworm) from one of the latest ISO images
> > (https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-
> > amd64-netinst.iso from 2023-02-21) and after an apparently succesfull
> > installation the system cannot be booted.

Enrique, thanks for the report.

We've published an official release one week ago. I'm not sure why
you're not using that instead of a random weekly build.

> This is a known issue - try using the Alpha 2 installer in which this
> issue is not present.
> 
> The e2fsprogs mismatch with grub is likely to be fixed by reverting
> problematic versions.

No, the problem here is that e2fsck is from testing, while the
filesystem has been created by mke2fs from unstable, and the former
doesn't know about a new feature turned on by the latter.


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


signature.asc
Description: PGP signature

Processed: pacparser: diff for NMU version 1.3.6-1.4

[Debian Bug Tracking System]

Processing control commands:

> tags 1026106 + patch
Bug #1026106 [src:pacparser] pacparser: CVE-2019-25078: memory overwrite issue 
for pacparser_find_proxy function
Added tag(s) patch.
> tags 1026106 + pending
Bug #1026106 [src:pacparser] pacparser: CVE-2019-25078: memory overwrite issue 
for pacparser_find_proxy function
Added tag(s) pending.

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

Processed: qca2: diff for NMU version 2.3.5-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1031438 + patch
Bug #1031438 [src:qca2] qca2: FTBFS: dh_auto_test: error: cd build && make -j8 
test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2
Added tag(s) patch.
> tags 1031438 + pending
Bug #1031438 [src:qca2] qca2: FTBFS: dh_auto_test: error: cd build && make -j8 
test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2
Added tag(s) pending.

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

Bug#1031438: qca2: diff for NMU version 2.3.5-1.1

[Adrian Bunk]

Control: tags 1031438 + patch
Control: tags 1031438 + pending

Dear maintainer,

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

cu
Adrian
diff -Nru qca2-2.3.5/debian/changelog qca2-2.3.5/debian/changelog
--- qca2-2.3.5/debian/changelog	2022-10-22 17:37:05.0 +0300
+++ qca2-2.3.5/debian/changelog	2023-02-25 17:03:48.0 +0200
@@ -1,3 +1,11 @@
+qca2 (2.3.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix to disable test that no longer works with
+OpenSSL 3.0.8. (Closes: #1031438)
+
+ -- Adrian Bunk   Sat, 25 Feb 2023 17:03:48 +0200
+
 qca2 (2.3.5-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru qca2-2.3.5/debian/patches/0001-Remove-test-that-openssl-has-decided-it-s-wrong.patch qca2-2.3.5/debian/patches/0001-Remove-test-that-openssl-has-decided-it-s-wrong.patch
--- qca2-2.3.5/debian/patches/0001-Remove-test-that-openssl-has-decided-it-s-wrong.patch	1970-01-01 02:00:00.0 +0200
+++ qca2-2.3.5/debian/patches/0001-Remove-test-that-openssl-has-decided-it-s-wrong.patch	2023-02-25 17:03:29.0 +0200
@@ -0,0 +1,34 @@
+From 714073747c4a3ccff7a8c85c72872bdf6bd3db4a Mon Sep 17 00:00:00 2001
+From: Albert Astals Cid 
+Date: Mon, 20 Feb 2023 00:19:19 +0100
+Subject: Remove test that openssl has decided it's wrong
+
+---
+ unittest/pkits/pkits.cpp | 4 
+ 1 file changed, 4 insertions(+)
+
+diff --git a/unittest/pkits/pkits.cpp b/unittest/pkits/pkits.cpp
+index 8f4af29f..7a41121c 100644
+--- a/unittest/pkits/pkits.cpp
 b/unittest/pkits/pkits.cpp
+@@ -256,6 +256,9 @@ void Pkits::pkits4_1_4()
+ 
+ void Pkits::pkits4_1_5()
+ {
++// openssl has decided that they don't want to support this ¯\_(ツ)_/¯
++// https://github.com/openssl/openssl/issues/20233
++#if 0
+ QStringList providersToTest;
+ providersToTest.append(QStringLiteral("qca-ossl"));
+ 
+@@ -298,6 +301,7 @@ void Pkits::pkits4_1_5()
+ QCOMPARE(cert.validate(trusted, untrusted), QCA::ValidityGood);
+ }
+ }
++#endif
+ }
+ 
+ void Pkits::pkits4_1_6()
+-- 
+2.30.2
+
diff -Nru qca2-2.3.5/debian/patches/series qca2-2.3.5/debian/patches/series
--- qca2-2.3.5/debian/patches/series	2022-10-22 16:06:35.0 +0300
+++ qca2-2.3.5/debian/patches/series	2023-02-25 17:03:48.0 +0200
@@ -1,3 +1,4 @@
 upstream_hashunittest-run-sha384longtest-only-for-providers-t.patch
 pipeunittest_more_wait.diff
 disable_pgpunittest.diff
+0001-Remove-test-that-openssl-has-decided-it-s-wrong.patch

Bug#1026106: pacparser: diff for NMU version 1.3.6-1.4

[Adrian Bunk]

Control: tags 1026106 + patch
Control: tags 1026106 + pending

Dear maintainer,

I've prepared an NMU for pacparser (versioned as 1.3.6-1.4) and uploaded 
it to DELAYED/5. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru pacparser-1.3.6/debian/changelog pacparser-1.3.6/debian/changelog
--- pacparser-1.3.6/debian/changelog	2022-07-25 00:20:17.0 +0300
+++ pacparser-1.3.6/debian/changelog	2023-02-25 16:48:20.0 +0200
@@ -1,3 +1,11 @@
+pacparser (1.3.6-1.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * CVE-2019-25078: Possible memory overwrite in pacparser_find_proxy()
+(Closes: #1026106)
+
+ -- Adrian Bunk   Sat, 25 Feb 2023 16:48:20 +0200
+
 pacparser (1.3.6-1.3) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru pacparser-1.3.6/debian/patches/0001-Fix-possible-memory-overwrite-vulnerability.-134.patch pacparser-1.3.6/debian/patches/0001-Fix-possible-memory-overwrite-vulnerability.-134.patch
--- pacparser-1.3.6/debian/patches/0001-Fix-possible-memory-overwrite-vulnerability.-134.patch	1970-01-01 02:00:00.0 +0200
+++ pacparser-1.3.6/debian/patches/0001-Fix-possible-memory-overwrite-vulnerability.-134.patch	2023-02-25 16:48:20.0 +0200
@@ -0,0 +1,30 @@
+From 91a93b40f6b4e0a1a9ac497edfbc2a4b18196483 Mon Sep 17 00:00:00 2001
+From: Manu Garg 
+Date: Wed, 13 Apr 2022 14:30:07 -0700
+Subject: Fix possible memory overwrite vulnerability. (#134)
+
+---
+ src/pacparser.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/pacparser.c b/src/pacparser.c
+index cc70a64..5a37d09 100644
+--- a/src/pacparser.c
 b/src/pacparser.c
+@@ -440,11 +440,11 @@ pacparser_find_proxy(const char *url, const char *host)
+   // Hostname shouldn't have single quotes in them
+   if (strchr(host, '\'')) {
+ print_error("%s %s\n", error_prefix,
+-		"Invalid hostname: hostname can't have single quotes.");
++  "Invalid hostname: hostname can't have single quotes.");
+ return NULL;
+   }
+ 
+-  script = (char*) malloc(32 + strlen(url) + strlen(host));
++  script = (char*) malloc(32 + strlen(sanitized_url) + strlen(host));
+   script[0] = '\0';
+   strcat(script, "FindProxyForURL('");
+   strcat(script, sanitized_url);
+-- 
+2.30.2
+
diff -Nru pacparser-1.3.6/debian/patches/series pacparser-1.3.6/debian/patches/series
--- pacparser-1.3.6/debian/patches/series	2020-03-02 07:22:40.0 +0200
+++ pacparser-1.3.6/debian/patches/series	2023-02-25 16:48:18.0 +0200
@@ -1 +1,2 @@
 py3only.patch
+0001-Fix-possible-memory-overwrite-vulnerability.-134.patch

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

[Scott Kitterman]

Generally favorably, but I'd rather wait for upstream to agree on it, otherwise 
it may be a patch we have to maintain forever.  What's their reaction to the 
change?

It's also late in the release cycle to do it (not definitely a problem, but 
calls for caution).

Scott K

On February 25, 2023 2:18:08 PM UTC, Sebastian Andrzej Siewior 
 wrote:
>On 2023-02-24 21:00:43 [+], Scott Kitterman wrote:
>> I don't know of anything.  I'd go ahead and upload the fix.
>
>how do you feel about replacing libtfm with openssl?
>
>> Scott K
>
>Sebastian

Bug#1031931: youtube-dl: All binaries missing in youtube-dl 2021.12.17-2

[Michael Stoeger]

Package: youtube-dl
Version: 2021.12.17-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

it looks like the whole binary part is missing in the current version of
youtube-dl in Debian testing and unstable. Of course, the program is not usable
with /usr/bin/youtube-dl missing.

The package youtube-dl_2021.12.17-2_all.deb is quite small (75KB) compared to
the prior version youtube-dl_2021.12.17-1~bpo11+1_all.deb (1.1MB).
I checked the deb package and the data.tar.xz contains only the directory
./usr/share/doc/youtube-dl/, nothing else:

$ tar tvpf data.tar.xz
drwxr-xr-x root/root 0 2023-01-03 23:21 ./
drwxr-xr-x root/root 0 2023-01-03 23:21 ./usr/
drwxr-xr-x root/root 0 2023-01-03 23:21 ./usr/share/
drwxr-xr-x root/root 0 2023-01-03 23:21 ./usr/share/doc/
drwxr-xr-x root/root 0 2023-01-03 23:21 ./usr/share/doc/youtube-dl/
-rw-r--r-- root/root  2778 2023-01-03 23:21 ./usr/share/doc/youtube-
dl/NEWS.Debian.gz
-rw-r--r-- root/root  3016 2023-01-03 23:21 ./usr/share/doc/youtube-
dl/changelog.Debian.gz
-rw-r--r-- root/root 61719 2021-12-16 19:49 ./usr/share/doc/youtube-
dl/changelog.gz
-rw-r--r-- root/root  2563 2022-10-16 08:35 ./usr/share/doc/youtube-
dl/copyright



Best regards, Michael
PS: I hope, I did not adress a bug already submitted. I am not too familiar
with the Debian bug tracking but I did not find a matching bug report in
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=youtube-dl


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages youtube-dl depends on:
ii  python33.11.1-3
ii  python3-pkg-resources  66.1.1-1

Versions of packages youtube-dl recommends:
ii  ca-certificates   20211016
ii  curl  7.87.0-2
ii  ffmpeg7:5.1.2-2
ii  mplayer   2:1.5+svn38408-1
ii  mpv   0.35.1-1
ii  python3-pycryptodome  3.11.0+dfsg1-4
ii  python3-pyxattr   0.8.0-1+b1
ii  rtmpdump  2.4+20151223.gitfa8646d.1-2+b2
ii  wget  1.21.3-1+b2

Versions of packages youtube-dl suggests:
pn  libfribidi-bin | bidiv  
ii  phantomjs   2.1.1+dfsg-2+b2

-- no debconf information

Bug#1031801: marked as done (libduktape.so.207: undefined symbol: log2)

[Debian Bug Tracking System]

Your message dated Sat, 25 Feb 2023 14:35:29 +
with message-id 
and subject line Bug#1031801: fixed in duktape 2.7.0-2
has caused the Debian Bug report #1031801,
regarding libduktape.so.207: undefined symbol: log2
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.)


-- 
1031801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libduktape207
Version: 2.7.0-1+b1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

with this package version installed starting e.g. polkitd fails with:

/usr/lib/polkit-1/polkitd: symbol lookup error:
  /usr/lib/x86_64-linux-gnu/libduktape.so.207: undefined symbol: log2

It appears that libduktape.so.207 is missing a link against libm:

$ ldd /usr/lib/x86_64-linux-gnu/libduktape.so.207
linux-vdso.so.1 (0x7ffda6777000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb0fce14000)
/lib64/ld-linux-x86-64.so.2 (0x7fb0fd04c000)

Recompiling and linking with -lm fixes the issue.

Cheers
Daniel


-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (700, 'stable-updates'), (700, 'stable-security'), (700, 
'stable'), (500, 'testing'), (200, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages libduktape207 depends on:
ii  libc6  2.36-8

libduktape207 recommends no packages.

libduktape207 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: duktape
Source-Version: 2.7.0-2
Done: Thorsten Alteholz 

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated duktape package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 25 Feb 2023 12:31:54 +0100
Source: duktape
Architecture: source
Version: 2.7.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian IoT Maintainers 

Changed-By: Thorsten Alteholz 
Closes: 1031801
Changes:
 duktape (2.7.0-2) unstable; urgency=medium
 .
   * add -lm to LDFLAGS for libduktape
 (Closes: #1031801)
Checksums-Sha1:
 efb4a16c6fa9bc7af8e7879d8ea56b9011ea 2194 duktape_2.7.0-2.dsc
 8200c8e417dbab7adcc12c4dbdef7651cfc55794 1026524 duktape_2.7.0.orig.tar.xz
 63f1b8e7a2d8908bd77d455701476aaf2dd4e908 7520 duktape_2.7.0-2.debian.tar.xz
 215c9ae856a166757eb3444ed36930bac4a062ee 7308 duktape_2.7.0-2_amd64.buildinfo
Checksums-Sha256:
 929e540895cf8711c922fccc9b2e6cb4c6cf07ccff7ceea1fdf673f82002f726 2194 
duktape_2.7.0-2.dsc
 90f8d2fa8b5567c6899830ddef2c03f3c27960b11aca222fa17aa7ac613c2890 1026524 
duktape_2.7.0.orig.tar.xz
 60f9c4893f4f539f23a8d7c373a29b6dc78aad82c2112bb46a11f0aae68c1ec0 7520 
duktape_2.7.0-2.debian.tar.xz
 4dc2d4a1cfffdebf85bfc660abf33ac85d9b3f2f4929e0eb134b306a7dc335b2 7308 
duktape_2.7.0-2_amd64.buildinfo
Files:
 4ba42d09f67b3eae08dea077691f67a7 2194 interpreters optional duktape_2.7.0-2.dsc
 b3200b02ab80125b694bae887d7c1ca6 1026524 interpreters optional 
duktape_2.7.0.orig.tar.xz
 7c072b735abaf4187d3abf6b98afa9d5 7520 interpreters optional 
duktape_2.7.0-2.debian.tar.xz
 304dcfda9c97a708b70d2c8d2844d9fd 7308 interpreters optional 
duktape_2.7.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmP6ES1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR1JUD/9CDWUgM9d9UZjbsFFGgxh2s2WGQY0v
WoaIUV5Qrx+JdrAjkuSVwkMFOTSWlfxuUND1m/+WfBYUGiDWUrOegKbaOEtstvFQ
M16tOMpl5+IaLVFqWnKbDTNCUBblUWIHQ87dp59dFcOaQO3kLXhmG8FaWq6NjUV0
8LQxK2ATtfIf1YazKg/HC0CMmFiqQ1uVWcZjYIaCrq2WNcqF5lG3p+mRcoIiUeKn