Processed: tagging 1056822
Processing commands for cont...@bugs.debian.org: > tags 1056822 + ftbfs Bug #1056822 [src:mpi4py-fft] mpi4py-fft: ftbfs with cython 3.0.x Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1056807
Processing commands for cont...@bugs.debian.org: > tags 1056807 + ftbfs Bug #1056807 [src:h5py] h5py: ftbfs with cython 3.0.x Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059257: marked as done (gemmi: CVE-2023-49287)
Your message dated Sun, 31 Dec 2023 09:25:46 +0200 with message-id <201db86d-a721-6e8e-4690-9f3f656d7...@debian.org> and subject line 1059257: done has caused the Debian Bug report #1059257, regarding gemmi: CVE-2023-49287 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.) -- 1059257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gemmi X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for gemmi. CVE-2023-49287[0]: | TinyDir is a lightweight C directory and file reader. Buffer | overflows in the `tinydir_file_open()` function. This vulnerability | has been patched in version 1.2.6. https://github.com/cxong/tinydir/security/advisories/GHSA-jf5r-wgf4-qhxf https://github.com/cxong/tinydir/commit/8124807260735a837226fa151493536591f6715d https://github.com/hnsecurity/vulns/blob/main/HNS-2023-04-tinydir.txt gemmi embeds a copy of tinydir, if it's not used to open files from potentially untrusted paths, feel free to downgrade. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-49287 https://www.cve.org/CVERecord?id=CVE-2023-49287 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Version: 0.6.4+ds-1 Hello, The upstream has confirmed that the issue is already fixed in gemmi/0.6.4+ds-1 which has tinydir/1.2.6. Andrius--- End Message ---
Bug#1057564: marked as done (python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS)
Your message dated Sun, 31 Dec 2023 06:34:30 +
with message-id
and subject line Bug#1057564: fixed in python-dbusmock 0.30.2-1
has caused the Debian Bug report #1057564,
regarding python3-dbusmock: inconsistent signature for PairDevice causes
gnome-bluetooth3 FTBFS
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.)
--
1057564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnome-bluetooth3
Version: 42.7-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
dh_update_autotools_config
dh_autoreconf
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
-Dgtk_doc=true \
-Dintrospection=true
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8
meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1
-Dgtk_doc=true -Dintrospection=true
The Meson build system
Version: 1.3.0
Source dir: /<>
Build dir: /<>/obj-x86_64-linux-gnu
[... snipped ...]
OK
==
4/17
test: Tests.test_connect
start time: 16:32:54
duration: 30.04s
result: exit status 0
command: top_builddir=/<>/obj-x86_64-linux-gnu
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=248
top_srcdir=/<> LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/lib /usr/bin/python3
/<>/obj-x86_64-linux-gnu/../tests/integration-test.py Tests.test_connect
--- stdout ---
1701793974.786 AddAdapter "hci0" "my-computer"
1701793974.787 emit / org.freedesktop.DBus.ObjectManager.InterfacesAdded "/org/bluez/hci0" {"org.bluez.Adapter1": {"UUIDs": ["1200--1000-8000-00805f9b34fb", "1800--1000-8000-00805f9b34fb", "1801--1000-8000-00805f9b34fb",
"110e--1000-8000-00805f9b34fb", "110c--1000-8000-00805f9b34fb"], "Discoverable": False, "Discovering": False, "Pairable": True, "Powered": True, "Address": "00:01:02:03:04:05", "AddressType": "public",
"Alias": "my-computer", "Modalias": "usb:v1D6Bp0245d050A", "Name": "my-computer", "Class": 268, "DiscoverableTimeout": 180, "PairableTimeout": 0}}
1701793974.787 AddDevice "hci0" "11:22:33:44:55:66" "My Phone"
1701793974.788 emit / org.freedesktop.DBus.ObjectManager.InterfacesAdded "/org/bluez/hci0/dev_11_22_33_44_55_66" {"org.bluez.Device1": {"Address": "11:22:33:44:55:66", "AddressType": "public", "Name": "My Phone", "Icon": "", "Class": 0, "Appearance": 0, "UUIDs": [],
"Paired": False, "Connected": False, "Trusted": False, "Blocked": False, "WakeAllowed": False, "Alias": "My Phone", "Adapter": "/org/bluez/hci0", "LegacyPairing": False, "Modalias": "", "RSSI": -79, "TxPower": 0, "ManufacturerData": [],
"ServiceData": [], "ServicesResolved": False, "AdvertisingFlags": [], "AdvertisingData": []}}
1701793974.863 GetAll /org/freedesktop/UPower org.freedesktop.UPower
1701793974.863 GetManagedObjects
1701793974.864 EnumerateDevices
1701793974.864 Connect
1701793974.864 emit /org/bluez/hci0/dev_11_22_33_44_55_66
org.freedesktop.DBus.Properties.PropertiesChanged "org.bluez.Device1"
{"Connected": True} []
1701793974.865 Disconnect
1701793974.865 emit /org/bluez/hci0/dev_11_22_33_44_55_66
org.freedesktop.DBus.Properties.PropertiesChanged "org.bluez.Device1"
{"Connected": False} []
Running out-of-process test test_connect
--- stderr ---
.
--
Ran 1 test in 0.417s
OK
==
5/17
test: Tests.test_connectable_devices
start time: 16:33:24
duration: 30.05s
result: exit status 0
command: top_builddir=/<>/obj-x86_64-linux-gnu
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 top_srcdir=/<>
Processed: Bug#1058784 marked as pending in golang-github-evanw-esbuild
Processing control commands: > tag -1 pending Bug #1058784 [esbuild] esbuild: [armel] install @esbuild/arm Added tag(s) pending. -- 1058784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058784: marked as pending in golang-github-evanw-esbuild
Control: tag -1 pending Hello, Bug #1058784 in golang-github-evanw-esbuild 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/golang-github-evanw-esbuild/-/commit/2aae91da2e0583f4e5514e2766053177b91db206 Fix armel install Closes: #1058784 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058784
Bug#1058389: marked as done (python-yarg: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Sun, 31 Dec 2023 02:35:26 +
with message-id
and subject line Bug#1058389: fixed in python-yarg 0.1.9-3
has caused the Debian Bug report #1058389,
regarding python-yarg: 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.)
--
1058389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-yarg
Version: 0.1.9-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 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 '/<>'
> PYTHONPATH=/<>/src/ \
> http_proxy=http://127.0.0.1:9 \
> https_proxy=https://127.0.0.1:9 \
> python3 -m sphinx -N -bhtml docs/source debian/html
> Running Sphinx v7.2.6
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> writing output...
> building [html]: targets for 7 source files that are out of date
> updating environment: [new config] 7 added, 0 changed, 0 removed
> [2Kreading sources... [ 14%] api-rss
> [2Kreading sources... [ 29%] api-search
> [2Kreading sources... [ 43%] changelog
> [2Kreading sources... [ 57%] contributors
> [2Kreading sources... [ 71%] faq
> [2Kreading sources... [ 86%] index
> [2Kreading sources... [100%] intro
>
> /<>/docs/source/api-search.rst:4: WARNING: duplicate object
> description of yarg, other instance in api-rss, use :no-index: for one of them
> 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... [ 14%] api-rss
> [2Kwriting output... [ 29%] api-search
> [2Kwriting output... [ 43%] changelog
> [2Kwriting output... [ 57%] contributors
> [2Kwriting output... [ 71%] faq
> [2Kwriting output... [ 86%] index
> [2Kwriting output... [100%] intro
>
> generating indices... genindex py-modindex done
> [2Khighlighting module code... [ 20%] yarg.client
> [2Khighlighting module code... [ 40%] yarg.exceptions
> [2Khighlighting module code... [ 60%] yarg.package
> [2Khighlighting module code... [ 80%] yarg.parse
> [2Khighlighting module code... [100%] yarg.release
>
> 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 debian/html.
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12_yarg/build;
> python3.12 -m pytest -v /<>/tests/ -p no:warnings
> = test session starts
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0 --
> /usr/bin/python3.12
> cachedir: .pytest_cache
> rootdir: /<>
> collecting ... collected 58 items
>
> ../../../tests/test_client.py::TestClient::test_end_slash PASSED [
> 1%]
> ../../../tests/test_client.py::TestClient::test_get PASSED [
> 3%]
> ../../../tests/test_exceptions.py::TestHTTPErrorWithReason::test_repr PASSED
> [ 5%]
> ../../../tests/test_exceptions.py::TestHTTPErrorWithReason::test_str PASSED [
> 6%]
> ../../../tests/test_exceptions.py::TestHTTPErrorNoReason::test_repr PASSED [
> 8%]
> ../../../tests/test_exceptions.py::TestHTTPErrorNoReason::test_str PASSED [
> 10%]
> ../../../tests/test_package.py::TestPackage::test_author FAILED [
> 12%]
> ../../../tests/test_package.py::TestPackage::test_bugtracker FAILED [
> 13%]
> ../../../tests/test_package.py::TestPackage::test_classifiers FAILED [
> 15%]
> ../../../tests/test_package.py::TestPackage::test_description FAILED [
> 17%]
> ../../../tests/test_package.py::TestPackage::test_docs FAILED[
> 18%]
> ../../../tests/test_package.py::TestPackage::test_downloads FAILED [
> 20%]
> ../../../tests/test_package.py::TestPackage::test_has_egg FAILED [
> 22%]
> ../../../tests/test_package.py::TestPackage::test_has_source FAILED [
> 24%]
> ../../../tests/test_package.py::TestPackage::test_has_wheel FAILED [
> 25%]
> ../../../tests/test_package.py::TestPackage::test_homepage FAILED[
> 27%]
> ../../../tests/test_package.py::TestPackage::test_latest_release_id FAILED [
> 29%]
>
Bug#1057231: marked as done (btrfs-progs: will FTBFS when udev.pc changes udevdir)
Your message dated Sun, 31 Dec 2023 02:34:19 + with message-id and subject line Bug#1057231: fixed in btrfs-progs 6.6.3-1 has caused the Debian Bug report #1057231, regarding btrfs-progs: will FTBFS when udev.pc changes udevdir 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.) -- 1057231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: btrfs-progs Version: 6.3.2-1 Severity: normal User: helm...@debian.org Usertags: dep17m2 Dear Maintainer, your package installs the files /lib/udev/rules.d/64-btrfs-dm.rules and /lib/udev/rules.d/64-btrfs-zoned.rules. For the ongoing UsrMerge effort [1], /lib needs to become "empty", IOW no package should install a file there. Instead, files should be installed into /usr/lib. Apparently these paths are hard-coded, either in the upstream build system or the packaging. Please change your package to install into /usr/lib/udev/rules.d at your earliest convenience. Per the wiki, it is useful to first upload to experimental and wait a few days for the dumat tool to evaluate the change, and only then upload to unstable. At a later point during the trixie cycle, I expect this bug will become release-critical. Thanks for considering, Chris [1] https://wiki.debian.org/UsrMerge --- End Message --- --- Begin Message --- Source: btrfs-progs Source-Version: 6.6.3-1 Done: Adam Borowski We believe that the bug you reported is fixed in the latest version of btrfs-progs, 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 1057...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adam Borowski (supplier of updated btrfs-progs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 29 Dec 2023 19:03:32 +0100 Source: btrfs-progs Architecture: source Version: 6.6.3-1 Distribution: unstable Urgency: medium Maintainer: Adam Borowski Changed-By: Adam Borowski Closes: 1030950 1044007 1055372 1057231 Changes: btrfs-progs (6.6.3-1) unstable; urgency=medium . * New upstream release (closes: #1055372). * Add B-Dep on python3-sphinx-rtd-theme, required for building docs. * Fix failure to build twice in a row (closes: #1044007). * Query udevdir via pkg-config, fixing FTBFS (closes: #1057231). * Build with support for converting from reiserfs (closes: #1030950). * Temporarily move the VCS to sr.ht * Slightly improve description. * Standardize debian/rules somewhat. Checksums-Sha1: fcf81535f8251a698fbe5f474f2606f219c15330 2523 btrfs-progs_6.6.3-1.dsc 1da2d3c6370a865187afc9fc46d9514ae90781e0 2557216 btrfs-progs_6.6.3.orig.tar.xz 2271d220817ed3edc9f927ea87474082f86feea3 16972 btrfs-progs_6.6.3-1.debian.tar.xz d575dd983e164c7368cc1a85bb08c9367fe69238 11834 btrfs-progs_6.6.3-1_amd64.buildinfo Checksums-Sha256: 029216f0cad8cf13e2c76168d7b3fd176b3c3e5fc8b5b1e1258f6fe8ff1f9fed 2523 btrfs-progs_6.6.3-1.dsc f41ce53f6673ff551ee4a3fe7dc9601e5a0dde6b6d09177d1fab62718abc6d9a 2557216 btrfs-progs_6.6.3.orig.tar.xz add51f16e9102954d3b40938415e481715705ea60eddcd52d346855995cb53df 16972 btrfs-progs_6.6.3-1.debian.tar.xz 8a2a46c479c94c81d1802d50049a7e2d16ae69c28a3c0cc575aefc31052ebf74 11834 btrfs-progs_6.6.3-1_amd64.buildinfo Files: 665ef7337374f5a5d6ccfafc3c6a7758 2523 admin optional btrfs-progs_6.6.3-1.dsc a26465478fd2d009cc2fe9f035cc299d 2557216 admin optional btrfs-progs_6.6.3.orig.tar.xz b24156e1c6fedf140c135aae6e0510c3 16972 admin optional btrfs-progs_6.6.3-1.debian.tar.xz 8a9eae9c1d393d1c5dd614f1757b818c 11834 admin optional btrfs-progs_6.6.3-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmWQx+AACgkQWogwR199 EGFdRBAA1+bl2/BfliuBx08YrN1H/E+wNuhaNFjl2KFSY8hm6l+6FHCE3ubWORj0 cippOzk1Cr0oOHU65BW2l/SlqAggerH7RIY6+9j27G2tvMENe5svzqohznurgVFI Fh6Joy7PUjeEuftlVnVapcsJyEx5CVoS7+X9ZgMgpih+gOa0p7N70Kmn71JqOrUg HP4BTv08hn52HI3iOmExeFnf4Y3l5YOGAwyeAGQsoH406F9+O0oC1yd5+2tskFtK PUK4EPoT61zGg6bbWb6ZgVhsT8ENYYZdqox1n90wxopHTjIOzRdhT6PCMpYbpf5n wFmd/Maf7xPJf4D34sjkKAJyocJkPBsDyKrIoe9aYOGns0yuzpSXOgDAFZzaLPVG
Processed: Re: Bug#1057564: python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS
Processing control commands: > block 1058116 by 1057564 Bug #1058116 [gnome-bluetooth3] gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0 1058116 was blocked by: 1057564 1058116 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #1058116 to the same blocks previously set > tags 1058116 + patch pending Bug #1058116 [gnome-bluetooth3] gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0 Ignoring request to alter tags of bug #1058116 to the same tags previously set > tags 1057564 + patch Bug #1057564 [python3-dbusmock] python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS Ignoring request to alter tags of bug #1057564 to the same tags previously set -- 1057564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057564 1058116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1057564: python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS
Processing control commands: > block 1058116 by 1057564 Bug #1058116 [gnome-bluetooth3] gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0 1058116 was not blocked by any bugs. 1058116 was not blocking any bugs. Added blocking bug(s) of 1058116: 1057564 > tags 1058116 + patch pending Bug #1058116 [gnome-bluetooth3] gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0 Added tag(s) patch and pending. > tags 1057564 + patch Bug #1057564 [python3-dbusmock] python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS Added tag(s) patch. -- 1057564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057564 1058116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057564: python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS
Control: block 1058116 by 1057564
Control: tags 1058116 + patch pending
Control: tags 1057564 + patch
On Sat, 30 Dec 2023 at 21:18:37 +, Simon McVittie wrote:
> Because you can't clone a merged bug, I'm unmerging the two equivalent
> FTBFS bug reports, and arbitrarily choosing to use:
>
> - #1058116 to represent the gnome-bluetooth3 test failure with dbusmock
> 0.30.0-2, which is genuinely a gnome-bluetooth3 bug, for which I've
> proposed a fix in
> https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/merge_requests/175.
> The symptom is that multiple tests time out.
This fix for #1058116 is pending in gnome-team git, but cannot usefully
be uploaded until the other bug is fixed:
> - #1057564 to represent the gnome-bluetooth3 test failure with dbusmock
> 0.30.1-1, even after applying GNOME/gnome-bluetooth!175, which as far
> as I can see is a dbusmock regression, reported as
> https://github.com/martinpitt/python-dbusmock/issues/193
> (I haven't tested a patch for this, I hope it's as simple as removing
> the obsolete 3rd argument in one call to PairDevice()).
That is indeed sufficient. Please see
https://github.com/martinpitt/python-dbusmock/pull/194 or the
attached patch.
smcv
>From e5679687939375265a0d080148cc129feade02e1 Mon Sep 17 00:00:00 2001
From: Simon McVittie
Date: Sat, 30 Dec 2023 23:58:08 +
Subject: [PATCH] bluez5: Fix invalid arguments to PairDevice
The third (device class) argument to PairDevice was removed in 0.30.1,
but this call to it was still passing a third parameter, resulting in
an error from dbus-python whenever Pair() was called. This caused a
unit test regression in gnome-bluetooth.
Fixes: 63264e18 "bluez5: Clean up static default properties, re-drop PairDevice class_ parameter"
Bug: https://github.com/martinpitt/python-dbusmock/issues/193
Bug-Debian: https://bugs.debian.org/1057564
Signed-off-by: Simon McVittie
---
dbusmock/templates/bluez5.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dbusmock/templates/bluez5.py b/dbusmock/templates/bluez5.py
index 4c590da..5603bd8 100644
--- a/dbusmock/templates/bluez5.py
+++ b/dbusmock/templates/bluez5.py
@@ -333,7 +333,7 @@ def Pair(device):
raise dbus.exceptions.DBusException("Device already paired", name="org.bluez.Error.AlreadyExists")
device_address = device.props[DEVICE_IFACE]["Address"]
adapter_device_name = Path(device.props[DEVICE_IFACE]["Adapter"]).name
-device.PairDevice(adapter_device_name, device_address, MOCK_PHONE_CLASS)
+device.PairDevice(adapter_device_name, device_address)
@dbus.service.method(DEVICE_IFACE, in_signature="", out_signature="")
--
2.43.0
Processed: unmerging 1057564, reassign 1057564 to python3-dbusmock ..., affects 1057564
Processing commands for cont...@bugs.debian.org: > unmerge 1057564 Bug #1057564 [gnome-bluetooth3] gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0 Ignoring request to unmerge a bug which is not merged with any others. > reassign 1057564 python3-dbusmock 0.30.1-1 Bug #1057564 [gnome-bluetooth3] gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0 Bug reassigned from package 'gnome-bluetooth3' to 'python3-dbusmock'. No longer marked as found in versions 42.7-1. Ignoring request to alter fixed versions of bug #1057564 to the same values previously set Bug #1057564 [python3-dbusmock] gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0 Marked as found in versions python-dbusmock/0.30.1-1. > retitle 1057564 python3-dbusmock: inconsistent signature for PairDevice > causes gnome-bluetooth3 FTBFS Bug #1057564 [python3-dbusmock] gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0 Changed Bug title to 'python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS' from 'gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0'. > forwarded 1057564 https://github.com/martinpitt/python-dbusmock/issues/193 Bug #1057564 [python3-dbusmock] python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS Changed Bug forwarded-to-address to 'https://github.com/martinpitt/python-dbusmock/issues/193' from 'https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/142'. > affects 1057564 + src:gnome-bluetooth3 Bug #1057564 [python3-dbusmock] python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS Ignoring request to set affects of bug 1057564 to the same value previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1057564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057564 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unmerging 1057564
Processing commands for cont...@bugs.debian.org: > unmerge 1057564 Bug #1057564 [gnome-bluetooth3] gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0 Bug #1058116 [gnome-bluetooth3] gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0 Disconnected #1057564 from all other report(s). > thanks Stopping processing here. Please contact me if you need assistance. -- 1057564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057564 1058116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056823: marked as done (nipy: ftbfs with cython 3.0.x)
Your message dated Sat, 30 Dec 2023 23:19:43 +
with message-id
and subject line Bug#1056823: fixed in nipy 0.6.0-1
has caused the Debian Bug report #1056823,
regarding nipy: ftbfs with cython 3.0.x
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.)
--
1056823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nipy
Version: 0.5.0-8
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: cython3
[This bug is targeted to the upcoming trixie release]
The package fails to build in a test rebuild on at least arm64 with
cython 3.0.5, but succeeds to build with cython 0.29.36. Please
update the package to build with cython 3.0.5 (available in experimental).
If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable). There is no replacement for cython3-dbg.
Build logs building with cython 3.0.5 can be found at
https://people.debian.org/~stefanor/cython3/cython-3.0.5/
See also https://lists.debian.org/debian-python/2023/11/msg00034.html
--- End Message ---
--- Begin Message ---
Source: nipy
Source-Version: 0.6.0-1
Done: Étienne Mollier
We believe that the bug you reported is fixed in the latest version of
nipy, 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.
Étienne Mollier (supplier of updated nipy 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: Sat, 30 Dec 2023 23:49:25 +0100
Source: nipy
Architecture: source
Version: 0.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Étienne Mollier
Closes: 1018423 1056693 1056823
Changes:
nipy (0.6.0-1) unstable; urgency=medium
.
[ Andreas Tille ]
* Add alternatives
liblapack-dev | liblapack.so,
libblas-dev | libblas.so,
.
[ Komolehin Israel Timilehin ]
* Added autopkgtest
.
[ Étienne Mollier ]
* New upstream version (Closes: #1056693, #1056823)
* Remove trailing whitespace in debian/changelog (routine-update)
* sphinx-ext patch: delete: applied upstream.
* numpy-fix.patch: delete: issues fixed upstream.
* numpy1.24.patch: delete: applied upstream.
* nibabel5.0.0.patch: delete: applied upstream.
* nibabel5.1.0.patch: delete: issue fixed upstream.
* standard-gifty-support.patch: delete: fixed upstream.
* remove-imagefileerror.patch: delete: fixed upstream.
* python3-shebang.patch: new: ensure scripts run python3.
* d/rules: remove execute_before_dh_auto_build.
The numpy automated patching and the recompilation of cython objects
have become unneed.
* d/control: build depends on python3-mesonpy.
* d/rules: remove all tests overrides.
With the new system, pybuild is now capturing the test suite properly.
* d/control: tests depend on python3-transforms3d.
* d/rules: remove unexport of LDFLAGS.
The underlying issue with distutils is not current anymore.
* d/control: remove dependency on nose. (Closes: #1018423)
* d/rules: reinforce documentation building process.
* d/{control,rules}: migrate to dh-sequence-python3.
* d/t/control: tests depend on pytest.
* d/copyright: delete reference to removed file.
* d/copyright: bump upstream copyright year.
Checksums-Sha1:
908f8f0fcfc58f57319ead453207398b6ca7c4dd 2624 nipy_0.6.0-1.dsc
93bf6086b84396cc3ca362da90b1d3728b8c1eb8 1650342 nipy_0.6.0.orig.tar.gz
eb78534a9da71f6a895e0676cfa3adab4719bcd1 11280 nipy_0.6.0-1.debian.tar.xz
Checksums-Sha256:
1e596638caf0c61a9517ef0a64d57ee3f4056cf5e865a8e733ed6e7bc7faa0be 2624
nipy_0.6.0-1.dsc
aba02a5d00c83667f41d398879283e8e5329a924cb51f0bb620f08507cc41efd 1650342
nipy_0.6.0.orig.tar.gz
0bd151e893edb53597b6e62b95f72d52f6ec72ce3a29c8d58610588ae25c0bbf 11280
nipy_0.6.0-1.debian.tar.xz
Files:
412558ebe296d22485d8bcf850ad390a 2624 python optional nipy_0.6.0-1.dsc
317b44e5378f8c0c349d21788060696a 1650342 python optional nipy_0.6.0.orig.tar.gz
2b191d3b274d5c5447a08c1e144d90ae 11280
Bug#1040988: fixed in picom 10.2-2
On Tue, 26 Dec 2023 16:19:12 + Debian FTP Masters wrote: * Fix infinite loop with GNOME (Closes: #1040988) Upstream also added: https://github.com/yshui/picom/commit/7366553be2b825495c5b1e09be09d0fabde4b9b4 Otherwise, picom won't start at the beginning of a session (no windows yet).
Bug#1058720: slurm-wlm: CVE-2023-49933 CVE-2023-49935 CVE-2023-49936 CVE-2023-49937 CVE-2023-49938
Dear Salvatore, I prepared an updated version of the slurm-wlm package for bookworm in response to CVE-2023-49933/49935/49936/49937/49938 The package can be found here: https://people.debian.org/~oliva/slurm-wlm-22.05.8-4+deb12u2 debdiff attached. A new package for sid in under preparation. Please let me know if I can be of any further help. I take this opportunity to wish you and to all the security team members a successful and prosperous new year. Best regards, -- Gennaro Oliva On Fri, Dec 15, 2023 at 06:21:05AM +0100, Salvatore Bonaccorso wrote: > Source: slurm-wlm > Version: 23.02.6-1 > Severity: grave > Tags: security upstream > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > > Hi Gennaro, > > The following vulnerabilities were published for slurm-wlm. > > CVE-2023-49933[0]: > | An issue was discovered in SchedMD Slurm 22.05.x, 23.02.x, and > | 23.11.x. There is Improper Enforcement of Message Integrity During > | Transmission in a Communication Channel. This allows attackers to > | modify RPC traffic in a way that bypasses message hash checks. The > | fixed versions are 22.05.11, 23.02.7, and 23.11.1. > > > CVE-2023-49935[1]: > | An issue was discovered in SchedMD Slurm 23.02.x and 23.11.x. There > | is Incorrect Access Control because of a slurmd Message Integrity > | Bypass. An attacker can reuse root-level authentication tokens > | during interaction with the slurmd process. This bypasses the RPC > | message hashes that protect against undesired MUNGE credential > | reuse. The fixed versions are 23.02.7 and 23.11.1. > > > CVE-2023-49936[2]: > | An issue was discovered in SchedMD Slurm 22.05.x, 23.02.x, and > | 23.11.x. A NULL pointer dereference leads to denial of service. The > | fixed versions are 22.05.11, 23.02.7, and 23.11.1. > > > CVE-2023-49937[3]: > | An issue was discovered in SchedMD Slurm 22.05.x, 23.02.x, and > | 23.11.x. Because of a double free, attackers can cause a denial of > | service or possibly execute arbitrary code. The fixed versions are > | 22.05.11, 23.02.7, and 23.11.1. > > > CVE-2023-49938[4]: > | An issue was discovered in SchedMD Slurm 22.05.x and 23.02.x. There > | is Incorrect Access Control: an attacker can modified their extended > | group list that is used with the sbcast subsystem, and open files > | with an unauthorized set of extended groups. The fixed versions are > | 22.05.11 and 23.02.7. > > > If you fix the vulnerabilities please also make sure to include the > CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. > > For further information see: > > [0] https://security-tracker.debian.org/tracker/CVE-2023-49933 > https://www.cve.org/CVERecord?id=CVE-2023-49933 > [1] https://security-tracker.debian.org/tracker/CVE-2023-49935 > https://www.cve.org/CVERecord?id=CVE-2023-49935 > [2] https://security-tracker.debian.org/tracker/CVE-2023-49936 > https://www.cve.org/CVERecord?id=CVE-2023-49936 > [3] https://security-tracker.debian.org/tracker/CVE-2023-49937 > https://www.cve.org/CVERecord?id=CVE-2023-49937 > [4] https://security-tracker.debian.org/tracker/CVE-2023-49938 > https://www.cve.org/CVERecord?id=CVE-2023-49938 > > Regards, > Salvatore > -- Gennaro Oliva diffstat for slurm-wlm-22.05.8 slurm-wlm-22.05.8 changelog|7 patches/CVE-2023-49933-49936-49937-49938 | 717 +++ patches/series |1 3 files changed, 725 insertions(+) diff -Nru slurm-wlm-22.05.8/debian/changelog slurm-wlm-22.05.8/debian/changelog --- slurm-wlm-22.05.8/debian/changelog 2023-10-12 20:09:40.0 +0200 +++ slurm-wlm-22.05.8/debian/changelog 2023-12-25 09:26:16.0 +0100 @@ -1,3 +1,10 @@ +slurm-wlm (22.05.8-4+deb12u2) bookworm-security; urgency=medium + + * Fix CVE-2023-49933, CVE-2023-49935, CVE-2023-49936, CVE-2023-49937, +CVE-2023-49938 (Closes: #1058720) + + -- Gennaro Oliva Mon, 25 Dec 2023 09:26:16 +0100 + slurm-wlm (22.05.8-4+deb12u1) bookworm-security; urgency=medium * Fix CVE-2023-41914 diff -Nru slurm-wlm-22.05.8/debian/patches/CVE-2023-49933-49936-49937-49938 slurm-wlm-22.05.8/debian/patches/CVE-2023-49933-49936-49937-49938 --- slurm-wlm-22.05.8/debian/patches/CVE-2023-49933-49936-49937-49938 1970-01-01 01:00:00.0 +0100 +++ slurm-wlm-22.05.8/debian/patches/CVE-2023-49933-49936-49937-49938 2023-12-25 09:26:16.0 +0100 @@ -0,0 +1,717 @@ +Description: Fix CVE-2023-49933/49935/49936/49937/49938 + Fix improper enforcement of message integrity during transmission in a + communication channel that allows attackers to modify RPC traffic in a way that + bypasses message hash checks. Fix a NULL pointer dereference that leads to denial of + service. Fix a double free that allows attackers to cause a denial of service or + possibly execute arbitrary code. Fix incorrect access control that can enable + an attacker to modify their extended group list that is used
Processed (with 1 error): Re: Bug#1057564: gnome-bluetooth3: FTBFS: failing tests
Processing control commands: > unmerge 1057564 1058116 Unknown command or malformed arguments to command. > reassign 1057564 python3-dbusmock 0.30.1-1 Bug #1057564 [src:gnome-bluetooth3,src:python-dbusmock] gnome-bluetooth3: FTBFS: failing tests Bug #1058116 [src:gnome-bluetooth3,src:python-dbusmock] gnome-bluetooth3: FTBFS: RuntimeError: Event loop is closed Bug reassigned from package 'src:gnome-bluetooth3,src:python-dbusmock' to 'python3-dbusmock'. Bug reassigned from package 'src:gnome-bluetooth3,src:python-dbusmock' to 'python3-dbusmock'. No longer marked as found in versions python-dbusmock/0.30.1-1, gnome-bluetooth3/42.7-1, and python-dbusmock/0.30.0-2. No longer marked as found in versions python-dbusmock/0.30.0-2, gnome-bluetooth3/42.7-1, and python-dbusmock/0.30.1-1. Ignoring request to alter fixed versions of bug #1057564 to the same values previously set Ignoring request to alter fixed versions of bug #1058116 to the same values previously set Bug #1057564 [python3-dbusmock] gnome-bluetooth3: FTBFS: failing tests Bug #1058116 [python3-dbusmock] gnome-bluetooth3: FTBFS: RuntimeError: Event loop is closed Marked as found in versions python-dbusmock/0.30.1-1. Marked as found in versions python-dbusmock/0.30.1-1. > retitle 1057564 python3-dbusmock: inconsistent signature for PairDevice > causes gnome-bluetooth3 FTBFS Bug #1057564 [python3-dbusmock] gnome-bluetooth3: FTBFS: failing tests Bug #1058116 [python3-dbusmock] gnome-bluetooth3: FTBFS: RuntimeError: Event loop is closed Changed Bug title to 'python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS' from 'gnome-bluetooth3: FTBFS: failing tests'. Changed Bug title to 'python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS' from 'gnome-bluetooth3: FTBFS: RuntimeError: Event loop is closed'. > forwarded 1057564 https://github.com/martinpitt/python-dbusmock/issues/193 Bug #1057564 [python3-dbusmock] python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS Bug #1058116 [python3-dbusmock] python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS Changed Bug forwarded-to-address to 'https://github.com/martinpitt/python-dbusmock/issues/193' from 'https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/142'. Changed Bug forwarded-to-address to 'https://github.com/martinpitt/python-dbusmock/issues/193' from 'https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/142'. > affects 1057564 + src:gnome-bluetooth3 Bug #1057564 [python3-dbusmock] python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS Bug #1058116 [python3-dbusmock] python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS Added indication that 1057564 affects src:gnome-bluetooth3 Added indication that 1058116 affects src:gnome-bluetooth3 > reassign 1058116 gnome-bluetooth3 42.7-1 Bug #1058116 [python3-dbusmock] python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS Bug #1057564 [python3-dbusmock] python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS Bug reassigned from package 'python3-dbusmock' to 'gnome-bluetooth3'. Bug reassigned from package 'python3-dbusmock' to 'gnome-bluetooth3'. No longer marked as found in versions python-dbusmock/0.30.1-1. No longer marked as found in versions python-dbusmock/0.30.1-1. Ignoring request to alter fixed versions of bug #1058116 to the same values previously set Ignoring request to alter fixed versions of bug #1057564 to the same values previously set Bug #1058116 [gnome-bluetooth3] python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS Bug #1057564 [gnome-bluetooth3] python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS There is no source info for the package 'gnome-bluetooth3' at version '42.7-1' with architecture '' Unable to make a source version for version '42.7-1' Marked as found in versions 42.7-1. Marked as found in versions 42.7-1. > retitle 1058116 gnome-bluetooth3: FTBFS: multiple tests time out with > dbusmock >= 0.30.0 Bug #1058116 [gnome-bluetooth3] python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS Bug #1057564 [gnome-bluetooth3] python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS Changed Bug title to 'gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0' from 'python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS'. Changed Bug title to 'gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0' from 'python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS'. > forwarded 1058116 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/142 Bug #1058116 [gnome-bluetooth3] gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >=
Bug#1057564: gnome-bluetooth3: FTBFS: failing tests
Control: unmerge 1057564 1058116 Control: reassign 1057564 python3-dbusmock 0.30.1-1 Control: retitle 1057564 python3-dbusmock: inconsistent signature for PairDevice causes gnome-bluetooth3 FTBFS Control: forwarded 1057564 https://github.com/martinpitt/python-dbusmock/issues/193 Control: affects 1057564 + src:gnome-bluetooth3 Control: reassign 1058116 gnome-bluetooth3 42.7-1 Control: retitle 1058116 gnome-bluetooth3: FTBFS: multiple tests time out with dbusmock >= 0.30.0 Control: forwarded 1058116 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/142 On Sat, 30 Dec 2023 at 01:53:56 +, Simon McVittie wrote: > On Tue, 05 Dec 2023 at 23:05:55 +0100, Santiago Vila wrote: > > During a rebuild of all packages in unstable, your package failed to build: > > This seems to be another casualty of recent updates to python-dbusmock. > With python-dbusmock downgraded to 0.29.1-2, all tests pass and > gnome-bluetooth3/42.7-1 builds successfully. With 0.30.0-2 (trixie) > or 0.30.1-1 (sid), several tests time out. I found a solution for the failure with dbusmock 0.30.0-2 and sent it upstream to https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/merge_requests/175, and it works with dbusmock 0.30.0-2, but unfortunately one test still fails with dbusmock 0.30.1-1. As far as I can see, that's genuinely a dbusmock bug. Because you can't clone a merged bug, I'm unmerging the two equivalent FTBFS bug reports, and arbitrarily choosing to use: - #1058116 to represent the gnome-bluetooth3 test failure with dbusmock 0.30.0-2, which is genuinely a gnome-bluetooth3 bug, for which I've proposed a fix in https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/merge_requests/175. The symptom is that multiple tests time out. - #1057564 to represent the gnome-bluetooth3 test failure with dbusmock 0.30.1-1, even after applying GNOME/gnome-bluetooth!175, which as far as I can see is a dbusmock regression, reported as https://github.com/martinpitt/python-dbusmock/issues/193 (I haven't tested a patch for this, I hope it's as simple as removing the obsolete 3rd argument in one call to PairDevice()). The symptom is that one test fails with "org.freedesktop.DBus.Error.InvalidArgs: Invalid arguments: Fewer items found in D-Bus signature than in Python arguments". smcv
Bug#1059661: marked as done (python-changelog: autopkgtest failure with Python 3.12)
Your message dated Sat, 30 Dec 2023 20:43:59 + with message-id and subject line Bug#1059661: fixed in python-changelog 0.6.1-2 has caused the Debian Bug report #1059661, regarding python-changelog: autopkgtest failure with Python 3.12 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.) -- 1059661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-changelog Version: 0.6.1-1 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.12 Hi Maintainer python-changelog's autopkgtests fail with Python 3.12 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/p/python-changelog/testing/amd64/ 50s autopkgtest [20:10:33]: test autodep8-python3: [--- 50s Testing with python3.12: 50s Traceback (most recent call last): 50s File "", line 1, in 50s File "/usr/lib/python3/dist-packages/changelog/__init__.py", line 3, in 50s from .sphinxext import setup # noqa 50s 50s File "/usr/lib/python3/dist-packages/changelog/sphinxext.py", line 7, in 50s from .docutils import ChangeDirective 50s File "/usr/lib/python3/dist-packages/changelog/docutils.py", line 2, in 50s from distutils.version import LooseVersion 50s ModuleNotFoundError: No module named 'distutils' 51s autopkgtest [20:10:34]: test autodep8-python3: ---] --- End Message --- --- Begin Message --- Source: python-changelog Source-Version: 0.6.1-2 Done: Dmitry Shachnev We believe that the bug you reported is fixed in the latest version of python-changelog, 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 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated python-changelog 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: Sat, 30 Dec 2023 23:02:06 +0300 Source: python-changelog Architecture: source Version: 0.6.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Dmitry Shachnev Closes: 1059661 Changes: python-changelog (0.6.1-2) unstable; urgency=medium . * Add run-time dependency on python3-setuptools (closes: #1059661). Checksums-Sha1: 244bcac4e7e59eab73b8ad8bd6cd6c1b9975f775 2172 python-changelog_0.6.1-2.dsc f6e61d48add98ab8c0442695bbfce9f0c009acfe 3328 python-changelog_0.6.1-2.debian.tar.xz 43fd8fe3ac25293eea18e9a0f5d3c58652d5945c 7693 python-changelog_0.6.1-2_source.buildinfo Checksums-Sha256: 3804fb082699e347a0e4553debebee33628a501920f2731fe0f402a7e476264c 2172 python-changelog_0.6.1-2.dsc f010b6b420edeaf282578b7650076c38aa1ed1d7bb720349e18da076d6cb4c03 3328 python-changelog_0.6.1-2.debian.tar.xz 86cbb831dd9efb90fcc23c2f362df2393f9f14e8220f66f43395f8086a02f0ad 7693 python-changelog_0.6.1-2_source.buildinfo Files: 59a873a28a805199b499b6545193482a 2172 python optional python-changelog_0.6.1-2.dsc 8a0c07d1d6be4cde95e1eb4fab7cb30d 3328 python optional python-changelog_0.6.1-2.debian.tar.xz f7d274c7f2d614c4a8a7485103d375f4 7693 python optional python-changelog_0.6.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEq2sdvrA0LydXHe1qsmYUtFL0RrYFAmWQekUTHG1pdHlhNTdA ZGViaWFuLm9yZwAKCRCyZhS0UvRGtlbJD/90aOBBDzAy2XPSGmSuBgVTcAco0+n3 5UgwFLpf7Q+hFcdRH9EE6+80BYUpb5IzdHckxGsCELAI3wJz5Q9XlqaiPXE4A6wH DHYoQWhhYXYg2vsCrjNrS9XcMiAVGXpYDnDaLBWMEa6VMFrBFa6Mui9ebv/A3TsQ rtJgHFO9jBXVDLfJrdXoeM5UJ5eDd64q/HyO9I2+5PeCpP7mrC6ZQSCG5MkXGs/B ZERAMuakQzQhKRn2lR4HF68E7aRbW+wMrZAk1Igb2kw849WUqW5logx/EjG5k8rs t7EczXSCV8vmK+WaiBMAv52Pas50Ie65iibnpvpzHZRYgkSWEoskzgVHiOsmqVp9 iUWL0CjbLpuAE4D19dG/WA9oDGcYxVQ982rhzIDy7EWZXf9HuoBNpMgigJ1d8NWY gutZv0fSz4azsrTuYpYHk6bUlKS3reEmUxxX6WMdk6d/ZIy9mf0jecL/yGlDuyjl IbVgL+Mes6G/VB95gmtj7qP8kc/zy4/buZ0yHxIOlAuzPLSu1tvwMAy7fQimou4J d0M72Px7rftDAWPGeF0e7ImMC7/GZ4g2tt2CscGXhltoc6DXkhFLRbV82m15NxWM aY8eVYeinOJqkDMpc2UJoNgtkQQztXAjkzvGi6ZkGwFcK+HvOPl13M97dNOjoVtA e6WZhJIoJ/pwXA== =zt6s -END PGP SIGNATURE End Message ---
Bug#1059661: marked as pending in python-changelog
Control: tag -1 pending Hello, Bug #1059661 in python-changelog reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-changelog/-/commit/56e0707bb663442e2d444ca9464b82ef21e4a4e1 Add run-time dependency on python3-setuptools. Closes: #1059661. (this message was generated automatically) -- Greetings https://bugs.debian.org/1059661
Processed: Bug#1059661 marked as pending in python-changelog
Processing control commands: > tag -1 pending Bug #1059661 [src:python-changelog] python-changelog: autopkgtest failure with Python 3.12 Added tag(s) pending. -- 1059661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056076: marked as done (laserboy: FTBFS: boost1.83 transition)
Your message dated Sat, 30 Dec 2023 19:37:29 +
with message-id
and subject line Bug#1056076: fixed in laserboy 2016.03.15-1.3
has caused the Debian Bug report #1056076,
regarding laserboy: FTBFS: boost1.83 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.)
--
1056076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: laserboy
Version: 2016.03.15-1.2
Severity: normal
User: gl...@debian.org
Usertags: boost183 ftbfs-boost183-transition
Hi,
we are preparing the transition of all libs on the new boost 1.83. During the
rebuild of packages against this library it was identified that probably your
package fails to build.
Relevant part (hopefully):
-
4: Error: ./src/objectvalidation.cpp 96: event.start() is not set
-
To reproduce this behavior, you can install -dev Boost packages from the
experimental repository, as shown in the following command:
apt install libboost-dev -t experimental
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/laserboy_2016.03.15-1.2_unstable_boost181.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-boost183-transition;users=gl...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-boost183-transition=gl...@debian.org=1=1=1=1#results
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 are unable to reproduce this, please provide a build log and diff it
so that we can identify any relevant changes that may have occurred in the
meantime.
--- End Message ---
--- Begin Message ---
Source: laserboy
Source-Version: 2016.03.15-1.3
Done: Boyuan Yang
We believe that the bug you reported is fixed in the latest version of
laserboy, 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.
Boyuan Yang (supplier of updated laserboy 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: Sat, 30 Dec 2023 13:49:49 -0500
Source: laserboy
Architecture: source
Version: 2016.03.15-1.3
Distribution: unstable
Urgency: medium
Maintainer: Richard Ulrich
Changed-By: Boyuan Yang
Closes: 1056076
Changes:
laserboy (2016.03.15-1.3) unstable; urgency=medium
.
* Non-maintainer upload.
* debian/watch: Fix upstream monitoring script.
* debian/patches/0005-Fix-boost1.83-build.patch: Fix boost1.83
build by explicitly using std::{i|o}fstream. (Closes: #1056076)
Checksums-Sha1:
d41c75f7543e34a40fdb2f622556314e2a835fdb 1896 laserboy_2016.03.15-1.3.dsc
c78bd852b6cbb64221e1e1606cb5d69ac8368bd1 3810094
laserboy_2016.03.15.orig.tar.gz
61a3b4b7bbd2abb90c612dda055fbc068f9834cf 5388
laserboy_2016.03.15-1.3.debian.tar.xz
871ae0c022bf627d78cb6fb32c40166241cd585f 12421
laserboy_2016.03.15-1.3_amd64.buildinfo
Checksums-Sha256:
43cc3fb0e84223542a0cdb455c3deaa265a7fe339e43cb61cc0b4f2df56dd37e 1896
laserboy_2016.03.15-1.3.dsc
064de6b21a7cf7ba710c75440cb5add76e2c11b1d067813f50546b3cc0455635 3810094
laserboy_2016.03.15.orig.tar.gz
240b296e7771f407873e04b1053254cb748835acb420d4323843ddbeb6872793 5388
laserboy_2016.03.15-1.3.debian.tar.xz
69a387accc66c50b93a26f8478fc157c51da5482fda01dab2c80148ed013c3a5 12421
laserboy_2016.03.15-1.3_amd64.buildinfo
Files:
274b3ecd5ec230fb394dd55300aa4e28 1896 graphics optional
laserboy_2016.03.15-1.3.dsc
c4446ee9b1ce310984334ba9baa9a5d2 3810094 graphics optional
laserboy_2016.03.15.orig.tar.gz
5b2cc772a173f2ccb9f99cfbc3b5b646 5388 graphics optional
laserboy_2016.03.15-1.3.debian.tar.xz
d804c950a67ab1e8485e7fe50f605419 12421 graphics optional
laserboy_2016.03.15-1.3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmWQau4ACgkQwpPntGGC
Ws4JWA//bLB114u04OXfxiFgTsj3FEnCZj9s2cy7RdfgBfENgowBbnijTa1Xf2PT
NxeW+ML5p8y5wdeQM5Uk3rRNLhAPL3v8lbjRlc+a5Jhrp1Y0P/Gpr26x2KVdIWaw
iQZr09x/iZoxbHMFxWdmkt1lqKSr5EPnilUxazBj/scXCMZiAhh8zjDn8j7nHSS4
Bug#1059138: marked as done (litecoin: FTBFS: error: ‘std::map, boost::filesystem::path>::mapped_type’ {aka ‘class boost::filesystem::path’} has no member named ‘BOOST
Your message dated Sat, 30 Dec 2023 18:35:21 +
with message-id
and subject line Bug#1059138: fixed in litecoin 0.21.2.2-1.2
has caused the Debian Bug report #1059138,
regarding litecoin: FTBFS: error: ‘std::map,
boost::filesystem::path>::mapped_type’ {aka ‘class boost::filesystem::path’}
has no member named ‘BOOST_FILESYSTEM_C_STR’
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.)
--
1059138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: litecoin
Version: 0.21.2.2-1.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=litecoin=amd64=0.21.2.2-1.1%2Bb1=1702920034=0
wallet/test/init_test_fixture.cpp: In constructor
‘InitWalletDirTestingSetup::InitWalletDirTestingSetup(const std::string&)’:
wallet/test/init_test_fixture.cpp:34:52: error:
‘std::map,
boost::filesystem::path>::mapped_type’ {aka ‘class boost::filesystem::path’}
has no member named ‘BOOST_FILESYSTEM_C_STR’
34 | std::ofstream
f(m_walletdir_path_cases["file"].BOOST_FILESYSTEM_C_STR);
|
^~
g++ -std=c++14 -DHAVE_CONFIG_H -I. -I../src/config-I.
-I./secp256k1-zkp/include -DBOOST_SP_USE_STD_ATOMIC -DBOOST_AC_USE_STD_ATOMIC
-pthread -I/usr/include -I./libmw/include -I./libmw/deps/caches/include
-I./libmw/deps/ghc/include -I./libmw/deps/mio/include -I./univalue/include
-DBOOST_TEST_DYN_LINK -I. -I./libmw/include -I./libmw/deps/crypto/include
-Ilibmw/test/framework/include -Wdate-time -D_FORTIFY_SOURCE=2
-DHAVE_BUILD_INFO -D__STDC_FORMAT_MACROS -fstack-reuse=none -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIC
-fno-extended-identifiers -c -o test/test_litecoin-amount_tests.o `test -f
'test/amount_tests.cpp' || echo './'`test/amount_tests.cpp
make[4]: *** [Makefile:18665:
wallet/test/test_test_litecoin-init_test_fixture.o] Error 1
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: litecoin
Source-Version: 0.21.2.2-1.2
Done: Anton Gladky
We believe that the bug you reported is fixed in the latest version of
litecoin, 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 1059...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Anton Gladky (supplier of updated litecoin 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: Sat, 30 Dec 2023 15:17:54 +0100
Source: litecoin
Architecture: source
Version: 0.21.2.2-1.2
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov
Changed-By: Anton Gladky
Closes: 1059138
Changes:
litecoin (0.21.2.2-1.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix compilation against boost 1.83. (Closes: #1059138)
Checksums-Sha1:
67babc85fe87ee9b4198b5571481230fa7cfdd1d 2145 litecoin_0.21.2.2-1.2.dsc
c19f19f416e8a45f08ab5e4d6f86333788039e90 16584
litecoin_0.21.2.2-1.2.debian.tar.xz
1187836a3c9e1d4cb827948a6ff318d1672d0803 17796
litecoin_0.21.2.2-1.2_source.buildinfo
Checksums-Sha256:
db19062cd7012baacef8c07455aa3e97eced0f4ad94b43e3ca69056f1ddf7a70 2145
litecoin_0.21.2.2-1.2.dsc
286bd09a5f28dec554707fba6d4b277bb2a0246c8fc3c54675a40b84e4066462 16584
litecoin_0.21.2.2-1.2.debian.tar.xz
151f7fe7e79da756afdf6e017a1108ec1f6e18e11dba05b428fd160335bda8a1 17796
litecoin_0.21.2.2-1.2_source.buildinfo
Files:
4949ec5cbbc0945cf0e4b7a1aca08b2f 2145 utils optional litecoin_0.21.2.2-1.2.dsc
5d52f0d24440659a4d486680f6420274 16584 utils optional
litecoin_0.21.2.2-1.2.debian.tar.xz
2a0c3fda98a2675c2208d2c81d6ad3bf 17796 utils optional
litecoin_0.21.2.2-1.2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmWQMuUACgkQ0+Fzg8+n
/waXaQ/8C8VEXKCOvZXb8vdiGwVYETMZ/DMXG/Kd+hHR+9A5lxNaPdtIrbjbUaZl
QgAIUTYxVM0tJDZ6OefXm/cK6utXOIoifUsfgnJjpOYeyCZ/4iXiM2cpHPrAHmut
dqSup2HPVb5R9ukpxo429dlLueCErjzqoMl+5Wju/KVHfwRrGQiudCyfrJw3MFwA
Bug#1058743: marked as done (libuv1: FTBFS on s390x on older kernels)
Your message dated Sat, 30 Dec 2023 18:35:02 +
with message-id
and subject line Bug#1058743: fixed in libuv1 1.46.0-3
has caused the Debian Bug report #1058743,
regarding libuv1: FTBFS on s390x on older kernels
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.)
--
1058743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libuv1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: scho...@ubuntu.com
Hi!
If the buildd is using an older kernel version, such as 5.4 as is the
case in the Ubuntu s390x builders, the build fails on the following
tests:
not ok 147 - idle_starvation
not ok 366 - timer_from_check
In Ubuntu, the attached patch was applied to fix it.
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-14-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru
libuv1-1.46.0/debian/patches/lp2046442-linux-don-t-use-io_uring-on-pre-5.10.186-kernels-409.patch
libuv1-1.46.0/debian/patches/lp2046442-linux-don-t-use-io_uring-on-pre-5.10.186-kernels-409.patch
---
libuv1-1.46.0/debian/patches/lp2046442-linux-don-t-use-io_uring-on-pre-5.10.186-kernels-409.patch
1970-01-01 01:00:00.0 +0100
+++
libuv1-1.46.0/debian/patches/lp2046442-linux-don-t-use-io_uring-on-pre-5.10.186-kernels-409.patch
2023-12-15 12:44:07.0 +0100
@@ -0,0 +1,39 @@
+From 50b53cbd0db8d4e7be06939a0976ff520e791d31 Mon Sep 17 00:00:00 2001
+From: Ben Noordhuis
+Date: Wed, 12 Jul 2023 23:33:49 +0200
+Subject: [PATCH] linux: don't use io_uring on pre-5.10.186 kernels (#4093)
+
+Those kernels have a known resource consumption bug where the sqpoll
+thread busy-loops.
+
+Fixes: https://github.com/libuv/libuv/issues/4089
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libuv1/+bug/2046442
+Origin: upstream,
https://github.com/libuv/libuv/commit/50b53cbd0db8d4e7be06939a0976ff520e791d31
+Applied-Upstream: v1.47.0
+---
+ src/unix/linux.c | 8 +++-
+ 1 file changed, 7 insertions(+), 1 deletion(-)
+
+diff --git a/src/unix/linux.c b/src/unix/linux.c
+index 28803225..65fb847f 100644
+--- a/src/unix/linux.c
b/src/unix/linux.c
+@@ -431,8 +431,14 @@ static int uv__use_io_uring(void) {
+ use = atomic_load_explicit(_io_uring, memory_order_relaxed);
+
+ if (use == 0) {
++/* Older kernels have a bug where the sqpoll thread uses 100% CPU. */
++use = uv__kernel_version() >= /* 5.10.186 */ 0x050ABA ? 1 : -1;
++
++/* But users can still enable it if they so desire. */
+ val = getenv("UV_USE_IO_URING");
+-use = val == NULL || atoi(val) ? 1 : -1;
++if (val != NULL)
++ use = atoi(val) ? 1 : -1;
++
+ atomic_store_explicit(_io_uring, use, memory_order_relaxed);
+ }
+
+--
+2.40.1
+
diff -Nru libuv1-1.46.0/debian/patches/series
libuv1-1.46.0/debian/patches/series
--- libuv1-1.46.0/debian/patches/series 2023-10-15 16:37:48.0 +0200
+++ libuv1-1.46.0/debian/patches/series 2023-12-15 12:43:14.0 +0100
@@ -3,3 +3,4 @@
disable_ipv6_test.patch
path_max_zero_st_size
skip-multicast-test
+lp2046442-linux-don-t-use-io_uring-on-pre-5.10.186-kernels-409.patch
--- End Message ---
--- Begin Message ---
Source: libuv1
Source-Version: 1.46.0-3
Done: Dominique Dumont
We believe that the bug you reported is fixed in the latest version of
libuv1, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dominique Dumont (supplier of updated libuv1 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:
Processed: tagging 1056844
Processing commands for cont...@bugs.debian.org: > tags 1056844 + ftbfs Bug #1056844 [src:pyregion] pyregion: ftbfs with cython 3.0.x Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 1055758 in 7.3.0p2-1
Processing commands for cont...@bugs.debian.org: > fixed 1055758 7.3.0p2-1 Bug #1055758 [opensmtpd] opensmtpd: OpenSMTPD release in stable (bookworm) is useless due to #1037359 Ignoring request to alter fixed versions of bug #1055758 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1055758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1056820
Processing commands for cont...@bugs.debian.org: > tags 1056820 + ftbfs Bug #1056820 [src:mpi4py] mpi4py: ftbfs with cython 3.0.x Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1054747 to ruby-pry-byebug
Processing commands for cont...@bugs.debian.org:
> reassign 1054747 ruby-pry-byebug
Bug #1054747 {Done: Vinay Keshava } [ruby-pry-debug]
ruby-octokit: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: require
'pry-byebug'
Warning: Unknown package 'ruby-pry-debug'
Bug reassigned from package 'ruby-pry-debug' to 'ruby-pry-byebug'.
Ignoring request to alter found versions of bug #1054747 to the same values
previously set
Ignoring request to alter fixed versions of bug #1054747 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1054747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1058876: libopenmpi-dev: paths missing /usr/include...(for fortran mpi.mod)
On 27/12/2023 21:30, Drew Parsons wrote:
Hi Alistair, given the complexity around hacking openmpi to
accommodate placing the mod files under /usr/include, I'm starting to
wonder whether it's the best way of resolving Bug#1058526 in the first
place.
I did it bit of background reading on the fortran mod files. There's a
fair bit of dissent about them, and no consensus on a proper
location. e.g. https://fortranwiki.org/fortran/show/Library+distribution
The files are binary dependent (and compiler version dependent), and
not clear that /usr/include is the best place for them anyway.
mpich seems to be fine placing them in
/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/mpich, and openmpi
seemed to be happy enough doing the same up until Bug#1058526.
Is there a different way of resolving Bug#1058526 without moving the
mod files to /usr/include?
Drew
I had altered FMODDIR from /usr/lib/ to /usr/include to match what
appears to be most conventional, but given the problems caused, I'm
backing out that change and reverting to /usr/lib/${DEB_HOST_MULTIARCH}/.
It will take changes in dh-fortran-mod and openmpi which I'm doing today.
Alastair
--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
ph: +353 87 6847928 e: alast...@mckinstry.ie, im: @alastair:mckinstry.ie
Processed: Bug#1057929 marked as pending in buildbot
Processing control commands: > tag -1 pending Bug #1057929 [src:buildbot] buildbot: FTBFS: locale.Error: unsupported locale setting Added tag(s) pending. -- 1057929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057929: marked as pending in buildbot
Control: tag -1 pending Hello, Bug #1057929 in buildbot reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/buildbot/-/commit/c340fc5a17db85a06a15b345cbf6b9dfe14bb63e d/patches: force C.UTF-8 locale when building docs Closes: #1057929 Signed-off-by: Robin Jarry (this message was generated automatically) -- Greetings https://bugs.debian.org/1057929
Processed: Bug#1057609 marked as pending in tpm2-pytss
Processing control commands:
> tag -1 pending
Bug #1057609 {Done: Bastian Germann } [src:tpm2-pytss]
tpm2-pytss: FTBFS: Handler for event 'build-finished' threw an exception (exception: str
expected, not _StrPath)
Added tag(s) pending.
--
1057609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1057609: marked as pending in tpm2-pytss
Control: tag -1 pending Hello, Bug #1057609 in tpm2-pytss reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/tpm2-pytss/-/commit/2ca47ac8bcb1a449a35042aef38fb819f8ed26f6 Disconnect sphinx extdev handler (Closes: #1057609) (this message was generated automatically) -- Greetings https://bugs.debian.org/1057609
Bug#1057609: marked as done (tpm2-pytss: FTBFS: Handler for event 'build-finished' threw an exception (exception: str expected, not _StrPath))
Your message dated Sat, 30 Dec 2023 11:50:45 +
with message-id
and subject line Bug#1057609: fixed in tpm2-pytss 2.1.0-2
has caused the Debian Bug report #1057609,
regarding tpm2-pytss: FTBFS: Handler for event 'build-finished' threw an exception (exception: str
expected, not _StrPath)
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.)
--
1057609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tpm2-pytss
Version: 2.1.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=pybuild --with python3,sphinxdoc
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.12 with "build"
module
I: pybuild base:310: python3.12 -m build --skip-dependency-check --no-isolation --wheel
--outdir /<>/.pybuild/cpython3_3.12_tpm2_pytss
* Building wheel...
/<>/scripts/prepare_headers.py:27: SyntaxWarning: invalid escape
sequence '\('
s = re.sub("#define TSS2_RC_LAYER\(level\).*", "", s)
/<>/scripts/prepare_headers.py:28: SyntaxWarning: invalid escape
sequence '\('
s = re.sub("(#define.*)TSS2_RC_LAYER\(0xff\)", "\g<1>0xff", s)
/<>/scripts/prepare_headers.py:28: SyntaxWarning: invalid escape
sequence '\g'
s = re.sub("(#define.*)TSS2_RC_LAYER\(0xff\)", "\g<1>0xff", s)
/<>/scripts/prepare_headers.py:31: SyntaxWarning: invalid escape
sequence '\*'
s = re.sub("/\*.*?\*/", "", s, flags=re.MULTILINE)
/<>/scripts/prepare_headers.py:34: SyntaxWarning: invalid escape
sequence '\('
s = re.sub("(#define [A-Za-z0-9_]+) +\(\(.*?\) \(.*?\)\)", "\g<1>...", s)
/<>/scripts/prepare_headers.py:34: SyntaxWarning: invalid escape
sequence '\g'
s = re.sub("(#define [A-Za-z0-9_]+) +\(\(.*?\) \(.*?\)\)", "\g<1>...", s)
/<>/scripts/prepare_headers.py:35: SyntaxWarning: invalid escape
sequence '\('
s = re.sub("(#define [A-Za-z0-9_]+) +\(\(.*?\).*?\) ", "\g<1>...", s)
/<>/scripts/prepare_headers.py:35: SyntaxWarning: invalid escape
sequence '\g'
s = re.sub("(#define [A-Za-z0-9_]+) +\(\(.*?\).*?\) ", "\g<1>...", s)
/<>/scripts/prepare_headers.py:37: SyntaxWarning: invalid escape
sequence '\)'
"(#define [A-Za-z0-9_]+) .*\n.*?.*\)\)", "\g<1>...", s, flags=re.MULTILINE
/<>/scripts/prepare_headers.py:37: SyntaxWarning: invalid escape
sequence '\g'
"(#define [A-Za-z0-9_]+) .*\n.*?.*\)\)", "\g<1>...", s, flags=re.MULTILINE
/<>/scripts/prepare_headers.py:39: SyntaxWarning: invalid escape
sequence '\g'
s = re.sub("(#define [A-Za-z0-9_]+) .*", "\g<1>...", s)
/<>/scripts/prepare_headers.py:42: SyntaxWarning: invalid escape
sequence '\['
s = re.sub("\[.+?\]", "[...]", s)
/<>/scripts/prepare_headers.py:77: SyntaxWarning: invalid escape
sequence '\)'
"#define TPM2_MAX_TAGGED_POLICIES.*\n.*TPMS_TAGGED_POLICY\)\)",
/<>/scripts/prepare_headers.py:262: SyntaxWarning: invalid escape
sequence '\s'
"TSS2_RC\s+Tss2_MU_BYTE_Marshal\(.+?\);", s, re.DOTALL | re.MULTILINE
/<>/scripts/prepare_headers.py:266: SyntaxWarning: invalid escape
sequence '\s'
"TSS2_RC\s+Tss2_MU_BYTE_Marshal\(.+?\);", "", s, 1, re.DOTALL | re.MULTILINE
/<>/scripts/prepare_headers.py:270: SyntaxWarning: invalid escape
sequence '\s'
"TSS2_RC\s+Tss2_MU_BYTE_Unmarshal\(.+?\);", s, re.DOTALL | re.MULTILINE
/<>/scripts/prepare_headers.py:274: SyntaxWarning: invalid escape
sequence '\s'
"TSS2_RC\s+Tss2_MU_BYTE_Unmarshal\(.+?\);",
adding path: /<>/scripts
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-cpython-312
creating build/lib.linux-x86_64-cpython-312/tpm2_pytss
copying src/tpm2_pytss/utils.py -> build/lib.linux-x86_64-cpython-312/tpm2_pytss
copying src/tpm2_pytss/TCTISPIHelper.py ->
build/lib.linux-x86_64-cpython-312/tpm2_pytss
copying src/tpm2_pytss/__init__.py ->
build/lib.linux-x86_64-cpython-312/tpm2_pytss
copying src/tpm2_pytss/TCTI.py -> build/lib.linux-x86_64-cpython-312/tpm2_pytss
copying src/tpm2_pytss/TCTILdr.py ->
build/lib.linux-x86_64-cpython-312/tpm2_pytss
copying src/tpm2_pytss/policy.py ->
build/lib.linux-x86_64-cpython-312/tpm2_pytss
copying src/tpm2_pytss/FAPI.py -> build/lib.linux-x86_64-cpython-312/tpm2_pytss
copying src/tpm2_pytss/constants.py ->
build/lib.linux-x86_64-cpython-312/tpm2_pytss
copying
Bug#1059659: marked as done (pg8000: autopkgtest failure with Python 3.12)
Your message dated Sat, 30 Dec 2023 11:50:12 +
with message-id
and subject line Bug#1059659: fixed in pg8000 1.30.3-2
has caused the Debian Bug report #1059659,
regarding pg8000: autopkgtest failure with Python 3.12
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.)
--
1059659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pg8000
Version: 1.30.3-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.12
Hi Maintainer
pg8000's autopkgtests fail with Python 3.12 [1]. I've copied what I
hope is the relevant part of the log below.
Regards
Graham
[1] https://ci.debian.net/packages/p/pg8000/testing/amd64/
49s === FAILURES
===
49s _ test_readme
__
49s
49s def test_readme():
49s failure_count, _ = doctest.testfile(
49s str(Path("..") / "README.rst"), verbose=False, optionflags=doctest.ELLIPSIS
49s )
49s > assert failure_count == 0
49s E assert 301 == 0
49s
49s test/test_readme.py:10: AssertionError
49s - Captured stdout call
-
49s **
49s File
"/tmp/autopkgtest-lxc.liyep0go/downtmp/build.OAq/src/test/../README.rst",
line 50, in README.rst
49s Failed example:
49s import pg8000.native
49s Exception raised:
49s Traceback (most recent call last):
49s File "/usr/lib/python3.12/doctest.py", line 1359, in __run
49s exec(compile(example.source, filename, "single",
49s File "", line 1, in
49s import pg8000.native
49s File
"/tmp/autopkgtest-lxc.liyep0go/downtmp/build.OAq/src/pg8000/__init__.py",
line 1, in
49s from pg8000.legacy import (
49s File "/tmp/autopkgtest-lxc.liyep0go/downtmp/build.OAq/src/pg8000/legacy.py",
line 6, in
49s from pg8000.converters import (
49s File
"/tmp/autopkgtest-lxc.liyep0go/downtmp/build.OAq/src/pg8000/converters.py",
line 21, in
49s from dateutil.parser import ParserError, parse
49s File "/usr/lib/python3/dist-packages/dateutil/parser/__init__.py",
line 2, in
49s from ._parser import parse, parser, parserinfo, ParserError
49s File "/usr/lib/python3/dist-packages/dateutil/parser/_parser.py",
line 50, in
49s from .. import tz
49s File "/usr/lib/python3/dist-packages/dateutil/tz/__init__.py",
line 2, in
49s from .tz import *
49s File "/usr/lib/python3/dist-packages/dateutil/tz/tz.py", line 37,
in
49s EPOCH = datetime.datetime.utcfromtimestamp(0)
49s ^
49s DeprecationWarning: datetime.datetime.utcfromtimestamp() is
deprecated and scheduled for removal in a future version. Use
timezone-aware objects to represent datetimes in UTC:
datetime.datetime.fromtimestamp(timestamp, datetime.UTC).
49s **
--- End Message ---
--- Begin Message ---
Source: pg8000
Source-Version: 1.30.3-2
Done: Jeroen Ploemen
We believe that the bug you reported is fixed in the latest version of
pg8000, 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 1059...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jeroen Ploemen (supplier of updated pg8000 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: Sat, 30 Dec 2023 11:29:37 +
Source: pg8000
Built-For-Profiles: noudeb
Architecture: source
Version: 1.30.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Jeroen Ploemen
Closes: 1059659
Changes:
pg8000 (1.30.3-2) unstable; urgency=medium
.
* Team upload.
* Tests: make deprecation warnings non-fatal in the doctest. (Closes:
#1059659)
Checksums-Sha1:
2f4a776f8d71fa9241c0bc08790af8b775ec8a8b 2341 pg8000_1.30.3-2.dsc
9ad0a42233487646d96aa2c803b8fbf04182c0cc 5624 pg8000_1.30.3-2.debian.tar.xz
06e3c050b1c739b4174c7ce85dbb70bd8dd0e838 14841 pg8000_1.30.3-2_source.buildinfo
Checksums-Sha256:
f2e01b7906db69add9d5ba56c2170fa8b41713c0bd7e53ff9692a172a777e624 2341
pg8000_1.30.3-2.dsc
Processed: reassign 1054747 to ruby-pry-debug
Processing commands for cont...@bugs.debian.org:
> reassign 1054747 ruby-pry-debug
Bug #1054747 {Done: Vinay Keshava }
[src:ruby-octokit] ruby-octokit: FTBFS: ERROR: Test "ruby3.1" failed:
Failure/Error: require 'pry-byebug'
Bug reassigned from package 'src:ruby-octokit' to 'ruby-pry-debug'.
Warning: Unknown package 'ruby-pry-debug'
Warning: Unknown package 'ruby-pry-debug'
No longer marked as found in versions ruby-octokit/4.20.0-1.
Warning: Unknown package 'ruby-pry-debug'
Warning: Unknown package 'ruby-pry-debug'
No longer marked as fixed in versions ruby-pry-byebug/3.10.1-1.
Warning: Unknown package 'ruby-pry-debug'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1054747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1054792: marked as done (lammps: FTBFS: dh_install: error: missing files, aborting)
Your message dated Sat, 30 Dec 2023 11:07:50 + with message-id and subject line Bug#1054792: fixed in lammps 20231121+dfsg-1 has caused the Debian Bug report #1054792, regarding lammps: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lammps Version: 20220106.git7586adbb6a+ds1-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/debian/build' > make[2]: Nothing to be done for 'preinstall'. > make[2]: Leaving directory '/<>/debian/build' > Install the project... > /usr/bin/cmake -P cmake_install.cmake > -- Install configuration: "None" > -- Installing: /<>/debian/tmp/usr/bin/lmp > -- Set runtime path of "/<>/debian/tmp/usr/bin/lmp" to "" > -- Installing: /<>/debian/tmp/usr/include/lammps/angle.h > -- Installing: /<>/debian/tmp/usr/include/lammps/atom.h > -- Installing: /<>/debian/tmp/usr/include/lammps/bond.h > -- Installing: /<>/debian/tmp/usr/include/lammps/citeme.h > -- Installing: /<>/debian/tmp/usr/include/lammps/comm.h > -- Installing: /<>/debian/tmp/usr/include/lammps/compute.h > -- Installing: /<>/debian/tmp/usr/include/lammps/dihedral.h > -- Installing: /<>/debian/tmp/usr/include/lammps/domain.h > -- Installing: /<>/debian/tmp/usr/include/lammps/error.h > -- Installing: /<>/debian/tmp/usr/include/lammps/fix.h > -- Installing: /<>/debian/tmp/usr/include/lammps/force.h > -- Installing: /<>/debian/tmp/usr/include/lammps/group.h > -- Installing: /<>/debian/tmp/usr/include/lammps/improper.h > -- Installing: /<>/debian/tmp/usr/include/lammps/input.h > -- Installing: /<>/debian/tmp/usr/include/lammps/info.h > -- Installing: /<>/debian/tmp/usr/include/lammps/kspace.h > -- Installing: /<>/debian/tmp/usr/include/lammps/lammps.h > -- Installing: /<>/debian/tmp/usr/include/lammps/lattice.h > -- Installing: /<>/debian/tmp/usr/include/lammps/library.h > -- Installing: /<>/debian/tmp/usr/include/lammps/lmppython.h > -- Installing: /<>/debian/tmp/usr/include/lammps/lmptype.h > -- Installing: /<>/debian/tmp/usr/include/lammps/memory.h > -- Installing: /<>/debian/tmp/usr/include/lammps/modify.h > -- Installing: /<>/debian/tmp/usr/include/lammps/neighbor.h > -- Installing: /<>/debian/tmp/usr/include/lammps/neigh_list.h > -- Installing: /<>/debian/tmp/usr/include/lammps/output.h > -- Installing: /<>/debian/tmp/usr/include/lammps/pair.h > -- Installing: /<>/debian/tmp/usr/include/lammps/pointers.h > -- Installing: /<>/debian/tmp/usr/include/lammps/region.h > -- Installing: /<>/debian/tmp/usr/include/lammps/timer.h > -- Installing: /<>/debian/tmp/usr/include/lammps/universe.h > -- Installing: /<>/debian/tmp/usr/include/lammps/update.h > -- Installing: /<>/debian/tmp/usr/include/lammps/utils.h > -- Installing: /<>/debian/tmp/usr/include/lammps/variable.h > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/liblammps.so.0 > -- Set runtime path of > "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/liblammps.so.0" to "" > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/liblammps.so > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/liblammps.pc > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/LAMMPS/LAMMPS_Targets.cmake > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/LAMMPS/LAMMPS_Targets-none.cmake > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/LAMMPS/LAMMPSConfig.cmake > -- Installing: > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/LAMMPS/LAMMPSConfigVersion.cmake > -- Installing: /<>/debian/tmp/usr/share/man/man1/lmp.1 > -- Installing: /<>/debian/tmp/etc/profile.d/lammps.sh > -- Installing: /<>/debian/tmp/etc/profile.d/lammps.csh > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: > SetuptoolsDeprecationWarning: setup.py install is deprecated. > !! > > > > Please avoid running ``setup.py`` directly. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html > for details. > > > > !! >
Bug#1058091: marked as done (presets: FTBFS: ModuleNotFoundError: No module named 'imp')
Your message dated Sat, 30 Dec 2023 11:08:24 +
with message-id
and subject line Bug#1058091: fixed in presets 0.1.3-4
has caused the Debian Bug report #1058091,
regarding presets: FTBFS: ModuleNotFoundError: No module named 'imp'
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.)
--
1058091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: presets
Version: 0.1.3-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py clean
> Traceback (most recent call last):
> File "/<>/setup.py", line 3, in
> import imp
> ModuleNotFoundError: No module named 'imp'
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.12 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11"
> returned exit code 13
> make: *** [debian/rules:5: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/presets_0.1.3-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=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: presets
Source-Version: 0.1.3-4
Done: Josenilson Ferreira da Silva
We believe that the bug you reported is fixed in the latest version of
presets, 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 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Josenilson Ferreira da Silva (supplier of updated
presets 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: Sat, 30 Dec 2023 07:28:02 -0300
Source: presets
Architecture: source
Version: 0.1.3-4
Distribution: unstable
Urgency: medium
Maintainer: Josenilson Ferreira da Silva
Changed-By: Josenilson Ferreira da Silva
Closes: 1058091
Changes:
presets (0.1.3-4) unstable; urgency=medium
.
* debian/control:
- Bumped Standards-Version to 4.6.2
- Added Testsuite: autopkgtest-pkg-pybuild
* debian/copyrigth: updated copyright year maintainer
* debian/patches: Fixed obsolete module error (Closes: #1058091)
Checksums-Sha1:
10dd0c31aaf4efefcf470afdedd9daaaf6814a17 2092 presets_0.1.3-4.dsc
aa79a7ef7a7aa94fbee5b5bea1d10cb14673db50 3020 presets_0.1.3-4.debian.tar.xz
2d529829d79a86b9e25c98e6cf9a3e0314d4b1d0 8963 presets_0.1.3-4_source.buildinfo
Checksums-Sha256:
7ae4a690e9e5cc6e89c6fc3d7c90de88d246c479305895932223d9eab5a43ee3 2092
presets_0.1.3-4.dsc
e9555f0930174534ca6583b443b1c231bc6e429e89927c7bbc2a5815b6c2a94e 3020
presets_0.1.3-4.debian.tar.xz
f2cc83814a09c13178dd84a557212d879bf6d12664ef0da0380e191afa8b3cfb 8963
presets_0.1.3-4_source.buildinfo
Files:
747734ed0be2d9d495e27ad55d4dcfa5 2092 python optional presets_0.1.3-4.dsc
e9b791e4b5e72e135b35586139102a15 3020 python optional
presets_0.1.3-4.debian.tar.xz
0f366e0d77dc3028513266529a581fda 8963 python optional
presets_0.1.3-4_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEqBlNXRF+LQLfMNMNB6n1YjE0Rs0FAmWP9NEACgkQB6n1YjE0
Rs1MTg//cpNcjsk6yk4wjwiJO1Apxr4umYkb0nwK1U69vhQqVqHPO4zVKvVa+B6o
8jkk0xPV6B9rBSfopAfftNkRVDEvPl1Zux7U1Qeig+bh8xZuBi1NkcvX62j2+mZo
Bug#1057609: tpm2-pytss: FTBFS: Handler for event 'build-finished' threw an exception (exception: str expected, not _StrPath)
The PYTHONPATH for the sphinx build has to contain the built module, so please replace ./src.
Processed: Bug#1059659 marked as pending in pg8000
Processing control commands: > tag -1 pending Bug #1059659 [src:pg8000] pg8000: autopkgtest failure with Python 3.12 Added tag(s) pending. -- 1059659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1059659: marked as pending in pg8000
Control: tag -1 pending Hello, Bug #1059659 in pg8000 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/pg8000/-/commit/cc8e6612d1ea4967b9e7af9e299fea1df2cd9722 Patches: add 0004 to make testsuite deprecation warnings nonfatal. (Closes: #1059659) (this message was generated automatically) -- Greetings https://bugs.debian.org/1059659
Processed: deal.ii ftbfs on ppc64el (with boost1.83)
Processing commands for cont...@bugs.debian.org: > forwarded 1059349 https://github.com/dealii/dealii/issues/16390 Bug #1059349 [src:deal.ii] deal.ii ftbfs on ppc64el (with boost1.83) Set Bug forwarded-to-address to 'https://github.com/dealii/dealii/issues/16390'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1059349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042829: marked as done (zipios++: FTBFS with recent jdupes)
Your message dated Sat, 30 Dec 2023 09:56:02 + with message-id and subject line Bug#1042829: fixed in zipios++ 2.3.2-1 has caused the Debian Bug report #1042829, regarding zipios++: 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.) -- 1042829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zipios++ Version: 2.2.6-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, zipios++/experimental recently started to FTBFS during a binary-arch build. The version in sid and binary-indep builds in experimental are not affected. ... debian/rules override_dh_link make[1]: Entering directory '/build/zipios++-2.2.6' dh_link rm -f debian/libzipios-dev/usr/lib/x86_64-linux-gnu/libzipios.so ln -s libzipios.so.2 debian/libzipios-dev/usr/lib/x86_64-linux-gnu/libzipios.so rm -f debian/libzipios2/usr/lib/x86_64-linux-gnu/libzipios.so.2 ln -s libzipios.so.2.2 debian/libzipios2/usr/lib/x86_64-linux-gnu/libzipios.so.2 jdupes -rl debian/libzipios-doc/usr/share/doc could not stat dir debian/libzipios-doc/usr/share/doc No duplicates found. make[1]: *** [debian/rules:28: override_dh_link] Error 1 make[1]: Leaving directory '/build/zipios++-2.2.6' make: *** [debian/rules:10: binary-arch] Error 2 This is probably caused by some recent changes in jdupes. Instead of override_dh_link you should rather use execute_after_dh_link-indep: jdupes -rl debian/libzipios-doc/usr/share/doc (completely untested, based on the log, I didn't look at the source) Andreas --- End Message --- --- Begin Message --- Source: zipios++ Source-Version: 2.3.2-1 Done: Francois Mazen We believe that the bug you reported is fixed in the latest version of zipios++, 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 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francois Mazen (supplier of updated zipios++ 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: Sat, 30 Dec 2023 09:34:38 +0100 Source: zipios++ Architecture: source Version: 2.3.2-1 Distribution: experimental Urgency: high Maintainer: Francois Mazen Changed-By: Francois Mazen Closes: 1042829 Changes: zipios++ (2.3.2-1) experimental; urgency=high . [ Debian Janitor ] * Apply multi-arch hints. + libzipios++-doc: Add Multi-Arch: foreign. * Use secure URI in Homepage field. * Set upstream metadata fields: Bug-Submit, Repository. . [ Francois Mazen ] * New upstream version. * Update standards version to 4.6.2, no changes needed. * Fix FTBFS with recent jdupes (Closes: #1042829) Checksums-Sha1: 13df0efdf395543bfe97a96ad2e8593f802132f3 2173 zipios++_2.3.2-1.dsc 5e06c8e6bead32a7b0ce8a859b2bf27a757b6430 340856 zipios++_2.3.2.orig.tar.gz bb8f40fef2db9a8146203cea274fefa34fa6d4ab 6528 zipios++_2.3.2-1.debian.tar.xz 877afa593d40fbdf033ec438ce371456a40854c6 8453 zipios++_2.3.2-1_source.buildinfo Checksums-Sha256: c42ed58d1c1d81412cb2aeedaa09ca5757b75479159d7a2b214693c1fa322f72 2173 zipios++_2.3.2-1.dsc d78b86c83af32864f1d68ced31bc0b2c47c69be0df518dca02b6b5ddd668dfe5 340856 zipios++_2.3.2.orig.tar.gz b67eee5e5416e358eb322ed87348644ab907bc2733d7953986a1f864ca3152a0 6528 zipios++_2.3.2-1.debian.tar.xz a22c7f20017c46edced986071fc1ee07ca319310fd1c016cc29b594bb02498d2 8453 zipios++_2.3.2-1_source.buildinfo Files: d36925e2eb7a11a6662c7441558e8cf5 2173 devel optional zipios++_2.3.2-1.dsc a49e5895e5a9163aa96a741229cbd458 340856 devel optional zipios++_2.3.2.orig.tar.gz dd090ea9452d8a66a970da984f69ce3f 6528 devel optional zipios++_2.3.2-1.debian.tar.xz b555c4b00271cfbd9bc545bdb4842c5f 8453 devel optional zipios++_2.3.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEhqWr1v/bCgx/UFfTR5f6chw1HJ4FAmWP4rUPHG16ZkBkZWJp YW4ub3JnAAoJEEeX+nIcNRyeob4QAJ+uM8jzoIprVOJBf/XNGX7f3git94WR3/FA 0X6p4XR8ce7GMbqdQZLFogZY2sCeTNycINWkOXQzU96IqhQ/vr7YjlCjGtLCJ5I3 2pgIYrMW6SF7dov1LFZ3+6gp6sYMu16MDwxCNegQMySg8s1S0eyh6qVpa4dUvzgL
Bug#1055973: marked as done (wesnoth: FTBFS: boost1.83 transition)
Your message dated Sat, 30 Dec 2023 09:55:50 +
with message-id
and subject line Bug#1055973: fixed in wesnoth-1.16 1:1.16.11-1
has caused the Debian Bug report #1055973,
regarding wesnoth: FTBFS: boost1.83 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.)
--
1055973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wesnoth
Version: 1:1.16.10-2
Severity: normal
User: gl...@debian.org
Usertags: boost183 ftbfs-boost183-transition
Hi,
we are preparing the transition of all libs on the new boost 1.83. During the
rebuild of packages against this library it was identified that probably your
package fails to build.
Relevant part (hopefully):
-
/<>/src/gettext.cpp:321:154: error: invalid new-expression of
abstract class type â{anonymous}::wesnoth_message_formatâ
321 | current_locale_ =
std::locale(current_locale_, new wesnoth_message_format(current_locale_,
loaded_domains_, loaded_paths_));
|
^
/<>/src/gettext.cpp:85:15: note: because the following virtual
functions are pure within â{anonymous}::wesnoth_message_formatâ:
85 | class wesnoth_message_format : public bl::message_format
-
To reproduce this behavior, you can install -dev Boost packages from the
experimental repository, as shown in the following command:
apt install libboost-dev -t experimental.
The full build log is available from:
http://qa-logs.debian.net/2023/10/26/wesnoth-1.16_1.16.10-2_unstable_boost181.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-boost183-transition;users=gl...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-boost183-transition=gl...@debian.org
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: wesnoth-1.16
Source-Version: 1:1.16.11-1
Done: Vincent Cheng
We believe that the bug you reported is fixed in the latest version of
wesnoth-1.16, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Vincent Cheng (supplier of updated wesnoth-1.16 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: Sat, 30 Dec 2023 01:18:06 -0800
Source: wesnoth-1.16
Built-For-Profiles: noudeb
Architecture: source
Version: 1:1.16.11-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team
Changed-By: Vincent Cheng
Closes: 1055973
Changes:
wesnoth-1.16 (1:1.16.11-1) unstable; urgency=medium
.
* New upstream release.
- Fix FTBFS with boost 1.83. (Closes: #1055973)
Checksums-Sha1:
12843ed635317a4053eff2161d4b39f5ba4511ec 4073 wesnoth-1.16_1.16.11-1.dsc
74549eaf01f7e7ca0954abc996de75704bfdbd70 476635149
wesnoth-1.16_1.16.11.orig.tar.bz2
745ce4939916248c44e00e974abe60618748307f 69012
wesnoth-1.16_1.16.11-1.debian.tar.xz
Checksums-Sha256:
a5cd6879542f44fed82380287ceffab3770ee12e11b9ec1101b1d42ff0f7c20f 4073
wesnoth-1.16_1.16.11-1.dsc
5761867f0346d554e63958b9680ad268385218a5547141310877837d3a2882db 476635149
wesnoth-1.16_1.16.11.orig.tar.bz2
37f328e25e4542a8b0f040a19385158b6c36fe2494888c2d6230f65c783fff84 69012
wesnoth-1.16_1.16.11-1.debian.tar.xz
Files:
b2104efc762299e01a3305342bc7ce49 4073 games optional wesnoth-1.16_1.16.11-1.dsc
926fce1f3b89e9cf409437a4b78802e6 476635149 games optional
wesnoth-1.16_1.16.11.orig.tar.bz2
07f4df6cf39834de623820f06d05721f 69012 games optional
wesnoth-1.16_1.16.11-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
Processed: bug 1057564 is forwarded to https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/142
Processing commands for cont...@bugs.debian.org: > forwarded 1057564 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/142 Bug #1057564 [src:gnome-bluetooth3,src:python-dbusmock] gnome-bluetooth3: FTBFS: failing tests Bug #1058116 [src:gnome-bluetooth3,src:python-dbusmock] gnome-bluetooth3: FTBFS: RuntimeError: Event loop is closed Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/142'. Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/142'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1057564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057564 1058116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027827: litecoin: FTBFS in bullseye (expired certificates in test suite)
I would volunteer to file a stable update request if you agree to move the package to the Cryptocoin Team.
Bug#1057542: ap-utils: FTBFS: input.c:340:43: error: invalid application of ‘sizeof’ to incomplete type ‘ITEM’ {aka ‘struct tagITEM’}
On 2023-12-05 23:03 +0100, Santiago Vila wrote:
> Package: src:ap-utils
> Version: 1.5-5
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
>
> [snip]
>
> The above is just how the build ends and not necessarily the most relevant
> part.
Indeed, the actual error was missing. To work around the massive amount
of -Woverflow warnings (there are literally thousands of them), I added
-Wno-overflow to DEB_CFLAGS_MAINT_APPEND, and this is what I got:
,
| gcc -DHAVE_CONFIG_H -I. -I.. -I../intl -Wdate-time -D_FORTIFY_SOURCE=2 -g
-O2 -ffile-prefix-map=/usr/local/src/deb-src/ap-utils/ap-utils=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wall -pedantic -Wno-overflow
-Wno-error=format-security -Wall -W -c -o input.o input.c
| input.c: In function 'get_value':
| input.c:129:18: warning: variable 'y' set but not used
[-Wunused-but-set-variable]
| 129 | int c, i, x, y;
| | ^
| input.c: In function 'menu_choose':
| input.c:340:43: error: invalid application of 'sizeof' to incomplete type
'ITEM' {aka 'struct tagITEM'}
| 340 | ITEM **menu_item = calloc(num, sizeof(ITEM)), **ip = menu_item;
| | ^~~~
`
Since ncurses patchlevel 20231021 the ITEM structure is opaque, hence
its size is unknown to the compiler. This probably means that the
menu_choose() function needs some substantial changes. I have not
investigated further, if somebody cares about this package and the old
AP points it supports they will have to do the work.
Cheers,
Sven
Bug#1057198: marked as done (rust-wasmtime: FTBFS error[E0599]: no function or associated item named `from_str` found for struct `Triple` in the current scope)
Your message dated Sat, 30 Dec 2023 09:35:24 + with message-id and subject line Bug#1057198: fixed in rust-wasmtime 15.0.1+dfsg-1 has caused the Debian Bug report #1057198, regarding rust-wasmtime: FTBFS error[E0599]: no function or associated item named `from_str` found for struct `Triple` in the current scope 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.) -- 1057198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-wasmtime Version: 15.0.0+dfsg-3 Severity: serious Control: block 1055090 by -1 https://buildd.debian.org/status/fetch.php?pkg=rust-wasmtime=all=15.0.0%2Bdfsg-3=1701097543=0 error[E0599]: no function or associated item named `from_str` found for struct `Triple` in the current scope --> cranelift/codegen/src/isa/mod.rs:118:12 | 118 | lookup(triple!(name)) |^ function or associated item not found in `Triple` | = help: items from traits can only be used if the trait is in scope = note: this error originates in the macro `triple` (in Nightly builds, run with -Z macro-backtrace for more info) help: the following trait is implemented but not in scope; perhaps add a `use` for it: | 46 + use core::str::FromStr; | For more information about this error, try `rustc --explain E0599`. The following warnings were emitted during compilation: --- End Message --- --- Begin Message --- Source: rust-wasmtime Source-Version: 15.0.1+dfsg-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of rust-wasmtime, 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 1057...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated rust-wasmtime 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: Sat, 30 Dec 2023 10:10:12 +0100 Source: rust-wasmtime Architecture: source Version: 15.0.1+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 1057198 Changes: rust-wasmtime (15.0.1+dfsg-1) experimental; urgency=medium . * drop patches 2001_arbitrary 2001_target-lexicon, obsoleted by Debian package changes; tighten (build-)dependency on package for crate target-lexicon; closes: bug#1057198, thanks to Peter Green * update patches * bump project version in virtual packages and autopkgtests Checksums-Sha1: b79ef6973463dc6f0eb554f07fbc55ade544af9c 3336 rust-wasmtime_15.0.1+dfsg-1.dsc f3d7be28c0b2d70d71d93c32749e215c58fb9884 3345136 rust-wasmtime_15.0.1+dfsg.orig.tar.xz 312bfa0c9cbffc2eaf5e9a53275605944d4d30b1 19992 rust-wasmtime_15.0.1+dfsg-1.debian.tar.xz 3b7496a479d895aa8ff19a42f120e4f7c989 21334 rust-wasmtime_15.0.1+dfsg-1_amd64.buildinfo Checksums-Sha256: 1ead60e4a09ec4d8336be7d59915accaad492984fdbde2c4d276a668c2ad82d0 3336 rust-wasmtime_15.0.1+dfsg-1.dsc 7906ecd48518d773dc5b74491809dc578a3752636df56f252fde23bffbbb9933 3345136 rust-wasmtime_15.0.1+dfsg.orig.tar.xz c56f00586219b57b4f16ddef01ed8dd5be8a2c429e2f952476efc294bc494666 19992 rust-wasmtime_15.0.1+dfsg-1.debian.tar.xz 3196c396b7b52eb963f3144c530b63a09408d8f503611a0bb8ab0480656bca66 21334 rust-wasmtime_15.0.1+dfsg-1_amd64.buildinfo Files: f914a4614a0fb862dc65af2293e6a3ed 3336 rust optional rust-wasmtime_15.0.1+dfsg-1.dsc 01c383b787bc943d144bfe720134b970 3345136 rust optional rust-wasmtime_15.0.1+dfsg.orig.tar.xz 928d29f420dc53996a5177890f301d04 19992 rust optional rust-wasmtime_15.0.1+dfsg-1.debian.tar.xz a51334a40d6f8348474a2208269ce1e1 21334 rust optional rust-wasmtime_15.0.1+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmWP4dsACgkQLHwxRsGg ASHc8w/+ON3f0y+88uVU5lUcYV2ZJe1lFSypFrVAhWAUTCGwgfOCsQ4t/rz3S+ca MQP2G5gapE6Rh3EsnAhuGA48EponerO07FK7SMDsAiPCNQjZAjVDLYyjf9ArK+gH nlaMPWlnCzDq2WNYe288gxXKFpl0+CR5E8e3W70XbsPg1NxKbUv9HFkyGNf1MWhB 34IkEZ03KsJxxboVh8x6mARn/4wqx+4lbqmXx8r6lWViwdA4zEQKHjkf5S/BSVGY Vujcq1tC2ZZITPeb59oFqIqbggPGTaI2mLdIU5RDPD+uNgwoDO29brpvKqFiyiSA
Bug#1042666: marked as done (flask-silk: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')
Your message dated Sat, 30 Dec 2023 08:34:10 + with message-id and subject line Bug#1042666: fixed in flask-silk 0.2-22 has caused the Debian Bug report #1042666, regarding flask-silk: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' 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.) -- 1042666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flask-silk Version: 0.2-21 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, flask-silk fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.11/build/flask_silk > copying flask_silk/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/flask_silk > running egg_info > writing Flask_Silk.egg-info/PKG-INFO > writing dependency_links to Flask_Silk.egg-info/dependency_links.txt > writing requirements to Flask_Silk.egg-info/requires.txt > writing top-level names to Flask_Silk.egg-info/top_level.txt > writing manifest file 'Flask_Silk.egg-info/SOURCES.txt' > reading manifest file 'Flask_Silk.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > adding license file 'LICENSE' > writing manifest file 'Flask_Silk.egg-info/SOURCES.txt' > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: > Package 'flask_silk.icons' is absent from the `packages` configuration. > !! > > > > > # Package would be ignored # > > Python recognizes 'flask_silk.icons' as an importable package[^1], > but it is absent from setuptools' `packages` configuration. > > This leads to an ambiguous overall configuration. If you want to > distribute this > package, please make sure that 'flask_silk.icons' is explicitly added > to the `packages` configuration field. > > Alternatively, you can also rely on setuptools' discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" on setuptools > documentation page: > > - > https://setuptools.pypa.io/en/latest/userguide/package_discovery.html > > If you don't want 'flask_silk.icons' to be distributed and are > already explicitly excluding 'flask_silk.icons' via > `find_namespace_packages(...)/find_namespace` or > `find_packages(...)/find`, > you can try to use `exclude_package_data`, or > `include-package-data=False` in > combination with a more fine grained `package-data` configuration. > > You can read more about "package data files" on setuptools > documentation page: > > - https://setuptools.pypa.io/en/latest/userguide/datafiles.html > > > [^1]: For Python, any directory (with suitable naming) can be > imported, > even if it does not contain any `.py` files. > On the other hand, currently there is no concept of package data > directory, all directories are treated like packages. > > > > !! > check.warn(importable) > creating /<>/.pybuild/cpython3_3.11/build/flask_silk/icons > copying flask_silk/icons/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/flask_silk/icons > copying flask_silk/icons/accept.png -> > /<>/.pybuild/cpython3_3.11/build/flask_silk/icons > copying flask_silk/icons/add.png -> > /<>/.pybuild/cpython3_3.11/build/flask_silk/icons > copying flask_silk/icons/anchor.png -> > /<>/.pybuild/cpython3_3.11/build/flask_silk/icons > copying flask_silk/icons/application.png -> > /<>/.pybuild/cpython3_3.11/build/flask_silk/icons > copying flask_silk/icons/application_add.png -> > /<>/.pybuild/cpython3_3.11/build/flask_silk/icons > copying flask_silk/icons/application_cascade.png -> > /<>/.pybuild/cpython3_3.11/build/flask_silk/icons > copying flask_silk/icons/application_delete.png -> > /<>/.pybuild/cpython3_3.11/build/flask_silk/icons > copying flask_silk/icons/application_double.png -> >
