Bug#1032120: Upload of new upstream version before fix has migrated to testing (Was: Re: Bug#1032120: tiledb: uses atomic operations, but is not linked to libatomic)
Hi, I am removing myself from the uploaders field/maintenance of tiledb-py. Feel free to update it once tiledb is ready for migration. The repository lives at python team namespace. -- Best, Nilesh signature.asc Description: PGP signature
Bug#1032975: igdiscover -- Broken, unusable package due to incomplete code in the binary package
Package: igdiscover Version: 0.11-4 Severity: serious Usertags: ftbfs-bookworm Dear Maintainer, igdiscover vendors just a /usr/bin/igdiscover with is supposed to be nothing more than just a wrapper. The actual code is missing from the binary package (i.e. the python files) effectively making igdiscover useless. Even after fixing that, igdiscover is still broken because of a broken Snakefile and it is not able to run the pipeline/workflow which is the main functionality here (it is a workflow tool). Steps to check can be found here[1]. Remember to change merge tool to 'flash' (and apt-get install flash) before running `igdiscover run`. It chokes at not being able to find "igblastn" -- it might be originatin from ncbi-igblast. I've fixed the first part (py files installation) and pushed changes to salsa in a different branch here[2]. I do not have any more time to look into it. [1]: https://docs.igdiscover.se/en/stable/testing.html [2]: https://salsa.debian.org/med-team/igdiscover/-/tree/bookworm-release -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_IN, LC_CTYPE=en_IN (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 igdiscover depends on: ii python3 3.11.1-2 pn python3-cutadapt pn python3-matplotlib ii python3-numpy1:1.24.1-2+b1 pn python3-pandas pn python3-ruamel.yaml pn python3-scipy pn python3-seaborn pn python3-sqt pn python3-xopen igdiscover recommends no packages. Versions of packages igdiscover suggests: pn igdiscover-doc pn snakemake
Bug#997744: marked as done (pt-websocket: FTBFS: go install: version is required when current directory is not in a module)
Your message dated Wed, 15 Mar 2023 01:21:56 + with message-id and subject line Bug#1032893: Removed package(s) from unstable has caused the Debian Bug report #997744, regarding pt-websocket: FTBFS: go install: version is required when current directory is not in a module 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.) -- 997744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pt-websocket Version: 0.2-9 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): > make[1]: Entering directory '/<>' > cd obj-x86_64-linux-gnu && GOPATH=$PWD go install -v > git.torproject.org/pluggable-transports/websocket/websocket > git.torproject.org/pluggable-transports/websocket/pt-websocket-server > go install: version is required when current directory is not in a module > Try 'go install > git.torproject.org/pluggable-transports/websocket/websocket@latest > git.torproject.org/pluggable-transports/websocket/pt-websocket-server@latest' > to install the latest version > make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/pt-websocket_0.2-9_unstable.log 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 marking 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 --- Version: 0.2-9+rm Dear submitter, as the package pt-websocket 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/1032893 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#1020055: marked as done (tnetstring3: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit code 13)
Your message dated Wed, 15 Mar 2023 01:19:46 +
with message-id
and subject line Bug#1028349: Removed package(s) from unstable
has caused the Debian Bug report #1020055,
regarding tnetstring3: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.10 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.)
--
1020055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tnetstring3
Version: 0.3.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 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 --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated
> (level 9 in use)
> I: pybuild base:240: python3.10 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level
> 9 in use)
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10/build/tnetstring
> copying tnetstring/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/tnetstring
> running build_ext
> building '_tnetstring' extension
> creating build
> creating build/temp.linux-x86_64-cpython-310
> creating build/temp.linux-x86_64-cpython-310/tnetstring
> x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv
> -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g
> -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.10 -c
> tnetstring/_tnetstring.c -o
> build/temp.linux-x86_64-cpython-310/tnetstring/_tnetstring.o
> In file included from tnetstring/tns_core.c:9,
> from tnetstring/_tnetstring.c:16:
> tnetstring/tns_core.c: In function ‘tns_parse’:
> tnetstring/tns_core.c:56:50: warning: comparison of integer expressions of
> different signedness: ‘size_t’ {aka ‘long unsigned int’} and ‘int’
> [-Wsign-compare]
>56 | check(tns_strtosz(data, len, , ) != -1,
> | ^~
> tnetstring/dbg.h:12:31: note: in definition of macro ‘check’
>12 | #define check(A, M, ...) if(!(A)) { if(PyErr_Occurred() == NULL) {
> PyErr_Format(PyExc_ValueError, M, ##__VA_ARGS__); }; goto error; }
> | ^
> tnetstring/tns_core.c: In function ‘tns_outbuf_puts’:
> tnetstring/tns_core.c:444:36: warning: comparison of integer expressions of
> different signedness: ‘long int’ and ‘size_t’ {aka ‘long unsigned int’}
> [-Wsign-compare]
> 444 | if(outbuf->head - outbuf->buffer < len) {
> |^
> tnetstring/_tnetstring.c: In function ‘_tnetstring_load’:
> tnetstring/_tnetstring.c:153:51: warning: comparison of integer expressions
> of different signedness: ‘Py_ssize_t’ {aka ‘long int’} and ‘size_t’ {aka
> ‘long unsigned int’} [-Wsign-compare]
> 153 | if(!PyBytes_Check(res) || PyBytes_GET_SIZE(res) != datalen + 1) {
> | ^~
> x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -fwrapv -O2
> -Wl,-z,relro -Wl,-z,now -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2
> build/temp.linux-x86_64-cpython-310/tnetstring/_tnetstring.o
> -L/usr/lib/x86_64-linux-gnu -o
> /<>/.pybuild/cpython3_3.10/build/_tnetstring.cpython-310-x86_64-linux-gnu.so
>dh_auto_test -O--buildsystem=pybuild
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9
> in use)
> I: pybuild base:240: python3.10 setup.py test
> running test
> WARNING: Testing via this command is deprecated and will be removed in a
> future version. Users looking for a generic test entry point independent of
> test runner are encouraged to use tox.
> running egg_info
> writing tnetstring3.egg-info/PKG-INFO
> writing dependency_links to tnetstring3.egg-info/dependency_links.txt
> writing top-level names to tnetstring3.egg-info/top_level.txt
> reading manifest file
Processed: Re: Bug#1021662: libosip2: CVE-2022-41550
Processing control commands: > fixed -1 5.3.0-2.1 Bug #1021662 [src:libosip2] libosip2: CVE-2022-41550 The source 'libosip2' and version '5.3.0-2.1' do not appear to match any binary packages Marked as fixed in versions libosip2/5.3.0-2.1. -- 1021662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021662: libosip2: CVE-2022-41550
Control: fixed -1 5.3.0-2.1
I have just uploaded a NMU to fix this. debdiff attached.diff -Nru libosip2-5.3.0/debian/changelog libosip2-5.3.0/debian/changelog
--- libosip2-5.3.0/debian/changelog 2022-03-08 23:51:47.0 +0100
+++ libosip2-5.3.0/debian/changelog 2023-03-15 01:04:10.0 +0100
@@ -1,3 +1,10 @@
+libosip2 (5.3.0-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix CVE-2022-41550.
+
+ -- Bastian Germann Wed, 15 Mar 2023 01:04:10 +0100
+
libosip2 (5.3.0-2) unstable; urgency=medium
* enable testsuite
diff -Nru libosip2-5.3.0/debian/patches/CVE-2022-41550.patch
libosip2-5.3.0/debian/patches/CVE-2022-41550.patch
--- libosip2-5.3.0/debian/patches/CVE-2022-41550.patch 1970-01-01
01:00:00.0 +0100
+++ libosip2-5.3.0/debian/patches/CVE-2022-41550.patch 2023-03-15
01:04:10.0 +0100
@@ -0,0 +1,22 @@
+Origin: upstream, f77f16c832c3c37589c2b749f01b644dc44a55b5
+From: Aymeric Moizard
+Date: Tue, 27 Sep 2022 11:03:15 +0200
+Subject: [bug #63103] https://savannah.gnu.org/bugs/?63103 * in multipart
+ bodies, LWS can't exist
+
+---
+ src/osipparser2/osip_body.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/src/osipparser2/osip_body.c b/src/osipparser2/osip_body.c
+index 6490e4f..c28b831 100644
+--- a/src/osipparser2/osip_body.c
b/src/osipparser2/osip_body.c
+@@ -237,6 +237,7 @@ static int osip_body_parse_header(osip_body_t *body, const
char *start_of_osip_b
+ i = __osip_find_next_crlf(start_of_line, _of_line);
+
+ if (i == -2) {
++ return OSIP_SYNTAXERROR;
+ } else if (i != 0)
+ return i; /* error case: no end of body found */
+
diff -Nru libosip2-5.3.0/debian/patches/series
libosip2-5.3.0/debian/patches/series
--- libosip2-5.3.0/debian/patches/series1970-01-01 01:00:00.0
+0100
+++ libosip2-5.3.0/debian/patches/series2023-03-15 01:03:58.0
+0100
@@ -0,0 +1 @@
+CVE-2022-41550.patch
Bug#1032032: FTBFS: error: AM_INIT_AUTOMAKE expanded multiple times
Dear maintainers, the patch for fenix-plugins in my last e-mail was missing a line (copy'n'paste mistake). Sorry! Please find the updated patch attached to this e-mail. With this patch, I was able to successfully build fenix-plugins for armhf. Best regards, Thomas Uhle 04-update-configure-ac.patch.gz Description: GNU Zip compressed data
Bug#1032966: tzdata-legacy: file conflict with tzdata 2022g-7
Package: tzdata-legacy Version: 2022g-7exp1 Severity: serious There was an error installing your package: , | Unpacking tzdata-legacy (2022g-7exp1) ... | dpkg: error processing archive /var/cache/apt/archives/tzdata-legacy_2022g-7exp1_all.deb (--unpack): | trying to overwrite '/usr/share/zoneinfo/right/Africa/Abidjan', which is also in package tzdata 2022g-7 | Errors were encountered while processing: | /var/cache/apt/archives/tzdata-legacy_2022g-7exp1_all.deb ` After upgrading tzdata version 2022g-7exp1 the install succeeded, so the Breaks/Replaces on tzdata needs to be bumped. Unfortunately this problem will constantly reoccur with updates to tzdata in Bookworm. It seems to me that tzdata-legacy should actually have unversioned Replaces+Breaks (or Replaces+Conflicts) on tzdata-bookworm, and tzdata should stop providing tzdata-bookworm in uploads not targeted at Bookworm. -- System Information: Debian Release: 12.0 APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386
Bug#1032538: marked as done (emacs: CVE-2023-27985 CVE-2023-27986)
Your message dated Tue, 14 Mar 2023 21:19:49 + with message-id and subject line Bug#1032538: fixed in emacs 1:28.2+1-13 has caused the Debian Bug report #1032538, regarding emacs: CVE-2023-27985 CVE-2023-27986 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.) -- 1032538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: emacs Version: 1:28.2+1-11 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi No CVEs are yet assigned for the the following two issues: | emacsclient-mail.desktop is vulnerable to shell command | injections and Emacs Lisp injections through a crafted | mailto: URI. See: https://www.openwall.com/lists/oss-security/2023/03/08/2 Fixes: http://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-29=d32091199ae5de590a83f1542a01d75fba000467 http://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-29=3c1693d08b0a71d40a77e7b40c0ebc42dca2d2cc Those do not affect older versions in bullseye. Making it RC for bookworm and have a fix included before bookworm release. Regards, Salvatore --- End Message --- --- Begin Message --- Source: emacs Source-Version: 1:28.2+1-13 Done: Sean Whitton We believe that the bug you reported is fixed in the latest version of emacs, 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 1032...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (supplier of updated emacs 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, 14 Mar 2023 13:30:28 -0700 Source: emacs Architecture: source Version: 1:28.2+1-13 Distribution: unstable Urgency: high Maintainer: Rob Browning Changed-By: Sean Whitton Closes: 1032538 Changes: emacs (1:28.2+1-13) unstable; urgency=high . * Cherry-pick upstream fixes for command injection vulnerabilities (CVE-2023-27984, CVE-2023-27986) (Closes: #1032538). Checksums-Sha1: 5e06d903df52126f12a4f1ab6be9913c016c986b 2995 emacs_28.2+1-13.dsc 4ff4c5e1a63a0d5ef1a1a612d7d70e5ff70fa53c 121140 emacs_28.2+1-13.debian.tar.xz Checksums-Sha256: 6eed0c850fb9f463ac5249a69da0547b0ac98503d98d4b89ea5c5106dedc1ebc 2995 emacs_28.2+1-13.dsc b2a878c66b62b8601d2c7c1c7e8fb8c285fc0efc7723442e45a12ffd8df1da46 121140 emacs_28.2+1-13.debian.tar.xz Files: b11a8af4743b211e9e6e59c7a3ad1930 2995 editors optional emacs_28.2+1-13.dsc 8cc46222e6d95a09efc3a9af54ed07d1 121140 editors optional emacs_28.2+1-13.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmQQ4PYACgkQaVt65L8G YkB2yhAAhS3XMCAhawHN2yl8TKziJpzQgv7PctUp0a1o3dklwKwhrtccHIgSQ5yu OLfi8GjgnnKBEHEhRMPYWjlo9YZ/5m6egv5JJYOc8U7AsiI66jBP7GXOeTVAH/Ni SSoVrXtgDU+2vtN+G9imLUacnaukL0dTXOCq0JS3Oefsh9l2IC/ialfdVKNsKV2H /rionEmpJI931ly+1s47RbBTrIt8a4lo7YPgFuqWzW8PpzDetJZwUxbN2KotJgvz Gpgq6XB00fMOrfH7Sekl80Ceqx9CbzoROpVuMEXnoy0KQE3Zen4B5pbgmi9pphxy 1V2xfRYbTHUSmmJnvc+NAx7JhAppSyEyJk0hcH1lmDNmuvzTIPNVD40p6WvoR1wt HI8oXbGHc8EYAuH2xgTRP4kMsocxDFbnfCsz1AUB8rUZSLkR8Uja1BV+0mh9JqCf OPQXJkO8xMK1BQnOWj++bAqIddcj96JSPIVLZkjc8eC+9SoIl4eDj0z2XZCKsuo/ iVCMFudyUZXuwj03btD1fooCUxuvYERF9lRM1/rUodpyiE5NAK6OUcEwPPcDCllE 8YfvQkRPF4bVk6g1ZstVQvFLc9hncmifhaNwSq0KW+4hEh1Q2fNU2tldxxemCUEd W7IMrRut0did+/04gFQ1JnfAQAu38JWS/GKLkspRAANp+k2RhLw= =uT71 -END PGP SIGNATURE End Message ---
Bug#1031888: marked as done (emacs-nox: bullseye-security update fails to install on mips64el)
Your message dated Tue, 14 Mar 2023 14:04:19 -0700 with message-id <873567yrho@athena.silentflame.com> and subject line Re: Bug#1031888: emacs-nox: bullseye-security update fails to install on mips64el has caused the Debian Bug report #1031888, regarding emacs-nox: bullseye-security update fails to install on mips64el 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.) -- 1031888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: emacs Version: 1:27.1+1-3.1+deb11u2 Severity: grave Control: affects -1 + security.debian.org Control: affects -1 + release.debian.org X-Debbugs-Cc: t...@security.debian.org X-Debbugs-Cc: debian-ad...@lists.debian.org Hi, Upgrading emacs-nox on a bullseye mips64el system to the latest security update fails: Setting up emacs-nox (1:27.1+1-3.1+deb11u2) ... update-alternatives: using /usr/bin/emacs-nox to provide /usr/bin/emacs (emacs) in auto mode Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs emacs: could not load dump file "/usr/lib/emacs/27.1/mips64el-linux-gnuabi64/emacs.pdmp": out of memory ERROR: install script from emacsen-common package failed dpkg: error processing package emacs-nox (--configure): installed emacs-nox package post-installation script subprocess returned error exit status 1 Downgrading to +deb11u1 on the same system works fine. Removing the emacs packages and installing +deb11u2 directly fails in the same way. This is reproducible on four debian.org buildds. Regards, Adam --- End Message --- --- Begin Message --- Version: 1:28.2+1-11 Hello, On Sun 26 Feb 2023 at 09:41PM +02, Adrian Bunk wrote: > While I suspect they are the same, there is no proof that this leak is > actually the same as the mips64el installation issue. Looks like it was. -- Sean Whitton--- End Message ---
Processed: Re: Bug#1032468: file-roller: does not work - no error messages except on stderr (org.freedesktop.DBus.Error.ServiceUnknown)
Processing control commands: > severity -1 important Bug #1032468 [file-roller] file-roller: does not work - no error messages except on stderr (org.freedesktop.DBus.Error.ServiceUnknown) Severity set to 'important' from 'grave' > tags -1 + moreinfo unreproducible Bug #1032468 [file-roller] file-roller: does not work - no error messages except on stderr (org.freedesktop.DBus.Error.ServiceUnknown) Added tag(s) unreproducible and moreinfo. -- 1032468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032468: file-roller: does not work - no error messages except on stderr (org.freedesktop.DBus.Error.ServiceUnknown)
Control: severity -1 important Control: tags -1 + moreinfo unreproducible On Tue, 07 Mar 2023 at 17:00:57 +0100, Vincent Lefevre wrote: > Justification: renders package unusable It is not the case that file-roller is unusable. There must be something specific to the system where you reproduced this (and possibly other systems) that is not the same as in the environment where I tested. I tried to reproduce this in a virtual machine. In case the problem was the absence of GNOME, I didn't use GNOME, and in case the problem was a missing dependency, I didn't install Recommends. The base VM was the output of autopkgtest-build-qemu(1) for bookworm. This is not *completely* minimal: it has systemd-logind, among other things. For the test environment, I installed: * wget, with Recommends (to download the test file) * firefox-esr, file-roller, openbox, xdm and xorg, without Recommends and then rebooted and logged in. In an xterm in the openbox environment, after using wget to download the test file you named: `file-roller Math-MPFR-4.25.tar.gz` works as expected for me. `firefox-esr ./Math-MPFR-4.25.tar.gz`, followed by choosing "Archive Manager" to handle the file, also works as expected for me. > merged-usr: no This might possibly be relevant? Non-merged /usr is no longer a supported configuration for bookworm, except as a transitional state while upgrading from bullseye to bookworm. On Mon, 13 Mar 2023 at 01:32:59 +0100, Vincent Lefevre wrote: > Outside of Firefox, file-roller > appears to work, but it takes at least 25 seconds before the window > appears! This often indicates a D-Bus method call timing out. Running dbus-monitor --session in the same environment as file-roller will log the D-Bus method calls that are happening, which should give some indication of which specific call is timing out. Reading the system log (the systemd journal) might also provide useful information. Similarly, when launching file-roller from Firefox, using dbus-monitor and reading the system log should reveal more information about how and why it's failing to start. > BTW, I'm a bit surprised that this is related, as the file-roller > package does not depend on libdbus-1-3 (there's also no mention > of dbus in the description and the man page). Many desktop components use the D-Bus protocol to communicate. libdbus-1-3 is not the only commonly-used implementation of the D-Bus protocol (there are implementations in GLib and in libsystemd), and the fact that a component uses D-Bus is an implementation detail which wouldn't make sense to mention in a man page, in the same way that "is written in C++" wouldn't be relevant in a man page. In this particular case, "Failed to register: %s" seems likely to be coming from gio/gapplication.c in glib2.0. file-roller appears to have the single-instance design, where the first instance of file-roller that is run claims a D-Bus name, and the second and subsequent instances send messages to the first instance asking it to implement the desired UI. gapplication is one implementation of that design, and it might be the messages being exchanged between the instances that are timing out. "GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown" means the machine-readable part of the error message sent by the D-Bus implementation was that error code, which means: a message was sent to a D-Bus service that doesn't exist. ": org.freedesktop.DBus.Error.ServiceUnknown" means that the human-readable part of the error message was set equal to the machine-readable part. This is unusual. Normally, a ServiceUnknown error message would come from either dbus-daemon or dbus-broker, but when dbus-daemon produces those errors, it sets the human-readable part to something more human-readable, normally this: The name %s was not provided by any .service files ... and you say you don't have dbus-broker installed, so it can't be that either. So there must be something different going on here. Is there anything unusual about the way you installed Firefox or file-roller? (For instance if they are installed as Flatpak, Snap or AppImage apps, or running in some sort of sandbox, or running remotely?) What desktop environment are you using? Or if the answer is "a desktop environment that I made myself out of individual components", which components? Are you using dbus-daemon or dbus-broker or something else to provide the D-Bus session bus? Is there anything else unusual going on, for example involving containers or distributed systems? smcv
Bug#1032959: gobject-introspection: 1.76 fails to build on several architectures
Source: gobject-introspection Version: 1.76.0-1 Severity: serious Tags: trixie sid experimental ftbfs Control: forwarded -1 https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/458 gobject-introspection fails to build in experimental on several Debian release architectures. See the upstream bug. https://buildd.debian.org/status/package.php?p=gobject-introspection=experimental Thank you, Jeremy Bícha
Bug#1032929: marked as done (nginx-common: missing Breaks+Replaces: nginx (<< 1.22.1-8))
Your message dated Tue, 14 Mar 2023 16:19:18 + with message-id and subject line Bug#1032929: fixed in nginx 1.22.1-9 has caused the Debian Bug report #1032929, regarding nginx-common: missing Breaks+Replaces: nginx (<< 1.22.1-8) 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.) -- 1032929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nginx-common Version: 1.22.1-8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../nginx-common_1.22.1-8_all.deb ... Unpacking nginx-common (1.22.1-8) ... dpkg: error processing archive /var/cache/apt/archives/nginx-common_1.22.1-8_all.deb (--unpack): trying to overwrite '/etc/default/nginx', which is also in package nginx 1.22.1-7 Errors were encountered while processing: /var/cache/apt/archives/nginx-common_1.22.1-8_all.deb cheers, Andreas nginx=1.22.1-7_nginx-common=1.22.1-8.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: nginx Source-Version: 1.22.1-9 Done: Jan Mojžíš We believe that the bug you reported is fixed in the latest version of nginx, 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 1032...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jan Mojžíš (supplier of updated nginx 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, 14 Mar 2023 16:19:32 +0100 Source: nginx Architecture: source Version: 1.22.1-9 Distribution: unstable Urgency: medium Maintainer: Debian Nginx Maintainers Changed-By: Jan Mojžíš Closes: 1032929 Changes: nginx (1.22.1-9) unstable; urgency=medium . * d/control: nginx-common Breaks+Replaces: nginx (<< 1.22.1-8) (Closes: 1032929) Checksums-Sha1: 10742b0c8c8f1d89ce97e70a60658341dad233c8 3554 nginx_1.22.1-9.dsc dce0d43da5e59b5a96df61f06fcf68b5e94f0791 71780 nginx_1.22.1-9.debian.tar.xz 1c331294dc694828291baaf03faa0a239fca1f59 8235 nginx_1.22.1-9_source.buildinfo Checksums-Sha256: b6f68457c16e230f811d590f0854780550390747d49e76a017cc7818b4a0c478 3554 nginx_1.22.1-9.dsc 1b4c0ed0325bd35d39c781dca383fb91d6fcdd7ab3c7d9995bf78ad005430199 71780 nginx_1.22.1-9.debian.tar.xz 6c61b61838f13b11b2ff66f67b55d6b53e39c02da5a21665a0cac312d46efda5 8235 nginx_1.22.1-9_source.buildinfo Files: 7f4f522cb18d73ab3361a5c70e5c9cb1 3554 httpd optional nginx_1.22.1-9.dsc fe69629fa1527f6554b2284b48120de7 71780 httpd optional nginx_1.22.1-9.debian.tar.xz 30cf2de7f270beae6bb6f2a9323e00c9 8235 httpd optional nginx_1.22.1-9_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAzFiEE0Aiwwj2EeeRrn8uQRdpRdJaTn/kFAmQQklEVHGphbi5tb2p6 aXNAZ21haWwuY29tAAoJEEXaUXSWk5/5qcEP+NF+DUvSHEQLKVeTWOIwaAjdhuAe hwgbh5W5TsLW+BePViv/u3VPdqAi7ZymymoZVN/Ltrzm+hzbEMBA1ibJ5R6sWFLk fXx7z3wArzz9CWT/sqNG7ZYXQbcFX0pCwDGJeYTcnEYxlQ5jv6ST0lEcjKYtBSwg r72IzeLfD761Cu7YftOFPoRYv2YcTFJ1lfILTxL1DJCTVvOb8/541FVT/cDHUVYE qzXqIW+vtVpy0FrcZ8A+oA2/QGg0O8jPn7XafN+rR+EzXGXxAA1MdcrIZPtO9lb8 PYjMiWBVkX18pz7xTGbutm1+f7+1HHBsTQZAYx7YtZYHzBtPOszrDo8/q1xS6iXv IKUXYYQ3v5XIjGgqwLWH45i0UI1zn7rAqDVgKd29uegDq2kvd8Evyzfmge/tTAAT 7DPrZvy0t6flJwjzLI2Zc9XF7l3+E8vCcsfSdRzhYDBNapEfycu20cEpZeO8PKsR BH7FnlHNWJB3R1QGWKSaYs0HUiF4WSAYceUayqVlr1/af9lxPvPi4qCvOrQah++b b88ishUO3uQYCA6LrIvLbrbAoANMKHBK63b/84caaoLq61PwLowNFkg8b+QOIL/R sbGWDXOQAco3hG9si2R7rk51Rgm7gVMG3QBosr7t72q7raz65rxwqSyuzrusfhcp L8rb6fAnIROzZdU= =KbFz -END PGP SIGNATURE End Message ---
Processed: Re: breaks upgrades if systemd-resolved can't run
Processing control commands: > severity -1 wishlist Bug #1032937 [systemd-resolved] systemd-resolved: Overwriting /etc/resolv.conf with link to /run/systemd/resolve/stub-resolv.conf breaks install in chroot Severity set to 'wishlist' from 'serious' > tags -1 wontfix Bug #1032937 [systemd-resolved] systemd-resolved: Overwriting /etc/resolv.conf with link to /run/systemd/resolve/stub-resolv.conf breaks install in chroot Added tag(s) wontfix. -- 1032937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032937: breaks upgrades if systemd-resolved can't run
Control: severity -1 wishlist Control: tags -1 wontfix On Tue, 14 Mar 2023 15:05:20 +0100 Bastian Blank wrote: > Control: severity -1 serious > > Let's make this RC, as it breaks updates. > > The systemd-resolved package modifies a global config file > /etc/resolv.conf. This breaks any name resolution if resolved is not > running. Especially if it can't run at all. > > | root@debian-sid:~# ls -al /etc/resolv.conf > | lrwxrwxrwx 1 root root 40 Mar 14 14:03 /etc/resolv.conf -> /../run/systemd/resolve/stub-resolv.conf > | root@debian-sid:~# getent hosts heise.de > | 2a02:2e0:3fe:1001:302:: heise.de > | root@debian-sid:~# systemctl stop systemd-resolved > | root@debian-sid:~# getent hosts heise.de > | root@debian-sid:~# > > Sorry, but the only person to know if resolved can be used is the admin, > not a package. Exactly, so the admin shouldn't install a package that in the description says: "Installing this package automatically overwrites /etc/resolv.conf and switches it to be managed by systemd-resolved." if that's not what they want to achieve. I agree that the /etc/resolv.conf interface is garbage, but there's nothing we can do about it, that's just how it works. This is the only way read-only images can be supported sanely. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Processed: Re: errors during upgrade
Processing control commands: > block -1 by 1031909 Bug #960727 [python3-distutils] errors during upgrade 960727 was not blocked by any bugs. 960727 was not blocking any bugs. Added blocking bug(s) of 960727: 1031909 -- 960727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: breaks upgrades if systemd-resolved can't run
Processing control commands: > severity -1 serious Bug #1032937 [systemd-resolved] systemd-resolved: Overwriting /etc/resolv.conf with link to /run/systemd/resolve/stub-resolv.conf breaks install in chroot Severity set to 'serious' from 'important' -- 1032937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 1009035 in 0.4.0-1
Processing commands for cont...@bugs.debian.org: > fixed 1009035 0.4.0-1 Bug #1009035 [src:ruby-asciidoctor-include-ext] ruby-asciidoctor-include-ext: CVE-2022-24803 - Command Injection vulnerability Marked as fixed in versions ruby-asciidoctor-include-ext/0.4.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031965: marked as done (python3-pyodc-docs is empty)
Your message dated Tue, 14 Mar 2023 12:04:14 + with message-id and subject line Bug#1031965: fixed in pyodc 1.1.4-1 has caused the Debian Bug report #1031965, regarding python3-pyodc-docs is empty 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.) -- 1031965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pyodc-docs Version: 1.1.2-1 Severity: serious /. /usr /usr/share /usr/share/doc /usr/share/doc/python3-pyodc-docs /usr/share/doc/python3-pyodc-docs/changelog.Debian.gz /usr/share/doc/python3-pyodc-docs/changelog.gz /usr/share/doc/python3-pyodc-docs/copyright --- End Message --- --- Begin Message --- Source: pyodc Source-Version: 1.1.4-1 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of pyodc, 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 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated pyodc 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, 4 Mar 2023 01:09:28 + Source: pyodc Architecture: source Version: 1.1.4-1 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1031965 Changes: pyodc (1.1.4-1) unstable; urgency=medium . * New upstream release. * Build-dep on pandoc, Closes: #1031965 * Standards-Version: 4.6.1 * Rename docs file to correct name * Ship symlinks to common js files * Mark -docs pkg as M-A: foreign * Patch to use pre-downloaded objects.inv file Checksums-Sha1: 169b7f0aebdf337b83cb8909141f753b2e3da516 2092 pyodc_1.1.4-1.dsc 0bdb2344ff2489d7861c1683ae0807bc41c80002 56784 pyodc_1.1.4.orig.tar.xz adb9e5ceb5f91e591c75fab1e9e5c4b999bb4a9f 3788 pyodc_1.1.4-1.debian.tar.xz Checksums-Sha256: 01c41035df75042070f485423852a3d89ec3b8f9380911dd4499f678282a60aa 2092 pyodc_1.1.4-1.dsc fbc3ce3a0c1c81ac85a747e11767c385e5baad662e6846a3fb28ec2fa3e1e7b0 56784 pyodc_1.1.4.orig.tar.xz 466f0d23419277a51026f0dd293c58ef484b6cae6336ab93d7bc04c0914ce3fd 3788 pyodc_1.1.4-1.debian.tar.xz Files: 9a5f9b08cf722436bcda15c12be59b48 2092 python optional pyodc_1.1.4-1.dsc 0ef6144117568cd334b7bc7a77d36e84 56784 python optional pyodc_1.1.4.orig.tar.xz 9e1ff1bea4485d972c323fcdf6fe5107 3788 python optional pyodc_1.1.4-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmQQULMACgkQy+a7Tl2a 06VRuhAAoC8M/IKK616l1HpoKKr3jX4mbUnx9kKTnE5YapR5UmdIhFefElg9pNOP PT0y23iGD4tvE9gScFy+DPXQCH0G8ECkfCyrsrINQ/RbrthYddvJjbAABhAIRyoZ CqpJE47Z8ms6az4jbyLyOgXdZKHLxNm4KsBHZdWIMtisjE1qczjJV85DoFO9VgNp +P1rTrdQOnSXY+gknv48bReVyOVIu9of61yHWlEhcEwPx0M5OXF8/soLYbeE+8Sy nTsZ7rOWWmRgR/GzT5CcXahETNEXaogukp8sVbOdttQYNTaIb04PjWDvJfEpKffn RX0J6UIsLfbcG4yy6mh5g0MRS61OHfsZpM0DToM6ur6DvhOwx0rrHBbp37hWy4iX eAj/X8rwlsXJsTM2/TRqizMpWShUbklqbJfzf+aLJj+2x2bcSp2aDYpnTVlFkhhZ Z63pokTlRYJU2jFPmcJbrc7ytIVNIZqc6XyDqt+XnRUMb2d6XuhrIPEEe36Q5dZ0 TH87ae8uqIm4dg7j41vysXUwAWNq5FgCv6pr9XhlW1nwxVs3T4KdnqH2DZPpfUeH a2637C+tVkke1P3pNqbxXMyw+P+4BOrQCVNZ/O2IQK2U5gP9H6/8zqWg2pPevWzb XzcEEgQloNqcS5E9nUiuMCq09F42hUKq7ZDNwA/pkTHg/KiukQs= =ZO/T -END PGP SIGNATURE End Message ---
Processed: git-updates.diff not applied ?
Processing control commands:
> reopen -1
Bug #1016903 {Done: Matthias Klose } [g++-12] tree-vectorize:
Wrong code at O2 level (-fno-tree-vectorize is working)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 12.2.0-2.
--
1016903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1016903: git-updates.diff not applied ?
Control: reopen -1 > the upstream fix went into 12.2.0-2. Would be so kind as to demonstrate how ? Here is what I see on my side: % ssh barriere.debian.org % sessionid=$(schroot -b -c sid_i386-dchroot) % dd-schroot-cmd -c $sessionid apt-get update % dd-schroot-cmd -c $sessionid apt-get upgrade % dd-schroot-cmd -c $sessionid apt-get build-dep gcc-12 % dget -u http://deb.debian.org/debian/pool/main/g/gcc-12/gcc-12_12.2.0-14.dsc % schroot -r -c $sessionid Then a simple check within the sid schroot: % cd gcc-12-12.2.0 % grep -r "use emulated vector type for call" . ./debian/patches/git-updates.diff:+ "use emulated vector type for call\n"); % grep -r git-updates . ./debian/rules.patch:# git-updates \ So yes I can see PR106322 patch in file "git-updates.diff". But it looks as if it is never applied to the source tree. To reproduce the issue, just use the test from gcc-testsuite: % wget -O pr106322.c "https://gcc.gnu.org/git/?p=gcc.git;a=blob_plain;f=gcc/testsuite/gcc.target/i386/pr106322.c;h=31333c5fdccbe02ce7cf5055ce852edc0da1af67;hb=9f532fec01d6651cc3cc136073f044a7953d8560; % gcc -O2 pr106322.c && ./a.out zsh: IOT instruction ./a.out Compared with: % /usr/lib/gcc-snapshot/bin/gcc -O2 pr106322.c && ./a.out && echo "success" success Per discussion with gcc-upstream: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322#c54 [...] OK. Thanks for the update! FWIW, with the reduced test case in comment #45, I just tried with releases/gcc-12 r12-8709 (without my fix), the aborting was reproduced; while with r12-8710 (my fix), it executed well. [...]
Processed: Re: libgpuarray: i386 test fail with new pocl
Processing control commands: > severity -1 normal Bug #1031414 [src:pocl,src:libgpuarray] libgpuarray: i386 test fail with new pocl Severity set to 'normal' from 'serious' -- 1031414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031414: libgpuarray: i386 test fail with new pocl
Followup-For: Bug #1031414 Control: severity -1 normal This should have been addressed in pyopencl. Andreas
Bug#1032930: pynest2d: FTBFS with cmake 3.25: Libnest2D could not be found because dependency clipper could not be found.
Source: pynest2d Version: 5.0.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, pynest2d/experimental started to FTBFS after some (transitive) build-dependency has been upgraded. Most likely this is caused by cmake 3.25 (the last successful build was done with cmake 3.23). This does not affect the version in sid since that does not seem to check for clipper. https://buildd.debian.org/status/fetch.php?pkg=pynest2d=amd64=5.0.0-1%2Bb1=1675641711=0 dh_auto_configure -a -O--buildsystem=pybuild I: pybuild base:240: dh_auto_configure --buildsystem=cmake --builddirectory=/<>/.pybuild/cpython3_3.11/build -- -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python3.11 -DPYTHON_LIBRARY:FILEPATH=/usr/lib/python3.11/config-3.11-x86_64-linux-gnu/libpython3.11.so -DPYTHON_INCLUDE_DIR:PATH=/usr/include/python3.11 -DPython_EXECUTABLE=/usr/bin/python3.11 -DPython_LIBRARY=/usr/lib/python3.11/config-3.11-x86_64-linux-gnu/libpython3.11.so -DPython_INCLUDE_DIR=/usr/include/python3.11 -DPython3_EXECUTABLE=/usr/bin/python3.11 -DPython3_LIBRARY=/usr/lib/python3.11/config-3.11-x86_64-linux-gnu/libpython3.11.so -DPython3_INCLUDE_DIR=/usr/include/python3.11 -DPYVER=3.11 cd .pybuild/cpython3_3.11/build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DPYTHON_EXECUTABLE:FILEPATH=/usr/bin/python3.11 -DPYTHON_LIBRARY:FILEPATH=/usr/lib/python3.11/config-3.11-x86_64-linux-gnu/libpython3.11.so -DPYTHON_INCLUDE_DIR:PATH=/usr/include/python3.11 -DPython_EXECUTABLE=/usr/bin/python3.11 -DPython_LIBRARY=/usr/lib/python3.11/config-3.11-x86_64-linux-gnu/libpython3.11.so -DPython_INCLUDE_DIR=/usr/include/python3.11 -DPython3_EXECUTABLE=/usr/bin/python3.11 -DPython3_LIBRARY=/usr/lib/python3.11/config-3.11-x86_64-linux-gnu/libpython3.11.so -DPython3_INCLUDE_DIR=/usr/include/python3.11 -DPYVER=3.11 ../../.. -- The C compiler identification is GNU 12.2.0 -- The CXX compiler identification is GNU 12.2.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Setting BUILD_SHARED_LIBS to ON -- Generating compile commands to /<>/.pybuild/cpython3_3.11/build/compile_commands.json -- Setting POSITION_INDEPENDENT_CODE: ON -- Setting C++17 support with extensions off and standard required -- Setting Python version to 3.11. Set Python_VERSION if you want to compile against an other version. -- Found Python: /usr/bin/python3.11 (found suitable exact version "3.11.1") found components: Interpreter Development Development.Module Development.Embed -- Linking and building against Python 3.11.1 -- Found SIP version: 6.7.6 -- Using dependent package: Threads -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success -- Found Threads: TRUE -- Using dependent package: Boost -- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake (found version "1.74.0") -- Using dependent package: clipper CMake Warning (dev) at /usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:438 (message): The package name passed to `find_package_handle_standard_args` (Clipper) does not match the name of the calling package (clipper). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): /usr/lib/cmake/Libnest2D/Findclipper.cmake:67 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) /usr/share/cmake-3.25/Modules/CMakeFindDependencyMacro.cmake:47 (find_package) /usr/lib/cmake/Libnest2D/Libnest2DConfig.cmake:20 (find_dependency) CMakeLists.txt:33 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Found Clipper: /usr/include/polyclipping CMake Error at CMakeLists.txt:33 (find_package): Found package configuration file: /usr/lib/cmake/Libnest2D/Libnest2DConfig.cmake but it set Libnest2D_FOUND to FALSE so package "Libnest2D" is considered to be NOT FOUND. Reason given by package: Libnest2D could not be found because dependency clipper could not be found. -- Configuring incomplete, errors occurred! Andreas
Bug#1016903: closing again
Version: 12.2.0-2 the upstream fix went into 12.2.0-2. If the problem persists, then there's probably another issue. Please file a separate issue, after testing both gcc-12 and gcc-13 from experimental.
Bug#1016903: marked as done (tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working))
Your message dated Tue, 14 Mar 2023 10:47:07 +0100 with message-id and subject line closing again has caused the Debian Bug report #1016903, regarding tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) 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.) -- 1016903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: g++-12 Version: 12.1.0-7 Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 Affects: src:highway I am getting some odd behavior for unit test of highway. I believe there is some wrong-code generation using g++ + -O2 (tree-vectorize is default now). --- End Message --- --- Begin Message --- Version: 12.2.0-2 the upstream fix went into 12.2.0-2. If the problem persists, then there's probably another issue. Please file a separate issue, after testing both gcc-12 and gcc-13 from experimental.--- End Message ---
Bug#1032929: nginx-common: missing Breaks+Replaces: nginx (<< 1.22.1-8)
Package: nginx-common Version: 1.22.1-8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../nginx-common_1.22.1-8_all.deb ... Unpacking nginx-common (1.22.1-8) ... dpkg: error processing archive /var/cache/apt/archives/nginx-common_1.22.1-8_all.deb (--unpack): trying to overwrite '/etc/default/nginx', which is also in package nginx 1.22.1-7 Errors were encountered while processing: /var/cache/apt/archives/nginx-common_1.22.1-8_all.deb cheers, Andreas nginx=1.22.1-7_nginx-common=1.22.1-8.log.gz Description: application/gzip
Bug#1032517: marked as done (nginx settings deleted on upgrade)
Your message dated Tue, 14 Mar 2023 07:04:05 + with message-id and subject line Bug#1032517: fixed in nginx 1.22.1-8 has caused the Debian Bug report #1032517, regarding nginx settings deleted on upgrade 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.) -- 1032517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nginx Version: 1.22.1-7 Severity: grave Justification: causes non-serious data loss Dear Maintainer, last weekend I did an "apt upgrade" of my system as usual, asking apt to prune configuration files for packages that are being uninstalled. Now I realize that my nginx stopped working, and it turns out its configuration files are just completely gone. Look like the recent package reorganization went wrong and actually deletes configuration under certain conditions -- that's pretty bad. Package updates shouldn't cause a loss of configuration files, even when pruning packages that are not present any more. Kind regards, Ralf -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-5-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 nginx depends on: ii debconf [debconf-2.0] 1.5.82 ii iproute2 6.1.0-1 ii libc6 2.36-8 ii libcrypt1 1:4.4.33-2 ii libpcre2-8-0 10.42-1 ii libssl33.0.8-1 ii zlib1g 1:1.2.13.dfsg-1 nginx recommends no packages. Versions of packages nginx suggests: ii fcgiwrap 1.1.0-14 pn nginx-doc ii ssl-cert 1.1.2 -- Configuration Files: /etc/nginx/fastcgi.conf [Errno 2] No such file or directory: '/etc/nginx/fastcgi.conf' /etc/nginx/fastcgi_params [Errno 2] No such file or directory: '/etc/nginx/fastcgi_params' /etc/nginx/koi-utf [Errno 2] No such file or directory: '/etc/nginx/koi-utf' /etc/nginx/koi-win [Errno 2] No such file or directory: '/etc/nginx/koi-win' /etc/nginx/mime.types [Errno 2] No such file or directory: '/etc/nginx/mime.types' /etc/nginx/nginx.conf [Errno 2] No such file or directory: '/etc/nginx/nginx.conf' /etc/nginx/proxy_params [Errno 2] No such file or directory: '/etc/nginx/proxy_params' /etc/nginx/scgi_params [Errno 2] No such file or directory: '/etc/nginx/scgi_params' /etc/nginx/sites-available/default [Errno 2] No such file or directory: '/etc/nginx/sites-available/default' /etc/nginx/snippets/fastcgi-php.conf [Errno 2] No such file or directory: '/etc/nginx/snippets/fastcgi-php.conf' /etc/nginx/snippets/snakeoil.conf [Errno 2] No such file or directory: '/etc/nginx/snippets/snakeoil.conf' /etc/nginx/uwsgi_params [Errno 2] No such file or directory: '/etc/nginx/uwsgi_params' /etc/nginx/win-utf [Errno 2] No such file or directory: '/etc/nginx/win-utf' -- debconf information: nginx/log-symlinks: --- End Message --- --- Begin Message --- Source: nginx Source-Version: 1.22.1-8 Done: Jan Mojžíš We believe that the bug you reported is fixed in the latest version of nginx, 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 1032...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jan Mojžíš (supplier of updated nginx 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, 14 Mar 2023 06:53:32 +0100 Source: nginx Architecture: source Version: 1.22.1-8 Distribution: unstable Urgency: medium Maintainer: Debian Nginx Maintainers Changed-By: Jan Mojžíš Closes: 1032517 Changes: nginx (1.22.1-8) unstable; urgency=medium . * Main change: Configuration files returned to nginx-common package. This fixes the serious problem of losing configuration files during upgrade. This is a rollback of a change made in 1.22.1-6 (Closes: 1032517) * d/control: fix nginx-full
Bug#1010541: marked as done (git-sizer: FTBFS on ppc64el)
Your message dated Tue, 14 Mar 2023 06:49:00 + with message-id and subject line Bug#1010541: fixed in git-sizer 1.5.0-3 has caused the Debian Bug report #1010541, regarding git-sizer: FTBFS on ppc64el 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.) -- 1010541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: git-sizer Version: 1.5.0-1 Severity: serious Tags: ftbfs sid bookworm 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=git-sizer=ppc64el=1.5.0-1%2Bb1=1651440393=0 --- PASS: TestNontrivialPipeline (0.05s) === CONT TestBigEPIPE pipeline_test.go:327: Error Trace:pipeline_test.go:327 Error: An error is expected but got nil. Test: TestBigEPIPE --- FAIL: TestBigEPIPE (0.05s) --- PASS: TestPipelineWithFunction (0.05s) --- PASS: TestPipelineReadFromSlowly (0.30s) --- PASS: TestPipelineReadFromSlowly2 (0.63s) --- PASS: TestLittleEPIPE (1.01s) FAIL FAILgithub.com/github/git-sizer/internal/pipe 1.016s ? github.com/github/git-sizer/internal/refopts[no test files] ? github.com/github/git-sizer/internal/testutils [no test files] ? github.com/github/git-sizer/isatty [no test files] ? github.com/github/git-sizer/meter [no test files] ? github.com/github/git-sizer/sizes [no test files] FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/github/git-sizer github.com/github/git-sizer/counts github.com/github/git-sizer/git github.com/github/git-sizer/internal/pipe github.com/github/git-sizer/internal/refopts github.com/github/git-sizer/internal/testutils github.com/github/git-sizer/isatty github.com/github/git-sizer/meter github.com/github/git-sizer/sizes returned exit code 1 make[1]: *** [debian/rules:12: override_dh_auto_test] Error 25 make[1]: Leaving directory '/<>' Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: git-sizer Source-Version: 1.5.0-3 Done: Shengjing Zhu We believe that the bug you reported is fixed in the latest version of git-sizer, 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 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shengjing Zhu (supplier of updated git-sizer 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: Tue, 14 Mar 2023 13:53:21 +0800 Source: git-sizer Architecture: source Version: 1.5.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Shengjing Zhu Closes: 1009690 1010541 Changes: git-sizer (1.5.0-3) unstable; urgency=medium . * Team upload * Add patch to increase pipe buffer in tests (Really closes: #1009690, #1010541) Checksums-Sha1: bca950833a62e22b4e0873fbbeb2de84e75767c0 1566 git-sizer_1.5.0-3.dsc f96cdc1bfeb382ed3c55ebe8891cc55bfe3ffc95 3884 git-sizer_1.5.0-3.debian.tar.xz 106cb5d994a359fd2666d417449a506dcede840b 6322 git-sizer_1.5.0-3_amd64.buildinfo Checksums-Sha256: bcb0ee2d0debac62fdaa40f8fa0a8b98bb5557f114de53962ce3c9273010a9b0 1566 git-sizer_1.5.0-3.dsc 6798643bc5872735e5dafcf0d247d4368a0deef79ed9988a834c49573564eecc 3884 git-sizer_1.5.0-3.debian.tar.xz a5e8ec5d20d938e5d91afdd276d93010ce38641c6fe807d2e4dd3036ca6916f9 6322 git-sizer_1.5.0-3_amd64.buildinfo Files: d99e7d60f1511d0557f1360f15d53918 1566 vcs optional git-sizer_1.5.0-3.dsc 3f0364fd20814f462d82597585a9dbcb 3884 vcs optional git-sizer_1.5.0-3.debian.tar.xz 895399e8a7e48deacc3a0a76bed19ee5 6322 vcs optional git-sizer_1.5.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSRhdT1d2eu7mxV1B5/RPol6lUUywUCZBAVyAAKCRB/RPol6lUU y7ivAPwJRcFfLnWnS+GTYnkfEtSBmslocmhjGsK4bUCMQb5cTwD/XZzoIgzl2sbL XdVdW4w+q8rJPXCWXM/4+BBXKnnuMwI= =uMGd -END PGP SIGNATURE End Message ---
Bug#1009690: marked as done (git-sizer: autopkgtest regression on ppc64el: An error is expected but got nil.)
Your message dated Tue, 14 Mar 2023 06:49:00 + with message-id and subject line Bug#1009690: fixed in git-sizer 1.5.0-3 has caused the Debian Bug report #1009690, regarding git-sizer: autopkgtest regression on ppc64el: An error is expected but got nil. 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.) -- 1009690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: git-sizer Version: 1.5.0-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of git-sizer the autopkgtest of git-sizer fails on ppc64el in testing when that autopkgtest is run with the binary packages of git-sizer from unstable. It passes when run with only packages from testing. In tabular form: passfail git-sizer from testing1.5.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=git-sizer https://ci.debian.net/data/autopkgtest/testing/ppc64el/g/git-sizer/20831344/log.gz === CONT TestLittleEPIPE === CONT TestBigEPIPE pipeline_test.go:327: Error Trace:pipeline_test.go:327 Error: An error is expected but got nil. Test: TestBigEPIPE --- FAIL: TestBigEPIPE (0.03s) === CONT TestPipelineCanceled --- PASS: TestPipelineWithFunction (0.03s) === CONT TestPipelineInterrupted --- PASS: TestIgnoredSIGPIPE (0.04s) === CONT TestPipelineStderr --- PASS: TestPipelineCanceled (0.01s) === CONT TestPipelineExit --- PASS: TestPipelineStderr (0.01s) === CONT TestPipelineDir --- PASS: TestPipelineDir (0.01s) === CONT TestPipelineTwoCommandsPiping --- PASS: TestPipelineInterrupted (0.02s) === CONT TestPipelineReadFromSlowly2 --- PASS: TestPipelineExit (0.02s) === CONT TestPipelineReadFromSlowly --- PASS: TestPipelineTwoCommandsPiping (0.01s) === CONT TestNontrivialPipeline --- PASS: TestNontrivialPipeline (0.01s) === CONT TestPipelineSingleCommandWithStdout --- PASS: TestPipelineSingleCommandWithStdout (0.01s) === CONT TestPipelineSingleCommandOutput --- PASS: TestPipelineSingleCommandOutput (0.01s) === CONT TestPipelineSecondStageFailsToStart --- PASS: TestPipelineSecondStageFailsToStart (0.00s) === CONT TestErrors/pipe-then-error-then-finish-early === CONT TestErrors/error-then-pipe-then-finish-early === CONT TestErrors/finish-early-then-pipe === CONT TestErrors/pipe-then-finish-early-with-gap === CONT TestErrors/two-pipe-then-finish-early === CONT TestErrors/pipe-then-two-finish-early === CONT TestErrors/pipe-then-finish-early === CONT TestErrors/error-after-finish-early === CONT TestErrors/error-before-finish-early === CONT TestErrors/finish-early-ignored === CONT TestErrors/two-spaced-errors === CONT TestErrors/error-then-pipe === CONT TestErrors/pipe-then-error === CONT TestErrors/two-consecutive-errors === CONT TestErrors/error === CONT TestErrors/lonely-error --- PASS: TestErrors (0.00s) --- PASS: TestErrors/no-error (0.00s) --- PASS: TestErrors/pipe-then-error-then-finish-early (0.00s) --- PASS: TestErrors/error-then-pipe-then-finish-early (0.00s) --- PASS: TestErrors/finish-early-then-pipe (0.00s) --- PASS: TestErrors/pipe-then-finish-early-with-gap (0.00s) --- PASS: TestErrors/two-pipe-then-finish-early (0.00s) --- PASS: TestErrors/pipe-then-two-finish-early (0.00s) --- PASS: TestErrors/pipe-then-finish-early (0.00s) --- PASS: TestErrors/error-after-finish-early (0.00s) --- PASS: TestErrors/error-before-finish-early (0.00s) --- PASS: TestErrors/finish-early-ignored (0.00s) --- PASS: TestErrors/two-spaced-errors (0.00s) --- PASS: TestErrors/error-then-pipe (0.00s) --- PASS: TestErrors/pipe-then-error (0.00s) --- PASS: TestErrors/two-consecutive-errors (0.00s) --- PASS: TestErrors/error (0.00s) --- PASS: TestErrors/lonely-error (0.00s) --- PASS: TestPipelineReadFromSlowly (0.30s) --- PASS: TestPipelineReadFromSlowly2 (0.69s) --- PASS: TestLittleEPIPE (1.02s) FAIL FAILgithub.com/github/git-sizer/internal/pipe 1.042s ? github.com/github/git-sizer/internal/refopts[no test files] ?
