Bug#1005772: marked as done (go-rpmdb: trying to overwrite '/usr/bin/rpmdb', which is also in package rpm)
Your message dated Thu, 24 Mar 2022 05:34:06 + with message-id and subject line Bug#1005772: fixed in go-rpmdb 0.0~git20210911.73bd0ce-2 has caused the Debian Bug report #1005772, regarding go-rpmdb: trying to overwrite '/usr/bin/rpmdb', which is also in package rpm 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.) -- 1005772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: go-rpmdb Version: 0.0~git20210911.73bd0ce-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Preparing to unpack .../go-rpmdb_0.0~git20210911.73bd0ce-1_amd64.deb ... Unpacking go-rpmdb (0.0~git20210911.73bd0ce-1) ... dpkg: error processing archive /var/cache/apt/archives/go-rpmdb_0.0~git20210911.73bd0ce-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/rpmdb', which is also in package rpm 4.17.0+dfsg1-4 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/go-rpmdb_0.0~git20210911.73bd0ce-1_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. The use of alternatives might also be an option, this will need coordination with the rpm package. cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html rpm=4.17.0+dfsg1-4_go-rpmdb=0.0~git20210911.73bd0ce-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: go-rpmdb Source-Version: 0.0~git20210911.73bd0ce-2 Done: Nobuhiro Iwamatsu We believe that the bug you reported is fixed in the latest version of go-rpmdb, 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 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nobuhiro Iwamatsu (supplier of updated go-rpmdb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 24 Mar 2022 14:04:20 +0900 Source: go-rpmdb Architecture: source Version: 0.0~git20210911.73bd0ce-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Nobuhiro Iwamatsu Closes: 1005772 Changes: go-rpmdb (0.0~git20210911.73bd0ce-2) unstable; urgency=medium . * Update d/go-rpmdb.install. - Change file name from rpmdb to go-rpmdb (Closes:#1005772) * Update d/control. - Add dh-exec to B-D. Checksums-Sha1: 896534338a8b418ff4e45a0a06ca2fa4add220bf 2373 go-rpmdb_0.0~git20210911.73bd0ce-2.dsc e08cc4a3ca915453cfe42969b6186425b6b0e4e0 2904 go-rpmdb_0.0~git20210911.73bd0ce-2.debian.tar.xz 6dce6293510dc99cdbf5f4d272e3e68c8c3cef8c 6864 go-rpmdb_0.0~git20210911.73bd0ce-2_amd64.buildinfo Checksums-Sha256: 4f276e14a097286f5e349ebad029deeda67761d6558a32a83c3f2e8eaf9e593e 2373 go-rpmdb_0.0~git20210911.73bd0ce-2.dsc 01b6e510861974ed52086ddcdfab68d1a86a8ec2bd0a2d827749b2be54a14183 2904 go-rpmdb_0.0~git20210911.73bd0ce-2.debian.tar.xz 356c64b0101a016af2acd2addbad7fc601f351e5b746bb7be779fef206d529ea 6864 go-rpmdb_0.0~git20210911.73bd0ce-2_amd64.buildinfo Files: d17b225291cb39f3a2b18a7dbc5ca74f 2373 golang optional go-rpmdb_0.0~git20210911.73bd0ce-2.dsc ea9363171672158c1b52fc8f52d7a24f 2904 golang optional go-rpmdb_0.0~git20210911.73bd0ce-2.debian.tar.xz 513d5a779daa2a51168272e91b429cd5 6864 golang optional go-rpmdb_0.0~git20210911.73bd0ce-2_amd64.
Processed: forcibly merging 984008 1006919
Processing commands for cont...@bugs.debian.org: > forcemerge 984008 1006919 Bug #984008 [src:cbmc] cbmc: ftbfs with GCC-11 Bug #1006919 [src:cbmc] src:cbmc FTBFS Added tag(s) ftbfs. Merged 984008 1006919 > thanks Stopping processing here. Please contact me if you need assistance. -- 1006919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006919 984008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008189: meson: gnome module incorrectly requires gtk4-update-icon-cache
Source: meson Version: 0.62.0-1 Severity: serious Tags: patch The new meson version breaks things that uses the gnome module to update the icon cache. Specifically, it requires gtk4-update-icon-cache which is only recommended by gtk4 and the Debian buildds don't install recommends by default. However, both gtk3 and gtk4 indirectly depend on gtk-update-icon-cache Therefore, please cherry-pick this commit: https://github.com/mesonbuild/meson/commit/dac212e1bba7 Thank you, Jeremy Bicha
Processed: tagging 1008180
Processing commands for cont...@bugs.debian.org: > tags 1008180 + pending Bug #1008180 [src:php-pear] php-pear : Depends: php-archive-tar (>= 1.4.9) but it is not installable Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1008180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008180: php-pear uninstallable
On Wed, Mar 23, 2022 at 09:21:57AM -0400, Joe Nahmias wrote: > Hello Ondřej, > > Firstly, thanks for all your work on packaging PHP for Debian! > > I noticed that the recent php-pear upload to Debian unstable, > 1:1.10.13+submodules+notgz+2022032201-1, is uninstallable due to a bad dep on > php-archive-tar. I see in the Salsa git repo that you reverted a commit and > then updated the changelog with -2, but there is no tag nor was -2 uploaded to > Debian. > > Was this deliberate? Is more testing needed? Can you just tag/upload? Should > I? > > Much appreciated, > --Joe On the assumption that this was likely an oversight, I uploaded the -2 from Salsa (with a quick addition to close the bug in the changelog) to the DELAYED/2 queue. Happy to revert if this is undesirable. --Joe
Bug#1008188: marked as done (reportbug is unusable, can't be run without sudo)
Your message dated Wed, 23 Mar 2022 21:56:56 -0400
with message-id
and subject line Re: Bug#1008188: reportbug is unusable, can't be run without
sudo
has caused the Debian Bug report #1008188,
regarding reportbug is unusable, can't be run without sudo
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.)
--
1008188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 11.4
Severity: grave
Basically reportbug is broken.
Traceback (most recent call last):
File "/usr/bin/reportbug", line 39, in
from reportbug import utils
File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 70, in
from . import debbugs # noqa: E402
File "/usr/lib/python3/dist-packages/reportbug/debbugs.py", line 33, in
import debianbts
File "/usr/lib/python3/dist-packages/debianbts/__init__.py", line 1, in
from debianbts.debianbts import * # noqa
File "/usr/lib/python3/dist-packages/debianbts/debianbts.py", line 21, in
import pysimplesoap
File "/usr/lib/python3/dist-packages/pysimplesoap/__init__.py", line 16,
in
from . import client, server, simplexml, transport
File "/usr/lib/python3/dist-packages/pysimplesoap/client.py", line 33, in
from .transport import get_http_wrapper, set_http_wrapper, get_Http
File "/usr/lib/python3/dist-packages/pysimplesoap/transport.py", line 66,
in
import httplib2
File
"/home/jorge/.local/lib/python3.9/site-packages/httplib2/__init__.py", line
52, in
from . import auth
File "/home/jorge/.local/lib/python3.9/site-packages/httplib2/auth.py",
line 20, in
auth_param_name =
token.copy().setName("auth-param-name").addParseAction(pp.downcaseTokens)
AttributeError: module 'pyparsing' has no attribute 'downcaseTokens'
-- Package-specific info:
** Environment settings:
INTERFACE="text"
** /root/.reportbugrc:
reportbug_version "11.4.1"
mode advanced
ui text
realname "jorge"
email "1994jorgesanc...@gmail.com"
no-check-uid
smtphost "smtp.google.com"
smtptls
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.16.0-5-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_DIE
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 reportbug depends on:
ii apt2.4.2
ii python33.9.8-1
ii python3-reportbug 11.4.1
ii sensible-utils 0.0.17
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn claws-mail
ii debconf1.5.79
pn debsums
pn dlocate
pn emacs-bin-common
ii exim4-daemon-light [mail-transport-agent] 4.95-4+b1
ii file 1:5.41-2
ii gnupg 2.2.27-3
pn python3-urwid
pn reportbug-gtk
ii xdg-utils 1.1.3-4.1
Versions of packages python3-reportbug depends on:
ii apt2.4.2
ii file 1:5.41-2
ii python33.9.8-1
ii python3-apt2.3.0+b1
ii python3-debian 0.1.43
ii python3-debianbts 3.2.0
ii python3-requests 2.25.1+dfsg-2
ii sensible-utils 0.0.17
python3-reportbug suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Mar 23, 2022 at 9:21 PM J K sanchez <1994jorgesanc...@gmail.com> wrote:
>
> Package: reportbug
> Version: 11.4
> Severity: grave
>
> Basically reportbug is broken.
that seems unlikely, given you just reported 1008187
>
> Traceback (most recent call last):
> File "/usr/bin/reportbug", line 39, in
> from reportbug import utils
> File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 70, in
>
> from . import debbugs # noqa: E402
> File "/usr/lib/python3/dist-packages/reportbug/debbugs.py", line 33, in
>
> import debianbts
> File "/usr/lib/python3/dist-packages/debianbts/__init__.py", line 1, in
>
> from debianbts.debianbts import * # noqa
> File "/usr/lib/python3/dist-packages/debianbts/debianbts.py", line 21, in
>
> import pysimplesoap
> File "/usr/lib/python3/dist-packages/pysimplesoap/__init__.py", line 16,
Bug#1008188: reportbug is unusable, can't be run without sudo
Package: reportbug
Version: 11.4
Severity: grave
Basically reportbug is broken.
Traceback (most recent call last):
File "/usr/bin/reportbug", line 39, in
from reportbug import utils
File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 70, in
from . import debbugs # noqa: E402
File "/usr/lib/python3/dist-packages/reportbug/debbugs.py", line 33, in
import debianbts
File "/usr/lib/python3/dist-packages/debianbts/__init__.py", line 1, in
from debianbts.debianbts import * # noqa
File "/usr/lib/python3/dist-packages/debianbts/debianbts.py", line 21, in
import pysimplesoap
File "/usr/lib/python3/dist-packages/pysimplesoap/__init__.py", line 16,
in
from . import client, server, simplexml, transport
File "/usr/lib/python3/dist-packages/pysimplesoap/client.py", line 33, in
from .transport import get_http_wrapper, set_http_wrapper, get_Http
File "/usr/lib/python3/dist-packages/pysimplesoap/transport.py", line 66,
in
import httplib2
File
"/home/jorge/.local/lib/python3.9/site-packages/httplib2/__init__.py", line
52, in
from . import auth
File "/home/jorge/.local/lib/python3.9/site-packages/httplib2/auth.py",
line 20, in
auth_param_name =
token.copy().setName("auth-param-name").addParseAction(pp.downcaseTokens)
AttributeError: module 'pyparsing' has no attribute 'downcaseTokens'
-- Package-specific info:
** Environment settings:
INTERFACE="text"
** /root/.reportbugrc:
reportbug_version "11.4.1"
mode advanced
ui text
realname "jorge"
email "1994jorgesanc...@gmail.com"
no-check-uid
smtphost "smtp.google.com"
smtptls
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.16.0-5-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_DIE
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 reportbug depends on:
ii apt2.4.2
ii python33.9.8-1
ii python3-reportbug 11.4.1
ii sensible-utils 0.0.17
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn claws-mail
ii debconf1.5.79
pn debsums
pn dlocate
pn emacs-bin-common
ii exim4-daemon-light [mail-transport-agent] 4.95-4+b1
ii file 1:5.41-2
ii gnupg 2.2.27-3
pn python3-urwid
pn reportbug-gtk
ii xdg-utils 1.1.3-4.1
Versions of packages python3-reportbug depends on:
ii apt2.4.2
ii file 1:5.41-2
ii python33.9.8-1
ii python3-apt2.3.0+b1
ii python3-debian 0.1.43
ii python3-debianbts 3.2.0
ii python3-requests 2.25.1+dfsg-2
ii sensible-utils 0.0.17
python3-reportbug suggests no packages.
-- no debconf information
Bug#1006039: marked as done (pytest-xdist: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13)
Your message dated Thu, 24 Mar 2022 01:03:49 +
with message-id
and subject line Bug#1006039: fixed in pytest-xdist 2.5.0-2
has caused the Debian Bug report #1006039,
regarding pytest-xdist: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1006039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-xdist
Version: 2.5.0-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):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:237: python3.10 setup.py config
> running config
> I: pybuild base:237: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:237: /usr/bin/python3.10 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist
> copying src/xdist/__init__.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist
> copying src/xdist/workermanage.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist
> copying src/xdist/dsession.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist
> copying src/xdist/report.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist
> copying src/xdist/newhooks.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist
> copying src/xdist/looponfail.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist
> copying src/xdist/remote.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist
> copying src/xdist/_version.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist
> copying src/xdist/plugin.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist
> creating
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist/scheduler
> copying src/xdist/scheduler/load.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist/scheduler
> copying src/xdist/scheduler/__init__.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist/scheduler
> copying src/xdist/scheduler/loadgroup.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist/scheduler
> copying src/xdist/scheduler/each.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist/scheduler
> copying src/xdist/scheduler/loadfile.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist/scheduler
> copying src/xdist/scheduler/loadscope.py ->
> /<>/.pybuild/cpython3_3.10_pytest-xdist/build/xdist/scheduler
> I: pybuild base:237: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist
> copying src/xdist/__init__.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist
> copying src/xdist/workermanage.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist
> copying src/xdist/dsession.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist
> copying src/xdist/report.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist
> copying src/xdist/newhooks.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist
> copying src/xdist/looponfail.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist
> copying src/xdist/remote.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist
> copying src/xdist/_version.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist
> copying src/xdist/plugin.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist
> creating
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist/scheduler
> copying src/xdist/scheduler/load.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist/scheduler
> copying src/xdist/scheduler/__init__.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist/scheduler
> copying src/xdist/scheduler/loadgroup.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist/scheduler
> copying src/xdist/scheduler/each.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist/scheduler
> copying src/xdist/scheduler/loadfile.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist/scheduler
> copying src/xdist/scheduler/loadscope.py ->
> /<>/.pybuild/cpython3_3.9_pytest-xdist/build/xdist/scheduler
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:237: cd
> /<>/.pybuild/cpython3_3.10_pytest-xdist/b
Processed: notfound 1008180 in 1:1.10.12+submodules+notgz+20210212-1 ...
Processing commands for cont...@bugs.debian.org: > notfound 1008180 1:1.10.12+submodules+notgz+20210212-1 Bug #1008180 [src:php-pear] php-pear : Depends: php-archive-tar (>= 1.4.9) but it is not installable No longer marked as found in versions php-pear/1:1.10.12+submodules+notgz+20210212-1. > found 1008180 1:1.10.13+submodules+notgz+2022032201-1 Bug #1008180 [src:php-pear] php-pear : Depends: php-archive-tar (>= 1.4.9) but it is not installable Marked as found in versions php-pear/1:1.10.13+submodules+notgz+2022032201-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1008180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008179: pandas: disable numba tests again
Source: pandas Version: 1.3.5+dfsg-3 Severity: serious Tags: sid bookworm numba is not ready for python 3.10 (#1000336) and is being removed for the upcoming transition. Please disable the numba tests until that is fixed as otherwise pandas is not buildable in bookworm. Cheers -- Sebastian Ramacher
Bug#1008180: php-pear : Depends: php-archive-tar (>= 1.4.9) but it is not installable
Source: php-pear Version: 1:1.10.12+submodules+notgz+20210212-1 Severity: serious Justification: uninstallable / unsatisfied Depends X-Debbugs-Cc: car...@debian.org Hi It looks php-pear got a new Depends which makes the package uninstallable: # apt-get install php-pear Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: php-pear : Depends: php-archive-tar (>= 1.4.9) but it is not installable E: Unable to correct problems, you have held broken packages. Regards, Salvatore
Bug#1005545: marked as done (gcr: FTBFS: ../gck/meson.build:130:2: ERROR: gnome.generate_gir got unknown keyword arguments "packages")
Your message dated Wed, 23 Mar 2022 20:41:09 + with message-id and subject line Bug#1005545: fixed in gcr 3.40.0-4 has caused the Debian Bug report #1005545, regarding gcr: FTBFS: ../gck/meson.build:130:2: ERROR: gnome.generate_gir got unknown keyword arguments "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.) -- 1005545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcr Version: 3.40.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- \ > -Dgtk_doc=true \ > -Dintrospection=true \ > -Dgtk=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dgtk_doc=true > -Dintrospection=true -Dgtk=true > The Meson build system > Version: 0.61.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: gcr > Project version: 3.40.0 > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.38 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency glib-2.0 found: YES 2.70.3 > Run-time dependency gmodule-no-export-2.0 found: YES 2.70.3 > Run-time dependency gthread-2.0 found: YES 2.70.3 > Run-time dependency gobject-2.0 found: YES 2.70.3 > Run-time dependency gio-2.0 found: YES 2.70.3 > Run-time dependency gio-unix-2.0 found: YES 2.70.3 > Program gpg found: YES (/usr/bin/gpg) > Run-time dependency libgcrypt found: YES 1.9.4 > Run-time dependency p11-kit-1 found: YES 0.24.0 > Run-time dependency gtk+-3.0 found: YES 3.24.31 > Has header "locale.h" : YES > Checking for function "timegm" : YES > Checking for function "mlock" : YES > Configuring config.h using configuration > Configuring gck-version.h using configuration > Program glib-mkenums found: YES (/usr/bin/glib-mkenums) > Program glib-mkenums found: YES (/usr/bin/glib-mkenums) > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Program glib-genmarshal found: YES (/usr/bin/glib-genmarshal) > Compiler for C supports link arguments > -Wl,--version-script,/<>/gck/libgck.map: YES > > ../gck/meson.build:130:2: ERROR: gnome.generate_gir got unknown keyword > arguments "packages" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2022-02-12T22:39:42.514438 > Main binary: /usr/bin/python3 > Build Options: -Dgtk_doc=true -Dintrospection=true -Dgtk=true -Dprefix=/usr > -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc > -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.61.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: gcr > Project version: 3.40.0 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.38 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,-z,defs > Sanity check compile stdout: > > - > Sanity check compile stderr: > > - > Running test binary command: > /<>/obj-x86_64-linux-gnu/meson-private/sanitycheckc.exe > C compiler for the build machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) > 11.2.0") > C linker for the build machine: cc ld.bfd 2
Bug#1005545: marked as pending in gcr
Control: tag -1 pending Hello, Bug #1005545 in gcr reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gcr/-/commit/cb063fab972029bc66fe64b0e3256017e4ee4465 Cherry-pick patch to fix build with latest meson Closes: #1005545 (this message was generated automatically) -- Greetings https://bugs.debian.org/1005545
Processed: Bug#1005545 marked as pending in gcr
Processing control commands: > tag -1 pending Bug #1005545 [src:gcr] gcr: FTBFS: ../gck/meson.build:130:2: ERROR: gnome.generate_gir got unknown keyword arguments "packages" Added tag(s) pending. -- 1005545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 997445, tagging 997410, found 1008140 in 4.3.6~ds1+~cs9.7.12-1, tagging 1006127 ...
Processing commands for cont...@bugs.debian.org:
> tags 997445 + experimental
Bug #997445 {Done: Nicolas Boulenguez } [src:libaunit]
libaunit: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.'
Added tag(s) experimental.
> tags 997410 + experimental
Bug #997410 {Done: Nicolas Boulenguez }
[src:libtemplates-parser] libtemplates-parser: FTBFS: '! LaTeX Error: File
`tgtermes.sty' not found.'
Added tag(s) experimental.
> found 1008140 4.3.6~ds1+~cs9.7.12-1
Bug #1008140 {Done: Yadd } [chai] mocha: Incompatible with
current node-chai
Marked as found in versions node-chai/4.3.6~ds1+~cs9.7.12-1.
> tags 1006127 + stretch buster
Bug #1006127 [wireless-regdb] wireless-regdb stable policy
Added tag(s) buster and stretch.
> reassign 928184 src:valgrind-if-available
Bug #928184 {Done: Adam Borowski } [valgrind] valgrind:
please add valgrind-if-available metapackage
Bug reassigned from package 'valgrind' to 'src:valgrind-if-available'.
No longer marked as found in versions valgrind/1:3.14.0-3.
No longer marked as fixed in versions valgrind-if-available/3.18.1.
> fixed 928184 3.18.1
Bug #928184 {Done: Adam Borowski }
[src:valgrind-if-available] valgrind: please add valgrind-if-available
metapackage
Marked as fixed in versions valgrind-if-available/3.18.1.
> affects 928184 + src:valgrind
Bug #928184 {Done: Adam Borowski }
[src:valgrind-if-available] valgrind: please add valgrind-if-available
metapackage
Added indication that 928184 affects src:valgrind
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1006127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006127
1008140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008140
928184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928184
997410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997410
997445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1008150: libgrpc-dev: library name conflict with libupb-dev: libupb.so*
On 23/03/2022 18.43, László Böszörményi (GCS) wrote: Adding mutual Conflicts is not a valid solution here! For the moment, it will be my option. :-/ With zero rdepends that's somewhat acceptable. It seems upb is not fully mature and recently I can't install it with cmake. Might be the reason gRPC started to bundle upb and build with that exact snapshot version. If it's a bundled copy, grpc should probably rename the resulting library (and its SONAME) to e.g. libupb-grpc.so.* to not invade libupb's SONAME space. Andreas
Bug#1005858: gh,gitsome: File conflict, both ship /usr/bin/gh
Hi, On 23-03-2022 12:32, Jonas Smedegaard wrote: Quoting Anthony Fok (2022-03-23 11:08:36) Rather than keeping this "Serious" bug open and keeping both gitsome and gh out of Debian testing, I think the simple solution of having gh "Conflicts: gitsome", which is one of the option specified in https://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts, would suffice for now, allowing both packages to (re-)enter testing in the meantime. SZ, if you think the use of alternatives (such that both the gitsome and gh packages can be installed simultaneously) is a better solution, I'd be happy to work something out with you too. Please note that above Policy section covers only the functionality of that packaging hint, not its suitability. It is my understanding that both that specific use of Conflicts and the use of alternatives is only acceptable for executables providing same or at least largely overlapping) ABI. Do gitsome and gh provide same or quite similar ABI? It was already quoted in the bug report, policy is pretty clear (emphasis mine) (yes, I *suspect* that /usr/bin/gh does something quite different from reading the package descriptions): """ 10.1. Binaries Two different packages *must not* install programs with different functionality but with *the same filenames*. (The case of two programs having the same functionality but different implementations is handled via “alternatives” or the “Conflicts” mechanism. See Maintainer Scripts and Conflicting binary packages - Conflicts respectively.) If this case happens, one of the programs must be renamed. The maintainers should report this to the debian-devel mailing list and try to find a consensus about which program will have to be renamed. If a consensus cannot be reached, both programs must be renamed. """ Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1004870: python-xarray: autopkgtest regression on s390x
Hi Rajendra On Sun, 6 Mar 2022 at 12:42, Rajendra Kharat1 wrote: > Could you please share the steps to reproduce the issue. > As when I am trying to reproduce I ran into different problem of segmentation > fault. > Below are the steps that I followed. > 1. Install python3-xarray on debian on s390x arch. > 2. cd /usr/lib/python3/dist-packages/xarray > 3. python3 -m pytest tests/ -vvv > > For now I am debugging the segmentation fault, however just wanted to > validate the steps to reproduce. Here's a quick and dirty way to run autopkgtests locally: sudo apt install autopkgtest apt source python-xarray sudo autopkgtest -B python-xarray-0.17.0/ -- null Regards Graham
Processed: Re: Bug#1008150: libgrpc-dev: library name conflict with libupb-dev: libupb.so*
Processing control commands: > tags -1 +pending Bug #1008150 [libgrpc-dev] libgrpc-dev: library name conflict with libupb-dev: libupb.so* Added tag(s) pending. -- 1008150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008150: libgrpc-dev: library name conflict with libupb-dev: libupb.so*
Control: tags -1 +pending On Wed, Mar 23, 2022 at 10:57 AM Andreas Beckmann wrote: > during a test with piuparts I noticed your package failed to install > because it tries to overwrite other packages files. [...] > upb and grpc seem to be two unrelated projects, unfortunately > grpc/experimental started to use a library name already used by upb. > They use different SOVERSIONs right now, so the conflict is only > on the .so link. Indeed, these are different projects. > Adding mutual Conflicts is not a valid solution here! For the moment, it will be my option. :-/ It seems upb is not fully mature and recently I can't install it with cmake. Might be the reason gRPC started to bundle upb and build with that exact snapshot version. Regards, Laszlo/GCS
Processed (with 1 error): update bts with meta info
Processing commands for cont...@bugs.debian.org:
> reassign 1007737 src:golang-github-yuin-goldmark-highlighting
Bug #1007737 {Done: Anthony Fok }
[src:golang-github-alecthomas-chroma,src:golang-github-yuin-goldmark-highlighting]
golang-github-alecthomas-chroma breaks
golang-github-yuin-goldmark-highlighting autopkgtest:failed to render HTML
Bug reassigned from package
'src:golang-github-alecthomas-chroma,src:golang-github-yuin-goldmark-highlighting'
to 'src:golang-github-yuin-goldmark-highlighting'.
No longer marked as found in versions golang-github-alecthomas-chroma/0.10.0-1
and golang-github-yuin-goldmark-highlighting/0.0~git20210516.9216f9c-1.
No longer marked as fixed in versions
golang-github-yuin-goldmark-highlighting/0.0~git20220208.594be19-1.
> found 100773710077370.0~git20210516.9216f9c-1
Unknown command or malformed arguments to command.
> affects 1007737 src:golang-github-alecthomas-chroma
Bug #1007737 {Done: Anthony Fok }
[src:golang-github-yuin-goldmark-highlighting] golang-github-alecthomas-chroma
breaks golang-github-yuin-goldmark-highlighting autopkgtest:failed to render
HTML
Added indication that 1007737 affects src:golang-github-alecthomas-chroma
> fixed 1007737 0.0~git20220208.594be19-1
Bug #1007737 {Done: Anthony Fok }
[src:golang-github-yuin-goldmark-highlighting] golang-github-alecthomas-chroma
breaks golang-github-yuin-goldmark-highlighting autopkgtest:failed to render
HTML
Marked as fixed in versions
golang-github-yuin-goldmark-highlighting/0.0~git20220208.594be19-1.
> reassign 1007734 src:golang-github-niklasfasching-go-org 1.6.0-1
Bug #1007734 {Done: Anthony Fok }
[src:golang-github-alecthomas-chroma, src:golang-github-niklasfasching-go-org]
golang-github-alecthomas-chroma breaks golang-github-niklasfasching-go-org
autopkgtest: hashes do not match
Bug reassigned from package 'src:golang-github-alecthomas-chroma,
src:golang-github-niklasfasching-go-org' to
'src:golang-github-niklasfasching-go-org'.
No longer marked as found in versions golang-github-alecthomas-chroma/0.10.0-1
and golang-github-niklasfasching-go-org/1.6.0-1.
No longer marked as fixed in versions
golang-github-niklasfasching-go-org/1.6.2-1.
Bug #1007734 {Done: Anthony Fok }
[src:golang-github-niklasfasching-go-org] golang-github-alecthomas-chroma
breaks golang-github-niklasfasching-go-org autopkgtest: hashes do not match
Marked as found in versions golang-github-niklasfasching-go-org/1.6.0-1.
> affects 1007734 src:golang-github-alecthomas-chroma
Bug #1007734 {Done: Anthony Fok }
[src:golang-github-niklasfasching-go-org] golang-github-alecthomas-chroma
breaks golang-github-niklasfasching-go-org autopkgtest: hashes do not match
Added indication that 1007734 affects src:golang-github-alecthomas-chroma
> fixed 1007734 1.6.2-1
Bug #1007734 {Done: Anthony Fok }
[src:golang-github-niklasfasching-go-org] golang-github-alecthomas-chroma
breaks golang-github-niklasfasching-go-org autopkgtest: hashes do not match
Marked as fixed in versions golang-github-niklasfasching-go-org/1.6.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1007734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007734
1007737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1001057: wi32-loader migration [was: Re: Bug#998353: Bug#1007707: Update Indonesian translation]
Hold your horses. On 23-03-2022 07:44, Paul Gevers wrote: Last time [1], I just CC'ed ftpmaster and the magic happened, so dear ftpmasters, can you do "that" again? win32-loader is blocked behind grub2 now. I'm not aware of progress with bug #1001057 (in CC). Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1008119: [Debian-pan-maintainers] Bug#1008119: src:pyfai: fails to migrate to testing for too long: autopkgtest regression
Hi Jerome, On 23-03-2022 09:14, Jerome Kieffer wrote: I am the upstream author of pyFAI and the release 0.21.1 is a bugfix for the regressions spotted by the debian CI on a couple of 32-bit computer architectures (thanks to debian for that). Thus I don't understand why the migration from unstable to testing is blocked, especially that the tests passes on all architectures now. As noted by Fred, the tests apparently regressed in testing also now. I *suspect* it's due to python3.10 but haven't checked at all. However, the migration is now blocked by bug 1004509 which was filed *before* the regression happened in testing. So, while migration now would not cause a regression anymore (we could hint the package along), failing tests in testing are considered RC [1], so this needs to be solved one way or the other. Paul [1] https://release.debian.org/testing/rc_policy.txt 6(a) OpenPGP_signature Description: OpenPGP digital signature
Bug#998980: marked as done (gnu-standards: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Wed, 23 Mar 2022 15:22:57 + with message-id and subject line Bug#998980: fixed in gnu-standards 2022.03.23-0.1 has caused the Debian Bug report #998980, regarding gnu-standards: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnu-standards Version: 2010.03.11-1.1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: gnu-standards Source-Version: 2022.03.23-0.1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gnu-standards, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gnu-standards package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 23 Mar 2022 15:48:33 +0100 Source: gnu-standards Built-For-Profiles: noudeb Architecture: source Version: 2022.03.23-0.1 Distribution: unstable Urgency: medium Maintainer: Tim Retout Changed-By: Matthias Klose Closes: 741151 965564 978484 995652 998980 Changes: gnu-standards (2022.03.23-0.1) unstable; urgency=medium . * Non-maintainer upload. * Update from the upstream VCS. Closes: #741151. * Bump debhelper and standards version. Closes: #965564. * Add build targets. Closes: #998980. * Mark as M-A: foreign. Closes: #978484. * Make the build reproduible. Closes: #995652. Checksums-Sha1: 797017bc0742a3fd40b7a3ab5d5d6d7f330cf153 2041 gnu-standards_2022.03.23-0.1.dsc b809eb34f2773595956e73a3d0831e34edc516c9 132762 gnu-standards_2022.03.23.orig.tar.gz b670ed1b767bfc2b74b33b87150c6e87fa01ba9d 4688 gnu-standards_2022.03.23-0.1.debian.tar.xz 3ac638bd67077ce6645ab24452aa3d68580e90dc 6552 gnu-standards_2022.03.23-0.1_source.buildinfo Checksums-Sha256: 1e04df695c01f61316bf71874eb86008b33732f0db33cd31b68b91a76613f7bf 2041 gnu-standards_2022.03.23-0.1.dsc f7cd65d222f15195afd6cee6411fd0a598fe2059d83b9a83ff2c1efb94910119 132762 gnu-standards_2022.03.23.orig.tar.gz 6ddb17f2c5797999a7b5b6c65bb2dd567cf92b090530374afb24e49db42f8564 4688 gnu-standards_2022.03.23-0.1.debian.tar.xz ceb920a093b30206be514cedc7607ec9532cabe3dd0a73087426dc8447837e27 6552 gnu-standards_2022.03.23-0.1_source.buildinfo Files: 47e6158d60470b71e7a8c8f285390350 2041 doc optional gnu-standards_2022.03.23-0.1.dsc daa5d9ea7d496a4fe4902615e84b4afc 132762 doc optional gnu-standards_2022.03.23.orig.tar.gz a8938455ebe5d907fc40760265966d40 4688 doc optional gnu-standards_2022.03.23-0.1.debian.tar.xz 6f65e89f4fb89b58960e2c1bd1c2cbc3 6552 doc optional gnu-standards_2022.03.23-0.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmI7NXgQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9VBbD/9RbKJUvFk18eKlpEsIWw04F9cOi6x+0n+o rs1efCuSoQ5WQH1ygG4HhjXOJusarlBJUnsVGMp9mmaNuoNUka44xZlErt8jpaOj 88ltO+XTo6dDN3HNW93YroFNw//ARdvUJERGghwsnhbdhV8Uo/xpK6E1BcPETnmw Lwza/vvBUoqeJzKUwZWjsYFNN8hys7rqeclRGSsA0OhnqwUMinQdiOuYPW67icYj lXE0bvB3k2mDnWbzcEGlnNA8EQYwqBrWDoVjjiPq1dFApwOU5eRxY+eBmuC89Rc3 465VcfKU469TbX+aTMnrYYQD2lnw7yvCMEIz1gN4upLAV9dUi002Hchf+uwFoM7q Z7XlUoeu7NVcrOpxrM59BaonAn01DiJYVMi/CUO8CcgWZQiko72IYppgcsGvkBZS oJvICwXQCEKYr6HgtOvRYDPLzgOkT5v5IAutasm
Bug#965564: marked as done (gnu-standards: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Wed, 23 Mar 2022 15:22:57 + with message-id and subject line Bug#965564: fixed in gnu-standards 2022.03.23-0.1 has caused the Debian Bug report #965564, regarding gnu-standards: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965564 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnu-standards Version: 2010.03.11-1.1 Severity: normal Usertags: compat-5-6-removal Hi, The package gnu-standards uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: gnu-standards Source-Version: 2022.03.23-0.1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gnu-standards, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gnu-standards package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 23 Mar 2022 15:48:33 +0100 Source: gnu-standards Built-For-Profiles: noudeb Architecture: source Version: 2022.03.23-0.1 Distribution: unstable Urgency: medium Maintainer: Tim Retout Changed-By: Matthias Klose Closes: 741151 965564 978484 995652 998980 Changes: gnu-standards (2022.03.23-0.1) unstable; urgency=medium . * Non-maintainer upload. * Update from the upstream VCS. Closes: #741151. * Bump debhelper and standards version. Closes: #965564. * Add build targets. Closes: #998980. * Mark as M-A: foreign. Closes: #978484. * Make the build reproduible. Closes: #995652. Checksums-Sha1: 797017bc0742a3fd40b7a3ab5d5d6d7f330cf153 2041 gnu-standards_2022.03.23-0.1.dsc b809eb34f2773595956e73a3d0831e34edc516c9 132762 gnu-standards_2022.03.23.orig.tar.gz b670ed1b767bfc2b74b33b87150c6e87fa01ba9d 4688 gnu-standards_2022.03.23-0.1.debian.tar.xz 3ac638bd67077ce6645ab24452aa3d68580e90dc 6552 gnu-standards_2022.03.23-0.1_source.buildinfo Checksums-Sha256: 1e04df695c01f61316bf71874eb86008b33732f0db33cd31b68b91a76613f7bf 2041 gnu-standards_2022.03.23-0.1.dsc f7cd65d222f15195afd6cee6411fd0a598fe2059d83b9a83ff2c1efb94910119 132762 gnu-standards_2022.03.23.orig.tar.gz 6ddb17f2c5797999a7b5b6c65bb2dd567cf92b090530374afb24e49db42f8564 4688 gnu-standards_2022.03.23-0.1.debian.tar.xz ceb920a093b30206be514cedc7607ec9532cabe3dd0a73087426dc8447837e27 6552 gnu-standards_2022.03.23-0.1_source.buildinfo Files: 47e6158d60470b71e7a8c8f285390350 2041 doc optional gnu-standards_2022.03.23-0.1.dsc daa5d9ea7d496a4fe4902615e84b4afc 132762 doc optional gnu-standards_2022.03.23.orig.tar.gz a8938455ebe5d907fc40760265966d40 4688 doc optional gnu-standards_2022.03.23-0.1.debian.tar.xz 6f65e89f4fb89b58960e2c1bd1c2cbc3 6552 doc optional gnu-standards_2022.03.23-0.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmI7NXgQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9VBbD/9RbKJUvFk18eKlpEsIWw04F9cOi6x+0n+o rs1efCuSoQ5WQH1ygG4HhjXOJusarlBJUnsVGMp9mmaNuoNUka44xZlErt8jpaOj 88ltO+XT
Bug#1008171: python-confluent-kafka: FTBFS on big-endian
Source: python-confluent-kafka
Version: 1.7.0-1
Severity: serious
Tags: ftbfs
X-Debbugs-CC: debian-s...@lists.debian.org, ol...@debian.org
Hi Maintainer
Since the upload of 1.7.0-1, python-confluent-kafka FTBFS on s390x and
some other big-endian architectures (e.g. powerpc, ppc64) [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://buildd.debian.org/status/package.php?p=python-confluent-kafka
=== FAILURES ===
__ test_purge __
def test_purge():
"""
Verify that when we have a higher message.timeout.ms timeout,
we can use purge()
to stop waiting for messages and get delivery reports
"""
p = Producer(
{"socket.timeout.ms": 10, "error_cb": error_cb,
"message.timeout.ms": 3}
) # 30 seconds
# Hack to detect on_delivery was called because inner
functions can modify nonlocal objects.
# When python2 support is dropped, we can use the "nonlocal"
keyword instead
cb_detector = {"on_delivery_called": False}
def on_delivery(err, msg):
cb_detector["on_delivery_called"] = True
# Because we are purging messages, we should see a
PURGE_QUEUE kafka error
assert err.code() == KafkaError._PURGE_QUEUE
# Our message won't be delivered, but also won't timeout yet
because our timeout is 30s.
p.produce(topic="some_topic", value="testing", partition=9,
callback=on_delivery)
p.flush(0.002)
assert not cb_detector["on_delivery_called"]
# When in_queue set to false, we won't purge the message and
get delivery callback
p.purge(in_queue=False)
p.flush(0.002)
> assert not cb_detector["on_delivery_called"]
E assert not True
tests/test_Producer.py:267: AssertionError
- Captured stderr call -
%5|1647555748.271|CONFWARN|rdkafka#producer-27| [thrd:app]: No
`bootstrap.servers` configured: client will not be able to connect to
Kafka cluster
=== short test summary info
FAILED tests/test_Producer.py::test_purge - assert not True
=== 1 failed, 61 passed, 4 skipped in 19.19s ===
Bug#1008170: FTBFS: randomly test failures
Package: node-openid Severity: serious Tags: ftbfs Justification: FTBFS node-openid test randomly fails. I added a "trace-warning" in test to see from where comes this failure. node-openid implements OpenID 1.0/1.1/2.0 protocols, all deprecated in favor of OpenID-Connect. This package has no reverse dependencies and looks to be a candidate for removal.
Bug#953530: [Pkg-samba-maint] Bug#953530: samba-common-bin: post-install fails with "lock directory /run/samba does not exist"
23.03.2022 16:38, Diederik de Haas wrote: On woensdag 23 maart 2022 06:54:57 CET Axel Beckert wrote: Gian Piero Carrubba wrote: Init: sysvinit (via /sbin/init) Diederik de Haas wrote: I do not have a /run/samba/ directory on my Bookworm system/server. I don't think it's relevant, but it (still?) has sysv-init as init. I think, I see a pattern here: My three affected hosts have sysvinit, too (on purpose). Yeah, that's a pattern :-) Looking a bit further and I found https://bugs.debian.org/975422 through https://salsa.debian.org/samba-team/samba/-/commit/0c3b2056764cd1a566766c3e1764d7c312eab5d7 titled: "Ensure systemd-tmpfiles is called before testparm (Closes: #975422)" How about just mkdir -p /run/samba at the place of #DEBHELPER# in there ? /mjt
Bug#953530: samba-common-bin: post-install fails with "lock directory /run/samba does not exist"
On woensdag 23 maart 2022 06:54:57 CET Axel Beckert wrote: > Gian Piero Carrubba wrote: > > Init: sysvinit (via /sbin/init) > > Diederik de Haas wrote: > > I do not have a /run/samba/ directory on my Bookworm system/server. > > I don't think it's relevant, but it (still?) has sysv-init as init. > I think, I see a pattern here: My three affected hosts have sysvinit, > too (on purpose). Yeah, that's a pattern :-) Looking a bit further and I found https://bugs.debian.org/975422 through https://salsa.debian.org/samba-team/samba/-/commit/0c3b2056764cd1a566766c3e1764d7c312eab5d7 titled: "Ensure systemd-tmpfiles is called before testparm (Closes: #975422)" This seems highly relevant for this issue. On woensdag 23 maart 2022 06:54:57 CET Axel Beckert wrote: > The reason why this pops up now with multiple people again is probably > that we had a bunch of important kernel updates and hence reboots and > empty /run/ tmpfs after reboot — which brings up this issue again even > if you had created /run/samba/ manually after the previous reboot. My (Xen Dom0) *Bookworm* system/server is somewhat unusual in that it's off most of the time and reboots (or cold boots) happen more regular then what most people expect for a Xen Dom0 system. Not sure what to make of this and whether it's relevant ... Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Bug#1007724: no locking at all
VA, please provide a tested patch against our VCS https://salsa.debian.org/debian/xscreensaver thanks
Bug#1004818: marked as done (os-autoinst: FTBFS: test failure)
Your message dated Wed, 23 Mar 2022 13:11:34 +0100
with message-id
and subject line Re: os-autoinst: FTBFS: test failure
has caused the Debian Bug report #1004818,
regarding os-autoinst: FTBFS: test failure
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.)
--
1004818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: os-autoinst
Version: 4.6.1632799442.f77d4e1-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
os-autoinst FTBFS in unstable:
Start 3: test-perl-testsuite
3: Test command: /<>/tools/invoke-tests "--prove-tool"
"/usr/bin/prove" "--make-tool" "/usr/bin/ninja" "--build-directory"
"/<>/build"
3: Test timeout computed to be: 1000
3: [12:23:12] ./00-compile-check-all.t . ok30351 ms ( 0.05
usr 0.00 sys + 26.74 cusr 3.13 csys = 29.92 CPU)
3: [12:23:13] ./01-test_needle.t ... ok 1246 ms ( 0.02
usr 0.00 sys + 1.28 cusr 0.11 csys = 1.41 CPU)
3: [12:23:14] ./02-test_ocr.t .. ok 707 ms ( 0.00
usr 0.00 sys + 0.73 cusr 0.09 csys = 0.82 CPU)
3: [12:23:14] ./03-testapi.t ... ok 486 ms ( 0.01
usr 0.00 sys + 0.46 cusr 0.02 csys = 0.49 CPU)
3: [12:23:15] ./04-check_vars_docu.t ... ok 77 ms ( 0.00
usr 0.00 sys + 0.07 cusr 0.01 csys = 0.08 CPU)
3: [12:23:15] ./04-testapi-python.t ok 362 ms ( 0.00
usr 0.00 sys + 0.33 cusr 0.02 csys = 0.35 CPU)
3: [12:23:15] ./05-distribution.t .. ok 276 ms ( 0.00
usr 0.00 sys + 0.26 cusr 0.02 csys = 0.28 CPU)
3: Useless use of a constant ("can load python test module at a"...) in void
context at ./08-autotest.t line 342.
3: [37m[2022-02-01T12:23:16.070 UTC] [debug] scheduling test tests/test.py
3: [0m[12:23:16] ./08-autotest.t .. ok 377 ms (
0.01 usr 0.00 sys + 0.35 cusr 0.03 csys = 0.39 CPU)
3: [12:23:17] ./10-terminal.t .. ok 1418 ms ( 0.01
usr 0.00 sys + 0.28 cusr 0.08 csys = 0.37 CPU)
3: [12:23:18] ./10-test-image-conversion-benchmark.t ... ok 1435 ms ( 0.01
usr 0.00 sys + 1.37 cusr 0.06 csys = 1.44 CPU)
3:
[33m[0m[33m[0m[33m[0m[33m[0m[33m[0m[33m[0m[33m[0m[33m[0m[33m[0m[12:23:19]
./10-virtio_terminal.t ... ok 379 ms ( 0.00 usr 0.00 sys
+ 0.32 cusr 0.06 csys = 0.38 CPU)
3: [12:23:19] ./11-image-ppm.t . ok 309 ms ( 0.00
usr 0.00 sys + 0.29 cusr 0.03 csys = 0.32 CPU)
3: [12:23:19] ./12-bmwqemu.t ... ok 248 ms ( 0.00
usr 0.00 sys + 0.23 cusr 0.01 csys = 0.24 CPU)
3: [12:23:20] ./15-logging.t ... ok 234 ms ( 0.00
usr 0.00 sys + 0.22 cusr 0.02 csys = 0.24 CPU)
3: [12:23:20] ./16-send_with_fd.t .. ok 320 ms ( 0.00
usr 0.00 sys + 0.27 cusr 0.05 csys = 0.32 CPU)
3: [12:23:20] ./17-basetest.t .. ok 298 ms ( 0.00
usr 0.00 sys + 0.28 cusr 0.03 csys = 0.31 CPU)
3: [12:23:22] ./18-qemu.t .. ok 1382 ms ( 0.01
usr 0.00 sys + 0.29 cusr 0.09 csys = 0.39 CPU)
3: [12:23:22] ./19-isotovideo-command-processing.t . ok 298 ms ( 0.00
usr 0.00 sys + 0.27 cusr 0.03 csys = 0.30 CPU)
3: [12:23:22] ./20-openqa-benchmark-stopwatch-utils.t .. ok 117 ms ( 0.00
usr 0.00 sys + 0.09 cusr 0.03 csys = 0.12 CPU)
3:
3: # Failed test 'no (unexpected) warnings (via done_testing)'
3: # at ./21-needle-downloader.t line 126.
3: # Got the following unexpected warnings:
3: # 1: Mojo::Reactor::Poll: Timer failed: Label not found for "last
T2_SUBTEST_WRAPPER" at /usr/share/perl/5.32/Test2/Hub/Subtest.pm line 67.
3: # Looks like you failed 1 test of 5.
3: [12:23:40] ./21-needle-downloader.t .
3: Dubious, test returned 1 (wstat 256, 0x100)
3: Failed 1/5 subtests
3: [12:23:40] ./22-svirt.t . ok 457 ms ( 0.01
usr 0.01 sys + 0.41 cusr 0.06 csys = 0.49 CPU)
3: [12:23:41] ./23-baseclass.t . ok 292 ms ( 0.00
usr 0.00 sys + 0.23 cusr 0.06 csys = 0.29 CPU)
3: [12:23:41] ./24-myjsonrpc-debug.t ... ok 231 ms ( 0.01
usr 0.00 sys + 0.22 cusr 0.01 csys = 0.24 CPU)
3: [12:23:41] ./24-myjsonrpc.t . ok 233 ms ( 0.00
usr 0.00 sys + 0.23 cusr 0.01 csys = 0.24 CPU)
3: [12:23:41] ./25-spvm.t .. o
Bug#997410: marked as done (libtemplates-parser: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.')
Your message dated Wed, 23 Mar 2022 12:00:13 +
with message-id
and subject line Bug#997410: fixed in libtemplates-parser 22.0.0-1
has caused the Debian Bug report #997410,
regarding libtemplates-parser: FTBFS: '! LaTeX Error: File `tgtermes.sty' not
found.'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtemplates-parser
Version: 21.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/docs/build/latex'
> latexmk -pdf -dvi- -ps- 'templates_parser.tex'
> Rc files read:
> /etc/LatexMk
> latexmkrc
> Latexmk: This is Latexmk, John Collins, 21 September 2021, version: 4.75.
> Rule 'pdflatex': File changes, etc:
>Changed files, or newly in use since previous run(s):
> 'templates_parser.tex'
>
> Run number 1 of rule 'pdflatex'
>
>
> Running 'pdflatex -interaction=nonstopmode -recorder "templates_parser.tex"'
>
> Latexmk: applying rule 'pdflatex'...
> This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian)
> (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> (./templates_parser.tex
> LaTeX2e <2021-06-01> patch level 1
> L3 programming layer <2021-08-27> (./sphinxmanual.cls
> Document Class: sphinxmanual 2019/12/01 v2.3.0 Document class (Sphinx manual)
> (/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
> Document Class: report 2021/02/12 v1.4n Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/cmap/cmap.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty<>)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def))
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf))
>
> ! LaTeX Error: File `tgtermes.sty' not found.
>
> Type X to quit or to proceed,
> or enter new name. (Default extension: sty)
>
> Enter file name:
> ! Emergency stop.
>
>
> l.37 \usepackage
> {tgheros}^^M
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on templates_parser.log.
> Latexmk: Missing input file 'tgtermes.sty' (or dependence on it) from
> following:
> '! LaTeX Error: File `tgtermes.sty' not found.'
> Collected error summary (may duplicate other messages):
> pdflatex: Command for 'pdflatex' gave return code 1
> Refer to 'templates_parser.log' for details
> Latexmk: Use the -f option to force complete processing,
> unless error was exceeding maximum runs, or warnings treated as errors.
> Latexmk: Examining 'templates_parser.log'
> === TeX engine is 'pdfTeX'
> Latexmk: Errors, so I did not complete making targets
> make[4]: *** [Makefile:29: templates_parser.pdf] Error 12
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/libtemplates-parser_21.0.0-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you 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: libtemplates-parser
Source-Version: 22.0.0-1
Done: Nicolas Boulenguez
We believe that the bug you reported is fixed in the latest version of
libtemplates-parser, which is due to b
Bug#997445: marked as done (libaunit: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.')
Your message dated Wed, 23 Mar 2022 12:00:10 +
with message-id
and subject line Bug#997445: fixed in libaunit 22.0.0-1
has caused the Debian Bug report #997445,
regarding libaunit: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libaunit
Version: 21.0.0.fa386849-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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 '/<>/doc/build/aunit_cb/pdf'
> latexmk -pdf -dvi- -ps- 'aunit_cb.tex'
> Rc files read:
> /etc/LatexMk
> latexmkrc
> Latexmk: This is Latexmk, John Collins, 21 September 2021, version: 4.75.
> Rule 'pdflatex': File changes, etc:
>Changed files, or newly in use since previous run(s):
> 'aunit_cb.tex'
>
> Run number 1 of rule 'pdflatex'
>
>
> Running 'pdflatex -interaction=nonstopmode -recorder "aunit_cb.tex"'
>
> Latexmk: applying rule 'pdflatex'...
> This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian)
> (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> (./aunit_cb.tex
> LaTeX2e <2021-06-01> patch level 1
> L3 programming layer <2021-08-27> (./sphinxmanual.cls
> Document Class: sphinxmanual 2019/12/01 v2.3.0 Document class (Sphinx manual)
> (/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
> Document Class: report 2021/02/12 v1.4n Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/cmap/cmap.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty<>)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def))
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf))
>
> ! LaTeX Error: File `tgtermes.sty' not found.
>
> Type X to quit or to proceed,
> or enter new name. (Default extension: sty)
>
> Enter file name:
> ! Emergency stop.
>
>
> l.37 \usepackage
> {tgheros}^^M
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on aunit_cb.log.
> Latexmk: Missing input file 'tgtermes.sty' (or dependence on it) from
> following:
> '! LaTeX Error: File `tgtermes.sty' not found.'
> Collected error summary (may duplicate other messages):
> pdflatex: Command for 'pdflatex' gave return code 1
> Refer to 'aunit_cb.log' for details
> Latexmk: Use the -f option to force complete processing,
> unless error was exceeding maximum runs, or warnings treated as errors.
> Latexmk: Examining 'aunit_cb.log'
> === TeX engine is 'pdfTeX'
> Latexmk: Errors, so I did not complete making targets
> make[3]: *** [Makefile:29: aunit_cb.pdf] Error 12
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/libaunit_21.0.0.fa386849-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you 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: libaunit
Source-Version: 22.0.0-1
Done: Nicolas Boulenguez
We believe that the bug you reported is fixed in the latest version of
libaunit, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one
Bug#1005858: gh,gitsome: File conflict, both ship /usr/bin/gh
Quoting Anthony Fok (2022-03-23 11:08:36) > Rather than keeping this "Serious" bug open and keeping both gitsome > and gh out of Debian testing, I think the simple solution of having gh > "Conflicts: gitsome", which is one of the option specified in > https://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts, > would suffice for now, allowing both packages to (re-)enter testing in > the meantime. > > SZ, if you think the use of alternatives (such that both the gitsome > and gh packages can be installed simultaneously) is a better solution, > I'd be happy to work something out with you too. Please note that above Policy section covers only the functionality of that packaging hint, not its suitability. It is my understanding that both that specific use of Conflicts and the use of alternatives is only acceptable for executables providing same or at least largely overlapping) ABI. Do gitsome and gh provide same or quite similar ABI? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1008148: marked as done (esdm: missing Build-Depends: cmake)
Your message dated Wed, 23 Mar 2022 11:33:52 + with message-id and subject line Bug#1008148: fixed in esdm 1.0-2 has caused the Debian Bug report #1008148, regarding esdm: missing Build-Depends: cmake 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.) -- 1008148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: esdm Version: 1.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source esdm FTBFS in a minimal buildd chroot: https://buildd.debian.org/status/fetch.php?pkg=esdm&arch=arm64&ver=1.0-1&stamp=1645887435&raw=0 debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- -DPLANTUML_JAR_PATH=/usr/share/plantuml -DBACKEND_KDSA_DUMMY=On -DBACKEND_PMEM=On -DBACKEND_S3=Off -DENABLE_HDF5=On -DENABLE_MPI=On -DBACKEND_POSIX=On install -d /<>/debian/.debhelper/generated/_source/home install -d debian/build cd debian/build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/aarch64-linux-gnu -DPLANTUML_JAR_PATH=/usr/share/plantuml -DBACKEND_KDSA_DUMMY=On -DBACKEND_PMEM=On -DBACKEND_S3=Off -DENABLE_HDF5=On -DENABLE_MPI=On -DBACKEND_POSIX=On ../.. Can't exec "cmake": No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 523. dh_auto_configure: error: cd debian/build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/aarch64-linux-gnu -DPLANTUML_JAR_PATH=/usr/share/plantuml -DBACKEND_KDSA_DUMMY=On -DBACKEND_PMEM=On -DBACKEND_S3=Off -DENABLE_HDF5=On -DENABLE_MPI=On -DBACKEND_POSIX=On ../.. failed to execute: No child processes dh_auto_configure: error: cd debian/build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/aarch64-linux-gnu -DPLANTUML_JAR_PATH=/usr/share/plantuml -DBACKEND_KDSA_DUMMY=On -DBACKEND_PMEM=On -DBACKEND_S3=Off -DENABLE_HDF5=On -DENABLE_MPI=On -DBACKEND_POSIX=On ../.. returned exit code 2 make[1]: *** [debian/rules:26: override_dh_auto_configure] Error 2 make[1]: Leaving directory '/<>' Maybe more B-D than just cmake are missing, I haven't tested that. Andreas --- End Message --- --- Begin Message --- Source: esdm Source-Version: 1.0-2 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of esdm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated esdm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 23 Mar 2022 10:30:43 + Source: esdm Binary: esdm-tools esdm-tools-dbgsym libesdm-dev libesdm-dev-dbgsym libesdm0d libesdm0d-dbgsym Architecture: source amd64 Version: 1.0-2 Distribution: experimental Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: esdm-tools - Earth System Data Middleware libesdm-dev - Earth System Data Middleware - devel files libesdm0d - Earth System Data Middleware - libraries Closes: 1008148 Changes: esdm (1.0-2) experimental; urgency=medium . * Add cmake a
Bug#1008139: marked as done (FTBFS: fail to build with nodejs >= 14)
Your message dated Wed, 23 Mar 2022 11:24:32 +
with message-id
and subject line Bug#1008139: fixed in node-evp-bytestokey 1.0.3-11
has caused the Debian Bug report #1008139,
regarding FTBFS: fail to build with nodejs >= 14
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.)
--
1008139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-evp-bytestokey
Version: 1.0.3-10
Severity: serious
Tags: ftbfs
Justification: FTBFS
Hi,
node-evp-bytestokey fails to build with libnode-dev >= 14. See
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-evp-bytestokey/20258806/log.gz
--- 8< ---
../test/main.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE
md5_key32_iv16(Nan::NAN_METHOD_ARGS_TYPE)’:
../test/main.cc:28:11: error: no matching function for call to
‘v8::Object::Set(v8::Local, v8::Local)’
28 | obj->Set(Nan::New("key").ToLocalChecked(),
Nan::CopyBuffer((const char*) key, 32).ToLocalChecked());
|
^~~
In file included from /usr/include/nodejs/src/node.h:67,
from ../test/main.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h:3670:37: note: candidate:
‘v8::Maybe v8::Object::Set(v8::Local, v8::Local,
v8::Local)’
3670 | V8_WARN_UNUSED_RESULT Maybe Set(Local context,
| ^~~
/usr/include/nodejs/deps/v8/include/v8.h:3670:37: note: candidate expects 3
arguments, 2 provided
/usr/include/nodejs/deps/v8/include/v8.h:3673:37: note: candidate:
‘v8::Maybe v8::Object::Set(v8::Local, uint32_t,
v8::Local)’
3673 | V8_WARN_UNUSED_RESULT Maybe Set(Local context,
uint32_t index,
[...]
--- >8 ---
--- End Message ---
--- Begin Message ---
Source: node-evp-bytestokey
Source-Version: 1.0.3-11
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-evp-bytestokey, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1008...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated node-evp-bytestokey package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 23 Mar 2022 12:07:38 +0100
Source: node-evp-bytestokey
Architecture: source
Version: 1.0.3-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Closes: 1008139
Changes:
node-evp-bytestokey (1.0.3-11) unstable; urgency=medium
.
* Team upload
* Drop test, incompatible with nodejs >= 14 (Closes: #1008139)
* Use dh-sequence-nodejs auto install
Checksums-Sha1:
9f15e6a4950b19a6ab324a966dfa89517448ad14 2164 node-evp-bytestokey_1.0.3-11.dsc
265600441057ce367d0f616858318c8c8f537da3 3408
node-evp-bytestokey_1.0.3-11.debian.tar.xz
Checksums-Sha256:
92fef6b27bea8811f936585c00e0e06339d8cafdba3a01419d0a00f28c916d25 2164
node-evp-bytestokey_1.0.3-11.dsc
a514222c1be6596ea78fcd15b30bcfbd75da5049f6416ce5fa407cdb2ab90e95 3408
node-evp-bytestokey_1.0.3-11.debian.tar.xz
Files:
745d1c84c3ab4f11bcbe037a8ed24615 2164 javascript optional
node-evp-bytestokey_1.0.3-11.dsc
f31df633d05dbae8177cccb0ce5d5efc 3408 javascript optional
node-evp-bytestokey_1.0.3-11.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI6/9UACgkQ9tdMp8mZ
7ule3g/+M/B+UZBJpMqTQTiSR+NTn7GMm1O8X5+uI6yJ96jB0d4j3R3D51YwxGCk
xkn/i2cOxgEzD4fdAThSsPvqf8Q7ocVH3QqsaCXWtct73kJZFIS9OufcssMZfIwU
Vbtl8R8gOpvdgDSV3r2dyfPAYdBtcto6/2UI07aX6R1ZoW7qWG8Ie4PgvUWEdKmj
Js0JZIRA2MMeHQ5afGfj+fVYe1VJKrLVPY2QSVTU6yH6gkXgBvtpJ3sTitZeCBda
a2kx9MFlJSL6ROQWM8Kc08Omza7BLXP3KEFY+yGYOTzMMSTUYG32DfkKB+8jIuyn
m0oG89cv88frHbsMvguWSz0LvSFLjoDkeSPY5siWPrejOLvji8nIcqHjrSo/c/ov
Xy8aIMC/1M80N9ADRKQfivEqPdLmufWixwlF11j7RmZfnNEkVgQm7tuYVybJ+5Pr
zHLEC0LmZulwMWH18PW+s0OYhvW7SeyAOHn/j5WpQIZWOvfeXQKoU/cWlIB7ni6z
6taD+lcoSIBvl2cj/R7A0qxghKY7KTcakkBkoGiSoI3LKZPORWGTf7T+/iEQjEpI
tWorr0kocNDmubZVcQuRi8wYD4gPmIoc4hTaVg+mZ+0vZaG1YnqqQVYlB4sYfXVS
WyLI0trBONF2q3m4v6FeOlQ8r2fBclFrQ+wzmwSCRXCukRcOn6E=
=TIy7
-END PGP SIGNATURE End Message ---
Processed: Bug#1008139 marked as pending in node-evp-bytestokey
Processing control commands: > tag -1 pending Bug #1008139 [node-evp-bytestokey] FTBFS: fail to build with nodejs >= 14 Added tag(s) pending. -- 1008139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008139: marked as pending in node-evp-bytestokey
Control: tag -1 pending Hello, Bug #1008139 in node-evp-bytestokey reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-evp-bytestokey/-/commit/048d2652a527f2fef062436842141cd6b30810ac Drop test, incompatible with nodejs >= 14 Closes: #1008139 (this message was generated automatically) -- Greetings https://bugs.debian.org/1008139
Bug#1005858: marked as done (gh,gitsome: File conflict, both ship /usr/bin/gh)
Your message dated Wed, 23 Mar 2022 10:33:57 + with message-id and subject line Bug#1005858: fixed in gh 2.4.0+dfsg1-2 has caused the Debian Bug report #1005858, regarding gh,gitsome: File conflict, both ship /usr/bin/gh 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.) -- 1005858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gh,gitsome Severity: serious Control: found -1 gitsome/0.8.0+ds-6 Control: found -1 gh/2.4.0+dfsg1-1 Hi, installing gh fails for me as follows: Unpacking gh (2.4.0+dfsg1-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-DkqFj5/24-gh_2.4.0+dfsg1-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/gh', which is also in package gitsome 0.8.0+ds-6 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: gh Source-Version: 2.4.0+dfsg1-2 Done: Anthony Fok We believe that the bug you reported is fixed in the latest version of gh, 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 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anthony Fok (supplier of updated gh package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 23 Mar 2022 04:10:32 -0600 Source: gh Architecture: source Version: 2.4.0+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Anthony Fok Closes: 1005858 Changes: gh (2.4.0+dfsg1-2) unstable; urgency=medium . * Add "Conflicts: gitsome" which also provides /usr/bin/gh. Thanks to Axel Beckert for the bug report. (Closes: #1005858) * Source-only upload for migration to testing Checksums-Sha1: 9f5763d080e115d65c0eca8c652ff371b61ba724 3914 gh_2.4.0+dfsg1-2.dsc 9c45336cf61d68d7c222eb87dca6684a833db80f 938968 gh_2.4.0+dfsg1-2.debian.tar.xz 9a208f4b967af6643fc87fd25f4c737edf94d18b 12737 gh_2.4.0+dfsg1-2_amd64.buildinfo Checksums-Sha256: 2b401025edcd9fe39235ca256013c96e640fbae309964802ae472ab57908191e 3914 gh_2.4.0+dfsg1-2.dsc 98d6e213277b552ffe614bfeef3fc518b84fff8747b2546cbcced187824cce66 938968 gh_2.4.0+dfsg1-2.debian.tar.xz 88c9dbad32e9fddce753b6d65d46265d172415974569617ab5fed56ff150bafa 12737 gh_2.4.0+dfsg1-2_amd64.buildinfo Files: 4744828efa180c2c7ea53206d2587ffc 3914 golang optional gh_2.4.0+dfsg1-2.dsc 4e4e5f8a990556bdf9e607c1a2179ce1 938968 golang optional gh_2.4.0+dfsg1-2.debian.tar.xz 6e3f19ea948f34d880ce7e3f1be94a18 12737 golang optional gh_2.4.0+dfsg1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAmI69EwQHGZva2FAZGVi aWFuLm9yZwAKCRDqJQC0EsWazyVHD/9o46STw0EEqfl9GkGKGmVuM6xj2Pwu1cqp FlrRLm6BD/oDRmgzscBVWm03EDGvco6KXjM+8drCceJuxtu20WHavc2llWLpSZ2r crlu93xVwxPIi7I0Xno4aKn4ZfrPNbJVCnfh+N4AcYx//7ci/hSGuM2YCCfwkLPM +dvyfzfO2c4I57bs2zgobDR+6frCFMAXnQRdFXrvi8uXJ18igekMSWO9MXuHiKyL 7N64J7EyUuueXJmqM9pemxCrbA7vVxJmGtTebcCyaRQWBuEoNpz9eyi7kGhwHm5W h0SSGuDLASdzc0PDYnmOEeh1aHhuCljIV8SeSlb4c7nYsFpBn9Q/Ufq8qY60Lsn0 ikHakQ5VLGCgxUvoHjtsQNLevQQRBDhPsLtrmqG/oZgcZtGDe388rUlBj63QRfBM 7FrAD4xJSSv1ShQtLytE3sz1gzr2Yu9KI3Kjt3hjlL/jFH7kE17zYGxqEWKN1rMZ m72rJmK+B8aHVrty2K44YnV2Ud6//QxNcp38M5qJfY9l/LKQjGoSPxH0rSHQZZxd VIFM2Aywx3/ejBWRBmMAxBZDUXlXqtDwL14MQtqdD+Sot2xah1HZ1X4Qw2+36Wz7 WFYsbJR9s8/e3GapAVjn2KdpYkxXW4drOe+ezFATSM2KBu9HZowIR+oV1bvLtv8u H2E+nVkpAg== =ua9V -END PGP SIGNATURE End Message ---
Bug#1005858: marked as pending in gh
Control: tag -1 pending Hello, Bug #1005858 in gh reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/gh/-/commit/ddd2a18bd88467d4587816bab74ff7341faf5562 Add "Conflicts: gitsome" which also provides /usr/bin/gh Thanks: Axel Beckert for the bug report. Closes: #1005858 (this message was generated automatically) -- Greetings https://bugs.debian.org/1005858
Processed: Bug#1005858 marked as pending in gh
Processing control commands: > tag -1 pending Bug #1005858 [gh,gitsome] gh,gitsome: File conflict, both ship /usr/bin/gh Added tag(s) pending. -- 1005858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008152: gprbuild: FTBFS during binary-indep build
Source: gprbuild Version: 2022.0.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, gprbuild/experimental FTBFS during a binary-indep build. (A combined binary build works fine as does a binary-arch build.) [...] looking for now-outdated files... Extension error (sphinx.environment.collectors.toctree): Handler > for event 'env-get-updated' threw an exception (exception: invalid load key, '\x00'.) looking for now-outdated files... looking for now-outdated files... make[2]: *** [Makefile:48: pdf] Error 2 make[2]: *** Waiting for unfinished jobs [...] Andreas gprbuild_2022.0.0-1_indep.log.gz Description: application/gzip
Bug#1005858: gh,gitsome: File conflict, both ship /usr/bin/gh
Hi everyone, On Sat, Feb 26, 2022 at 7:09 PM Paul Wise wrote: > > Control: forwarded -1 https://github.com/donnemartin/gitsome/issues/177 > > On Sat, 26 Feb 2022 23:43:14 +0800 SZ Lin (林上智) wrote: > > > The "gitsome" has used "gh" since 2017, and thus would you mind renaming > > the "gh" in your package to avoid the conflict issue? > > Since gh is the official GitHub client, probably it should retain "gh" > and gitsome should move to "git some" or similar, as I have suggested > in the above upstream issue. The only commentor there agreed with me. Thank you all for the discussion and attempt at resolving the filename conflict. Judging from gitsome's GitHub repo being left stagnant since May 2019, with Issues and PRs unanswered, despite the fact that upstream author is still active daily on GitHub, I doubt we'll see a reply from gitsome's author anytime soon. Automation scripts are relying on the GitHub CLI command to be named as "gh", so renaming /usr/bin/gh in "gh" to something else is out of the question too. Rather than keeping this "Serious" bug open and keeping both gitsome and gh out of Debian testing, I think the simple solution of having gh "Conflicts: gitsome", which is one of the option specified in https://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts, would suffice for now, allowing both packages to (re-)enter testing in the meantime. SZ, if you think the use of alternatives (such that both the gitsome and gh packages can be installed simultaneously) is a better solution, I'd be happy to work something out with you too. Cheers, Anthony
Bug#1008150: libgrpc-dev: library name conflict with libupb-dev: libupb.so*
Package: libgrpc-dev Version: 1.44.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../libgrpc-dev_1.44.0-1_amd64.deb ... Unpacking libgrpc-dev:amd64 (1.44.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libgrpc-dev_1.44.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libupb.so', which is also in package libupb-dev:amd64 0.0.0~git200730-1 Errors were encountered while processing: /var/cache/apt/archives/libgrpc-dev_1.44.0-1_amd64.deb upb and grpc seem to be two unrelated projects, unfortunately grpc/experimental started to use a library name already used by upb. They use different SOVERSIONs right now, so the conflict is only on the .so link. Adding mutual Conflicts is not a valid solution here! cheers, Andreas libupb-dev=0.0.0~git200730-1_libgrpc-dev=1.44.0-1.log.gz Description: application/gzip
Bug#1008148: esdm: missing Build-Depends: cmake
Package: esdm Version: 1.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source esdm FTBFS in a minimal buildd chroot: https://buildd.debian.org/status/fetch.php?pkg=esdm&arch=arm64&ver=1.0-1&stamp=1645887435&raw=0 debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' dh_auto_configure -- -DPLANTUML_JAR_PATH=/usr/share/plantuml -DBACKEND_KDSA_DUMMY=On -DBACKEND_PMEM=On -DBACKEND_S3=Off -DENABLE_HDF5=On -DENABLE_MPI=On -DBACKEND_POSIX=On install -d /<>/debian/.debhelper/generated/_source/home install -d debian/build cd debian/build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/aarch64-linux-gnu -DPLANTUML_JAR_PATH=/usr/share/plantuml -DBACKEND_KDSA_DUMMY=On -DBACKEND_PMEM=On -DBACKEND_S3=Off -DENABLE_HDF5=On -DENABLE_MPI=On -DBACKEND_POSIX=On ../.. Can't exec "cmake": No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 523. dh_auto_configure: error: cd debian/build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/aarch64-linux-gnu -DPLANTUML_JAR_PATH=/usr/share/plantuml -DBACKEND_KDSA_DUMMY=On -DBACKEND_PMEM=On -DBACKEND_S3=Off -DENABLE_HDF5=On -DENABLE_MPI=On -DBACKEND_POSIX=On ../.. failed to execute: No child processes dh_auto_configure: error: cd debian/build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/aarch64-linux-gnu -DPLANTUML_JAR_PATH=/usr/share/plantuml -DBACKEND_KDSA_DUMMY=On -DBACKEND_PMEM=On -DBACKEND_S3=Off -DENABLE_HDF5=On -DENABLE_MPI=On -DBACKEND_POSIX=On ../.. returned exit code 2 make[1]: *** [debian/rules:26: override_dh_auto_configure] Error 2 make[1]: Leaving directory '/<>' Maybe more B-D than just cmake are missing, I haven't tested that. Andreas
Bug#1007734: marked as done (golang-github-alecthomas-chroma breaks golang-github-niklasfasching-go-org autopkgtest: hashes do not match)
Your message dated Wed, 23 Mar 2022 03:25:18 -0600 with message-id and subject line Bug#1007734: fixed in golang-github-niklasfasching-go-org 1.6.2-1 has caused the Debian Bug report #1007734, regarding golang-github-alecthomas-chroma breaks golang-github-niklasfasching-go-org autopkgtest: hashes do not match 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.) -- 1007734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-alecthomas-chroma, golang-github-niklasfasching-go-org Control: found -1 golang-github-alecthomas-chroma/0.10.0-1 Control: found -1 golang-github-niklasfasching-go-org/1.6.0-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of golang-github-alecthomas-chroma the autopkgtest of golang-github-niklasfasching-go-org fails in testing when that autopkgtest is run with the binary packages of golang-github-alecthomas-chroma from unstable. It passes when run with only packages from testing. In tabular form: passfail golang-github-alecthomas-chroma from testing0.10.0-1 golang-github-niklasfasching-go-org from testing1.6.0-1 all othersfrom testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of golang-github-alecthomas-chroma to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=golang-github-alecthomas-chroma https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-niklasfasching-go-org/19989847/log.gz === RUN TestBlorg config_test.go:39: PublicDir hashes do not match: 'ab73939658896f4b21a1486bd7862751 -' -> '0add254dc2d8cb398cb9b9dc9e495e85 -' --- FAIL: TestBlorg (0.04s) FAIL FAILgithub.com/niklasfasching/go-org/blorg 0.059s === RUN TestHTMLWriter html_writer_test.go:30: testdata/blocks.org: passed! html_writer_test.go:30: testdata/captions.org: passed! html_writer_test.go:30: testdata/east_asian_line_breaks.org: passed! html_writer_test.go:30: testdata/footnotes.org: passed! html_writer_test.go:30: testdata/footnotes_in_headline.org: passed! html_writer_test.go:30: testdata/headlines.org: passed! html_writer_test.go:30: testdata/inline.org: passed! html_writer_test.go:30: testdata/keywords.org: passed! html_writer_test.go:30: testdata/latex.org: passed! html_writer_test.go:30: testdata/lists.org: passed! html_writer_test.go:30: testdata/misc.org: passed! html_writer_test.go:30: testdata/options.org: passed! html_writer_test.go:30: testdata/paragraphs.org: passed! html_writer_test.go:30: testdata/tables.org: passed! --- PASS: TestHTMLWriter (0.01s) === RUN TestExtendedHTMLWriter --- PASS: TestExtendedHTMLWriter (0.00s) === RUN TestPrettyRelativeLinks === RUN TestPrettyRelativeLinks/[[file:/hello.org]] === RUN TestPrettyRelativeLinks/[[file:hello.org]] === RUN TestPrettyRelativeLinks/[[http://hello.org]] === RUN TestPrettyRelativeLinks/[[/foo.png]] === RUN TestPrettyRelativeLinks/[[foo.png]] === RUN TestPrettyRelativeLinks/[[/foo.png][foo]] === RUN TestPrettyRelativeLinks/[[/hello.org][hello]] === RUN TestPrettyRelativeLinks/[[hello.org][hello]] === RUN TestPrettyRelativeLinks/[[foo.png][foo]] --- PASS: TestPrettyRelativeLinks (0.00s) --- PASS: TestPrettyRelativeLinks/[[file:/hello.org]] (0.00s) --- PASS: TestPrettyRelativeLinks/[[file:hello.org]] (0.00s) --- PASS: TestPrettyRelativeLinks/[[http://hello.org]] (0.00s) --- PASS: TestPrettyRelativeLinks/[[/foo.png]] (0.00s) --- PASS: TestPrettyRelativeLinks/[[foo.png]] (0.00s) --- PASS: TestPrettyRelativeLinks/[[/foo.png][foo]] (0.00s) --- PASS: TestPrettyRelativeLinks/[[/hello.org][hello]] (0.00s) --- PASS: TestPrettyRelativeLinks/[[hello.org][hello]] (0.00s) --- PASS: TestPrettyRelativeLinks/[[foo.png][foo]] (0.00s) === RUN TestOrgWriter org_writer_test.go:35: testdata/blocks.org: passed! org_writer_test.go:35: testdata/captions.org: passed! org_writer_test.go:35: testdata/east_asian_line_breaks.o
Bug#1008141: marked as done (FTBFS: unable to use iconv with nodejs >= 14)
Your message dated Wed, 23 Mar 2022 10:07:09 +0100 with message-id <8301f7c6-beeb-a264-3b24-5d43a5541...@debian.org> and subject line Re: [Pkg-javascript-devel] Bug#1008141: FTBFS: unable to use iconv with nodejs >= 14 has caused the Debian Bug report #1008141, regarding FTBFS: unable to use iconv with nodejs >= 14 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.) -- 1008141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nodejs Version: 16.13.2+really14.19.1~dfsg-5 Severity: serious Tags: ftbfs Justification: FTBFS During node-iconv rebuild, test fails: node --trace-uncaught test/run-tests.js internal/util/comparisons.js:386 memos.val1.delete(val1); ^^ SyntaxError: Unexpected token 'delete' Thrown at: at compileForInternalLoader (internal/bootstrap/loaders.js:285:18) at nativeModuleRequire (internal/bootstrap/loaders.js:315:14) at lazyLoadComparison (assert.js:78:22) at deepEqual (assert.js:468:34) at /tmp/tt/node_modules/iconv/test/test-basic.js:44:8 at Module._compile (internal/modules/cjs/loader.js:1085:14) at Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) at Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) Error is not related to node-iconv build: you can reproduce the problem using upstream build: $ npm i iconv $ cd node_modules/iconv $ node --trace-uncaught test/run-tests.js [ same error ] --- End Message --- --- Begin Message --- Fixed during transition, sorry for the noise On 23/03/2022 09:29, Yadd wrote: Package: nodejs Version: 16.13.2+really14.19.1~dfsg-5 Severity: serious Tags: ftbfs Justification: FTBFS During node-iconv rebuild, test fails: node --trace-uncaught test/run-tests.js internal/util/comparisons.js:386 memos.val1.delete(val1); ^^ SyntaxError: Unexpected token 'delete' Thrown at: at compileForInternalLoader (internal/bootstrap/loaders.js:285:18) at nativeModuleRequire (internal/bootstrap/loaders.js:315:14) at lazyLoadComparison (assert.js:78:22) at deepEqual (assert.js:468:34) at /tmp/tt/node_modules/iconv/test/test-basic.js:44:8 at Module._compile (internal/modules/cjs/loader.js:1085:14) at Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) at Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) Error is not related to node-iconv build: you can reproduce the problem using upstream build: $ npm i iconv $ cd node_modules/iconv $ node --trace-uncaught test/run-tests.js [ same error ] --- End Message ---
Bug#1008141: [Pkg-javascript-devel] Bug#1008141: Bug#1008141: FTBFS: unable to use iconv with nodejs >= 14
Quoting Yadd (2022-03-23 09:44:42) > Similar error found with node-sqlite3: Please mark the bugreport with "affects" in posts like the above. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1008141: [Pkg-javascript-devel] Bug#1008141: FTBFS: unable to use iconv with nodejs >= 14
On 23/03/2022 09:29, Yadd wrote: Package: nodejs Version: 16.13.2+really14.19.1~dfsg-5 Severity: serious Tags: ftbfs Justification: FTBFS During node-iconv rebuild, test fails: node --trace-uncaught test/run-tests.js internal/util/comparisons.js:386 memos.val1.delete(val1); Similar error found with node-sqlite3: + mocha -R spec --timeout 48 test/*.js Exception in PromiseRejectCallback: internal/process/promises.js:135 maybeUnhandledPromises.delete(promise); ^^ SyntaxError: Unexpected token 'delete'
Bug#1008141: [Pkg-javascript-devel] Bug#1008141: FTBFS: unable to use iconv with nodejs >= 14
On 23/03/2022 09:44, Yadd wrote: On 23/03/2022 09:29, Yadd wrote: Package: nodejs Version: 16.13.2+really14.19.1~dfsg-5 Severity: serious Tags: ftbfs Justification: FTBFS During node-iconv rebuild, test fails: node --trace-uncaught test/run-tests.js internal/util/comparisons.js:386 memos.val1.delete(val1); Similar error found with node-sqlite3: + mocha -R spec --timeout 48 test/*.js Exception in PromiseRejectCallback: internal/process/promises.js:135 maybeUnhandledPromises.delete(promise); ^^ SyntaxError: Unexpected token 'delete' Similar error with node-websocket: + tape test/unit/dropBeforeAccept.js test/unit/regressions.js test/unit/request.js test/unit/w3cwebsocket.js test/unit/websocketFrame.js TAP version 13 # Drop TCP Connection Before server accepts the request internal/cluster/master.js:168 handles.delete(key); ^^ SyntaxError: Unexpected token 'delete'
Bug#1008140: marked as done (mocha: Incompatible with current node-chai)
Your message dated Wed, 23 Mar 2022 08:34:12 +
with message-id
and subject line Bug#1008140: fixed in node-chai 4.3.6~ds1+~cs9.7.12-3
has caused the Debian Bug report #1008140,
regarding mocha: Incompatible with current node-chai
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.)
--
1008140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mocha
Version: 9.2.2+ds1+~cs28.3.8-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
During node-esquery rebuild, mocha fails:
undefined ERROR: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath
'./register-assert' is not defined by "exports" in
/usr/share/node_modules/chai/package.json imported from
/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js
at new NodeError (internal/errors.js:322:7)
at throwExportsNotFound (internal/modules/esm/resolve.js:332:9)
at packageExportsResolve (internal/modules/esm/resolve.js:523:7)
at packageResolve (internal/modules/esm/resolve.js:721:14)
at moduleResolve (internal/modules/esm/resolve.js:773:18)
at Loader.defaultResolve [as _resolve]
(internal/modules/esm/resolve.js:887:11)
at Loader.resolve (internal/modules/esm/loader.js:89:40)
at Loader.getModuleJob (internal/modules/esm/loader.js:242:28)
at Loader.import (internal/modules/esm/loader.js:177:28)
at importModuleDynamically (internal/modules/cjs/loader.js:1028:27)
at exports.importModuleDynamicallyCallback
(internal/process/esm_loader.js:30:14)
at formattedImport (/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:30:3)
at exports.requireOrImport
(/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:48:38)
at exports.handleRequires
(/usr/share/nodejs/mocha/lib/cli/run-helpers.js:94:34)
at async /usr/share/nodejs/mocha/lib/cli/run.js:353:25 {
code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}
--- End Message ---
--- Begin Message ---
Source: node-chai
Source-Version: 4.3.6~ds1+~cs9.7.12-3
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-chai, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1008...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated node-chai package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 23 Mar 2022 09:15:31 +0100
Source: node-chai
Architecture: source
Version: 4.3.6~ds1+~cs9.7.12-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Closes: 1008140
Changes:
node-chai (4.3.6~ds1+~cs9.7.12-3) unstable; urgency=medium
.
* Team upload
* Explicitely export registers also for .mjs (Closes: #1008140)
Checksums-Sha1:
80a2427382b454200ea56ffe595603c1794b9bc9 3750
node-chai_4.3.6~ds1+~cs9.7.12-3.dsc
afd17f93b0610c36f3fa521a365bf370bc7f2a34 6728
node-chai_4.3.6~ds1+~cs9.7.12-3.debian.tar.xz
Checksums-Sha256:
3004aad5117eb75d278c44459f954b51c2c0d254758c22b61252333c9afde1e3 3750
node-chai_4.3.6~ds1+~cs9.7.12-3.dsc
533d2ac648978fe05c78fa37c8de7433f44d2df5ee5bd9795f29bfaf5d6ef3b6 6728
node-chai_4.3.6~ds1+~cs9.7.12-3.debian.tar.xz
Files:
3cf9d4125126b9a9d510f967d2320fc5 3750 javascript optional
node-chai_4.3.6~ds1+~cs9.7.12-3.dsc
08006e421ac8f653c98d3fd451af88b4 6728 javascript optional
node-chai_4.3.6~ds1+~cs9.7.12-3.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI616MACgkQ9tdMp8mZ
7ulQ9w/9H3JfwzseFRm4WE3E4MGgj/outRcaVJtltLMgZkRrOGj9r9kFo70Ru9IQ
tMgzteGDAEnreIwyUjJXmd8DoMk6y01uZ/pfmTfm6pRSzFuo2gCOvO63BI+s5Upx
34t6kyjkhkMpX9ccJbF6BzBG4DeiMT0pI7P+f6EJkHpKaFNDttRqXjbIZsNj8t9h
j0Gkoqlqx5QY2B7zV7wG+tMI99nx7+f2yMB2JCedqM9k+8IlN8uwhH4zAtKOgH00
zqcsyaPs1NlOrdNZ50sfh8QqEVyioCFpNg2SAEC8xKe2wc5j94rtcr7vN9G4aAIp
bwMrJfjgoGDa2Ra843ZYCylMwHHFpPrANQ0gBR5BH+uIyZzzfpeXpStlRyt019gU
Ql8TqbOFtKTqhQMbqVvS4efby2Y2d0q65JKDcxeg9nGdkS6LYBln5QCRqc0nXjVj
NwmTfWf3iylMB3G/qEB5+EXoLm/hxWyoXMZMTdj3o/5PvKGKWIV22XJdCM5CorXE
DHgj4jlCfqHiWyvNDsqn8DPAsNhb33fdeWDhK3AWU3yMSH22SpRpUFIzr4Ob62c7
jyCQh9p8lYo8GYNKU9mY/soonsj2cc1qb2119bAfQbj07wugJjYIWPbLf5YgADWu
8TYz+PooGg9OWPstInd79C/WwjQeS9pB8fDRDKLR3TN+qP
Bug#1000491: marked as done (FTBFS with Why3 1.4.0)
Your message dated Wed, 23 Mar 2022 08:34:02 + with message-id and subject line Bug#1000491: fixed in frama-c 20211203-chromium-1 has caused the Debian Bug report #1000491, regarding FTBFS with Why3 1.4.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: frama-c Version: 20201209+titanium-4.1 Severity: serious Tags: ftbfs Dear Maintainer, Frama-c FTBFS with Why3 1.4.0: > [...] > File "src/plugins/wp/Why3Provers.ml", line 31, characters 19-61: > 31 | let config = Why3.Whyconf.load_default_config_if_needed config in > ^^ > Error: Unbound value Why3.Whyconf.load_default_config_if_needed > make[1]: *** [share/Makefile.generic:78: src/plugins/wp/Why3Provers.cmo] > Error 2 > make[1]: *** Waiting for unfinished jobs > make[1]: Leaving directory '/<>' > dh_auto_build: error: make -j4 returned exit code 2 > make: *** [debian/rules:45: binary-arch] Error 25 > dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit > status 2 This may be fixed by the new upstream release v23 (Vanadium). Cheers, -- Stéphane -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 --- End Message --- --- Begin Message --- Source: frama-c Source-Version: 20211203-chromium-1 Done: Ralf Treinen We believe that the bug you reported is fixed in the latest version of frama-c, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ralf Treinen (supplier of updated frama-c 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: Tue, 22 Mar 2022 08:02:03 +0100 Source: frama-c Architecture: source Version: 20211203-chromium-1 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Ralf Treinen Closes: 1000491 Changes: frama-c (20211203-chromium-1) unstable; urgency=medium . * New upstream release. This release fixes FTBFS with why3 >= 1.4.0 (closes: #1000491) - drop patch 0001-E-ACSL-avoid-cmx-dependencies-when-in-a-byte-only-ar which has been applied upstream. - refresh remaining patches * install: move libeacsl-dlmalloc.a from usr/lib to usr/lib/frama-c/e-acsl * d/copyright: remove some file patterns that no longer apply. * d/tests/wp: update call to "why3 config" * Standards-Version 4.6.0 (no change) Checksums-Sha1: 8e5bb20456069aa542968ef477083a5dee8a9028 2367 frama-c_20211203-chromium-1.dsc a83bf5d7cd318e8cc4b244c0113e6fe65f40b7b7 7874109 frama-c_20211203-chromium.orig.tar.gz e03987fedcea6440e3d5934734cbc4a5cfc77b28 15884 frama-c_20211203-chromium-1.debian.tar.xz 76a56bec14da5e2f36dcd8ccf6f4fdfcc2a97ec4 13613 frama-c_20211203-chromium-1_source.buildinfo Checksums-Sha256: a019264d6a1a2fac6f2c3ae4fa077b5ec2331825debcf44ff88102d17b12813b 2367 frama-c_20211203-chromium-1.dsc f679af29e0169bb55ea9b5823ed61c112be4a003b64ab894c82390d5b37e75e9 7874109 frama-c_20211203-chromium.orig.tar.gz adfdd2c9a896216f34e6392dac0fdd2284cb07439746c64755581989559eb84e 15884 frama-c_20211203-chromium-1.debian.tar.xz 6a3b21c04a79c0cbf6a97d94a05a712bd453de6750423617eefec11d923520d0 13613 frama-c_20211203-chromium-1_source.buildinfo Files: 1379c9b1623c273c9b35ce13b0075278 2367 devel optional frama-c_20211203-chromium-1.dsc 94a007badc034dc0ec4c09c51b13fa97 7874109 devel optional frama-c_20211203-chromium.orig.tar.gz e5e67031a4a4a5c15edf8a9e1bea8157 15884 devel optional frama-c_20211203-chromium-1.debian.tar.xz d8b76cf730b3b58057a5edf95a66c76a 13613 devel optional frama-c_20211203-chromium-1_source.buildinfo -BEGIN
Bug#1008119: [Debian-pan-maintainers] Bug#1008119: Bug#1008119: src:pyfai: fails to migrate to testing for too long: autopkgtest regression
It seems that it failing now https://ci.debian.net/packages/p/pyfai/ I am on 0.21.2 but I do not know if it solve this mask issue. Cheers Fred
Bug#1008141: FTBFS: unable to use iconv with nodejs >= 14
Package: nodejs Version: 16.13.2+really14.19.1~dfsg-5 Severity: serious Tags: ftbfs Justification: FTBFS During node-iconv rebuild, test fails: node --trace-uncaught test/run-tests.js internal/util/comparisons.js:386 memos.val1.delete(val1); ^^ SyntaxError: Unexpected token 'delete' Thrown at: at compileForInternalLoader (internal/bootstrap/loaders.js:285:18) at nativeModuleRequire (internal/bootstrap/loaders.js:315:14) at lazyLoadComparison (assert.js:78:22) at deepEqual (assert.js:468:34) at /tmp/tt/node_modules/iconv/test/test-basic.js:44:8 at Module._compile (internal/modules/cjs/loader.js:1085:14) at Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) at Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) Error is not related to node-iconv build: you can reproduce the problem using upstream build: $ npm i iconv $ cd node_modules/iconv $ node --trace-uncaught test/run-tests.js [ same error ]
Bug#1008119: [Debian-pan-maintainers] Bug#1008119: src:pyfai: fails to migrate to testing for too long: autopkgtest regression
Dear Paul, I am the upstream author of pyFAI and the release 0.21.1 is a bugfix for the regressions spotted by the debian CI on a couple of 32-bit computer architectures (thanks to debian for that). Thus I don't understand why the migration from unstable to testing is blocked, especially that the tests passes on all architectures now. Best regards, Jerome Nota, a version 0.21.2 was released with some documentation improvements. On Tue, 22 Mar 2022 20:34:35 +0100 Paul Gevers wrote: > Source: pyfai > Version: 0.20.0+dfsg1-4.1 > Severity: serious > Control: close -1 0.21.1+dfsg1-1 > Tags: sid bookworm > User: release.debian@packages.debian.org > Usertags: out-of-sync > Control: block -1 by 1004509 > > 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:pyfai has been trying to migrate for 61 > days [2]. Hence, I am filing this bug. > > 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=pyfai > -- Jérôme Kieffer tel +33 476 882 445
Bug#1008140: marked as pending in node-chai
Control: tag -1 pending Hello, Bug #1008140 in node-chai reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-chai/-/commit/169b9960baf613dea1474babb917214429deeb91 Explicitely export registers also for .mjs Closes: #1008140 (this message was generated automatically) -- Greetings https://bugs.debian.org/1008140
Processed: Bug#1008140 marked as pending in node-chai
Processing control commands: > tag -1 pending Bug #1008140 [chai] mocha: Incompatible with current node-chai Added tag(s) pending. -- 1008140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1008140
Processing commands for cont...@bugs.debian.org: > affects 1008140 node-esquery Bug #1008140 [chai] mocha: Incompatible with current node-chai Added indication that 1008140 affects node-esquery > thanks Stopping processing here. Please contact me if you need assistance. -- 1008140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001669: closed by Debian FTP Masters (reply to Aniol Martí ) (Bug#1001669: fixed in openvpn-auth-ldap 2.0.4-2)
Hi, On Mon, 21 Mar 2022 11:14:47 +0100 Bernhard Schmidt wrote: Hi, unfortunately this is still happening in 2.0.4-2 https://ci.debian.net/packages/o/openvpn-auth-ldap/unstable/amd64/ Right now this would be preventing the new version of openvpn to migrate (I can retry of course). Bernhard I've tried several times and I can't reproduce the bug. I would need further details or assistance. Besides, I also noticed that the last test passed fine: https://ci.debian.net/data/autopkgtest/unstable/amd64/o/openvpn-auth-ldap/20263239/log.gz Regards, Aniol
Processed: reassign 1008140 to chai
Processing commands for cont...@bugs.debian.org: > reassign 1008140 chai Bug #1008140 [mocha] mocha: Incompatible with current node-chai Bug reassigned from package 'mocha' to 'chai'. No longer marked as found in versions node-mocha/9.2.2+ds1+~cs28.3.8-1. Ignoring request to alter fixed versions of bug #1008140 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1008140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008140: mocha: Incompatible with current node-chai
Package: mocha
Version: 9.2.2+ds1+~cs28.3.8-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
During node-esquery rebuild, mocha fails:
undefined ERROR: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath
'./register-assert' is not defined by "exports" in
/usr/share/node_modules/chai/package.json imported from
/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js
at new NodeError (internal/errors.js:322:7)
at throwExportsNotFound (internal/modules/esm/resolve.js:332:9)
at packageExportsResolve (internal/modules/esm/resolve.js:523:7)
at packageResolve (internal/modules/esm/resolve.js:721:14)
at moduleResolve (internal/modules/esm/resolve.js:773:18)
at Loader.defaultResolve [as _resolve]
(internal/modules/esm/resolve.js:887:11)
at Loader.resolve (internal/modules/esm/loader.js:89:40)
at Loader.getModuleJob (internal/modules/esm/loader.js:242:28)
at Loader.import (internal/modules/esm/loader.js:177:28)
at importModuleDynamically (internal/modules/cjs/loader.js:1028:27)
at exports.importModuleDynamicallyCallback
(internal/process/esm_loader.js:30:14)
at formattedImport (/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:30:3)
at exports.requireOrImport
(/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:48:38)
at exports.handleRequires
(/usr/share/nodejs/mocha/lib/cli/run-helpers.js:94:34)
at async /usr/share/nodejs/mocha/lib/cli/run.js:353:25 {
code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}
Bug#1008139: FTBFS: fail to build with nodejs >= 14
Package: node-evp-bytestokey
Version: 1.0.3-10
Severity: serious
Tags: ftbfs
Justification: FTBFS
Hi,
node-evp-bytestokey fails to build with libnode-dev >= 14. See
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-evp-bytestokey/20258806/log.gz
--- 8< ---
../test/main.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE
md5_key32_iv16(Nan::NAN_METHOD_ARGS_TYPE)’:
../test/main.cc:28:11: error: no matching function for call to
‘v8::Object::Set(v8::Local, v8::Local)’
28 | obj->Set(Nan::New("key").ToLocalChecked(),
Nan::CopyBuffer((const char*) key, 32).ToLocalChecked());
|
^~~
In file included from /usr/include/nodejs/src/node.h:67,
from ../test/main.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h:3670:37: note: candidate:
‘v8::Maybe v8::Object::Set(v8::Local, v8::Local,
v8::Local)’
3670 | V8_WARN_UNUSED_RESULT Maybe Set(Local context,
| ^~~
/usr/include/nodejs/deps/v8/include/v8.h:3670:37: note: candidate expects 3
arguments, 2 provided
/usr/include/nodejs/deps/v8/include/v8.h:3673:37: note: candidate:
‘v8::Maybe v8::Object::Set(v8::Local, uint32_t,
v8::Local)’
3673 | V8_WARN_UNUSED_RESULT Maybe Set(Local context,
uint32_t index,
[...]
--- >8 ---
Processed: src:freecontact: fails to migrate to testing for too long: FTBFS on armel
Processing control commands: > close -1 1.0.21-12 Bug #1008138 [src:freecontact] src:freecontact: fails to migrate to testing for too long: FTBFS on armel Marked as fixed in versions freecontact/1.0.21-12. Bug #1008138 [src:freecontact] src:freecontact: fails to migrate to testing for too long: FTBFS on armel Marked Bug as done -- 1008138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008138: src:freecontact: fails to migrate to testing for too long: FTBFS on armel
Source: freecontact Version: 1.0.21-11 Severity: serious Control: close -1 1.0.21-12 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:freecontact has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package fails to build from source on armel. 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=freecontact OpenPGP_signature Description: OpenPGP digital signature
