Bug#1037213: Awstats bug #1037213 - is bug really fixed?
On 01 sept. 2023 13:55, Lourisvaldo Figueredo Junior wrote: > Hi Christian, > > I saw now that you adopted the awstats package and that you closed this bug > (1037213). > But I believe the bug is not resolved yet. It happens on bookworm. I have two > bugs open right now to fix this. [1] > > Since you are the maintainer now, how do you want to resolve this issue? I noticed that you have filed a bug 1050591 to backport cahnges added in 7.8-4 to bulleye. May be you can do the same for bookworm ? Christian
Bug#1050937: protobuf: FTBFS: ModuleNotFoundError: No module named 'tzdata'
Hello, probably tzdata split in legacy made this package FTBFS.
Solutions are:
1) fix the test to work with main tzdata
2) add dependency on tzdata-legacy package
G.
On Thu, 31 Aug 2023 23:07:59 +0800 Bo YU wrote:
Source: protobuf
Version: 3.21.12-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
protobuf fails to build from source. From my build log on amd64:
```
Traceback (most recent call last):
File "/usr/lib/python3.11/zoneinfo/_common.py", line 12, in load_tzdata
return resources.files(package_name).joinpath(resource_name).open("rb")
^
File "/usr/lib/python3.11/importlib/resources/_common.py", line 22, in files
return from_package(get_package(package))
File "/usr/lib/python3.11/importlib/resources/_common.py", line 53, in
get_package
resolved = resolve(package)
File "/usr/lib/python3.11/importlib/resources/_common.py", line 44, in resolve
return cand if isinstance(cand, types.ModuleType) else
importlib.import_module(cand)
^
File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1204, in _gcd_import
File "", line 1176, in _find_and_load
File "", line 1126, in _find_and_load_unlocked
File "", line 241, in _call_with_frames_removed
File "", line 1204, in _gcd_import
File "", line 1176, in _find_and_load
File "", line 1140, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'tzdata'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/<>/python3/setup.py", line 324, in
setup(
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
185, in setup
return run_commands(dist)
^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
201, in run_commands
dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
969, in run_commands
self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 223,
in run
self.run_tests()
File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 226,
in run_tests
test = unittest.main(
^^
OpenPGP_signature
Description: OpenPGP digital signature
Processed: tags 1042038 patch
Processing commands for cont...@bugs.debian.org: > tags 1042038 patch Bug #1042038 [src:mfem] mfem: FTBFS: hash.hpp:1001:39: error: ISO C++ forbids declaration of ‘type name’ with no type [-fpermissive] Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042038: mfem: FTBFS: hash.hpp:1001:39: error: ISO C++ forbids declaration of ‘type name’ with no type [-fpermissive]
Please find attached a patch with an upstream patch to fix this.
Related: https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes
>From b07acda4afb3056040bd2b07d209b76bec90a988 Mon Sep 17 00:00:00 2001
From: Amin Bandali
Date: Fri, 1 Sep 2023 21:11:04 -0400
Subject: [PATCH] Add upstream patch to fix FTBFS with gcc-13 (Closes:
#1042038)
---
debian/changelog | 7
debian/patches/fix-ftbfs-gcc-13.patch | 53 +++
debian/patches/series | 1 +
3 files changed, 61 insertions(+)
create mode 100644 debian/patches/fix-ftbfs-gcc-13.patch
diff --git a/debian/changelog b/debian/changelog
index 7d95e4c1e..e30df4c4d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+mfem (4.5.2+ds-2) UNRELEASED; urgency=medium
+
+ * Add upstream patch to fix FTBFS with gcc-13 (Closes: #1042038)
+- debian/patches/fix-ftbfs-gcc-13.patch
+
+ -- Amin Bandali Fri, 01 Sep 2023 21:10:21 -0400
+
mfem (4.5.2+ds-1) unstable; urgency=medium
* Initial release. (Closes: #1023223)
diff --git a/debian/patches/fix-ftbfs-gcc-13.patch b/debian/patches/fix-ftbfs-gcc-13.patch
new file mode 100644
index 0..5d202ab25
--- /dev/null
+++ b/debian/patches/fix-ftbfs-gcc-13.patch
@@ -0,0 +1,53 @@
+From 314a32af2ee80af8c9af7d8ad71babd51851154c Mon Sep 17 00:00:00 2001
+From: David Dement
+Origin: https://github.com/mfem/mfem/commit/314a32af2ee80af8c9af7d8ad71babd51851154c
+Date: Thu, 27 Apr 2023 10:33:51 -0400
+Subject: [PATCH] Fixes comilation errors when compiling with gcc-13 on Fedora
+ 38
+
+When compiling with gcc-13, types such as uint64_t are not defined.
+It is likely that is included implicitly with older compiler
+versions.
+---
+ general/hash.hpp| 1 +
+ general/mem_manager.cpp | 1 +
+ mesh/vtk.hpp| 2 ++
+ 3 files changed, 4 insertions(+)
+
+diff --git a/general/hash.hpp b/general/hash.hpp
+index 86d987d8029..288d51288df 100644
+--- a/general/hash.hpp
b/general/hash.hpp
+@@ -16,6 +16,7 @@
+ #include "array.hpp"
+ #include "globals.hpp"
+ #include
++#include
+
+ namespace mfem
+ {
+diff --git a/general/mem_manager.cpp b/general/mem_manager.cpp
+index 416a6ac6203..37b80c878ad 100644
+--- a/general/mem_manager.cpp
b/general/mem_manager.cpp
+@@ -16,6 +16,7 @@
+ #include // std::memcpy, std::memcmp
+ #include
+ #include // std::max
++#include
+
+ // Uncomment to try _WIN32 platform
+ //#define _WIN32
+diff --git a/mesh/vtk.hpp b/mesh/vtk.hpp
+index a59bed27592..50eeea5bc78 100644
+--- a/mesh/vtk.hpp
b/mesh/vtk.hpp
+@@ -12,6 +12,8 @@
+ #ifndef MFEM_VTK
+ #define MFEM_VTK
+
++#include
++
+ #include "../fem/geom.hpp"
+ #include "../general/binaryio.hpp"
+
diff --git a/debian/patches/series b/debian/patches/series
index 6f0d8f01a..d42e867b3 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
static-no-shared-yes
not-makefile
+fix-ftbfs-gcc-13.patch
--
2.39.2
Bug#1041249: cpp-httplib: FTBFS on s390x: ../test/test.cc:5462: Failure
Sebastian, cpp-httplib has built on all release architectures now. This bug is now blocking migration to Testing. Thank you, Jeremy Bícha
Processed: notfixed 1037213 in 7.9-1
Processing commands for cont...@bugs.debian.org:
> notfixed 1037213 7.9-1
Bug #1037213 {Done: Christian Marillat } [awstats]
awstats: prompting due to modified conffiles which were not modified by the
user: /etc/logrotate.d/httpd-prerotate/awstats
No longer marked as fixed in versions awstats/7.9-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1037213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1037213: Awstats bug #1037213 - is bug really fixed?
On 01 sept. 2023 13:55, Lourisvaldo Figueredo Junior wrote: > Hi Christian, Hi, > I saw now that you adopted the awstats package and that you closed this bug > (1037213). > But I believe the bug is not resolved yet. It happens on bookworm. I have two > bugs open right now to fix this. [1] > > Since you are the maintainer now, how do you want to resolve this issue? This bug has been fixed in version 7.8-4 7.8-4 need to be backported in bookworm Christian
Processed: fixed 1037213 in 7.8-4
Processing commands for cont...@bugs.debian.org:
> fixed 1037213 7.8-4
Bug #1037213 {Done: Christian Marillat } [awstats]
awstats: prompting due to modified conffiles which were not modified by the
user: /etc/logrotate.d/httpd-prerotate/awstats
Marked as fixed in versions awstats/7.8-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1037213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1051066: netatalk: 9 outstanding CVEs in Bullseye with available patches
To add the justification for the critical severity of this ticket: At least 6 of the 9 vulnerabilities grant theoretical root access of a Debian system running non-patched netatalk. CVE-2022-43634, CVE-2022-23124, CVE-2022-23123, CVE-2022-23122, CVE-2022-23121, CVE-2022-0194
Bug#1051066: netatalk: 9 outstanding CVEs in Bullseye with available patches
Package: netatalk Version: 3.1.12~ds-8 Severity: critical Tags: patch security Justification: root security hole X-Debbugs-Cc: pkg-netatalk-de...@alioth-lists.debian.net, Debian Security Team Nine CVE security advisories were addressed in netatalk upstream releases between 3.1.13 and 3.1.15. The full list is below: CVE-2022-45188 CVE-2022-43634 CVE-2022-23125 CVE-2022-23124 CVE-2022-23123 CVE-2022-23122 CVE-2022-23121 CVE-2022-0194 CVE-2021-31439 Current status of patching these vulnerabilities: - netatalk oldoldstable has already been patched by the Security Team. - netatalk unstable has already been patched by the maintainer team. - The netatalk package was excluded from stable, no action required. - What remains is to patch oldstable, hence this ticket. A debpatch has been attached to the related Release bug ticket, where approval to proceed with an oldstable release has been requested. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049325 -- System Information: Debian Release: 11.7 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-11-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages netatalk depends on: ii init-system-helpers 1.60 ii libacl1 2.2.53-10 ii libavahi-client3 0.8-5+deb11u2 ii libavahi-common3 0.8-5+deb11u2 ii libc62.31-13+deb11u6 ii libcrack22.9.6-3.4 ii libcrypt11:4.4.18-4 ii libdb5.3 5.3.28+dfsg1-0.8 ii libdbus-glib-1-2 0.110-6 ii libevent-2.1-7 2.1.12-stable-1 ii libgcrypt20 1.8.7-6 ii libglib2.0-0 2.66.8-1 ii libgssapi-krb5-2 1.18.3-6+deb11u3 ii libkrb5-31.18.3-6+deb11u3 ii libldap-2.4-22.4.57+dfsg-3+deb11u1 ii libmariadb3 1:10.5.19-0+deb11u2 ii libpam-modules 1.4.0-9+deb11u1 ii libpam0g 1.4.0-9+deb11u1 ii libssl1.11.1.1n-0+deb11u4 ii libtalloc2 2.3.1-2+b1 ii libtdb1 1.4.3-1+b1 ii libtracker-sparql-2.0-0 2.3.6-2 ii libwrap0 7.6.q-31 ii lsb-base 11.1.0 ii netbase 6.3 ii perl 5.32.1-4+deb11u2 Versions of packages netatalk recommends: ii avahi-daemon 0.8-5+deb11u2 ii cracklib-runtime 2.9.6-3.4 ii dbus 1.12.24-0+deb11u1 ii lsof 4.93.2+dfsg-1.1 ii procps2:3.3.17-5 ii python3 3.9.2-3 ii python3-dbus 1.2.16-5 ii tracker 2.3.6-2 Versions of packages netatalk suggests: pn quota -- no debconf information
Bug#1051065: weex: d/copyright: Incorrect upstream source
Source: weex Severity: serious Version: 2.8.4.2 debian/copyright claims the upstream source is at http://weex.sourceforge.net. I cannot find version 2.8.4, 2.8.4.1, or 2.8.4.2 at that website. Please fix the copyright file. If there are no such versions, please fix your source format to be non-native and have a Debian revision.
Bug#1051063: vim-scripts: no license assumption must be non-free
Source: vim-scripts Severity: serious Version: 20210124.2 In vim-script's copyright file, the following assumption is written: "Summary of license information of each script is reported below. For scripts which license is "no license" it is assumed in good faith that having being posted on vim.org their licence is at least as free as the licence of Vim itself." This assumption is wrong. International copyright agreements unfortunately make those files non-DFSG-free. Please move them affected files to a new source package with Section: non-free/editors.
Bug#1042147: marked as done (virt-manager: FTBFS: AssertionError: Conversion outputs did not match.)
Your message dated Fri, 01 Sep 2023 20:55:54 + with message-id and subject line Bug#1042147: fixed in virt-manager 1:4.1.0-3 has caused the Debian Bug report #1042147, regarding virt-manager: FTBFS: AssertionError: Conversion outputs did not match. 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.) -- 1042147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: virt-manager Version: 1:4.1.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > pytest-3 -v -rs > = test session starts > == > platform linux -- Python 3.11.4, pytest-7.4.0, pluggy-1.2.0 -- > /usr/bin/python3 > cachedir: .pytest_cache > rootdir: /<> > configfile: setup.cfg > testpaths: tests/ > collecting ... collected 543 items > > tests/test_capabilities.py::testCapsCPUFeaturesNewSyntax PASSED [ > 0%] > tests/test_capabilities.py::testCapsUtilFuncs PASSED [ > 0%] > tests/test_capabilities.py::testDomainCapabilities PASSED[ > 0%] > tests/test_capabilities.py::testDomainCapabilitiesx86 PASSED [ > 0%] > tests/test_capabilities.py::testDomainCapabilitiesAArch64 PASSED [ > 0%] > tests/test_cloner.py::test_clone_unmanaged PASSED[ > 1%] > tests/test_cloner.py::test_generate_name PASSED [ > 1%] > tests/test_conn.py::test_misc PASSED [ > 1%] > tests/test_conn.py::test_default_uri PASSED [ > 1%] > tests/test_conn.py::test_poll PASSED [ > 1%] > tests/test_disk.py::test_disk_numtotarget PASSED [ > 2%] > tests/test_disk.py::test_disk_dir_searchable PASSED [ > 2%] > tests/test_disk.py::test_disk_path_in_use_kernel PASSED [ > 2%] > tests/test_disk.py::test_disk_diskbackend_misc PASSED[ > 2%] > tests/test_disk.py::test_disk_diskbackend_parse PASSED [ > 2%] > tests/test_disk.py::test_disk_rbd_path PASSED[ > 2%] > tests/test_misc.py::test_misc_cpu_topology PASSED[ > 3%] > tests/test_misc.py::test_misc_guest_osinfo_metadata PASSED [ > 3%] > tests/test_misc.py::test_misc_nonpredicatble_generate PASSED [ > 3%] > tests/test_misc.py::test_misc_support_cornercases PASSED [ > 3%] > tests/test_misc.py::test_misc_osxml_cornercases PASSED [ > 3%] > tests/test_misc.py::test_misc_cpu_cornercases PASSED [ > 4%] > tests/test_misc.py::test_misc_meter PASSED [ > 4%] > tests/test_nodedev.py::testFunkyChars PASSED [ > 4%] > tests/test_nodedev.py::testNetDevice PASSED [ > 4%] > tests/test_nodedev.py::testPCIDevice PASSED [ > 4%] > tests/test_nodedev.py::testUSBDevDevice PASSED [ > 4%] > tests/test_nodedev.py::testSCSIDevice PASSED [ > 5%] > tests/test_nodedev.py::testStorageDevice PASSED [ > 5%] > tests/test_nodedev.py::testSCSIBus PASSED[ > 5%] > tests/test_nodedev.py::testDRMDevice PASSED [ > 5%] > tests/test_nodedev.py::testDASDMdev PASSED [ > 5%] > tests/test_nodedev.py::testAPQNMdev PASSED [ > 6%] > tests/test_nodedev.py::testPCIMdev PASSED[ > 6%] > tests/test_nodedev.py::testPCIMdevNewFormat PASSED [ > 6%] > tests/test_nodedev.py::testNodeDev2USB1 PASSED [ > 6%] > tests/test_nodedev.py::testNodeDev2USB2 PASSED [ > 6%] > tests/test_nodedev.py::testNodeDev2PCI PASSED[ > 6%] > tests/test_nodedev.py::testNodeDevFail PASSED[ > 7%] > tests/test_osdict.py::test_list_os PASSED[ > 7%] > tests/test_osdict.py::test_recommended_resources PASSED [ > 7%] > tests/test_osdict.py::test_urldetct_ma
Bug#1051059: vde2: d/copyright: Upstream source not mentioned
Source: vde2 Severity: serious Version: 2.3.2+r586-8 Please add the upstream source to debian/copyright, as required by Policy §12.5.
Bug#1051055: focalinux: non-free GFDL variant
Source: focalinux Version: 2010-09-3.1 Severity: serious Your package is licensed under the GFDL-1.1, not the GFDL-NIV-1.1 variant (with no Front-Cover or Back-Cover Texts or Invariant Sections). Please see https://www.debian.org/vote/2006/vote_001 on why this is a non-free license. Please consider asking upstream for a change.
Processed: tagging 1042147
Processing commands for cont...@bugs.debian.org: > tags 1042147 + pending Bug #1042147 [src:virt-manager] virt-manager: FTBFS: AssertionError: Conversion outputs did not match. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1042147 marked as pending in virt-manager
Processing control commands: > tag -1 pending Bug #1042147 [src:virt-manager] virt-manager: FTBFS: AssertionError: Conversion outputs did not match. Ignoring request to alter tags of bug #1042147 to the same tags previously set -- 1042147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042147: marked as pending in virt-manager
Control: tag -1 pending Hello, Bug #1042147 in virt-manager 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/libvirt-team/virt-manager/-/commit/35d6d1eeea61ea361289eb940ada658ecd74a017 d/patches: fix tests with newer osinfo-db Closes: #1042147 (this message was generated automatically) -- Greetings https://bugs.debian.org/1042147
Bug#1042182: marked as done (python-pytest-subtests: FTBFS: ModuleNotFoundError: No module named 'attr')
Your message dated Fri, 01 Sep 2023 19:36:22 + with message-id and subject line Bug#1042182: fixed in python-pytest-subtests 0.11.0-2 has caused the Debian Bug report #1042182, regarding python-pytest-subtests: FTBFS: ModuleNotFoundError: No module named 'attr' 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.) -- 1042182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pytest-subtests Version: 0.11.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild >dh_auto_build -O--buildsystem=pybuild > I: pybuild plugin_pyproject:107: Building wheel for python3.11 with "build" > module > I: pybuild base:240: python3.11 -m build --skip-dependency-check > --no-isolation --wheel --outdir > /<>/.pybuild/cpython3_3.11_pytest-subtests > * Building wheel... > /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: > _DeprecatedConfig: Deprecated config in `setup.cfg` > !! > > > > The license_file parameter is deprecated, use license_files instead. > > By 2023-Oct-30, you need to update your project and remove deprecated > calls > or your builds will no longer be supported. > > See > https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for > details. > > > > !! > parsed = self.parsers.get(option_name, lambda x: x)(value) > running bdist_wheel > running build > running build_py > creating build > creating build/lib > copying src/pytest_subtests.py -> build/lib > installing to build/bdist.linux-x86_64/wheel > running install > running install_lib > creating build/bdist.linux-x86_64 > creating build/bdist.linux-x86_64/wheel > copying build/lib/pytest_subtests.py -> build/bdist.linux-x86_64/wheel > running install_egg_info > running egg_info > creating src/pytest_subtests.egg-info > writing src/pytest_subtests.egg-info/PKG-INFO > writing dependency_links to src/pytest_subtests.egg-info/dependency_links.txt > writing entry points to src/pytest_subtests.egg-info/entry_points.txt > writing requirements to src/pytest_subtests.egg-info/requires.txt > writing top-level names to src/pytest_subtests.egg-info/top_level.txt > writing manifest file 'src/pytest_subtests.egg-info/SOURCES.txt' > reading manifest file 'src/pytest_subtests.egg-info/SOURCES.txt' > adding license file 'LICENSE' > writing manifest file 'src/pytest_subtests.egg-info/SOURCES.txt' > Copying src/pytest_subtests.egg-info to > build/bdist.linux-x86_64/wheel/pytest_subtests-0.11.0.egg-info > running install_scripts > creating build/bdist.linux-x86_64/wheel/pytest_subtests-0.11.0.dist-info/WHEEL > creating > '/<>/.pybuild/cpython3_3.11_pytest-subtests/.tmp-6ph07p_p/pytest_subtests-0.11.0-py3-none-any.whl' > and adding 'build/bdist.linux-x86_64/wheel' to it > adding 'pytest_subtests.py' > adding 'pytest_subtests-0.11.0.dist-info/LICENSE' > adding 'pytest_subtests-0.11.0.dist-info/METADATA' > adding 'pytest_subtests-0.11.0.dist-info/WHEEL' > adding 'pytest_subtests-0.11.0.dist-info/entry_points.txt' > adding 'pytest_subtests-0.11.0.dist-info/top_level.txt' > adding 'pytest_subtests-0.11.0.dist-info/RECORD' > removing build/bdist.linux-x86_64/wheel > Successfully built pytest_subtests-0.11.0-py3-none-any.whl > I: pybuild plugin_pyproject:119: Unpacking wheel built for python3.11 with > "installer" module >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:240: cd > /<>/.pybuild/cpython3_3.11_pytest-subtests/build; python3.11 -m > pytest tests > Traceback (most recent call last): > File "", line 198, in _run_module_as_main > File "", line 88, in _run_code > File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 5, in > > raise SystemExit(pytest.console_main()) > ^ > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 189, > in console_main > code = main() >^^ > File "/usr/lib/python3/dist-packages/_pytest/config/__
Processed: Bug#1042182 marked as pending in python-pytest-subtests
Processing control commands: > tag -1 pending Bug #1042182 [src:python-pytest-subtests] python-pytest-subtests: FTBFS: ModuleNotFoundError: No module named 'attr' Added tag(s) pending. -- 1042182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042182: marked as pending in python-pytest-subtests
Control: tag -1 pending Hello, Bug #1042182 in python-pytest-subtests 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-pytest-subtests/-/commit/5b022e2570101bce10bdb1cd5a9b0b7e63ce35d4 Add python3-attr to Build-Depends, required by tests (Closes: #1042182). (this message was generated automatically) -- Greetings https://bugs.debian.org/1042182
Bug#1041572: marked as done (gnome-shell-extension-freon: needs update for GNOME Shell 44)
Your message dated Fri, 01 Sep 2023 19:21:53 + with message-id and subject line Bug#1041572: fixed in gnome-shell-extension-freon 52+dfsg-2 has caused the Debian Bug report #1041572, regarding gnome-shell-extension-freon: needs update for GNOME Shell 44 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.) -- 1041572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041572 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-freon Version: 52+dfsg-1 Severity: important Tags: trixie sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-44 This extension has not been checked for compatibility with GNOME Shell 44. Depending how compatible it is, it will either need an update to its metadata.json and debian/control to declare compatibility with the new version, or code changes to adapt it to the new Shell version. If not updated, it will have to be removed from testing for the GNOME Shell 44 transition (I don't know when that will be). This bug will be raised to serious severity when the transition is ready to go ahead. If a new upstream version is compatible with Shell 44 but not 43, please upload to experimental for now. Thanks, smcv --- End Message --- --- Begin Message --- Source: gnome-shell-extension-freon Source-Version: 52+dfsg-2 Done: Matteo F. Vescovi We believe that the bug you reported is fixed in the latest version of gnome-shell-extension-freon, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matteo F. Vescovi (supplier of updated gnome-shell-extension-freon 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, 01 Sep 2023 20:38:28 +0200 Source: gnome-shell-extension-freon Architecture: source Version: 52+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Matteo F. Vescovi Closes: 1041572 Changes: gnome-shell-extension-freon (52+dfsg-2) unstable; urgency=medium . * debian/control: extend support to GNOME Shell 44 (Closes: #1041572) Checksums-Sha1: b137669c3e8f312fd5d32df61f54bc221d1a1441 2367 gnome-shell-extension-freon_52+dfsg-2.dsc fecdd5262220e65b8ab5d8bdbfb571ecf6b69815 4352 gnome-shell-extension-freon_52+dfsg-2.debian.tar.xz 9861f5aaa21e7906e6161d2b159feda3568bc5f8 6373 gnome-shell-extension-freon_52+dfsg-2_source.buildinfo Checksums-Sha256: c5706c1698be82ba5e3eb35f8ef4e0f813a842c78c1b4675600cc5ec560bbfad 2367 gnome-shell-extension-freon_52+dfsg-2.dsc 42652474bd243503b8b2a77370369e3f678c118c9b7e156ad22abf43daef489c 4352 gnome-shell-extension-freon_52+dfsg-2.debian.tar.xz c5b1a4d51c8db5139cd16fd4e56ccf77c1d50c0c3ff22299092805c20a9f1a4a 6373 gnome-shell-extension-freon_52+dfsg-2_source.buildinfo Files: c8dfcd81e1156f548838b10d60924265 2367 gnome optional gnome-shell-extension-freon_52+dfsg-2.dsc 54c34232a33b31dfecd69c2102083858 4352 gnome optional gnome-shell-extension-freon_52+dfsg-2.debian.tar.xz 81e68875f6411dc8189bbe70dcdc4015 6373 gnome optional gnome-shell-extension-freon_52+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Debian powered! iQKTBAEBCgB9FiEE890J+NqH0d9QRsmbBhL0lE7NzVoFAmTyMQxfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYz REQwOUY4REE4N0QxREY1MDQ2Qzk5QjA2MTJGNDk0NEVDRENENUEACgkQBhL0lE7N zVoLpg//c3bRv39o4MxbJGEY2hCc6e5u1HD32dHFM9j9/4ibrDueBphhi9BcqrIy fY0lCVcuFmZQ81Klm2A7yz9bskgKB9Rr2KZm/w0BaMHjuXWabVstvwlaBwFM6+Lx X0t+uYCW+V/r/iOJejoRMPSV9xkThvleXY0zzRDkCYpExgVyQ//HqB6Xa+PXA6Ou nTSrUm+QacQPGsjwPz8EeADnxERB/ZQOw1PEUKgQF1Z2sx5ALS1c2CVRkQERqA1z HIFGHXhwdU6aHZaYL9vZYwikbOloObg0uTDrXMjYGXx1swuUfBYu8CEwy4rHJHKv XTcA2z7Wc506qAARXnhqcxhsdUm4Lk4WDy/TA0oTLxgvfzJ+j7Jmx/Wgtco90LeW fmYSurQhGKFA9rZjF46lbVCsx859ltssqvR1R4furrLT/J/UCh7vpfmifpQ4yjW+ iTPpVBFF143Mc3SkqA7VNxyMzJNXqIRwGcJRYOV4JVdaheCAy4UpHttjvfwXCel5 c0a/d0QvoIILK6sQIEpGfbHYXa9dN9TVBVJVB3T+I12F9txT1Pvw8pf8/RcSu7sc TjL7vmYo0YV0LobRPJdFb91gxsgGHxXmqP7Z8w49beakBEEU7slwwNhkTWlmdL8T c2zDt82tuzuOe5MbCn2MYbAdl0RatrkwsPboXzuUIXzujI53wVo= =6XMc -END PGP SIGNATURE End Message ---
Bug#1037865: marked as done (spring: ftbfs with GCC-13)
Your message dated Fri, 01 Sep 2023 17:40:01 + with message-id and subject line Bug#1037865: fixed in spring 106.0+dfsg-2 has caused the Debian Bug report #1037865, regarding spring: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:spring Version: 106.0+dfsg-1 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/spring_106.0+dfsg-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] cd /<>/obj-x86_64-linux-gnu/rts/aGui && /usr/bin/c++ -DASIO_STANDALONE -DSPRING_DATADIR=\"/usr/share/games/spring:/usr/lib/spring\" -DSTREFLOP_SSE -DSYNCCHECK -DTHREADPOOL -D_GLIBCXX_USE_NANOSLEEP -D_RANDOM_TCC -I/<>/rts/lib/lua/include -I/<>/include/AL -I/<>/rts -I/usr/include/IL -I/<>/include/SDL2 -I/usr/include/SDL2 -I/<>/rts/lib/slimsig/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -fdiagnostics-color=auto -march=x86-64 -msse -mfpmath=sse -mno-sse2 -mno-sse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -mno-sse4 -mno-sse4a -mno-avx -mno-fma -mno-fma4 -mno-xop -mno-lwp -mno-avx2 -fsingle-precision-constant -frounding-math -mieee-fp -pipe -fno-strict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden -pthread -O2 -Wformat -Wformat-security -DNDEBUG -g -MD -MT rts/aGui/CMakeFiles/engineaGui.dir/V erticalLayout.cpp.o -MF CMakeFiles/engineaGui.dir/VerticalLayout.cpp.o.d -o CMakeFiles/engineaGui.dir/VerticalLayout.cpp.o -c /<>/rts/aGui/VerticalLayout.cpp In file included from /<>/rts/Rendering/GL/RenderDataBuffer.hpp:12, from /<>/rts/Rendering/Fonts/glFont.h:12, from /<>/rts/aGui/LineEdit.cpp:7: /<>/rts/Rendering/Shaders/Shader.h:16:32: warning: ‘template struct std::unary_function’ is deprecated [-Wdeprecated-declarations] 16 | struct fast_hash : public std::unary_function |^~ In file included from /usr/include/c++/13/string:49, from /<>/rts/aGui/LineEdit.h:6, from /<>/rts/aGui/LineEdit.cpp:3: /usr/include/c++/13/bits/stl_function.h:117:12: note: declared here 117 | struct unary_function |^~ [ 9%] Building CXX object rts/aGui/CMakeFiles/engineaGui.dir/Window.cpp.o cd /<>/obj-x86_64-linux-gnu/rts/aGui && /usr/bin/c++ -DASIO_STANDALONE -DSPRING_DATADIR=\"/usr/share/games/spring:/usr/lib/spring\" -DSTREFLOP_SSE -DSYNCCHECK -DTHREADPOOL -D_GLIBCXX_USE_NANOSLEEP -D_RANDOM_TCC -I/<>/rts/lib/lua/include -I/<>/include/AL -I/<>/rts -I/usr/include/IL -I/<>/include/SDL2 -I/usr/include/SDL2 -I/<>/rts/lib/slimsig/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -fdiagnostics-color=auto -march=x86-64 -msse -mfpmath=sse -mno-sse2 -mno-sse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -mno-sse4 -mno-sse4a -mno-avx -mno-fma -mno-fma4 -mno-xop -mno-lwp -mno-avx2 -fsingle-precision-constant -frounding-math -mieee-fp -pipe -fno-strict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden -pthread -O2 -Wformat -Wformat-security -DNDEBUG -g -MD -MT rts/aGui/CMakeFiles/engineaGui.dir/W indow.cpp.o -MF CMakeFiles/engineaGui.dir/Window.cpp.o.d -o CMakeFiles/engineaGui.dir/Window.cpp.o -c /<>/rts/aGui/Window.cpp
Bug#1041810: marked as done (librsvg: CVE-2023-38633)
Your message dated Fri, 01 Sep 2023 17:32:23 + with message-id and subject line Bug#1041810: fixed in librsvg 2.50.3+dfsg-1+deb11u1 has caused the Debian Bug report #1041810, regarding librsvg: CVE-2023-38633 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.) -- 1041810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041810 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: librsvg Version: 2.54.5+dfsg-3 Severity: important Tags: security upstream Forwarded: https://gitlab.gnome.org/GNOME/librsvg/-/issues/996 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for librsvg. CVE-2023-38633[0]: | A directory traversal problem in the URL decoder of librsvg before | 2.56.3 could be used by local or remote attackers to disclose files | (on the local filesystem outside of the expected area), as | demonstrated by href=".?../../../../../../../../../../etc/passwd" in | an xi:include element. 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-38633 https://www.cve.org/CVERecord?id=CVE-2023-38633 [1] https://gitlab.gnome.org/GNOME/librsvg/-/issues/996 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: librsvg Source-Version: 2.50.3+dfsg-1+deb11u1 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of librsvg, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated librsvg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 19 Aug 2023 23:25:46 BST Source: librsvg Architecture: source Version: 2.50.3+dfsg-1+deb11u1 Distribution: bullseye-security Urgency: high Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 1041810 Changes: librsvg (2.50.3+dfsg-1+deb11u1) bullseye-security; urgency=high . * Team upload * d/gbp.conf: Branch for bullseye * d/p/996-Fix-arbitrary-file-read-when-href-has-special-charact.patch: Add patch from upstream 2.50.8 to fix a directory traversal vulnerability (Closes: #1041810, CVE-2023-38633) * d/p/Fix-compilation-on-rustc-1.40.0.patch: Add patch from upstream 2.50.9 to fix a build regression in the fix for #1041810 * d/p/tests-Fix-build-with-older-Autotools.patch: Fix another build regression in the fix for #1041810 Checksums-Sha256: e53781567bc5b1bbc83c4c212e88315a4eb659790431e24c979269acd7c0b0b2 3033 librsvg_2.50.3+dfsg-1+deb11u1.dsc 959b744c95516d8aa90034c3f48fb8c519440e8633649f71fdb0e39306824667 33936 librsvg_2.50.3+dfsg-1+deb11u1.debian.tar.xz b2fc5196e8d7ed4ae85bc7667133bf71129af291d5ae4af42746effa09731282 11627 librsvg_2.50.3+dfsg-1+deb11u1_source.buildinfo 6aa4e614292de77c6b5fa1fd05d6c5d658d4bb9857f678b7b57d0865d5e50116 16290880 librsvg_2.50.3+dfsg.orig.tar.xz Checksums-Sha1: 0080c49c026d4bdf7d7d987ed28d6a8d85971941 3033 librsvg_2.50.3+dfsg-1+deb11u1.dsc 6db6e6054454d500077d61d992d9b0edcd31c8c1 33936 librsvg_2.50.3+dfsg-1+deb11u1.debian.tar.xz b54edacb04b5ce83dd4d96090514648f935a6d20 11627 librsvg_2.50.3+dfsg-1+deb11u1_source.buildinfo a5daf615ef09be4aeedc312cbb0e44f8c680da37 16290880 librsvg_2.50.3+dfsg.orig.tar.xz Files: 111a82280e7c3f2be7046d516400eee1 3033 libs optional librsvg_2.50.3+dfsg-1+deb11u1.dsc 6c31383fbb38a409ec5bda4638006062 33936 libs optional librsvg_2.50.3+dfsg-1+deb11u1.debian.tar.xz c3ea8345c627b45e8a3ad1c016b533d8 11627 libs optional librsvg_2.50.3+dfsg-1+deb11u1_source.buildinfo 55172cde181acf4dcc0595cd296bc58f 16290880 libs optional librsvg_2.50.3+dfsg.orig.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmThQaQACgkQ4FrhR4+B TE/HWw/9Fy3lmNCv+qZrQ9kOMSfJK0VJ/jzTf/WSJD+kDdHrp4HaTmQ9G3vJ+jLI mgE1jPPvDwgHrSWkjlb1HBWzRG9qu+LP/XL9bB7LpRRLdu/nsJVgQ/jn6PCgwcgJ djqLaGwrqzsyxkUHCZoCHj9ymYfktz2XIBLwWktpYM
Bug#1037213: Awstats bug #1037213 - is bug really fixed?
Hi Christian, I saw now that you adopted the awstats package and that you closed this bug (1037213). But I believe the bug is not resolved yet. It happens on bookworm. I have two bugs open right now to fix this. [1] Since you are the maintainer now, how do you want to resolve this issue? [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050384 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050591 signature.asc Description: This is a digitally signed message part.
Bug#1037865: marked as pending in spring
Control: tag -1 pending Hello, Bug #1037865 in spring 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/games-team/spring/-/commit/1767889af0ac90325f5a4014fe985d4431ce91fb Fix FTBFS with GCC 13. Closes: #1037865 (this message was generated automatically) -- Greetings https://bugs.debian.org/1037865
Processed: Bug#1037865 marked as pending in spring
Processing control commands: > tag -1 pending Bug #1037865 [src:spring] spring: ftbfs with GCC-13 Added tag(s) pending. -- 1037865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > block 1050591 by 1037213 Bug #1050591 [release.debian.org] bullseye-pu: package awstats/7.8-2+deb11u2 1050591 was blocked by: 1050384 1050591 was not blocking any bugs. Added blocking bug(s) of 1050591: 1037213 > block 1050384 by 1037213 Bug #1050384 [release.debian.org] bookworm-pu: package awstats/7.8-3+deb12u1 1050384 was not blocked by any bugs. 1050384 was blocking: 1050591 Added blocking bug(s) of 1050384: 1037213 > End of message, stopping processing here. Please contact me if you need assistance. -- 1050384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050384 1050591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999313: marked as done (log4net: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Fri, 01 Sep 2023 16:22:59 + with message-id and subject line Bug#999313: fixed in log4net 1.2.10+dfsg-9 has caused the Debian Bug report #999313, regarding log4net: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: log4net Version: 1.2.10+dfsg-8 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: log4net Source-Version: 1.2.10+dfsg-9 Done: Mirco Bauer We believe that the bug you reported is fixed in the latest version of log4net, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mirco Bauer (supplier of updated log4net package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Apr 2023 12:37:50 + Source: log4net Architecture: source Version: 1.2.10+dfsg-9 Distribution: unstable Urgency: medium Maintainer: Debian CLI Libraries Team Changed-By: Mirco Bauer Closes: 965701 999313 Changes: log4net (1.2.10+dfsg-9) unstable; urgency=medium . * add build-indep target (Closes: #999313) * bump debhelper compat to 13 (Closes: #965701) * bump cli-common-dev build-dep to >= 0.8~ * debian/copyright: refer to common Apache 2.0 license to fix lintian error * debian/docs: install Apache-2.0 notice file to fix lintian errors * debian/control: update Vcs-* fields for salsa to fix lintian warnings * debian/control: add myself to uploaders Checksums-Sha1: 0555612fe49da583f21ddc8a151c0f66f7d75608 2043 log4net_1.2.10+dfsg-9.dsc 4f3daa152bbbe1038986c5dfb7f9fcffd37820c7 4732 log4net_1.2.10+dfsg-9.debian.tar.xz b39b206364cc35a91a4182d0e76792014a8aed96 5430 log4net_1.2.10+dfsg-9_source.buildinfo Checksums-Sha256: 5f9bfa379fc2f799dd39db12f0d5c176249ae1462e051e7b95fa47255af86cc3 2043 log4net_1.2.10+dfsg-9.dsc 7704e9f8693485b7328c4a6c9d900181e5d8bae71aa37402af618856b7944087 4732 log4net_1.2.10+dfsg-9.debian.tar.xz 016a293eadb6f25aa13bd443c61e20daf2aa881a37c476b2e48f69db2a86d786 5430 log4net_1.2.10+dfsg-9_source.buildinfo Files: 577319fc38488e7e0c9c5beb8fd22039 2043 libs optional log4net_1.2.10+dfsg-9.dsc 02dd59bb31da39abdbc754aec67ef451 4732 libs optional log4net_1.2.10+dfsg-9.debian.tar.xz 0f414810e710d0b417124a94449f38c2 5430 libs optional log4net_1.2.10+dfsg-9_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTyCroQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFJXPC/wOmh5ku/9N9pOZ9/PdL0ggJc607hvaJf0+ Z6BAjaV/KlrW9wkASpfZ6BMRshKeDd9ALNFqxhggQg+SMD7vKCHrSFk6jbZDwN5Y i2NpqXTXpSIeWCX8D+bMJHn67q5CPtLYiq+XOEaClKjaxRs+UFCJhANtLOOHCZP7 Iz2rTiVDimECGYhbzmpTAApXxAblee7y57F+zqFmmRiiuimk1ctVwPQ72YBHSqWZ iDtVJdp7pn7rYxXJrkr/64G9oTDt7xP/YhTxjhobS1RWCPO0brNo6W4ToeY5L4UN kLzrOTuWqpFLhxwp9QoK0Dmx5yoKPBviuctwIzqzdhjO2psw9nS5fZ/N9wlZ03lx mEfRT7v6p8Vpm/+tPyCxQFWh7vAXqXmD0+tNeMKn35O3xhj0YClCwzURygJnDLmG AYbgtgI/DKVNsALXMEWD2ohx4efsmqxY4k4V1WopbWw1gCEGBDRYc07/5K+fJioC KZ5uR19ftdzyCt/50AHtZyOmeTGj4E8= =iQP2 -END PGP SIGNATURE End Message ---
Bug#965701: marked as done (log4net: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Fri, 01 Sep 2023 16:22:59 + with message-id and subject line Bug#965701: fixed in log4net 1.2.10+dfsg-9 has caused the Debian Bug report #965701, regarding log4net: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: log4net Version: 1.2.10+dfsg-7 Severity: normal Usertags: compat-5-6-removal Hi, The package log4net uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: log4net Source-Version: 1.2.10+dfsg-9 Done: Mirco Bauer We believe that the bug you reported is fixed in the latest version of log4net, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mirco Bauer (supplier of updated log4net package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Apr 2023 12:37:50 + Source: log4net Architecture: source Version: 1.2.10+dfsg-9 Distribution: unstable Urgency: medium Maintainer: Debian CLI Libraries Team Changed-By: Mirco Bauer Closes: 965701 999313 Changes: log4net (1.2.10+dfsg-9) unstable; urgency=medium . * add build-indep target (Closes: #999313) * bump debhelper compat to 13 (Closes: #965701) * bump cli-common-dev build-dep to >= 0.8~ * debian/copyright: refer to common Apache 2.0 license to fix lintian error * debian/docs: install Apache-2.0 notice file to fix lintian errors * debian/control: update Vcs-* fields for salsa to fix lintian warnings * debian/control: add myself to uploaders Checksums-Sha1: 0555612fe49da583f21ddc8a151c0f66f7d75608 2043 log4net_1.2.10+dfsg-9.dsc 4f3daa152bbbe1038986c5dfb7f9fcffd37820c7 4732 log4net_1.2.10+dfsg-9.debian.tar.xz b39b206364cc35a91a4182d0e76792014a8aed96 5430 log4net_1.2.10+dfsg-9_source.buildinfo Checksums-Sha256: 5f9bfa379fc2f799dd39db12f0d5c176249ae1462e051e7b95fa47255af86cc3 2043 log4net_1.2.10+dfsg-9.dsc 7704e9f8693485b7328c4a6c9d900181e5d8bae71aa37402af618856b7944087 4732 log4net_1.2.10+dfsg-9.debian.tar.xz 016a293eadb6f25aa13bd443c61e20daf2aa881a37c476b2e48f69db2a86d786 5430 log4net_1.2.10+dfsg-9_source.buildinfo Files: 577319fc38488e7e0c9c5beb8fd22039 2043 libs optional log4net_1.2.10+dfsg-9.dsc 02dd59bb31da39abdbc754aec67ef451 4732 libs optional log4net_1.2.10+dfsg-9.debian.tar.xz 0f414810e710d0b417124a94449f38c2 5430 libs optional log4net_1.2.10+dfsg-9_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTyCroQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFJXPC/wOmh5ku/9N9pOZ9/PdL0ggJc607hvaJf0+ Z6BAjaV/KlrW9wkASpfZ6BMRshKeDd9ALNFqxhggQg+SMD7vKCHrSFk6jbZDwN5Y i2NpqXTXpSIeWCX8D+bMJHn67q5CPtLYiq+XOEaClKjaxRs+UFCJhANtLOOHCZP7 Iz2rTiVDimECGYhbzmpTAApXxAblee7y57F+zqFmmRiiuimk1ctVwPQ72YBHSqWZ iDtVJdp7pn7rYxXJrkr/64G9oTDt7xP/YhTxjhobS1RWCPO0brNo6W4ToeY5L4UN kLzrOTuWqpFLhxwp9QoK0Dmx5yoKPBviuctwIzqzdhjO2psw9nS5fZ/N9wlZ03lx mEfRT7v6p8Vpm/+tPyCxQFWh7vAXqXmD0+tNeMKn35O3xhj0YClCwzURygJnDL
Bug#965701: log4net: Removal of obsolete debhelper compat 5 and 6 in bookworm
There is activity on the reverse dependency quickroute-linux, which is why I wanted to NMU this. I have seen Mirco's changes in git and am sponsoring them instead.
Bug#1049903: Acknowledgement (petsc: misbuild with gcc-13)
Hi Drew, Sorry, your message didn't go to 1049903-submit...@bugs.debian.org so I didn't receive it. > With patching, wouldn't it be simpler to just add -lstdc++ to > CXX_LINKER_FLAGS at configuration time (in debian/rules) rather than > hacking the upstream detection code? As you say, hardcoding in the > upstream scripts doesn't really resolve the underlying problem. Unfortunately, CXX_LINKER_FLAGS is the variable used to pass flags to the *C++ linker*. But what is being done here is invoking the *C linker* to link to C++ code. And if the code in question were being linked with the C++ linker, it wouldn't need an explicit -lstdc++ argument anyway. I tried every which way to get this to work via environment exports with no luck. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#997717: marked as done (golang-github-twstrike-gotk3adapter: FTBFS: src/github.com/gotk3/gotk3/gtk/accel.go:247:5: val.accel_flags undefined (type _Ctype_struct__GtkAccelKey has no field or method
Your message dated Fri, 01 Sep 2023 15:22:24 + with message-id and subject line Bug#1050861: Removed package(s) from unstable has caused the Debian Bug report #997717, regarding golang-github-twstrike-gotk3adapter: FTBFS: src/github.com/gotk3/gotk3/gtk/accel.go:247:5: val.accel_flags undefined (type _Ctype_struct__GtkAccelKey has no field or method accel_flags) 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.) -- 997717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-twstrike-gotk3adapter Version: 0.0~git20170505.0.901a95d+ds-3.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 > github.com/twstrike/gotk3adapter/gdk_mock > github.com/twstrike/gotk3adapter/gdka github.com/twstrike/gotk3adapter/gdki > github.com/twstrike/gotk3adapter/glib_mock > github.com/twstrike/gotk3adapter/gliba github.com/twstrike/gotk3adapter/glibi > github.com/twstrike/gotk3adapter/gtk_mock > github.com/twstrike/gotk3adapter/gtka github.com/twstrike/gotk3adapter/gtki > github.com/twstrike/gotk3adapter/pango_mock > github.com/twstrike/gotk3adapter/pangoa > github.com/twstrike/gotk3adapter/pangoi > internal/unsafeheader > github.com/twstrike/gotk3adapter/glibi > internal/abi > internal/cpu > internal/goexperiment > runtime/internal/atomic > github.com/twstrike/gotk3adapter/gdki > github.com/twstrike/gotk3adapter/glib_mock > internal/bytealg > runtime/internal/sys > internal/itoa > github.com/twstrike/gotk3adapter/gdk_mock > runtime/internal/math > math/bits > unicode/utf8 > internal/race > sync/atomic > math > unicode > runtime > github.com/twstrike/gotk3adapter/gtki > github.com/twstrike/gotk3adapter/pangoi > github.com/twstrike/gotk3adapter/pango_mock > github.com/twstrike/gotk3adapter/gtk_mock > internal/reflectlite > sync > internal/testlog > runtime/cgo > errors > sort > io > strconv > internal/oserror > syscall > path > reflect > time > internal/syscall/unix > internal/syscall/execenv > io/fs > internal/poll > internal/fmtsort > os > fmt > github.com/gotk3/gotk3/glib > # github.com/gotk3/gotk3/glib > cgo-gcc-prolog: In function ‘_cgo_734360ee47f5_Cfunc_g_binding_get_source’: > cgo-gcc-prolog:71:2: warning: ‘g_binding_get_source’ is deprecated: Use > 'g_binding_dup_source' instead [-Wdeprecated-declarations] > In file included from /usr/include/glib-2.0/glib-object.h:22, > from /usr/include/glib-2.0/gio/gioenums.h:28, > from /usr/include/glib-2.0/gio/giotypes.h:28, > from /usr/include/glib-2.0/gio/gio.h:26, > from src/github.com/gotk3/gotk3/glib/gbinding.go:4: > /usr/include/glib-2.0/gobject/gbinding.h:113:23: note: declared here > 113 | GObject * g_binding_get_source (GBinding > *binding); > | ^~~~ > cgo-gcc-prolog: In function ‘_cgo_734360ee47f5_Cfunc_g_binding_get_target’: > cgo-gcc-prolog:107:2: warning: ‘g_binding_get_target’ is deprecated: Use > 'g_binding_dup_target' instead [-Wdeprecated-declarations] > In file included from /usr/include/glib-2.0/glib-object.h:22, > from /usr/include/glib-2.0/gio/gioenums.h:28, > from /usr/include/glib-2.0/gio/giotypes.h:28, > from /usr/include/glib-2.0/gio/gio.h:26, > from src/github.com/gotk3/gotk3/glib/gbinding.go:4: > /usr/include/glib-2.0/gobject/gbinding.h:117:23: note: declared here > 117 | GObject * g_binding_get_target (GBinding > *binding); > | ^~~~ > github.com/twstrike/gotk3adapter/gliba > github.com/gotk3/gotk3/cairo > github.com/gotk3/gotk3/gdk > github.com/gotk3/gotk3/pango > github.com/twstrike/gotk3adapter/pangoa > # github.com/gotk3/gotk3/gdk > cgo-gcc-prolog: In function ‘_cgo_f31c63d07257_Cfunc_gdk_device_grab’: > cgo-gcc-prolog:285:2: warning: ‘gdk_device_grab’ is deprecated: Use > 'gdk_seat_grab' instead [-Wdeprecated-declarations] > In file included from /usr/include/gtk-3.0/gdk/gdkdnd.h
Processed: rm
Processing commands for cont...@bugs.debian.org: > severity 1049370 normal Bug #1049370 [src:zeitgeist-sharp] RM: zeitgeist-sharp -- RoQA; leaf package Severity set to 'normal' from 'serious' > reassign 1049370 ftp.debian.org Bug #1049370 [src:zeitgeist-sharp] RM: zeitgeist-sharp -- RoQA; leaf package Bug reassigned from package 'src:zeitgeist-sharp' to 'ftp.debian.org'. No longer marked as found in versions zeitgeist-sharp/0.8.0.0-5.1. Ignoring request to alter fixed versions of bug #1049370 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 1049370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967990: marked as done (mmorph: Removal of sys_nerr and sys_errlist)
Your message dated Fri, 01 Sep 2023 15:20:15 + with message-id and subject line Bug#1050816: Removed package(s) from unstable has caused the Debian Bug report #967990, regarding mmorph: Removal of sys_nerr and sys_errlist 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.) -- 967990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mmorph Version: 2.3.4.2-17 Severity: important Hello, Version 2.32 of glibc will not ship the sys_nerr and sys_errlist symbols any more. This package is using them, so will start FTBFS when we upload version 2.32 of glibc. Samuel --- End Message --- --- Begin Message --- Version: 2.3.4.2-17+rm Dear submitter, as the package mmorph has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1050816 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1016457: marked as done (clif: non-DFSG source code in clif)
Your message dated Fri, 01 Sep 2023 15:19:47 + with message-id and subject line Bug#1050811: Removed package(s) from unstable has caused the Debian Bug report #1016457, regarding clif: non-DFSG source code in clif 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.) -- 1016457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: clif Version: 0.90.2-1 Severity: serious Tags: upstream Justification: Policy 2.2.1 X-Debbugs-Cc: eribe...@debian.org The file ch-lex.c doesn't have a license on its header. However, starting at line 927, I noticed the following text: -- /* Copyright (c) 1989 AT&T */ /*All Rights Reserved */ /* THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT&T */ /* The copyright notice above does not evidence any*/ /* actual or intended publication of such source code. */ #pragma ident "@(#)ncform 6.8 95/02/11 SMI" -- It's clear to me that part of the file includes a non-free source code. Eriberto --- End Message --- --- Begin Message --- Version: 0.93-10+rm Dear submitter, as the package clif has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1050811 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#999992: marked as done (pike8.0: depends on obsolete pcre3 library)
Your message dated Fri, 01 Sep 2023 15:04:28 + with message-id and subject line Bug#92: fixed in pike8.0 8.0.1738-1.1 has caused the Debian Bug report #92, regarding pike8.0: depends on obsolete pcre3 library 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.) -- 92: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pike8.0 Severity: important User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian --- End Message --- --- Begin Message --- Source: pike8.0 Source-Version: 8.0.1738-1.1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of pike8.0, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated pike8.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 22 Aug 2023 11:50:42 + Source: pike8.0 Architecture: source Version: 8.0.1738-1.1 Distribution: unstable Urgency: medium Maintainer: Magnus Holmgren Changed-By: Bastian Germann Closes: 92 Changes: pike8.0 (8.0.1738-1.1) unstable; urgency=medium . * Non-maintainer upload. * Drop pike8.0-pcre (Closes: #92). Checksums-Sha1: 321a914b3e2fc7291b681bf45f944fdb73c0bdc8 3396 pike8.0_8.0.1738-1.1.dsc 80145e0c1ce4fa42058b9bde9a524c0a40ba9a95 37696 pike8.0_8.0.1738-1.1.debian.tar.xz 29f71f81cce0b1547575314270143574fb9d92a6 7192 pike8.0_8.0.1738-1.1_source.buildinfo Checksums-Sha256: a17bbc912acd962ff63a77d310b52d1ae5d43ed2bac2a8d2c1aa0a2a1bc3c9fd 3396 pike8.0_8.0.1738-1.1.dsc 3a057547eaa105695caa3d35940e08484fada93b1de2a8a90b3acb66c222ab31 37696 pike8.0_8.0.1738-1.1.debian.tar.xz 18c05249f8cce9b34dbe4e2f61ae763d80358f1f93a571321bdbedb6aa248e0b 7192 pike8.0_8.0.1738-1.1_source.buildinfo Files: 946c42d79a2af769c7ef47661e140ae1 3396 interpreters optional pike8.0_8.0.1738-1.1.dsc 82025e8ae11ed122b39815ecd5b31a04 37696 interpreters optional pike8.0_8.0.1738-1.1.debian.tar.xz 167f8605624984ec252c29291492bb9a 7192 interpreters optional pike8.0_8.0.1738-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTx+GgQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFJTAC/9xohGVoJtsJc3z2MP1+sod1F3jVhy6TZTG xsprWXi/WeScmitOXAiRpYUwjDAjGF/B2AxQKRXPyrkTVv06zuGsCj8Reck6YH8U 3gCawuGra+U9W7x6EaxMraqL+Qc799TNyLLTHPR/u/pDobV0ZbIzayEQIu8Adhw0 8nlG+ruUom6t9s1Rzl8KDjeSash+cJY2B31xSrXSnk7LRlg0/l1cSwkORnjCVBYu JBfyEjW5t5xskPvEtPSl91ytGR11Ttd+P3y4ZPFZhIkY4UIn71Vlvr8Oo5mU+NT9 /lYlagtZkPFnM56Vy70G1OCz7HN/r07K0rMEoGb3XC/uDuhBLl8xEaW7aOgzYk96 QY2mlVnqIsJH/aY3P6tk2z6DOI8xp+9JGtKmxmqFlNdX3Lh6RvrXr9hpoVsO1PhW puKK/Hy8I+nsOOCztwS5aXy9CXXuqm5a87VYI0BqURKbhxCtXeLcoCIZIYmTKZY3 VwbIVvhUPEArf4nCBTF6O3ugJ55c0Lo= =v5IK -END PGP SIGNATURE End Message ---
Bug#999992: pike8.0: depends on obsolete pcre3 library
On Tue, 22 Aug 2023 14:20:15 +0200 Bastian Germann wrote: Please find a patch enclosed with pike8.0-pcre dropped. I am uploading a NMU with the previously sent debdiff.
Bug#1031747: python-socks: autopkgtest regression
On Wed, 22 Feb 2023 00:45:20 +0200 Adrian Bunk wrote: > Source: python-socks > Version: 2.1.1-1 > Severity: serious > > https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-socks/31564223/log.gz > > ... > autopkgtest [18:13:28]: test unittests: [--- > === python3.11 === > ImportError while loading conftest '/tmp/autopkgtest- lxc.hgtwobwo/downtmp/autopkgtest_tmp/tests/conftest.py'. > tests/conftest.py:34: in > from tests.proxy_server import ProxyConfig, ProxyServer > tests/proxy_server.py:9: in > from tiny_proxy import ( > E ModuleNotFoundError: No module named 'tiny_proxy' > autopkgtest [18:13:29]: test unittests: ---] > autopkgtest [18:13:29]: test unittests: - - - - - - - - - - results - - - - - - - - - - > unittests FAIL non-zero exit status 4 > ... This failure can be solved by packaging tiny_proxy: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051025 I have the tested that locally. -- Benjamin Drung Debian & Ubuntu Developer
Bug#1051029: libinfinity: build-depends on old libgsasl7-dev
Source: libinfinity Version: 0.7.2-1 Severity: Serious tags: patch Hello, for some reasons, libgsasl7-dev was renamed in libgsasl-dev $ sed s/libgsasl7-dev/libgsasl-dev/g -i debian/control Should be enough to fix the issue. G. OpenPGP_signature Description: OpenPGP digital signature
Bug#1051031: libvmime: build-depends on old libgsasl7-dev
Source: libvmime Version: 0.9.8-8 Severity: Serious tags: patch Hello, for some reasons, libgsasl7-dev was renamed in libgsasl-dev $ sed s/libgsasl7-dev/libgsasl-dev/g -i debian/control Should be enough to fix the issue. G. OpenPGP_signature Description: OpenPGP digital signature
Bug#1040475: marked as done (apacheds: broken symlinks: /usr/share/apacheds/lib/*.jar -> ../../java/*.jar)
Your message dated Fri, 01 Sep 2023 12:19:12 + with message-id and subject line Bug#1040475: fixed in apache-directory-server 2.0.0~M26-3 has caused the Debian Bug report #1040475, regarding apacheds: broken symlinks: /usr/share/apacheds/lib/*.jar -> ../../java/*.jar 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.) -- 1040475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apacheds Version: 2.0.0~M26-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) broken symlinks: 0m57.3s ERROR: FAIL: Broken symlinks: /usr/share/apacheds/lib/apache-directory-api-all.jar -> ../../java/apache-directory-api-all.jar (apacheds) /usr/share/apacheds/lib/apacheds-jdbm1.jar -> ../../java/apacheds-jdbm1.jar (apacheds) /usr/share/apacheds/lib/bcprov.jar -> ../../java/bcprov.jar (apacheds) /usr/share/apacheds/lib/commons-lang.jar -> ../../java/commons-lang.jar (apacheds) /usr/share/apacheds/lib/commons-pool.jar -> ../../java/commons-pool.jar (apacheds) /usr/share/apacheds/lib/dom4j.jar -> ../../java/dom4j.jar (apacheds) /usr/share/apacheds/lib/mavibot.jar -> ../../java/mavibot.jar (apacheds) /usr/share/apacheds/lib/mina2-core.jar -> ../../java/mina2-core.jar (apacheds) /usr/share/apacheds/lib/slf4j-api.jar -> ../../java/slf4j-api.jar (apacheds) /usr/share/apacheds/lib/slf4j-log4j12.jar -> ../../java/slf4j-log4j12.jar (apacheds) /usr/share/apacheds/lib/xpp3.jar -> ../../java/xpp3.jar (apacheds) If these missing .jars cause the service to fail, please raise the severity and get this fixed in stable, too. cheers, Andreas --- End Message --- --- Begin Message --- Source: apache-directory-server Source-Version: 2.0.0~M26-3 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of apache-directory-server, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated apache-directory-server 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, 01 Sep 2023 13:10:15 +0200 Source: apache-directory-server Architecture: source Version: 2.0.0~M26-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Closes: 1040475 Changes: apache-directory-server (2.0.0~M26-3) unstable; urgency=medium . * Team upload. * Link caffeine.jar and commons-collections4.jar into apacheds lib directory. Fixes a startup failure. * apacheds.default: Set --add-opens java.base/sun.security.util=ALL-UNNAMED to fix IllegalAccessError with Java 17. (Closes: #1040475) Checksums-Sha1: 669abeefae77c91dac163bedbecaefec21d5e05e 2906 apache-directory-server_2.0.0~M26-3.dsc 72205a023b1609fe322f811222d6684ec7b92d89 12992 apache-directory-server_2.0.0~M26-3.debian.tar.xz 80c448493db9c2f9629b56250ff7ee6c8fdc3d18 16125 apache-directory-server_2.0.0~M26-3_amd64.buildinfo Checksums-Sha256: a77f8f8b5c0dc4812de18d06618f6e9bfdbca2b79028add4e70b2a453a72d769 2906 apache-directory-server_2.0.0~M26-3.dsc 268de2ab7623a663b706442556ae2002514c148c2cd0fa26b175dc0b1be0c259 12992 apache-directory-server_2.0.0~M26-3.debian.tar.xz 6083de472f7d45c4794d14f8ea196793ec20d7309f984cd719a885e41a84b07b 16125 apache-directory-server_2.0.0~M26-3_amd64.buildinfo Files: 18e438eab9654337abae803ea0109e73 2906 java optional apache-directory-server_2.0.0~M26-3.dsc e9b153c27df0289929de18c83c685fbf 12992 java optional apache-directory-server_2.0.0~M26-3.debian.tar.xz 03d30585c78e87c5c7936094cde4a27c 16125 java optional apache-directory-server_2.0.0~M26-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmTxzJZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HknnQQAMgC6MmlzeopW5neuiDRp0vUdzZo8QnSOoC3 x5ZrVq9XIJYC580VknjNLNfhUqhN8GEkwhopGenYxfawOd2Y
Processed: tagging 1050832
Processing commands for cont...@bugs.debian.org: > tags 1050832 + upstream fixed-upstream Bug #1050832 [python-xarray] sarsen: autopkgtest needs update for python-xarray 2023.08.0 Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1050832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1050832
Processing commands for cont...@bugs.debian.org: > affects 1050832 src:sarsen Bug #1050832 [python-xarray] sarsen: autopkgtest needs update for python-xarray 2023.08.0 Added indication that 1050832 affects src:sarsen > thanks Stopping processing here. Please contact me if you need assistance. -- 1050832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1050832
Processing commands for cont...@bugs.debian.org: > reassign 1050832 python-xarray 2023.08.0-1 Bug #1050832 [src:sarsen] sarsen: autopkgtest needs update for python-xarray 2023.08.0 Bug reassigned from package 'src:sarsen' to 'python-xarray'. No longer marked as found in versions sarsen/0.9.3+ds-2. Ignoring request to alter fixed versions of bug #1050832 to the same values previously set Bug #1050832 [python-xarray] sarsen: autopkgtest needs update for python-xarray 2023.08.0 There is no source info for the package 'python-xarray' at version '2023.08.0-1' with architecture '' Unable to make a source version for version '2023.08.0-1' Marked as found in versions 2023.08.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1050832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050832: sarsen: autopkgtest needs update for python-xarray 2023.08.0
Dear Graham, On Wed, 30 Aug 2023 08:08:49 + Graham Inggs wrote: Control: severity -1 serious Control: tags -1 + ftbfs As can be seen on reproducible builds [1], this same error causes sarsen to FTBFS in unstable. [1] https://tests.reproducible-builds.org/debian/rb-pkg/sarsen.html I think that this is a regression in xarray v2023.08.0. I have tested sarsen with the latest development version of xarray from git main, and it works correctly. Apparently the fix is in the PR #8094 (https://github.com/pydata/xarray/pull/8094) merged tree days ago. If it is OK for you I will re-assigning the issue to xarray. kind regards -- Antonio Valentino
Bug#1051017: cdo: Major data error with ICON files
Package: cdo Version: 2.2.1 Severity: serious Tags: upstream Justification: 2 X-Debbugs-Cc: Momtchil Momtchev Just a heads up that there is a serious issue with the cdo version in bookworm - it produces broken (flipped on the Y-axis) GRIBs when "remapping" (extracting) data from the ICON output files. The one in bullseye works correctly. As this is probably the number one reason commoners use cdo, it is a major showstopper. Here is the original bug report: https://code.mpimet.mpg.de/boards/1/topics/14808 The issue has been fixed in 2.2.2. -- System Information: Debian Release: 12.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-11-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cdo depends on: ii libc6 2.36-9+deb12u1 pn libcdi0 ii libcurl3-gnutls 7.88.1-10+deb12u1 ii libfftw3-double3 3.3.10-1 ii libgcc-s1 12.2.0-14 ii libgomp1 12.2.0-14 pn libhdf5-103-1 pn libmagplus3v5 pn libnetcdf19 pn libproj25 ii libstdc++612.2.0-14 pn libudunits2-0 Versions of packages cdo recommends: pn python3-cdo cdo suggests no packages.
Processed: retitle
Processing commands for cont...@bugs.debian.org: > retitle 1050784 debianutils: fails to reinstall Bug #1050784 [debianutils] debianutils: fails to reinstall / will fail to install 5.11 Changed Bug title to 'debianutils: fails to reinstall' from 'debianutils: fails to reinstall / will fail to install 5.11'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1050784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051006: smuxi: useless empty package
Package: smuxi Version: 1.1-1.2 Severity: grave Justification: renders package unusable The package doesn't have any dependencies and its only contents is: $ dpkg --contents smuxi_1.1-1.2_all.deb drwxr-xr-x root/root 0 2023-08-04 21:42 ./ drwxr-xr-x root/root 0 2023-08-04 21:42 ./usr/ drwxr-xr-x root/root 0 2023-08-04 21:42 ./usr/share/ drwxr-xr-x root/root 0 2023-08-04 21:42 ./usr/share/doc/ drwxr-xr-x root/root 0 2023-08-04 21:42 ./usr/share/doc/smuxi/ -rw-r--r-- root/root 2638 2021-02-12 13:03 ./usr/share/doc/smuxi/HACKING.md -rw-r--r-- root/root 1739 2021-02-12 13:34 ./usr/share/doc/smuxi/README.md -rw-r--r-- root/root 844 2023-08-04 21:42 ./usr/share/doc/smuxi/changelog.Debian.gz -rw-r--r-- root/root 4534 2023-07-21 17:57 ./usr/share/doc/smuxi/copyright -- Michał Politowski Talking has been known to lead to communication if practiced carelessly.
Bug#1051003: libgdbm6: trap divide error in libgdbm.so.6.0.0
Package: libgdbm6 Version: 1.23-3 Severity: critical Justification: breaks unrelated software Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? We are authenticating dovecot users via PAM. Our PAM-Setup includes pam_shield. pam_shield uses libgdbm6. As soon as pam_shield is triggered (meaning it blocks an IP) we get a trap divide error. Details see below * What exactly did you do (or not do) that was effective (or ineffective)? When removing pam_shield from our PAM-Setup the problem disappears * What was the outcome of this action? * What outcome did you expect instead? Just works. Journal-Output: Aug 31 18:02:34 xyz dovecot[2451]: auth: Error: auth-worker: Aborted PASSV request for x...@xyz.xyz: Worker process died unexpectedly Aug 31 18:02:34 xyz dovecot[2451]: auth-worker: Fatal: master: service(auth-worker): child 118182 killed with signal 8 Aug 31 18:02:34 xyz kernel: traps: auth[118182] trap divide error ip:7f7366d16f06 sp:7ffc44386580 error:0 in libgdbm.so.6.0.0[7f7366d12000+a000] PAM-Setup: auth required pam_abl.so config=/etc/security/pam_abl.conf auth sufficient pam_mysql.so list-of-options-remoed auth required pam_shield.so auth required pam_deny.so *** End of the template - remove these template lines *** -- System Information: Debian Release: 12.1 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'stable-security') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-11-cloud-amd64 (SMP w/6 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libgdbm6 depends on: ii libc6 2.36-9+deb12u1 libgdbm6 recommends no packages. Versions of packages libgdbm6 suggests: pn gdbm-l10n -- no debconf information
Processed: closing 1036806
Processing commands for cont...@bugs.debian.org: > close 1036806 Bug #1036806 [src:matrix-synapse] matrix-synapse: not suitable for inclusion in bookworm Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1036806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050998: Error while importing Python "lensfun" module
Package: python3-lensfun Version: 0.3.4-1 Severity: serious I just installed the package "python3-lensfun" on Debian testing. When trying to import the module, an error occurs: *> python3* Python 3.9.15 (main, Nov 21 2022, 16:07:38) [GCC 12.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import lensfun Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'lensfun' >>> The same error occurs when trying to launch the "lensfun-update-data" command line tool. *> dpkg --status python3-lensfun* Package: python3-lensfun Status: install ok installed Priority: optional Section: python Installed-Size: 58 Maintainer: Debian KDE Extras Team Architecture: amd64 Source: lensfun Version: 0.3.4-1 Depends: liblensfun1 (= 0.3.4-1), python3:any *> dpkg -L python3-lensfun* /. /usr /usr/lib /usr/lib/python3 /usr/lib/python3/dist-packages /usr/lib/python3/dist-packages/lensfun /usr/lib/python3/dist-packages/lensfun/__init__.py /usr/lib/python3/dist-packages/lensfun-0.3.4-py3.11.egg-info /usr/lib/python3/dist-packages/lensfun-0.3.4-py3.11.egg-info/PKG-INFO /usr/lib/python3/dist-packages/lensfun-0.3.4-py3.11.egg-info/dependency_links.txt /usr/lib/python3/dist-packages/lensfun-0.3.4-py3.11.egg-info/top_level.txt /usr/share /usr/share/doc /usr/share/doc/python3-lensfun /usr/share/doc/python3-lensfun/changelog.Debian.gz /usr/share/doc/python3-lensfun/changelog.gz /usr/share/doc/python3-lensfun/copyright
Bug#1039472: works
My bad, it worked.
Bug#1039472: Doesn't work
Hi, I tried installing ca-certificates-java 20230620~deb12u1 from bookworm proposed-updates, and I still have the same issue described in this bug. Can we have this fixed ?!? Cheers, Thomas Goirand (zigo)
Processed: Re: Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa
Processing control commands: > severity -1 normal Bug #1050991 [src:linux] FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa Severity set to 'normal' from 'serious' -- 1050991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050991: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa
Control: severity -1 normal On Fri, Sep 01, 2023 at 09:15:50AM +0200, Johannes Schauer Marin Rodrigues wrote: > Helmut informed me that bugs that break bootstrap (rebootstrap fails to > cross-build linux-libc-dev because of this bug) are usually filed with serious > severity, so doing that now. Thanks! Returning to normal, this is no normal build. Bastian -- If there are self-made purgatories, then we all have to live in them. -- Spock, "This Side of Paradise", stardate 3417.7
Bug#1041574: marked as done (gnome-shell-extension-hamster: needs update for GNOME Shell 44)
Your message dated Fri, 01 Sep 2023 07:19:32 + with message-id and subject line Bug#1041574: fixed in gnome-shell-extension-hamster 0.10.0+git20230901-1 has caused the Debian Bug report #1041574, regarding gnome-shell-extension-hamster: needs update for GNOME Shell 44 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.) -- 1041574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-hamster Version: 0.10.0+git20210628-4 Severity: important Tags: trixie sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-44 This extension has not been checked for compatibility with GNOME Shell 44. Depending how compatible it is, it will either need an update to its metadata.json and debian/control to declare compatibility with the new version, or code changes to adapt it to the new Shell version. If not updated, it will have to be removed from testing for the GNOME Shell 44 transition (I don't know when that will be). This bug will be raised to serious severity when the transition is ready to go ahead. If a new upstream version is compatible with Shell 44 but not 43, please upload to experimental for now. Thanks, smcv --- End Message --- --- Begin Message --- Source: gnome-shell-extension-hamster Source-Version: 0.10.0+git20230901-1 Done: Raphaël Hertzog We believe that the bug you reported is fixed in the latest version of gnome-shell-extension-hamster, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphaël Hertzog (supplier of updated gnome-shell-extension-hamster 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, 01 Sep 2023 08:43:28 +0200 Source: gnome-shell-extension-hamster Architecture: source Version: 0.10.0+git20230901-1 Distribution: unstable Urgency: medium Maintainer: Project Hamster Team Changed-By: Raphaël Hertzog Closes: 1041574 Changes: gnome-shell-extension-hamster (0.10.0+git20230901-1) unstable; urgency=medium . * New upstream git snapshot with GNOME Shell 44 compat. (Closes: #1041574) * Removes all patches. Checksums-Sha1: 2cd735b9ce1aafe4e4121957d1d58a96b5e00589 2022 gnome-shell-extension-hamster_0.10.0+git20230901-1.dsc f5c50c1f3eaf6953203a8cb1a2ea8861feedf42f 77553 gnome-shell-extension-hamster_0.10.0+git20230901.orig.tar.gz 6f36d7a0cc97ff0aa528eeb444a08056e2989ef8 2536 gnome-shell-extension-hamster_0.10.0+git20230901-1.debian.tar.xz b21c0cf5b336feed4976e453b27146c3b25c0f54 9085 gnome-shell-extension-hamster_0.10.0+git20230901-1_source.buildinfo Checksums-Sha256: a6fd2f4e40b2c55b8a41855b07a0b25c9909426805ad7a0ba4a6136c6f19860c 2022 gnome-shell-extension-hamster_0.10.0+git20230901-1.dsc 9c1f507a238050430a977bceac1c56057823d47f397fd21f64ab0cc6f07809b2 77553 gnome-shell-extension-hamster_0.10.0+git20230901.orig.tar.gz 253ccfe378a87ab6cb2e227a94e486a72747da5cb65a827a510fc7bb0a59fe72 2536 gnome-shell-extension-hamster_0.10.0+git20230901-1.debian.tar.xz 1747f9b6556e71394cc10954c5a619e62a1ec0c75df32aa14e0930e7eadad04a 9085 gnome-shell-extension-hamster_0.10.0+git20230901-1_source.buildinfo Files: 8dd48d2149a967a7393dff82ffc927a7 2022 gnome optional gnome-shell-extension-hamster_0.10.0+git20230901-1.dsc 65b76ff7200ef76ff76f937367158e96 77553 gnome optional gnome-shell-extension-hamster_0.10.0+git20230901.orig.tar.gz d9a1abdf6147bb426fae141d1f26ec7a 2536 gnome optional gnome-shell-extension-hamster_0.10.0+git20230901-1.debian.tar.xz f911a3e1ba1521717eec587f4fdbd684 9085 gnome optional gnome-shell-extension-hamster_0.10.0+git20230901-1_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Signed by Raphael Hertzog iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAmTxifkACgkQA4gdq+vC mrlWZQf+PJlD5L2mfWh5oSzolj5mgIzqX+BDDe2wegMxVvXMY13ckf+rZur1tTYv aPgEl4jMUG/EFrruh4fCbMhX5r7kBGMl/rkm/vDJb0HYT8YFCves5F0E6G2oLr2g kfSTGFc2veVSdw+sNbmXmelL5deJI0H087qa4hS17T8jcDlx2wwolvMLoIwOUzyR fTlI9UNrEnO/pltUNdqsEzCbOWAEkq0W0s8muEMhyr98GrHzN5ynh5KnZ8IGGQEo R/bK7wEr8L11k8+FQzIO0YEc6W4Nftjew0Nn+HO78WRA8BHx7r
Processed (with 2 errors): Re: FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa
Processing control commands: > severity -1 serious Bug #1050991 [src:linux] FTCBFS amd64 -> arm64 due to using host-arch flags for native builds and vice-versa Severity set to 'serious' from 'normal' > user debian-cr...@lists.debian.org Unknown command or malformed arguments to command. > usertag -1 + ftcbfs Unknown command or malformed arguments to command. -- 1050991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > fixed 1016903 12.2.0-8 Bug #1016903 [g++-12] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) Marked as fixed in versions gcc-12/12.2.0-8. > End of message, stopping processing here. Please contact me if you need assistance. -- 1016903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
