Bug#1053672: Apple copyright notices in test .xlsx files
On Sun, 2023-10-08 at 15:04 +0100, Rebecca N. Palmer wrote: > Given this, why is that copyright notice there, and what does it imply > that we should do? (E.g. does Apple Numbers automatically copy > Apple-owned items (e.g. fonts) into files it creates? If so, is there a > way to remove these items to get a Free file?) *.xlsx files are actually just *.zip files containing XML and other files. The Apple copyright for both of the files you mention comes from the Apple copyright listed for the ICC profile embedded in the EXIF data in the JPEG file that was saved as a thumbnail of the spreadsheet. I am not sure what that means for the license of the test cases in openpyxl and but it would be easy to fix by either deleting the thumbnail, or removing the ICC profile, but that would alter the test cases, probably that wouldn't affect the tests passing/failing though. $ unzip conditional-formatting.xlsx Archive: conditional-formatting.xlsx inflating: [Content_Types].xml inflating: _rels/.rels inflating: xl/_rels/workbook.xml.rels inflating: xl/workbook.xml extracting: docProps/thumbnail.jpeg inflating: xl/theme/theme1.xml inflating: xl/styles.xml inflating: xl/worksheets/sheet1.xml inflating: docProps/core.xml inflating: docProps/app.xml $ grep -ri apple grep: conditional-formatting.xlsx: binary file matches grep: docProps/thumbnail.jpeg: binary file matches $ exiftool docProps/thumbnail.jpeg | grep -i apple Profile CMM Type: Apple Computer Inc. Primary Platform: Apple Computer Inc. Device Manufacturer : Apple Computer Inc. Profile Creator : Apple Computer Inc. Profile Copyright : Copyright 2007 Apple Inc., all rights reserved. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1052996: marked as done (radicale FTBFS with the nocheck build profile)
Your message dated Mon, 09 Oct 2023 05:04:02 +
with message-id
and subject line Bug#1052996: fixed in radicale 3.1.8-3
has caused the Debian Bug report #1052996,
regarding radicale FTBFS with the nocheck build profile
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.)
--
1052996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: radicale
Version: 3.1.8-2
Severity: serious
Tags: ftbfs
radicale fails to build from source in unstable when adding the nocheck
build profile. Since trixie, such a failure is considered
release-critical. A build log ends as follows:
|debian/rules execute_after_dh_auto_install
| make[1]: Entering directory '/<>'
|
PATH="/<>/debian/tmp/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
PYTHONPATH="/<>/debian/tmp/usr/lib/python3.11/dist-packages"
help2man --name "a simple calendar server" --no-info --version-string="3.1.8-2"
--output debian/radicale.1 radicale || {
PATH="/<>/debian/tmp/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
PYTHONPATH="/<>/debian/tmp/usr/lib/python3.11/dist-packages"
radicale --help; false; }
| help2man: can't get `--help' info from radicale
| Try `--no-discard-stderr' if option outputs to stderr
| Traceback (most recent call last):
| File "/<>/debian/tmp/usr/bin/radicale", line 33, in
| sys.exit(load_entry_point('Radicale==3.1.8', 'console_scripts',
'radicale')())
|
^^
| File "/<>/debian/tmp/usr/bin/radicale", line 25, in
importlib_load_entry_point
| return next(matches).load()
|
| File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 202, in load
| module = import_module(match.group('module'))
|
| File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
| return _bootstrap._gcd_import(name[level:], package, level)
|
| File "", line 1204, in _gcd_import
| File "", line 1176, in _find_and_load
| File "", line 1126, in _find_and_load_unlocked
| File "", line 241, in _call_with_frames_removed
| File "", line 1204, in _gcd_import
| File "", line 1176, in _find_and_load
| File "", line 1147, in _find_and_load_unlocked
| File "", line 690, in _load_unlocked
| File "", line 940, in exec_module
| File "", line 241, in _call_with_frames_removed
| File
"/<>/debian/tmp/usr/lib/python3.11/dist-packages/radicale/__init__.py",
line 33, in
| from radicale.app import Application
| File
"/<>/debian/tmp/usr/lib/python3.11/dist-packages/radicale/app/__init__.py",
line 38, in
| from radicale.app.base import ApplicationBase
| File
"/<>/debian/tmp/usr/lib/python3.11/dist-packages/radicale/app/base.py",
line 29, in
| import defusedxml.ElementTree as DefusedET # isort:skip
| ^^
| ModuleNotFoundError: No module named 'defusedxml'
| make[1]: *** [debian/rules:41: execute_after_dh_auto_install] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:61: binary] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Helmut
--- End Message ---
--- Begin Message ---
Source: radicale
Source-Version: 3.1.8-3
Done: Jonas Smedegaard
We believe that the bug you reported is fixed in the latest version of
radicale, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard (supplier of updated radicale 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, 09 Oct 2023 06:47:23 +0200
Source: radicale
Architecture: source
Version: 3.1.8-3
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard
Changed-By: Jonas Smedegaard
Closes: 1052996
Changes:
radicale (3.1.8-3) unstable; urgency=medium
.
* build-depend unconditionally on python3-defusedxml;
Bug#1042123: marked as done (python-aiortc: FTBFS: unsatisfiable build-dependency: python3-aioice (< 0.9) but 0.9.0-1 is to be installed)
Your message dated Mon, 09 Oct 2023 04:49:06 + with message-id and subject line Bug#1042123: fixed in python-aiortc 1.5.0-1 has caused the Debian Bug report #1042123, regarding python-aiortc: FTBFS: unsatisfiable build-dependency: python3-aioice (< 0.9) but 0.9.0-1 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-aiortc Version: 1.4.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-sequence-python3, > dh-sequence-sphinxdoc, libopus-dev, libvpx-dev, python3-aioice (<< 0.9), > python3-aioice (>= 0.8), python3-all-dev, python3-av (<< 11), python3-av (>= > 9), python3-cffi, python3-crc32c, python3-cryptography, python3-openssl (>= > 23), pybuild-plugin-pyproject, python3-pyee (>= 9.0.0), python3-pylibsrtp, > python3-pytest, python3-pytest-asyncio, python3-pytest-timeout, > python3-setuptools, python3-sphinx, python3-sphinx-autodoc-typehints, > python3-sphinxcontrib-asyncio, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-sequence-python3, > dh-sequence-sphinxdoc, libopus-dev, libvpx-dev, python3-aioice (<< 0.9), > python3-aioice (>= 0.8), python3-all-dev, python3-av (<< 11), python3-av (>= > 9), python3-cffi, python3-crc32c, python3-cryptography, python3-openssl (>= > 23), pybuild-plugin-pyproject, python3-pyee (>= 9.0.0), python3-pylibsrtp, > python3-pytest, python3-pytest-asyncio, python3-pytest-timeout, > python3-setuptools, python3-sphinx, python3-sphinx-autodoc-typehints, > python3-sphinxcontrib-asyncio, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [575 B] > Get:5 copy:/<>/apt_archive ./ Packages [639 B] > Fetched 2177 B in 0s (164 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: python3-aioice (< 0.9) but > 0.9.0-1 is to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/07/26/python-aiortc_1.4.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See 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: python-aiortc Source-Version: 1.5.0-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of python-aiortc, 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,
Processed: Debian bugs control
Processing commands for cont...@bugs.debian.org: > retitle 1052838 mariadb: FTBFS multiple archs: Post-build tests randomly fail > on reserved port Bug #1052838 [src:mariadb] mariadb: FTBFS: make[1]: *** [debian/rules:161: override_dh_auto_test] Error 1 Changed Bug title to 'mariadb: FTBFS multiple archs: Post-build tests randomly fail on reserved port' from 'mariadb: FTBFS: make[1]: *** [debian/rules:161: override_dh_auto_test] Error 1'. > tags 1052838 ftbfs confirmed help Bug #1052838 [src:mariadb] mariadb: FTBFS multiple archs: Post-build tests randomly fail on reserved port Added tag(s) confirmed and help. > thanks Stopping processing here. Please contact me if you need assistance. -- 1052838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to radicale, tagging 1052996
Processing commands for cont...@bugs.debian.org: > limit source radicale Limiting to bugs with field 'source' containing at least one of 'radicale' Limit currently set to 'source':'radicale' > tags 1052996 + pending Bug #1052996 [src:radicale] radicale FTBFS with the nocheck build profile Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1052996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052838: [debian-mysql] Bug#1052838: Bug#1052838: mariadb: FTBFS: make[1]: *** [debian/rules:161: override_dh_auto_test] Error 1
I saw this now after 1:10.11.5-2 upload on multiple builders. Snippets from logs https://buildd.debian.org/status/fetch.php?pkg=mariadb=powerpc=1%3A10.11.5-2=1696735216=0 main.failed_auth_unixsocket w13 [ fail ] Test ended at 2023-10-08 03:17:49 CURRENT_TEST: main.failed_auth_unixsocket Failed to start mysqld.1 mysqltest failed but provided no output - saving '/<>/builddir/mysql-test/var/13/log/main.failed_auth_unixsocket/' to '/<>/builddir/mysql-test/var/log/main.failed_auth_unixsocket/' Retrying test main.failed_auth_unixsocket, attempt(2/3)... worker[13] > Restart - not started ***Warnings generated in error logs during shutdown after running tests: main.failed_auth_unixsocket 2023-10-08 3:17:49 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:17:49 0 [ERROR] Do you already have another server running on port: 16120 ? 2023-10-08 3:17:49 0 [ERROR] Aborting main.password_expiration_unix_socket w13 [ fail ] Test ended at 2023-10-08 03:18:16 CURRENT_TEST: main.password_expiration_unix_socket Failed to start mysqld.1 mysqltest failed but provided no output - skipping '/<>/builddir/mysql-test/var/13/log/main.password_expiration_unix_socket/' Retrying test main.password_expiration_unix_socket, attempt(2/3)... main.order_byw14 [ pass ] 3306 worker[13] > Restart - not started ***Warnings generated in error logs during shutdown after running tests: main.password_expiration_unix_socket 2023-10-08 3:18:16 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:18:16 0 [ERROR] Do you already have another server running on port: 16120 ? 2023-10-08 3:18:16 0 [ERROR] Aborting main.ssl_cipher w15 [ fail ]main.ssl_cipher w15 [ fail ] ... 2023-10-08 3:18:22 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:18:22 0 [ERROR] Do you already have another server running on port: 16140 ? main.func_intw13 [ fail ]main.func_int w13 [ fail ] ... 2023-10-08 3:18:42 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:18:42 0 [ERROR] Do you already have another server running on port: 16120 ? main.plugin_loaderr w6 [ fail ] ... 2023-10-08 3:18:59 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:18:59 0 [ERROR] Do you already have another server running on port: 16100 ? etc Failing test(s): main.failed_auth_unixsocket main.password_expiration_unix_socket main.ssl_cipher main.func_int main.grant_4332 main.plugin_loaderr main.func_isnull main.grant_binlog_replay main.func_json main.grant_cache_no_prot https://buildd.debian.org/status/fetch.php?pkg=mariadb=ppc64=1%3A10.11.5-2=1696735349=0 main.connect w3 [ fail ] Test ended at 2023-10-08 03:17:18 CURRENT_TEST: main.connect Failed to start mysqld.1 mysqltest failed but provided no output - saving '/<>/builddir/mysql-test/var/3/log/main.connect/' to '/<>/builddir/mysql-test/var/log/main.connect/' Retrying test main.connect, attempt(2/3)... worker[3] > Restart - not started ***Warnings generated in error logs during shutdown after running tests: main.connect 2023-10-08 3:17:18 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:17:18 0 [ERROR] Do you already have another server running on port: 16140 ? 2023-10-08 3:17:18 0 [ERROR] Aborting main.innodb_load_xa w5 [ fail ] .. 2023-10-08 3:17:33 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:17:33 0 [ERROR] Do you already have another server running on port: 16120 ? main.flush_block_commit_notembedded 'innodb' w3 [ fail ] ... 2023-10-08 3:17:45 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:17:45 0 [ERROR] Do you already have another server running on port: 16140 ? main.long_unique_innodb 'innodb' w9 [ fail ] ... 2023-10-08 3:19:29 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use 2023-10-08 3:19:29 0 [ERROR] Do you already have another server running on port: 16260 ? Both builds above ran on builder 'blaauw' with kernel Linux 6.5.0-1-powerpc64 #1 SMP Debian 6.5.3-1 (2023-09-13) ppc64 (ppc64) I have not been able to reproduce this on any Salsa-CI builders or on Launchpad.
Bug#1053314: Depends: python3-h5py-mpi without python3-h5py
Nilesh explained most of the situation correctly. I can give some more background.It made sense (to me) to have h5py built against hdf5-mpi, since I figured that if you need the complexity of the hdf5 file format then you probably want to use it in an MPI environment. There was a complaint from a user though, who wanted to make use of a massive ensemble of HDF5 (h5py) serial jobs, and the small cost of loading up MPI support was interfering with their throughput. So the compromise solution was to provide both builds, with a custom __init__.py to select the serial or MPI build depending on runtime environment. If an MPI environment is detected then the h5py MPI build is loaded, otherwise the serial build is loaded. If you want to run h5py in a serial process, then one might say you'd normally want the serial build. As Nilesh noted, I put in a mechanism to load the MPI build if you really want to access the mpi build in a serial process (mpirun -n 1 is not a "serial" process as such, it's still an MPI environment even though using only 1 process). The mechanism to force MPI loading is NOT to set OMPI_COMM_WORLD_SIZE. I recommend NOT doing that. I couldn't promise it won't mess up other things, certainly it will get in the way of an MPICH environment. No, the mechanism for handling this for h5py is described in /usr/share/doc/python3-h5py/README.Debian: set H5PY_ALWAYS_USE_MPI=1 Is there a way to force h5py to import _debian_h5py_serial instead of _debian_h5py_mpi, via the generic h5py namespace? It sounds like there is some confusion about how xmds2 should be used. Is it intended to be used as a serial process or MPI? I noted in the bug report that xmds2 Depends: libhdf5-serial-dev. Is it even using MPI? If you want it to be using h5py-serial, then why does xmsd2 depend on python3-h5py-mpi? It seems to me that xmds2's h5py dependency should be the same as its hdf5 dependency. If it uses libhdf5-serial then should it be depending on just python3-h5py (implying python3-h5py-serial, make it explicit if needed) and not depend on python3-h5py-mpi? If xmds2 is intended to be flexible, equally happy in serial and MPI environments (and can actually make use of h5py-mpi) then perhaps the dependency should cover all cases, Depends: python3-h5py, python3-h5py-serial, python3-h5py-mpi all three explicitly, since otherwise one or the other of -serial or -mpi would be missed. The problem raises interesting questions about h5py configuration. I set up it so you could choose how you want it to work, with or without MPI support. But it looks like an edge case is missing: it's failing in serial jobs if you chose to set up your installation with python3-h5py-mpi and explicitly don't want python3-h5py-serial (unless you always set H5PY_ALWAYS_USE_MPI). Perhaps I should add an additional fallback to try h5py-mpi if h5py-serial is not found (in a serial job), the same way that h5py-serial is loaded as a fallback in an MPI job if h5py-mpi is not found. On the other hand maybe that just hides the real problem, that h5py-serial was not installed when actually it was wanted after all. The ImportError correctly identifies that case. On 2023-10-08 17:38, Nilesh Patra wrote: Hello, On 10/8/23 17:22, Rafael Laboissière wrote: Ok, I tried to fix the building problem by including python3-h5py, alongside with python3-h5py-mpi, into Build-Depends, as suggested by Drew, but the xmds2 package FTBFS. Here is a way to reproduce the problem without building the package: $ dpkg -l python3-h5py\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-===---=== ii python3-h5py 3.9.0-3 all general-purpose Python interface to hdf5 ii python3-h5py-mpi 3.9.0-3 amd64 general-purpose Python interface to hdf5 (Python 3 MPI) un python3-h5py-serial (no description available) $ echo 'import h5py' | python3 Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/h5py/__init__.py", line 21, in from . import _debian_h5py_serial as _h5py ImportError: cannot import name '_debian_h5py_serial' from partially initialized module 'h5py' (most likely due to a circular import) (/usr/lib/python3/dist-packages/h5py/__init__.py) Is there a way to force h5py to import _debian_h5py_serial instead of _debian_h5py_mpi, via the generic h5py namespace? Drew would probably answer that question better but from taking a brief look, it seems to be on expected lines. This should work if you run it explicitly with mpi. $ mpirun -n 1 python3 -c "import h5py" && echo
Processed: Re: rust-async-process - update for new rustix.
Processing commands for cont...@bugs.debian.org: > severity 1050678 serious Bug #1050678 [rust-async-process] rust-async-process - update for new rustix. Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1050678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052813: marked as done (python-asdf: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Sun, 08 Oct 2023 21:38:18 +
with message-id
and subject line Bug#1052813: fixed in python-asdf 2.15.2-1
has caused the Debian Bug report #1052813,
regarding python-asdf: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p 3.11 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1052813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-asdf
Version: 2.15.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> 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:110: Building wheel for python3.11 with "build"
> module
> I: pybuild base:291: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.11_asdf
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/pytest_asdf
> copying pytest_asdf/__init__.py -> build/lib/pytest_asdf
> copying pytest_asdf/plugin.py -> build/lib/pytest_asdf
> creating build/lib/asdf
> copying asdf/reference.py -> build/lib/asdf
> copying asdf/_types.py -> build/lib/asdf
> copying asdf/_node_info.py -> build/lib/asdf
> copying asdf/types.py -> build/lib/asdf
> copying asdf/generic_io.py -> build/lib/asdf
> copying asdf/constants.py -> build/lib/asdf
> copying asdf/block.py -> build/lib/asdf
> copying asdf/tagged.py -> build/lib/asdf
> copying asdf/_version.py -> build/lib/asdf
> copying asdf/entry_points.py -> build/lib/asdf
> copying asdf/yamlutil.py -> build/lib/asdf
> copying asdf/_type_index.py -> build/lib/asdf
> copying asdf/__init__.py -> build/lib/asdf
> copying asdf/conftest.py -> build/lib/asdf
> copying asdf/resource.py -> build/lib/asdf
> copying asdf/exceptions.py -> build/lib/asdf
> copying asdf/versioning.py -> build/lib/asdf
> copying asdf/treeutil.py -> build/lib/asdf
> copying asdf/type_index.py -> build/lib/asdf
> copying asdf/asdf.py -> build/lib/asdf
> copying asdf/search.py -> build/lib/asdf
> copying asdf/_resolver.py -> build/lib/asdf
> copying asdf/fits_embed.py -> build/lib/asdf
> copying asdf/_helpers.py -> build/lib/asdf
> copying asdf/stream.py -> build/lib/asdf
> copying asdf/_display.py -> build/lib/asdf
> copying asdf/util.py -> build/lib/asdf
> copying asdf/config.py -> build/lib/asdf
> copying asdf/schema.py -> build/lib/asdf
> copying asdf/_convenience.py -> build/lib/asdf
> copying asdf/compression.py -> build/lib/asdf
> copying asdf/resolver.py -> build/lib/asdf
> copying asdf/asdftypes.py -> build/lib/asdf
> creating build/lib/asdf/tags
> copying asdf/tags/__init__.py -> build/lib/asdf/tags
> creating build/lib/asdf/commands
> copying asdf/commands/remove_hdu.py -> build/lib/asdf/commands
> copying asdf/commands/extract.py -> build/lib/asdf/commands
> copying asdf/commands/defragment.py -> build/lib/asdf/commands
> copying asdf/commands/info.py -> build/lib/asdf/commands
> copying asdf/commands/extension.py -> build/lib/asdf/commands
> copying asdf/commands/main.py -> build/lib/asdf/commands
> copying asdf/commands/__init__.py -> build/lib/asdf/commands
> copying asdf/commands/exploded.py -> build/lib/asdf/commands
> copying asdf/commands/diff.py -> build/lib/asdf/commands
> copying asdf/commands/tags.py -> build/lib/asdf/commands
> copying asdf/commands/to_yaml.py -> build/lib/asdf/commands
> copying asdf/commands/edit.py -> build/lib/asdf/commands
> creating build/lib/asdf/_tests
> copying asdf/_tests/test_search.py -> build/lib/asdf/_tests
> copying asdf/_tests/test_fits_embed.py -> build/lib/asdf/_tests
> copying asdf/_tests/test_stream.py -> build/lib/asdf/_tests
> copying asdf/_tests/test_treeutil.py -> build/lib/asdf/_tests
> copying asdf/_tests/test_yaml.py -> build/lib/asdf/_tests
> copying asdf/_tests/test_util.py -> build/lib/asdf/_tests
> copying asdf/_tests/__init__.py -> build/lib/asdf/_tests
> copying asdf/_tests/conftest.py -> build/lib/asdf/_tests
> copying asdf/_tests/test_deprecated.py -> build/lib/asdf/_tests
> copying asdf/_tests/test_types.py -> build/lib/asdf/_tests
> copying asdf/_tests/test_config.py ->
Processed: Re: graph-tool: FTBFS: fatal error: ld terminated with signal 9 [Killed] [cannot reproduce]
Processing commands for cont...@bugs.debian.org:
> found 1042029 2.45+ds-10
Bug #1042029 {Done: Jerome BENOIT } [src:graph-tool]
graph-tool: FTBFS: collect2: fatal error: ld terminated with signal 9 [Killed]
Did not alter found versions and reopened.
> tags 1042029 + patch
Bug #1042029 [src:graph-tool] graph-tool: FTBFS: collect2: fatal error: ld
terminated with signal 9 [Killed]
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1042029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042029: graph-tool: FTBFS: fatal error: ld terminated with signal 9 [Killed] [cannot reproduce]
found 1042029 2.45+ds-10
tags 1042029 + patch
thanks
El 26/7/23 a las 23:12, Jerome BENOIT escribió:
Hi Lucas, I could not reproduce the issue in the current Sid environment
(I tried twice) so I am closing the bug. It is highly probable that
your build encountered a resource issue as this software is really heavy to
build.
Hello.
This is certainly heavy to build.
However, it is so needlessly.
For example, configure.ac unconditionally adds -O3 to CXXFLAGS.
This is already a bug, because packages should honor whatever comes
from dpkg-buildflags (usually -O2).
Trivial patch attached. While I have not tested specifically if it solves
the issue for me, I think it is a patch which should be applied in either case.
[ For the record, I also tried to build this package and it also failed for me.
Last time I tried it was using a machine with 16 GB of RAM and 4 GB of swap.
To put things in perspective, I can build *all* the 35208 source packages
currently
in trixie with 16 GB of RAM. But not this one ].
Thanks.--- a/configure.ac
+++ b/configure.ac
@@ -65,7 +65,7 @@ dnl set default visibility
[CXXFLAGS="-fvisibility=default -fvisibility-inlines-hidden ${CXXFLAGS}"]
dnl set default optimizations
-[CXXFLAGS="-O3 ${CXXFLAGS}"]
+[CXXFLAGS="${CXXFLAGS}"]
dnl disable annoying boost warnings
[CPPFLAGS="-DBOOST_ALLOW_DEPRECATED_HEADERS ${CPPFLAGS}"]
Processed: unarchive
Processing commands for cont...@bugs.debian.org:
> unarchive 1042029
Bug #1042029 {Done: Jerome BENOIT } [src:graph-tool]
graph-tool: FTBFS: collect2: fatal error: ld terminated with signal 9 [Killed]
Unarchived Bug 1042029
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1042029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Only applies to bullseye
Processing commands for cont...@bugs.debian.org:
> found 1014556 91.0-1
Bug #1014556 [src:firefox-esr] firefox-esr: FTBFS on mipsel ("terminate called
after throwing an instance of 'std::bad_alloc'")
The source 'firefox-esr' and version '91.0-1' do not appear to match any binary
packages
Marked as found in versions firefox-esr/91.0-1.
> tags 1014556 bullseye
Bug #1014556 [src:firefox-esr] firefox-esr: FTBFS on mipsel ("terminate called
after throwing an instance of 'std::bad_alloc'")
Added tag(s) bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1014556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 1043059
Processing commands for cont...@bugs.debian.org: > close 1043059 Bug #1043059 [src:abseil] abseil/experimental FTBFS on mipsel Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1043059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053686: pandoc: cannot fulfill the build dependencies
Source: pandoc Version: 2.17.1.1-3 Severity: serious Tags: ftbfs builddeps:pandoc : Depends: libghc-aeson-dev (< 2.1) but 2.1.2.1-4 is to be installed Depends: libghc-doclayout-dev (< 0.4) but 0.4.0.1-1 is to be installed Depends: libghc-haddock-library-dev (< 1.11) but 1.11.0-1 is to be installed Depends: libghc-hslua-aeson-dev (< 2.2) but 2.3.0.1-1 is to be installed Depends: libghc-hslua-marshalling-dev (< 2.2) but 2.3.0-1 is to be installed Depends: libghc-jira-wiki-markup-dev (< 1.5) but 1.5.1-1 is to be installed Depends: libghc-pandoc-types-dev (< 1.23) but 1.23.1-1 is to be installed
Processed: src:procps: fails to migrate to testing for too long: FTBFS on amd64/i386 and autopkgtest elsewhere
Processing control commands:
> close -1 2:4.0.4-1
Bug #1053684 [src:procps] src:procps: fails to migrate to testing for too long:
FTBFS on amd64/i386 and autopkgtest elsewhere
Marked as fixed in versions procps/2:4.0.4-1.
Bug #1053684 [src:procps] src:procps: fails to migrate to testing for too long:
FTBFS on amd64/i386 and autopkgtest elsewhere
Marked Bug as done
> block -1 by 1052034
Bug #1053684 {Done: Paul Gevers } [src:procps] src:procps:
fails to migrate to testing for too long: FTBFS on amd64/i386 and autopkgtest
elsewhere
1053684 was not blocked by any bugs.
1053684 was not blocking any bugs.
Added blocking bug(s) of 1053684: 1052034
--
1053684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1053684: src:procps: fails to migrate to testing for too long: FTBFS on amd64/i386 and autopkgtest elsewhere
Source: procps Version: 2:4.0.3-1 Severity: serious Control: close -1 2:4.0.4-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1052034 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:procps has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable fails to build from source on amd64 and i386 as reported in bug 1052034. It fails it's own autopkgtest on all architectures where it runs. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=procps OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: affects 1053431
Processing commands for cont...@bugs.debian.org: > affects 1053431 src:rust-ripgrep Bug #1053431 [rust-grep-regex] rust-grep-regex - depends/build-depends on old version of regex-syntax Added indication that 1053431 affects src:rust-ripgrep > thanks Stopping processing here. Please contact me if you need assistance. -- 1053431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1053431
Processing commands for cont...@bugs.debian.org: > tags 1053431 + ftbfs Bug #1053431 [rust-grep-regex] rust-grep-regex - depends/build-depends on old version of regex-syntax Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1053440
Processing commands for cont...@bugs.debian.org: > affects 1053440 src:rust-sequoia-sqv src:rust-sequoia-sop > src:rust-sequoia-keyring-linter src:rust-sequoia-wot src:rust-ripasso-cursive Bug #1053440 [rust-sequoia-openpgp] rust-sequoia-openpgp - incompatible with new regex-syntax. Added indication that 1053440 affects src:rust-sequoia-sqv, src:rust-sequoia-sop, src:rust-sequoia-keyring-linter, src:rust-sequoia-wot, and src:rust-ripasso-cursive > thanks Stopping processing here. Please contact me if you need assistance. -- 1053440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1053440
Processing commands for cont...@bugs.debian.org: > tags 1053440 + ftbfs Bug #1053440 [rust-sequoia-openpgp] rust-sequoia-openpgp - incompatible with new regex-syntax. Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1053657 is normal
Processing commands for cont...@bugs.debian.org: > severity 1053657 normal Bug #1053657 [dhcpcd-base] dhcpcd-base has ineffective Replaces due to /usr-merge and looses files in upgrade Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1053657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052973: marked as done (octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1)
* Sébastien Villemot [2023-10-07 08:23]: Hi Rafael, Le samedi 07 octobre 2023 à 14:15 +0200, Rafael Laboissière a écrit : I have a question for the Debian Octave Group, related to Bug#1052973, which has been fixed in version 8.3.0-3 of octave-dev. This bug was preventing the building of the octave-image package. Should we include octave-dev >= 8.3.0-3 in Build-Depends of the otave-image package ? I would say no. If every time that a bug is fixed in a dependency, we were to bump the version requirement, then we would basically always depend on the latest version of every package. Ok, thanks for the advise. Also, it may be possible that octave-image builds against an old version of octave-dev that was not affected by the bug. Apparently (but I did not check it thoroughly) , the “bug” in mkoctifle was always there, but has only been exposed when the Debian build tools started injecting some new -f* options into CFLAGS that was propagated into the call of mkoctfile. This confuses mkoctfile's options parser, resulting into a wrong behavior. Best, Rafael Laboissière
Bug#1053314: Depends: python3-h5py-mpi without python3-h5py
Hello, On 10/8/23 17:22, Rafael Laboissière wrote: Ok, I tried to fix the building problem by including python3-h5py, alongside with python3-h5py-mpi, into Build-Depends, as suggested by Drew, but the xmds2 package FTBFS. Here is a way to reproduce the problem without building the package: $ dpkg -l python3-h5py\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-===---=== ii python3-h5py 3.9.0-3 all general-purpose Python interface to hdf5 ii python3-h5py-mpi 3.9.0-3 amd64 general-purpose Python interface to hdf5 (Python 3 MPI) un python3-h5py-serial (no description available) $ echo 'import h5py' | python3 Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/h5py/__init__.py", line 21, in from . import _debian_h5py_serial as _h5py ImportError: cannot import name '_debian_h5py_serial' from partially initialized module 'h5py' (most likely due to a circular import) (/usr/lib/python3/dist-packages/h5py/__init__.py) Is there a way to force h5py to import _debian_h5py_serial instead of _debian_h5py_mpi, via the generic h5py namespace? Drew would probably answer that question better but from taking a brief look, it seems to be on expected lines. This should work if you run it explicitly with mpi. $ mpirun -n 1 python3 -c "import h5py" && echo "true" true or with setting the MPI var manually. $ OMPI_COMM_WORLD_SIZE=1 python3 -c "import h5py" && echo "true" true If you want the _debian_h5py_serial interface then you need python3-h5py-serial and the B-D (and Depends) on h5py-mpi should be dropped which would mean this package does not need the -mpi package. Otherwise, a (unreliable) hack that you could do it that add a B-D on h5py *before* mpi and then -serial should also be installed (at least on my env). If the code really needs h5py-mpi, then it should be running the build/tests with mpi enabled (via openmpi). At least that's the impression I get from reading. https://sources.debian.org/src/h5py/3.9.0-3/debian/README.Debian/ This patch gets the package building for me with h5py-mpi+h5py, but not sure if it is the right thing to do -- please verify for yourself as package maintainer :) --- a/xpdeint/XSILFile.py +++ b/xpdeint/XSILFile.py @@ -31,6 +31,9 @@ numpy = None +# Set env var to use h5py-mpi +os.environ['OMPI_COMM_WORLD_SIZE'] = '1' + def require_h5py(): global h5py if not h5py:
Bug#1052508: marked as done (src:x2goserver: fails to migrate to testing for too long: uploader built arch:all)
Your message dated Sun, 08 Oct 2023 15:07:28 + with message-id and subject line Bug#1052508: fixed in x2goserver 4.1.0.6-1.1 has caused the Debian Bug report #1052508, regarding src:x2goserver: fails to migrate to testing for too long: uploader built arch:all 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.) -- 1052508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: x2goserver Version: 4.1.0.3-7 Severity: serious Control: close -1 4.1.0.6-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:x2goserver has been trying to migrate for 32 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=x2goserver OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: x2goserver Source-Version: 4.1.0.6-1.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of x2goserver, 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 1052...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated x2goserver package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Sep 2023 16:10:47 +0200 Source: x2goserver Architecture: source Version: 4.1.0.6-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Remote Maintainers Changed-By: Paul Gevers Closes: 1052508 Changes: x2goserver (4.1.0.6-1.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #1052508) Checksums-Sha1: 81a265a5ddc988c1211f399aa3ed5489677c95e6 2982 x2goserver_4.1.0.6-1.1.dsc 7d71b00dff6fec8af4416430f185ba2abe5e37cf 43816 x2goserver_4.1.0.6-1.1.debian.tar.xz Checksums-Sha256: e4bb8e4617213c8844be1b6c2a6f20cf2d38ab3ff2b41414ae100bd173e0e0d4 2982 x2goserver_4.1.0.6-1.1.dsc 28bb20a513beb96c588786191d865df3b9f56b410ac4343b2490b13c3913bce9 43816 x2goserver_4.1.0.6-1.1.debian.tar.xz Files: 53b02d7e01f6761de7ca262d97dc2480 2982 x11 optional x2goserver_4.1.0.6-1.1.dsc 1353573bf88caf712f0b9b594a84f707 43816 x11 optional x2goserver_4.1.0.6-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmUO8hoACgkQnFyZ6wW9 dQqb0Qf+JGQ/v6tJ3FdFSwUr2FNfLs4Iz1EwGkyfZkDnhl1qVjJBN4NfNwggosyD DOC4+hd+nbI7mRtWTNc4ZntIXG59bS2IFmTiNiokrNebLOjpV1chvu16oH0qU/zh e1BmaZW4SSZx9BVxunt/AjrSDuxd0J1xEUYoOMovL5l7IfL/ZEdF8sIXwvnSChiH xED0Tk0KsXlkdC5sWj16+Re7dqG8aYAS6a34RNzUbcCv3ykeCzc5r+mJew8v1IEa OCfAe0lZSMrLIkZp6PwezkVvYkjoDTkxsCM2sh9+iTeJeLqHN/td465JgHHuJ5dJ
Bug#1050232: marked as done (pyregion: binary-any FTBFS with recent jdupes)
Your message dated Sun, 08 Oct 2023 14:47:14 + with message-id and subject line Bug#1050232: fixed in pyregion 2.2.0-1 has caused the Debian Bug report #1050232, regarding pyregion: binary-any FTBFS with recent jdupes 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.) -- 1050232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyregion Version: 2.1.1-2 Severity: serious Tags: ftbfs Justification: fails to build from source Dear maintainer, pyregion fails to build from source when building only binary-any and not binary-all. From my build log on amd64: | make[1]: Leaving directory '/<>' |dh_installdocs -a -O--buildsystem=pybuild |dh_sphinxdoc -a -O--buildsystem=pybuild | dh_sphinxdoc: warning: Sphinx documentation not found |dh_installchangelogs -a -O--buildsystem=pybuild |dh_python3 -a -O--buildsystem=pybuild |dh_installsystemduser -a -O--buildsystem=pybuild |dh_perl -a -O--buildsystem=pybuild |debian/rules override_dh_link | make[1]: Entering directory '/<>' | py3versions: no X-Python3-Version in control file, using supported versions | jdupes -rl debian/python-pyregion-doc/usr | | could not stat dir debian/python-pyregion-doc/usr | No duplicates found. | make[1]: *** [debian/rules:48: override_dh_link] Error 1 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:13: binary-arch] Error 2 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 A full build log on riscv64 is also available: https://buildd.debian.org/status/fetch.php?pkg=pyregion=riscv64=2.1.1-2=1692574703=0 The return value of jdupes changed after bookworm to no longer return success when the given paths do not exist, which causes this failure in binary-any builds. A possible patch is: --- pyregion-2.1.1/debian/rules +++ pyregion-2.1.1/debian/rules @@ -44,6 +44,5 @@ dh_auto_build PYTHONPATH=. sphinx-build $(SPHINXOPTS) -N -bhtml docs/ -d debian/doctrees build/html -override_dh_link: +execute_after_dh_link-indep: jdupes -rl debian/python-pyregion-doc/usr - dh_link Regards Aurelien --- End Message --- --- Begin Message --- Source: pyregion Source-Version: 2.2.0-1 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of pyregion, 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 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated pyregion 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: Sun, 08 Oct 2023 15:08:52 +0200 Source: pyregion Architecture: source Version: 2.2.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Closes: 1050232 Changes: pyregion (2.2.0-1) unstable; urgency=medium . * Team upload * New upstream version 2.2.0 * Make patches conform to gbp pq * Remove all patches: applied upstream * Push Standards-Version to 4.6.2. No changes needed * Rename MIT license shortname to standard name Expat * Fix binary-any FTBFS (Closes: #1050232) * Add new py3-setuptools-scm and py3-sphinx-rtd-theme build dependencies * Add gitlab-ci.yml * Update CI test call Checksums-Sha1: 410f3a0a1d59fc1b3a5fbba474cd5099799109b0 2313 pyregion_2.2.0-1.dsc 79e70db7744efb6f902be7fca09641a2b1155985 978105 pyregion_2.2.0.orig.tar.gz 447d7ef19aa9b456a875ae09068a1b016fc6d089 4464 pyregion_2.2.0-1.debian.tar.xz Checksums-Sha256: 78732bfe4557faae06fa1564877b72ad4c35d587a681ca0c526c915519559a7d 2313 pyregion_2.2.0-1.dsc 5cbdb8017c744d39e36d67ec530dbfafc7ae245aa512185b35645b87f259f850 978105 pyregion_2.2.0.orig.tar.gz 16a82dbf843cc8781fee95ec118387478ed35a80ee8984a0ec45f4076e6f72df 4464 pyregion_2.2.0-1.debian.tar.xz Files: 2c5da87c6cdb6c3571ee4ef0a7eaba87 2313 python optional pyregion_2.2.0-1.dsc 54f9c062409892a95cd4fee46a6105bb 978105 python optional pyregion_2.2.0.orig.tar.gz 2ad7936bdc78959a96d26b6e6800df24 4464 python optional pyregion_2.2.0-1.debian.tar.xz -BEGIN PGP SIGNATURE-
Bug#1053673: RM: libwnck -- RoQA; leaf library; depends on gtk2
Source: libwnck Severity: serious Version: 2.30.7-6 Please remove libwnck. It does not have any reverse dependencies anymore and depends on the obsolete gtk2. I am going to file a RM bug when this is autoremoved from testing.
Processed: please retain bug metadata
Processing control commands: > reassign -1 dhcpcd-base Bug #1053657 [src:dhcpcd5] dhcpcd-base has ineffective Replaces due to /usr-merge and looses files in upgrade Bug reassigned from package 'src:dhcpcd5' to 'dhcpcd-base'. Ignoring request to alter found versions of bug #1053657 to the same values previously set Ignoring request to alter fixed versions of bug #1053657 to the same values previously set > found -1 9.4.1-24~deb12u2 Bug #1053657 [dhcpcd-base] dhcpcd-base has ineffective Replaces due to /usr-merge and looses files in upgrade Marked as found in versions dhcpcd5/9.4.1-24~deb12u2. > severity -1 serious Bug #1053657 [dhcpcd-base] dhcpcd-base has ineffective Replaces due to /usr-merge and looses files in upgrade Severity set to 'serious' from 'normal' > tags -1 + bookworm Bug #1053657 [dhcpcd-base] dhcpcd-base has ineffective Replaces due to /usr-merge and looses files in upgrade Added tag(s) bookworm. -- 1053657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053672: Apple copyright notices in test .xlsx files
Source: openpyxl Version: 3.0.9-2 Severity: serious licensecheck -r --copyright . on openpyxl finds these: ./openpyxl/formatting/tests/data/conditional-formatting.xlsx: UNKNOWN [Copyright: 2007 Apple Inc.] ./openpyxl/reader/tests/data/complex-styles.xlsx: UNKNOWN [Copyright: 2007 Apple Inc.] If opened in 'less' these files do contain the text "Copyright 2007 Apple Inc., all rights reserved.", marked as 'etext'. However, if opened in LibreOffice, no _obvious_ command displays this text. File > Properties instead displays creation and modification dates/authors that match the openpyxl upstream commit dates/authors (2012-4), which suggests that these are *not* straightforward copies of Apple-owned example files. Their actual contents are mostly formatting, i.e. they look like something created specifically to be a test case for reading formatting, or possibly a documentation example for formatting but the above makes that less likely, not something copied from real-world use. Given this, why is that copyright notice there, and what does it imply that we should do? (E.g. does Apple Numbers automatically copy Apple-owned items (e.g. fonts) into files it creates? If so, is there a way to remove these items to get a Free file?)
Processed: Re: RM: gtimer -- RoQA; low popcon; depends on gtk2
Processing control commands: > reassign -1 ftp.debian.org Bug #1051070 [src:gtimer] RM: gtimer -- RoQA; low popcon; depends on gtk2 Bug reassigned from package 'src:gtimer' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #1051070 to the same values previously set Ignoring request to alter fixed versions of bug #1051070 to the same values previously set > severity -1 normal Bug #1051070 [ftp.debian.org] RM: gtimer -- RoQA; low popcon; depends on gtk2 Severity set to 'normal' from 'serious' -- 1051070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051070: RM: gtimer -- RoQA; low popcon; depends on gtk2
Control: reassign -1 ftp.debian.org Control: severity -1 normal Please remove gtimer, which does not seem to be used a lot and is unmaintained upstream.
Bug#1050359: RM: gpr -- RoQA; dead upstream; depends on gtk2
Control: reassign -1 ftp.debian.org Control: severity -1 normal Please remove gpr. It is dead upstream. The Debian version is essentially a fork that is also not updated since 2011.
Processed: Re: RM: gpr -- RoQA; dead upstream; depends on gtk2
Processing control commands: > reassign -1 ftp.debian.org Bug #1050359 [src:gpr] RM: gpr -- RoQA; dead upstream; depends on gtk2 Bug reassigned from package 'src:gpr' to 'ftp.debian.org'. No longer marked as found in versions gpr/0.15deb-2. Ignoring request to alter fixed versions of bug #1050359 to the same values previously set > severity -1 normal Bug #1050359 [ftp.debian.org] RM: gpr -- RoQA; dead upstream; depends on gtk2 Severity set to 'normal' from 'serious' -- 1050359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038687: radicale's autopkg tests fail with Python 3.11.4
Control: forwarded -1 https://github.com/Kozea/Radicale/issues/1336 I told upstream about this. I suspect the problem is in the server, not the tests. -- Happy hacking Petter Reinholdtsen
Processed: Re: radicale's autopkg tests fail with Python 3.11.4
Processing control commands: > forwarded -1 https://github.com/Kozea/Radicale/issues/1336 Bug #1038687 [src:radicale] radicale's autopkg tests fail with Python 3.11.4 Set Bug forwarded-to-address to 'https://github.com/Kozea/Radicale/issues/1336'. -- 1038687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053314: Depends: python3-h5py-mpi without python3-h5py
Ok, I tried to fix the building problem by including python3-h5py, alongside with python3-h5py-mpi, into Build-Depends, as suggested by Drew, but the xmds2 package FTBFS. Here is a way to reproduce the problem without building the package: $ dpkg -l python3-h5py\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=== ii python3-h5py3.9.0-3 all general-purpose Python interface to hdf5 ii python3-h5py-mpi3.9.0-3 amd64general-purpose Python interface to hdf5 (Python 3 MPI) un python3-h5py-serial (no description available) $ echo 'import h5py' | python3 Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/h5py/__init__.py", line 21, in from . import _debian_h5py_serial as _h5py ImportError: cannot import name '_debian_h5py_serial' from partially initialized module 'h5py' (most likely due to a circular import) (/usr/lib/python3/dist-packages/h5py/__init__.py) Is there a way to force h5py to import _debian_h5py_serial instead of _debian_h5py_mpi, via the generic h5py namespace? Best, Rafael * Rafael Laboissière [2023-10-08 10:27]: * Nilesh Patra [2023-10-04 02:24]: On Sun, 01 Oct 2023 15:25:43 +0200 Drew Parsons wrote: Package: xmds2 Version: 3.1.0+dfsg2-4 Severity: serious Justification: debci xmds2 Depends: python3-h5py-mpi without depending on python3-h5py python3-h5py-mpi only provides the h5py._debian_h5py_mpi namespace, not h5py. Hence tests using h5py without specifying _debian_h5py_mpi fail. This is the case with h5py 3.9.0. (Marking Severity: serious due to debci failure) python3-h5py provides the h5py namespace, so if xmds2 strictly needs the mpi build, but accessing via the generic h5py namespace, then the Depends should specify both packages Depends: python3-h5py python3-h5py-mpi Note there seems to be an inconsistency in the xmds2 package configuration. It has MPI dependencies (python3-h5py-mpi, also mpi-default-dev, libfftw3-mpi-dev), but with respect to hdf5 it has Depends: libhdf5-serial-dev Should that instead be Depends: libhdf5-mpi-dev ? Seems you're right, taking a brief look at it. I've CC'ed Rafael to further comment/upload a fix. @Rafael, this seems to be the last blocker on h5py transition to testing, so prompt action would be really cool! Thanks to Drew for the bug report and Nilesh for the remainder. I was out of town these last days and could not react to your messages. I am taking a look at the issue right now. Best, Rafael
Processed: tagging 1053638, tagging 1053633
Processing commands for cont...@bugs.debian.org: > tags 1053638 + sid trixie Bug #1053638 [src:rust-pbr] rust-pbr: Remove from Debian? Added tag(s) sid and trixie. > tags 1053633 + sid trixie Bug #1053633 [src:haskell-yi-core] haskell-yi-core: FTBFS with haskell-unix-compat >= 0.7 Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053633 1053638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1053657 is normal
Processing commands for cont...@bugs.debian.org: > severity 1053657 normal Bug #1053657 [dhcpcd-base] dhcpcd-base has ineffective Replaces due to /usr-merge and looses files in upgrade Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1053657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052996: radicale FTBFS with the nocheck build profile
Status: tags -1 + patch [Helmut Grohne] > | ModuleNotFoundError: No module named 'defusedxml' I suspect this patch will fix the issue. diff --git a/debian/control b/debian/control index 0ae7774..e89bb74 100644 --- a/debian/control +++ b/debian/control @@ -17,7 +17,7 @@ Build-Depends: python3, python3-bcrypt , python3-dateutil (>= 2.7.3), - python3-defusedxml , + python3-defusedxml, python3-passlib , python3-pkg-resources, python3-pytest , -- Happy hacking Petter Reinholdtsen
Bug#1052834: marked as done (hugo: FTBFS: build-dependency not installable: golang-github-bep-logg-dev (>= 0.2.0))
Your message dated Sun, 08 Oct 2023 08:36:20 + with message-id and subject line Bug#1052834: fixed in hugo 0.114.1-2 has caused the Debian Bug report #1052834, regarding hugo: FTBFS: build-dependency not installable: golang-github-bep-logg-dev (>= 0.2.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.) -- 1052834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hugo Version: 0.114.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: asciidoctor, debhelper (>= 13.4), debhelper-compat (= > 13), dh-sequence-bash-completion, dh-sequence-golang, golang-any (>= > 2:1.19~), golang-github-alecthomas-chroma-v2-dev (>= 2.7.0), > golang-github-armon-go-radix-dev, golang-github-aws-aws-sdk-go-dev (>= > 1.43.5), golang-github-bep-clock-dev (>= 0.3.0), > golang-github-bep-debounce-dev (>= 1.2.0+really1.2.0), > golang-github-bep-gitmap-dev (>= 1.1.2), golang-github-bep-goat-dev (>= > 0.5.0), golang-github-bep-godartsass-dev (>= 1.2.0), > golang-github-bep-godartsass-v2-dev (>= 2.0.0), > golang-github-bep-golibsass-dev (>= 1.1.1), golang-github-bep-gowebp-dev (>= > 0.2.0), golang-github-bep-helpers-dev (>= 0.4.0), > golang-github-bep-lazycache-dev (>= 0.2.0), golang-github-bep-logg-dev (>= > 0.2.0), golang-github-bep-mclib-dev (>= 1.20400.20402), > golang-github-bep-overlayfs-dev (>= 0.6.0), golang-github-bep-simplecobra-dev > (>= 0.3.2), golang-github-bep-tmc-dev (>= 0.5.1), > golang-github-burntsushi-locker-dev, golang-github-clbanning-mxj-dev (>= > 2.5.7), golang-github-cli-safeexec-dev (>= 1.0.1), > golang-github-disintegration-gift-dev (>= 1.2.1), > golang-github-dustin-go-humanize-dev (>= 1.0.1), > golang-github-evanw-esbuild-dev (>= 0.18.5), golang-github-fatih-color-dev > (>= 1.15.0), golang-github-fortytw2-leaktest-dev, > golang-github-frankban-quicktest-dev (>= 1.14.5), > golang-github-fsnotify-fsnotify-dev (>= 1.6.0), > golang-github-getkin-kin-openapi-dev (>= 0.118.0), > golang-github-ghodss-yaml-dev, golang-github-go-playground-locales-dev (>= > 0.14.0), golang-github-gobuffalo-flect-dev (>= 1.0.2), > golang-github-gobwas-glob-dev, golang-github-google-go-cmp-dev (>= 0.5.9), > golang-github-gorilla-websocket-dev (>= 1.5.0), > golang-github-hairyhenderson-go-codeowners-dev (>= 0.3.0), > golang-github-jdkato-prose-dev (>= 1.2.1), > golang-github-kylelemons-godebug-dev (>= 1.1.0), > golang-github-kyokomi-emoji-dev (>= 2.2.12), > golang-github-marekm4-color-extractor-dev (>= 1.2.0), > golang-github-mattn-go-isatty-dev (>= 0.0.19), > golang-github-mitchellh-hashstructure-dev (>= 1.1.0), > golang-github-mitchellh-mapstructure-dev (>= 1.5.0), > golang-github-muesli-smartcrop-dev (>= 0.3.0), > golang-github-niklasfasching-go-org-dev (>= 1.6.6), > golang-github-olekukonko-tablewriter-dev (>= 0.0.5), > golang-github-pelletier-go-toml.v2-dev (>= 2.0.8), > golang-github-puerkitobio-purell-dev (>= 1.1.1), > golang-github-rogpeppe-go-internal-dev (>= 1.10.0+git20230508.a4f6fab), > golang-github-rwcarlsen-goexif-dev (>= 0.0~git20190401.9e8deec), > golang-github-sanity-io-litter-dev (>= 1.5.5), golang-github-spf13-afero-dev > (>= 1.9.5), golang-github-spf13-cast-dev (>= 1.5.1), > golang-github-spf13-cobra-dev (>= 1.7.0), golang-github-spf13-fsync-dev (>= > 0.9.0), golang-github-spf13-pflag-dev (>= 1.0.5), > golang-github-tdewolff-minify-dev (>= 2.12.7), > golang-github-tdewolff-parse-dev (>= 2.6.6), golang-github-yuin-goldmark-dev > (>= 1.5.4), golang-go.uber-atomic-dev (>= 1.11.0), golang-gocloud-dev (>= > 0.23.0), golang-golang-x-exp-dev (>= 0.0~git20221028.83b7d23-2~), > golang-golang-x-image-dev (>= 0.8.0), golang-golang-x-net-dev (>= 1:0.11.0), > golang-golang-x-sync-dev (>= 0.3.0), golang-golang-x-text-dev (>= 0.10.0), > golang-golang-x-tools-dev (>= 0.9.1), golang-google-api-dev (>= 0.61.0), > golang-gopkg-yaml.v2-dev (>= 2.4.0), golang-uber-automaxprocs-dev (>= 1.5.2), > libsass-dev (>= 3.6.5), libwebp-dev (>= 1.2.4), python3-docutils, tzdata, > build-essential,
Bug#1053314: Depends: python3-h5py-mpi without python3-h5py
* Nilesh Patra [2023-10-04 02:24]: On Sun, 01 Oct 2023 15:25:43 +0200 Drew Parsons wrote: Package: xmds2 Version: 3.1.0+dfsg2-4 Severity: serious Justification: debci xmds2 Depends: python3-h5py-mpi without depending on python3-h5py python3-h5py-mpi only provides the h5py._debian_h5py_mpi namespace, not h5py. Hence tests using h5py without specifying _debian_h5py_mpi fail. This is the case with h5py 3.9.0. (Marking Severity: serious due to debci failure) python3-h5py provides the h5py namespace, so if xmds2 strictly needs the mpi build, but accessing via the generic h5py namespace, then the Depends should specify both packages Depends: python3-h5py python3-h5py-mpi Note there seems to be an inconsistency in the xmds2 package configuration. It has MPI dependencies (python3-h5py-mpi, also mpi-default-dev, libfftw3-mpi-dev), but with respect to hdf5 it has Depends: libhdf5-serial-dev Should that instead be Depends: libhdf5-mpi-dev ? Seems you're right, taking a brief look at it. I've CC'ed Rafael to further comment/upload a fix. @Rafael, this seems to be the last blocker on h5py transition to testing, so prompt action would be really cool! Thanks to Drew for the bug report and Nilesh for the remainder. I was out of town these last days and could not react to your messages. I am taking a look at the issue right now. Best, Rafael
Bug#1052834: marked as pending in hugo
Control: tag -1 pending Hello, Bug #1052834 in hugo reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/hugo/-/commit/e8bd0017833ca4a7ffb4d70adb628af917dee7e3 Add temporary local copy of github.com/bep/logg v0.2.0 while golang-github-bep-logg waits in the NEW queue. Closes: #1052834 (this message was generated automatically) -- Greetings https://bugs.debian.org/1052834
Processed: Bug#1052834 marked as pending in hugo
Processing control commands: > tag -1 pending Bug #1052834 [src:hugo] hugo: FTBFS: build-dependency not installable: golang-github-bep-logg-dev (>= 0.2.0) Added tag(s) pending. -- 1052834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041242: libheif1: 1.16.2-1+b1 breaks displaying any pictures
Hey Jeremy On Sat, 2023-09-30 at 05:39 -0400, Jeremy Bícha wrote: > I pushed my change to the wip/10421242 branch of > https://salsa.debian.org/multimedia-team/libheif if someone wants to > do a test build. I finally came around testing this. 1) building (with all build-deps installed) generally fails for me: ... -- Installing: /home/calestyo/ggg/libheif-1.16.2/debian/tmp/usr/lib/x86_64-linux-gnu/libheif.so.1.16.2 -- Installing: /home/calestyo/ggg/libheif-1.16.2/debian/tmp/usr/lib/x86_64-linux-gnu/libheif.so.1 -- Installing: /home/calestyo/ggg/libheif-1.16.2/debian/tmp/usr/lib/x86_64-linux-gnu/libheif.so -- Installing: /home/calestyo/ggg/libheif-1.16.2/debian/tmp/usr/include/x86_64-linux-gnu/libheif/heif.h -- Installing: /home/calestyo/ggg/libheif-1.16.2/debian/tmp/usr/include/x86_64-linux-gnu/libheif/heif_cxx.h -- Installing: /home/calestyo/ggg/libheif-1.16.2/debian/tmp/usr/include/x86_64-linux-gnu/libheif/heif_plugin.h -- Installing: /home/calestyo/ggg/libheif-1.16.2/debian/tmp/usr/include/x86_64-linux-gnu/libheif/heif_version.h -- Installing: /home/calestyo/ggg/libheif-1.16.2/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/libheif/libheif-config.cmake -- Installing: /home/calestyo/ggg/libheif-1.16.2/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/libheif/libheif-config-none.cmake -- Installing: /home/calestyo/ggg/libheif-1.16.2/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/libheif/libheif-config-version.cmake -- Installing: /home/calestyo/ggg/libheif-1.16.2/debian/tmp/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-heif.so -- Set runtime path of "/home/calestyo/ggg/libheif-1.16.2/debian/tmp/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-heif.so" to "" -- Installing: /home/calestyo/ggg/libheif-1.16.2/debian/tmp/usr/share/thumbnailers/heif.thumbnailer make[1]: Leaving directory '/home/calestyo/ggg/libheif-1.16.2/obj-x86_64-linux-gnu' dh_install dh_install: warning: Cannot find (any matches for) "usr/lib/*/libheif/plugins/libheif-rav1e.so" (tried in ., debian/tmp) dh_install: warning: libheif-plugin-rav1e missing files: usr/lib/*/libheif/plugins/libheif-rav1e.so dh_install: error: missing files, aborting make: *** [debian/rules:19: binary] Error 255 I first tried disabling the plugin in debian/rules, but that didn't help, had to manually remove the file from debian/libheif-plugin- rav1e.install ... so I guess that particular plugin will be broken ^^ 2) With the current version in sid (1.16.2-3), displaying heif files worked for me with eog, but not geequie. 3) The manual bild with the patch from wip/10421242 also worked with eog, but also failed with geeqie. I've opened a new issue upstream: https://github.com/strukturag/libheif/issues/974 Thanks, Chris.
Bug#1053491: marked as done (src:libcbor: fails to migrate to testing for too long: uploader built arch:all)
Your message dated Sun, 08 Oct 2023 07:19:17 + with message-id and subject line Bug#1053491: fixed in libcbor 0.10.2-1.1 has caused the Debian Bug report #1053491, regarding src:libcbor: fails to migrate to testing for too long: uploader built arch:all 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.) -- 1053491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcbor Version: 0.8.0-2 Severity: serious Control: close -1 0.10.2-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1052004 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:libcbor has been trying to migrate for 31 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd (bug 1052004). Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/3 (normally 15 in bugs like this, but because of bug 1052004), closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=libcbor OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: libcbor Source-Version: 0.10.2-1.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of libcbor, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated libcbor 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, 05 Oct 2023 08:47:27 +0200 Source: libcbor Architecture: source Version: 0.10.2-1.1 Distribution: unstable Urgency: medium Maintainer: Vincent Bernat Changed-By: Paul Gevers Closes: 1052004 1053491 Changes: libcbor (0.10.2-1.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #1052004, #1053491) Checksums-Sha1: 1e8652fe314fc3be5299cd20fb1cd259f2e25808 1761 libcbor_0.10.2-1.1.dsc 6dd4395298903e6ffd9ba276d832800c186b9577 4304 libcbor_0.10.2-1.1.debian.tar.xz Checksums-Sha256: 02961a5d969749a46e3d241478801b762b6e5472c7968ee848dd29dbfd87a126 1761 libcbor_0.10.2-1.1.dsc a666c4c1ef4e948c45d0b910c40ae898b29c259569ee6579f85295172b533374 4304 libcbor_0.10.2-1.1.debian.tar.xz Files: 244f0f5fba17ad967826328d40ea4be6 1761 libs optional libcbor_0.10.2-1.1.dsc 4f1ea951dc48d2685e94176334718723 4304 libs optional libcbor_0.10.2-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmUeXJUACgkQnFyZ6wW9 dQpsBwf9H83vsRs5IwnjNAqnTPY4kqkigXVVODvOxGCzBU3NFHPjmB/nC04E5TlS 4p4Zh3lCkfH/qR0z2vZufnJCJU6kdHKutchERrab+zsd6j+bM4tux/SwO/Z+B6Vb 1y/6sxrn7Gx3hfHQqkayNErDi6jxzPZQilyShQCElx8st8rs+s0uEK+NTSsB63Gq 3dYRgQ79f7JYRi1hnnkzEoIGoxa3DDq5eEveQplEeamPmUjLozUx97CHTzGZ156Y
Bug#1052004: marked as done (libcbor: requires source-only upload to transition)
Your message dated Sun, 08 Oct 2023 07:19:17 + with message-id and subject line Bug#1052004: fixed in libcbor 0.10.2-1.1 has caused the Debian Bug report #1052004, regarding libcbor: requires source-only upload to transition 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.) -- 1052004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libcbor Version: 0.10.2-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org https://qa.debian.org/excuses.php?package=libcbor Issues preventing migration: Not built on buildd: arch amd64 binaries uploaded by bernat Not built on buildd: arch all binaries uploaded by bernat, a new source-only upload is needed to allow migration Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: libcbor Source-Version: 0.10.2-1.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of libcbor, 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 1052...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated libcbor 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, 05 Oct 2023 08:47:27 +0200 Source: libcbor Architecture: source Version: 0.10.2-1.1 Distribution: unstable Urgency: medium Maintainer: Vincent Bernat Changed-By: Paul Gevers Closes: 1052004 1053491 Changes: libcbor (0.10.2-1.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #1052004, #1053491) Checksums-Sha1: 1e8652fe314fc3be5299cd20fb1cd259f2e25808 1761 libcbor_0.10.2-1.1.dsc 6dd4395298903e6ffd9ba276d832800c186b9577 4304 libcbor_0.10.2-1.1.debian.tar.xz Checksums-Sha256: 02961a5d969749a46e3d241478801b762b6e5472c7968ee848dd29dbfd87a126 1761 libcbor_0.10.2-1.1.dsc a666c4c1ef4e948c45d0b910c40ae898b29c259569ee6579f85295172b533374 4304 libcbor_0.10.2-1.1.debian.tar.xz Files: 244f0f5fba17ad967826328d40ea4be6 1761 libs optional libcbor_0.10.2-1.1.dsc 4f1ea951dc48d2685e94176334718723 4304 libs optional libcbor_0.10.2-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmUeXJUACgkQnFyZ6wW9 dQpsBwf9H83vsRs5IwnjNAqnTPY4kqkigXVVODvOxGCzBU3NFHPjmB/nC04E5TlS 4p4Zh3lCkfH/qR0z2vZufnJCJU6kdHKutchERrab+zsd6j+bM4tux/SwO/Z+B6Vb 1y/6sxrn7Gx3hfHQqkayNErDi6jxzPZQilyShQCElx8st8rs+s0uEK+NTSsB63Gq 3dYRgQ79f7JYRi1hnnkzEoIGoxa3DDq5eEveQplEeamPmUjLozUx97CHTzGZ156Y o4DT5nQHsNLq3wo5Za9Re72NzDUHqrlIi/i5NdNDPkHi6NEHGhD2nmKaKy0qnS1+ WaeK/pUwVl2mdMdAvCy1w7aLxPP+kQ== =0BOT -END PGP SIGNATURE End Message ---
Bug#1053657: dhcpcd-base has ineffective Replaces due to /usr-merge and looses files in upgrade
Package: dhcpcd-base Version: 9.4.1-24~deb12u2 Severity: serious Justification: file loss during upgrade X-Debbugs-Cc: debian-rele...@lists.debian.org User: helm...@debian.org Usertags: dep17p1 Unfortunately, the stable update of dhcpcd5 introduced a regression relevant to upgrades from bullseye. The bullseye dhcpcd5 package contained the files - /lib/dhcpcd/dhcpcd-hooks/01-test - /lib/dhcpcd/dhcpcd-hooks/20-resolv.conf - /lib/dhcpcd/dhcpcd-hooks/30-hostname - /lib/dhcpcd/dhcpcd-hooks/60-ntp-common.conf - /lib/dhcpcd/dhcpcd-hooks/62-chrony.conf - /lib/dhcpcd/dhcpcd-hooks/64-timesyncd.conf - /lib/dhcpcd/dhcpcd-hooks/68-openntpd.conf - /lib/dhcpcd/dhcpcd-run-hooks and these have been moved into dhcpcd-base in that particular stable update. The update correctly declares Replaces for this. Unfortunately, it also moves these files from /lib to /usr/lib. Therefore, the declared Replaces have no effect (regarding these files) and as a consequence, an upgrade may delete the affected files. Fortunately, a very simple upgrade from bullseye to bookworm with only dhcpcd5 installed unpacks the new dhcpcd5 package before unpacking dhcpcd-base and therefore the issue is not trivially reproducible and probably does not affect the majority of users. We cannot rule out other upgrade scenarios though and we can also construct a breaking scenario using mmdebstrap. mmdebstrap bullseye /dev/null --variant=apt --include dhcpcd5 --chrooted-customize-hook='sed -i -e s/bullseye/bookworm/ /etc/apt/sources.list && apt update && apt-get install -y libc6 usrmerge && apt-get download dhcpcd-base && dpkg --auto-deconfigure --unpack ./dhcpcd-base_*.deb && dpkg -r dhcpcd5 && ls /usr/lib/dhcpcd/dhcpcd-hooks' If you run this, it ends with: | Selecting previously unselected package dhcpcd-base. | dpkg: considering deconfiguration of dhcpcd5, which would be broken by installation of dhcpcd-base ... | dpkg: yes, will deconfigure dhcpcd5 (broken by dhcpcd-base) | (Reading database ... 6731 files and directories currently installed.) | Preparing to unpack .../dhcpcd-base_9.4.1-24~deb12u2_amd64.deb ... | De-configuring dhcpcd5 (7.1.0-2+b1) ... | Unpacking dhcpcd-base (9.4.1-24~deb12u2) ... | Replacing files in old package dhcpcd5 (7.1.0-2+b1) ... | (Reading database ... 6752 files and directories currently installed.) | Removing dhcpcd5 (7.1.0-2+b1) ... | ls: cannot access '/usr/lib/dhcpcd/dhcpcd-hooks': No such file or directory This kind of problem has been categorized in the https://subdivi.de/~helmut/dep17.html as P1 and the recommended mitigation M7 is changing Breaks+Replaces to Conflicts. I think this mitigation is fully applicable here, because apt will by default unpack the updated dhcpcd5 package first and then the conflict is resolved. The additional constraint is satisfied by the default solution of apt. I am not sure why dhcpcd-base has moved these files from / to /usr in violation of the file move moratorium that was meant to prevent precisely this kind of bug. In any case, please do *not* move them back as that could cause further trouble. I'm sorry for not having spotted this before the point release and will now monitor stable p-u suites for similar problems to raise this earlier. Can I assume that a package sits in p-u for at least three days before migrating to a stable release? Helmut
