Processed: Bug#1071347 marked as pending in r-bioc-rtracklayer
Processing control commands: > tag -1 pending Bug #1071347 [src:r-bioc-rtracklayer] r-bioc-rtracklayer: FTBFS: handlers.c:10:11: error: format not a string literal and no format arguments Added tag(s) pending. -- 1071347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071347: marked as pending in r-bioc-rtracklayer
Control: tag -1 pending Hello, Bug #1071347 in r-bioc-rtracklayer 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/r-pkg-team/r-bioc-rtracklayer/-/commit/cd36736bece8d52d0d8c1bb3ff2f4ea6330e7324 New upstream release fixes FTBFS. Closes: #1071347 (this message was generated automatically) -- Greetings https://bugs.debian.org/1071347
Bug#1074697: marked as done (nordugrid-arc-nagios-plugins: FTBFS: ImportError: cannot import name 'SafeConfigParser' from 'configparser' (/usr/lib/python3.12/configparser.py). Did you mean: 'RawConfig
Your message dated Fri, 12 Jul 2024 06:34:46 +
with message-id
and subject line Bug#1074697: fixed in nordugrid-arc-nagios-plugins 2.0.1-2
has caused the Debian Bug report #1074697,
regarding nordugrid-arc-nagios-plugins: FTBFS: ImportError: cannot import name
'SafeConfigParser' from 'configparser' (/usr/lib/python3.12/configparser.py).
Did you mean: 'RawConfigParser'?
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.)
--
1074697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nordugrid-arc-nagios-plugins
Version: 2.0.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> sphinx-build -b html -d _build/doctrees . _build/html
> Running Sphinx v7.2.6
> 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
> writing output...
> building [html]: targets for 6 source files that are out of date
> updating environment: [new config] 6 added, 0 changed, 0 removed
> [2Kreading sources... [ 17%] arcce
> [2Kreading sources... [ 33%] arcinfosys
> [2Kreading sources... [ 50%] gridstorage
> [2Kreading sources... [ 67%] index
> [2Kreading sources... [ 83%] intro
> [2Kreading sources... [100%] sample_config
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> copying assets... copying static files... done
> copying extra files... done
> done
> [2Kwriting output... [ 17%] arcce
> [2Kwriting output... [ 33%] arcinfosys
> [2Kwriting output... [ 50%] gridstorage
> [2Kwriting output... [ 67%] index
> [2Kwriting output... [ 83%] intro
> [2Kwriting output... [100%] sample_config
>
> generating indices... genindex done
> writing additional pages... search done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 1 warning.
>
> The HTML pages are in _build/html.
>
> Build finished. The HTML pages are in _build/html.
> make[2]: Leaving directory '/<>/doc'
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12/build;
> python3.12 -m unittest discover -v
> arcnagios.ce.jobplugins (unittest.loader._FailedTest.arcnagios.ce.jobplugins)
> ... ERROR
>
> ==
> ERROR: arcnagios.ce.jobplugins
> (unittest.loader._FailedTest.arcnagios.ce.jobplugins)
> --
> ImportError: Failed to import test module: arcnagios.ce.jobplugins
> Traceback (most recent call last):
> File "/usr/lib/python3.12/unittest/loader.py", line 429, in _find_test_path
> package = self._get_module_from_name(name)
>
> File "/usr/lib/python3.12/unittest/loader.py", line 339, in
> _get_module_from_name
> __import__(name)
> File
> "/<>/.pybuild/cpython3_3.12/build/arcnagios/ce/jobplugins/__init__.py",
> line 3, in
> from arcnagios.ce.jobplugins.scripted import ScriptedJobPlugin
> File
> "/<>/.pybuild/cpython3_3.12/build/arcnagios/ce/jobplugins/scripted.py",
> line 5, in
> from arcnagios.ce.jobplugin import JobPlugin
> File
> "/<>/.pybuild/cpython3_3.12/build/arcnagios/ce/jobplugin.py",
> line 4, in
> from arcnagios import substitution
> File
> "/<>/.pybuild/cpython3_3.12/build/arcnagios/substitution.py",
> line 8, in
> from arcnagios.nagutils import ServiceUnknown
> File "/<>/.pybuild/cpython3_3.12/build/arcnagios/nagutils.py",
> line 5, in
> from configparser import SafeConfigParser, InterpolationError,
> NoOptionError
> ImportError: cannot import name 'SafeConfigParser' from 'configparser'
> (/usr/lib/python3.12/configparser.py). Did you mean: 'RawConfigParser'?
>
>
> --
> Ran 1 test in 0.002s
>
> FAILED (errors=1)
> E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd
> /<>/.pybuild/cpython3_3.12/build; python3.12 -m unittest
> discover -v
> dh_auto_test: error: pybuild --test -i python{version} -p 3.12 returned exit
> code 13
The full build log is available from:
http://qa-logs.debian.net/2024/07/0
Bug#1071351: marked as pending in r-bioc-sparsearray
Control: tag -1 pending Hello, Bug #1071351 in r-bioc-sparsearray 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/r-pkg-team/r-bioc-sparsearray/-/commit/e05553d69df910f7074d8ebb4d86b31a89ca9077 new upstream version fixes FTBFS. Closes: #1071351 (this message was generated automatically) -- Greetings https://bugs.debian.org/1071351
Processed: Bug#1071351 marked as pending in r-bioc-sparsearray
Processing control commands: > tag -1 pending Bug #1071351 [src:r-bioc-sparsearray] r-bioc-sparsearray: FTBFS: leaf_vector_utils.c:33:17: error: format not a string literal and no format arguments Added tag(s) pending. -- 1071351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1076172: pixman: FTBFS on armhf: Error: garbage following instruction -- `bne 01f'
Source: pixman Version: 0.42.2-1 Severity: serious Dear Maintainer, The package fails to build on armhf on current sid/testing with: ../../pixman/pixman-arm-simd-asm.h:821: Error: garbage following instruction -- `bne 01f' ../../pixman/pixman-arm-simd-asm.h:869: Info: macro invoked from here ../../pixman/pixman-arm-simd-asm.h:326: Info: macro invoked from here ../../pixman/pixman-arm-simd-asm.h:343:Info: macro invoked from here ../../pixman/pixman-arm-simd-asm.h:354: Info: macro invoked from here ../../pixman/pixman-arm-simd-asm.h:408: Info: macro invoked from here ../../pixman/pixman-arm-simd-asm.h:793: Info: macro invoked from here ../../pixman/pixman-arm-simd-asm.S:875:Info: macro invoked from here ../../pixman/pixman-arm-simd-asm.h:822: Error: garbage following instruction -- `bcc 03f' ../../pixman/pixman-arm-simd-asm.h:869: Info: macro invoked from here ../../pixman/pixman-arm-simd-asm.h:326: Info: macro invoked from here ../../pixman/pixman-arm-simd-asm.h:343:Info: macro invoked from here ../../pixman/pixman-arm-simd-asm.h:354: Info: macro invoked from here ../../pixman/pixman-arm-simd-asm.h:408: Info: macro invoked from here ../../pixman/pixman-arm-simd-asm.h:793: Info: macro invoked from here ../../pixman/pixman-arm-simd-asm.S:875:Info: macro invoked from here See https://gitlab.freedesktop.org/pixman/pixman/-/issues/96 and bug 1073870. Mike
Bug#1069219: pymatgen ftbfs with Python 3.12
Package: pymatgen Version: 2024.1.27+dfsg1-7 Followup-For: Bug #1069219 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu oracular ubuntu-patch Control: tags -1 patch Dear Maintainer, In the absence of the new upstream of the package, would it be possible to consider applying a Python 3.12 compatibility patch meanwhile? In Ubuntu, the attached patch was applied to achieve the following: * d/p/python312.patch: cherry-pick upstream patch to resolve python 3.12 ftbfs (LP: #2067725). Thanks for considering the patch. -- System Information: Debian Release: trixie/sid APT prefers noble-updates APT policy: (500, 'noble-updates'), (500, 'noble-security'), (500, 'noble'), (100, 'noble-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.8.0-36-generic (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru pymatgen-2024.1.27+dfsg1/debian/patches/python312.patch pymatgen-2024.1.27+dfsg1/debian/patches/python312.patch --- pymatgen-2024.1.27+dfsg1/debian/patches/python312.patch 1970-01-01 12:00:00.0 +1200 +++ pymatgen-2024.1.27+dfsg1/debian/patches/python312.patch 2024-07-10 15:59:41.0 +1200 @@ -0,0 +1,749 @@ +Description: Officially support Python 3.12 and test in CI (#3685) + * add python 3.12 to officially supported versions and test it in CI + * down pin chgnet>=0.3.0 + * fix weird typo nrafo_ew_tstructs + * don't depend on tblite above 3.11 since unsupported + https://github.com/tblite/tblite/issues/175 + * improve TestVasprun.test_standard + * drop Lobsterin inerheritance from UserDict, use simple dict instead and + modify __getitem__ to get the salient __getitem__ behavior from UserDict + * try DotDict as super class for Lobsterin + * override Lobsterin.__contains__ to fix on py312 +Author: Janosh Riebesell +Bug: https://github.com/materialsproject/pymatgen/pull/3685 +Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/pymatgen/+bug/2067725 +Origin: upstream, https://github.com/materialsproject/pymatgen/pull/3685 +Last-Update: 2024-07-11 + +--- a/.github/workflows/release.yml b/.github/workflows/release.yml +@@ -96,7 +96,7 @@ + - uses: actions/setup-python@v5 + name: Install Python + with: +- python-version: "3.11" ++ python-version: "3.12" + + - run: | + python -m pip install build +@@ -137,10 +137,10 @@ + # For pypi trusted publishing + id-token: write + steps: +- - name: Set up Python 3.11 ++ - name: Set up Python + uses: actions/setup-python@v5 + with: +- python-version: 3.11 ++ python-version: "3.12" + + - name: Get build artifacts + uses: actions/download-artifact@v3 +--- a/.github/workflows/test.yml b/.github/workflows/test.yml +@@ -29,16 +29,16 @@ + matrix: + # pytest-split automatically distributes work load so parallel jobs finish in similar time + os: [ubuntu-latest, windows-latest] +-python-version: ["3.9", "3.11"] ++python-version: ["3.9", "3.12"] + split: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10] + # include/exclude is meant to maximize CI coverage of different platforms and python + # versions while minimizing the total number of jobs. We run all pytest splits with the + # oldest supported python version (currently 3.9) on windows (seems most likely to surface +-# errors) and with newest version (currently 3.11) on ubuntu (to get complete and speedy ++# errors) and with newest version (currently 3.12) on ubuntu (to get complete and speedy + # coverage on unix). We ignore mac-os, which is assumed to be similar to ubuntu. + exclude: + - os: windows-latest +-python-version: "3.11" ++python-version: "3.12" + - os: ubuntu-latest + python-version: "3.9" + +--- a/dev_scripts/chemenv/get_plane_permutations_optimized.py b/dev_scripts/chemenv/get_plane_permutations_optimized.py +@@ -209,7 +209,7 @@ + # Definition of the facets + all_planes_point_indices = [algo.plane_points] + if algo.other_plane_points is not None: +-all_planes_point_indices.extend(algo.other_plane_points) ++all_planes_point_indices += algo.other_plane_points + + # Loop on the facets + explicit_permutations_per_plane = [] +@@ -305,7 +305,7 @@ + # Definition of the facets + all_planes_point_indices = [algo.plane_points] + if algo.other_plane_points is not None: +-all_planes_point_indices.extend(algo.other_plane_points) ++all_planes_point_indice
Processed: Re: pymatgen ftbfs with Python 3.12
Processing control commands: > tags -1 patch Bug #1069219 [src:pymatgen] pymatgen ftbfs with Python 3.12 Added tag(s) patch. -- 1069219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1074656 marked as pending in heat
Processing control commands: > tag -1 pending Bug #1074656 [src:heat] heat: FTBFS: AttributeError: does not have the attribute 'sleep' Added tag(s) pending. -- 1074656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074656: marked as pending in heat
Control: tag -1 pending Hello, Bug #1074656 in heat 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/openstack-team/services/heat/-/commit/a7052b93416cf899da8caa6890503b7326134fad * Blacklist failing tests (Closes: #1074656). See upstream bug tracker report: https://storyboard.openstack.org/#!/story/2011174 - test_push_metadata_software_deployments_retry - test_push_metadata_software_deployments_retry - test_prepare_ports_for_replace_detach_failed - test_restore_ports_after_rollback_attach_failed (this message was generated automatically) -- Greetings https://bugs.debian.org/1074656
Bug#1074736: marked as done (rust-eui48: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)
Your message dated Fri, 12 Jul 2024 01:50:40 +
with message-id
and subject line Bug#1074736: fixed in rust-eui48 1.1.0-2
has caused the Debian Bug report #1074736,
regarding rust-eui48: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo
build returned exit code 101
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.)
--
1074736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-eui48
Version: 1.1.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem cargo
>dh_update_autotools_config -O--buildsystem=cargo
>dh_autoreconf -O--buildsystem=cargo
>dh_auto_configure -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=8'] []
> ['-j8'] 0
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=8'] []
> ['-j8'] 0
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
> '-j8', '--target', 'x86_64-unknown-linux-gnu'],) {}
>Compiling memchr v2.7.1
>Compiling regex-syntax v0.8.2
>Compiling rustc-serialize v0.3.24
> Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=memchr
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/memchr-2.7.1
> CARGO_PKG_AUTHORS='Andrew Gallant :bluss'
> CARGO_PKG_DESCRIPTION='Provides extremely fast (uses SIMD on x86_64, aarch64
> and wasm32) routines for
> 1, 2 or 3 byte search and single substring search.
> ' CARGO_PKG_HOMEPAGE='https://github.com/BurntSushi/memchr'
> CARGO_PKG_LICENSE='Unlicense OR MIT' CARGO_PKG_LICENSE_FILE=''
> CARGO_PKG_NAME=memchr CARGO_PKG_README=README.md
> CARGO_PKG_REPOSITORY='https://github.com/BurntSushi/memchr'
> CARGO_PKG_RUST_VERSION=1.61 CARGO_PKG_VERSION=2.7.1 CARGO_PKG_VERSION_MAJOR=2
> CARGO_PKG_VERSION_MINOR=7 CARGO_PKG_VERSION_PATCH=1 CARGO_PKG_VERSION_PRE=''
> CARGO_RUSTC_CURRENT_DIR=/<>/debian/cargo_registry/memchr-2.7.1
> LD_LIBRARY_PATH=/<>/target/debug/deps rustc --crate-name memchr
> --edition=2021 /<>/debian/cargo_registry/memchr-2.7.1/src/lib.rs
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat
> --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C
> debuginfo=2 --cfg 'feature="alloc"' --cfg 'feature="default"' --cfg
> 'feature="std"' -C metadata=939fc8ddee1334aa -C
> extra-filename=-939fc8ddee1334aa --out-dir
> /<>/target/x86_64-unknown-linux-gnu/debug/deps --target
> x86_64-unknown-linux-gnu -L
> dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L
> dependency=/<>/target/debug/deps --cap-lints warn -C debuginfo=2
> -C strip=none --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C
> link-arg=-Wl,-z,relro --remap-path-prefix
> /<>=/usr/share/cargo/registry/eui48-1.1.0 --remap-path-prefix
> /<>/debian/cargo_registry=/usr/share/cargo/registry`
> Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=rustc_serialize
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/rustc-serialize-0.3.24
> CARGO_PKG_AUTHORS='The Rust Project Developers'
> CARGO_PKG_DESCRIPTION='Generic serialization/deserialization support
> corresponding to the
> `derive(RustcEncodable, RustcDecodable)` mode in the compiler. Also includes
> support for hex, base64, and json encoding and decoding.
> ' CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/rustc-serialize'
> CARGO_PKG_LICENSE=MIT/Apache-2.0 CARGO_PKG_LICENSE_FILE=''
> CARGO_PKG_NAME=rustc-serialize CARGO_PKG_README=README.md
> CARGO_PKG_REPOSITORY='https://github.com/rust-lang/rustc-serialize'
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.3.24 CARGO_PKG_VERSION_MAJOR=0
> CARGO_PKG_VERSION_MINOR=3 CARGO_PKG_VERSION_PATCH=24 CARGO_PKG_VERSION_PRE=''
> CARGO_RUSTC_CURRENT_DIR=/<>/debian/cargo_registry/rustc-serialize-0.3.24
> LD_LIBRARY_PATH=/<>/target/debug/deps rustc --crate-name
> rustc_serialize --edition=2015
> /<>/debian/cargo_registry/rustc-serialize-0.3.24/src/lib.rs
> --error-format=json --
Bug#1074021: marked as done (swift: flaky autopkgtest: timeout too tight?)
Your message dated Fri, 12 Jul 2024 01:34:14 +
with message-id
and subject line Bug#1074021: fixed in swift 2.33.0-6
has caused the Debian Bug report #1074021,
regarding swift: flaky autopkgtest: timeout too tight?
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.)
--
1074021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swift
Version: 2.33.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it regularly fails, particularly on amd64, but all architectures
are affected. I copied the failure output of one of the recent failures
and wondered if maybe one (or more) internal timeouts are too tight. The
autopkgtest also seems to fail systematically on s390x due to
autopkgtest timeout since halfway May 2024.
Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.
Don't hesitate to reach out if you need help and some more information
from our infrastructure.
Paul
https://ci.debian.net/data/autopkgtest/testing/amd64/s/swift/47856417/log.gz
286s ==
286s FAIL:
test.unit.proxy.controllers.test_obj.TestECObjController.test_GET_disconnect
286s
test.unit.proxy.controllers.test_obj.TestECObjController.test_GET_disconnect
286s --
286s testtools.testresult.real._StringException: Traceback (most recent
call last):
286s File
"/tmp/autopkgtest-lxc.npd7s04o/downtmp/build.4lh/src/test/unit/proxy/controllers/test_obj.py",
line 2957, in test_GET_disconnect
286s self.assertIn("Trying to read EC fragment during GET (retrying)",
286s File "/usr/lib/python3.11/unittest/case.py", line 1140, in assertIn
286s self.fail(self._formatMessage(msg, standardMsg))
286s File "/usr/lib/python3.11/unittest/case.py", line 703, in fail
286s raise self.failureException(msg)
286s AssertionError: 'Trying to read EC fragment during GET (retrying)'
not found in "ChunkWriteTimeout feeding fragments for '/a/c/o':
ChunkWriteTimeout (0.1s after 3.59s)"
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: swift
Source-Version: 2.33.0-6
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
swift, 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 1074...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated swift 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, 12 Jul 2024 02:46:42 +0200
Source: swift
Architecture: source
Version: 2.33.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Closes: 1074021
Changes:
swift (2.33.0-6) unstable; urgency=medium
.
* Add TestECObjController.test_GET_disconnect to autpkgtest blacklist, as per
suggestion from release team (timeout too tight) (Closes: #1074021).
Checksums-Sha1:
8b66e55ddc6cea7ead6fc9d382162504a595ee1e 3127 swift_2.33.0-6.dsc
05db8f95b29b15ab2f5b896baf6142b9993a68c4 30700 swift_2.33.0-6.debian.tar.xz
96227a0258e822f74ca8f304b585042935c8362d 14889 swift_2.33.0-6_amd64.buildinfo
Checksums-Sha256:
6771fb753812c1e2492c82fffdce31a82f81d9b6ad49bb4a05ce52c4330ab9b4 3127
swift_2.33.0-6.dsc
dad2425e43c159d4dcb43ebc8352bde2c7ed4da997fb2ccba2c6a17bcece0fad 30700
swift_2.33.0-6.debian.tar.xz
96d0f48dda7df1d3d1c43d035e8c60fddde8d9d5efa87a443f2105cb3601084c 14889
swift_2.33.0-6_amd64.buildinfo
Files:
7c7793930e0e2c819a8344bcfd58ac0c 3127 net optional swift_2.33.0-6.dsc
024dc6e13b5fb01242e6e40bee25c143 30700 net optional
swift_2.33.0-6.debian.tar.xz
883e5f335ae625b66b6730e5bc833558 14889 net optional
swift_2.33.0-6_amd64.buildinfo
-BE
Processed: Bug#1074021 marked as pending in swift
Processing control commands: > tag -1 pending Bug #1074021 [src:swift] swift: flaky autopkgtest: timeout too tight? Added tag(s) pending. -- 1074021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074021: marked as pending in swift
Control: tag -1 pending Hello, Bug #1074021 in swift 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/openstack-team/services/swift/-/commit/32b6bb71b50529a2aab3dcdb62c4075c07fb5237 * Add TestECObjController.test_GET_disconnect to autpkgtest blacklist, as per suggestion from release team (timeout too tight) (Closes: #1074021). (this message was generated automatically) -- Greetings https://bugs.debian.org/1074021
Bug#1076017: purity-off: autopkgtest regression on arm64: output keeps growing
On Jul 11, Paul Gevers wrote: > You have an arm64 system? If yes, good to know it's not systematic and > apparently only happening on the ci.d.n infrastructure. It would be > interesting to figure out what the differences in setup (hardware) are. Yes. It's a Banana Pi M5 and I cannot see how this could be hardware-dependent. > I realized that. But apparently only arm64 is broken. So it's probably a > (indirect) dependency that broke your test on arm64. Have a look at the test: it just uses purity and perl. I should be able to check on the ci infrastructure myself in two weeks. -- ciao, Marco signature.asc Description: PGP signature
Bug#1069158: marked as done (jack-mixer: Missing Depends on python3-gi, gir1.2-gtk-3.0, and python3-cairo)
Your message dated Thu, 11 Jul 2024 23:21:11 +
with message-id
and subject line Bug#1069158: fixed in jack-mixer 18+git20240504-1
has caused the Debian Bug report #1069158,
regarding jack-mixer: Missing Depends on python3-gi, gir1.2-gtk-3.0, and
python3-cairo
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.)
--
1069158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jack-mixer
Version: 17-2+b2
Severity: serious
Justification: Policy 3.5
X-Debbugs-Cc: philipchung1...@yahoo.com
Dear Maintainer,
The jack_mixer binary fails to start if these packages are not installed.
I've reported this against the version currently in bookworm (stable),
but I believe it applies to testing and unstable as well.
Without python3-gi, the following trace appears:
Traceback (most recent call last):
File "/usr/bin/jack_mixer", line 5, in
from jack_mixer.app import main
File "/usr/lib/python3/dist-packages/jack_mixer/app.py", line 21, in
import gi
ModuleNotFoundError: No module named 'gi'
Without gir1.2-gtk-3.0, the trace is:
Traceback (most recent call last):
File "/usr/bin/jack_mixer", line 5, in
from jack_mixer.app import main
File "/usr/lib/python3/dist-packages/jack_mixer/app.py", line 23, in
gi.require_version("Gtk", "3.0")
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 126, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gtk not available
Without python3-cairo, the trace is:
Traceback (most recent call last):
File "/usr/bin/jack_mixer", line 5, in
from jack_mixer.app import main
File "/usr/lib/python3/dist-packages/jack_mixer/app.py", line 30, in
from .channel import InputChannel, NewInputChannelDialog,
NewOutputChannelDialog, OutputChannel
File "/usr/lib/python3/dist-packages/jack_mixer/channel.py", line 27, in
from . import meter
File "/usr/lib/python3/dist-packages/jack_mixer/meter.py", line 20, in
import cairo
ModuleNotFoundError: No module named 'cairo'
(See also bug #995784 about adding python3-cairo as a Recommends for
python3-gi)
Philip Chung
-- System Information:
Debian Release: 12.5
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-18-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages jack-mixer depends on:
ii jackd21.9.21~dfsg-3
ii libc6 2.36-9+deb12u4
ii libglib2.0-0 2.74.6-2
ii libjack-jackd2-0 [libjack-0.125] 1.9.21~dfsg-3
ii python3 3.11.2-1+b1
jack-mixer recommends no packages.
jack-mixer suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: jack-mixer
Source-Version: 18+git20240504-1
Done: Boyuan Yang
We believe that the bug you reported is fixed in the latest version of
jack-mixer, 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 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Boyuan Yang (supplier of updated jack-mixer 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: Thu, 11 Jul 2024 18:39:10 -0400
Source: jack-mixer
Architecture: source
Version: 18+git20240504-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Boyuan Yang
Closes: 1067970 1069158
Changes:
jack-mixer (18+git20240504-1) unstable; urgency=medium
.
* Team upload.
* New upstream snapshot.
+ Replace appdirs with platformdirs. (Closes: #1067970)
* debian/control:
+ Add missing dependency on python3-gi, python3-cairo. (Closes: #1069158)
+ Add missing dependency on gir1.2-gtk-3.0.
Checksums-Sha1:
5996c27041655001150dc7c7c843ad36ec2c97b3 2201 jack-mixer_18+git20240504-1.dsc
f4aa27f8199f211d3f939e04a2ccffc6a1c4e10c 152644
jack-mixer_18+git20240504.orig.tar.gz
a5d0001
Processed: notfound 1068928 in 4.1.6-3
Processing commands for cont...@bugs.debian.org:
> notfound 1068928 4.1.6-3
Bug #1068928 {Done: Samuel Thibault } [src:openmpi]
lammps : FTBFS on armhf (undefined symbol: pmix_value_load or error:
subprocess-exited-with-error)
Bug #1069418 {Done: Samuel Thibault } [src:openmpi]
ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" failed:
/usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Bug #1069429 {Done: Samuel Thibault } [src:openmpi]
dbcsr: FTBFS on armhf: tests fail
Bug #1069433 {Done: Samuel Thibault } [src:openmpi]
gtg-trace: FTBFS on armhf: tests fail
Bug #1069439 {Done: Samuel Thibault } [src:openmpi]
arpack: FTBFS on armhf: make[6]: *** [Makefile:831: test-suite.log] Error 1
Bug #1069511 {Done: Samuel Thibault } [src:openmpi]
mpgrafic: FTBFS on armhf: tests fail
Bug #1069512 {Done: Samuel Thibault } [src:openmpi]
python-escript: FTBFS on armhf: tests fail
No longer marked as found in versions openmpi/4.1.6-3.
No longer marked as found in versions openmpi/4.1.6-3.
No longer marked as found in versions openmpi/4.1.6-3.
No longer marked as found in versions openmpi/4.1.6-3.
No longer marked as found in versions openmpi/4.1.6-3.
No longer marked as found in versions openmpi/4.1.6-3.
No longer marked as found in versions openmpi/4.1.6-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1068928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068928
1069418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069418
1069429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069429
1069433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069433
1069439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069439
1069511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069511
1069512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1075793: plastimatch FTBFS with DCMTK 3.6.8
Thank you Adrian, Yes this is the correct patch. I'm inclined to make a new upstream release instead of patching, but let me know. Greg Sharp gregsh...@geocities.com
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> reassign 1068928 src:openmpi
Bug #1068928 [src:lammps] lammps : FTBFS on armhf (undefined symbol:
pmix_value_load or error: subprocess-exited-with-error)
Bug reassigned from package 'src:lammps' to 'src:openmpi'.
No longer marked as found in versions lammps/20240207+dfsg-1.1.
Ignoring request to alter fixed versions of bug #1068928 to the same values
previously set
> forcemerge 1069433 1068928
Bug #1069433 {Done: Samuel Thibault } [src:openmpi]
gtg-trace: FTBFS on armhf: tests fail
Bug #1069418 {Done: Samuel Thibault } [src:openmpi]
ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" failed:
/usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Bug #1069429 {Done: Samuel Thibault } [src:openmpi]
dbcsr: FTBFS on armhf: tests fail
Bug #1069439 {Done: Samuel Thibault } [src:openmpi]
arpack: FTBFS on armhf: make[6]: *** [Makefile:831: test-suite.log] Error 1
Bug #1069511 {Done: Samuel Thibault } [src:openmpi]
mpgrafic: FTBFS on armhf: tests fail
Bug #1069512 {Done: Samuel Thibault } [src:openmpi]
python-escript: FTBFS on armhf: tests fail
Bug #1069429 {Done: Samuel Thibault } [src:openmpi]
dbcsr: FTBFS on armhf: tests fail
Removed indication that 1069429 affects src:python-escript, src:ruby-mpi,
src:dbcsr, src:gtg-trace, src:mpgrafic, and src:arpack
Added indication that 1069429 affects
src:gtg-trace,src:python-escript,src:arpack,src:dbcsr,src:ruby-mpi,src:mpgrafic
Removed indication that 1069418 affects src:gtg-trace, src:mpgrafic,
src:arpack, src:python-escript, src:ruby-mpi, and src:dbcsr
Added indication that 1069418 affects
src:gtg-trace,src:python-escript,src:arpack,src:dbcsr,src:ruby-mpi,src:mpgrafic
Removed indication that 1069433 affects src:gtg-trace, src:arpack,
src:mpgrafic, src:python-escript, src:dbcsr, and src:ruby-mpi
Added indication that 1069433 affects
src:gtg-trace,src:python-escript,src:arpack,src:dbcsr,src:ruby-mpi,src:mpgrafic
Removed indication that 1069439 affects src:gtg-trace, src:mpgrafic,
src:arpack, src:python-escript, src:ruby-mpi, and src:dbcsr
Added indication that 1069439 affects
src:gtg-trace,src:python-escript,src:arpack,src:dbcsr,src:ruby-mpi,src:mpgrafic
Removed indication that 1069511 affects src:arpack, src:mpgrafic,
src:gtg-trace, src:dbcsr, src:ruby-mpi, and src:python-escript
Added indication that 1069511 affects
src:gtg-trace,src:python-escript,src:arpack,src:dbcsr,src:ruby-mpi,src:mpgrafic
Removed indication that 1069512 affects src:mpgrafic, src:arpack,
src:gtg-trace, src:ruby-mpi, src:dbcsr, and src:python-escript
Added indication that 1069512 affects
src:gtg-trace,src:python-escript,src:arpack,src:dbcsr,src:ruby-mpi,src:mpgrafic
Bug #1068928 [src:openmpi] lammps : FTBFS on armhf (undefined symbol:
pmix_value_load or error: subprocess-exited-with-error)
Severity set to 'serious' from 'important'
Marked Bug as done
Added indication that 1068928 affects
src:gtg-trace,src:python-escript,src:arpack,src:dbcsr,src:ruby-mpi,src:mpgrafic
Marked as fixed in versions openmpi/4.1.6-13.
Marked as found in versions openmpi/4.1.6-12 and openmpi/4.1.6-3.
Added tag(s) trixie and sid.
Bug #1069418 {Done: Samuel Thibault } [src:openmpi]
ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" failed:
/usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Bug #1069439 {Done: Samuel Thibault } [src:openmpi]
arpack: FTBFS on armhf: make[6]: *** [Makefile:831: test-suite.log] Error 1
Bug #1069511 {Done: Samuel Thibault } [src:openmpi]
mpgrafic: FTBFS on armhf: tests fail
Bug #1069512 {Done: Samuel Thibault } [src:openmpi]
python-escript: FTBFS on armhf: tests fail
Merged 1068928 1069418 1069429 1069433 1069439 1069511 1069512
> affects 1069433 src:lammps
Bug #1069433 {Done: Samuel Thibault } [src:openmpi]
gtg-trace: FTBFS on armhf: tests fail
Bug #1068928 {Done: Samuel Thibault } [src:openmpi]
lammps : FTBFS on armhf (undefined symbol: pmix_value_load or error:
subprocess-exited-with-error)
Bug #1069418 {Done: Samuel Thibault } [src:openmpi]
ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" failed:
/usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Bug #1069429 {Done: Samuel Thibault } [src:openmpi]
dbcsr: FTBFS on armhf: tests fail
Bug #1069439 {Done: Samuel Thibault } [src:openmpi]
arpack: FTBFS on armhf: make[6]: *** [Makefile:831: test-suite.log] Error 1
Bug #1069511 {Done: Samuel Thibault } [src:openmpi]
mpgrafic: FTBFS on armhf: tests fail
Bug #1069512 {Done: Samuel Thibault } [src:openmpi]
python-escript: FTBFS on armhf: tests fail
Added indication that 1069433 affects src:lammps
Added indication that 1068928 affects src:lammps
Added indication that 1069418 affects src:lammps
Added indication that 1069429 affects src:lammps
Added indication that 1069439 affects src:lammps
Added indication that 1069511 affects src:lammps
Added indication that 1069512 affects src:lammps
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Bug#1076120: onboard: Segmentation Fault on Mouse Hover After Update to Version 1.4.1-7
Hi, On Do 11 Jul 2024 13:17:40 CEST, KeyofBlueS wrote: On Thu, 11 Jul 2024 07:51:30 + Mike Gabriel wrote: Hi, On Do 11 Jul 2024 04:01:21 CEST, KeyofBlueS wrote: > Package: onboard > Version: 1.4.1-7 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: keyofbl...@gmail.com > > Dear Maintainer, > > After updating Onboard from version 1.4.1-6 to 1.4.1-7, the > application crashes > with a segmentation fault as soon as the mouse cursor hovers over its window. > This issue did not occur in the previous version. > > Steps to Reproduce: > - Update Onboard to version 1.4.1-7 > - Open Onboard. > - Move the mouse cursor over the Onboard window. > > Attached is the log file generated by Onboard during the crash. > > Thank you for your attention to this matter. Please let me know if > any further > information is required. > > Best regards. I rebuilt onboard 1.4.1-6 (against Python 3.12, the uploaded version was still using Python 3.11) and the crash also occurs in onboard 1.4.1-6. Can check your /var/log/dpkg.log and let me know what other packages got upgraded when upgrading onboard? Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net Hi Mike, attached is the dpkg.log Thanks. Could you try downgrading all packages from src:pkg glib2.0 to the version in testing? (2.80.4-1 -> 2.80.3-1): I.e. libglib2.0-0t64:amd64 and family members, see [1] under section "binaries". Thanks for helping with testing and fixing this issue. If that does not help, try downgrading libgtk-3-0 [2] to the pkg versions in testing. Mike [1] https://tracker.debian.org/pkg/glib2.0 [2] https://tracker.debian.org/pkg/gtk+3.0 -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpPqUNL8gKDO.pgp Description: Digitale PGP-Signatur
Bug#1076166: mdtraj: fails to build
Source: mdtraj Version: 1.10.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sudipm.mukher...@gmail.com Dear Maintainer, mdtraj is failing to build from source with the error: dh_numpy3 mv debian/python3-mdtraj.substvars.new debian/python3-mdtraj.substvars mv debian/python-mdtraj-doc.substvars.new debian/python-mdtraj-doc.substvars # setup.py builds the static lib libtheobald.a for each python version # but dh_python3 can't tell the difference between the different builds, # since py3.11 compiles libtheobald.o with -fwrapv, where py3.12 uses -fno-strict-overflow # So clean up manually (assume the binary difference is not an issue) rm -f debian/python3-mdtraj/usr/lib/python3.*/dist-packages/mdtraj/core/lib/libtheobald.a rmdir -p --ignore-fail-on-non-empty debian/python3-mdtraj/usr/lib/python3.*/dist-packages/mdtraj/core/lib rmdir: failed to remove 'debian/python3-mdtraj/usr/lib/python3.*/dist-packages/mdtraj/core/lib': No such file or directory make[1]: *** [debian/rules:59: execute_after_dh_python3] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:11: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 The latest log can be seen at https://buildd.debian.org/status/fetch.php?pkg=mdtraj&arch=amd64&ver=1.10.0-2%2Bb1&stamp=1720720921&raw=0 -- Regards Sudip
Bug#1065994: marked as done (ust: Please drop dependencies on python3-distutils)
Your message dated Thu, 11 Jul 2024 21:00:55 + with message-id and subject line Bug#1065994: fixed in ust 2.13.8-2 has caused the Debian Bug report #1065994, regarding ust: Please drop dependencies on python3-distutils 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.) -- 1065994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ust Version: 2.13.7-1 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham --- End Message --- --- Begin Message --- Source: ust Source-Version: 2.13.8-2 Done: Michael Jeanson We believe that the bug you reported is fixed in the latest version of ust, 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 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Jeanson (supplier of updated ust 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: Thu, 11 Jul 2024 15:56:21 -0400 Source: ust Architecture: source Version: 2.13.8-2 Distribution: unstable Urgency: medium Maintainer: Jon Bernard Changed-By: Michael Jeanson Closes: 1065994 Changes: ust (2.13.8-2) unstable; urgency=medium . * [a940c81] Replace distutils with setuptools for python 3.12 (Closes: #1065994) * [637c1bb] Bump standards version to 4.7.0 * [5c5f577] Fix liblttng-ust1t64 lintian override Checksums-Sha1: 91d321761939822e38508f991c4e493c1d8a5a88 3162 ust_2.13.8-2.dsc 33306cdfd9483796e14caec7918a05c90eab9cdb 1358168 ust_2.13.8.orig.tar.bz2 8c0b205bdeb3f8976aa1a1ca1acfc320fa6df36f 488 ust_2.13.8.orig.tar.bz2.asc 4aa571e57dad7165e47a8875b19f8d9053edefb0 18356 ust_2.13.8-2.debian.tar.xz d0b37e7cf9fa0abde3df55f886c5882fa6e7ff9e 13628 ust_2.13.8-2_source.buildinfo Checksums-Sha256: 0269fe53c2bf7e313594af6ef423005266709987fab2527c1bc3bcdd8325f2e8 3162 ust_2.13.8-2.dsc d4ef98dab9a37ad4f524ccafdfd50af4f266039b528dd5afabce78e49024d937 1358168 ust_2.13.8.orig.tar.bz2 6dd84f529340fcdcf5d39624bd9b4aa079926809102d08a3e9e43689206cdd85 488 ust_2.13.8.orig.tar.bz2.asc b7db27a63c6e2388ef2667ba902007ad0f8647c62334c30ca5d63c28f110 18356 ust_2.13.8-2.debian.tar.xz edf2e21d6ce3e2bd5e719533888e321281b612121f83a3b8dac76f74ea03db8e 13628 ust_2.13.8-2_source.buildinfo Files: c0233579ed15c3692d03953424a92775 3162 libs optional ust_2.13.8-2.dsc 4077be3f26d293d95fd779d12b830a10 1358168 libs optional ust_2.13.8.orig.tar.bz2 032a83c125e8768e02a46bae7f0af648 488 libs optional ust_2.13.8.orig.tar.bz2.asc 6e810f258b4c767ceb6429a340f0e181 18356 libs optional ust_2.13.8-2.debian.tar.xz 8f43ee3b5abe88db9d265a19a68355d2 13628 libs optional ust_2.13.8-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEmGYkMkK2Qid54gtihlYfRSGA/P4FAmaQOV0UHG1qZWFuc29u QGRlYmlhbi5vcmcACgkQhlYfRSGA/P54ZQ//VyPKqNES/7eqah8P0eWf405x/KhE Z2mU1PyGBOsCO7/zT3rGAkQKfsdp9awDYmOP/FVzO/orsWIqK+67M8OTUCXuF7z9 ee/JbksZbE3ntgiz/wV2UvI1KIt+C89mDxDXQToTfcYzcxdnacokRK9VuMIu2t3m /jgr4E+Ihc42/XTn37g7+7of+l/qLeQuF/OpT7f/2JONBzRTjAY22R9ee9j19xOX eMeIKm+2LQ0pJnT2HpxalgG8K4iWtmzfIxHGfORn2YtI2yWExJB6IAcjb+7MrAMm Lm0HdGQW4A7f5BUmM37x/eL2GB9lD0EubnNnR0d/vxqgBU74um1vYpzyhQ++db5h LYgwqx1n6J5SpFfKJ50JvsQijn2DlBDNBh5m3vuUMgZo6NCIJRk+pgIsV2A+bWN0 ALWbCboOSBfgLZ/e/f0ljHrN9Ieex/24ucbXPNH8PqzqTtzm3kEqelegkeGx4SPs IqXPC+FjS+zzSRKbNj4b7Jh0P4Ae+0CwAZXkB8lG0COUo4jLbhky31QMalBeoYUm FqSCIrnodw41ivsVA+9qRV12uPbcJEjgSVUUiSvHsG+1LuzNinkcUmG2Gq4g7a3v K3Cr9UWe+rgD1x7M9rrqPTQr76nf0bF6TndOECRG9ZAkHbC49NutnUF7WkOIGuMI Zyx5vwMUy9jhaZU= =qcbW -END PGP SIGNATURE- pgpYwSGbGkXWJ.pgp Description: PGP signature --- End Message ---
Bug#1066309: marked as done (bibcursed: FTBFS: bibcursed.c:77:10: error: implicit declaration of function ‘tolower’ [-Werror=implicit-function-declaration])
Your message dated Thu, 11 Jul 2024 21:19:15 + with message-id and subject line Bug#1066309: fixed in bibcursed 2.0.1-0.1 has caused the Debian Bug report #1066309, regarding bibcursed: FTBFS: bibcursed.c:77:10: error: implicit declaration of function ‘tolower’ [-Werror=implicit-function-declaration] 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.) -- 1066309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bibcursed Version: 2.0.0-6.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wshadow -o bibcursed bibcursed.c -lncurses -Wl,-z,relro > bibcursed.c: In function ‘menu’: > bibcursed.c:77:10: error: implicit declaration of function ‘tolower’ > [-Werror=implicit-function-declaration] >77 |lch = tolower(ch); > | ^~~ > bibcursed.c:28:1: note: include ‘’ or provide a declaration of > ‘tolower’ >27 | #include > +++ |+#include >28 | > bibcursed.c:81:18: error: implicit declaration of function ‘search_menu’ > [-Werror=implicit-function-declaration] >81 | case 's' : search_menu(); break; > | ^~~ > bibcursed.c:82:18: error: implicit declaration of function ‘add_entry’ > [-Werror=implicit-function-declaration] >82 | case 'a' : add_entry(); break; > | ^ > bibcursed.c:83:18: error: implicit declaration of function ‘delete_entry’ > [-Werror=implicit-function-declaration] >83 | case 'd' : delete_entry(); break; > | ^~~~ > bibcursed.c:84:18: error: implicit declaration of function ‘change_entry’ > [-Werror=implicit-function-declaration] >84 | case 'c' : change_entry(); break; > | ^~~~ > bibcursed.c:85:18: error: implicit declaration of function ‘config_options’ > [-Werror=implicit-function-declaration] >85 | case 'o' : config_options(); break; > | ^~ > bibcursed.c:86:18: error: implicit declaration of function ‘help’ > [-Werror=implicit-function-declaration] >86 | case 'h' : help(); break; > | ^~~~ > bibcursed.c:87:18: error: implicit declaration of function ‘quit_prog’ > [-Werror=implicit-function-declaration] >87 | case 'q' : quit_prog(); break; > | ^ > bibcursed.c: At top level: > bibcursed.c:93:1: warning: return type defaults to ‘int’ [-Wimplicit-int] >93 | help() > | ^~~~ > bibcursed.c:142:1: warning: return type defaults to ‘int’ [-Wimplicit-int] > 142 | config_options() > | ^~ > bibcursed.c:147:1: warning: return type defaults to ‘int’ [-Wimplicit-int] > 147 | add_entry() > | ^ > bibcursed.c: In function ‘add_entry’: > bibcursed.c:387:19: error: implicit declaration of function ‘field_menu’ > [-Werror=implicit-function-declaration] > 387 | print_pos+= field_menu(use_institution, set_institution, "A. > Institution"); > | ^~ > bibcursed.c: At top level: > bibcursed.c:851:1: warning: return type defaults to ‘int’ [-Wimplicit-int] > 851 | delete_entry() > | ^~~~ > bibcursed.c:961:1: warning: return type defaults to ‘int’ [-Wimplicit-int] > 961 | change_entry() > | ^~~~ > bibcursed.c: In function ‘change_entry’: > bibcursed.c:1030:7: error: implicit declaration of function ‘change_field’ > [-Werror=implicit-function-declaration] > 1030 | change_field(entry_name); > | ^~~~ > bibcursed.c: At top level: > bibcursed.c:1035:1: warning: return type defaults to ‘int’ [-Wimplicit-int] > 1035 | change_field(char *entry_name) > | ^~~~ > bibcursed.c: In function ‘change_field’: > bibcursed.c:1066:10: error: implicit declaration of function ‘toupper’ > [-Werror=implicit-function-declaration] > 1066 |lch = toupper(ch); >
Bug#1074643: presets: FTBFS:
Hi Lucas! First of all, I would like to thank you for always informing me about the status of my packages. I have always tried to respond to your requests as soon as I see your bugs. However, I would like to ask you: Where do you follow and know that the package has construction problems? I always see the status of each package on my page. https://qa.debian.org/developer.php?login=nilsonfsilva%40hotmail.com&comaint=yes However, this last Bug (presets), which you registered, does not appear with FTBFS failure on my page. Where can I see and fix bugs before they are opened? This can save you work. The objective of the question is precisely to understand and learn how the dynamics of build processes work. Thanks in advance! Nilson F. Silva
Bug#1076017: purity-off: autopkgtest regression on arm64: output keeps growing
Hi Marco, On 10-07-2024 11:23 p.m., Marco d'Itri wrote: I am not sure of how I can investigate this, since it works fine on my system. You have an arm64 system? If yes, good to know it's not systematic and apparently only happening on the ci.d.n infrastructure. It would be interesting to figure out what the differences in setup (hardware) are. If you're interested, I can give you access to a testbed on ci.d.n infrastructure to investigate. We'd need to align on the time, because I need to be around while you're testing. The test is written in shell and Perl, so I do not expect it to be architecture-dependent. The package is even "Architecture: all". I realized that. But apparently only arm64 is broken. So it's probably a (indirect) dependency that broke your test on arm64. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1063328: marked as done (libselinux1t64: /usr-move caused file loss (DEP17))
Your message dated Thu, 11 Jul 2024 21:12:17 +0200 with message-id and subject line #1063328: libselinux1t64 was removed has caused the Debian Bug report #1063328, regarding libselinux1t64: /usr-move caused file loss (DEP17) 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.) -- 1063328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libselinux1t64 Version: 3.5-2.1~exp1 Severity: serious Tags: patch User: helm...@debian.org Usertags: dep17p1 Control: affects -1 + libselinux1 X-Debbugs-Cc: vor...@debian.org Hi, The time64 bump for libselinux1 also causes a /usr-move file loss. Since it is essential, we cannot use Conflicts and hence the protective diversion has to persist into trixie. I'm attaching a patch for your convenience. I note that I could *not* test this patch using piuparts. I am filing a separate issue about that problem. Helmut diff --minimal -Nru libselinux-3.5/debian/changelog libselinux-3.5/debian/changelog --- libselinux-3.5/debian/changelog 2024-02-05 09:25:54.0 +0100 +++ libselinux-3.5/debian/changelog 2024-02-06 08:49:30.0 +0100 @@ -1,3 +1,10 @@ +libselinux (3.5-2.1~exp1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Add DEP17 protective diversion for /usr-move file loss. (Closes: #-1) + + -- Helmut Grohne Tue, 06 Feb 2024 08:49:30 +0100 + libselinux (3.5-2.1~exp1) experimental; urgency=medium * Non-maintainer upload. diff --minimal -Nru libselinux-3.5/debian/clean libselinux-3.5/debian/clean --- libselinux-3.5/debian/clean 1970-01-01 01:00:00.0 +0100 +++ libselinux-3.5/debian/clean 2024-02-06 08:45:34.0 +0100 @@ -0,0 +1,2 @@ +debian/libselinux1t64.preinst +debian/libselinux1t64.postrm diff --minimal -Nru libselinux-3.5/debian/libselinux1t64.lintian-overrides libselinux-3.5/debian/libselinux1t64.lintian-overrides --- libselinux-3.5/debian/libselinux1t64.lintian-overrides 2024-02-05 09:25:54.0 +0100 +++ libselinux-3.5/debian/libselinux1t64.lintian-overrides 2024-02-06 08:49:30.0 +0100 @@ -1 +1,2 @@ libselinux1t64: package-name-doesnt-match-sonames libselinux1 +diversion-for-unknown-file lib/x86_64-linux-gnu/libselinux.so.1 [preinst:*] diff --minimal -Nru libselinux-3.5/debian/libselinux1t64.postrm.in libselinux-3.5/debian/libselinux1t64.postrm.in --- libselinux-3.5/debian/libselinux1t64.postrm.in 1970-01-01 01:00:00.0 +0100 +++ libselinux-3.5/debian/libselinux1t64.postrm.in 2024-02-06 08:48:09.0 +0100 @@ -0,0 +1,11 @@ +#!/bin/sh + +set -e + +if [ "$1" = remove ]; then + dpkg-divert --package libselinux1t64 --no-rename --remove --divert "/lib/#DEB_HOST_MULTIARCH#/libselinux.so.1.usr-is-merged" "/lib/#DEB_HOST_MULTIARCH#/libselinux.so.1" +fi + +#DEBHELPER# + +exit 0 diff --minimal -Nru libselinux-3.5/debian/libselinux1t64.preinst.in libselinux-3.5/debian/libselinux1t64.preinst.in --- libselinux-3.5/debian/libselinux1t64.preinst.in 1970-01-01 01:00:00.0 +0100 +++ libselinux-3.5/debian/libselinux1t64.preinst.in 2024-02-06 08:48:39.0 +0100 @@ -0,0 +1,12 @@ +#!/bin/sh + +set -e + +if [ "$1" = install ]; then + # This DEP17 protective diversion should be removed after trixie is released. + dpkg-divert --package libselinux1t64 --no-rename --add --divert "/lib/#DEB_HOST_MULTIARCH#/libselinux.so.1.usr-is-merged" "/lib/#DEB_HOST_MULTIARCH#/libselinux.so.1" +fi + +#DEBHELPER# + +exit 0 diff --minimal -Nru libselinux-3.5/debian/rules libselinux-3.5/debian/rules --- libselinux-3.5/debian/rules 2024-02-05 09:25:54.0 +0100 +++ libselinux-3.5/debian/rules 2024-02-06 08:49:30.0 +0100 @@ -97,3 +97,8 @@ override_dh_makeshlibs: dh_makeshlibs -plibselinux1t64 --add-udeb="libselinux1-udeb" -V dh_makeshlibs --remaining-packages + +debian/%:debian/%.in + sed 's/#DEB_HOST_MULTIARCH#/$(DEB_HOST_MULTIARCH)/g' $< > $@ + +execute_before_dh_installdeb:debian/libselinux1t64.preinst debian/libselinux1t64.postrm --- End Message --- --- Begin Message --- The t64 package was removed from experimental. As such I assume this bug is no longer relevant, as there can be no file loss caused by renaming if nothing is renamed. Chris--- End Message ---
Processed: Bug#1071350 marked as pending in r-bioc-shortread
Processing control commands: > tag -1 pending Bug #1071350 [src:r-bioc-shortread] r-bioc-shortread: FTBFS: readBfaToc.cc:30:14: error: format not a string literal and no format arguments Added tag(s) pending. -- 1071350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071350: marked as pending in r-bioc-shortread
Control: tag -1 pending Hello, Bug #1071350 in r-bioc-shortread 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/r-pkg-team/r-bioc-shortread/-/commit/5f98289253492ef766b1c93b22fcb3406662350e new upstream version fixes FTBFS. Closes: #1071350 (this message was generated automatically) -- Greetings https://bugs.debian.org/1071350
Bug#1065848: marked as done (docker-compose: Please drop dependencies on python3-distutils)
Your message dated Thu, 11 Jul 2024 17:49:37 + with message-id and subject line Bug#1065848: fixed in docker-compose 1.29.2-6.1 has caused the Debian Bug report #1065848, regarding docker-compose: Please drop dependencies on python3-distutils 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.) -- 1065848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: docker-compose Version: 1.29.2-6 Severity: important User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham --- End Message --- --- Begin Message --- Source: docker-compose Source-Version: 1.29.2-6.1 Done: Emmanuel Arias We believe that the bug you reported is fixed in the latest version of docker-compose, 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 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Arias (supplier of updated docker-compose package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Jul 2024 12:49:42 -0300 Source: docker-compose Architecture: source Version: 1.29.2-6.1 Distribution: unstable Urgency: medium Maintainer: Docker Compose Team Changed-By: Emmanuel Arias Closes: 1065848 Changes: docker-compose (1.29.2-6.1) unstable; urgency=medium . * Non-maintainer upload. * d/patches/remove_distutils.patch: Add patch to remove the use of python3-distutils. * d/control: Remove python3-distutils from binary packages Dependency. Replaced by python3-packaging (Closes: #1065848). Checksums-Sha1: f0fc787906816f013916f8d8817cfb804e991f78 2513 docker-compose_1.29.2-6.1.dsc aea2364dcb5165d5f10319d3e2be20528883aa8d 7556 docker-compose_1.29.2-6.1.debian.tar.xz efb02c5aca7fb6c7f30498ee178f81032839eba2 7619 docker-compose_1.29.2-6.1_amd64.buildinfo Checksums-Sha256: 7e834b6e85b497214d7800b75dd46a87c9e77149635fc7e9778dfeb5d34d69a4 2513 docker-compose_1.29.2-6.1.dsc 2e28fb7d0a37842121e993f9d6bba83392de3bfcd610a9f118e3f7e262698e3c 7556 docker-compose_1.29.2-6.1.debian.tar.xz 722540e39efc170207f48742d8f372b546b6922986a3cfa51a402f162bba2d53 7619 docker-compose_1.29.2-6.1_amd64.buildinfo Files: fca783b1cc176d45e63448fa5f245697 2513 admin optional docker-compose_1.29.2-6.1.dsc a57703f20f1a3811241d4fbd3acc3e58 7556 admin optional docker-compose_1.29.2-6.1.debian.tar.xz 590f0679cbf7e5eea43a78a560bff002 7619 admin optional docker-compose_1.29.2-6.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEE3lnVbvHK7ir4q61+p3sXeEcY/EFAmaMGiESHGVhbWFudUBk ZWJpYW4ub3JnAAoJEPqd7F3hHGPxUBUQAJMdwGiXWNoZcMdXUW/uhvjl2QSWtoUb k4IFl4U1sztolLeeGPKhq9Lon3cEMuB0YqFxtoXjr9bzMUy4nqvEJ43RJdFIDd9L 36d7uLeWwfVrE8czdJZzSQr/TtBNlbLuTFgbjqX1sGUUsGbGN5EGEv1LnQYmX++9 Bnl6H/Sw2lRvcLcFFPPYQ4Vz2bTygSpVWXBuone/cfc4rHOwwQ5qqpKkDHdAS2JB 6Xkpi0sz5d84RbMXOOgo0YO7mUhHIJOkZAHw5hW2JdmUEVzlx8eHXF4uVv1P+aWP 8i2L9xDPwpNRb5RmIabPqu+jIhKDH4zrdFgMFgT6yILUtOloQLHXuSXOed/eL/FZ P0OTz1Ynp2zIHWesm5d+0o0DheVXrppc/WJOxIRxNNTHJP6jounFGDqSNaNW+Qg3 ijbSs+sGR+3LyZsxwT5xH4hOcdTZc+0pZ7cLcTBD8+btSYyZFSHJfE8LCUQLDGkH Gs16JefHT+xuxrgPn7xmLnCTRWDVSyzvURtDnDYZ+PEcCleqKc05VmP2+fyg7xNv xub8+E82al3HI3JLJ6IuaB/BOT0GBAJPDjNhmlfpMiZOD8DzZvI9YR8PmawrUTrl V7JCytAoIhnVDNMFVJVCcjBv9/UtXveTMIEr4O1/PFfq0m20mf3vYPbd5kt6YS5b FgErHu1IG8Om =MKnC -END PGP SIGNATURE- pgpECCobGthA2.pgp Description: PGP signature --- End Message ---
Bug#1063190: [Pkg-owncloud-maintainers] Bug#1063190: closing 1063190 [owncloud-client+t64 RC]
El mar, 9 jul 2024 a las 18:37, Agustin Martin () escribió:
>
> El mar, 9 jul 2024 a las 14:26, Pierre-Elliott Bécue
> () escribió:
> >
> > Feel free to upload it even not as a NMU. (you can add a Team Upload
> > entry if you prefer)
>
> Just uploaded as team upload (took a bit longer since I missed that
> source-only uploads to NEW are not allowed, and libowncloudsync0t64 is
> NEW). Should be already in the NEW queue.
Once accepted from NEW, also uploaded a dummy no-changes source-only
package to unblock "no source upload" migration to testing, versioned
as for old binary NMU. I do not think this worths a commit in git
repo.
> I have also created a merge request with the changes in salsa.debian.org.
Apart from that MR I am attaching final complete diff in
git-format-patch format, in case it is useful.
From ad2d5631ea143fe2537af049422f0698768ec0f6 Mon Sep 17 00:00:00 2001
From: Agustin Martin Domingo
Date: Mon, 8 Jul 2024 16:36:30 +0200
Subject: [PATCH] Adapt previous nmu_owncloud-client.debdiff to new
5.2.1.13040+dfsg-2 version (#1063190).
Original nmu_owncloud-client.debdiff by Lucas Kanashiro and Benjamin Drung.
Adapted for 5.2.1.13040+dfsg-2 using qt6.
Signed-off-by: Agustin Martin Domingo
---
debian/changelog | 7 +++
debian/control | 16 +---
...sync0.install => libowncloudsync0t64.install} | 0
debian/libowncloudsync0t64.lintian-overrides | 3 +++
4 files changed, 19 insertions(+), 7 deletions(-)
rename debian/{libowncloudsync0.install => libowncloudsync0t64.install} (100%)
create mode 100644 debian/libowncloudsync0t64.lintian-overrides
diff --git a/debian/changelog b/debian/changelog
index 5054bed65..55e2fba89 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+owncloud-client (5.2.1.13040+dfsg-3) unstable; urgency=medium
+
+ * Team upload.
+ * Rename libraries for 64-bit time_t transition (Closes: #1063190)
+
+ -- Agustin Martin Domingo Tue, 09 Jul 2024 16:25:57 +0200
+
owncloud-client (5.2.1.13040+dfsg-2) unstable; urgency=medium
* d/control:
diff --git a/debian/control b/debian/control
index dbabf8c41..39329f900 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,8 @@ Section: net
Priority: optional
Maintainer: ownCloud for Debian maintainers
Uploaders: Pierre-Elliott Bécue
-Build-Depends: cmake,
+Build-Depends: dpkg-dev (>= 1.22.5),
+ cmake,
debhelper-compat (= 13),
extra-cmake-modules,
libkdsingleapplication-qt6-dev,
@@ -22,7 +23,7 @@ Homepage: https://owncloud.org/sync-clients/
Package: owncloud-client
Architecture: any
Multi-Arch: no
-Depends: libowncloudsync0 (= ${binary:Version}),
+Depends: libowncloudsync0t64 (= ${binary:Version}),
libqt6sql6-sqlite,
libqt6svg6,
${misc:Depends},
@@ -40,12 +41,13 @@ Description: folder synchronization with an ownCloud server - GUI
owncloud-client provides the graphical client specialising in
synchronizing with cloud storage provided by ownCloud.
-Package: libowncloudsync0
+Package: libowncloudsync0t64
+Provides: ${t64:Provides}
Architecture: any
Multi-Arch: same
Depends: ${misc:Depends}, ${shlibs:Depends}
-Replaces: libocsync0
-Breaks: libocsync0
+Replaces: libowncloudsync0, libocsync0
+Breaks: libowncloudsync0 (<< ${source:Version}), libocsync0
Section: libs
Description: ownCloudSync folder synchronization - libraries
The ownCloudSync system lets you always have your latest files wherever
@@ -60,7 +62,7 @@ Description: ownCloudSync folder synchronization - libraries
Package: libowncloudsync-dev
Architecture: any
Multi-Arch: same
-Depends: libowncloudsync0 (= ${binary:Version}), ${misc:Depends}
+Depends: libowncloudsync0t64 (= ${binary:Version}), ${misc:Depends}
Replaces: libocsync-dev
Breaks: libocsync-dev
Section: libdevel
@@ -88,7 +90,7 @@ Description: ownCloudSync folder synchronization - shared data
Package: owncloud-client-cmd
Architecture: any
-Depends: libowncloudsync0 (= ${binary:Version}),
+Depends: libowncloudsync0t64 (= ${binary:Version}),
libqt6sql6-sqlite,
${misc:Depends},
${shlibs:Depends}
diff --git a/debian/libowncloudsync0.install b/debian/libowncloudsync0t64.install
similarity index 100%
rename from debian/libowncloudsync0.install
rename to debian/libowncloudsync0t64.install
diff --git a/debian/libowncloudsync0t64.lintian-overrides b/debian/libowncloudsync0t64.lintian-overrides
new file mode 100644
index 0..6d50bcfc5
--- /dev/null
+++ b/debian/libowncloudsync0t64.lintian-overrides
@@ -0,0 +1,3 @@
+#The lib is so unstable, that it makes no sense to ship symbolfiles
+libowncloudsync0t64: no-symbols-control-file usr/lib/*/libowncloud*.so.*
+libowncloudsync0t64: package-name-doesnt-match-sonames libowncloud-csync0 libowncloudResources0 libowncloudsync0
--
2.45.2
Processed: closing 1074726
Processing commands for cont...@bugs.debian.org: > close 1074726 Bug #1074726 [src:upstream-ontologist] upstream-ontologist: FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_build] Error 25 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1074726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:tifffile
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:tifffile > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1075798 (http://bugs.debian.org/1075798) > # Bug title: tifffile: Failing autopkgtest on s390x > # * https://github.com/cgohlke/tifffile/issues/262 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1075798 + fixed-upstream Bug #1075798 [src:tifffile] tifffile: Failing autopkgtest on s390x Added tag(s) fixed-upstream. > usertags 1075798 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1075798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074706: [Pkg-pascal-devel] Bug#1074706: msgfmt change breaks build
On 11/07/2024 12:38, Peter B wrote: Hi Davo, please raise this as a formal bug upstream with FPC. Or would you rather that I do this? Regards, Peter
Bug#1073325: marked as done (metview: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libatlas_ecmwf.so: undefined reference to `eckit::mpi::setCommDefault(char const*)')
Your message dated Thu, 11 Jul 2024 15:54:11 + with message-id and subject line Bug#1073325: fixed in metview 5.22.0-2 has caused the Debian Bug report #1073325, regarding metview: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libatlas_ecmwf.so: undefined reference to `eckit::mpi::setCommDefault(char const*)' 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.) -- 1073325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073325 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: metview Version: 5.22.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -fcf-protection > -std=gnu++17 -I /usr/include/eigen3 -Wdate-time -D_FORTIFY_SOURCE=2 -pipe > -Wall -Wextra -Wno-unused-parameter -Wno-unused-variable -Wno-sign-compare > -O3 -DNDEBUG -Wl,-z,relro -Wl,-z,now-Wl,--disable-new-dtags > "CMakeFiles/mir-formula.dir/mir-formula.cc.o" -o ../../../bin/mir-formula > -Wl,-rpath,/<>/debian/build/lib: ../../../lib/libmir.so.0.0.0 > /usr/lib/x86_64-linux-gnu/libeckit_linalg.so.0d > /usr/lib/x86_64-linux-gnu/libeckit_geometry.so.0d > /usr/lib/x86_64-linux-gnu/libeckit_option.so.0d > /usr/lib/x86_64-linux-gnu/libeckit.so.0d /usr/lib/x86_64-linux-gnu/librt.a > -ldl /usr/lib/x86_64-linux-gnu/libeccodes.so.0 -lm -latlas_ecmwf > /usr/bin/ld: > /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libatlas_ecmwf.so: > undefined reference to `eckit::mpi::setCommDefault(char const*)' > /usr/bin/ld: > /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libatlas_ecmwf.so: > undefined reference to `eckit::mpi::comm(char const*)' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2024/06/15/metview_5.22.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240615&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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: metview Source-Version: 5.22.0-2 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of metview, 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 1073...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated metview package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jul 2024 13:51:14 +0100 Source: metview Architecture: source Version: 5.22.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alastair McKinstry Closes: 1073325 1075265 Changes: metview (5.22.0-2) unstable; urgency=medium . * Patch g++14-changes.patch to fix FTBFS with g++14. Closes: #1075265 * Rebuild against updated atlas. Closes: #1073325 * Set Debian Science Maint. as maintainer * Fix broken vcs url * Standards-Version: 4.7.0; no changes required Checksums-Sha1: c473b54ca097a744adaf778eda013a267faa0088 3327 metview_5.22.0-2.dsc 91d288414f0f936b3f17003e7e6128580026c6e2 41388 metview_5.22.0-2.debian.tar.xz Checksums-Sha256: f9eb6ce4852271eb16a7cb8e8b4aa6ffbba57948582ba237ebea12894377dc92 3327 metview_5.22.0-2.dsc 9a95d15b6f8a16dc8cf8cb6b05171b8647a751e1a1c9c11f4f
Bug#1074712: marked as done (node-assume: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Thu, 11 Jul 2024 15:25:17 + with message-id and subject line Bug#1074712: fixed in node-assume 2.3.0-4 has caused the Debian Bug report #1074712, regarding node-assume: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1074712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-assume Version: 2.3.0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240702 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs > No build command found, searching known files >dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../. node_modules/assume > /bin/sh -ex debian/tests/pkg-js/test > + mocha ./test/assume.test.js > > > Assume > undefined can configure the amount stacks to slice off > undefined throw Error instances > undefined aliases chain properly > #csliceStacklone > undefined increases slice for each clone > undefined defaults to the same value if no clone value is provided > undefined can clone falsy values > #a > undefined is aliased as `an` > undefined classifies NaN > undefined classifies undefined > undefined classifies undefined > undefined classifies arguments > undefined classifies strings > undefined classifies numbers > undefined classifies arrays > undefined classifies dates > undefined classifies errors > undefined classifies regexps > undefined classifies booleans > undefined classifies buffers > (node:3118423) [DEP0005] DeprecationWarning: Buffer() is deprecated due to > security and usability issues. Please use the Buffer.alloc(), > Buffer.allocUnsafe(), or Buffer.from() methods instead. > (Use `node --trace-deprecation ...` to show where the warning was created) > undefined classifies float32arrays > undefined classifies float64arrays > undefined classifies int16arrays > undefined classifies int32arrays > undefined classifies int8arrays > undefined classifies uint16arrays > undefined classifies uint32arrays > undefined classifies uint8arrays > #eitherOfType > undefined is aliased as `eitherOfType`, `oneOfType` > undefined classifies a valid type > undefined supports negation properly > #instanceof > undefined is aliased as `instanceOf`, `inherit`, `inherits` > undefined correctly checks the instance > #includes > undefined is aliased as `instanceOf`, `inherit`, `inherits` > undefined check if a key in an object > undefined chars are in a given string > undefined check array indexes > undefined can deeply check array values > #ok > undefined is aliased as `truthy`, `truly`, `okay` > undefined is ok > #falsely > undefined is aliased as `falsey` and `falsy` > undefined is falsely > #true > undefined only checks booleans > #false > undefined only checks booleans > #exists > undefined is aliased as `exist` > undefined checks if values are not null > #length > undefined is aliased as `lengthOf`, `size` > undefined checks the length of a string > undefined checks the length of an array > undefined checks the amount of keys in a object > undefined prefers a `.length` key over the size of an object > undefined checks the amount of arguments in a function > #empty > undefined checks if strings are empty > undefined checks if array is empty > undefined check if objects are empty > #above > undefined is aliased as `gt`, `greater`, `greaterThan` > undefined accepts numbers > undefined accepts everything from .length > #least > undefined is aliased as `gte`, `atleast` > undefined accepts numbers > undefined accepts everything from .length > #below > undefined is aliased as `lt`, `less`, `lessThan` > undefined accepts numbers > undefined accepts everything from .length > #most > undefined is aliased as `lte`, `atmost` > undefined accepts numbers
Bug#1076125: (build-)dependency on removed python3-distutils
Hi, I uploaded in delayed a NMU to fix this bug. This will be in unstable soon. -- cheers, Emmanuel Arias ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ eam...@debian.org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1 ⠈⠳⣄ signature.asc Description: PGP signature
Processed: Bug#1074712 marked as pending in node-assume
Processing control commands: > tag -1 pending Bug #1074712 [src:node-assume] node-assume: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 1074712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074712: marked as pending in node-assume
Control: tag -1 pending Hello, Bug #1074712 in node-assume reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-assume/-/commit/37ed138850a0c9c464d46e80b34058597771e948 Fix test for Node.js 20 Closes: #1074712 (this message was generated automatically) -- Greetings https://bugs.debian.org/1074712
Processed: affects 1076148
Processing commands for cont...@bugs.debian.org: > affects 1076148 src:mpi4py Bug #1076148 [libpmix2t64] libpmix2t64: libpmix.so.2: cannot open shared object file: No such file or directory Added indication that 1076148 affects src:mpi4py > thanks Stopping processing here. Please contact me if you need assistance. -- 1076148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1071348 marked as pending in r-bioc-s4arrays
Processing control commands: > tag -1 pending Bug #1071348 [src:r-bioc-s4arrays] r-bioc-s4arrays: FTBFS: array_selection.c:352:17: error: format not a string literal and no format arguments Added tag(s) pending. -- 1071348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071348: marked as pending in r-bioc-s4arrays
Control: tag -1 pending Hello, Bug #1071348 in r-bioc-s4arrays 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/r-pkg-team/r-bioc-s4arrays/-/commit/48b527c3274eb043093fdb027d59b8037c16 new upstream version fixes FTBFS. Closes: #1071348 (this message was generated automatically) -- Greetings https://bugs.debian.org/1071348
Processed: Bug#1071346 marked as pending in r-bioc-rsamtools
Processing control commands: > tag -1 pending Bug #1071346 [src:r-bioc-rsamtools] r-bioc-rsamtools: FTBFS: samtools_patch.c:37:13: error: format not a string literal and no format arguments Added tag(s) pending. -- 1071346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071346: marked as pending in r-bioc-rsamtools
Control: tag -1 pending Hello, Bug #1071346 in r-bioc-rsamtools 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/r-pkg-team/r-bioc-rsamtools/-/commit/42a4bdcf3a6b82497a449fd65592f0bfe8caf153 new upstream version fixes FTBFS. Closes: #1071346 (this message was generated automatically) -- Greetings https://bugs.debian.org/1071346
Processed: libpmix2t64: libpmix.so.2: cannot open shared object file: No such file or directory
Processing control commands: > affects -1 src:dolfinx-mpc Bug #1076148 [libpmix2t64] libpmix2t64: libpmix.so.2: cannot open shared object file: No such file or directory Added indication that 1076148 affects src:dolfinx-mpc -- 1076148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1076148: libpmix2t64: libpmix.so.2: cannot open shared object file: No such file or directory
Package: libpmix2t64
Version: 5.0.3-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:dolfinx-mpc
https://buildd.debian.org/status/fetch.php?pkg=dolfinx-mpc&arch=amd64&ver=0.8.0.post1-4%2Bb1&stamp=1720703948&raw=0
...
[x86-csail-01:562901] mca_base_component_repository_open: unable to open
mca_pmix_ext3x: libpmix.so.2: cannot open shared object file: No such file or
directory (ignored)
...
This needs updating to 2.12.3:
$ cat debian/libpmix2t64.links
/usr/lib/${DEB_HOST_MULTIARCH}/pmix2/lib/libpmix.so.2.13.2
/usr/lib/${DEB_HOST_MULTIARCH}/libpmix.so.2
/usr/lib/${DEB_HOST_MULTIARCH}/pmix2/lib/libpmix.so.2.13.2
/usr/lib/${DEB_HOST_MULTIARCH}/libpmix.so.2.13.2
$
Processed: Bug#1071345 marked as pending in r-bioc-rhdf5
Processing control commands: > tag -1 pending Bug #1071345 [src:r-bioc-rhdf5] r-bioc-rhdf5: FTBFS: H5E.c:117:19: error: format not a string literal and no format arguments Added tag(s) pending. -- 1071345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071345: marked as pending in r-bioc-rhdf5
Control: tag -1 pending Hello, Bug #1071345 in r-bioc-rhdf5 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/r-pkg-team/r-bioc-rhdf5/-/commit/7a9e2fabbf7abdeb8180e9f558c63d5ab3d7f8b0 New upstream fixes FTBFS. Closes: #1071345 (this message was generated automatically) -- Greetings https://bugs.debian.org/1071345
Processed: fix my mess
Processing commands for cont...@bugs.debian.org:
> notfixed 1071342 r-bioc-hilbertvis/1.60.0-2
Bug #1071342 {Done: Michael R. Crusoe }
[src:r-bioc-hdf5array] r-bioc-hdf5array: FTBFS: H5DSetDescriptor.c:1182:17:
error: format not a string literal and no format arguments
The source r-bioc-hilbertvis and version 1.60.0-2 do not appear to match any
binary packages
No longer marked as fixed in versions r-bioc-hilbertvis/1.60.0-2.
> found 1071342 r-bioc-hdf5array/1.30.1-1
Bug #1071342 {Done: Michael R. Crusoe }
[src:r-bioc-hdf5array] r-bioc-hdf5array: FTBFS: H5DSetDescriptor.c:1182:17:
error: format not a string literal and no format arguments
Did not alter found versions and reopened.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1071342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1071343: marked as done (r-bioc-hilbertvis: FTBFS: make_wiggle_vector.c:16:17: error: format not a string literal and no format arguments)
Your message dated Thu, 11 Jul 2024 15:35:53 +0200 with message-id and subject line typo in changelog has caused the Debian Bug report #1071343, regarding r-bioc-hilbertvis: FTBFS: make_wiggle_vector.c:16:17: error: format not a string literal and no format arguments 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.) -- 1071343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:r-bioc-hilbertvis Version: 1.60.0-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem R dh_update_autotools_config -O--buildsystem=R dh_autoreconf -O--buildsystem=R dh_auto_configure -O--buildsystem=R dh_auto_build -O--buildsystem=R dh_auto_test -O--buildsystem=R create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=R dh_prep -O--buildsystem=R dh_auto_install --destdir=debian/r-bioc-hilbertvis/ -O--buildsystem=R I: R Package: HilbertVis Version: 1.60.0 I: Building using R version 4.4.0-2 I: R API version: r-api-4.0 I: Using built-time from d/changelog: Wed, 29 Nov 2023 20:56:28 +0100 mkdir -p /<>/debian/r-bioc-hilbertvis/usr/lib/R/site-library R CMD INSTALL -l /<>/debian/r-bioc-hilbertvis/usr/lib/R/site-library --clean . "--built-timestamp='Wed, 29 Nov 2023 20:56:28 +0100'" * installing *source* package ‘HilbertVis’ ... ** using staged installation ** libs using C compiler: ‘gcc (Debian 13.2.0-25) 13.2.0’ make[1]: Entering directory '/<>/src' gcc -I"/usr/share/R/include" -DNDEBUG -fpic -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c hilbert.c -o hilbert.o gcc -I"/usr/share/R/include" -DNDEBUG -fpic -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c make_wiggle_vector.c -o make_wiggle_vector.o make_wiggle_vector.c: In function ‘make_wiggle_vector’: make_wiggle_vector.c:16:17: error: format not a string literal and no format arguments [-Werror=format-security] 16 | error( buf ); | ^~~ cc1: some warnings being treated as errors make[1]: *** [/usr/lib/R/etc/Makeconf:195: make_wiggle_vector.o] Error 1 make[1]: Leaving directory '/<>/src' make[1]: Entering directory '/<>/src' make[1]: Leaving directory '/<>/src' ERROR: compilation failed for package ‘HilbertVis’ * removing ‘/<>/debian/r-bioc-hilbertvis/usr/lib/R/site-library/HilbertVis’ dh_auto_install: error: R CMD INSTALL -l /<>/debian/r-bioc-hilbertvis/usr/lib/R/site-library --clean . "--built-timestamp='Wed, 29 Nov 2023 20:56:28 +0100'" returned exit code 1 make: *** [debian/rules:4: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202405/ About the archive rebuild: The build was made on virtual machines of type m6a.large and r6a.large from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Version: r-bioc-hilbertvis/1.60.0-2--- End Message ---
Bug#1071342: marked as done (r-bioc-hdf5array: FTBFS: H5DSetDescriptor.c:1182:17: error: format not a string literal and no format arguments)
Your message dated Thu, 11 Jul 2024 13:20:32 + with message-id and subject line Bug#1071342: fixed in r-bioc-hilbertvis 1.60.0-2 has caused the Debian Bug report #1071342, regarding r-bioc-hdf5array: FTBFS: H5DSetDescriptor.c:1182:17: error: format not a string literal and no format arguments 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.) -- 1071342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:r-bioc-hdf5array Version: 1.30.1-1 Severity: serious Tags: ftbfs Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules binary dh binary --buildsystem R dh_update_autotools_config -O--buildsystem=R dh_autoreconf -O--buildsystem=R dh_auto_configure -O--buildsystem=R dh_auto_build -O--buildsystem=R dh_auto_test -O--buildsystem=R create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=R dh_prep -O--buildsystem=R dh_auto_install --destdir=debian/r-bioc-hdf5array/ -O--buildsystem=R I: R Package: HDF5Array Version: 1.30.1 I: Building using R version 4.4.0-2 I: R API version: r-api-4.0 I: Using built-time from d/changelog: Tue, 20 Feb 2024 14:26:16 +0100 mkdir -p /<>/debian/r-bioc-hdf5array/usr/lib/R/site-library R CMD INSTALL -l /<>/debian/r-bioc-hdf5array/usr/lib/R/site-library --clean . "--built-timestamp='Tue, 20 Feb 2024 14:26:16 +0100'" * installing *source* package ‘HDF5Array’ ... ** using staged installation ** libs using C compiler: ‘gcc (Debian 13.2.0-25) 13.2.0’ make[1]: Entering directory '/<>/src' gcc -I"/usr/share/R/include" -DNDEBUG -I'/usr/lib/R/site-library/S4Vectors/include' -I'/usr/lib/R/site-library/Rhdf5lib/include' -fpic -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c S4Vectors_stubs.c -o S4Vectors_stubs.o gcc -I"/usr/share/R/include" -DNDEBUG -I'/usr/lib/R/site-library/S4Vectors/include' -I'/usr/lib/R/site-library/Rhdf5lib/include' -fpic -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c H5File.c -o H5File.o gcc -I"/usr/share/R/include" -DNDEBUG -I'/usr/lib/R/site-library/S4Vectors/include' -I'/usr/lib/R/site-library/Rhdf5lib/include' -fpic -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c global_errmsg_buf.c -o global_errmsg_buf.o gcc -I"/usr/share/R/include" -DNDEBUG -I'/usr/lib/R/site-library/S4Vectors/include' -I'/usr/lib/R/site-library/Rhdf5lib/include' -fpic -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/r-base-4.4.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -c H5DSetDescriptor.c -o H5DSetDescriptor.o H5DSetDescriptor.c: In function ‘C_new_H5DSetDescriptor_xp’: H5DSetDescriptor.c:1182:17: error: format not a string literal and no format arguments [-Werror=format-security] 1182 | error(_HDF5Array_global_errmsg_buf()); | ^ cc1: some warnings being treated as errors make[1]: *** [/usr/lib/R/etc/Makeconf:195: H5DSetDescriptor.o] Error 1 make[1]: Leaving directory '/<>/src' make[1]: Entering directory '/<>/src' make[1]: Leaving directory '/<>/src' ERROR: compilation failed for package ‘HDF5Array’ * removing ‘/<>/debian/r-bioc-hdf5array/usr/lib/R/site-library/HDF5Array’ dh_auto_install: error: R CMD INSTALL -l /<>/debian/r-bioc-hdf5array/usr/lib/R/site-library --clean . "--built-timestamp='Tue, 20 Feb 2024 14:26:16 +0100'" returned exit code 1 make: *** [debian/rules:4: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202405/
Processed: Bug#1071342 marked as pending in r-bioc-hilbertvis
Processing control commands: > tag -1 pending Bug #1071342 [src:r-bioc-hdf5array] r-bioc-hdf5array: FTBFS: H5DSetDescriptor.c:1182:17: error: format not a string literal and no format arguments Ignoring request to alter tags of bug #1071342 to the same tags previously set -- 1071342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071342: marked as pending in r-bioc-hilbertvis
Control: tag -1 pending Hello, Bug #1071342 in r-bioc-hilbertvis 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/r-pkg-team/r-bioc-hilbertvis/-/commit/e8853435e688a06a4bfddebfaec9018ce9343412 Added patch to fix format security warning. Closes: #1071342 (this message was generated automatically) -- Greetings https://bugs.debian.org/1071342
Bug#1066313: torsocks upstream fix
Hello, In April you had said that you were going to try and upload a new version of torsocks, which fixes the FTBFS, but you were trying to fix a few lintian issues first. Do you have any update on that? It looks like it is going to be removed from testing soon if it is not fixed. Thanks! Micah
Processed: Re: [Pkg-pascal-devel] Bug#1074706: fpc: FTBFS: msgfmt change breaks build
Processing control commands: > tags -1 patch Bug #1074706 [src:fpc] fpc: FTBFS: make[1]: *** [Makefile:9: de] Error 1 Added tag(s) patch. -- 1074706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> notfound 1071171 0.6.2-1
Bug #1071171 {Done: "Michael R. Crusoe" }
[src:r-cran-mertools] r-cran-mertools: autopkgtest regression on i386 with
rmatrix 1.7-0
No longer marked as found in versions r-cran-mertools/0.6.2-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1071171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1074706: [Pkg-pascal-devel] Bug#1074706: fpc: FTBFS: msgfmt change breaks build
Control: tags -1 patch Adding this patch to the end of the series, fixes the build of the po files. Regards, PeterSubject: Fix msgfmt related build fail Author: Peter Blackman Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074706 Forwarded: no === --- a/fpcsrc/utils/fpdoc/intl/dglobals.de.po +++ b/fpcsrc/utils/fpdoc/intl/dglobals.de.po @@ -1,3 +1,7 @@ +msgid "" +msgstr "" +"Content-Type: text/plain; charset=UTF-8\n" + #: dglobals:sdocpackagetitle msgid "Reference for package '%s'" msgstr "Referenz für Paket '%s'" Index: b/fpcsrc/utils/fpdoc/intl/dwriter.de.po === --- a/fpcsrc/utils/fpdoc/intl/dwriter.de.po +++ b/fpcsrc/utils/fpdoc/intl/dwriter.de.po @@ -1,3 +1,7 @@ +msgid "" +msgstr "" +"Content-Type: text/plain; charset=UTF-8\n" + #: dwriter:serrfilewriting msgid "An error occurred during writing of file \"%s\": %s" msgstr "Beim Schreiben der Datei \"%s\" ist ein Fehler aufgetrete: %s" Index: b/fpcsrc/utils/fpdoc/intl/fpdoc.de.po === --- a/fpcsrc/utils/fpdoc/intl/fpdoc.de.po +++ b/fpcsrc/utils/fpdoc/intl/fpdoc.de.po @@ -1,3 +1,7 @@ +msgid "" +msgstr "" +"Content-Type: text/plain; charset=UTF-8\n" + #: fpdoc:stitle msgid "FPDoc - Free Pascal Documentation Tool" msgstr "FPDoc - Free-Pascal-Dokumentationstool" Index: b/fpcsrc/utils/fpdoc/intl/makeskel.de.po === --- a/fpcsrc/utils/fpdoc/intl/makeskel.de.po +++ b/fpcsrc/utils/fpdoc/intl/makeskel.de.po @@ -1,3 +1,7 @@ +msgid "" +msgstr "" +"Content-Type: text/plain; charset=UTF-8\n" + #: makeskel:stitle msgid "MakeSkel - FPDoc skeleton XML description file generator" msgstr "MakeSkel - Skelett-Generator für FPDoc-XML-Beschreibungsdateien"
Bug#1071349: marked as pending in r-bioc-s4vectors
Control: tag -1 pending Hello, Bug #1071349 in r-bioc-s4vectors 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/r-pkg-team/r-bioc-s4vectors/-/commit/d0b3b7299e44581f289c23d1774ec0b9520623b0 new upstream version fixes autopkgtests regression Closes: #1070843, #1071349 (this message was generated automatically) -- Greetings https://bugs.debian.org/1071349
Processed: Bug#1071349 marked as pending in r-bioc-s4vectors
Processing control commands: > tag -1 pending Bug #1071349 [src:r-bioc-s4vectors] r-bioc-s4vectors: FTBFS: Rle_class.c:1136:17: error: format not a string literal and no format arguments Added tag(s) pending. -- 1071349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070843: marked as pending in r-bioc-s4vectors
Control: tag -1 pending Hello, Bug #1070843 in r-bioc-s4vectors 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/r-pkg-team/r-bioc-s4vectors/-/commit/d0b3b7299e44581f289c23d1774ec0b9520623b0 new upstream version fixes autopkgtests regression Closes: #1070843, #1071349 (this message was generated automatically) -- Greetings https://bugs.debian.org/1070843
Processed: Bug#1070843 marked as pending in r-bioc-s4vectors
Processing control commands: > tag -1 pending Bug #1070843 [src:r-bioc-s4vectors] r-bioc-s4vectors: autopkgtest regression with r-base 4.4.0 Added tag(s) pending. -- 1070843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1070841 marked as pending in r-bioc-iranges
Processing control commands: > tag -1 pending Bug #1070841 [src:r-bioc-iranges] r-bioc-iranges: autopkgtest regression with r-base 4.4.0 Added tag(s) pending. -- 1070841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070841: marked as pending in r-bioc-iranges
Control: tag -1 pending Hello, Bug #1070841 in r-bioc-iranges 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/r-pkg-team/r-bioc-iranges/-/commit/2e8975a7d9c4fe78376feaa7169237afce8b5f7f new release fixes autopkgtest regression Closes: #1070841 (this message was generated automatically) -- Greetings https://bugs.debian.org/1070841
Bug#1073379: marked as done (hypercorn: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Thu, 11 Jul 2024 12:50:06 +
with message-id
and subject line Bug#1073379: fixed in hypercorn 0.17.3-1
has caused the Debian Bug report #1073379,
regarding hypercorn: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.12 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.)
--
1073379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hypercorn
Version: 0.16.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build"
> module
> I: pybuild base:311: python3.12 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.12_hypercorn
> * Building wheel...
> Successfully built hypercorn-0.16.0-py3-none-any.whl
> I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with
> "installer" module
> I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build"
> module
> I: pybuild base:311: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.11_hypercorn
> * Building wheel...
> Successfully built hypercorn-0.16.0-py3-none-any.whl
> I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.11 with
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:311: cd
> /<>/.pybuild/cpython3_3.12_hypercorn/build; python3.12 -m pytest
> --ignore=tests/test_app_wrappers.py
> --ignore=tests/middleware/test_dispatcher.py
> = test session starts
> ==
> platform linux -- Python 3.12.4, pytest-8.2.2, pluggy-1.5.0
> rootdir: /<>/.pybuild/cpython3_3.12_hypercorn/build
> configfile: pyproject.toml
> testpaths: tests
> plugins: hypothesis-6.103.1, cov-5.0.0, asyncio-0.20.3, trio-0.8.0
> asyncio: mode=Mode.STRICT
> collected 180 items
>
> tests/asyncio/test_keep_alive.py [
> 2%]
> tests/asyncio/test_lifespan.py [
> 4%]
> tests/asyncio/test_sanity.py [
> 6%]
> tests/asyncio/test_task_group.py .. [
> 7%]
> tests/asyncio/test_tcp_server.py .. [
> 8%]
> tests/middleware/test_http_to_https.py ... [
> 12%]
> tests/middleware/test_proxy_fix.py ..[
> 13%]
> tests/protocol/test_h11.py ..[
> 26%]
> tests/protocol/test_h2.py .. [
> 29%]
> tests/protocol/test_http_stream.py . [
> 41%]
> tests/protocol/test_ws_stream.py ... [
> 62%]
> ... [
> 64%]
> tests/test___main__.py [
> 73%]
> tests/test_config.py . [
> 80%]
> tests/test_logging.py .. [
> 88%]
> tests/test_utils.py ... [
> 94%]
> tests/trio/test_keep_alive.py [
> 96%]
> tests/trio/test_lifespan.py .F [
> 97%]
> tests/trio/test_sanity.py
> [100%]
>
> === FAILURES
> ===
> _ test_startup_failure
> _
> + Exception Group Traceback (most recent call last):
> | File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 341, in
> from_call
> | result: Optional[TResult] = func()
> | ^^
> | File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 241, in
>
> | lambda: runtest_hook(item=i
Bug#1065851: marked as done (doxyqml: Please drop dependencies on python3-distutils)
Your message dated Thu, 11 Jul 2024 12:49:56 + with message-id and subject line Bug#1065851: fixed in doxyqml 0.3.0-1.2 has caused the Debian Bug report #1065851, regarding doxyqml: Please drop dependencies on python3-distutils 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.) -- 1065851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: doxyqml Version: 0.3.0-1.1 Severity: important Tags: ftbfs trixie sid User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer This package has dependencies, build-dependencies and/or autopkgtest dependencies on python3-distutils. The python3-distutils binary package will soon be dropped from python3-stdlib-extensions. In fact, there is no module for Python 3.12 in python3-distutils, so these dependencies may already be unnecessary. Regards Graham --- End Message --- --- Begin Message --- Source: doxyqml Source-Version: 0.3.0-1.2 Done: Emmanuel Arias We believe that the bug you reported is fixed in the latest version of doxyqml, 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 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Arias (supplier of updated doxyqml package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 10 Jul 2024 09:00:49 -0300 Source: doxyqml Architecture: source Version: 0.3.0-1.2 Distribution: unstable Urgency: medium Maintainer: Loïc Minier Changed-By: Emmanuel Arias Closes: 1065851 Changes: doxyqml (0.3.0-1.2) unstable; urgency=medium . * Non-maintainer upload. * d/patches/remove_distutils.patch: Add patch to stop using distutils in source. * d/control: Remove python3-distutils from Build Dependency. Use python3-setuptools instead (Closes: #1065851). Checksums-Sha1: de993533d383e8948760bb7a69745e7462f532c2 1778 doxyqml_0.3.0-1.2.dsc f76398290517327a927382afb7187ddaf681940c 2440 doxyqml_0.3.0-1.2.debian.tar.xz 7627c4410fe620a4919dba5308f217a80837dc6e 6288 doxyqml_0.3.0-1.2_amd64.buildinfo Checksums-Sha256: 97f699f218a0baa4ccddc333458c070eabc0e0f86c11026e38ade1cfe950f445 1778 doxyqml_0.3.0-1.2.dsc 40a9ca716c40ee0a69667234d7b50d109ac56fdaa5fd4e1f5a67bbe409399693 2440 doxyqml_0.3.0-1.2.debian.tar.xz d999c9078f572f2ec65fad7eeeab539845afda8edad6d17e7b026eccb467771f 6288 doxyqml_0.3.0-1.2_amd64.buildinfo Files: b080fbf6ac3180f2596e11c5d4f7ee44 1778 devel optional doxyqml_0.3.0-1.2.dsc 88a6240ee72c8a0b1d5c134d11c17eb0 2440 devel optional doxyqml_0.3.0-1.2.debian.tar.xz 4554f65584c2d02148badd194ae68fc6 6288 devel optional doxyqml_0.3.0-1.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEE3lnVbvHK7ir4q61+p3sXeEcY/EFAmaOf70SHGVhbWFudUBk ZWJpYW4ub3JnAAoJEPqd7F3hHGPxHJIP/3cnr6lFPEU0rNjK+7gmilyBRiPCBZKn vrhzaaWq3IRClDgibwCPSokZE9HTVNlXnv0C01v24D4r9h464HC7547tSXwewA27 BX4iDS53jSy3GtU8OYRpWaRjrlIDz5TvUJGfpSuiUFXrscHbhOR+VFzcAppunxmG GsvTHbLHtHPFiewFRCBmRGjNG4xb+iL0P19v5UtchSs0bHovhVu84SKw1CTw6fcb Gqkk5JbygCIe5TzKLIG7C5Px4G54Oy7pp2VKWito8JNfkck5c5jGS63ufee6eMen Up2Tacix5yPYCLDHZWogZLwyYf9szLJv3XokMBW4Ro19gq9F9M1HQK9wqEih3vgk g2UVATWHAYOLCkfYBtAtO9kyQSl7kvK6k0VJ1DtKyn8iYzz9hQPMQj3HSJElIFbv TAwuilC9YUENHwYgG4lOmCqeaBE26nKOV1TMtG9KbvlAzeJSYe2z7/et28Tyl9t0 CU4KboZlSBa96En0DnBxgkW3n6y0goT+9O3SbiyXkLd+5qRXBLEJp8RUD6ghfjBQ thDZO6IcXihEaipSL5R0XRAG/+8Q2ZB8Je0UodX0pinc7kXGWDBfTW8MW7Og9Xpq KJCbZFeesezOtBHmmwr7/QWycJ3lMwx8HU4ZhPKEJseJeCbGrbfdrGb0lU/uZEP0 Y+FTQmaI8C/g =oj9K -END PGP SIGNATURE- pgpuaXkOZ_OI0.pgp Description: PGP signature --- End Message ---
Bug#1071171: marked as done (r-cran-mertools: autopkgtest regression on i386 with rmatrix 1.7-0)
Your message dated Thu, 11 Jul 2024 14:49:51 +0200
with message-id <7b9b9f10-eae1-48e6-8b8b-de5f65a0e...@debian.org>
and subject line Re: r-cran-mertools: autopkgtest regression on i386 with
rmatrix 1.7-0
has caused the Debian Bug report #1071171,
regarding r-cran-mertools: autopkgtest regression on i386 with rmatrix 1.7-0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1071171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-mertools
Version: 0.6.2-1
Severity: serious
X-Debbugs-Cc: Dirk Eddelbuettel
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
r-cran-mertools' autopkgtest regresses on i386 when tested with
rmatrix 1.7-0 [1]. I've copied what I hope is the relevant part of
the log below.
Additionally, r-cran-mertools' autopkgtests run for almost 3 hours and
time out when tested with lme4 4 1.1-35.3.
Regards
Graham
[1] hhttps://ci.debian.net/packages/r/r-cran-mertools/testing/i386/
108s Error in `private$handle_error()`:
108s ! testthat subprocess exited in file `test-merData.R`
108s Caused by error:
108s ! R session crashed with exit code -6
108s Backtrace:
108s x
108s 1. \-testthat::test_check("merTools", filter = "^[a-m]")
108s 2. \-testthat::test_dir(...)
108s 3. \-testthat:::test_files(...)
108s 4. \-testthat:::test_files_parallel(...)
108s 5. +-withr::with_dir(...)
108s 6. | \-base::force(code)
108s 7. +-testthat::with_reporter(...)
108s 8. | \-base::tryCatch(...)
108s 9. | \-base (local) tryCatchList(expr, classes, parentenv, handlers)
108s 10. | \-base (local) tryCatchOne(expr, names, parentenv, handlers[[1L]])
108s 11. | \-base (local) doTryCatch(return(expr), name, parentenv, handler)
108s 12. \-testthat:::parallel_event_loop_chunky(queue, reporters, ".")
108s 13. \-queue$poll(Inf)
108s 14. \-base::lapply(...)
108s 15. \-testthat (local) FUN(X[[i]], ...)
108s 16. \-private$handle_error(msg, i)
108s 17. \-rlang::abort(...)
108s Execution halted
--- End Message ---
--- Begin Message ---
control: notfound -1 0.6.2-1
The autopkgtest no longer fails on i386
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
Processed: 1060568 causes ftbfs
Processing commands for cont...@bugs.debian.org: > tags 1060568 + ftbfs Bug #1060568 [src:fence-agents] fence-agents: Please switch Build-Depends to systemd-dev Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1060568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071342: marked as pending in r-bioc-hdf5array
Control: tag -1 pending Hello, Bug #1071342 in r-bioc-hdf5array 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/r-pkg-team/r-bioc-hdf5array/-/commit/3f7f4a8767c5a524d6f560cc78b376128436a7c8 new upstream release fixes FTBFS. Closes: #1071342 (this message was generated automatically) -- Greetings https://bugs.debian.org/1071342
Processed: Bug#1071342 marked as pending in r-bioc-hdf5array
Processing control commands: > tag -1 pending Bug #1071342 [src:r-bioc-hdf5array] r-bioc-hdf5array: FTBFS: H5DSetDescriptor.c:1182:17: error: format not a string literal and no format arguments Added tag(s) pending. -- 1071342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071340: marked as pending in r-bioc-affxparser
Control: tag -1 pending Hello, Bug #1071340 in r-bioc-affxparser 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/r-pkg-team/r-bioc-affxparser/-/commit/169649e6dd9f2919f323d8098827b8e7d1c0733b New upstream version fixes FTBFS Closes: #1071340 Ready to upload to experimental. (this message was generated automatically) -- Greetings https://bugs.debian.org/1071340
Bug#1071341: marked as pending in r-bioc-genefilter
Control: tag -1 pending Hello, Bug #1071341 in r-bioc-genefilter 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/r-pkg-team/r-bioc-genefilter/-/commit/cc484ad80a17194f12bcdb407d1a8747d4bf3f2c New upstream release fixes FTBFS. Closes: #1071341 (this message was generated automatically) -- Greetings https://bugs.debian.org/1071341
Processed: Bug#1071340 marked as pending in r-bioc-affxparser
Processing control commands: > tag -1 pending Bug #1071340 [src:r-bioc-affxparser] r-bioc-affxparser: FTBFS: R_affx_cdf_parser.cpp:1099:17: error: format not a string literal and no format arguments Added tag(s) pending. -- 1071340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1071341 marked as pending in r-bioc-genefilter
Processing control commands: > tag -1 pending Bug #1071341 [src:r-bioc-genefilter] r-bioc-genefilter: FTBFS: nd.c:75:21: error: format not a string literal and no format arguments Added tag(s) pending. -- 1071341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: update bug metadata
Processing commands for cont...@bugs.debian.org: > found 1076142 3.0.1-3 Bug #1076142 [src:soundkonverter] soundkonverter: Upstream development ceased in 2022, consider removal? Marked as found in versions soundkonverter/3.0.1-3. > tags 1076142 sid trixie Bug #1076142 [src:soundkonverter] soundkonverter: Upstream development ceased in 2022, consider removal? Ignoring request to alter tags of bug #1076142 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1076142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: update bug metadata
Processing commands for cont...@bugs.debian.org: > reassign 1076142 src:soundkonverter Bug #1076142 [src:soundkoverter] soundkonverter: Upstream development ceased in 2022, consider removal? Warning: Unknown package 'src:soundkoverter' Bug reassigned from package 'src:soundkoverter' to 'src:soundkonverter'. No longer marked as found in versions soundkoverter/3.0.1-3. Ignoring request to alter fixed versions of bug #1076142 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1076142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1070842 marked as pending in r-bioc-mutationalpatterns
Processing control commands: > tag -1 pending Bug #1070842 [src:r-bioc-mutationalpatterns] r-bioc-mutationalpatterns: autopkgtest regression with r-base 4.4.0 Added tag(s) pending. -- 1070842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070842: marked as pending in r-bioc-mutationalpatterns
Control: tag -1 pending Hello, Bug #1070842 in r-bioc-mutationalpatterns 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/r-pkg-team/r-bioc-mutationalpatterns/-/commit/96d3cd2a823d90cdd9b628471ef80990839b Ready to upload to experimental New upstream version fixes autopkgtest regression with r-base 4.4.0 Closes: #1070842 (this message was generated automatically) -- Greetings https://bugs.debian.org/1070842
Bug#1076142: soundkonverter: Upstream development ceased in 2022, consider removal?
Source: soundkoverter Version: 3.0.1-3 Tags: sid trixie Severity: serious X-Debbugs-CC: m...@debian.org mes...@debian.org p...@debian.org Dear Debian soundkonverter package maintainer, The upstream GitHub repository, https://github.com/dfaust/soundkonverter , has been archived since 2022. It is obvious that the upstream for soundkonverter is now dead. As a result, please consider excluding this package from the future Trixie release or have it completely removed from Debian Sid/Testing archive. Otherwise we the Debian package maintainers will need to maintain this software by ourselves. An imminent issue would be taglib 2.0 compatibility (which I will submit in a separate RC bug very soon). Please feel free to let me know if you have any thoughts. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072632: marked as done (r-cran-rsqlite: autopkgtest regression in testing)
Your message dated Thu, 11 Jul 2024 11:34:34 +
with message-id
and subject line Bug#1072632: fixed in r-cran-rsqlite 2.3.7-2
has caused the Debian Bug report #1072632,
regarding r-cran-rsqlite: autopkgtest regression 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.)
--
1072632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-rsqlite
Version: 2.3.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Sometime around 2024-02-16, r-cran-rsqlite's autopkgtest regressed in
testing [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-rsqlite/testing/amd64/
68s ══ Failed tests
68s ── Failure ('test-affinity.R:98:3'): affinity checks for dbFetch()
─
68s `expect_equal(class(dbFetch(rs, 1)$a), real_type)` threw an
unexpected warning.
68s Message: Changing language has no effect when envvar LC_ALL='C.UTF-8'
68s Class: simpleWarning/warning/condition
68s Backtrace:
68s ▆
68s 1. ├─... %>% expect_warning("coercing") at test-affinity.R:98:3
68s 2. ├─testthat::expect_warning(., "coercing")
68s 3. │ └─testthat:::expect_condition_matching(...)
68s 4. │ └─testthat:::quasi_capture(...)
68s 5. │ ├─testthat (local) .capture(...)
68s 6. │ │ └─base::withCallingHandlers(...)
68s 7. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 8. ├─testthat::expect_warning(., "coercing")
68s 9. │ └─testthat:::expect_condition_matching(...)
68s 10. │ └─testthat:::quasi_capture(...)
68s 11. │ ├─testthat (local) .capture(...)
68s 12. │ │ └─base::withCallingHandlers(...)
68s 13. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 14. ├─testthat::expect_warning(., "coercing")
68s 15. │ └─testthat:::expect_condition_matching(...)
68s 16. │ └─testthat:::quasi_capture(...)
68s 17. │ ├─testthat (local) .capture(...)
68s 18. │ │ └─base::withCallingHandlers(...)
68s 19. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 20. ├─testthat::expect_warning(., "coercing")
68s 21. │ └─testthat:::expect_condition_matching(...)
68s 22. │ └─testthat:::quasi_capture(...)
68s 23. │ ├─testthat (local) .capture(...)
68s 24. │ │ └─base::withCallingHandlers(...)
68s 25. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 26. ├─testthat::expect_warning(., "coercing")
68s 27. │ └─testthat:::expect_condition_matching(...)
68s 28. │ └─testthat:::quasi_capture(...)
68s 29. │ ├─testthat (local) .capture(...)
68s 30. │ │ └─base::withCallingHandlers(...)
68s 31. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 32. ├─testthat::expect_warning(., "coercing")
68s 33. │ └─testthat:::expect_condition_matching(...)
68s 34. │ └─testthat:::quasi_capture(...)
68s 35. │ ├─testthat (local) .capture(...)
68s 36. │ │ └─base::withCallingHandlers(...)
68s 37. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 38. ├─testthat::expect_warning(., "coercing")
68s 39. │ └─testthat:::expect_condition_matching(...)
68s 40. │ └─testthat:::quasi_capture(...)
68s 41. │ ├─testthat (local) .capture(...)
68s 42. │ │ └─base::withCallingHandlers(...)
68s 43. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 44. ├─testthat::expect_warning(., "coercing")
68s 45. │ └─testthat:::expect_condition_matching(...)
68s 46. │ └─testthat:::quasi_capture(...)
68s 47. │ ├─testthat (local) .capture(...)
68s 48. │ │ └─base::withCallingHandlers(...)
68s 49. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 50. └─RSQLite (local) check_affinity_fetch("BLOB", class(blob()),
class(blob()))
68s 51. ├─testthat::expect_warning(...) at test-affinity.R:60:3
68s 52. │ └─testthat:::expect_condition_matching(...)
68s 53. │ └─testthat:::quasi_capture(...)
68s 54. │ ├─testthat (local) .capture(...)
68s 55. │ │ └─base::withCallingHandlers(...)
68s 56. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
68s 57. └─testthat::expect_equal(class(dbFetch(rs, 1)$a), real_type)
68s 58. └─testthat:::expect_waldo_equal("equal", act, exp, info, ...,
tolerance = tolerance)
68s 59. └─testthat:::waldo_compare(...)
68s 60. └─testthat:::local_reporter_output()
68s 61. └─reporter$local_user_output(.env)
68s 62. └─testthat::local_reproducible_output(...)
68s 63. └─withr::local_language(lang, .local_envir = .env)
68s 64. └─withr:::check_language_envvar("LC_ALL")
68s
68s [ FAIL 1 | WARN 842 | SKIP 8 | PASS 684 ]
68s Error: Test failures
68s In addition: W
Bug#1076120: onboard: Segmentation Fault on Mouse Hover After Update to Version 1.4.1-7
On Thu, 11 Jul 2024 07:51:30 + Mike Gabriel wrote: > Hi, > > On Do 11 Jul 2024 04:01:21 CEST, KeyofBlueS wrote: > > > Package: onboard > > Version: 1.4.1-7 > > Severity: grave > > Justification: renders package unusable > > X-Debbugs-Cc: keyofbl...@gmail.com > > > > Dear Maintainer, > > > > After updating Onboard from version 1.4.1-6 to 1.4.1-7, the > > application crashes > > with a segmentation fault as soon as the mouse cursor hovers over its window. > > This issue did not occur in the previous version. > > > > Steps to Reproduce: > > - Update Onboard to version 1.4.1-7 > > - Open Onboard. > > - Move the mouse cursor over the Onboard window. > > > > Attached is the log file generated by Onboard during the crash. > > > > Thank you for your attention to this matter. Please let me know if > > any further > > information is required. > > > > Best regards. > > I rebuilt onboard 1.4.1-6 (against Python 3.12, the uploaded version > was still using Python 3.11) and the crash also occurs in onboard > 1.4.1-6. > > Can check your /var/log/dpkg.log and let me know what other packages > got upgraded when upgrading onboard? > > Mike > -- > > mike gabriel aka sunweaver (Debian Developer) > mobile: +49 (1520) 1976 148 > landline: +49 (4351) 486 14 27 > > GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 > mail: sunwea...@debian.org, http://sunweavers.net > Hi Mike, attached is the dpkg.log Thanks. 2024-07-11 00:30:58 startup packages configure 2024-07-11 00:30:59 startup packages configure 2024-07-11 00:33:40 startup archives unpack 2024-07-11 00:33:40 upgrade python3-venv:amd64 3.11.8-1 3.12.3-1 2024-07-11 00:33:40 status half-configured python3-venv:amd64 3.11.8-1 2024-07-11 00:33:40 status unpacked python3-venv:amd64 3.11.8-1 2024-07-11 00:33:40 status half-installed python3-venv:amd64 3.11.8-1 2024-07-11 00:33:41 status unpacked python3-venv:amd64 3.12.3-1 2024-07-11 00:33:41 upgrade python3-uno:amd64 4:24.2.4-1+b1 4:24.2.4-1+b2 2024-07-11 00:33:41 status half-configured python3-uno:amd64 4:24.2.4-1+b1 2024-07-11 00:33:41 status unpacked python3-uno:amd64 4:24.2.4-1+b1 2024-07-11 00:33:41 status half-installed python3-uno:amd64 4:24.2.4-1+b1 2024-07-11 00:33:41 status triggers-pending libreoffice-common:all 4:24.2.4-1 2024-07-11 00:33:41 status unpacked python3-uno:amd64 4:24.2.4-1+b2 2024-07-11 00:33:41 upgrade python3-tdb:amd64 1.4.10-1 1.4.10-1+b1 2024-07-11 00:33:41 status triggers-pending libc-bin:amd64 2.38-14 2024-07-11 00:33:41 status half-configured python3-tdb:amd64 1.4.10-1 2024-07-11 00:33:41 status unpacked python3-tdb:amd64 1.4.10-1 2024-07-11 00:33:41 status half-installed python3-tdb:amd64 1.4.10-1 2024-07-11 00:33:41 status unpacked python3-tdb:amd64 1.4.10-1+b1 2024-07-11 00:33:41 upgrade libtalloc2:amd64 2.4.2-1+b1 2.4.2-1+b2 2024-07-11 00:33:41 status half-configured libtalloc2:amd64 2.4.2-1+b1 2024-07-11 00:33:41 status unpacked libtalloc2:amd64 2.4.2-1+b1 2024-07-11 00:33:41 status half-installed libtalloc2:amd64 2.4.2-1+b1 2024-07-11 00:33:41 status unpacked libtalloc2:amd64 2.4.2-1+b2 2024-07-11 00:33:41 upgrade python3-talloc:amd64 2.4.2-1+b1 2.4.2-1+b2 2024-07-11 00:33:41 status half-configured python3-talloc:amd64 2.4.2-1+b1 2024-07-11 00:33:41 status unpacked python3-talloc:amd64 2.4.2-1+b1 2024-07-11 00:33:41 status half-installed python3-talloc:amd64 2.4.2-1+b1 2024-07-11 00:33:42 status unpacked python3-talloc:amd64 2.4.2-1+b2 2024-07-11 00:33:42 upgrade python3-samba:amd64 2:4.20.2+dfsg-2 2:4.20.2+dfsg-6 2024-07-11 00:33:42 status half-configured python3-samba:amd64 2:4.20.2+dfsg-2 2024-07-11 00:33:42 status unpacked python3-samba:amd64 2:4.20.2+dfsg-2 2024-07-11 00:33:42 status half-installed python3-samba:amd64 2:4.20.2+dfsg-2 2024-07-11 00:33:42 status triggers-pending man-db:amd64 2.12.1-2 2024-07-11 00:33:42 status unpacked python3-samba:amd64 2:4.20.2+dfsg-6 2024-07-11 00:33:42 upgrade libpython3-dev:amd64 3.11.8-1 3.12.3-1 2024-07-11 00:33:42 status half-configured libpython3-dev:amd64 3.11.8-1 2024-07-11 00:33:42 status unpacked libpython3-dev:amd64 3.11.8-1 2024-07-11 00:33:42 status half-installed libpython3-dev:amd64 3.11.8-1 2024-07-11 00:33:42 status unpacked libpython3-dev:amd64 3.12.3-1 2024-07-11 00:33:42 upgrade python3-dev:amd64 3.11.8-1 3.12.3-1 2024-07-11 00:33:42 status half-configured python3-dev:amd64 3.11.8-1 2024-07-11 00:33:42 status unpacked python3-dev:amd64 3.11.8-1 2024-07-11 00:33:42 status half-installed python3-dev:amd64 3.11.8-1 2024-07-11 00:33:42 status unpacked python3-dev:amd64 3.12.3-1 2024-07-11 00:33:43 upgrade python3-ldb:amd64 2:2.9.1+samba4.20.2+dfsg-2 2:2.9.1+samba4.20.2+dfsg-6 2024-07-11 00:33:43 status half-configured python3-ldb:amd64 2:2.9.1+samba4.20.2+dfsg-2 2024-07-11 00:33:43 status unpacked python3-ldb:amd64 2:2.9.1+samba4.20.2+dfsg-2 2024-07-11 00:33:43 status half-installed python3-ldb:amd64 2:2.9.1+samba4.20.2+dfsg-2 2024-07-11 00:33:43 status unpacked python3-ldb:amd64 2:2.9.1+samba4.20.2+dfsg-6 202
Bug#1074706: [Pkg-pascal-devel] Bug#1074706: fpc: FTBFS: make[1]: *** [Makefile:9: de] Error 1
On 09/07/2024 17:08, Peter B wrote: Until recently, fpc built OK, and msgfmt did not appear in the build logs. Sorry, I got that bit wrong. I was looking at the 'all' build not the 'amd64' msgfmt used to work, but no longer. It seems a header such as msgid "" msgstr "" "Content-Type: text/plain; charset=UTF-8\n" needs to be added, AND the encoding changed to UTF-8 Regards, Peter
Bug#1065837: cappuccino: Please drop dependencies on python3-distutils
Hello Emmanuel, On Wed, Jul 10, 2024 at 09:20:45PM -0300, Emmanuel Arias wrote: > Dear maintainer, > > I'm going to upload a NMU to fix this RC bug. I'm going to upload in > DELAYED/3-days. I attached the patch that I applied. > > If you have any objections or would you like to make the changes > yourself please let me know. Thank you so much for the upload. I am good with it!
Bug#1056360: marked as done (python3-wikitrans: [wikimarkup.py] 'str' object has no attribute 'decode')
Your message dated Thu, 11 Jul 2024 10:34:42 +
with message-id
and subject line Bug#1056360: fixed in wikitrans 1.4-1
has caused the Debian Bug report #1056360,
regarding python3-wikitrans: [wikimarkup.py] 'str' object has no attribute
'decode'
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.)
--
1056360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-wikitrans
Version: 1.3-2
Severity: grave
Control: affects -1 dico-module-mediawiki
Usertags: pca.it-communication
Hi there,
after the dicod's `load python`[1] and `M4 quoting`[2], querying the
WikiMedia databases gives no match and the following errors in `dicod`:
```
root@harlock:~# /usr/bin/dicod --stderr -f
dicod: Info: dicod (GNU dico) 2.11 started
dicod: Info: Client info: "GNU dico 2.11"
dicod: Info: Client info: "GNU dico 2.11"
dicod: Debug: 57843 exited successfully
dicod: Info: Client info: "GNU dico 2.11"
dicod: Error: Traceback (most recent call last):
dicod: Error: File "/usr/share/dico/python/mediawiki.py", line 98, in
define_word
dicod: Error: wikiparser = TextWiktionaryMarkup (text=data)
dicod: Error:
dicod: Error: File "/usr/lib/python3/dist-packages/wikitrans/wiki2text.py",
line 278, in __init__
dicod: Error: super(TextWikiMarkup, self).__init__(*args, **keywords)
dicod: Error: File "/usr/lib/python3/dist-packages/wikitrans/wikimarkup.py",
line 1028, in __init__
dicod: Error: self.text = keywords[kw].decode('utf-8').split("\n")
dicod: Error: ^^^
dicod: Error: AttributeError: 'str' object has no attribute 'decode'. Did you
mean: 'encode'?
dicod: Debug: 57846 exited successfully
dicod: Debug: 57847 exited successfully
^Cdicod: Info: dicod (GNU dico) 2.11 terminating
root@harlock:~#
```
[1]
[2]
I am not a Python expert, the problem obviously disappears (and the
query succeeds) if I remove the conditional case at line 1027, which
seems bad to me since AFAIK only from Python3 `str` contains by
default UTF-8/Unicode characters[3] (and anyway user input could not
be in UTF-8):
```
elif kw == 'text':
if sys.version_info[0] > 2:
self.text = keywords[kw].decode('utf-8').split("\n")
else:
self.text = keywords[kw].split("\n")
```
[3]
Thx, bye,
Gismo / Luca
-- System Information:
Debian Release: 12.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldoldstable'), (500,
'stable'), (500, 'oldstable'), (100, 'bookworm-fasttrack'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-0.deb12.1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-wikitrans depends on:
ii python3 3.11.2-1+b1
python3-wikitrans recommends no packages.
python3-wikitrans suggests no packages.
-- no debconf information
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: wikitrans
Source-Version: 1.4-1
Done: Marc Dequènes (Duck)
We believe that the bug you reported is fixed in the latest version of
wikitrans, 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 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Marc Dequènes (Duck) (supplier of updated wikitrans package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 08 Jul 2024 18:36:53 +0200
Source: wikitrans
Architecture: source
Version: 1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Marc Dequènes (Duck)
Closes: 1056360
Changes:
wikitrans (1.4-1) unstable; urgency=medium
.
* New upstream version
Bug#1076127: (build-)dependency on removed python3-distutils
Control: tags -1 moreinfo upstream Control: severity -1 wishlist On Thu, 11 Jul 2024 08:08:05 +0200 Matthias Klose wrote: > Source: azure-cli > Version: 2.62.0-1 > Severity: serious > Tags: sid trixie > User: debian-pyt...@lists.debian.org > Usertags: python3.12 > > there are (build-)dependency on the now removed python3-distutils. > please remove them It's a runtime dependency, and it is still used, so it cannot just be removed. Have you file an upstream issue, or better yet, sent a PR upstream to provide an alternative? -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Processed: Re: (build-)dependency on removed python3-distutils
Processing control commands: > tags -1 moreinfo upstream Bug #1076127 [src:azure-cli] (build-)dependency on removed python3-distutils Added tag(s) moreinfo and upstream. > severity -1 wishlist Bug #1076127 [src:azure-cli] (build-)dependency on removed python3-distutils Severity set to 'wishlist' from 'serious' -- 1076127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1075980: marked as done (mpi4py: FTBFS with mpich as default MPI provider on 32 bit systems: testPackUnpackExternal (test_pack.TestPackExternal.testPackUnpackExternal) ... Conversion of types whos
Your message dated Thu, 11 Jul 2024 10:19:13 + with message-id and subject line Bug#1075980: fixed in mpi4py 3.1.6-2 has caused the Debian Bug report #1075980, regarding mpi4py: FTBFS with mpich as default MPI provider on 32 bit systems: testPackUnpackExternal (test_pack.TestPackExternal.testPackUnpackExternal) ... Conversion of types whose size is not the same as the size in external32 is not supported 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.) -- 1075980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mpi4py Version: 3.1.6-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=mpi4py&arch=armel&ver=3.1.6-1%2Bb1&stamp=1720427513&raw=0 testMessageNoProc (test_p2p_obj_matched.TestMessage.testMessageNoProc) ... ok testMessageNull (test_p2p_obj_matched.TestMessage.testMessageNull) ... ok testIMProbe (test_p2p_obj_matched.TestP2PMatchedSelf.testIMProbe) ... ok testProbeRecv (test_p2p_obj_matched.TestP2PMatchedSelf.testProbeRecv) ... ok testIMProbe (test_p2p_obj_matched.TestP2PMatchedSelfDup.testIMProbe) ... ok testProbeRecv (test_p2p_obj_matched.TestP2PMatchedSelfDup.testProbeRecv) ... ok testIMProbe (test_p2p_obj_matched.TestP2PMatchedWorld.testIMProbe) ... ok testProbeRecv (test_p2p_obj_matched.TestP2PMatchedWorld.testProbeRecv) ... ok testIMProbe (test_p2p_obj_matched.TestP2PMatchedWorldDup.testIMProbe) ... ok testProbeRecv (test_p2p_obj_matched.TestP2PMatchedWorldDup.testProbeRecv) ... ok testPackSize (test_pack.TestPackExternal.testPackSize) ... ok testPackUnpackExternal (test_pack.TestPackExternal.testPackUnpackExternal) ... Conversion of types whose size is not the same as the size in external32 is not supported Aborting with internal error [unset]: PMIU_write error; fd=-1 buf=:cmd=abort exitcode=1 message=Aborting with internal error : system msg for write_line failure : Bad file descriptor make[1]: *** [debian/rules:91: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:52: binary-arch] Error 2 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: mpi4py Source-Version: 3.1.6-2 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of mpi4py, 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 1075...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated mpi4py package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jul 2024 11:22:23 +0200 Source: mpi4py Architecture: source Version: 3.1.6-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 1075980 Changes: mpi4py (3.1.6-2) unstable; urgency=medium . * debian patch skip_failing_tests_32bit_mpich.patch skips failing tests with 32-bit mpich. See upstream Issue#514. Closes: #1075980. - armel, armhf, hppa: testPackUnpackExternal (test_pack.py) - powerpc: testArgsOnlyAtRoot (test_spawn.py) Checksums-Sha1: bb123f5777c0a94faf0cd90a955a598c279d3479 2499 mpi4py_3.1.6-2.dsc 6a76767ed0807ad685bba22a6b9e2bd0a5f05d07 13848 mpi4py_3.1.6-2.debian.tar.xz Checksums-Sha256: 0c83514cd197ebaaed8becc682995cca7bdf28c731601652f06e9fdd8b0c3f58 2499 mpi4py_3.1.6-2.dsc 83ac859b47fc0ef260741d8ddd925e6f5474a22b47168ef1c4af6813459b17a9 13848 mpi4py_3.1.6-2.debian.tar.xz Files: 626c056d2504a4495e5ebee658af5b93 2499 python optional mpi4py_3.1.6-2.dsc 5538eacdfd284c88a72dd46647b8d95a 13848 python optional mpi4py_3.1.6-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmaPrBAACgkQVz7x5L1a Afq5rxAAlG2uWYsLeDsFDZXmwh55SCuZd0MhR5cJygsodDdAH/EtPYzYH00vg3/K PqiAXsI0dmXV/Y8x3gS5QjXv2Sc9B/bk1KO4M0UBN3lsFtn2xHl+h59BzCtBK1Zl fwzp/uQcchS3TXW3hBzzMNcIY+4+0CpyfuAiDJo0TvlbQKD9g70D+sG4NeZajN98 2oG3OmpP2R5Gw9vLndBT2CvuoDFVS/E070aFac09PoRhzzlHeN29/NVphMr6w2Hx 3nh6iBOu/hb0Rej0Q8zdeO63uEvMI7fgFyEbqO3/b1pQuhpJXRdJLBf2o0
Bug#1074639: marked as done (muon-meson: FTBFS: collect2: error: ld returned 1 exit status)
Your message dated Thu, 11 Jul 2024 10:07:47 + with message-id and subject line Bug#1074639: fixed in muon-meson 0.2.0-2 has caused the Debian Bug report #1074639, regarding muon-meson: FTBFS: collect2: error: ld returned 1 exit status 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.) -- 1074639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: muon-meson Version: 0.2.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240702 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 '/<>' > mkdir build/home > HOME=$(realpath build/home) build/muon -C build test -v > ninja: no work to do. > ninja: no work to do. > running tests for project 'muon' > [ok ] 0.01s, fmt:fmt > [ok ] 0.02s, lang:array.meson > [fail*] 0.02s, lang:badnum.meson > [ok ] 0.02s, lang:configuration_data.meson > [ok ] 0.02s, lang:dict.meson > [ok ] 0.03s, lang:disabler.meson > [ok ] 0.03s, lang:environment.meson > [ok ] 0.03s, lang:fstring.meson > [ok ] 0.03s, lang:join.meson > [ok ] 0.02s, lang:join_paths.meson > [ok ] 0.02s, lang:katie.meson > [ok ] 0.02s, lang:multiline.meson > [ok ] 0.02s, lang:strings.meson > [ok ] 0.02s, lang:ternary.meson > [ok ] 0.02s, lang:unicode.meson > [ok ] 0.02s, lang:version_compare.meson > [ok ] 0.11s, lang:run_command.meson > [ok ] 0.15s, [project, muon]:muon/sizeof_invalid > [ok ] 0.20s, [project, common]:common/1 trivial > [ok ] 0.15s, [project, common]:common/3 static > [ok ] 0.17s, [project, common]:common/4 shared > [ok ] 0.19s, [project, common]:common/5 linkstatic > [ok ] 0.26s, [project, common]:common/6 linkshared > [ok ] 0.21s, [project, common]:common/7 mixed > [ok ] 0.66s, [project, common]:common/2 cpp > [ok ] 0.08s, [project, common]:common/9 header install > [ok ] 0.14s, [project, common, requires_python]:common/8 install > [ok ] 0.08s, [project, common]:common/10 man install > [ok ] 0.07s, [project, common]:common/12 data > [ok ] 0.14s, [project, common]:common/11 subdir > [ok ] 0.17s, [project, common]:common/15 if > [ok ] 0.23s, [project, common]:common/17 array > [ok ] 0.34s, [project, common]:common/16 comparison > [ok ] 0.15s, [project, common]:common/19 header in file list > [ok ] 0.18s, [project, common]:common/18 includedir > [ok ] 0.24s, [project, common]:common/20 global arg > [fail*] 1.69s, [project, muon]:muon/timeout > [ok ] 0.29s, [project, common]:common/21 target arg > [ok ] 1.17s, [project, common, requires_python]:common/14 configure file > [ok ] 0.30s, [project, common]:common/23 endian > [ok ] 0.30s, [project, common]:common/24 library versions > [ok ] 0.39s, [project, common, requires_python]:common/22 object > extraction > [ok ] 0.14s, [project, common]:common/25 config subdir > [ok ] 0.12s, [project, common]:common/27 multiline string > [ok ] 0.08s, [project, common]:common/29 compiler id > [ok ] 0.25s, [project, common, requires_python]:common/26 find program > [ok ] 0.29s, [project, common]:common/28 try compile > [ok ] 0.15s, [project, common]:common/31 define10 > [ok ] 0.08s, [project, common]:common/34 logic ops > [ok ] 0.07s, [project, common]:common/35 string operations > [ok ] 0.18s, [project, common, requires_python]:common/33 run program > [ok ] 0.30s, [project, common]:common/32 has header > [ok ] 0.50s, [project, common]:common/30 sizeof > [fail ] 0.14s, [project, common]:common/36 has function > [ok ] 0.08s, [project, common]:common/40 options > [ok ] 0.34s, [project, common]:common/37 has member > [ok ] 0.23s, [project, common]:common/39 library chain > [ok ] 0.24s, [project, common, requires_python]:common/41 test args > [ok ] 0.10s, [project, common]:common/43 subproject options > [ok ] 0.21s, [project, common]:common/42 subproject > [ok ] 0.54s, [project, common]:common/38 alignment > [ok ] 0.19s, [project, common]:common/45 custom install dirs > [ok ] 0.17s, [project, common]:common/47 same file name > [ok ] 0.32s, [project, common, requires_python]:common/44 pkgconfig-gen > [ok ] 0.26s, [project, common]:common/46 subproject subproject > [ok ] 0.10s, [project, common, requires_python]:common/49 custom target > [ok ] 0.19s, [project, common]:common/48 fil
Processed: Bug#1075980 marked as pending in mpi4py
Processing control commands: > tag -1 pending Bug #1075980 [src:mpi4py] mpi4py: FTBFS with mpich as default MPI provider on 32 bit systems: testPackUnpackExternal (test_pack.TestPackExternal.testPackUnpackExternal) ... Conversion of types whose size is not the same as the size in external32 is not supported Added tag(s) pending. -- 1075980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1075980: marked as pending in mpi4py
Control: tag -1 pending Hello, Bug #1075980 in mpi4py 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/science-team/mpi4py/-/commit/4abea17ca1883321cf9421dcf87f3a8f215f91dd add debian patch skip_failing_tests_32bit_mpich.patch skips failing tests with 32-bit mpich. - armel, armhf, hppa: testPackUnpackExternal (test_pack.py) - powerpc: testArgsOnlyAtRoot (test_spawn.py) identify arch with platform.machine() armel, armhf: 'arm' hppa: 'parisc' powerpc: 'ppc' https://wiki.debian.org/ArchitectureSpecificsMemo See upstream Issue#514. https://github.com/mpi4py/mpi4py/issues/514 Closes: #1075980 (this message was generated automatically) -- Greetings https://bugs.debian.org/1075980
Bug#1074729: marked as done (golang-github-safchain-ethtool: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/safchain/ethtool github.com/safchain/ethtool/exa
Your message dated Thu, 11 Jul 2024 11:30:01 +0200 with message-id <9f57c7a5-5e7b-47ef-80dc-529cf03b2...@debian.org> and subject line Re: golang-github-safchain-ethtool: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/safchain/ethtool github.com/safchain/ethtool/example returned exit code 1 has caused the Debian Bug report #1074729, regarding golang-github-safchain-ethtool: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/safchain/ethtool github.com/safchain/ethtool/example returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1074729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-safchain-ethtool Version: 0.4.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240702 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 > github.com/safchain/ethtool github.com/safchain/ethtool/example > internal/goos > internal/coverage/rtcov > internal/goarch > internal/godebugs > internal/unsafeheader > internal/goexperiment > runtime/internal/atomic > internal/cpu > runtime/internal/syscall > internal/chacha8rand > internal/abi > runtime/internal/math > runtime/internal/sys > internal/race > sync/atomic > unicode > unicode/utf8 > internal/itoa > math/bits > internal/bytealg > cmp > encoding > log/internal > slices > math > runtime > internal/reflectlite > sync > internal/testlog > errors > sort > internal/oserror > internal/safefilepath > path > io > strconv > syscall > strings > bytes > reflect > internal/syscall/execenv > internal/syscall/unix > time > io/fs > internal/poll > internal/fmtsort > encoding/binary > os > golang.org/x/sys/unix > fmt > encoding/hex > log > flag > github.com/safchain/ethtool > github.com/safchain/ethtool/example >dh_auto_test -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 > github.com/safchain/ethtool github.com/safchain/ethtool/example > ? github.com/safchain/ethtool/example [no test files] > === RUN TestCmdGet > ethtool_cmd_test.go:46: Unable to get settings from any interface of this > system. > --- FAIL: TestCmdGet (0.00s) > === RUN TestCmdGetMapped > ethtool_cmd_test.go:66: Unable to get settings map from any interface of > this system. > --- FAIL: TestCmdGetMapped (0.00s) > === RUN TestMsglvlGet > --- PASS: TestMsglvlGet (0.00s) > === RUN TestGoString > --- PASS: TestGoString (0.00s) > === RUN TestStats > --- PASS: TestStats (0.00s) > === RUN TestDriverName > --- PASS: TestDriverName (0.00s) > === RUN TestBusInfo > --- PASS: TestBusInfo (0.00s) > === RUN TestSupportedLinkModes > --- PASS: TestSupportedLinkModes (0.00s) > === RUN TestFeatures > --- PASS: TestFeatures (0.00s) > FAIL > FAIL github.com/safchain/ethtool 0.007s > FAIL > dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 > github.com/safchain/ethtool github.com/safchain/ethtool/example returned exit > code 1 The full build log is available from: http://qa-logs.debian.net/2024/07/02/golang-github-safchain-ethtool_0.4.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240702&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 --- This should have been taken care of with the latest upload (0.4.1-1). OpenPGP_signature.asc Description: OpenPGP digit
Bug#1076136: AttributeError: module 'ssl' has no attribute 'wrap_socket' with Python 3.12
Package: python3-mysql.connector
Version: 8.0.15-4
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
After the update to Python 3.12, I can no longer use the
mysql.connector.connect function due to this error:
File "/usr/lib/python3/dist-packages/mysql/connector/__init__.py", line 173,
in connect
return MySQLConnection(*args, **kwargs)
File "/usr/lib/python3/dist-packages/mysql/connector/connection.py", line
102, in __init__
self.connect(**kwargs)
File "/usr/lib/python3/dist-packages/mysql/connector/abstracts.py", line 735,
in connect
self._open_connection()
File "/usr/lib/python3/dist-packages/mysql/connector/connection.py", line
250, in _open_connection
self._do_auth(self._user, self._password,
File "/usr/lib/python3/dist-packages/mysql/connector/connection.py", line
155, in _do_auth
self._socket.switch_to_ssl(ssl_options.get('ca'),
File "/usr/lib/python3/dist-packages/mysql/connector/network.py", line 427,
in switch_to_ssl
self.sock = ssl.wrap_socket(
^^^
AttributeError: module 'ssl' has no attribute 'wrap_socket'
It seems that Python 3.12 removed the ssl.wrap_socket() function (see
https://docs.python.org/3.12/whatsnew/3.12.html#ssl).
Regards, Daniel
- -- System Information:
Debian Release: trixie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500,
'testing'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.9.8-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-mysql.connector depends on:
ii python3 3.12.3-1
ii python3-protobuf 3.21.12-8.2
python3-mysql.connector recommends no packages.
python3-mysql.connector suggests no packages.
- -- no debconf information
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmaPpIEACgkQS80FZ8KW
0F07uRAAuJHnoY3Ds5a+i45FC2Dra7WvpedIWULgM9TjNDbIfFGPjKyIZfzBUpAB
5xvUZkP47K/HzByVRUcotI8ila/S11irtCMnij1n4Nbo+VC999X2XPXdtTIpEe/k
bmSlcGbHs7Fx3wgwuWhDZesZgXPSKu9ghr3NX1Pe+ew+U5Q7S2XeFPMAItIuddKV
q+p4xVrNuW0RsKVbX9VwSMClgfIquskie1wjMRFS8nbM6oPJuVJYzLNST0hhplmC
VnQ4EBMt52bvhQn4/izZ+HumykN0FNnsN2KZ9VRt3D/Jc1Ed/XVXYx1uSaRIliVK
QPBSP5U8pcwCLhvqyiqBrVfzn8iF5uFJdSyjhIajO6LMHW4D3MhQo5FG7ATpDzMt
STdZunDlZ3MeaC47lZzsQkd2UI/36MxjlRCcMk8LBc7+f4MUspbrdzZpZaTu9Dxi
v/6/GY2yl1MbCg1izgOWcMTAtswa0TfYX4OKaDtXvtUI8t53c5ESpkJ2s23bxuHI
EpHX1/r+UNDLg98naxFi8te3BiR9acvh7ub9c31/bFO8mn07NoOPDffcqOjdDaA4
uZ+4xje94k/RG3kZa5VUeEGrXpj+SDbpkME9G6mpBP2nkDEdxK7NpVK1V0sdS7nz
zG46G6kNT0pHWK1Nu7jsOJ8lzvjJzA7RRYFFPhL5xT2GEAHav98=
=Ld/f
-END PGP SIGNATURE-
Bug#1076131: libllvm18: declares itself as MA: same but is not co-installable
Hello, Le 11/07/2024 à 10:34, Sebastian Ramacher a écrit : Package: libllvm18 Version: 1:18.1.8-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org Error: Sub-process /usr/bin/dpkg returned an error code (1) Taking into account the usual reverse dependencies of llvm (such as mesa), having a co-installable libllvm18 is a requirement. I am filing this bug as serious as member of the RT. Please do not downgrade the severity of this bug before contacting the release team. ok, I think i know how to fix it! Thanks for the bug report Cheers S
Processed: tagging 1065869, merging 1065869 1076126
Processing commands for cont...@bugs.debian.org:
> tags 1065869 + patch sid trixie
Bug #1065869 {Done: Bas Couwenberg } [src:grass] grass:
Please drop dependencies on python3-distutils
Added tag(s) patch, trixie, and sid.
> merge 1065869 1076126
Bug #1065869 {Done: Bas Couwenberg } [src:grass] grass:
Please drop dependencies on python3-distutils
Bug #1076126 {Done: Sebastiaan Couwenberg } [src:grass]
(build-)dependency on removed python3-distutils
Marked as fixed in versions grass/8.4.0~rc1-1~exp1; no longer marked as fixed
in versions 8.4.0~rc1-1~exp1.
Merged 1065869 1076126
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1065869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065869
1076126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1060562: marked as done (iio-sensor-proxy: Please switch Build-Depends to systemd-dev)
Your message dated Thu, 11 Jul 2024 08:37:26 + with message-id and subject line Bug#1060562: fixed in iio-sensor-proxy 3.5-2 has caused the Debian Bug report #1060562, regarding iio-sensor-proxy: Please switch Build-Depends to systemd-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.) -- 1060562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: iio-sensor-proxy Version: 3.5-1 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-dev Hi, your package iio-sensor-proxy declares a Build-Depends on systemd and/or udev. In most cases, this build dependency is added to get the paths that are defined in udev.pc or systemd.pc (via pkgconfig). Since systemd_253-2 [1], these two pkgconfig files have been split into a separate package named systemd-dev. This package is arch:all, so even available on non-Linux architectures, which will simplify the installation of upstream provided service files / udev rules. To not make existing source packages FTBFS, the systemd and udev package have a Depends: systemd-dev. This dependency will be removed at some point though before trixie is released. Once this happens, this issue will be bumped to RC. Please update your build dependencies accordingly at your earliest convenience. If all you need is the systemd.pc or udev.pc pkgconfig file, please replace any systemd or udev Build-Depends with systemd-dev. In most cases that should be sufficient. If your package needs further resources from systemd or udev to build successfully, it's fine to keep those Build-Depends in addition to systemd-dev. To ease stable backports, a version of systemd with those changes is provided via bookworm-backports. In case you have further questions, please contact the systemd team at . On behalf of the systemd team, Michael [1] https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 --- End Message --- --- Begin Message --- Source: iio-sensor-proxy Source-Version: 3.5-2 Done: Guido Günther We believe that the bug you reported is fixed in the latest version of iio-sensor-proxy, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guido Günther (supplier of updated iio-sensor-proxy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jul 2024 09:38:42 +0200 Source: iio-sensor-proxy Architecture: source Version: 3.5-2 Distribution: unstable Urgency: medium Maintainer: Ritesh Raj Sarraf Changed-By: Guido Günther Closes: 1060562 Changes: iio-sensor-proxy (3.5-2) unstable; urgency=medium . * d/control: B-D on systemd-dev instead of udev/systemd (Closes: #1060562) * Fix mismatched lintian overrides * Add superficial autopkgtest * Override systemd-service-file-missing-install-key. It's a DBus activated service Checksums-Sha1: 54f0b5e0a113bded881be4362c07aaefdba5b12b 2099 iio-sensor-proxy_3.5-2.dsc 1c51f1403ab02b4f8cbd2e9884b0f25f2a6772af 4420 iio-sensor-proxy_3.5-2.debian.tar.xz aa2a98e0ad0889be0a3c9f8eb6bb9f0b0ff11f8c 15517 iio-sensor-proxy_3.5-2_amd64.buildinfo Checksums-Sha256: 0acc407605b71275bdf6d2de35973b6ee0790239623526e4b80dc037e965f34d 2099 iio-sensor-proxy_3.5-2.dsc 36b55127ad729f1ed9342f3d38ef20b38a30a02bd64bf265c45863d62b6859fc 4420 iio-sensor-proxy_3.5-2.debian.tar.xz f7413d0c780eaf7e89374a23c1a439861dab8344a342b9595dde3d2f1a9075f4 15517 iio-sensor-proxy_3.5-2_amd64.buildinfo Files: 68cc57afd977a19e472337f2971a2e9c 2099 utils optional iio-sensor-proxy_3.5-2.dsc bc9ff0dd15db218459d308ba04274c6e 4420 utils optional iio-sensor-proxy_3.5-2.debian.tar.xz 1f4ef5aad408a960a02f593f611aa86c 15517 utils optional iio-sensor-proxy_3.5-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEY/bM35YinQkoayrDJb+GUkr8weMFAmaPlIgACgkQJb+GUkr8 weNBrw//atYl2QfXxYTEtfb97X+VLWusxm/hAJFlOaCvz19F/R6bqX2LM1d2h5qx 8tTJ5UQf8p1bgE+5ThJNC2WaZizNNY+0YR5b9/6FBsHaRkvN4ZHPgzGgJ180pf9t Fd80Fu4yQbw/QsJgZxu/ovjkcD9gKsRtAA+uuXb6Yy2VtsqAuy7IUa4a/LXItncO o6dVJfmBWNvg08FFtlH/eCqBxuQ6ida2hYD0LllDX
Processed: grass: Please drop dependencies on python3-distutils
Processing commands for cont...@bugs.debian.org:
> severity 1065869 serious
Bug #1065869 {Done: Bas Couwenberg } [src:grass] grass:
Please drop dependencies on python3-distutils
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1065869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1076131: libllvm18: declares itself as MA: same but is not co-installable
Package: libllvm18 Version: 1:18.1.8-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org While libllvm18 declares itself to be MA: same, this is no longer the case: # apt install libllvm18:amd64 libllvm18:i386 libllvm18 is already the newest version (1:18.1.8-2). Installing: libllvm18:i386 Summary: Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 0 Download size: 0 B / 29.0 MB Space needed: 140 MB / 1091 GB available Continue? [Y/n] debconf: delaying package configuration, since apt-utils is not installed (Reading database ... 16581 files and directories currently installed.) Preparing to unpack .../libllvm18_1%3a18.1.8-2_i386.deb ... Unpacking libllvm18:i386 (1:18.1.8-2) ... dpkg: error processing archive /var/cache/apt/archives/libllvm18_1%3a18.1.8-2_i386.deb (--unpack): trying to overwrite shared '/usr/lib/llvm-18/lib/libLLVM-18.so.1', which is different from other instances of package libllvm18:i386 Errors were encountered while processing: /var/cache/apt/archives/libllvm18_1%3a18.1.8-2_i386.deb Error: Sub-process /usr/bin/dpkg returned an error code (1) Taking into account the usual reverse dependencies of llvm (such as mesa), having a co-installable libllvm18 is a requirement. I am filing this bug as serious as member of the RT. Please do not downgrade the severity of this bug before contacting the release team. Cheers -- Sebastian Ramacher
Bug#1076130: slepc's autopkg tests fail on armhf and i386, triggered by gcc-13
Source: slepc Version: 3.20.2+dfsg1-2 Severity: serious Tags: sid trixie slepc's autopkg tests fail on armhf and i386, triggered by gcc-13, see https://ci.debian.net/packages/s/slepc/testing/armhf/48828710/ https://ci.debian.net/packages/s/slepc/testing/i386/48834824/
Bug#1076120: onboard: Segmentation Fault on Mouse Hover After Update to Version 1.4.1-7
Hi, On Do 11 Jul 2024 04:01:21 CEST, KeyofBlueS wrote: Package: onboard Version: 1.4.1-7 Severity: grave Justification: renders package unusable X-Debbugs-Cc: keyofbl...@gmail.com Dear Maintainer, After updating Onboard from version 1.4.1-6 to 1.4.1-7, the application crashes with a segmentation fault as soon as the mouse cursor hovers over its window. This issue did not occur in the previous version. Steps to Reproduce: - Update Onboard to version 1.4.1-7 - Open Onboard. - Move the mouse cursor over the Onboard window. Attached is the log file generated by Onboard during the crash. Thank you for your attention to this matter. Please let me know if any further information is required. Best regards. I rebuilt onboard 1.4.1-6 (against Python 3.12, the uploaded version was still using Python 3.11) and the crash also occurs in onboard 1.4.1-6. Can check your /var/log/dpkg.log and let me know what other packages got upgraded when upgrading onboard? Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgpmi8QbwO8pv.pgp Description: Digitale PGP-Signatur
Bug#1074250: ifupdown2 not working with python3.12
On Tue, 25 Jun 2024 03:05:39 -0400 Dave B wrote: > Package: ifupdown2 > Version: 3.0.0-1.1 > Severity: grave > Tags: ipv6 > Justification: renders package unusable > > Dear Maintainer, > >* What led up to the situation? The upgrade to python3.12 which replaced "readfp" with "read_file) Dear maintainer, Please let the package depend on a specific, tested, python version (3.11 for now) instead of the generic python3 package. Python is infamously known for breaking backward compatibility on every occasion they get. For a critical package like ifupdown2, this random breakage is not acceptable. Depending on a specific pyhton verion should alleviate this problem a little bit. -- mvg, Alex Hermann
Bug#1076126: (build-)dependency on removed python3-distutils
On 7/11/24 8:53 AM, Matthias Klose wrote: On 11.07.24 08:43, Sebastiaan Couwenberg wrote: On 7/11/24 8:29 AM, Matthias Klose wrote: On 11.07.24 08:15, Sebastiaan Couwenberg wrote: Version: 8.4.0~rc1-1~exp1 On 7/11/24 8:07 AM, Matthias Klose wrote: there are (build-)dependency on the now removed python3-distutils. Already fixed via #1065869. please consider fixing it in unstable as well, or uploading the package to unstable. I'll upload 8.3.2-2 to unstable if the 8.4.0 release doesn't happen before grass is affected by a transition of one of its dependencies, or the testing autoremoval is triggered. Which ever happens first. this way, you are blocking the final stage of the python 3.12 transitions. grass is going to be autoremoved from testing any way due to #1074751 affecting wxpython4.0 which won't migrate to testing due to autopkgtest regressions and being blocked by sip6 which likewise won't migrate due to its own autopkgtest regressions. But this shouldn't matter, as grass is not part of the python3.12-only transition. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
