Bug#1006878: marked as done (libjs-of-ocaml-ocamlbuild-ocaml-dev: missing Breaks+Replaces: libjs-of-ocaml (<< 4), libjs-of-ocaml-dev (<< 4))
Your message dated Tue, 08 Mar 2022 07:03:59 +
with message-id
and subject line Bug#1006878: fixed in js-of-ocaml-ocamlbuild
0.0.0+git20220118+852302c8-2
has caused the Debian Bug report #1006878,
regarding libjs-of-ocaml-ocamlbuild-ocaml-dev: missing Breaks+Replaces:
libjs-of-ocaml (<< 4), libjs-of-ocaml-dev (<< 4)
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.)
--
1006878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjs-of-ocaml-ocamlbuild-ocaml-dev
Version: 0.0.0+git20220118+852302c8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack
.../libjs-of-ocaml-ocamlbuild-ocaml-dev_0.0.0+git20220118+852302c8-1+b1_amd64.deb
...
Unpacking libjs-of-ocaml-ocamlbuild-ocaml-dev
(0.0.0+git20220118+852302c8-1+b1) ...
dpkg: error processing archive
/var/cache/apt/archives/libjs-of-ocaml-ocamlbuild-ocaml-dev_0.0.0+git20220118+852302c8-1+b1_amd64.deb
(--unpack):
trying to overwrite '/usr/lib/ocaml/js_of_ocaml-ocamlbuild/META', which is
also in package libjs-of-ocaml 3.11.0-1+b1
Errors were encountered while processing:
/var/cache/apt/archives/libjs-of-ocaml-ocamlbuild-ocaml-dev_0.0.0+git20220118+852302c8-1+b1_amd64.deb
these files conflict with libjs-of-ocaml:
usr/lib/ocaml/js_of_ocaml-ocamlbuild/META
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cma
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmxs
these files conflict with libjs-of-ocaml-dev
usr/lib/ocaml/js_of_ocaml-ocamlbuild/dune-package
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.a
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmi
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmt
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmti
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmx
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmxa
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.ml
usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.mli
usr/lib/ocaml/js_of_ocaml-ocamlbuild/opam
libjs-of-ocaml(-dev) 4.0.0-1+b1 in sid seems to no longer ship the
conflicting files.
cheers,
Andreas
libjs-of-ocaml-dev=3.11.0-1+b1_libjs-of-ocaml-ocamlbuild-ocaml-dev=0.0.0+git20220118+852302c8-1+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: js-of-ocaml-ocamlbuild
Source-Version: 0.0.0+git20220118+852302c8-2
Done: Stéphane Glondu
We believe that the bug you reported is fixed in the latest version of
js-of-ocaml-ocamlbuild, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1006...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stéphane Glondu (supplier of updated js-of-ocaml-ocamlbuild
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: Tue, 08 Mar 2022 07:40:32 +0100
Source: js-of-ocaml-ocamlbuild
Architecture: source
Version: 0.0.0+git20220118+852302c8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers
Changed-By: Stéphane Glondu
Closes: 1006878
Changes:
js-of-ocaml-ocamlbuild (0.0.0+git20220118+852302c8-2) unstable; urgency=medium
.
* Add Breaks+Replaces libjs-of-ocaml{,-dev} (<< 4) (Closes: #1006878)
Checksums-Sha1:
cacfbbca6e38253fa2d833712b91fd1bfdb2a497 2091
js-of-ocaml-ocamlbuild_0.0.0+git20220118+852302c8-2.dsc
6ca933f96119aae7998ce2021ad2a68dd9582e2f 2024
js-of-ocaml-ocamlbuild_0.0.0+git20220118+852302c8-2.debian.tar.xz
Checksums-Sha256:
c0866504c1930aca040e98cc857819e1c6996bc608a1e76b7360ff5c4e489e89 2091
js-of-ocaml-ocamlbuild_0.0.0+git20220118+852302c8-2.dsc
Bug#1006048: marked as done (python-readme-renderer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13)
Your message dated Tue, 08 Mar 2022 06:18:53 +
with message-id
and subject line Bug#1006048: fixed in python-readme-renderer 32.0-1
has caused the Debian Bug report #1006048,
regarding python-readme-renderer: 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.)
--
1006048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-readme-renderer
Version: 24.0-3
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 build
> dh build --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/build/readme_renderer
> copying readme_renderer/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/readme_renderer
> copying readme_renderer/markdown.py ->
> /<>/.pybuild/cpython3_3.10/build/readme_renderer
> copying readme_renderer/__main__.py ->
> /<>/.pybuild/cpython3_3.10/build/readme_renderer
> copying readme_renderer/__about__.py ->
> /<>/.pybuild/cpython3_3.10/build/readme_renderer
> copying readme_renderer/rst.py ->
> /<>/.pybuild/cpython3_3.10/build/readme_renderer
> copying readme_renderer/clean.py ->
> /<>/.pybuild/cpython3_3.10/build/readme_renderer
> copying readme_renderer/txt.py ->
> /<>/.pybuild/cpython3_3.10/build/readme_renderer
> creating
> /<>/.pybuild/cpython3_3.10/build/readme_renderer/integration
> copying readme_renderer/integration/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/readme_renderer/integration
> copying readme_renderer/integration/distutils.py ->
> /<>/.pybuild/cpython3_3.10/build/readme_renderer/integration
> I: pybuild base:237: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/readme_renderer
> copying readme_renderer/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/readme_renderer
> copying readme_renderer/markdown.py ->
> /<>/.pybuild/cpython3_3.9/build/readme_renderer
> copying readme_renderer/__main__.py ->
> /<>/.pybuild/cpython3_3.9/build/readme_renderer
> copying readme_renderer/__about__.py ->
> /<>/.pybuild/cpython3_3.9/build/readme_renderer
> copying readme_renderer/rst.py ->
> /<>/.pybuild/cpython3_3.9/build/readme_renderer
> copying readme_renderer/clean.py ->
> /<>/.pybuild/cpython3_3.9/build/readme_renderer
> copying readme_renderer/txt.py ->
> /<>/.pybuild/cpython3_3.9/build/readme_renderer
> creating
> /<>/.pybuild/cpython3_3.9/build/readme_renderer/integration
> copying readme_renderer/integration/__init__.py ->
> /<>/.pybuild/cpython3_3.9/build/readme_renderer/integration
> copying readme_renderer/integration/distutils.py ->
> /<>/.pybuild/cpython3_3.9/build/readme_renderer/integration
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:237: cd /<>/.pybuild/cpython3_3.10/build;
> python3.10 -m pytest tests
> = test session starts
> ==
> platform linux -- Python 3.10.2, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>, configfile: pytest.ini
> collected 67 items
>
> tests/test_clean.py .[
> 1%]
> tests/test_integration_distutils.py .. [
> 10%]
> tests/test_markdown.py .FF.. [
> 71%]
> tests/test_noextra.py ss [
> 74%]
> tests/test_rst.py [
> 98%]
> tests/test_txt.py .
> [100%]
>
> === FAILURES
> ===
> _
> test_md_fixtures[/<>/.pybuild/cpython3_3.10/build/tests/fixtures/test_GFM_highlight.md-/<>/.pybuild/cpython3_3.10/build/tests/fixtures/test_GFM_highlight.html-GFM]
> _
>
> md_filename =
> '/<>/.pybuild/cpython3_3.10/build/tests/fixtures/test_GFM_highlight.md'
> html_filename =
>
Bug#1005471: marked as done (translate-toolkit: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13)
Your message dated Tue, 08 Mar 2022 06:19:01 +
with message-id
and subject line Bug#1005471: fixed in translate-toolkit 3.6.0-1
has caused the Debian Bug report #1005471,
regarding translate-toolkit: 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.)
--
1005471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: translate-toolkit
Version: 3.4.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # The entry_points are created now, so run the test suite
> PYBUILD_BEFORE_TEST="cp -a translate/convert/test.*
> {build_dir}/translate/convert/" \
> PYBUILD_TEST_ARGS="." \
> PATH=/<>/debian/translate-toolkit/usr/bin:$PATH \
> dh_auto_test --buildsystem=pybuild
> I: pybuild pybuild:298: cp -a translate/convert/test.*
> /<>/.pybuild/cpython3_3.10_translate/build/translate/convert/
> I: pybuild base:237: cd
> /<>/.pybuild/cpython3_3.10_translate/build; python3.10 -m pytest
> .
> = test session starts
> ==
> platform linux -- Python 3.10.2, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>, configfile: pytest.ini
> collected 3073 items / 3 errors / 1 skipped / 3069 selected
>
> ERRORS
>
> _ ERROR collecting
> .pybuild/cpython3_3.10_translate/build/translate/convert/test_po2rc.py _
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.10_translate/build/translate/convert/test_po2rc.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.10/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> translate/convert/test_po2rc.py:1: in
> from translate.convert import po2rc, test_convert
> translate/convert/po2rc.py:28: in
> from translate.storage import po, rc
> translate/storage/rc.py:30: in
> from pyparsing import (
> E ImportError: cannot import name 'commaSeparatedList' from 'pyparsing'
> (/usr/lib/python3/dist-packages/pyparsing/__init__.py)
> _ ERROR collecting
> .pybuild/cpython3_3.10_translate/build/translate/convert/test_rc2po.py _
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.10_translate/build/translate/convert/test_rc2po.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.10/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> translate/convert/test_rc2po.py:1: in
> from translate.convert import rc2po, test_convert
> translate/convert/rc2po.py:27: in
> from translate.storage import po, rc
> translate/storage/rc.py:30: in
> from pyparsing import (
> E ImportError: cannot import name 'commaSeparatedList' from 'pyparsing'
> (/usr/lib/python3/dist-packages/pyparsing/__init__.py)
> _ ERROR collecting
> .pybuild/cpython3_3.10_translate/build/translate/storage/test_rc.py _
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.10_translate/build/translate/storage/test_rc.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.10/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> translate/storage/test_rc.py:3: in
> from translate.storage import rc
> translate/storage/rc.py:30: in
> from pyparsing import (
> E ImportError: cannot import name 'commaSeparatedList' from 'pyparsing'
> (/usr/lib/python3/dist-packages/pyparsing/__init__.py)
> === short test summary info
>
> ERROR translate/convert/test_po2rc.py
> ERROR translate/convert/test_rc2po.py
> ERROR translate/storage/test_rc.py
> !!! Interrupted: 3 errors during collection
>
> = 1 skipped, 3 errors in 3.30s
> =
> E: pybuild pybuild:367: test: plugin distutils failed with: exit code=2: cd
> /<>/.pybuild/cpython3_3.10_translate/build; python3.10 -m pytest
> .
> I: pybuild pybuild:298: cp -a translate/convert/test.*
>
Bug#1006910: pdal: Should not be included in bookworm
Source: pdal Version: 2.3.0+ds-2 Severity: serious Tags: upstream Justification: in the maintainer's opinion, makes the package unsuitable for release PDAL upstream has exhausted my tolerance of his combative attitude. I am no longer willing to spend time on maintaining this package. The package should be removed from Debian, as others should not be subjected to his attitude either. At time of writing cloudcompare and facet-analyser have pdal as a build dependency, and paraview also has it in its binary package dependencies. These packages will need to remove their pdal support. Once that's done pdal can be removed from Debian. If anyone wants to take over maintenance of the pdal package despite a combative upstream, that will need to happen outside the GIS team.
Bug#1006485: marked as done (fscrypt: CVE-2022-25326 CVE-2022-25327 CVE-2022-25328)
Your message dated Mon, 07 Mar 2022 22:04:02 + with message-id and subject line Bug#1006485: fixed in fscrypt 0.3.3-1 has caused the Debian Bug report #1006485, regarding fscrypt: CVE-2022-25326 CVE-2022-25327 CVE-2022-25328 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.) -- 1006485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fscrypt Version: 0.3.1-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for fscrypt. CVE-2022-25326[0]: | fscrypt through v0.3.2 creates a world-writable directory by default | when setting up a filesystem, allowing unprivileged users to exhaust | filesystem space. We recommend upgrading to fscrypt 0.3.3 or above and | adjusting the permissions on existing fscrypt metadata directories | where applicable. CVE-2022-25327[1]: | The PAM module for fscrypt doesn't adequately validate fscrypt | metadata files, allowing users to create malicious metadata files that | prevent other users from logging in. A local user can cause a denial | of service by creating a fscrypt metadata file that prevents other | users from logging into the system. We recommend upgrading to version | 0.3.3 or above CVE-2022-25328[2]: | The bash_completion script for fscrypt allows injection of commands | via crafted mountpoint paths, allowing privilege escalation under a | specific set of circumstances. A local user who has control over | mountpoint paths could potentially escalate their privileges if they | create a malicious mountpoint path and if the system administrator | happens to be using the fscrypt bash completion script to complete | mountpoint paths. We recommend upgrading to version 0.3.3 or above The issues do not warrant a DSA, but depending on feasibility it would be good th ave the fixes available as well in bullseye and buster through a point release. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-25326 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25326 [1] https://security-tracker.debian.org/tracker/CVE-2022-25327 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25327 [2] https://security-tracker.debian.org/tracker/CVE-2022-25328 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25328 [3] https://www.openwall.com/lists/oss-security/2022/02/24/1 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: fscrypt Source-Version: 0.3.3-1 Done: Paride Legovini We believe that the bug you reported is fixed in the latest version of fscrypt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paride Legovini (supplier of updated fscrypt 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: Mon, 07 Mar 2022 21:32:01 + Source: fscrypt Architecture: source Version: 0.3.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Paride Legovini Closes: 1006485 Changes: fscrypt (0.3.3-1) unstable; urgency=medium . * New upstream version 0.3.1. Closes: #1006485, tracking: - CVE-2022-25326 - CVE-2022-25327 - CVE-2022-25328 * d/gbp.conf: debian-branch = debian/latest (DEP-14) * d/copyright: update copyright years for debian/* Checksums-Sha1: 7ed14c439caae9e5cce70560a38b66f515a8d161 1972 fscrypt_0.3.3-1.dsc ba40c6bbbf31fae38f0903e9cb9fade644c64031 135152 fscrypt_0.3.3.orig.tar.xz f389222e59ccde6bd82cb5a8760ff58c58ca2731 5440 fscrypt_0.3.3-1.debian.tar.xz cd7847413902105c804ecd90f2bb180b2c33d41e 6785 fscrypt_0.3.3-1_amd64.buildinfo Checksums-Sha256: 9907a4dcbb6ed8ede85df8f6b9fc81cdfb5e4cd8019e22bfd1ffefbabea6103a 1972 fscrypt_0.3.3-1.dsc beec9ed0e03b76dbe82aba743242146a42e2b38df14638e54c49e2abaffc802b 135152
Processed: update bts meta info
Processing commands for cont...@bugs.debian.org:
> reassign 1006735 src:symfony 5.4.4+dfsg-1
Bug #1006735 {Done: David Prévot } [src:phpunit,
src:symfony] phpunit breaks symfony autopkgtest: rounding differences
Bug reassigned from package 'src:phpunit, src:symfony' to 'src:symfony'.
No longer marked as found in versions phpunit/9.5.14-1 and symfony/5.4.4+dfsg-1.
No longer marked as fixed in versions symfony/5.4.6+dfsg-1.
Bug #1006735 {Done: David Prévot } [src:symfony] phpunit
breaks symfony autopkgtest: rounding differences
Marked as found in versions symfony/5.4.4+dfsg-1.
> fixed 1006735 5.4.6+dfsg-1
Bug #1006735 {Done: David Prévot } [src:symfony] phpunit
breaks symfony autopkgtest: rounding differences
Marked as fixed in versions symfony/5.4.6+dfsg-1.
> affects 1006735 src:phpunit
Bug #1006735 {Done: David Prévot } [src:symfony] phpunit
breaks symfony autopkgtest: rounding differences
Added indication that 1006735 affects src:phpunit
> reassign 1006734 src:php-symfony-polyfill 1.24.0-1
Bug #1006734 {Done: David Prévot } [src:phpunit,
src:php-symfony-polyfill] phpunit breaks php-symfony-polyfill autopkgtest:
rounding differences
Bug reassigned from package 'src:phpunit, src:php-symfony-polyfill' to
'src:php-symfony-polyfill'.
No longer marked as found in versions php-symfony-polyfill/1.24.0-1 and
phpunit/9.5.14-1.
No longer marked as fixed in versions php-symfony-polyfill/1.25.0-1.
Bug #1006734 {Done: David Prévot }
[src:php-symfony-polyfill] phpunit breaks php-symfony-polyfill autopkgtest:
rounding differences
Marked as found in versions php-symfony-polyfill/1.24.0-1.
> fixed 1006734 1.25.0-1
Bug #1006734 {Done: David Prévot }
[src:php-symfony-polyfill] phpunit breaks php-symfony-polyfill autopkgtest:
rounding differences
Marked as fixed in versions php-symfony-polyfill/1.25.0-1.
> affects 1006734 src:phpunit
Bug #1006734 {Done: David Prévot }
[src:php-symfony-polyfill] phpunit breaks php-symfony-polyfill autopkgtest:
rounding differences
Added indication that 1006734 affects src:phpunit
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1006734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006734
1006735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: src:golang-github-komkom-toml: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 0.0~git20211215.3c8ee9d-1
Bug #1006893 [src:golang-github-komkom-toml] src:golang-github-komkom-toml:
fails to migrate to testing for too long: autopkgtest regression
Marked as fixed in versions golang-github-komkom-toml/0.0~git20211215.3c8ee9d-1.
Bug #1006893 [src:golang-github-komkom-toml] src:golang-github-komkom-toml:
fails to migrate to testing for too long: autopkgtest regression
Marked Bug as done
> block -1 by 1004048
Bug #1006893 {Done: Paul Gevers }
[src:golang-github-komkom-toml] src:golang-github-komkom-toml: fails to migrate
to testing for too long: autopkgtest regression
1006893 was not blocked by any bugs.
1006893 was not blocking any bugs.
Added blocking bug(s) of 1006893: 1004048
--
1006893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1006893: src:golang-github-komkom-toml: fails to migrate to testing for too long: autopkgtest regression
Source: golang-github-komkom-toml Version: 0.0~git20210303.132fb38-2 Severity: serious Control: close -1 0.0~git20211215.3c8ee9d-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1004048 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:golang-github-komkom-toml has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package has an autopkgtest regression with an associated bug report. 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=golang-github-komkom-toml OpenPGP_signature Description: OpenPGP digital signature
Bug#1006891: src:nuitka: fails to migrate to testing for too long: unresolved RC bug
Source: nuitka Version: 0.6.17.2+ds-1.1 Severity: serious Control: close -1 0.6.19.1+ds-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1006051 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:nuitka has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package has an unresolved RC 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=nuitka OpenPGP_signature Description: OpenPGP digital signature
Processed: src:nuitka: fails to migrate to testing for too long: unresolved RC bug
Processing control commands:
> close -1 0.6.19.1+ds-1
Bug #1006891 [src:nuitka] src:nuitka: fails to migrate to testing for too long:
unresolved RC bug
Marked as fixed in versions nuitka/0.6.19.1+ds-1.
Bug #1006891 [src:nuitka] src:nuitka: fails to migrate to testing for too long:
unresolved RC bug
Marked Bug as done
> block -1 by 1006051
Bug #1006891 {Done: Paul Gevers } [src:nuitka] src:nuitka:
fails to migrate to testing for too long: unresolved RC bug
1006891 was not blocked by any bugs.
1006891 was not blocking any bugs.
Added blocking bug(s) of 1006891: 1006051
--
1006891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#997829: marked as done (libipc-shareable-perl: autopkgtest regression on armhf and i386)
Your message dated Mon, 07 Mar 2022 18:20:11 + with message-id and subject line Bug#997829: fixed in libipc-shareable-perl 1.09-2 has caused the Debian Bug report #997829, regarding libipc-shareable-perl: autopkgtest regression on armhf and i386 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.) -- 997829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libipc-shareable-perl Version: 1.06-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of libipc-shareable-perl the autopkgtest of libipc-shareable-perl fails in testing when that autopkgtest is run with the binary packages of libipc-shareable-perl from unstable. It passes when run with only packages from testing. In tabular form: passfail libipc-shareable-perl from testing1.06-1 all others from testingfrom testing I copied some of the output at the bottom of this report. The issue seems to be related to 32 bit archs. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=libipc-shareable-perl https://ci.debian.net/data/autopkgtest/testing/armhf/libi/libipc-shareable-perl/16170185/log.gz t/65-seg_size.t .. ok 1 - size larger than MAX croaks ok ok 2 - ...and error is sane IPC_MEM env var not set, skipping the exhaust memory test not ok 3 - We croak if size is greater than max RAM # Failed test 'We croak if size is greater than max RAM' # at t/65-seg_size.t line 52. # got: '1' # expected: undef not ok 4 - ...and error is sane # Failed test '...and error is sane' # at t/65-seg_size.t line 54. # '' # doesn't match '(?^:Cannot allocate memory|Out of memory|Invalid argument)' ok 5 - size param is the same as the segment size ok 6 - actual size in bytes ok if sending in custom size 1..6 # Looks like you failed 2 tests of 6. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/6 subtests [...] t/85-spawn_object_contains_data.t skipped: IPC_SPAWN_TEST env var not set t/86-unspawn_object_contains_data.t .. skipped: IPC_SPAWN_TEST env var not set t/91-pod_linkcheck.t . skipped: Author test: RELEASE_TESTING not set t/93-manifest.t .. skipped: Author test: RELEASE_TESTING not set Test Summary Report --- t/65-seg_size.t(Wstat: 512 Tests: 6 Failed: 2) Failed tests: 3-4 Non-zero exit status: 2 Files=36, Tests=412, 16 wallclock secs ( 0.20 usr 0.36 sys + 4.66 cusr 4.92 csys = 10.14 CPU) Result: FAIL autopkgtest [10:47:54]: test autodep8-perl-build-deps OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: libipc-shareable-perl Source-Version: 1.09-2 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libipc-shareable-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libipc-shareable-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 07 Mar 2022 18:26:06 +0100 Source: libipc-shareable-perl Architecture: source Version: 1.09-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 997829 Changes: libipc-shareable-perl (1.09-2) unstable; urgency=medium . * Revert "Drop 32bit.patch, fixed (similarly) upstream." The test failure on 32-bit architectures still exists. (Closes: #997829) Checksums-Sha1: 0edb0110e3dd3af6a74c8b8dca53ce71bb44f1ed 2551 libipc-shareable-perl_1.09-2.dsc 9ce3db5e55aaf1aa2ea193373ba740b34f0c1ada 4612
Processed: fixed 997829 in 1.06-2
Processing commands for cont...@bugs.debian.org: > fixed 997829 1.06-2 Bug #997829 [src:libipc-shareable-perl] libipc-shareable-perl: autopkgtest regression on armhf and i386 Marked as fixed in versions libipc-shareable-perl/1.06-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 997829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997829: marked as pending in libipc-shareable-perl
Control: tag -1 pending Hello, Bug #997829 in libipc-shareable-perl 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/perl-team/modules/packages/libipc-shareable-perl/-/commit/e7843da856985993ffa726fd7ec909a0f5289b75 Revert "Drop 32bit.patch, fixed (similarily) upstream." The test failure on 32-bit architectures still exists. Closes: #997829 (this message was generated automatically) -- Greetings https://bugs.debian.org/997829
Processed: Bug#997829 marked as pending in libipc-shareable-perl
Processing control commands: > tag -1 pending Bug #997829 [src:libipc-shareable-perl] libipc-shareable-perl: autopkgtest regression on armhf and i386 Added tag(s) pending. -- 997829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:php8.1
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:php8.1 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1006672 (http://bugs.debian.org/1006672) > # Bug title: php8.1: CVE-2021-21708 > # * http://bugs.php.net/rss/bug.php?format=xml=81708 > # * remote status changed: (?) -> Closed > # * closed upstream > tags 1006672 + fixed-upstream Bug #1006672 [src:php8.1] php8.1: CVE-2021-21708 Added tag(s) fixed-upstream. > usertags 1006672 + status-Closed There were no usertags set. Usertags are now: status-Closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 997829 in 1.06-2
Processing commands for cont...@bugs.debian.org: > notfound 997829 1.06-2 Bug #997829 [src:libipc-shareable-perl] libipc-shareable-perl: autopkgtest regression on armhf and i386 Ignoring request to alter found versions of bug #997829 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 997829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006384: closed by Debian FTP Masters (reply to Olivier Sallou ) (Bug#1006384: fixed in logol 1.7.9+dfsg-2)
Hi, Paul Gevers писал 2022-03-06 21:36: > Hi Lev, > > On 06-03-2022 11:30, dogs...@riseup.net wrote: >> As I can see, there is only one reverse build-dependency on swi-prolog >> apart from eye and logol, that is ppl. It is a C++ library providing >> SWI-Prolog interface. I tried to build it against swi-prolog from >> unstable on amd64 porterbox and the build was successful (including >> tests, which are unfortunately not autopkgtest-ready). > > Is this enough to say the ABI change doesn't effect ppl? I'm not sure whether ppl depends and/or somehow uses some particular swi-prolog ABI, I tried to run tests from ppl source package with ppl and swi-prolog binary packages installed (from unstable), but with no success. I just don't know right now how to run them correctly (these are C++ source code, as far as I can tell). So, CCing uploaders of ppl. Tobias, Michael, is it possible that ABI changes in swi-prolog may break binaries of ppl in unstable? How can we test it? As quoted above, I already tried to build ppl against the newest swi-prolog in unstable, and ppl was built successfully. Regards, Lev
Processed: unarchiving 997829, reopening 997829, found 997829 in 1.09-1, notfound 997829 in 1.06-2
Processing commands for cont...@bugs.debian.org:
> unarchive 997829
Bug #997829 {Done: gregor herrmann }
[src:libipc-shareable-perl] libipc-shareable-perl: autopkgtest regression on
armhf and i386
Unarchived Bug 997829
> reopen 997829
Bug #997829 {Done: gregor herrmann }
[src:libipc-shareable-perl] libipc-shareable-perl: autopkgtest regression on
armhf and i386
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libipc-shareable-perl/1.06-2.
> found 997829 1.09-1
Bug #997829 [src:libipc-shareable-perl] libipc-shareable-perl: autopkgtest
regression on armhf and i386
Marked as found in versions libipc-shareable-perl/1.09-1.
> notfound 997829 1.06-2
Bug #997829 [src:libipc-shareable-perl] libipc-shareable-perl: autopkgtest
regression on armhf and i386
Ignoring request to alter found versions of bug #997829 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
997829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1004646: marked as done (node-tap-parser: node-minipass is now packaged separately)
Your message dated Mon, 07 Mar 2022 14:53:03 + with message-id and subject line Bug#1004646: fixed in node-tap-parser 10.1.0+~cs2.1.2-1 has caused the Debian Bug report #1004646, regarding node-tap-parser: node-minipass is now packaged separately 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.) -- 1004646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-tap-parser Version: 10.1.0-2 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 .../node-tap-parser_10.1.0-2_all.deb ... Unpacking node-tap-parser (10.1.0-2) ... dpkg: error processing archive /var/cache/apt/archives/node-tap-parser_10.1.0-2_all.deb (--unpack): trying to overwrite '/usr/share/nodejs/minipass/index.js', which is also in package node-minipass 3.1.6+~cs8.7.18-1 Errors were encountered while processing: /var/cache/apt/archives/node-tap-parser_10.1.0-2_all.deb cheers, Andreas node-minipass=3.1.6+~cs8.7.18-1_node-tap-parser=10.1.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: node-tap-parser Source-Version: 10.1.0+~cs2.1.2-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-tap-parser, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1004...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-tap-parser 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: Mon, 31 Jan 2022 02:43:56 +0100 Source: node-tap-parser Architecture: source Version: 10.1.0+~cs2.1.2-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1004646 Changes: node-tap-parser (10.1.0+~cs2.1.2-1) experimental; urgency=medium . * Team upload * Replace minipass component by dependency to node-minipass (Closes: #1004646) * New upstream version 10.1.0+~cs2.1.2 * Update test for tap 12 * Add lintian overrides Checksums-Sha1: 6dde8161cf551b38663a3f7050e368262e33d6d5 2835 node-tap-parser_10.1.0+~cs2.1.2-1.dsc 4736c3fea63bb019631f62c5f173bdc34d6a8b9a 2968 node-tap-parser_10.1.0+~cs2.1.2.orig-events-to-array.tar.gz 5a828c79318101e5f89a42b191f2688e7df33381 32736 node-tap-parser_10.1.0+~cs2.1.2.orig-tap-yaml.tar.gz f5a68f5313ee01ea8dffccd17c05db0ee383737f 148428 node-tap-parser_10.1.0+~cs2.1.2.orig.tar.gz 08f4a760bb25815071a1dc53cdfaca4a9f139ba3 4816 node-tap-parser_10.1.0+~cs2.1.2-1.debian.tar.xz Checksums-Sha256: 89f44a11ad02d9253b11ff9233bbadeda8157988fae9b6465ea4b10d9da3654f 2835 node-tap-parser_10.1.0+~cs2.1.2-1.dsc aec1dd86e500a6cf6e3e19dc92502882fe1572ebfd78bc0be9662a3070d4fa35 2968 node-tap-parser_10.1.0+~cs2.1.2.orig-events-to-array.tar.gz 593a61bff8d08c739db760ddd5160656750d0b8378b4f82d70152c38798cc8e5 32736 node-tap-parser_10.1.0+~cs2.1.2.orig-tap-yaml.tar.gz 5e0fba856234c58e8a47981ba63db00e2638300586122098d48881a188fcc724 148428 node-tap-parser_10.1.0+~cs2.1.2.orig.tar.gz db6cc6db98205b47001f9f1b099c0dbf464c45ce723cd0273450f05be633bcca 4816 node-tap-parser_10.1.0+~cs2.1.2-1.debian.tar.xz Files: 8673f3c9bbed5fd4703a4c7883c74bb8 2835 javascript optional node-tap-parser_10.1.0+~cs2.1.2-1.dsc b6a040d9fbae68c3c5ea71aba06a3a5d 2968 javascript optional node-tap-parser_10.1.0+~cs2.1.2.orig-events-to-array.tar.gz e45fdaa90ea0e6e57f2426189cc58b71 32736 javascript optional node-tap-parser_10.1.0+~cs2.1.2.orig-tap-yaml.tar.gz c6f0f8d6c8ce3ffbf6ae1ec255475d2f 148428 javascript optional node-tap-parser_10.1.0+~cs2.1.2.orig.tar.gz 33eb372914531c8d429d0247aad00ccd 4816 javascript optional node-tap-parser_10.1.0+~cs2.1.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmImFg0ACgkQ9tdMp8mZ 7un0eA/7BumrGGgOxVtows7tYBZAxtk95TeucI7Ewi8IGNZEcaua9KY1mpVXb+LF XOhceHTdXGaI6tHBXlYfRDxYPDzXaSgrwGBUPD+BuoZQgpp2F5uZSjDv8IUQ6EoW
Bug#1004646: marked as pending in node-tap-parser
Control: tag -1 pending Hello, Bug #1004646 in node-tap-parser 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-tap-parser/-/commit/44627e0e87a04323d2a4741503b1165b4dc74521 Replace minipass component by dependency to node-minipass Closes: #1004646 (this message was generated automatically) -- Greetings https://bugs.debian.org/1004646
Processed: Bug#1004646 marked as pending in node-tap-parser
Processing control commands: > tag -1 pending Bug #1004646 [node-tap-parser] node-tap-parser: node-minipass is now packaged separately Added tag(s) pending. -- 1004646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006017: playitslowly doesn't start (hasn't for awhile)
On Sat, Mar 05, 2022 at 11:16:44AM +0100, Andreas Beckmann wrote: > On 04/03/2022 13.15, Tiago Bortoletto Vaz wrote: > > This package has indeed been broken for a long time already. Upstream is > > inactive since 2015 and I'm not willing to do all the fixes it would > > need. Therefore I requested its removal from Debian archive. > > Then we should probably get it removed from stable and and oldstable as > well, since it it not usable there either. > Can you file the corresponding bugs, too? Sure, I'll proceed with the requests. Bests, -- Tiago
Bug#1006878: libjs-of-ocaml-ocamlbuild-ocaml-dev: missing Breaks+Replaces: libjs-of-ocaml (<< 4), libjs-of-ocaml-dev (<< 4)
Package: libjs-of-ocaml-ocamlbuild-ocaml-dev Version: 0.0.0+git20220118+852302c8-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libjs-of-ocaml-ocamlbuild-ocaml-dev_0.0.0+git20220118+852302c8-1+b1_amd64.deb ... Unpacking libjs-of-ocaml-ocamlbuild-ocaml-dev (0.0.0+git20220118+852302c8-1+b1) ... dpkg: error processing archive /var/cache/apt/archives/libjs-of-ocaml-ocamlbuild-ocaml-dev_0.0.0+git20220118+852302c8-1+b1_amd64.deb (--unpack): trying to overwrite '/usr/lib/ocaml/js_of_ocaml-ocamlbuild/META', which is also in package libjs-of-ocaml 3.11.0-1+b1 Errors were encountered while processing: /var/cache/apt/archives/libjs-of-ocaml-ocamlbuild-ocaml-dev_0.0.0+git20220118+852302c8-1+b1_amd64.deb these files conflict with libjs-of-ocaml: usr/lib/ocaml/js_of_ocaml-ocamlbuild/META usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cma usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmxs these files conflict with libjs-of-ocaml-dev usr/lib/ocaml/js_of_ocaml-ocamlbuild/dune-package usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.a usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmi usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmt usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmti usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmx usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.cmxa usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.ml usr/lib/ocaml/js_of_ocaml-ocamlbuild/ocamlbuild_js_of_ocaml.mli usr/lib/ocaml/js_of_ocaml-ocamlbuild/opam libjs-of-ocaml(-dev) 4.0.0-1+b1 in sid seems to no longer ship the conflicting files. cheers, Andreas libjs-of-ocaml-dev=3.11.0-1+b1_libjs-of-ocaml-ocamlbuild-ocaml-dev=0.0.0+git20220118+852302c8-1+b1.log.gz Description: application/gzip
Processed: found 1005147 in 2.3.1-2
Processing commands for cont...@bugs.debian.org: > found 1005147 2.3.1-2 Bug #1005147 [siftool] siftool: ships /usr/bin/test Marked as found in versions golang-github-sylabs-sif/2.3.1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1005147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005376: marked as done (kill(1) with negative PIDs kills the current process group)
Your message dated Mon, 07 Mar 2022 11:34:00 + with message-id and subject line Bug#1005376: fixed in procps 2:3.3.17-7 has caused the Debian Bug report #1005376, regarding kill(1) with negative PIDs kills the current process group 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.) -- 1005376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: procps Version: 2:3.3.17-5 Severity: serious Dear maintainer, calling kill(1) with negative PIDs always delivers the signal to the current process group, instead of the one with the specified PID. That is because the binary always calls kill(2) with 0 as first argument. This is known and has been fixed upstream: https://gitlab.com/procps-ng/procps/-/issues/211 https://gitlab.com/procps-ng/procps/-/commit/79097e55e4b08ec8c1de8332e32cf03c4be1d4ec This bug affects both Debian stable (Bullseye) and testing/unstable. Best, Felix--- End Message --- --- Begin Message --- Source: procps Source-Version: 2:3.3.17-7 Done: Craig Small We believe that the bug you reported is fixed in the latest version of procps, 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. Craig Small (supplier of updated procps 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: Mon, 07 Mar 2022 22:05:15 +1100 Source: procps Binary: libprocps-dev libprocps8 libprocps8-dbgsym procps procps-dbgsym Architecture: source amd64 Version: 2:3.3.17-7 Distribution: unstable Urgency: medium Maintainer: Craig Small Changed-By: Craig Small Description: libprocps-dev - library for accessing process information from /proc libprocps8 - library for accessing process information from /proc procps - /proc file system utilities Closes: 987557 1005018 1005285 1005376 1005392 Changes: procps (2:3.3.17-7) unstable; urgency=medium . * Update to Debian standards 4.6.0 * Correct patch test_proc_siginfo Closes: #987557 again * Install locale files for kfreebsd Closes: #1005285 * kill: Correctly handle negative pids Closes: #1005376 * pidwait: Check correct name for program Closes: #1005018 * Remove ancient unrequired preinst script Closes: #1005392 Checksums-Sha1: 66540ac42c332d77f4eeea7c652c7e6f73163fc7 2136 procps_3.3.17-7.dsc 02ea16a0f888dfac46b45e58175944dc121072f3 29196 procps_3.3.17-7.debian.tar.xz 0a075ae238490d8efa4dcd45fafe18f8e7ae7d83 76316 libprocps-dev_3.3.17-7_amd64.deb 7d5324ceca46844b8949a23a22c258afe79f0c86 82868 libprocps8-dbgsym_3.3.17-7_amd64.deb af8f8d4f1d9fcbb2bc24f9fe684b548ee1d661bf 63820 libprocps8_3.3.17-7_amd64.deb 95e74d3090df3f90b30cd5a6cd4d8e37ba82e10c 385660 procps-dbgsym_3.3.17-7_amd64.deb efb3b56152b0d157e6634ef4382b0ea6ef5e5a65 7201 procps_3.3.17-7_amd64.buildinfo 3fdb5be08c7d2e47cd0bbdf1bb8f1992629bf40c 501504 procps_3.3.17-7_amd64.deb Checksums-Sha256: 732d511886d3141ca96d189706232eada1b73dc44e3671ca7ef2ffd6838d01f7 2136 procps_3.3.17-7.dsc 43148a05c2694b946dd485aea135a3c0645019e785b80064d0ebffa88426f6a9 29196 procps_3.3.17-7.debian.tar.xz e94e680479a4981dc453a3ec7146775f8611177f2a808014ee104487bef045e1 76316 libprocps-dev_3.3.17-7_amd64.deb c1a8e219089f0bd07427e7987a42f268a3b28f775b99f8b59ee9cc20c9dfadd2 82868 libprocps8-dbgsym_3.3.17-7_amd64.deb 5c4b1b27e0b2a936e261097d2a07092b9f63ffde3936b7f1fefb1421824e8626 63820 libprocps8_3.3.17-7_amd64.deb 238cb402d7b60dcfb8f5636899bacc1c89127172c06b653a83c457b20f986bbd 385660 procps-dbgsym_3.3.17-7_amd64.deb cbf38e22c961ae808c4ded3cd3929c5c9f92484b21b3f56b5844c737580d 7201 procps_3.3.17-7_amd64.buildinfo 5f98f7b8fb751909d436b59fa55259088c7dfe300ca78ab602f2462002de37f2 501504 procps_3.3.17-7_amd64.deb Files: 2114cf4eacbe3b048a3f400c9125e881 2136 admin optional procps_3.3.17-7.dsc c135879200d274af60ad9cc81b7fd52d 29196 admin optional procps_3.3.17-7.debian.tar.xz 199bb313e8e4328bc42db9d0e612439e 76316 libdevel optional libprocps-dev_3.3.17-7_amd64.deb fcae55e2a67d3bdeedde366dcd4ffc1c 82868 debug optional libprocps8-dbgsym_3.3.17-7_amd64.deb
Bug#1006089: marked as done (fonts-firacode: FTBFS: pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution was not found and is required by fonttools)
Your message dated Mon, 7 Mar 2022 12:20:13 +0100
with message-id
and subject line dependency fixed
has caused the Debian Bug report #1006089,
regarding fonts-firacode: FTBFS: pkg_resources.DistributionNotFound: The
'unicodedata2>=14.0.0' distribution was not found and is required by fonttools
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.)
--
1006089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fonts-firacode
Version: 6.2-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):
> make[1]: Entering directory '/<>'
> bash script/build.sh
> Making distr/ttf/FiraCode-Light.ttf
> Traceback (most recent call last):
> File "/usr/bin/fontmake", line 33, in
> sys.exit(load_entry_point('fontmake==2.4.1', 'console_scripts',
> 'fontmake')())
> File "/usr/bin/fontmake", line 25, in importlib_load_entry_point
> return next(matches).load()
> File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
> module = import_module(match.group('module'))
> File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1030, in _gcd_import
> File "", line 1007, in _find_and_load
> File "", line 986, in _find_and_load_unlocked
> File "", line 680, in _load_unlocked
> File "", line 850, in exec_module
> File "", line 228, in _call_with_frames_removed
> File "/usr/lib/python3/dist-packages/fontmake/__main__.py", line 20, in
>
> from ufo2ft import CFFOptimization
> File "/usr/lib/python3/dist-packages/ufo2ft/__init__.py", line 8, in
>
> from ufo2ft.featureCompiler import (
> File "/usr/lib/python3/dist-packages/ufo2ft/featureCompiler.py", line 14,
> in
> from ufo2ft.featureWriters import (
> File "/usr/lib/python3/dist-packages/ufo2ft/featureWriters/__init__.py",
> line 11, in
> from .markFeatureWriter import MarkFeatureWriter
> File
> "/usr/lib/python3/dist-packages/ufo2ft/featureWriters/markFeatureWriter.py",
> line 9, in
> from ufo2ft.fontInfoData import getAttrWithFallback
> File "/usr/lib/python3/dist-packages/ufo2ft/fontInfoData.py", line 23, in
>
> from fontTools import ufoLib
> File "/usr/lib/python3/dist-packages/fontTools/ufoLib/__init__.py", line 8,
> in
> import fs
> File "/usr/lib/python3/dist-packages/fs/__init__.py", line 4, in
> __import__("pkg_resources").declare_namespace(__name__) # type: ignore
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3267,
> in
> def _initialize_master_working_set():
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3241,
> in _call_aside
> f(*args, **kwargs)
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3279,
> in _initialize_master_working_set
> working_set = WorkingSet._build_master()
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 573,
> in _build_master
> ws.require(__requires__)
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 891,
> in require
> needed = self.resolve(parse_requirements(requirements))
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 777,
> in resolve
> raise DistributionNotFound(req, requirers)
> pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution
> was not found and is required by fonttools
> make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/02/18/fonts-firacode_6.2-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
The fonttools unicodedata2 issue was not caused by these packages,
and after it got fixed, they build ok now.
Closing.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁'Russkiy voyennyi korabl, idi nakhuy'
⢿⡄⠘⠷⠚⠋⠀
⠈⠳⣄--- End Message ---
Bug#1006106: marked as done (fonts-mononoki: FTBFS: pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution was not found and is required by fonttools)
Your message dated Mon, 7 Mar 2022 12:20:13 +0100
with message-id
and subject line dependency fixed
has caused the Debian Bug report #1006106,
regarding fonts-mononoki: FTBFS: pkg_resources.DistributionNotFound: The
'unicodedata2>=14.0.0' distribution was not found and is required by fonttools
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.)
--
1006106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fonts-mononoki
Version: 1.2+dfsg2-2
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):
> make[1]: Entering directory '/<>'
> # No interpolated instances for the time being,
> # see https://github.com/googlefonts/ufo2ft/issues/339
> fontmake -o ttf -u src/*.ufo
> Traceback (most recent call last):
> File "/usr/bin/fontmake", line 33, in
> sys.exit(load_entry_point('fontmake==2.4.1', 'console_scripts',
> 'fontmake')())
> File "/usr/bin/fontmake", line 25, in importlib_load_entry_point
> return next(matches).load()
> File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
> module = import_module(match.group('module'))
> File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1030, in _gcd_import
> File "", line 1007, in _find_and_load
> File "", line 986, in _find_and_load_unlocked
> File "", line 680, in _load_unlocked
> File "", line 850, in exec_module
> File "", line 228, in _call_with_frames_removed
> File "/usr/lib/python3/dist-packages/fontmake/__main__.py", line 20, in
>
> from ufo2ft import CFFOptimization
> File "/usr/lib/python3/dist-packages/ufo2ft/__init__.py", line 8, in
>
> from ufo2ft.featureCompiler import (
> File "/usr/lib/python3/dist-packages/ufo2ft/featureCompiler.py", line 14,
> in
> from ufo2ft.featureWriters import (
> File "/usr/lib/python3/dist-packages/ufo2ft/featureWriters/__init__.py",
> line 11, in
> from .markFeatureWriter import MarkFeatureWriter
> File
> "/usr/lib/python3/dist-packages/ufo2ft/featureWriters/markFeatureWriter.py",
> line 9, in
> from ufo2ft.fontInfoData import getAttrWithFallback
> File "/usr/lib/python3/dist-packages/ufo2ft/fontInfoData.py", line 23, in
>
> from fontTools import ufoLib
> File "/usr/lib/python3/dist-packages/fontTools/ufoLib/__init__.py", line 8,
> in
> import fs
> File "/usr/lib/python3/dist-packages/fs/__init__.py", line 4, in
> __import__("pkg_resources").declare_namespace(__name__) # type: ignore
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3267,
> in
> def _initialize_master_working_set():
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3241,
> in _call_aside
> f(*args, **kwargs)
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3279,
> in _initialize_master_working_set
> working_set = WorkingSet._build_master()
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 573,
> in _build_master
> ws.require(__requires__)
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 891,
> in require
> needed = self.resolve(parse_requirements(requirements))
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 777,
> in resolve
> raise DistributionNotFound(req, requirers)
> pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution
> was not found and is required by fonttools
> make[1]: *** [debian/rules:9: master_ttf] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/02/18/fonts-mononoki_1.2+dfsg2-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 ---
The fonttools unicodedata2 issue was not caused by these packages,
and after it got fixed, they build ok now.
Closing.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁'Russkiy voyennyi korabl, idi nakhuy'
⢿⡄⠘⠷⠚⠋⠀
⠈⠳⣄---
Bug#1006090: marked as done (fonts-hack: FTBFS: pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution was not found and is required by fonttools)
Your message dated Mon, 7 Mar 2022 12:20:13 +0100
with message-id
and subject line dependency fixed
has caused the Debian Bug report #1006090,
regarding fonts-hack: FTBFS: pkg_resources.DistributionNotFound: The
'unicodedata2>=14.0.0' distribution was not found and is required by fonttools
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.)
--
1006090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fonts-hack
Version: 3.003-3
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):
> make[2]: Entering directory '/<>'
> ./build-ttf.sh
> Confirming that build dependencies are installed...
>
> /usr/bin/fontmake
> fontTools Python library identified
> /usr/bin/ttfautohint
> Starting build...
>
> Traceback (most recent call last):
> File "/usr/bin/fontmake", line 33, in
> sys.exit(load_entry_point('fontmake==2.4.1', 'console_scripts',
> 'fontmake')())
> File "/usr/bin/fontmake", line 25, in importlib_load_entry_point
> return next(matches).load()
> File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
> module = import_module(match.group('module'))
> File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1030, in _gcd_import
> File "", line 1007, in _find_and_load
> File "", line 986, in _find_and_load_unlocked
> File "", line 680, in _load_unlocked
> File "", line 850, in exec_module
> File "", line 228, in _call_with_frames_removed
> File "/usr/lib/python3/dist-packages/fontmake/__main__.py", line 20, in
>
> from ufo2ft import CFFOptimization
> File "/usr/lib/python3/dist-packages/ufo2ft/__init__.py", line 8, in
>
> from ufo2ft.featureCompiler import (
> File "/usr/lib/python3/dist-packages/ufo2ft/featureCompiler.py", line 14,
> in
> from ufo2ft.featureWriters import (
> File "/usr/lib/python3/dist-packages/ufo2ft/featureWriters/__init__.py",
> line 11, in
> from .markFeatureWriter import MarkFeatureWriter
> File
> "/usr/lib/python3/dist-packages/ufo2ft/featureWriters/markFeatureWriter.py",
> line 9, in
> from ufo2ft.fontInfoData import getAttrWithFallback
> File "/usr/lib/python3/dist-packages/ufo2ft/fontInfoData.py", line 23, in
>
> from fontTools import ufoLib
> File "/usr/lib/python3/dist-packages/fontTools/ufoLib/__init__.py", line 8,
> in
> import fs
> File "/usr/lib/python3/dist-packages/fs/__init__.py", line 4, in
> __import__("pkg_resources").declare_namespace(__name__) # type: ignore
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3267,
> in
> def _initialize_master_working_set():
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3241,
> in _call_aside
> f(*args, **kwargs)
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3279,
> in _initialize_master_working_set
> working_set = WorkingSet._build_master()
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 573,
> in _build_master
> ws.require(__requires__)
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 891,
> in require
> needed = self.resolve(parse_requirements(requirements))
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 777,
> in resolve
> raise DistributionNotFound(req, requirers)
> pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution
> was not found and is required by fonttools
> Unable to build the Hack-Regular variant set. Build canceled.
> make[2]: *** [Makefile:26: ttf] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/02/18/fonts-hack_3.003-3_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 ---
The fonttools unicodedata2 issue was not caused by these packages,
and after it got fixed, they build ok now.
Closing.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
Processed: Re: Bug#1000188: python3.10: testsuite gets stuck in a loop on buildds
Processing control commands: > severity -1 serious Bug #1000188 [src:python3.10] python3.10: testsuite gets stuck in a loop on buildds Severity set to 'serious' from 'important' -- 1000188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005477: marked as done (comic-neue: FTBFS: pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution was not found and is required by fonttools)
Your message dated Mon, 7 Mar 2022 11:23:05 +0100
with message-id
and subject line Re: Bug#1005477: comic-neue: FTBFS:
pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution was
not found and is required by fonttools
has caused the Debian Bug report #1005477,
regarding comic-neue: FTBFS: pkg_resources.DistributionNotFound: The
'unicodedata2>=14.0.0' distribution was not found and is required by fonttools
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.)
--
1005477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: comic-neue
Version: 2.51-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 '/<>'
> for glyph in Sources/Glyphs/ComicNeue_Italics.glyphs
> Sources/Glyphs/ComicNeue_Roman.glyphs ; \
> do \
> fontmake -i -o otf -g ${glyph} ; \
> done
> Traceback (most recent call last):
> File "/usr/bin/fontmake", line 33, in
> sys.exit(load_entry_point('fontmake==2.4.1', 'console_scripts',
> 'fontmake')())
> File "/usr/bin/fontmake", line 25, in importlib_load_entry_point
> return next(matches).load()
> File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
> module = import_module(match.group('module'))
> File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1030, in _gcd_import
> File "", line 1007, in _find_and_load
> File "", line 986, in _find_and_load_unlocked
> File "", line 680, in _load_unlocked
> File "", line 850, in exec_module
> File "", line 228, in _call_with_frames_removed
> File "/usr/lib/python3/dist-packages/fontmake/__main__.py", line 20, in
>
> from ufo2ft import CFFOptimization
> File "/usr/lib/python3/dist-packages/ufo2ft/__init__.py", line 8, in
>
> from ufo2ft.featureCompiler import (
> File "/usr/lib/python3/dist-packages/ufo2ft/featureCompiler.py", line 14,
> in
> from ufo2ft.featureWriters import (
> File "/usr/lib/python3/dist-packages/ufo2ft/featureWriters/__init__.py",
> line 11, in
> from .markFeatureWriter import MarkFeatureWriter
> File
> "/usr/lib/python3/dist-packages/ufo2ft/featureWriters/markFeatureWriter.py",
> line 9, in
> from ufo2ft.fontInfoData import getAttrWithFallback
> File "/usr/lib/python3/dist-packages/ufo2ft/fontInfoData.py", line 23, in
>
> from fontTools import ufoLib
> File "/usr/lib/python3/dist-packages/fontTools/ufoLib/__init__.py", line 8,
> in
> import fs
> File "/usr/lib/python3/dist-packages/fs/__init__.py", line 4, in
> __import__("pkg_resources").declare_namespace(__name__) # type: ignore
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3267,
> in
> def _initialize_master_working_set():
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3241,
> in _call_aside
> f(*args, **kwargs)
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3279,
> in _initialize_master_working_set
> working_set = WorkingSet._build_master()
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 573,
> in _build_master
> ws.require(__requires__)
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 891,
> in require
> needed = self.resolve(parse_requirements(requirements))
> File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 777,
> in resolve
> raise DistributionNotFound(req, requirers)
> pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution
> was not found and is required by fonttools
> Traceback (most recent call last):
> File "/usr/bin/fontmake", line 33, in
> sys.exit(load_entry_point('fontmake==2.4.1', 'console_scripts',
> 'fontmake')())
> File "/usr/bin/fontmake", line 25, in importlib_load_entry_point
> return next(matches).load()
> File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
> module = import_module(match.group('module'))
> File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> File "", line 1030, in _gcd_import
> File "", line 1007, in _find_and_load
> File "", line 986, in _find_and_load_unlocked
> File "", line
Bug#1005376: marked as pending in procps
Control: tag -1 pending Hello, Bug #1005376 in procps reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/procps/-/commit/bfbb15f8107afd16791a085be872b8c1a48df093 kill: Correctly handle negative pids Closes: #1005376 References: https://gitlab.com/procps-ng/procps/-/commit/79097e55e4b08ec8c1de8332e32cf03c4be1d4ec (this message was generated automatically) -- Greetings https://bugs.debian.org/1005376
Processed: Bug#1005376 marked as pending in procps
Processing control commands: > tag -1 pending Bug #1005376 [procps] kill(1) with negative PIDs kills the current process group Ignoring request to alter tags of bug #1005376 to the same tags previously set -- 1005376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1005376 marked as pending in procps
Processing control commands: > tag -1 pending Bug #1005376 [procps] kill(1) with negative PIDs kills the current process group Added tag(s) pending. -- 1005376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005376: marked as pending in procps
Control: tag -1 pending Hello, Bug #1005376 in procps reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/procps/-/commit/612df76f2484060eb580e748b327dbb538ab0076 kill: Correctly handle negative pids Closes: #1005376 References: https://gitlab.com/procps-ng/procps/-/commit/79097e55e4b08ec8c1de8332e32cf03c4be1d4ec (this message was generated automatically) -- Greetings https://bugs.debian.org/1005376
