Processed: closing 1031576
Processing commands for cont...@bugs.debian.org: > close 1031576 Bug #1031576 [src:vulkan-validationlayers] vulkan-validationlayers: FTBFS in testing: vk_sdk_platform.h:27:2: error: #warning "vk_sdk_platform.h is deprecated and will be removed in future release! Use VK_SDK_PLATFORM_SUPRRESS_DEPRECATION_WARNING to suppress warning!" [-Werror=cpp] Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1031576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055319: rust-rustls-webpki autopkgtest failure.
Package: rust-rustls-webpki Version: 0.101.6-1 Severity: serious The autopkgtest for rust-rustls-webpki fails with 238s error[E0583]: file not found for module `test_utils` 238s --> src/lib.rs:65:1 238s| 238s 65 | pub(crate) mod test_utils; 238s| ^^ 238s| 238s= help: to create the module `test_utils`, create file "src/test_utils.rs" or "src/test_utils/mod.rs" This bug affects both the versions in unstable and experimental. It does not affect the version currently in testing. It appears that the file src/test_utils.rs is included in the source package but is not making it into the binary package for some reason.
Bug#1052915: libdnf: FTBFS: dh_install: error: missing files, aborting
Looks like there was another issue, that only happens on sbuild/buildd but not on pbuilder, a missing "-p" for mkdir in d/rules: >debian/rules override_dh_auto_test > make[1]: Entering directory '/<>' > mkdir '/<>/debian/tests-home' > mkdir: cannot create directory ‘/<>/debian/tests-home’: File > exists > make[1]: *** [debian/rules:52: override_dh_auto_test] Error 1 Uploaded a new NMU, full debdiff attached. -- Kind regards, Luca Boccassi --- libdnf-0.69.0/debian/changelog 2023-01-08 09:08:51.0 + +++ libdnf-0.69.0/debian/changelog 2023-11-03 19:22:17.0 + @@ -1,3 +1,17 @@ +libdnf (0.69.0-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Use mkdir -p in override_dh_auto_test to fix FTBFS on buildds + + -- Luca Boccassi Fri, 03 Nov 2023 19:22:17 + + +libdnf (0.69.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Move python3 modules from /usr/lib/local/ (Closes: #1052915) + + -- Luca Boccassi Sun, 29 Oct 2023 15:57:28 + + libdnf (0.69.0-2) unstable; urgency=medium * Set myself to maintainer diff -Nru libdnf-0.69.0/debian/python3-hawkey.install libdnf-0.69.0/debian/python3-hawkey.install --- libdnf-0.69.0/debian/python3-hawkey.install 2022-11-12 22:06:07.0 + +++ libdnf-0.69.0/debian/python3-hawkey.install 2023-11-03 19:17:26.0 + @@ -1 +1 @@ -usr/local/lib/python3.*/dist-packages/hawkey +usr/lib/python3/dist-packages/hawkey diff -Nru libdnf-0.69.0/debian/python3-libdnf.install libdnf-0.69.0/debian/python3-libdnf.install --- libdnf-0.69.0/debian/python3-libdnf.install 2022-11-12 22:06:07.0 + +++ libdnf-0.69.0/debian/python3-libdnf.install 2023-11-03 19:17:11.0 + @@ -1 +1 @@ -usr/local/lib/python3.*/dist-packages/libdnf +usr/lib/python3/dist-packages/libdnf diff -Nru libdnf-0.69.0/debian/rules libdnf-0.69.0/debian/rules --- libdnf-0.69.0/debian/rules 2022-11-12 22:05:59.0 + +++ libdnf-0.69.0/debian/rules 2023-11-03 19:21:34.0 + @@ -49,7 +49,7 @@ dh_auto_clean --builddirectory=build override_dh_auto_test: - mkdir '$(CURDIR)/debian/tests-home' + mkdir -p '$(CURDIR)/debian/tests-home' LC_ALL=C HOME='$(CURDIR)/debian/tests-home' dh_auto_test --builddirectory=build -- ARGS='-V' override_dh_missing: signature.asc Description: This is a digitally signed message part
Processed: Re: gamin: unmaintained upstream
Processing control commands: > tags -1 - wontfix Bug #1008205 [src:gamin] gamin: unmaintained upstream Removed tag(s) wontfix. > retitle -1 RM: gamin -- RoQA; dead upstream Bug #1008205 [src:gamin] gamin: unmaintained upstream Changed Bug title to 'RM: gamin -- RoQA; dead upstream' from 'gamin: unmaintained upstream'. > severity -1 serious Bug #1008205 [src:gamin] RM: gamin -- RoQA; dead upstream Severity set to 'serious' from 'important' -- 1008205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055150: a2d: apt remove a2k nukes user data (postinst)
Hi, I have revised postrm not to remove user config files. I let the dpkg to take care of config files. Thank you, Yogeswaran Umasankar
Processed: Re: devscripts: FTBFS fails in test test/test_debchange
Processing commands for cont...@bugs.debian.org: > severity 1051924 serious Bug #1051924 [devscripts] devscripts: FTBFS fails in test test/test_debchange Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1051924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: pgpainless: FTBFS: make[1]: *** [debian/rules:40: override_dh_auto_test] Error 1
Processing commands for cont...@bugs.debian.org: > # also happens in bookworm > tags 1054771 + bookworm Bug #1054771 [src:pgpainless] pgpainless: FTBFS: make[1]: *** [debian/rules:40: override_dh_auto_test] Error 1 Added tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1054771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054771 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ruby-puppetserver-ca-cli: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: csr.add_attribute(extension_attribute(extensions))
Processing commands for cont...@bugs.debian.org: > # also happens in bookworm > tags 1052722 + bookworm Bug #1052722 [src:ruby-puppetserver-ca-cli] ruby-puppetserver-ca-cli: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: csr.add_attribute(extension_attribute(extensions)) Added tag(s) bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1052722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: libgovirt: FTBFS randomly (Could not connect to localhost: Connection refused)
Processing commands for cont...@bugs.debian.org: > severity 1030904 serious Bug #1030904 [src:libgovirt] libgovirt: FTBFS randomly (Could not connect to localhost: Connection refused) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1030904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: node-wikibase-cli: FTBFS: TypeError: Cannot read properties of undefined (reading 'Q11')
Processing commands for cont...@bugs.debian.org: > # also happens in bookworm > tags 1042298 + bookworm Bug #1042298 [src:node-wikibase-cli] node-wikibase-cli: FTBFS: TypeError: Cannot read properties of undefined (reading 'Q11') Added tag(s) bookworm. > End of message, stopping processing here. Please contact me if you need assistance. -- 1042298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1055106 marked as pending in django-tables
Processing control commands:
> tag -1 pending
Bug #1055106 {Done: Carsten Schoenert }
[src:django-tables] Test failure prevents Django 4.x from entering in testing
Added tag(s) pending.
--
1055106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1055106: marked as pending in django-tables
Control: tag -1 pending Hello, Bug #1055106 in django-tables reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/django-tables/-/commit/52c39aaa33729f9183f89da15c5dbdd56c8972c4 autopkgtest: Adjust test syntax The root cause is that url() function was deprecated since Django 3.1 [3] and removed in Django 4.x Closes: #1055106 (this message was generated automatically) -- Greetings https://bugs.debian.org/1055106
Bug#1055106: marked as done (Test failure prevents Django 4.x from entering in testing)
Your message dated Fri, 03 Nov 2023 20:35:19 + with message-id and subject line Bug#1055106: fixed in django-tables 2.6.0-2 has caused the Debian Bug report #1055106, regarding Test failure prevents Django 4.x from entering in testing 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.) -- 1055106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:django-tables Version: 2.6.0-1 Severity: grave Tags: patch Dear Maintainer, Tests fail on Debian CI infrastructure [1] and on my local machine as well (full log attached). This failure prevents python-django (3:4.2.6-1) from entering in testing [2]. $> autopkgtest --no-built-binaries django-tables_2.6.0-1.dsc -- null ... ... ImportError: cannot import name 'url' from 'django.conf.urls' (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) autopkgtest [14:12:24]: test test-run-py3: ---] autopkgtest [14:12:24]: test test-run-py3: - - - - - - - - - - results - - - - - - - - - - test-run-py3 FAIL non-zero exit status 1 autopkgtest [14:12:24]: summary command1 PASS test-run-py3 FAIL non-zero exit status 1 The root cause is that url() function was deprecated since Django 3.1 [3] and removed in Django 4.x Attached patch addresses the failure. Kind Regards [1] https://ci.debian.net/data/autopkgtest/unstable/amd64/d/django-tables/39070283/log.gz [2] https://qa.debian.org/excuses.php?package=python-django [3] https://code.djangoproject.com/ticket/31534--- django-tables-2.6.0/debian/tests/test-run-py3 2023-05-25 15:35:19.0 + +++ django-tables-2.6.0/debian/tests/test-run-py3-new 2023-10-31 14:37:50.661433357 + @@ -45,14 +45,14 @@ cat > testproject/urls.py << __EOF__ -from django.conf.urls import url +from django.urls import re_path from django.contrib import admin from tutorial.views import people urlpatterns = [ -url(r'^admin/', admin.site.urls), -url(r'^people/', people) +re_path(r'^admin/', admin.site.urls), +re_path(r'^people/', people) ] __EOF__ full_log.tar.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: django-tables Source-Version: 2.6.0-2 Done: Carsten Schoenert We believe that the bug you reported is fixed in the latest version of django-tables, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carsten Schoenert (supplier of updated django-tables package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 Nov 2023 21:12:40 +0100 Source: django-tables Architecture: source Version: 2.6.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Carsten Schoenert Closes: 1044842 1055106 Changes: django-tables (2.6.0-2) unstable; urgency=medium . * Team upload. [ s3v ] * [52c39aa] autopkgtest: Adjust test syntax (Closes: #1055106) . [ Carsten Schoenert ] * [707b808] d/rules: Remove potential symlink in dh_clean (Closes: #1044842) Checksums-Sha1: dc150e60cc89ce63149c51150c76ff6407aa8ccc 2780 django-tables_2.6.0-2.dsc c2a59369c8da7f261eef8682581ef2ab66e542a9 10260 django-tables_2.6.0-2.debian.tar.xz 87d4eb1e251bad9469ad88530364965be64b74ce 9640 django-tables_2.6.0-2_amd64.buildinfo Checksums-Sha256: 19295c7924e29af7825117c4cc016b371d927b177ad70d30dee0e29c7df59d2a 2780 django-tables_2.6.0-2.dsc 98e0b16c7e6436e3446720cf34bf4f3c87bcdb4668cb2a13120d59633f054057 10260 django-tables_2.6.0-2.debian.tar.xz 03abef766ba8647bf73396fe31f28242439caaef9a999b0a45629e32d37daf2a 9640 django-tables_2.6.0-2_amd64.buildinfo Files: 474816bcc20aa4357a04b3511327c222 2780 python optional django-tables_2.6.0-2.dsc e45ac7f1a4b2e92d91fe45ff0cf73582 10260 python optional django-tables_2.6.0-2.debian.tar.xz 0e86984e0d0d704f3e102261769f7990 9640 python optional django-tables_2.6.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAmVFVUcACgkQgwFgFCUd
Processed: Re: Bug#1052002: firefox: FTBFS: ERROR: Cannot find wasi headers or problem with the wasm compiler. Please fix the problem. Or build with --without-wasm-sandboxed-libraries
Processing control commands:
> reopen -1
Bug #1052002 {Done: Sylvestre Ledru } [clang-16] firefox:
FTBFS: ERROR: Cannot find wasi headers or problem with the wasm compiler.
Please fix the problem. Or build with --without-wasm-sandboxed-libraries
'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 llvm-toolchain-16/1:16.0.6-17.
> found -1 1:16.0.6-17
Bug #1052002 [clang-16] firefox: FTBFS: ERROR: Cannot find wasi headers or
problem with the wasm compiler. Please fix the problem. Or build with
--without-wasm-sandboxed-libraries
Marked as found in versions llvm-toolchain-16/1:16.0.6-17.
--
1052002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1052002: firefox: FTBFS: ERROR: Cannot find wasi headers or problem with the wasm compiler. Please fix the problem. Or build with --without-wasm-sandboxed-libraries
Control: reopen -1
Control: found -1 1:16.0.6-17
This is still not fixed :( Mike's findings still stand:
On Sat, Sep 16, 2023 at 05:53:55AM +0900, Mike Hommey wrote:
> This is a regression from the upgrade to clang 16.
>
> with clang 14:
> #include "..." search starts here:
> #include <...> search starts here:
> /usr/include/wasm32-wasi/c++/v1
> /usr/lib/llvm-14/lib/clang/14.0.6/include
> /usr/local/include
> /usr/include/wasm32-wasi
> /usr/include
> End of search list.
>
> with clang 16:
> #include "..." search starts here:
> #include <...> search starts here:
> /usr/lib/llvm-16/lib/clang/16/include
> /usr/local/include
> /usr/include/wasm32-wasi
> /usr/include
> End of search list.
>
> Note how /usr/include/wasm32-wasi/c++/v1 is missing.
Test case:
$ apt install clang lld libclang-rt-dev-wasm32 libc++-dev-wasm32
$ cat > hello.cpp <
int main() {
std::cout << "hello world" << std::endl;
return 0;
}
EOF
$ /usr/bin/clang++ -v --target=wasm32-wasi hello.cpp
Only C++ include paths are affected, not C. This almost certainly has to
do with the patch we carry for wasm include paths, that I have
contributed to. Unfortunately I have no time to look into it right now
:( I may find some time in a couple of weeks, but hoping someone else
can take care of it in the meantime :/
Best,
Faidon
Processed: Bug#1042602 marked as pending in sphinx-panels
Processing control commands:
> tag -1 pending
Bug #1042602 [src:sphinx-panels] sphinx-panels: FTBFS with Sphinx 7.1, docutils
0.20: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
3.11 returned exit code 13
Added tag(s) pending.
--
1042602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042602: marked as pending in sphinx-panels
Control: tag -1 pending Hello, Bug #1042602 in sphinx-panels reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/sphinx-panels/-/commit/1f3d878102410405119f5633b807b16f39060282 Add a patch to make the tests pass with Sphinx 7. Closes: #1042602. (this message was generated automatically) -- Greetings https://bugs.debian.org/1042602
Processed: found 1053004 in 5.1+ds-4, found 1053004 in 7.13.0+dfsg-2
Processing commands for cont...@bugs.debian.org: > found 1053004 5.1+ds-4 Bug #1053004 [src:phppgadmin] phppgadmin: CVE-2023-40619 Marked as found in versions phppgadmin/5.1+ds-4. > found 1053004 7.13.0+dfsg-2 Bug #1053004 [src:phppgadmin] phppgadmin: CVE-2023-40619 Ignoring request to alter found versions of bug #1053004 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1053004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1053004 is grave
Processing commands for cont...@bugs.debian.org: > severity 1053004 grave Bug #1053004 [src:phppgadmin] phppgadmin: CVE-2023-40619 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1053004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052821: marked as done (python-phx-class-registry: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Fri, 03 Nov 2023 19:25:58 +
with message-id
and subject line Bug#1052821: fixed in python-phx-class-registry 4.1.0-1
has caused the Debian Bug report #1052821,
regarding python-phx-class-registry: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 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.)
--
1052821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-phx-class-registry
Version: 3.0.5-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:291: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.11_phx-class-registry/build/class_registry
> copying class_registry/cache.py ->
> /<>/.pybuild/cpython3_3.11_phx-class-registry/build/class_registry
> copying class_registry/entry_points.py ->
> /<>/.pybuild/cpython3_3.11_phx-class-registry/build/class_registry
> copying class_registry/__init__.py ->
> /<>/.pybuild/cpython3_3.11_phx-class-registry/build/class_registry
> copying class_registry/auto_register.py ->
> /<>/.pybuild/cpython3_3.11_phx-class-registry/build/class_registry
> copying class_registry/patcher.py ->
> /<>/.pybuild/cpython3_3.11_phx-class-registry/build/class_registry
> copying class_registry/registry.py ->
> /<>/.pybuild/cpython3_3.11_phx-class-registry/build/class_registry
> PYTHONPATH=. http_proxy='127.0.0.1:9' python3 -m sphinx -N -bhtml docs
> build/html
> Running Sphinx v5.3.0
> WARNING: Invalid configuration value found: 'language = None'. Update your
> configuration to a valid language code. Falling back to 'en' (English).
> making output directory... done
> WARNING: html_static_path entry '_static' does not exist
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 6 source files that are out of date
> updating environment: [new config] 6 added, 0 changed, 0 removed
> reading sources... [ 16%] advanced_topics
> reading sources... [ 33%] entry_points
> reading sources... [ 50%] factories_vs_registries
> reading sources... [ 66%] getting_started
> reading sources... [ 83%] index
> reading sources... [100%] iterating_over_registries
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 16%] advanced_topics
> writing output... [ 33%] entry_points
> writing output... [ 50%] factories_vs_registries
> writing output... [ 66%] getting_started
> writing output... [ 83%] index
> writing output... [100%] iterating_over_registries
>
> generating indices... genindex done
> writing additional pages... search done
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 2 warnings.
>
> The HTML pages are in build/html.
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:291: cd
> /<>/.pybuild/cpython3_3.11_phx-class-registry/build; python3.11
> -m pytest test
> = test session starts
> ==
> platform linux -- Python 3.11.5, pytest-7.4.2, pluggy-1.3.0
> rootdir: /<>
> collected 24 items
>
> test/auto_register_test.py ... [
> 12%]
> test/cache_test.py ... [
> 25%]
> test/entry_points_test.py F.FF [
> 41%]
> test/patcher_test.py .. [
> 50%]
> test/registry_test.py
> [100%]
>
> === FAILURES
> ===
> EntryPointClassRegistryTestCase.test_branding
> _
>
> self = testMethod=test_branding>
>
> def test_branding(self):
> """
> Configuring the registry to "brand" each class/instance with its
> corresponding key.
> """
> registry = EntryPointClassRegistry('pokemon', attr_name='poke_type')
> try:
> # Branding is applied immediately to each registered class.
> >
Bug#1054323: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected
Hi Andreas,
On 03-11-2023 07:11, Andreas Tille wrote:
I did not used a tight Depends (see r-cran-matrix (>= $${rmbversion}) in
[1]) but I think the check you suggested to patch out will fire for new
Matrix versions.
Hence, if you really want to do this version dance (which I prefer we
don't, but I agree aligning with upstream is good), I think we prefer
the tight versioned dependency. Because than it shows up in the
transition overview and it's clear it needs a rebuild (I guess binNMU
now should work). A "mere" regression just blocks r-cran-matrix until
somebody informs you (typically me, but only after one month), which is
annoying for everyone involved.
BTW, now we have a new kind of regression[2]
56s Error: (converted from warning) package ‘TMB’ was built under R version
4.3.2
I have no idea how to fix this from my side.
Well, exactly the same trick, but instead of r-cran-matrix on one of the
core r things? Or block that "converted from warning" thing from
converting warnings to errors.
Paul
[1] https://release.debian.org/transitions/
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1042125: marked as done (robot-testing-framework: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Fri, 03 Nov 2023 18:39:02 + with message-id and subject line Bug#1037843: fixed in robot-testing-framework 2.0.1+ds1-3 has caused the Debian Bug report #1037843, regarding robot-testing-framework: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below 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.) -- 1037843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: robot-testing-framework Version: 2.0.1+ds1-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_installexamples -plibrobottestingframework-doc > --doc-main-package=robot-testing-framework > dh_installexamples --remaining-packages > dh_installexamples: warning: No packages to build. Possible architecture > mismatch: amd64, want: all any > make[1]: Leaving directory '/<>' >dh_installexamples -Nlibrobottestingframework-doc >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: warning: debian/librobottestingframework2/DEBIAN/symbols > doesn't match completely debian/librobottestingframework2.symbols > --- debian/librobottestingframework2.symbols > (librobottestingframework2_2.0.1+ds1-2_amd64) > +++ dpkg-gensymbolsSVMRME 2023-07-26 19:15:36.916556396 + > @@ -235,6 +235,7 @@ > > _ZNSt6thread11_State_implINS_8_InvokerISt5tupleIJPFvPvEPN21robottestingframework23WebProgressListenerImplEED0Ev@Base > 2.0.0 > > _ZNSt6thread11_State_implINS_8_InvokerISt5tupleIJPFvPvEPN21robottestingframework23WebProgressListenerImplEED1Ev@Base > 2.0.0 > > _ZNSt6thread11_State_implINS_8_InvokerISt5tupleIJPFvPvEPN21robottestingframework23WebProgressListenerImplEED2Ev@Base > 2.0.0 > + _ZNSt6thread24_M_thread_deps_never_runEv@Base 2.0.1+ds1-2 > > _ZNSt6vectorIN21robottestingframework23WebProgressListenerImpl10TestStatusESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base > 2.0.0 > > _ZNSt6vectorIPN21robottestingframework11ResultEventESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base > 2.0.0 > > _ZNSt6vectorIPN21robottestingframework14FixtureManagerESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base > 2.0.0 > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/librobottestingframework-dll2/DEBIAN/symbols > doesn't match completely debian/librobottestingframework-dll2.symbols > --- debian/librobottestingframework-dll2.symbols > (librobottestingframework-dll2_2.0.1+ds1-2_amd64) > +++ dpkg-gensymbolssIXP3N 2023-07-26 19:15:37.068557101 + > @@ -71,7 +71,7 @@ > _ZNK7shlibpp20SharedLibraryFactory7isValidEv@Base 2.0.0 > _ZNK7shlibpp20SharedLibraryFactory8getErrorB5cxx11Ev@Base 2.0.0 > _ZNK7shlibpp20SharedLibraryFactory9getStatusEv@Base 2.0.0 > - > _ZStplIcSt11char_traitsIcESaIcEENSt7__cxx1112basic_stringIT_T0_T1_EEPKS5_RKS8_@Base > 2.0.0 > +#MISSING: 2.0.1+ds1-2# > _ZStplIcSt11char_traitsIcESaIcEENSt7__cxx1112basic_stringIT_T0_T1_EEPKS5_RKS8_@Base > 2.0.0 > _ZTI19DllPluginLoaderImplIN21robottestingframework14FixtureManagerEE@Base > 2.0.0 > _ZTI19DllPluginLoaderImplIN21robottestingframework8TestCaseEE@Base 2.0.0 > _ZTIN21robottestingframework6plugin12PluginLoaderE@Base 2.0.0 > dh_makeshlibs: error: failing due to earlier errors > make: *** [debian/rules:11: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/07/26/robot-testing-framework_2.0.1+ds1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See
Bug#1037843: marked as done (robot-testing-framework: ftbfs with GCC-13)
Your message dated Fri, 03 Nov 2023 18:39:02 + with message-id and subject line Bug#1037843: fixed in robot-testing-framework 2.0.1+ds1-3 has caused the Debian Bug report #1037843, regarding robot-testing-framework: ftbfs with GCC-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.) -- 1037843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:robot-testing-framework Version: 2.0.1+ds1-2 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/robot-testing-framework_2.0.1+ds1-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/dll/SharedLibraryClassApi.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/dll/SharedLibraryClassFactory.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/dll/SharedLibraryFactory.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/dll/Vocab.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/dll/robottestingframework_dll_config.h -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/librobottestingframework-lua.so.2 -- Set runtime path of "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/librobottestingframework-lua.so.2" to "" -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/librobottestingframework-lua.so -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/lua/LuaPluginLoader.h -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/librobottestingframework-ruby.so.2 -- Set runtime path of "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/librobottestingframework-ruby.so.2" to "" -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/librobottestingframework-ruby.so -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/robottestingframework/ruby/RubyPluginLoader.h -- Installing: /<>/debian/tmp/usr/bin/robottestingframework-testrunner -- Set runtime path of "/<>/debian/tmp/usr/bin/robottestingframework-testrunner" to "" make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_install debian/rules override_dh_installdocs-indep make[1]: Entering directory '/<>' dh_installdocs -plibrobottestingframework-doc --doc-main-package=robot-testing-framework -Xjquery.js dh_installdocs --remaining-packages dh_installdocs: warning: No packages to build. Possible architecture mismatch: amd64, want: all any dh_doxygen -plibrobottestingframework-doc make[1]: Leaving directory '/<>' dh_installdocs -Nlibrobottestingframework-doc dh_installchangelogs debian/rules override_dh_installexamples-indep make[1]: Entering directory '/<>' dh_installexamples -plibrobottestingframework-doc --doc-main-package=robot-testing-framework dh_installexamples --remaining-packages dh_installexamples: warning: No packages to build. Possible architecture mismatch: amd64, want: all any make[1]: Leaving directory '/<>' dh_installexamples -Nlibrobottestingframework-doc dh_perl dh_link dh_strip_nondeterminism dh_compress dh_fixperms dh_missing dh_dwz -a dh_strip -a dh_makeshlibs -a dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/librobottestingframework2/DEBIAN/symbols doesn't match completely debian/librobottestingframework2.symbols ---
Processed: Bug#1052821 marked as pending in python-phx-class-registry
Processing control commands:
> tag -1 pending
Bug #1052821 [src:python-phx-class-registry] python-phx-class-registry: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11
returned exit code 13
Added tag(s) pending.
--
1052821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1052821: marked as pending in python-phx-class-registry
Control: tag -1 pending Hello, Bug #1052821 in python-phx-class-registry reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-phx-class-registry/-/commit/79a14cdee53c6663a6c0a3622f279aa7ba9b6ac1 Move back and forth egg-info test directory to prevent pybuild from removing it (Closes: #1052821) (this message was generated automatically) -- Greetings https://bugs.debian.org/1052821
Bug#1052804: ycmd: FTBFS: make[1]: *** [debian/rules:28: override_dh_auto_test] Error 1
Control: forwarded -1 https://github.com/ycm-core/ycmd/issues/1718 Hi, the problem is that upstream code isn't supporting Unicode 15.1 yet, which introduced a new word break rule. They embed the code (for 13), but for Debian I opted to drop the embed and use whatever unicode-data ships to rebuild the files, which bites us in the rear end here – as it kinda should be. I reported upstream and they have a PR implementing the needed support already as well: https://github.com/ycm-core/ycmd/pull/1719 As said there it works fine for me in local tests, so this issue here should be resolvable in the near future. vim-youcompleteme (which is a rdepends of ycmd) is currently affected by a regression in vim through (https://bugs.debian.org/1055287) which makes updating ycmd with the unmerged upstream patch not that useful for now (as it would never migrate – or, well, battle with vim for a spot). So, I am currently waiting for either vim or upstream to act first while dealing with other housekeeping things (clang-17 support) in the meantime; so much as a status report in case anyone wonders. Best regards David Kalnischkies signature.asc Description: PGP signature
Processed: Re: Bug#1052804: ycmd: FTBFS: make[1]: *** [debian/rules:28: override_dh_auto_test] Error 1
Processing control commands: > forwarded -1 https://github.com/ycm-core/ycmd/issues/1718 Bug #1052804 [src:ycmd] ycmd: FTBFS: make[1]: *** [debian/rules:28: override_dh_auto_test] Error 1 Set Bug forwarded-to-address to 'https://github.com/ycm-core/ycmd/issues/1718'. -- 1052804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1055275 is important
Processing commands for cont...@bugs.debian.org: > severity 1055275 important Bug #1055275 [dhcpcd] dhcpcd: Version 10.0.4 fails to fork in the background Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 1055275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041458: marked as done (colmap: FTBFS on i386)
Your message dated Fri, 3 Nov 2023 19:17:25 +0100 with message-id and subject line colmap: FTBFS on i386 has caused the Debian Bug report #1041458, regarding colmap: FTBFS on 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.) -- 1041458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: colmap Version: 3.8-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=colmap=i386=3.8-1%2Bb1=1689694063=0 [ 92%] Building CXX object src/CMakeFiles/colmap.dir/colmap_autogen/UYX5XTB5RZ/qrc_resources.cpp.o cd /<>/obj-i686-linux-gnu/src && /usr/bin/c++ -DBOOST_ALL_NO_LIB -DGFLAGS_IS_A_DLL=0 -DGLOG_CUSTOM_PREFIX_SUPPORT -DGUI_ENABLED -DOPENGL_ENABLED -DOPENMP_ENABLED -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -I/<>/lib -I/<>/src -isystem /usr/include/eigen3 -isystem /usr/include/i386-linux-gnu/qt5 -isystem /usr/include/i386-linux-gnu/qt5/QtCore -isystem /usr/lib/i386-linux-gnu/qt5/mkspecs/linux-g++ -isystem /usr/include/i386-linux-gnu/qt5/QtOpenGL -isystem /usr/include/i386-linux-gnu/qt5/QtWidgets -isystem /usr/include/i386-linux-gnu/qt5/QtGui -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DDISABLE_CPU_NEON -Wno-maybe-uninitialized -fopenmp -Wall -std=c++14 -fPIC -fPIC -MD -MT src/CMakeFiles/colmap.dir/colmap_autogen/UYX5XTB5RZ/qrc_resources.cpp.o -MF CMakeFiles/colmap.dir/colmap_autogen/UYX5XTB5RZ/qrc_resources.cpp.o.d -o CMakeFiles/colmap.dir/colmap_autogen/UYX5XTB5RZ/qrc_resources.cpp.o -c /<>/obj-i686-linux-gnu/src/colmap_autogen/UYX5XTB5RZ/qrc_resources.cpp cc1plus: out of memory allocating 72 bytes after a total of 89124864 bytes make[3]: *** [src/CMakeFiles/colmap.dir/build.make:657: src/CMakeFiles/colmap.dir/estimators/generalized_absolute_pose_coeffs.cc.o] Error 1 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- has been fixed in sid--- End Message ---
Bug#1054675: marked as done (genomicsdb: FTBFS: catch.h:50:10: fatal error: catch2/catch.hpp: No such file or directory)
Your message dated Fri, 03 Nov 2023 18:05:45 + with message-id and subject line Bug#1054675: fixed in genomicsdb 1.5.0-2 has caused the Debian Bug report #1054675, regarding genomicsdb: FTBFS: catch.h:50:10: fatal error: catch2/catch.hpp: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: genomicsdb Version: 1.5.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86_64-linux-gnu/genomicsdb-tiledb/test && > /usr/bin/c++ -DCATCH2_MAJOR_VERSION=2 -DENABLE_ZSTD -DHAVE_OPENMP > -DTILEDB_TEST_DIR=\"/<>/genomicsdb-tiledb/test\" > -DTILEDB_VERBOSE -D_FILE_OFFSET_BITS=64 -I/<>/genomicsdb-htslib > -I/usr/include/muparserx > -I/<>/genomicsdb-tiledb/test/include/benchmark > -I/<>/genomicsdb-tiledb/test/include/c_api > -I/<>/genomicsdb-tiledb/test/include/catch2 > -I/<>/genomicsdb-tiledb/test/../core/include/array > -I/<>/genomicsdb-tiledb/test/../core/include/c_api > -I/<>/genomicsdb-tiledb/test/../core/include/codec > -I/<>/genomicsdb-tiledb/test/../core/include/expressions > -I/<>/genomicsdb-tiledb/test/../core/include/fragment > -I/<>/genomicsdb-tiledb/test/../core/include/metadata > -I/<>/genomicsdb-tiledb/test/../core/include/misc > -I/<>/genomicsdb-tiledb/test/../core/include/storage_manager -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 > -Wno-literal-suffix -fopenmp -std=c++17 -MD -MT > genomicsdb-tiledb/test/CMakeFiles/test_array_schema.dir/src/array/test_array_schema.cc.o > -MF CMakeFiles/test_array_schema.dir/src/array/test_array_schema.cc.o.d -o > CMakeFiles/test_array_schema.dir/src/array/test_array_schema.cc.o -c > /<>/genomicsdb-tiledb/test/src/array/test_array_schema.cc > In file included from > /<>/genomicsdb-tiledb/test/src/array/test_array_schema.cc:38: > /<>/genomicsdb-tiledb/test/include/catch2/catch.h:50:10: fatal > error: catch2/catch.hpp: No such file or directory >50 | #include > | ^~ > compilation terminated. > make[4]: *** > [genomicsdb-tiledb/test/CMakeFiles/test_array_schema.dir/build.make:79: > genomicsdb-tiledb/test/CMakeFiles/test_array_schema.dir/src/array/test_array_schema.cc.o] > Error 1 The full build log is available from: http://qa-logs.debian.net/2023/10/27/genomicsdb_1.5.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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: genomicsdb Source-Version: 1.5.0-2 Done: Pierre Gruet We believe that the bug you reported is fixed in the latest version of genomicsdb, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre Gruet (supplier of updated genomicsdb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 Nov 2023 17:16:04 +0100 Source: genomicsdb Architecture: source Version: 1.5.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Pierre Gruet Closes: 1054675 Changes: genomicsdb (1.5.0-2) unstable;
Bug#1055267: marked as done (libreoffice-uiconfig-*: missing Breaks for the Replaces)
Your message dated Fri, 03 Nov 2023 17:32:06 + with message-id and subject line Bug#1055267: fixed in libreoffice 4:7.6.3~rc1-2 has caused the Debian Bug report #1055267, regarding libreoffice-uiconfig-*: missing Breaks for the Replaces 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.) -- 1055267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libreoffice Version: 4:7.6.2-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts replaces-without-breaks Hi, during a test with piuparts and DOSE tools I noticed your package causes removal of files that also belong to another package. This is caused by using Replaces without corresponding Breaks. The installation sequence to reproduce this problem is apt-get install libreoffice-base-nogui/sid # (1) apt-get install libreoffice-uiconfig-base/experimental apt-get remove libreoffice-uiconfig-base # (2) The list of installed files at points (1) and (2) should be identical, but the following files have disappeared: usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/admindialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/advancedsettingsdialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/appborderwindow.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/appdetailwindow.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/applycolpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/appswapwindow.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/authentificationpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/autocharsetpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/choosedatasourcedialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/colcontrolbox.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/collectionviewdialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/colwidthdialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/connectionpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/copytablepage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbaseindexdialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbasepage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbtreelist.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbwizconnectionpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbwizmysqlintropage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbwizmysqlnativepage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbwizspreadsheetpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbwiztextpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/deleteallrowsdialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/designsavemodifieddialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/detailwindow.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/directsqldialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/emptypage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/fielddescpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/fielddescpanel.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/fielddialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/finalpagewizard.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/generalpagedialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/generalpagewizard.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/generalspecialjdbcdetailspage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/generatedvaluespage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/indexdesigndialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/jdbcconnectionpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/joindialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/jointablemenu.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/joinviewmenu.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/keymenu.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/ldapconnectionpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/ldappage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/limitbox.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/migrwarndlg.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/mysqlnativepage.ui
Bug#1037627: marked as done (dub: ftbfs with GCC-13)
Your message dated Fri, 03 Nov 2023 17:19:37 + with message-id and subject line Bug#1037627: fixed in dub 1.27.0-4 has caused the Debian Bug report #1037627, regarding dub: ftbfs with GCC-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.) -- 1037627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dub Version: 1.27.0-3 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/dub_1.27.0-3_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 debian/rules clean dh clean debian/rules override_dh_auto_clean make[1]: Entering directory '/<>' dh_auto_clean rm -f /<>/scripts/man/*.1 make[1]: Leaving directory '/<>' dh_clean debian/rules binary dh binary dh_update_autotools_config dh_autoreconf debian/rules override_dh_auto_build make[1]: Entering directory '/<>' gdmd -run /<>/build.d \ -g -O -w -release Wrote version_.d` file with version: 1.27.0-3 Building dub using gdmd (dflags: ["-g", "-O", "-w", "-release", "-frelease"]), this may take a while... Command `["gdmd", "-of/<>/bin/dub", "-I/<>/source", "-version=DubUseCurl", "-version=DubApplication", "-g", "-O", "-w", "-release", "-frelease", "@build-files.txt"]` failed, output was: Serializing composite type BuildRequirements which has no serializable fields Serializing composite type BuildOptions which has no serializable fields source/dub/internal/undead/xml.d:594:49: error: scope variable ‘o’ assigned to non-scope parameter ‘o’ calling ‘toType’ 594 | const doc = toType!(const Document)(o); | ^ source/dub/internal/undead/xml.d:614:49: error: scope variable ‘o’ assigned to non-scope parameter ‘o’ calling ‘toType’ 614 | const doc = toType!(const Document)(o); | ^ source/dub/internal/undead/xml.d:845:48: error: scope variable ‘o’ assigned to non-scope parameter ‘o’ calling ‘toType’ 845 | const element = toType!(const Element)(o); |^ source/dub/internal/undead/xml.d:869:48: error: scope variable ‘o’ assigned to non-scope parameter ‘o’ calling ‘toType’ 869 | const element = toType!(const Element)(o); |^ source/dub/internal/undead/xml.d:1280:42: error: scope variable ‘o’ assigned to non-scope parameter ‘o’ calling ‘toType’ 1280 | const item = toType!(const Item)(o); | ^ source/dub/internal/undead/xml.d:1299:42: error: scope variable ‘o’ assigned to non-scope parameter ‘o’ calling ‘toType’ 1299 | const item = toType!(const Item)(o); | ^ source/dub/internal/undead/xml.d:1368:42: error: scope variable ‘o’ assigned to non-scope parameter ‘o’ calling ‘toType’ 1368 | const item = toType!(const Item)(o); | ^ source/dub/internal/undead/xml.d:1387:42: error: scope variable ‘o’ assigned to non-scope parameter ‘o’ calling ‘toType’ 1387 | const item = toType!(const Item)(o); | ^ source/dub/internal/undead/xml.d:1445:42: error: scope variable ‘o’ assigned to non-scope parameter ‘o’ calling ‘toType’
Processed: Bug#1055267 marked as pending in libreoffice
Processing control commands: > tag -1 pending Bug #1055267 [src:libreoffice] libreoffice-uiconfig-*: missing Breaks for the Replaces Ignoring request to alter tags of bug #1055267 to the same tags previously set -- 1055267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055267: marked as pending in libreoffice
Control: tag -1 pending Hello, Bug #1055267 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/d2ebf999d53f47f1e21eb98f9895081976c77028 duplicate Replaces: as Breaks: in -uiconfig-* (closes: #1055267) (this message was generated automatically) -- Greetings https://bugs.debian.org/1055267
Bug#1055267: marked as pending in libreoffice
Control: tag -1 pending Hello, Bug #1055267 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/d2ebf999d53f47f1e21eb98f9895081976c77028 duplicate Replaces: as Breaks: in -uiconfig-* (closes: #1055267) (this message was generated automatically) -- Greetings https://bugs.debian.org/1055267
Processed: Bug#1055267 marked as pending in libreoffice
Processing control commands: > tag -1 pending Bug #1055267 [src:libreoffice] libreoffice-uiconfig-*: missing Breaks for the Replaces Added tag(s) pending. -- 1055267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030129: ca-certificates-java - Fails to install: Error loading java.security file
FWIW, I can still reproduce the problem with Debian 10 (yeah I know, I should upgrade :), by attempting to install build-essential and openjdk-11-jre-headless in one apt-get invocation. E.g. using a simple Dockerfile: == FROM debian:10 RUN DEBIAN_FRONTEND=noninteractive apt-get -q -y update RUN DEBIAN_FRONTEND=noninteractive apt-get -q -y upgrade RUN DEBIAN_FRONTEND=noninteractive apt-get -q -y install build-essential openjdk-11-jre-headless == Results in: == ... #7 21.52 Setting up ca-certificates-java (20190405) ... #7 21.55 head: cannot open '/etc/ssl/certs/java/cacerts' for reading: No such file or directory #7 21.62 Exception in thread "main" java.lang.InternalError: Error loading java.security file #7 21.62at java.base/java.security.Security.initialize(Security.java:94) #7 21.62at java.base/java.security.Security$1.run(Security.java:79) #7 21.62at java.base/java.security.Security$1.run(Security.java:77) #7 21.62at java.base/java.security.AccessController.doPrivileged(Native Method) #7 21.62at java.base/java.security.Security.(Security.java:77) #7 21.62at java.base/sun.security.jca.ProviderList.(ProviderList.java:176) #7 21.62at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:94) #7 21.62at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:92) #7 21.62at java.base/java.security.AccessController.doPrivileged(Native Method) #7 21.62at java.base/sun.security.jca.ProviderList.fromSecurityProperties(ProviderList.java:91) #7 21.62at java.base/sun.security.jca.Providers.(Providers.java:54) #7 21.62at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:156) #7 21.62at java.base/java.security.cert.CertificateFactory.getInstance(CertificateFactory.java:193) #7 21.62at org.debian.security.KeyStoreHandler.(KeyStoreHandler.java:50) #7 21.62at org.debian.security.UpdateCertificates.(UpdateCertificates.java:65) #7 21.62at org.debian.security.UpdateCertificates.main(UpdateCertificates.java:51) #7 21.64 dpkg: error processing package ca-certificates-java (--configure): #7 21.64 installed ca-certificates-java package post-installation script subprocess returned error exit status 1 #7 21.64 dpkg: dependency problems prevent configuration of openjdk-11-jre-headless:amd64: #7 21.64 openjdk-11-jre-headless:amd64 depends on ca-certificates-java (>= 20190405~); however: #7 21.64 Package ca-certificates-java is not configured yet. #7 21.64 #7 21.64 dpkg: error processing package openjdk-11-jre-headless:amd64 (--configure): #7 21.64 dependency problems - leaving unconfigured #7 21.64 Processing triggers for libc-bin (2.28-10+deb10u2) ... #7 21.66 Processing triggers for ca-certificates (20200601~deb10u2) ... #7 21.67 Updating certificates in /etc/ssl/certs... #7 22.04 0 added, 0 removed; done. #7 22.04 Running hooks in /etc/ca-certificates/update.d... #7 22.04 #7 22.12 Exception in thread "main" java.lang.InternalError: Error loading java.security file #7 22.12at java.base/java.security.Security.initialize(Security.java:94) #7 22.12at java.base/java.security.Security$1.run(Security.java:79) #7 22.12at java.base/java.security.Security$1.run(Security.java:77) #7 22.12at java.base/java.security.AccessController.doPrivileged(Native Method) #7 22.12at java.base/java.security.Security.(Security.java:77) #7 22.12at java.base/sun.security.jca.ProviderList.(ProviderList.java:176) #7 22.12at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:94) #7 22.12at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:92) #7 22.12at java.base/java.security.AccessController.doPrivileged(Native Method) #7 22.12at java.base/sun.security.jca.ProviderList.fromSecurityProperties(ProviderList.java:91) #7 22.12at java.base/sun.security.jca.Providers.(Providers.java:54) #7 22.12at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:156) #7 22.12at java.base/java.security.cert.CertificateFactory.getInstance(CertificateFactory.java:193) #7 22.12at org.debian.security.KeyStoreHandler.(KeyStoreHandler.java:50) #7 22.12at org.debian.security.UpdateCertificates.(UpdateCertificates.java:65) #7 22.12at org.debian.security.UpdateCertificates.main(UpdateCertificates.java:51) #7 22.13 E: /etc/ca-certificates/update.d/jks-keystore exited with code 1. #7 22.13 done. #7 22.15 Errors were encountered while processing: #7 22.15 ca-certificates-java #7 22.15 openjdk-11-jre-headless:amd64 #7 22.17 E: Sub-process /usr/bin/dpkg returned an error code (1)
Bug#1052915: marked as done (libdnf: FTBFS: dh_install: error: missing files, aborting)
Your message dated Fri, 03 Nov 2023 16:35:37 + with message-id and subject line Bug#1052915: fixed in libdnf 0.69.0-2.1 has caused the Debian Bug report #1052915, regarding libdnf: FTBFS: dh_install: error: missing files, aborting 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.) -- 1052915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdnf Version: 0.69.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/build' > make[3]: Nothing to be done for 'preinstall'. > make[3]: Leaving directory '/<>/build' > Install the project... > /usr/bin/cmake -P cmake_install.cmake > -- Install configuration: "None" > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/libdnf.pc > -- Installing: /<>/debian/tmp/usr/include/libdnf/config.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/log.hpp > -- Installing: /<>/debian/tmp/usr/include/libdnf/nevra.hpp > -- Installing: /<>/debian/tmp/usr/include/libdnf/nsvcap.hpp > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-advisory.h > -- Installing: > /<>/debian/tmp/usr/include/libdnf/dnf-advisorypkg.h > -- Installing: > /<>/debian/tmp/usr/include/libdnf/dnf-advisoryref.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-db.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-conf.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-context.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-enums.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-goal.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-keyring.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-lock.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-package.h > -- Installing: > /<>/debian/tmp/usr/include/libdnf/dnf-packagedelta.h > -- Installing: > /<>/debian/tmp/usr/include/libdnf/dnf-repo-loader.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-rpmts.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-sack.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-reldep.h > -- Installing: > /<>/debian/tmp/usr/include/libdnf/dnf-reldep-list.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-repo.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-state.h > -- Installing: > /<>/debian/tmp/usr/include/libdnf/dnf-transaction.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-types.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-utils.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/dnf-version.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/libdnf.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-goal.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-nevra.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-package.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-packageset.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-query.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-repo.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-selector.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-subject.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-types.h > -- Installing: /<>/debian/tmp/usr/include/libdnf/hy-util.h > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libdnf.so.2 > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libdnf.so > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libdnf/plugins/README > -- Installing: /<>/debian/tmp/usr/include/libdnf/utils/logger.hpp > -- Installing: > /<>/debian/tmp/usr/include/libdnf/utils/PreserveOrderMap.hpp > -- Installing: /<>/debian/tmp/usr/include/libdnf/conf/Option.hpp > -- Installing: > /<>/debian/tmp/usr/include/libdnf/conf/OptionChild.hpp > -- Installing: > /<>/debian/tmp/usr/include/libdnf/conf/OptionBool.hpp > -- Installing: > /<>/debian/tmp/usr/include/libdnf/conf/OptionEnum.hpp > -- Installing: > /<>/debian/tmp/usr/include/libdnf/conf/OptionNumber.hpp > -- Installing: > /<>/debian/tmp/usr/include/libdnf/conf/OptionPath.hpp > -- Installing: > /<>/debian/tmp/usr/include/libdnf/conf/OptionSeconds.hpp > -- Installing: > /<>/debian/tmp/usr/include/libdnf/conf/OptionString.hpp > -- Installing: > /<>/debian/tmp/usr/include/libdnf/conf/OptionStringList.hpp > -- Installing: > /<>/debian/tmp/usr/include/libdnf/conf/OptionBinds.hpp > -- Installing:
Bug#1052911: marked as done (librepo: FTBFS: dh_install: error: missing files, aborting)
Your message dated Fri, 03 Nov 2023 16:35:45 + with message-id and subject line Bug#1052911: fixed in librepo 1.14.5-3.1 has caused the Debian Bug report #1052911, regarding librepo: FTBFS: dh_install: error: missing files, aborting 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.) -- 1052911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: librepo Version: 1.14.5-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/build' > make[3]: Nothing to be done for 'preinstall'. > make[3]: Leaving directory '/<>/build' > Install the project... > /usr/bin/cmake -P cmake_install.cmake > -- Install configuration: "None" > -- Installing: /<>/debian/tmp/usr/include/librepo/checksum.h > -- Installing: /<>/debian/tmp/usr/include/librepo/fastestmirror.h > -- Installing: /<>/debian/tmp/usr/include/librepo/gpg.h > -- Installing: /<>/debian/tmp/usr/include/librepo/handle.h > -- Installing: /<>/debian/tmp/usr/include/librepo/librepo.h > -- Installing: > /<>/debian/tmp/usr/include/librepo/metadata_downloader.h > -- Installing: /<>/debian/tmp/usr/include/librepo/metalink.h > -- Installing: /<>/debian/tmp/usr/include/librepo/mirrorlist.h > -- Installing: > /<>/debian/tmp/usr/include/librepo/package_downloader.h > -- Installing: /<>/debian/tmp/usr/include/librepo/rcodes.h > -- Installing: /<>/debian/tmp/usr/include/librepo/repoconf.h > -- Installing: /<>/debian/tmp/usr/include/librepo/repomd.h > -- Installing: /<>/debian/tmp/usr/include/librepo/repoutil_yum.h > -- Installing: /<>/debian/tmp/usr/include/librepo/result.h > -- Installing: /<>/debian/tmp/usr/include/librepo/types.h > -- Installing: > /<>/debian/tmp/usr/include/librepo/url_substitution.h > -- Installing: /<>/debian/tmp/usr/include/librepo/util.h > -- Installing: /<>/debian/tmp/usr/include/librepo/version.h > -- Installing: /<>/debian/tmp/usr/include/librepo/xmlparser.h > -- Installing: /<>/debian/tmp/usr/include/librepo/yum.h > -- Installing: /<>/debian/tmp/usr/include/librepo/downloader.h > -- Installing: > /<>/debian/tmp/usr/include/librepo/downloader_internal.h > -- Installing: > /<>/debian/tmp/usr/include/librepo/downloadtarget.h > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/librepo.so.0 > -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/librepo.so > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/librepo.pc > -- Installing: > /<>/debian/tmp/usr/lib/python3/dist-packages/librepo/__init__.py > -- Installing: > /<>/debian/tmp/usr/lib/python3/dist-packages/librepo/_librepo.so > make[2]: Leaving directory '/<>/build' > # Use system-provides files. > rm -fv 'build/doc/python/_static/jquery.js' \ >'build/doc/python/_static/underscore.js' \ >'build/doc/c/html/jquery.js' \ >'build/doc/python/_static/doctools.js' \ >'build/doc/python/_static/language_data.js' \ >'build/doc/python/_static/searchtools.js' > removed 'build/doc/python/_static/jquery.js' > removed 'build/doc/python/_static/underscore.js' > removed 'build/doc/c/html/jquery.js' > removed 'build/doc/python/_static/doctools.js' > removed 'build/doc/python/_static/language_data.js' > removed 'build/doc/python/_static/searchtools.js' > make[1]: Leaving directory '/<>' >dh_install -O--buildsystem=cmake > dh_install: warning: Cannot find (any matches for) "usr/local/lib/python3.*" > (tried in ., debian/tmp) > > dh_install: warning: python3-librepo missing files: usr/local/lib/python3.* > dh_install: error: missing files, aborting > make: *** [debian/rules:11: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/09/25/librepo_1.14.5-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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
Bug#1052913: marked as done (libcomps: FTBFS: dh_install: error: missing files, aborting)
Your message dated Fri, 03 Nov 2023 16:11:21 + with message-id and subject line Bug#1052913: fixed in libcomps 0.1.19-2.1 has caused the Debian Bug report #1052913, regarding libcomps: FTBFS: dh_install: error: missing files, aborting 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.) -- 1052913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcomps Version: 0.1.19-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/build' > make[3]: Nothing to be done for 'preinstall'. > make[3]: Leaving directory '/<>/build' > Install the project... > /usr/bin/cmake -P cmake_install.cmake > -- Install configuration: "None" > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcomps.so.0 > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcomps.so > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_doc.h > -- Installing: > /<>/debian/tmp/usr/include/libcomps/comps_docgroup.h > -- Installing: > /<>/debian/tmp/usr/include/libcomps/comps_doccategory.h > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_docenv.h > -- Installing: > /<>/debian/tmp/usr/include/libcomps/comps_docpackage.h > -- Installing: > /<>/debian/tmp/usr/include/libcomps/comps_docgroupid.h > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_obj.h > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_mm.h > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_hslist.h > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_dict.h > -- Installing: > /<>/debian/tmp/usr/include/libcomps/comps_objradix.h > -- Installing: > /<>/debian/tmp/usr/include/libcomps/comps_objmradix.h > -- Installing: > /<>/debian/tmp/usr/include/libcomps/comps_objdict.h > -- Installing: > /<>/debian/tmp/usr/include/libcomps/comps_objlist.h > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_elem.h > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_radix.h > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_mradix.h > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_bradix.h > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_set.h > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_parse.h > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_log.h > -- Installing: > /<>/debian/tmp/usr/include/libcomps/comps_default.h > -- Installing: /<>/debian/tmp/usr/include/libcomps/comps_utils.h > -- Installing: > /<>/debian/tmp/usr/include/libcomps/comps_validate.h > -- Installing: > /<>/debian/tmp/usr/include/libcomps/comps_log_codes.h > -- Up-to-date: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcomps.so.0 > -- Up-to-date: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcomps.so > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/libcomps.pc > -- Up-to-date: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/libcomps.pc > -- Installing: > /<>/debian/tmp/usr/lib/python3/dist-packages/libcomps/__init__.py > -- Installing: > /<>/debian/tmp/usr/lib/python3/dist-packages/libcomps/_libpycomps.so > running install_egg_info > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: > SetuptoolsDeprecationWarning: setup.py install is deprecated. > !! > > > > Please avoid running ``setup.py`` directly. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html > for details. > > > > !! > self.initialize_options() > running egg_info > creating src/libcomps.egg-info > writing src/libcomps.egg-info/PKG-INFO > writing dependency_links to src/libcomps.egg-info/dependency_links.txt > writing top-level names to src/libcomps.egg-info/top_level.txt > writing manifest file 'src/libcomps.egg-info/SOURCES.txt' > reading manifest file 'src/libcomps.egg-info/SOURCES.txt' > writing manifest file 'src/libcomps.egg-info/SOURCES.txt' > Copying src/libcomps.egg-info to > /<>/debian/tmp//usr/lib/python3/dist-packages/libcomps-0.1.19.egg-info > make[2]: Leaving directory '/<>/build' > # Remove doctree files (redundant, conflicts with reproducible builds) > rm -rfv
Bug#1029333: marked as done (golang-github-bsm-go-vlq-dev: Depends: golang-github-onsi-gomega-dev but it is not installable)
Your message dated Fri, 3 Nov 2023 20:42:52 +0530 with message-id <20231103151252.2i4m54cae3zwy...@office.mailbox.org> and subject line Re: golang-github-bsm-go-vlq-dev: Depends: golang-github-onsi-gomega-dev but it is not installable has caused the Debian Bug report #1029333, regarding golang-github-bsm-go-vlq-dev: Depends: golang-github-onsi-gomega-dev but it is not installable 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.) -- 1029333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: golang-github-bsm-go-vlq-dev Version: 0.0~git20150828.ec6e8d4-1 Severity: serious The following packages have unmet dependencies: golang-github-bsm-go-vlq-dev : Depends: golang-github-onsi-gomega-dev but it is not installable --- End Message --- --- Begin Message --- Version: 0.0~git20150828.ec6e8d4-2 This is fixed but I forgot to mention this in d/ch. Closing. On Sat, 21 Jan 2023 13:51:38 +0200 Adrian Bunk wrote: > Package: golang-github-bsm-go-vlq-dev > Version: 0.0~git20150828.ec6e8d4-1 > Severity: serious > > The following packages have unmet dependencies: > golang-github-bsm-go-vlq-dev : Depends: golang-github-onsi-gomega-dev but it > is not installable > > Best, Nilesh signature.asc Description: PGP signature --- End Message ---
Bug#1055286: r-cran-spatstat.core: Fails autopkgtests on all archs
Source: r-cran-spatstat.core Version: 2.4-4-2 Severity: serious Tags: trixie sid Dear Maintainer, Spatstat.core fails its autopkgtests with: This is due to an API change in spatstat.random to which this package did not adapt to. https://github.com/spatstat/spatstat.random/commit/5e90d382ee6a4bbb6266b5b77d832f3dcc129b3b It has also been removed from CRAN and archive since December 22. https://cran.r-project.org/web/packages/spatstat.core/index.html It may make sense to remove it altogether but it should be removed from testing for sure. Thanks, Nilesh -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_IN, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: tagging 1055264
Processing commands for cont...@bugs.debian.org: > tags 1055264 + pending confirmed fixed-upstream Bug #1055264 [src:mongo-c-driver] mongo-c-driver FTBFS on 32bit Added tag(s) fixed-upstream, pending, and confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1055264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054261: marked as done (tint2 coredumps on startup)
Your message dated Fri, 03 Nov 2023 13:50:09 + with message-id and subject line Bug#1054261: fixed in tint2 17.0.1-1.1 has caused the Debian Bug report #1054261, regarding tint2 coredumps on startup 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.) -- 1054261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tint2 Version: 17.0.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, tint2 crashes reliably on startup with this: ``` $ tint2 tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes tint2: xRandr: Found crtc's: 6 tint2: xRandr: Linking output DisplayPort-1 with crtc 0, resolution 1920x1080, DPI 102 tint2: xRandr: Linking output HDMI-A-0 with crtc 1, resolution 1920x1080, DPI 102 tint2: xRandr: crtc 2 seems disabled tint2: xRandr: crtc 3 seems disabled tint2: xRandr: crtc 4 seems disabled tint2: xRandr: crtc 5 seems disabled tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'. tint2: Loading config file: /home/phil/.config/tint2/tint2rc tint2: real transparency off depth: 24 tint2: panel items: TSC tint2: Systray composited rendering off tint2: systray_asb forced to 100 0 0 tint2: nb monitors 2, nb monitors used 2, nb desktops 4 tint2: panel 1 uses scale 1 tint2: panel 2 uses scale 1 tint2: Kernel uevent interface initialized... tint2: systray window 27263052 tint2: systray started add_icon: 46137383 (), pid 24844, visual 0x55fcc6f9e1c0, colormap 46137384, depth 32, width 22, height 22 tint2: Couldn't get geometry of window! systray 823: cannot embed icon for window 46137383 () parent 27263080 pid 24844 tint2: remove_icon: 46137383 () Segmentation fault (core dumped) ``` Despite what the message says, even if you define G_SLICE=always-malloc, it still prints that message: ``` [phil@rider ~]$ export G_SLICE=always-malloc [phil@rider ~]$ tint2 tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes tint2: xRandr: Found crtc's: 6 ``` The internet believes it's due to newer glibc2: https://bbs.archlinux.org/viewtopic.php?id=284293 I'm using openbox. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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 tint2 depends on: ii libc6 2.37-12 ii libcairo2 1.18.0-1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.78.0-2 ii libgtk-3-03.24.38-5 ii libimlib2 1.12.1-1 ii libpango-1.0-01.51.0+ds-2 ii libpangocairo-1.0-0 1.51.0+ds-2 ii librsvg2-22.54.7+dfsg-2 ii libstartup-notification0 0.12-6+b1 ii libx11-6 2:1.8.7-1 ii libxcomposite11:0.4.5-1 ii libxdamage1 1:1.1.6-1 ii libxext6 2:1.3.4-1+b1 ii libxinerama1 2:1.1.4-3 ii libxrandr22:1.5.2-2+b1 ii libxrender1 1:0.9.10-1.1 tint2 recommends no packages. tint2 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: tint2 Source-Version: 17.0.1-1.1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of tint2, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated tint2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 Nov 2023 13:40:45 +0100 Source: tint2 Architecture: source Version: 17.0.1-1.1 Distribution: unstable Urgency: medium
Bug#1054261: tint2 coredumps on startup
I am uploading a NMU to fix this, which also includes the latest git commits. The change that I am sponsoring is also available in git.
Bug#1055275: dhcpcd: Version 10.0.4 fails to fork in the background
Package: dhcpcd Version: 1:10.0.4-1 Severity: critical Justification: breaks the whole system Dear Maintainer, I'm using dhcpcd on my raspbian os and it was updated on 31 October to latest version 10.0.4. Since then, my raspberrypi started loosing network every 24h. After some investigation I found out that my dhcpcd daemon is not working in the background. I believe this is related to this bug: https://github.com/NetworkConfiguration/dhcpcd/issues/260 It would be nice to downgrade the package version until upstream bug is fixed. Best regards -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Foreign Architectures: armhf Kernel: Linux 6.1.21-v8+ (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CRAP Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages dhcpcd depends on: ii dhcpcd-base1:10.0.4-1 ii lsb-base 11.6 ii sysvinit-utils [lsb-base] 3.08-3 Versions of packages dhcpcd recommends: ii wpasupplicant 2:2.10-15 Versions of packages dhcpcd suggests: pn dhcpcd-gtk -- no debconf information
Processed: these two bugs are really the same
Processing commands for cont...@bugs.debian.org: > forcemerge 994274 1042037 Bug #994274 [src:syslinux] syslinux: FTBFS with gnu-efi 3.0.13 Bug #1042037 [src:syslinux] syslinux: FTBFS: main.c:33:8: error: unknown type name ‘jmp_buf’ Added tag(s) bookworm. Merged 994274 1042037 > thanks Stopping processing here. Please contact me if you need assistance. -- 1042037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042037 994274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055256: marked as done (colmap: Missing build dependency on libcgal-dev)
Your message dated Fri, 03 Nov 2023 10:49:46 + with message-id and subject line Bug#1055256: fixed in colmap 3.8+git20231101+ds-2 has caused the Debian Bug report #1055256, regarding colmap: Missing build dependency on libcgal-dev 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.) -- 1055256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: colmap Version: 3.8+git20231101+ds-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=colmap=3.8%2Bgit20231101%2Bds-1 ... CMake Error at cmake/FindDependencies.cmake:62 (find_package): By not providing "FindCGAL.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "CGAL", but CMake did not find one. Could not find a package configuration file provided by "CGAL" with any of the following names: CGALConfig.cmake cgal-config.cmake Add the installation prefix of "CGAL" to CMAKE_PREFIX_PATH or set "CGAL_DIR" to a directory containing one of the above files. If "CGAL" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:86 (include) -- Configuring incomplete, errors occurred! --- End Message --- --- Begin Message --- Source: colmap Source-Version: 3.8+git20231101+ds-2 Done: Gürkan Myczko We believe that the bug you reported is fixed in the latest version of colmap, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated colmap 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: Fri, 03 Nov 2023 11:30:29 +0100 Source: colmap Architecture: source Version: 3.8+git20231101+ds-2 Distribution: unstable Urgency: medium Maintainer: Gürkan Myczko Changed-By: Gürkan Myczko Closes: 1055256 Changes: colmap (3.8+git20231101+ds-2) unstable; urgency=medium . * d/control: add missing b-d libcgal-dev. (Closes: #1055256) Checksums-Sha1: 9614392d0cbd2ab9ffd520ab6deb9f027e3eebe5 2195 colmap_3.8+git20231101+ds-2.dsc 5883bc912aaffd26826abb69777d4e9b12355a73 21912 colmap_3.8+git20231101+ds-2.debian.tar.xz 136a54129996e8d2a347c80767c2dd34797f01e1 17323 colmap_3.8+git20231101+ds-2_source.buildinfo Checksums-Sha256: 93daf8cd17f649671af73fc805bb41cac7ddd59070c18c2d571aebe8435f6995 2195 colmap_3.8+git20231101+ds-2.dsc 63560a88c634d1970a62b2484611faab43800c108c98aca8533e272c28826ee0 21912 colmap_3.8+git20231101+ds-2.debian.tar.xz c081bfe636abe35ac0e0ccfd1b8113a1239df55be964ac3da4c84c17a2431ce4 17323 colmap_3.8+git20231101+ds-2_source.buildinfo Files: afaa20f3376d30f04edfd9d56c31e2d0 2195 science optional colmap_3.8+git20231101+ds-2.dsc 4d395fb8e8f2f3e15219dac42f9bef89 21912 science optional colmap_3.8+git20231101+ds-2.debian.tar.xz 0c8533ac6bb9f4f8a313da1f6ab6d589 17323 science optional colmap_3.8+git20231101+ds-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmVEzNoACgkQEWhSvN91 FcAeeA/+MywZvTvhztj2pPJNMq9Rl/bR5vw2+fnWWTa4EeT73NB7LvYy1ksFM+83 mAIvWKGrbR9YFmlDy6cy6y/Q1CN5E84cAt2ss+NSa6GwdotnicJyPWTWPWTNCRcl Hm8SRe1RlG9znJiDf3gsuVvBN4TtK92/0sk1OoR0obpSLaCsTXY6zoFsoBAwo23P fsaMewJiyZHdcu+C2c0RnhmnxpKgae5FBrLDi8qUrJ9ZPngUyabO1xkcy6DQFChp 2VOna9quq5DPxnbwVVYeVBQfS9YSURNMExw+Q1gruN2S7thv5//6rOGz8FmYRXfT /ZLgEH96uoIo6rB5oewgrvXcys0iJqgqWCYQvtznUrxkRKP0lVgS827YNpQZwqYg TUDBrKreMnHDn08M9ixNECcteniKWGR+oDzRHnjyw15fZPco/vd6GR7CMqo/6Uxq qzGyfQKfcFK+JuDAt2tchAMe4YMrfrX03smLkK0VMXhENWtap1s5X5cypO8DKr7c g/dao3R0L+hQJa2pPrwalaCnbGlbfdLBuo/lF0SgUfiuzMAI4+brJWl+XP18pFtG ZsmkETOkoZGJG7UvOZeA9bJr5/XJ9YgowurqER54sOCpjC5WdXFLcDMYZdzj5rjj V4VJMQi4ylpK/lg454QFsmLAFcdYuBnfne+o7RzVTvrCqnn320I= =y9Hr -END PGP SIGNATURE End Message ---
Bug#1054862: marked as pending in debomatic
Control: tag -1 pending Hello, Bug #1054862 in debomatic reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/debomatic/-/commit/7d9a36e0a3f84e0fadfb25b10fd7216388a39bdc Handle case when egg-info directory is not empty (Closes: #1054862) (this message was generated automatically) -- Greetings https://bugs.debian.org/1054862
Processed: Bug#1054862 marked as pending in debomatic
Processing control commands: > tag -1 pending Bug #1054862 [src:debomatic] debomatic: FTBFS: make[1]: *** [debian/rules:11: execute_after_dh_auto_install] Error 1 Added tag(s) pending. -- 1054862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054930: marked as done (debug-me: FTBFS: unsatisfiable build-dependency: libghc-aeson-dev (< 2.1) but 2.1.2.1-5 is to be installed)
Your message dated Fri, 03 Nov 2023 10:34:06 + with message-id and subject line Bug#1054930: fixed in debug-me 1.20221231-2 has caused the Debian Bug report #1054930, regarding debug-me: FTBFS: unsatisfiable build-dependency: libghc-aeson-dev (< 2.1) but 2.1.2.1-5 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debug-me Version: 1.20221231-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 10), dh-exec, ghc (>= 8.4.3), > libghc-aeson-dev (>= 0.11), libghc-aeson-dev (<< 2.1), libghc-async-dev (>= > 2.1), libghc-cereal-dev (>= 0.5), libghc-cryptonite-dev (>= 0.20), > libghc-graphviz-dev (>= 2999.18.0), libghc-graphviz-dev (<< 2999.21), > libghc-http-client-dev (>= 0.4), libghc-http-client-tls-dev (>= 0.2), > libghc-http-types-dev (>= 0.9), libghc-memory-dev (>= 0.13), > libghc-mime-mail-dev (>= 0.4), libghc-network-dev (>= 2.6), > libghc-network-uri-dev (>= 2.6), libghc-optparse-applicative-dev (>= 0.12), > libghc-posix-pty-dev (>= 0.2.1), libghc-protobuf-dev (>= 0.2), > libghc-sandi-dev (>= 0.4), libghc-stm-chans-dev (>= 3.0), > libghc-terminal-size-dev (>= 0.3), libghc-text-dev (>= 1.2.2), > libghc-unbounded-delays-dev (>= 0.1), libghc-unordered-containers-dev (>= > 0.2), libghc-utf8-string-dev (>= 1.0), libghc-uuid-dev (>= 1.3), > libghc-wai-dev (>= 3.2), libghc-wai-websockets-dev (>= 3.0), libghc-warp-dev > (>= 3.2), libghc-websockets-dev (>= 0.12.6.0), build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 10), dh-exec, ghc (>= 8.4.3), > libghc-aeson-dev (>= 0.11), libghc-aeson-dev (<< 2.1), libghc-async-dev (>= > 2.1), libghc-cereal-dev (>= 0.5), libghc-cryptonite-dev (>= 0.20), > libghc-graphviz-dev (>= 2999.18.0), libghc-graphviz-dev (<< 2999.21), > libghc-http-client-dev (>= 0.4), libghc-http-client-tls-dev (>= 0.2), > libghc-http-types-dev (>= 0.9), libghc-memory-dev (>= 0.13), > libghc-mime-mail-dev (>= 0.4), libghc-network-dev (>= 2.6), > libghc-network-uri-dev (>= 2.6), libghc-optparse-applicative-dev (>= 0.12), > libghc-posix-pty-dev (>= 0.2.1), libghc-protobuf-dev (>= 0.2), > libghc-sandi-dev (>= 0.4), libghc-stm-chans-dev (>= 3.0), > libghc-terminal-size-dev (>= 0.3), libghc-text-dev (>= 1.2.2), > libghc-unbounded-delays-dev (>= 0.1), libghc-unordered-containers-dev (>= > 0.2), libghc-utf8-string-dev (>= 1.0), libghc-uuid-dev (>= 1.3), > libghc-wai-dev (>= 3.2), libghc-wai-websockets-dev (>= 3.0), libghc-warp-dev > (>= 3.2), libghc-websockets-dev (>= 0.12.6.0), build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [615 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [1566 B] > Get:5 copy:/<>/apt_archive ./ Packages [1596 B] > Fetched 3777 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > 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: > sbuild-build-depends-main-dummy : Depends: libghc-aeson-dev (< 2.1) but > 2.1.2.1-5 is to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/10/28/debug-me_1.20221231-1_unstable.log All bugs filed during this archive rebuild are listed at:
Bug#1042307: marked as done (python-outcome: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Fri, 03 Nov 2023 10:04:48 +
with message-id
and subject line Bug#1042307: fixed in python-outcome 1.2.0-1.1
has caused the Debian Bug report #1042307,
regarding python-outcome: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 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.)
--
1042307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-outcome
Version: 1.2.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
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:240: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/outcome
> copying src/outcome/_version.py ->
> /<>/.pybuild/cpython3_3.11/build/outcome
> copying src/outcome/__init__.py ->
> /<>/.pybuild/cpython3_3.11/build/outcome
> copying src/outcome/_util.py ->
> /<>/.pybuild/cpython3_3.11/build/outcome
> copying src/outcome/_impl.py ->
> /<>/.pybuild/cpython3_3.11/build/outcome
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build;
> python3.11 -m pytest tests
> = test session starts
> ==
> platform linux -- Python 3.11.4, pytest-7.4.0, pluggy-1.2.0
> rootdir: /<>
> configfile: setup.cfg
> collected 0 items / 2 errors
>
> ERRORS
>
> __ ERROR collecting .pybuild/cpython3_3.11/build/tests/test_async.py
> ___
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11/build/tests/test_async.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_async.py:6: in
> import outcome
> outcome/__init__.py:3: in
> from ._impl import Error, Outcome, Value, acapture, capture
> outcome/_impl.py:3: in
> import attr
> E ModuleNotFoundError: No module named 'attr'
> ___ ERROR collecting .pybuild/cpython3_3.11/build/tests/test_sync.py
> ___
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.11/build/tests/test_sync.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_sync.py:6: in
> import outcome
> outcome/__init__.py:3: in
> from ._impl import Error, Outcome, Value, acapture, capture
> outcome/_impl.py:3: in
> import attr
> E ModuleNotFoundError: No module named 'attr'
> === warnings summary
> ===
> ../../../../../../usr/lib/python3/dist-packages/_pytest/config/__init__.py:1373
> /usr/lib/python3/dist-packages/_pytest/config/__init__.py:1373:
> PytestConfigWarning: Unknown config option: asyncio_mode
>
> self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")
>
> -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
> === short test summary info
>
> ERROR tests/test_async.py
> ERROR tests/test_sync.py
> !!! Interrupted: 2 errors during collection
>
> = 1 warning, 2 errors in 0.14s
> =
> E: pybuild pybuild:388: test: plugin distutils failed with: exit code=2: cd
> /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest tests
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11
> returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2023/07/26/python-outcome_1.2.0-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
Bug#1055267: libreoffice-uiconfig-*: missing Breaks for the Replaces
Source: libreoffice Version: 4:7.6.2-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts replaces-without-breaks Hi, during a test with piuparts and DOSE tools I noticed your package causes removal of files that also belong to another package. This is caused by using Replaces without corresponding Breaks. The installation sequence to reproduce this problem is apt-get install libreoffice-base-nogui/sid # (1) apt-get install libreoffice-uiconfig-base/experimental apt-get remove libreoffice-uiconfig-base # (2) The list of installed files at points (1) and (2) should be identical, but the following files have disappeared: usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/admindialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/advancedsettingsdialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/appborderwindow.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/appdetailwindow.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/applycolpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/appswapwindow.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/authentificationpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/autocharsetpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/choosedatasourcedialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/colcontrolbox.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/collectionviewdialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/colwidthdialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/connectionpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/copytablepage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbaseindexdialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbasepage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbtreelist.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbwizconnectionpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbwizmysqlintropage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbwizmysqlnativepage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbwizspreadsheetpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/dbwiztextpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/deleteallrowsdialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/designsavemodifieddialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/detailwindow.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/directsqldialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/emptypage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/fielddescpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/fielddescpanel.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/fielddialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/finalpagewizard.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/generalpagedialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/generalpagewizard.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/generalspecialjdbcdetailspage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/generatedvaluespage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/indexdesigndialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/jdbcconnectionpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/joindialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/jointablemenu.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/joinviewmenu.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/keymenu.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/ldapconnectionpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/ldappage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/limitbox.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/migrwarndlg.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/mysqlnativepage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/mysqlnativesettings.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/namematchingpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/odbcpage.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/parametersdialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/password.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/querycolmenu.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/queryfilterdialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/queryfuncmenu.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/querypropertiesdialog.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/queryview.ui usr/lib/libreoffice/share/config/soffice.cfg/dbaccess/ui/relationdialog.ui
Processed: Re: python-outcome: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Processing control commands:
> tag -1 patch
Bug #1042307 [src:python-outcome] python-outcome: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) patch.
--
1042307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042307: python-outcome: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Control: tag -1 patch diff -Nru python-outcome-1.2.0/debian/changelog python-outcome-1.2.0/debian/changelog --- python-outcome-1.2.0/debian/changelog 2022-07-03 21:00:10.0 +0800 +++ python-outcome-1.2.0/debian/changelog 2023-11-03 17:05:18.0 +0800 @@ -1,3 +1,10 @@ +python-outcome (1.2.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Declare explict B-D on python3-attr. Closes: #1042307 + + -- Tianyu Chen Fri, 03 Nov 2023 17:05:18 +0800 + python-outcome (1.2.0-1) unstable; urgency=medium * New upstream release. diff -Nru python-outcome-1.2.0/debian/control python-outcome-1.2.0/debian/control --- python-outcome-1.2.0/debian/control 2022-07-03 20:54:37.0 +0800 +++ python-outcome-1.2.0/debian/control 2023-11-03 17:05:14.0 +0800 @@ -8,6 +8,7 @@ dh-python, python3, python3-async-generator, + python3-attr, python3-pytest, python3-setuptools Homepage: https://github.com/python-trio/outcome OpenPGP_0x361D0FCF29AEC6B8.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: Re: Package builds fine
Processing control commands:
> tags -1 + patch
Bug #1042668 {Done: Thomas Goirand } [src:python-pbr]
python-pbr: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command
'build_sphinx'pbr.tests.test_core.TestCore.test_setup_py_build_sphinx
Added tag(s) patch.
--
1042668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042668: Package builds fine
Control: tags -1 + patch Hi Thomas! On Mon, Oct 30, 2023 at 04:27:51PM +0100, Thomas Goirand wrote: > Tried rebuilding and it works. Closing... In fact, this package still FTBFS with new Sphinx. Backporting upstream commit [1] helps. I have created a merge request in salsa [2] to do that. I think ideally this bug should be re-opened and then closed from the changelog, but as you explicitly asked to not re-open bugs [3], I am not doing that. [1]: https://opendev.org/openstack/pbr/commit/47c5afe79aa334b3 [2]: https://salsa.debian.org/openstack-team/libs/python-pbr/-/merge_requests/4 [3]: https://lists.debian.org/debian-python/2023/10/msg00059.html -- Dmitry Shachnev signature.asc Description: PGP signature
Processed: Re: Bug#1053499: hilive: flaky autopkgtest on several archs: segfault
Processing control commands: > tags -1 upstream Bug #1053499 [src:hilive] hilive: flaky autopkgtest on several archs: segfault Added tag(s) upstream. > forwarded -1 https://gitlab.com/lokat/HiLive2/-/issues/24 Bug #1053499 [src:hilive] hilive: flaky autopkgtest on several archs: segfault Set Bug forwarded-to-address to 'https://gitlab.com/lokat/HiLive2/-/issues/24'. -- 1053499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053499: hilive: flaky autopkgtest on several archs: segfault
Control: tags -1 upstream Control: forwarded -1 https://gitlab.com/lokat/HiLive2/-/issues/24 -- http://fam-tille.de
Bug#1055264: mongo-c-driver FTBFS on 32bit
Source: mongo-c-driver
Version: 1.25.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=mongo-c-driver=1.25.0-1
...
In file included from
/<>/src/libmongoc/src/mongoc/mongoc-linux-distro-scanner.c:28:
/<>/src/libmongoc/src/mongoc/mongoc-linux-distro-scanner.c: In
function ‘_fgets_wrapper’:
/<>/src/libmongoc/src/mongoc/mongoc-trace-private.h:39:22: error:
format ‘%ld’ expects argument of type ‘long int’, but argument 6 has type
‘size_t’ {aka ‘unsigned int’} [-Werror=format=]
39 | "TRACE: %s():%d " msg, \
| ^
/<>/src/libmongoc/src/mongoc/mongoc-linux-distro-scanner.c:70:7:
note: in expansion of macro ‘TRACE’
70 | TRACE ("Found line of length %ld, bailing out", len);
| ^
...
Bug#1052919: marked as done (sreview: FTBFS: Can't locate File/Which.pm in @INC)
Your message dated Fri, 03 Nov 2023 07:49:33 + with message-id and subject line Bug#1052919: fixed in sreview 0.9.3-1 has caused the Debian Bug report #1052919, regarding sreview: FTBFS: Can't locate File/Which.pm in @INC 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.) -- 1052919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sreview Version: 0.9.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', > 'blib/arch')" t/*.t > t/010-config.t ... > 1..9 > ok 1 - use SReview::Config; > ok 2 - loading nonexisting config produces a warning but succeeds > ok 3 - An object of class 'SReview::Config' isa 'SReview::Config' > ok 4 - loading an existing config file succeeds and prints no warning > ok 5 - Config dump output is as expected > ok 6 - Description of configuration value is as expected > ok 7 - Trying to parse a syntactically invalid perl script produces an > exception > ok 8 - Trying to read a config variable that does not exist produces an > exception > ok 9 - Reading data that does not exist yet produces the default > ok > t/040-db.t ... > 1..7 > ok 1 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 2 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 3 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 4 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 5 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 6 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 7 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok > t/080-runthrough.t ... > 1..15 > ok 1 - use SReview::Files::Factory; > ok 2 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 3 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 4 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 5 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 6 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 7 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 8 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 9 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 10 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 11 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 12 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 13 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 14 # skip Can't test database work unless the SREVIEWTEST_DB environment > variable points to a database which we may clobber and recreate > ok 15 # skip Can't test database work unless the SREVIEWTEST_DB
Bug#1054323: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Package version inconsistency detected
Hi Paul,
Am Thu, Nov 02, 2023 at 07:23:55PM +0100 schrieb Paul Gevers:
> On 02-11-2023 15:13, Andreas Tille wrote:
> > There is probably one remaining problem. As per file R/zzz.R[2] the
> > function checkMatrixPackageVersion verifies that TMB is running always
> > with the Matrix version it was built against.
>
> Well, I suggested before to just patch that check out. Is it really doing
> any good?
Sorry for my weak memory. I have no idea whether it is really doing any
good.
> If the test suite is remotely well done, it should catch the case
> where rmatrix breaks the package, while enabling running it against any
> version that works.
I might open an Issue about this.
> > Do you see some automatic
> > method to approach this which is better than simply waiting for a CI
> > test to fail (which should happen once a r-cran-matrix package of a new
> > Matrix version is uploaded)?
> Well, if you get the version tightly recorded, the migration software will
> refuse to migrate r-cran-matrix because it would break the version in
> testing. No CI is needed for that. But tight version relations are a pain,
> i.e. they limit apt in finding upgrade orders, so if too many packages do
> that, it might prevent people from upgrading their system.
I did not used a tight Depends (see r-cran-matrix (>= $${rmbversion}) in
[1]) but I think the check you suggested to patch out will fire for new
Matrix versions. Since I understand way to less about the internals I'm
hesitating to patch out something upstream considers necessary without
discussing.
BTW, now we have a new kind of regression[2]
56s Error: (converted from warning) package ‘TMB’ was built under R version
4.3.2
I have no idea how to fix this from my side.
Kind regards
Andreas.
[1]
https://salsa.debian.org/r-pkg-team/r-cran-tmb/-/blob/master/debian/rules#L10-13
[2]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-tmb/39490349/log.gz
--
http://fam-tille.de
