Processed: Bug#1024066 marked as pending in geventhttpclient
Processing control commands: > tag -1 pending Bug #1024066 [src:geventhttpclient] geventhttpclient FTBFS with Python 3.11 as supported version Added tag(s) pending. -- 1024066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024066: marked as pending in geventhttpclient
Control: tag -1 pending Hello, Bug #1024066 in geventhttpclient 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/geventhttpclient/-/commit/c4af8794265c3dcce20ebc25e61cd181b8c2096c New upstream release; Closes: #1024066 (this message was generated automatically) -- Greetings https://bugs.debian.org/1024066
Bug#1025835: marked as done (tiledb-py: build-depends on libtiledb-doc)
Your message dated Sun, 11 Dec 2022 05:50:46 + with message-id and subject line Bug#1025835: fixed in tiledb-py 0.19.0-1 has caused the Debian Bug report #1025835, regarding tiledb-py: build-depends on libtiledb-doc 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.) -- 1025835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tiledb-py Version: 0.18.2-1 Severity: serious Justification: rc policy - "Packages must be buildable within the same release" x-debbugs-cc: e...@debian.org User: debian...@lists.debian.org Usertags: edos-uninstallable tiledb-py build-depends on libtiledb-doc, which is no longer built by tiledb since version 2.13.0-1, this removal is no mentioned in the changelog, so it's not clear to me if it was deliberate or not. It is still present in unsable as a cruft package, but is completely gone from testing. This means that tiledb-py in testing is in violation of the rc policy. --- End Message --- --- Begin Message --- Source: tiledb-py Source-Version: 0.19.0-1 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of tiledb-py, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated tiledb-py 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: Sun, 11 Dec 2022 10:38:36 +0530 Source: tiledb-py Architecture: source Version: 0.19.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Nilesh Patra Closes: 1025835 Changes: tiledb-py (0.19.0-1) unstable; urgency=medium . * New upstream version 0.19.0 * Drop doc package, which was never rendering fine anyway (Closes: #1025835) * Remove superfluous string_view.hpp copyright mention which is no longer in source Checksums-Sha1: 12363d57d3eddf9930a44d5aec58a8f700166ef5 1934 tiledb-py_0.19.0-1.dsc 46ee3a7c007736064cc9316b8342086e0d020457 333069 tiledb-py_0.19.0.orig.tar.gz a03dd686e5919d95d580650c407ca61bda6ce8f4 5116 tiledb-py_0.19.0-1.debian.tar.xz 8c2e8b09c1d01d1a513a45eabb3e111b62365a48 9027 tiledb-py_0.19.0-1_amd64.buildinfo Checksums-Sha256: 3c448a97a993f41b515822fc63a2221213494ac29243ea00a40b7bdd0dbe29f0 1934 tiledb-py_0.19.0-1.dsc f100896ab95459018b5295c25273e0a1deaf933b89af63603a6e9202af69f12c 333069 tiledb-py_0.19.0.orig.tar.gz cd8939a62d73d4fae5ccc7b827ea3e3efb9b2991c4a287b00198b1faf0fedc9f 5116 tiledb-py_0.19.0-1.debian.tar.xz fdf2dd408aa44d14d374336e8c9aaf079f3c083e09514f32888d18fa26581169 9027 tiledb-py_0.19.0-1_amd64.buildinfo Files: c84a8ddb7d2cf9074e518305dc1a3e8b 1934 python optional tiledb-py_0.19.0-1.dsc a46f692f6ed0cd3774720a091dab8a61 333069 python optional tiledb-py_0.19.0.orig.tar.gz 437647d2f250dafeea79f737766ac01f 5116 python optional tiledb-py_0.19.0-1.debian.tar.xz d2be7dc8b52eca363f529564c59ac310 9027 python optional tiledb-py_0.19.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCY5VuCAAKCRAqJ5BL1yQ+ 2txPAP0RIrM/DwMolj6ZVOubsbhhsUjGB4+HfS665aG97Qk7gQEAo+dScDl0sVcP U7aehBBgxg1NnaGl31B26r2dg5b+TAo= =KjhJ -END PGP SIGNATURE End Message ---
Bug#1025835: marked as pending in tiledb-py
Control: tag -1 pending Hello, Bug #1025835 in tiledb-py 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/tiledb-py/-/commit/3ebd90b5a585801bc52d4a3bb1a54e72e95faa6a Drop doc package, which was never rendering fine anyway (Closes: #1025835) (this message was generated automatically) -- Greetings https://bugs.debian.org/1025835
Processed: Bug#1025835 marked as pending in tiledb-py
Processing control commands: > tag -1 pending Bug #1025835 [src:tiledb-py] tiledb-py: build-depends on libtiledb-doc Added tag(s) pending. -- 1025835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025739: Is an autogenerated configure shell script non-editable source
On Sat, 2022-12-10 at 10:28 +0100, Andreas Tille wrote: > So far for the actual case (bug report in CC). > > For the general case I somehow understand the consensus here on the list > that a missing configure.ac can be considered a bug but the severity > serious is not really rectified. If I understood this correctly I would > reset the severity to important at the beginning of next week. Personally I feel that severity serious is the correct one, but it sounds like the fix for the bug is quite simple: https://lists.debian.org/msgid-search/y5rir8qidvj4r...@argenau.bebt.de -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1025878: libkeduvocdocument-data: missing Breaks+Replaces: libkeduvocdocument5 (<< 4:22.11.90-2)
Package: libkeduvocdocument-data Version: 4:22.11.90-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install 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 .../libkeduvocdocument-data_4%3a22.11.90-2_all.deb ... Unpacking libkeduvocdocument-data (4:22.11.90-2) ... dpkg: error processing archive /var/cache/apt/archives/libkeduvocdocument-data_4%3a22.11.90-2_all.deb (--unpack): trying to overwrite '/usr/share/locale/ar/LC_MESSAGES/libkeduvocdocument.mo', which is also in package libkeduvocdocument5:amd64 4:21.12.3-1 Errors were encountered while processing: /var/cache/apt/archives/libkeduvocdocument-data_4%3a22.11.90-2_all.deb There are already Breaks+Replaces: libkeduvocdocument5 (<< 4:21.12.3) but that versioning is insufficient to catch all package versions predating the package split. cheers, Andreas libkeduvocdocument5=4:21.12.3-1_libkeduvocdocument-data=4:22.11.90-2.log.gz Description: application/gzip
Bug#1025876: elpa-snakemake: fails to install with emacs 28: misses 'snakemake-mode'
Package: elpa-snakemake Version: 2.0.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): ... Setting up elpa-snakemake (2.0.0-2) ... Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install elpa-snakemake for emacs install/snakemake-2.0.0: Handling install of emacsen flavor emacs install/snakemake-2.0.0: byte-compiling for emacs In toplevel form: snakemake.el:96:1: Error: Cannot open load file: No such file or directory, snakemake-mode ERROR: install script from elpa-snakemake package failed dpkg: error processing package elpa-snakemake (--configure): installed elpa-snakemake package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: elpa-snakemake ... cheers, Andreas elpa-snakemake=2.0.0-2_emacs.log.gz Description: application/gzip
Bug#1025322: marked as done (pylint: FTBFS with Python 3.11 as a supported version)
Your message dated Sun, 11 Dec 2022 03:15:56 + with message-id and subject line Bug#1025322: fixed in pylint 2.15.8-1 has caused the Debian Bug report #1025322, regarding pylint: FTBFS with Python 3.11 as a supported version 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.) -- 1025322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pylint Version: 2.15.5-1 Severity: serious Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.11 Hi Maintainer As can be seen on reproducible builds [1], pylint FTBFS due to tests timing out with Python 3.11 as a supported version. I've copied the tail of the build log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/pylint.html dh_auto_test -O--buildsystem=pybuild I: pybuild pybuild:300: rm -f /build/1st/pylint-2.15.5/tests/functional/u/unused_typing_imports.py /build/1st/pylint-2.15.5/tests/functional/m/missing_final_newline.py I: pybuild base:240: cd /build/1st/pylint-2.15.5/.pybuild/cpython3_3.11/build; python3.11 -m pytest -k 'not test_pkginfo and not test_do_not_import_files_from_local_directory and not test_import_plugin_from_local_directory_if_pythonpath_cwd and not test_can_list_directories_without_dunder_init and not test_fail_on_exit_code and not test__test_environ_pythonpath_no_arg' = test session starts == platform linux -- Python 3.11.0+, pytest-7.1.2, pluggy-1.0.0+repack benchmark: 3.2.2 (defaults: timer=time.perf_counter disable_gc=False min_rounds=5 min_time=0.05 max_time=1.0 calibration_precision=10 warmup=False warmup_iterations=10) rootdir: /build/1st/pylint-2.15.5, configfile: setup.cfg plugins: benchmark-3.2.2 collected 2047 items / 15 deselected / 2032 selected tests/test_check_parallel.py F..F.FMon Nov 21 18:20:40 UTC 2022 - pbuilder was killed by timeout after 18h. Mon Nov 21 18:20:42 UTC 2022 I: https://tests.reproducible-builds.org/debian/unstable/amd64/pylint : reproducible ➤ timeout --- End Message --- --- Begin Message --- Source: pylint Source-Version: 2.15.8-1 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of pylint, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated pylint 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, 10 Dec 2022 20:35:42 -0500 Source: pylint Architecture: source Version: 2.15.8-1 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Closes: 1025322 Changes: pylint (2.15.8-1) unstable; urgency=medium . * New upstream release * debian/control - bump astroid b-d to >= 2.12.13 - bump dill b-d to >= 0.3.6, needed for tests to pass with python 3.11; Closes: #1025322 - bump Standards-Version to 4.6.1.0 (no changes needed) * debian/NEWS, debian/NEWS.Debian - remove NEWS, very ancient * debian/copyright - extend packaging copyright years Checksums-Sha1: 252997d8a9b5f8635342286aef01d1d7476df607 2412 pylint_2.15.8-1.dsc 17c7b8bb94e51d08238c1ed03f8a5bb50ee0884c 976260 pylint_2.15.8.orig.tar.xz 49019995db82088f37632c413a904e9f827985f3 24076 pylint_2.15.8-1.debian.tar.xz 112ff02fe6f43ea25ed1a60c4aeb559bb2d70a7f 9371 pylint_2.15.8-1_source.buildinfo Checksums-Sha256: 9ef525295b85bac12b762435afd11733e033a3f9a95188a742350dde1eb39818 2412 pylint_2.15.8-1.dsc 8ec0ae4dbfb39ad5b1c2846d4d0b38706412dc1afc30f3218a599e5d71a365ed 976260 pylint_2.15.8.orig.tar.xz 1fde6d45d27f01e1fe3e52128dd78536fc24be21fba33009b960a89343d5846a 24076 pylint_2.15.8-1.debian.tar.xz b2947ef959341da4b2c8b313cd0959073619b68a54991f10d6efc065fb5415fe 9371 pylint_2.15.8-1_source.buildinfo Files: 85b1b6e45de3cf259828394ccfe1b26d 2412 python optional pylint_2.15.8-1.dsc 896e03f74aec8461530d2c32f4c42733 976260 python optional pylint_2.15.8.orig.tar.xz fbe11ce837ed50a33bd32fb5acf1880e 24076 python optional pylint_2.15.8-1.debian.tar.xz 7e7dbf2d07ecf74043dc
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 984038 +patch Bug #984038 [src:drawtiming] drawtiming: ftbfs with GCC-11 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 984038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984038: [PATCH] drawtiming : ftbfs with GCC-11
Someone (Thomas Sailer) offered upstream a patch that resolves the
FTBFS error.
I tested it and it works.
However, applying this patch uncovers some other (I would assume
unrelated ?) errors :
- Some compiler compiler seems to be required by the upstream
makefile, so I added bison to the build dependencies
- The automatic tests made after the compilation fail because
ImageMagick triggers a segmentation fault. I overrode auto test
and tested manually the binary, which seems to work.
I have included the patch, the new control and rules files, and I
am tagging this bug as having a patch.
Let me know if you have any questions.
Best,
Aymeric Agon-Rambosson
Description: Fix compile failures for newer g++ release
Author: Thomas Sailer
Forwarded: yes
Comment: Found on https://sourceforge.net/p/drawtiming/patches/12/
--- a/src/parser.yy
+++ b/src/parser.yy
@@ -42,13 +42,13 @@ statements:
statement { $$ = $1; deps.push_back ($1); }
| statements ',' statement { $$ = $3; deps.push_back ($3); }
| statements ';' statement { $$ = $3; deps.clear (); deps.push_back ($3); }
-| statements CAUSE statement { $$ = $3; data.add_dependencies ($3, deps);
+| statements CAUSE statement { $$ = $3; data_.add_dependencies ($3, deps);
deps.clear (); deps.push_back ($3); }
-| statements DELAY statement { $$ = $3; data.add_delay ($3, $1, $2); }
+| statements DELAY statement { $$ = $3; data_.add_delay ($3, $1, $2); }
statement:
-SYMBOL '=' SYMBOL { $$ = $1; data.set_value ($1, n, timing::sigvalue ($3)); }
-| SYMBOL '=' STRING { $$ = $1; data.set_value ($1, n, timing::sigvalue ($3, timing::STATE)); }
+SYMBOL '=' SYMBOL { $$ = $1; data_.set_value ($1, n, timing::sigvalue ($3)); }
+| SYMBOL '=' STRING { $$ = $1; data_.set_value ($1, n, timing::sigvalue ($3, timing::STATE)); }
| SYMBOL { $$ = $1; };
%%
--- a/src/globals.h
+++ b/src/globals.h
@@ -22,7 +22,7 @@
#define YYSTYPE std::string
extern unsigned n;
-extern timing::data data;
+extern timing::data data_;
extern timing::signal_sequence deps;
#endif
--- a/src/timing.cc
+++ b/src/timing.cc
@@ -113,16 +113,16 @@ sigdata &sigdata::operator= (const sigda
//
-data::data (void) : maxlen (0) {
+timing::data::data (void) : maxlen (0) {
}
-data::data (const data &d) {
+timing::data::data (const timing::data &d) {
*this = d;
}
//
-data &data::operator= (const data &d) {
+timing::data &timing::data::operator= (const timing::data &d) {
maxlen = d.maxlen;
signals = d.signals;
sequence = d.sequence;
@@ -132,7 +132,7 @@ data &data::operator= (const data &d) {
//
-sigdata &data::find_signal (const signame &name) {
+sigdata &timing::data::find_signal (const signame &name) {
signal_database::iterator i = signals.find (name);
if (i == signals.end ()) {
i = signals.insert (signal_database::value_type (name, sigdata ())).first;
@@ -143,7 +143,7 @@ sigdata &data::find_signal (const signam
//
-const sigdata &data::find_signal (const signame &name) const {
+const sigdata &timing::data::find_signal (const signame &name) const {
signal_database::const_iterator i = signals.find (name);
if (i == signals.end ())
throw not_found (name);
@@ -152,7 +152,7 @@ const sigdata &data::find_signal (const
//
-void data::add_dependency (const signame &name, const signame &dep) {
+void timing::data::add_dependency (const signame &name, const signame &dep) {
// find the signal
sigdata &sig = find_signal (name);
sigdata &trigger = find_signal (dep);
@@ -168,14 +168,14 @@ void data::add_dependency (const signame
//
-void data::add_dependencies (const signame &name, const signal_sequence &deps) {
+void timing::data::add_dependencies (const signame &name, const signal_sequence &deps) {
for (signal_sequence::const_iterator j = deps.begin (); j != deps.end (); ++ j)
add_dependency (name, *j);
}
//
-void data::add_delay (const signame &name, const signame &dep, const string &text) {
+void timing::data::add_delay (const signame &name, const signame &dep, const string &text) {
// a delay always indicates a dependency
// (but would require a way to select which is rendered)
// add_dependency (name, dep);
@@ -206,7 +206,7 @@ void data::add_delay (const signame &nam
//
-void data::set_value (const signame &name, unsigned n, const sigvalue &value) {
+void timing::data::set_value (const signame &name, unsigned n, const sigvalue &value) {
// find the signal
sigdata &sig = find_signal (name);
@@ -228,7 +228,7 @
Bug#1025322: marked as pending in pylint
Control: tag -1 pending Hello, Bug #1025322 in pylint 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/pylint/-/commit/2fd32bd76ac295167cbcc7dfde4a03fef9bb4c00 bump dill b-d to >= 0.3.6, needed for tests to pass with python 3.11; Closes: #1025322 (this message was generated automatically) -- Greetings https://bugs.debian.org/1025322
Processed: Bug#1025322 marked as pending in pylint
Processing control commands: > tag -1 pending Bug #1025322 [src:pylint] pylint: FTBFS with Python 3.11 as a supported version Added tag(s) pending. -- 1025322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025872: installing greetd immediately reboots and prevents any logins
Package: greetd Version: 0.8.0-1+b1 Severity: critical Hi, installing the greetd package will log out the current user. When attempting to log in again, the message "This account is currently not available." is shown and the user is put back into the login prompt. This happens independent of which user one tries to login with. There are two problems here: 1. installing greetd should log out the current user. This prevents editing /etc/greetd/config.toml to add the intended configuration. Since the package cannot know the user's intention, maybe the service should be disabled by default? 2. the default configuration reads: command = "/usr/sbin/agreety --cmd $SHELL" since greetd is run as the _greetd user and since the shell of the _greetd is /usr/sbin/nologin, $SHELL will become /usr/sbin/nologin and thus all login attempts will be made impossible. I think to close this bug, both issues must be addressed: 1. do not start the greetd service by default installing a package should not result into logging out the currently active user 2. provide a sensible default. Using $SHELL makes no sense when the default shell of the user running greetd is /usr/sbin/nologin. Maybe replace $SHELL with /bin/bash? Thanks! cheers, josch
Bug#1025648: marked as done (cacti: CVE-2022-46169: Unauthenticated Command Injection)
Your message dated Sat, 10 Dec 2022 23:47:09 + with message-id and subject line Bug#1025648: fixed in cacti 1.2.16+ds1-2+deb11u1 has caused the Debian Bug report #1025648, regarding cacti: CVE-2022-46169: Unauthenticated Command Injection 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.) -- 1025648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cacti Version: 1.2.22+ds1-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for cacti. CVE-2022-46169[0]: | Cacti is an open source platform which provides a robust and | extensible operational monitoring and fault management framework for | users. In affected versions a command injection vulnerability allows | an unauthenticated user to execute arbitrary code on a server running | Cacti, if a specific data source was selected for any monitored | device. The vulnerability resides in the `remote_agent.php` file. This | file can be accessed without authentication. This function retrieves | the IP address of the client via `get_client_addr` and resolves this | IP address to the corresponding hostname via `gethostbyaddr`. After | this, it is verified that an entry within the `poller` table exists, | where the hostname corresponds to the resolved hostname. If such an | entry was found, the function returns `true` and the client is | authorized. This authorization can be bypassed due to the | implementation of the `get_client_addr` function. The function is | defined in the file `lib/functions.php` and checks serval `$_SERVER` | variables to determine the IP address of the client. The variables | beginning with `HTTP_` can be arbitrarily set by an attacker. Since | there is a default entry in the `poller` table with the hostname of | the server running Cacti, an attacker can bypass the authentication | e.g. by providing the header `Forwarded-For:`. This | way the function `get_client_addr` returns the IP address of the | server running Cacti. The following call to `gethostbyaddr` will | resolve this IP address to the hostname of the server, which will pass | the `poller` hostname check because of the default entry. After the | authorization of the `remote_agent.php` file is bypassed, an attacker | can trigger different actions. One of these actions is called | `polldata`. The called function `poll_for_data` retrieves a few | request parameters and loads the corresponding `poller_item` entries | from the database. If the `action` of a `poller_item` equals | `POLLER_ACTION_SCRIPT_PHP`, the function `proc_open` is used to | execute a PHP script. The attacker-controlled parameter `$poller_id` | is retrieved via the function `get_nfilter_request_var`, which allows | arbitrary strings. This variable is later inserted into the string | passed to `proc_open`, which leads to a command injection | vulnerability. By e.g. providing the `poller_id=;id` the `id` command | is executed. In order to reach the vulnerable call, the attacker must | provide a `host_id` and `local_data_id`, where the `action` of the | corresponding `poller_item` is set to `POLLER_ACTION_SCRIPT_PHP`. Both | of these ids (`host_id` and `local_data_id`) can easily be | bruteforced. The only requirement is that a `poller_item` with an | `POLLER_ACTION_SCRIPT_PHP` action exists. This is very likely on a | productive instance because this action is added by some predefined | templates like `Device - Uptime` or `Device - Polling Time`. This | command injection vulnerability allows an unauthenticated user to | execute arbitrary commands if a `poller_item` with the `action` type | `POLLER_ACTION_SCRIPT_PHP` (`2`) is configured. The authorization | bypass should be prevented by not allowing an attacker to make | `get_client_addr` (file `lib/functions.php`) return an arbitrary IP | address. This could be done by not honoring the `HTTP_...` `$_SERVER` | variables. If these should be kept for compatibility reasons it should | at least be prevented to fake the IP address of the server running | Cacti. This vulnerability has been addressed in both the 1.2.x and | 1.3.x release branches with `1.2.23` being the first release | containing the patch. 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-2022-46169 https://www.cve.org/CV
Processed: notfound 1004547 in 2.39-8, notfixed 1004547 in 2.39-8, fixed 1004547 in 2.39-8 ..., tagging 1025812 ...
Processing commands for cont...@bugs.debian.org:
> notfound 1004547 2.39-8
Bug #1004547 {Done: Bo YU } [binutils-riscv64-linux-gnu]
binutils-riscv64-linux-gnu: linux build fails w/ latest as, ld
No longer marked as found in versions binutils/2.39-8.
> notfixed 1004547 2.39-8
Bug #1004547 {Done: Bo YU } [binutils-riscv64-linux-gnu]
binutils-riscv64-linux-gnu: linux build fails w/ latest as, ld
No longer marked as fixed in versions binutils-riscv64-linux-gnu/2.39-8.
> fixed 1004547 2.39-8
Bug #1004547 {Done: Bo YU } [binutils-riscv64-linux-gnu]
binutils-riscv64-linux-gnu: linux build fails w/ latest as, ld
Marked as fixed in versions binutils/2.39-8.
> notfixed 1024993 0.81.2+deb11u1
Bug #1024993 {Done: Santiago Vila } [sbuild] sbuild:
SUDO_FORCE_REMOVE=yes has no effect anymore
No longer marked as fixed in versions 0.81.2+deb11u1.
> notfixed 1011241 2:20.0~alpha1+dfsg1-2.
Bug #1011241 {Done: Vasyl Gello } [kodi] kodi: Unable to
change timezone (Kodi only uses system’s timezone)
There is no source info for the package 'kodi' at version
'2:20.0~alpha1+dfsg1-2.' with architecture ''
Unable to make a source version for version '2:20.0~alpha1+dfsg1-2.'
No longer marked as fixed in versions 2:20.0~alpha1+dfsg1-2..
> fixed 1011241 2:20.0~alpha1+dfsg1-2
Bug #1011241 {Done: Vasyl Gello } [kodi] kodi: Unable to
change timezone (Kodi only uses system’s timezone)
Marked as fixed in versions kodi/2:20.0~alpha1+dfsg1-2.
> fixed 739478 2.06-5
Bug #739478 {Done: Samuel Thibault } [grub2] grub2:
Scrambled d-i boot screen in kvm
Marked as fixed in versions grub2/2.06-5.
> tags 1025812 + sid bookworm
Bug #1025812 [elpa-haskell-mode] elpa-haskell-mode: Tests fail against Emacs
28.2
Added tag(s) bookworm and sid.
> found 1024218 11.1+repack-1
Bug #1024218 [apitrace] apitrace: FTBFS with libproc2
Marked as found in versions apitrace/11.1+repack-1.
> found 1024221 1.26+git20220524-1
Bug #1024221 [intel-gpu-tools] intel-gpu-tools: FTBFS with libproc2
Marked as found in versions intel-gpu-tools/1.26+git20220524-1.
> found 1024220 5.8.0.46-2
Bug #1024220 [deepin-screen-recorder] deepin-screen-recorder: FTBFS with
libproc2
Marked as found in versions deepin-screen-recorder/5.8.0.46-2.
> tags 1024220 + sid bookworm
Bug #1024220 [deepin-screen-recorder] deepin-screen-recorder: FTBFS with
libproc2
Added tag(s) bookworm and sid.
> found 1024225 4.7.4+repack1-1
Bug #1024225 [veyon-plugins] veyon-plugins: FTBFS with libproc2
Marked as found in versions veyon/4.7.4+repack1-1.
> fixed 883939 2:4.17.3+dfsg-3
Bug #883939 {Done: Michael Tokarev } [smbclient] smbclient
failing to connect with default protocol SMB3_11
Marked as fixed in versions samba/2:4.17.3+dfsg-3.
> reassign 1024687 src:libfm-qt 1.2.0-1
Bug #1024687 {Done: ChangZhuo Chen (陳昌倬) } [libfm-qt11]
libfm-qt11:amd64 1.1.0-3 -> 1.2.0-1 breaks some lxqt functionalities
Warning: Unknown package 'libfm-qt11'
Bug reassigned from package 'libfm-qt11' to 'src:libfm-qt'.
No longer marked as found in versions libfm-qt/1.2.0-1.
No longer marked as fixed in versions libfm-qt/1.2.0-3 and libfm-qt/1.2.0-4.
Bug #1024687 {Done: ChangZhuo Chen (陳昌倬) } [src:libfm-qt]
libfm-qt11:amd64 1.1.0-3 -> 1.2.0-1 breaks some lxqt functionalities
Marked as found in versions libfm-qt/1.2.0-1.
> fixed 1024687 1.2.0-3
Bug #1024687 {Done: ChangZhuo Chen (陳昌倬) } [src:libfm-qt]
libfm-qt11:amd64 1.1.0-3 -> 1.2.0-1 breaks some lxqt functionalities
Marked as fixed in versions libfm-qt/1.2.0-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1004547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004547
1011241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011241
1024218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024218
1024220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024220
1024221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024221
1024225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024225
1024687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024687
1024993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024993
1025812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025812
739478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739478
883939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1025869: tigervnc-scraping-server: Under bookworm server fails to start. Gives error in Wrapper.pm
Package: tigervnc-scraping-server Version: 1.12.0+dfsg-5 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** TigerVNC Server version 1.12.0, built 2022-07-09 14:10 Debian Testing (Bookworm) Try to start server: $x0vncserver -display:0 -SecurityTypes None Result: 0vncserver: /usr/bin/X0tigervnc exited with status 1, please look into '/home/mark/.vnc/[machine-name-redacted]:5900.log' to determine the reason! -2 Can't locate object method "cleanup" via package "File::Temp::Dir" at /usr/share/perl5/TigerVNC/Wrapper.pm line 1347, line 100. Looking at the referenced log file, there are no details. It just contains the usage. I am not a developer. I can test software if provided with a binary but find compiling challenging. Thank you! -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-2-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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 tigervnc-scraping-server depends on: ii libc6 2.36-4 ii libfile-readbackwards-perl 1.06-2 ii libgcc-s1 12.2.0-9 ii libgnutls30 3.7.8-4 ii libjpeg62-turbo 1:2.1.2-1+b1 ii libpam0g1.5.2-5 ii libpixman-1-0 0.40.0-1.1 ii libstdc++6 12.2.0-9 ii libx11-62:1.8.1-2 ii libxdamage1 1:1.1.5-2 ii libxext62:1.3.4-1+b1 ii libxfixes3 1:6.0.0-2 ii libxrandr2 2:1.5.2-2+b1 ii libxtst62:1.2.3-1.1 ii perl5.34.0-5 ii tigervnc-common 1.12.0+dfsg-5 ii zlib1g 1:1.2.11.dfsg-4.1 Versions of packages tigervnc-scraping-server recommends: ii tigervnc-tools 1.12.0+dfsg-5 Versions of packages tigervnc-scraping-server suggests: ii openssl 3.0.7-1 -- no debconf information
Bug#1025831: marked as done (vpb-driver: FTBFS due to missing threads.h)
Your message dated Sat, 10 Dec 2022 22:11:14 + with message-id and subject line Bug#1025831: fixed in vpb-driver 4.2.61-1.4 has caused the Debian Bug report #1025831, regarding vpb-driver: FTBFS due to missing threads.h 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.) -- 1025831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vpb-driver Version: 4.2.61-1.3 Severity: serious Tags: ftbfs Dear Maintainer, The package has a ftbfs on all arch: ``` ../../../include/vt/tonegen.h: In static member function ‘static void ToneGen::mutex_cleanup(void*)’: ../../../include/vt/tonegen.h:527:13: error: ‘pthread_mutex_unlock’ was not declared in this scope; did you mean ‘pthread_mutex_t’? 527 | pthread_mutex_unlock((pthread_mutex_t*)p); | ^~~~ | pthread_mutex_t ../../../include/vt/tonegen.h: In member function ‘void ToneGen::DoStop()’: ../../../include/vt/tonegen.h:538:17: error: ‘pthread_cond_broadcast’ was not declared in this scope; did you mean ‘pthread_condattr_t’? 538 | pthread_cond_broadcast( &m_cond ); | ^~ | pthread_condattr_t ../../../include/vt/tonegen.h: In constructor ‘ToneGen::ToneGen()’: ../../../include/vt/tonegen.h:559:9: error: ‘pthread_mutex_init’ was not declared in this scope; did you mean ‘pthread_mutex_t’? 559 | pthread_mutex_init(&m_mutex, NULL); | ^~ | pthread_mutex_t ../../../include/vt/tonegen.h:560:9: error: ‘pthread_cond_init’ was not declared in this scope; did you mean ‘pthread_cond_t’? 560 | pthread_cond_init(&m_cond, NULL); ... ``` The full buildd log is here: https://buildd.debian.org/status/fetch.php?pkg=vpb-driver&arch=all&ver=4.2.61-1.3&stamp=1670637027&raw=0 This should be easy to fix and I will update it once test and verify. -- Regards, -- Bo YU signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: vpb-driver Source-Version: 4.2.61-1.4 Done: Bo YU We believe that the bug you reported is fixed in the latest version of vpb-driver, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bo YU (supplier of updated vpb-driver package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 10 Dec 2022 17:49:17 +0800 Source: vpb-driver Architecture: source Version: 4.2.61-1.4 Distribution: unstable Urgency: medium Maintainer: Ron Lee Changed-By: Bo YU Closes: 1025831 Changes: vpb-driver (4.2.61-1.4) unstable; urgency=medium . * Non-maintainer upload. * Fix ftbfs. (Closes: #1025831) Checksums-Sha1: d01f7c829d726e49e491d9b168c63ce1c0fe0c11 1905 vpb-driver_4.2.61-1.4.dsc b06e47d3f2b892aaa2b27571fc88d194e23bae92 18752 vpb-driver_4.2.61-1.4.debian.tar.xz 0e1602282878a2e2bfdda0f8e612288e3f04527f 5747 vpb-driver_4.2.61-1.4_source.buildinfo Checksums-Sha256: 61da78465f41f6b08cd30af4d8ab56df0cfb59b39c58f3777eacfc52dd20ae67 1905 vpb-driver_4.2.61-1.4.dsc 61542bd8ec8b1ed5f85eb48d06ca7dfa4b61e8572d061db606f26950ddc003f9 18752 vpb-driver_4.2.61-1.4.debian.tar.xz fb3004e5e883029f1a37e217d62a3c3d711ca11bc5e26011cb33952be2585774 5747 vpb-driver_4.2.61-1.4_source.buildinfo Files: 46359512a3272449dde958f14123ab7d 1905 comm optional vpb-driver_4.2.61-1.4.dsc 182aea32914c25304bd331168ce1895a 18752 comm optional vpb-driver_4.2.61-1.4.debian.tar.xz f7f693d78b61680e564431f5b0f54d4a 5747 comm optional vpb-driver_4.2.61-1.4_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmOU+xUQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFL5RDACJwZiMdU/WFr4+uo3k8zcSIfgm/BVZhHLl nyg7JcFqaoTVgMbz3or9AVWtQB3Lh0HsRtp147vuy1VY/juI1WeERD9iwXSdloOU qhhhHFa7yM/lc7e5ZeiWsGEW07EI3k7PSFXdH1jXvJ+Tr3cd6hPJ+YipmNxzusJ1 tIXh7PsEAEUcNal3VhFsDe48Mh412pNvfTi/PPZyiArFs0kq17n4b8xlUT/QyFPl ZIbTtHV2dRqmSaDs+u1mraoqStL414XDvVSLDI9Igm0kivilMZ6vIBy96LsbtR8A lxbxyhGAxqcHSJINLhPjrcOwiBo1h0G1KGWXscKjwd8kXgxw9igYV
Processed: Re: Bug#1025868: lintian autopkgtest fails on all but amd64: x86_64-linux-gnu expected build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/generic.t
Processing control commands: > tag -1 + confirmed moreinfo Bug #1025868 [src:lintian] lintian autopkgtest fails on all but amd64: x86_64-linux-gnu expected build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/generic.t Added tag(s) moreinfo and confirmed. -- 1025868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025868: lintian autopkgtest fails on all but amd64: x86_64-linux-gnu expected build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/generic.t
Control: tag -1 + confirmed moreinfo Hi Paul, Paul Gevers wrote: > Source: lintian > Version: 2.111.0 Ehm, that version no more in the archive anywhere. Did you maybe mean 2.115.3 as currently in Testing and Unstable? (Feel free to remove the moreinfo tag once this is clarified.) > Your package has an autopkgtest, great. However, it fails currently > everywhere except on amd64. Correct. > Can you please investigate the situation Already done. Issue are mostly hardcoded x86_64 and amd64 strings in the test suite. Problem is IIRC that Lintian's testsuite currently doesn't support a templating system, at least not for many of these places. IIRC I fixed already some of them which were easy to fix. > and fix it? Will have to look into it again, but I fear in short term, it means to either reduce the tests or only run a subset on non-amd64 architectures. Anyway, thanks for the reminder. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#1025835: tiledb-py: build-depends on libtiledb-doc
On 10 December 2022 at 22:38, Nilesh Patra wrote: | On Sat, Dec 10, 2022 at 07:56:52AM -0600, Dirk Eddelbuettel wrote: | > | > On 10 December 2022 at 09:07, Peter Green wrote: | > | Source: tiledb-py | > | Version: 0.18.2-1 | > | Severity: serious | > | Justification: rc policy - "Packages must be buildable within the same release" | > | x-debbugs-cc: e...@debian.org | > | User: debian...@lists.debian.org | > | Usertags: edos-uninstallable | > | | > | tiledb-py build-depends on libtiledb-doc, which is no longer built by tiledb since | > | version 2.13.0-1, this removal is no mentioned in the changelog, so it's not clear to me | > | if it was deliberate or not. It is still present in unsable as a cruft package, but is | > | completely gone from testing. This means that tiledb-py in testing is in violation of | > | the rc policy. | > | > Good catch but that was in fact deliberate. | > | > The build (of a package I inherited / adopted) was giving me fits, and I as | > maintainer have decided to follow a) upstreams preference for documentation | > on the websites and b) simplify the build. | | While this is an acceptable stance, I'd really prefer if you consider to keep | vendoring the documentation. I have seen a number of bug reports and also heard | from many people that they'd like to have a copy of documentation offline as well, | as it a) enables to work when internet is spotty for them b) Look up everything | offline instead of the online source as the docs contain API that correspond to | the relevant version. | | I understand that vendoring documentation could be extra work, but if vendoring it | is not a source of nuisance for each and every update, and the build rules are constant | then I don't see a lot of issue with it. For your case, did you have any particular | issues/build failures while vendoring the documentation? | Also, I know that you understand tiledb far better than I do, but still I'd like to offer my help | for this issue, should you like it, and if you help me understand where exactly it crossed | the threshold for maintainer-time-well-spent. | | > We should adjust tiledb-py | | This is easy enough to do, which would mean removing doc package from tiledb-py as well. | But again, I'd like to do this only after I hear back from you. It's complicated. You and I may both have too many packages to dive into why this one suddenly fails on docs. To me, the library part matters more. We could always build a -doc package off the same sources, or debug the build, or ... but I do _not_ think we should hold the library package back for this. So I kindly ask you to adjust tiledb-py to unlock the tiledb (source) package for no longer shipping libtiledb-doc. | > (which needs an update for the now released 0.19.0 | > anyway, and had skipped minor release 0.18.3 which is ok) accordingly. | | Thanks for the ping. I work on hunderds of packages and I tend to skip updates so this | is helpful. It's a titch under two hundred for me and I keep an eye on my QA page every day or other day which works well enough. Plus, many of them are r-cran-* and I see via CRANberries [1] when those change upstream and quickly update those. Dirk [1] As RSS or tweets or here in html: https://dirk.eddelbuettel.com/cranberries/ -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1025831: vpb-driver: FTBFS due to missing threads.h
I am sponsoring the fix for this. debdiff is attached.diff -Nru vpb-driver-4.2.61/debian/changelog vpb-driver-4.2.61/debian/changelog --- vpb-driver-4.2.61/debian/changelog 2022-12-10 00:42:50.0 +0100 +++ vpb-driver-4.2.61/debian/changelog 2022-12-10 10:49:17.0 +0100 @@ -1,3 +1,10 @@ +vpb-driver (4.2.61-1.4) unstable; urgency=medium + + * Non-maintainer upload. + * Fix ftbfs. (Closes: #1025831) + + -- Bo YU Sat, 10 Dec 2022 17:49:17 +0800 + vpb-driver (4.2.61-1.3) unstable; urgency=medium * Non-maintainer upload diff -Nru vpb-driver-4.2.61/debian/patches/fix-ftbfs-missing-pthread.patch vpb-driver-4.2.61/debian/patches/fix-ftbfs-missing-pthread.patch --- vpb-driver-4.2.61/debian/patches/fix-ftbfs-missing-pthread.patch 1970-01-01 01:00:00.0 +0100 +++ vpb-driver-4.2.61/debian/patches/fix-ftbfs-missing-pthread.patch 2022-12-10 10:49:17.0 +0100 @@ -0,0 +1,49 @@ +Description: fix ftbfs due to missing pthread +Author: Bo YU +Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025831 +Forwarded: no +Last-Update: 2022-12-10 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/include/vt/tonegen.h b/include/vt/tonegen.h +@@ -35,6 +35,7 @@ + #include + #include + #include ++#include + + + //XXX this might be better as a generic tool in some other file, but for +--- a/src/utils/playwav.cpp b/src/utils/playwav.cpp +@@ -25,7 +25,7 @@ + \*---*/ + + #include "vpbapi.h" +-//#include "threads.h" // for billware ++#include "threads.h" + + #include + #include +--- a/src/utils/tonegen.cpp b/src/utils/tonegen.cpp +@@ -26,6 +26,7 @@ + + #include "vpbapi.h" + #include "kbhit.h" ++#include "threads.h" + + #include + #include +--- a/src/utils/vpbecho.cpp b/src/utils/vpbecho.cpp +@@ -34,7 +34,7 @@ + #include "vpbapi.h" + #include "verbose.h" + #include "kbhit.h" +-//#include "threads.h" // for billware ++#include "threads.h" + + #include + #include diff -Nru vpb-driver-4.2.61/debian/patches/series vpb-driver-4.2.61/debian/patches/series --- vpb-driver-4.2.61/debian/patches/series 2022-12-10 00:42:50.0 +0100 +++ vpb-driver-4.2.61/debian/patches/series 2022-12-10 04:56:35.0 +0100 @@ -1 +1,2 @@ debian.patch +fix-ftbfs-missing-pthread.patch
Bug#1025868: lintian autopkgtest fails on all but amd64: x86_64-linux-gnu expected build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/generic.t
Source: lintian Version: 2.111.0 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails currently everywhere except on amd64. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing as are regressions on all release architectures. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/arm64/l/lintian/28970519/log.gz # Hints do not match # # --- ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/hints.specified.calibrated # +++ ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/hints.actual.parsed # -gir1.2-good-42 (binary): typelib-not-in-multiarch-directory usr/lib/x86_64-linux-gnu/girepository-1.0 [usr/lib/girepository-1.0/GoodExtras-42.typelib] # -gir1.2-good-42 (binary): typelib-not-in-multiarch-directory usr/lib/x86_64-linux-gnu/girepository-1.0 [usr/lib/girepository-1.0/Good-42.typelib] # +gir1.2-good-42 (binary): typelib-not-in-multiarch-directory usr/lib/aarch64-linux-gnu/girepository-1.0 [usr/lib/girepository-1.0/GoodExtras-42.typelib] # +gir1.2-good-42 (binary): typelib-not-in-multiarch-directory usr/lib/aarch64-linux-gnu/girepository-1.0 [usr/lib/girepository-1.0/Good-42.typelib] # # Failed test 'Lintian passes for gir' # at /usr/share/lintian/lib/Test/Lintian/Run.pm line 343. # Looks like you failed 1 test of 1. ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/generic.t ... and # Hints do not match # # --- ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/files/contents/bin-sbin-confusion-in-elf/hints.specified.calibrated # +++ ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/files/contents/bin-sbin-confusion-in-elf/hints.actual.parsed # +bin-sbin-confusion-in-elf (binary): bin-sbin-mismatch sbin/our-script -> usr/bin/our-script [usr/bin/calls-sbin] # +bin-sbin-confusion-in-elf (binary): bin-sbin-mismatch bin/our-script -> usr/bin/our-script [usr/bin/calls-sbin] # # Failed test 'Lintian passes for bin-sbin-confusion-in-elf' # at /usr/share/lintian/lib/Test/Lintian/Run.pm line 343. # Looks like you failed 1 test of 1. ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/files/contents/bin-sbin-confusion-in-elf/generic.t OpenPGP_signature Description: OpenPGP digital signature
Bug#1024786: marked as done (aionotify: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine')
Your message dated Sat, 10 Dec 2022 21:19:26 + with message-id and subject line Bug#1024786: fixed in aionotify 0.2.0-3 has caused the Debian Bug report #1024786, regarding aionotify: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine' 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.) -- 1024786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aionotify Version: 0.2.0-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of aionotify fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 aionotify from testing0.2.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. E.g.: """ Removed the @asyncio.coroutine() decorator enabling legacy generator-based coroutines to be compatible with async / await code. The function has been deprecated since Python 3.8 and the removal was initially scheduled for Python 3.10. Use async def instead. (Contributed by Illia Volochii in bpo-43216.) """ More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/a/aionotify/28628638/log.gz Testing with python3.11: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/aionotify/__init__.py", line 5, in from .base import Watcher File "/usr/lib/python3/dist-packages/aionotify/base.py", line 10, in from . import aioutils File "/usr/lib/python3/dist-packages/aionotify/aioutils.py", line 122, in @asyncio.coroutine ^ AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you mean: 'coroutines'? autopkgtest [12:13:03]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: aionotify Source-Version: 0.2.0-3 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of aionotify, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated aionotify package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 10 Dec 2022 21:40:42 +0100 Source: aionotify Architecture: source Version: 0.2.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Timo Röhling Closes: 1024786 Changes: aionotify (0.2.0-3) unstable; urgency=medium . * Team upload. * Replace obsolete @asyncio.coroutine with async def (Closes: #1024786) * Bump Standards-Version to 4.6.1 Checksums-Sha1: 8d7f4331d542f706a70c74b20048a2ec1022483a 1870 aionotify_0.2.0-3.dsc 71b0e329b3ee1b8a0efb2e52f6c035f6d2e43daa 4996 aionotify_0.2.0-3.debian.tar.xz cdb4d0c606dae8eeb9852724448786e35af45c8f 6449 aionotify_0.2.0-3_amd64.buildinfo Checksums-Sha256: 5b87c32b221b07e100e5df04c38ba2e75093e811496f36a33463e76903776d8c 1870 aionotify_0.2.0-3.dsc 979fa21a3d1a913dd873e61a045b4432a34658609388b7ec210d4b56d9682ec7 4996 aionotify_0.2.0-3.debian.tar.xz e418e93f02c75846e7aeca693410397dc90b946ad065a15b237b4971915e
Bug#1025867: src:spyder: unsatisfied build dependency in testing: python3-qdarkstyle (< 3.1~)
Source: spyder Version: 5.3.3+dfsg-3 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature Description: OpenPGP digital signature
Bug#1023297: src:emacs: fails to migrate to testing for too long: unresolved RC issues
Hi Sean, On 09-12-2022 18:56, Sean Whitton wrote: If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Alright, all the RC bugs are closed. Of the four autopkgtest failures, emacs-deferred and flycheck we need to wait and see when they are re-run, Which happens daily. But I guess gcc needs to migrate first for the retest to be useful? I triggered some tests already in unstable and flycheck failed [1, 2]. emacs-defered seems to be fixed in unstable. but the evil-el and haskell-mode failures are due to bugs in those packages. evil-el is orphaned and haskell-mode is unmaintained. Could they both be hinted out of testing, please? I've added removal hints, I might need an iteration more. Paul [1] https://ci.debian.net/data/autopkgtest/unstable/amd64/f/flycheck/29209094/log.gz [2] https://ci.debian.net/data/autopkgtest/unstable/arm64/f/flycheck/29209095/log.gz OpenPGP_signature Description: OpenPGP digital signature
Bug#1025018: marked as done (python-aiomeasures: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine')
Your message dated Sat, 10 Dec 2022 20:58:38 + with message-id and subject line Bug#1025018: fixed in python-aiomeasures 0.5.14-5 has caused the Debian Bug report #1025018, regarding python-aiomeasures: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine' 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.) -- 1025018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-aiomeasures Version: 0.5.14-4 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-aiomeasures fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-aiomeasures from testing0.5.14-4 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-aiomeasures/28727759/log.gz Testing with python3.11: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/aiomeasures/__init__.py", line 9, in from .clients import * File "/usr/lib/python3/dist-packages/aiomeasures/clients/__init__.py", line 1, in from .datadog import Datadog File "/usr/lib/python3/dist-packages/aiomeasures/clients/datadog/__init__.py", line 1, in from .client import * File "/usr/lib/python3/dist-packages/aiomeasures/clients/datadog/client.py", line 4, in from aiomeasures.clients.bases import Client File "/usr/lib/python3/dist-packages/aiomeasures/clients/bases.py", line 10, in class Client(metaclass=ABCMeta): File "/usr/lib/python3/dist-packages/aiomeasures/clients/bases.py", line 57, in Client @asyncio.coroutine ^ AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you mean: 'coroutines'? autopkgtest [20:13:44]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-aiomeasures Source-Version: 0.5.14-5 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of python-aiomeasures, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated python-aiomeasures package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 10 Dec 2022 20:51:37 +0100 Source: python-aiomeasures Architecture: source Version: 0.5.14-5 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Timo Röhling Closes: 1025018 Changes: python-aiomeasures (0.5.14-5) unstable; urgency=medium . * Team upload. * Replace obsolete @asyncio.coroutine with async def (Closes: #1025018) * Bump Standards-Version to 4.6.1 Checksums-Sha1: 027d275d638401f678006f51c727fe32d9f75db6 2055 python-aiomeasures_0.5.14-5.dsc 343961848d1aaeb753561c1f273a84200f1a9c96 4240 python-aiomeasures_0.5.14-5.debian.tar.xz 678831b4c65386d407ce9497d3077ee21a4b6bce 6846 python-aiomeasures_0.5.14-5_amd64.buildinfo Checksums-Sha256: 6f2e27fe45a47ce522af6b2962847dfa338
Bug#1023000: reopen 1023000: flaky test in dpdk
reopen 1023000 found 1023000 21.11-5 thanks Hi, It seems the test is still flaky on at least amd64 [1]. Paul [1] https://ci.debian.net/packages/d/dpdk/testing/amd64/ OpenPGP_signature Description: OpenPGP digital signature
Bug#1025775: marked as done (libsdl2 breaks cataclysm-dda autopkgtest in lxc: only bottom left corner appears in screenshot)
Your message dated Sat, 10 Dec 2022 20:44:56 + with message-id and subject line Bug#1025775: fixed in cataclysm-dda 0.F-3-9 has caused the Debian Bug report #1025775, regarding libsdl2 breaks cataclysm-dda autopkgtest in lxc: only bottom left corner appears in screenshot 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.) -- 1025775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libsdl2, cataclysm-dda Control: found -1 libsdl2/2.26.0+dfsg-1 Control: found -1 cataclysm-dda/0.F-3-8 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of libsdl2 the autopkgtest of cataclysm-dda fails in testing when that autopkgtest is run with the binary packages of libsdl2 from unstable. It passes when run with only packages from testing. In tabular form: passfail libsdl2from testing2.26.0+dfsg-1 cataclysm-dda from testing0.F-3-8 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of libsdl2 to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? 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=libsdl2 https://ci.debian.net/data/autopkgtest/testing/amd64/c/cataclysm-dda/29137520/log.gz Estimating resolution as 141 XIO: fatal IO error 0 (Success) on X server ":99" after 466 requests (466 known processed) with 0 events remaining. /tmp/autopkgtest-lxc.yjpn_sfq/downtmp/wrapper.sh: Killing leaked background processes: 5102 PID TTY STAT TIME COMMAND 5102 ?Rl 0:00 cataclysm-tiles autopkgtest [15:21:00]: test command1 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: cataclysm-dda Source-Version: 0.F-3-9 Done: Reiner Herrmann We believe that the bug you reported is fixed in the latest version of cataclysm-dda, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reiner Herrmann (supplier of updated cataclysm-dda package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 10 Dec 2022 21:23:12 +0100 Source: cataclysm-dda Architecture: source Version: 0.F-3-9 Distribution: unstable Urgency: medium Maintainer: Reiner Herrmann Changed-By: Reiner Herrmann Closes: 1025775 Changes: cataclysm-dda (0.F-3-9) unstable; urgency=medium . [ Simon McVittie ] * d/tests/test-tiles: - Run a window manager inside Xvfb. (Closes: #1025775) - Show commands as we execute them. - Screenshot the whole screen, not just the window. - Show the OCR'd text in the log. - Use SDL_AUDIODRIVER=dummy instead of PulseAudio. - Use a white background for Xvfb. . [ Reiner Herrmann ] * d/tests/control: Drop pulseaudio from test dependencies. * d/tests/test-tiles: - start game with absolute path. - shutdown openbox gracefully. Checksums-Sha1: e4b6accc136c62dabf95699defcf5fea95a23522 2286 cataclysm-dda_0.F-3-9.dsc bb1d3308ee8f0c3dfd8b0fa51ef4b0fb1f1f53e4 27164 cataclysm-dda_0.F-3-9.debian.tar.xz dad9312fe273a1a999b4194c981315a420eb589c 6498 cataclysm-dda_0.F-3-9_source.buildinfo Checksums-Sha256: da82caa27135cc9dd63b55e971a7e23c5e554ecdb0cfa50d309bbd34a4a3fb65 2286 cataclysm-dda_0.F-3-9.dsc cf37ce0eff96849a023e2d40c21dfad6933801ca2153ff9c79d65b456d434290 27164 cataclysm-dda_0.F-3-9.debian.tar.xz 3a9a4199b13efe7765c832710ef9b471a2f960ce547cc19debd76be7afb57795 6498 cataclysm-dda_0.F-3-9_source.buildinfo Files: cfba985963797ae2d5f07ed439f3dee7 2286 games optional cataclysm-dda_0.F-3-9.dsc b841399ffc83180a53bed0f4261514e7 27164 games op
Processed: Bug#1024786 marked as pending in aionotify
Processing control commands: > tag -1 pending Bug #1024786 [src:aionotify] aionotify: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine' Added tag(s) pending. -- 1024786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024786: marked as pending in aionotify
Control: tag -1 pending Hello, Bug #1024786 in aionotify 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/aionotify/-/commit/a7ad9899d565b91808856447fffdf7da7324682c Replace obsolete @asyncio.coroutine with async def Closes: #1024786 (this message was generated automatically) -- Greetings https://bugs.debian.org/1024786
Bug#1025848: src:kiwi: unsatisfied build dependency in testing: python3-testinfra
Hi John, On 10-12-2022 15:44, John Paul Adrian Glaubitz wrote: I'm not sure what the point of this bug report is. src:kiwi will be removed (via autoremoval) from testing if it's build depends are not in testing (and this bug isn't closed). If any of the build dependencies are missing because someone reported a RC bug against it, it's not really my job to fix that particular bug. It's OK that you view it that way, but without the build dependencies in testing your package can't be in testing either. So you could help fixing the RC bugs in your build dependencies, or work around the build dependency (sometimes that's possible, not necessarily in this case). There is no apparent bug in kiwi that I know of, so I don't see what the purpose of this bug report is There's an RC issue with src:kiwi in bookworm. We don't want to ship src:kiwi in bookworm if it misses it's build dependencies in bookworm. is and what I am supposed to do except maybe go talk to the maintainer of python3-testinfra to tell him to fix their bugs. Talk, or help, or NMU, or work around it. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Bug#1025018 marked as pending in python-aiomeasures
Processing control commands: > tag -1 pending Bug #1025018 [src:python-aiomeasures] python-aiomeasures: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine' Added tag(s) pending. -- 1025018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025018 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025018: marked as pending in python-aiomeasures
Control: tag -1 pending Hello, Bug #1025018 in python-aiomeasures 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-aiomeasures/-/commit/7129ff540b6fee96ac2bb100100910bdffd8cb01 Replace obsolete @asyncio.coroutine with async def Closes: #1025018 (this message was generated automatically) -- Greetings https://bugs.debian.org/1025018
Bug#1025285: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022
Your message dated Sat, 10 Dec 2022 19:17:13 + with message-id and subject line Bug#1025285: fixed in nvidia-graphics-drivers-tesla-470 470.161.03-1~deb11u1 has caused the Debian Bug report #1025285, regarding nvidia-graphics-drivers-tesla-470: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 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.) -- 1025285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259 Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1 Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 Control: found -1 515.48.07-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5415 CVE-2022-34670 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer handler, where an unprivileged regular user can cause truncation errors when casting a primitive to a primitive of smaller size causes data to be lost in the conversion, which may lead to denial of service or information disclosure. CVE-2022-4
Bug#1025283: marked as done (nvidia-graphics-drivers-tesla-450: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022
Your message dated Sat, 10 Dec 2022 19:17:12 + with message-id and subject line Bug#1025283: fixed in nvidia-graphics-drivers-tesla-450 450.216.04-1~deb11u1 has caused the Debian Bug report #1025283, regarding nvidia-graphics-drivers-tesla-450: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 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.) -- 1025283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259 Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1 Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 Control: found -1 515.48.07-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5415 CVE-2022-34670 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer handler, where an unprivileged regular user can cause truncation errors when casting a primitive to a primitive of smaller size causes data to be lost in the conversion, which may lead to denial of service or information disclosure. CVE-2022-42263 NVIDIA GPU
Bug#1025281: marked as done (nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259)
Your message dated Sat, 10 Dec 2022 19:17:11 + with message-id and subject line Bug#1025281: fixed in nvidia-graphics-drivers-legacy-390xx 390.157-1~deb11u1 has caused the Debian Bug report #1025281, regarding nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259 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.) -- 1025281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259 Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1 Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 Control: found -1 515.48.07-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5415 CVE-2022-34670 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer handler, where an unprivileged regular user can cause truncation errors when casting a primitive to a primitive of smaller size causes data to be lost in the conversion, which may lead to denial of service or information disclosure. CVE-2022-42263 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer handler, where an Integer overflow may lead to denial of service or
Bug#1025279: marked as done (nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CV
Your message dated Sat, 10 Dec 2022 19:17:13 + with message-id and subject line Bug#1025279: fixed in nvidia-graphics-drivers-tesla-470 470.161.03-1~deb11u1 has caused the Debian Bug report #1025279, regarding nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 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.) -- 1025279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259 Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1 Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 Control: found -1 515.48.07-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5415 CVE-2022-34670 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer handler, where an unprivileged regular user can cause truncation errors when casting a primitive to a primitive of smaller size causes data to be lost in the conversion, which may lead to denial of service or information disclosure. CVE-
Bug#1025279: marked as done (nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CV
Your message dated Sat, 10 Dec 2022 19:17:10 + with message-id and subject line Bug#1025279: fixed in nvidia-graphics-drivers 470.161.03-1 has caused the Debian Bug report #1025279, regarding nvidia-graphics-drivers: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 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.) -- 1025279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers Severity: serious Tags: security upstream Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259 Control: tag -2 + wontfix Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4 Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34680, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259 Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: tag -4 + wontfix Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1 Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1 Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: tag -6 + wontfix Control: close -6 460.106.00-3 Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1 Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1 Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: reassign -9 src:nvidia-graphics-drivers-tesla 510.85.02-1 Control: retitle -9 nvidia-graphics-drivers-tesla: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Control: found -1 340.24-1 Control: found -1 343.22-1 Control: found -1 396.18-1 Control: found -1 430.14-1 Control: found -1 455.23.04-1 Control: found -1 465.24.02-1 Control: found -1 495.44-1 Control: found -1 515.48.07-1 https://nvidia.custhelp.com/app/answers/detail/a_id/5415 CVE-2022-34670 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer handler, where an unprivileged regular user can cause truncation errors when casting a primitive to a primitive of smaller size causes data to be lost in the conversion, which may lead to denial of service or information disclosure. CVE-2022-42263 NVIDIA
Bug#1024852: marked as done (nvidia-driver in bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1) do not support Linux kernel 6.0 or later)
Your message dated Sat, 10 Dec 2022 19:17:13 +
with message-id
and subject line Bug#1024852: fixed in nvidia-graphics-drivers-tesla-470
470.161.03-1~deb11u1
has caused the Debian Bug report #1024852,
regarding nvidia-driver in bullseye (470.141.03-1~deb11u1) and
bullseye-backports (470.103.01-1~bpo11+1) do not support Linux kernel 6.0 or
later
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.)
--
1024852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 470.103.01-1~bpo11+1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
About a week ago, linux-image-6.0.0-0.deb11.2-amd64 was introduced in
bullseye-backports. The problem is that the nvidia-driver version in both
bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1)
(for some reason, the version in bullseye is newer which is strange) DO NOT
support Linux kernel 6.0.
When a user who uses a backported linux kernel and nvidia-driver upgrades their
system, they will get an error message that looks like this
https://imgur.com/sEVx1vc (sorry if I couldn't give you the text output; I am
reporting this on behalf of a friend)
This issue is reproducable and happened on two of my friends' machines. We
found a current workaround that involves booting to kernel 5.1x in the Grub
menu, running sudo apt purge linux-image-6.0.0-0.deb11.2-amd64 && sudo apt
install -t bullseye-backports nvidia-driver && sudo reboot now.
According to this Phoronix article (
https://www.phoronix.com/news/NVIDIA-515.76-Linux-Driver ), nvidia-driver
515.76 or newer support Linux kernel 6.0. I believe the solution is to upgrade
nvidia-driver to 515.76 or newer in bullseye-backports so that users can use
their graphics card on kernel 6.0.
Thank you for reading my bug report and I hope you guys have a great day!
--
Alex Relis
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-470
Source-Version: 470.161.03-1~deb11u1
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-tesla-470, 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 1024...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated
nvidia-graphics-drivers-tesla-470 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, 10 Dec 2022 02:43:07 +0100
Source: nvidia-graphics-drivers-tesla-470
Architecture: source
Version: 470.161.03-1~deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Debian NVIDIA Maintainers
Changed-By: Andreas Beckmann
Closes: 1020697 1021974 1022738 1024852 1025279 1025285
Changes:
nvidia-graphics-drivers-tesla-470 (470.161.03-1~deb11u1) bullseye;
urgency=medium
.
* Rebuild for bullseye.
.
nvidia-graphics-drivers-tesla-470 (470.161.03-1) unstable; urgency=medium
.
* New upstream production branch release 470.161.03 (2022-11-22).
* Fixed CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677,
CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254,
CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258,
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262,
CVE-2022-42263, CVE-2022-42264. (Closes: #1025285)
https://nvidia.custhelp.com/app/answers/detail/a_id/5415
- Fixed a bug that caused the Xorg server to crash if an NvFBC capture
session is started while video memory is full.
* Improved compatibility with recent Linux kernels.
* New upstream Tesla release (amd64 only) 470.141.10 (2022-10-19).
.
[ Andreas Beckmann ]
* Refresh patches.
* Add missing #includes to fix kernel module build for ppc64el.
* Rename the internally used ARCH variable which might clash on externally
set values.
* Use substitutions for ${nvidia-kernel} and friends (510.108.03-1).
* Try to compile a kernel module at package build time (510.108.03-1).
.
nvidia-graphics-drivers (470.161.03-1) bullseye; urgency=medium
.
*
Bug#1024852: marked as done (nvidia-driver in bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1) do not support Linux kernel 6.0 or later)
Your message dated Sat, 10 Dec 2022 19:17:10 +
with message-id
and subject line Bug#1024852: fixed in nvidia-graphics-drivers 470.161.03-1
has caused the Debian Bug report #1024852,
regarding nvidia-driver in bullseye (470.141.03-1~deb11u1) and
bullseye-backports (470.103.01-1~bpo11+1) do not support Linux kernel 6.0 or
later
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.)
--
1024852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 470.103.01-1~bpo11+1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
About a week ago, linux-image-6.0.0-0.deb11.2-amd64 was introduced in
bullseye-backports. The problem is that the nvidia-driver version in both
bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1)
(for some reason, the version in bullseye is newer which is strange) DO NOT
support Linux kernel 6.0.
When a user who uses a backported linux kernel and nvidia-driver upgrades their
system, they will get an error message that looks like this
https://imgur.com/sEVx1vc (sorry if I couldn't give you the text output; I am
reporting this on behalf of a friend)
This issue is reproducable and happened on two of my friends' machines. We
found a current workaround that involves booting to kernel 5.1x in the Grub
menu, running sudo apt purge linux-image-6.0.0-0.deb11.2-amd64 && sudo apt
install -t bullseye-backports nvidia-driver && sudo reboot now.
According to this Phoronix article (
https://www.phoronix.com/news/NVIDIA-515.76-Linux-Driver ), nvidia-driver
515.76 or newer support Linux kernel 6.0. I believe the solution is to upgrade
nvidia-driver to 515.76 or newer in bullseye-backports so that users can use
their graphics card on kernel 6.0.
Thank you for reading my bug report and I hope you guys have a great day!
--
Alex Relis
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 470.161.03-1
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers, 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 1024...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated nvidia-graphics-drivers
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, 10 Dec 2022 00:52:57 +0100
Source: nvidia-graphics-drivers
Architecture: source
Version: 470.161.03-1
Distribution: bullseye
Urgency: medium
Maintainer: Debian NVIDIA Maintainers
Changed-By: Andreas Beckmann
Closes: 1020697 1021974 1022738 1024852 1025279
Changes:
nvidia-graphics-drivers (470.161.03-1) bullseye; urgency=medium
.
* New upstream production branch release 470.161.03 (2022-11-22).
* Fixed CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677,
CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254,
CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258,
CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262,
CVE-2022-42263, CVE-2022-42264. (Closes: #1025279)
https://nvidia.custhelp.com/app/answers/detail/a_id/5415
- Fixed a bug that caused the Xorg server to crash if an NvFBC capture
session is started while video memory is full.
* Improved compatibility with recent Linux kernels. (Closes: #1024852)
* New upstream Tesla release (amd64 only) 470.141.10 (2022-10-19).
.
[ Andreas Beckmann ]
* Refresh patches.
* Add missing #includes to fix kernel module build for ppc64el.
* Rename the internally used ARCH variable which might clash on externally
set values.
* Use substitutions for ${nvidia-kernel} and friends (510.108.03-1).
* Try to compile a kernel module at package build time (510.108.03-1).
* Upload to bullseye.
.
nvidia-graphics-drivers (470.141.03-3) UNRELEASED; urgency=medium
.
* Backport get_task_ioprio changes from 510.85.02, acpi changes from
510.85.02 and 515.65.01, drm_frambuffer.h changes from 515.76 to fix
kernel module buil
Bug#1014828: marked as done (openexr: CVE-2021-3933 CVE-2021-3941 CVE-2021-45942)
Your message dated Sat, 10 Dec 2022 19:17:13 + with message-id and subject line Bug#1014828: fixed in openexr 2.5.4-2+deb11u1 has caused the Debian Bug report #1014828, regarding openexr: CVE-2021-3933 CVE-2021-3941 CVE-2021-45942 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.) -- 1014828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openexr X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for openexr. CVE-2021-3933[0]: | An integer overflow could occur when OpenEXR processes a crafted file | on systems where size_t < 64 bits. This could cause an invalid | bytesPerLine and maxBytesPerLine value, which could lead to problems | with application stability or lead to other attack paths. https://bugzilla.redhat.com/show_bug.cgi?id=2019783 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=38912 Fixed by: https://github.com/AcademySoftwareFoundation/openexr/commit/5a0adf1aba7d41c6b94ba167c0c4308d2eecfd17 CVE-2021-3941[1]: | In ImfChromaticities.cpp routine RGBtoXYZ(), there are some division | operations such as `float Z = (1 - chroma.white.x - chroma.white.y) * | Y / chroma.white.y;` and `chroma.green.y * (X + Z))) / d;` but the | divisor is not checked for a 0 value. A specially crafted file could | trigger a divide-by-zero condition which could affect the availability | of programs linked with OpenEXR. https://bugzilla.redhat.com/show_bug.cgi?id=2019789 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=39084 https://github.com/AcademySoftwareFoundation/openexr/pull/1153 Fixed by: https://github.com/AcademySoftwareFoundation/openexr/commit/a0cfa81153b2464b864c5fe39a53cb03339092ed CVE-2021-45942[2]: | OpenEXR 3.1.x before 3.1.4 has a heap-based buffer overflow in | Imf_3_1::LineCompositeTask::execute (called from | IlmThread_3_1::NullThreadPoolProvider::addTask and | IlmThread_3_1::ThreadPool::addGlobalTask). NOTE: db217f2 may be | inapplicable. https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=41416 https://github.com/AcademySoftwareFoundation/openexr/pull/1209 https://github.com/AcademySoftwareFoundation/openexr/commit/11cad77da87c4fa2aab7d58dd5339e254db7937e If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-3933 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3933 [1] https://security-tracker.debian.org/tracker/CVE-2021-3941 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3941 [2] https://security-tracker.debian.org/tracker/CVE-2021-45942 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45942 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: openexr Source-Version: 2.5.4-2+deb11u1 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of openexr, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated openexr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 10 Dec 2022 15:03:52 CET Source: openexr Architecture: source Version: 2.5.4-2+deb11u1 Distribution: bullseye-security Urgency: high Maintainer: Debian PhotoTools Maintainers Changed-By: Markus Koschany Checksums-Sha1: 5e02983d0c476b13a5813ca3cbe07429d9862359 2467 openexr_2.5.4-2+deb11u1.dsc 13a75bed4e3bfc10ff1304599b8de3613844971b 27535491 openexr_2.5.4.orig.tar.gz 23b0c22a137c3d9dc2ccf99edcf62b4b45173605 25788 openexr_2.5.4-2+deb11u1.debian.tar.xz ddb131a8c56e364b77b28ba24dc6c4ccb3bbfef8 8662 openexr_2.5.4-2+deb11u1_amd64.buildinfo Checksums-Sha256: 2807eaffae0d6ffde4e5414bfdf3fb89c2216b46dda5d9e4daefd14236bec3c5 2467 openexr_2.5.4-2+deb11u1.dsc dba19e9c6720c6f64fbc8b9d1867eaa75da6438109b941eefdc75ed141b6576d 27535491 openexr_2.5.4.orig.tar.gz 83fba965ff63da0ba233b7cf7aca946e2
Bug#1025836: marked as done (byte-buddy: build-depends on dropped package)
Your message dated Sat, 10 Dec 2022 19:05:51 + with message-id and subject line Bug#1025836: fixed in byte-buddy 1.8.2-3 has caused the Debian Bug report #1025836, regarding byte-buddy: build-depends on dropped package 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.) -- 1025836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: byte-buddy Version: 1.8.2-2 Severity: serious Tags: bookworm, sid Justification: rc policy - "Packages must be buildable within the same release" User:debian...@lists.debian.org Usertags: edos-uninstallable byte-buddy build-depends on libasm-java-doc which is longer built by the asm source package. It is still present in unstable as a cruft package, but is completely gone from testing. This means that byte-buddy in testing is in violation of the rc policy. --- End Message --- --- Begin Message --- Source: byte-buddy Source-Version: 1.8.2-3 Done: tony mancill We believe that the bug you reported is fixed in the latest version of byte-buddy, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated byte-buddy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 10 Dec 2022 10:14:33 -0800 Source: byte-buddy Architecture: source Version: 1.8.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: tony mancill Closes: 1025836 Changes: byte-buddy (1.8.2-3) unstable; urgency=medium . * Team upload. * Drop javadoc package (Closes: #1025836) * Use debhelper-compat (=13) * Update Homepage URL * Set Rules-Requires-Root: no in debian/control * Bump Standards-Version to 4.6.1 * Freshen years in debian/copyright Checksums-Sha1: 7e2042657faa68df2bc90dda2a1f5db79101a488 2341 byte-buddy_1.8.2-3.dsc 8b38408ab8474b8053627cb8669a5d2294079bce 3584 byte-buddy_1.8.2-3.debian.tar.xz ecf08aaaf82b7c15a2ac9201620c33e131532cb4 14523 byte-buddy_1.8.2-3_amd64.buildinfo Checksums-Sha256: 7dfc4e40f25928174af7f5e768aaa5aa9a87951811cf987a4700f4f3bd94e9a7 2341 byte-buddy_1.8.2-3.dsc 7ca1db225bdc781ab5e57de2deb60f3824a5fd20e8ea8de2a85838e8f4b4a0a7 3584 byte-buddy_1.8.2-3.debian.tar.xz 30a423de66985798eb36ffba2bad3d1e23842c9815e5bd49cc9feed994582db4 14523 byte-buddy_1.8.2-3_amd64.buildinfo Files: 6555ccbee9d0dc19442d1066fe1d03ca 2341 java optional byte-buddy_1.8.2-3.dsc c72e12f2f879ef8305d7f45ba9227401 3584 java optional byte-buddy_1.8.2-3.debian.tar.xz 4159ab82e59c942b1b94207119ba4352 14523 java optional byte-buddy_1.8.2-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmOU07sUHHRtYW5jaWxs QGRlYmlhbi5vcmcACgkQIdIFiZdLPpZkDA//TjkQQcE8uEGoZAEvQ6dTEO63btIl /lD27+7Z7fbdlUTwRjuq0mQ9VuckBa/DBliG5HGOn2KW94bitfgcAuidxnzo+UYG nOog5KGxeFm0uOU6+1q1sIQA9TM/aQ9tfWyn2nia68cc0F9ScTaRJ6ooYyUdImFm 9rX5zOgxhLJihbC+Cq3rha3lhFP4Mftorcu/6slxlfgNDmD3cH2BQS1B9ewbbLDG kka6/tOwNccCGQqAZ2oScF2II+iRiGFtO5NI/FpfVHtYadlyYBo+dv4TSAIiMaRm 6yAL8bYi+4blqcDD+KSRJ8TmFg4uWrkAfLw6j0ei4TY6TA0VA0No2lE2s38qTV1k MKi7PMzrd1Ovh1jL9Jx3yp2eGsFfB3oPykJMx9OhiP/fh0MkDzAy9l+9GeZM7HYo 6HIHsaIpJ7eTlWmjKOW6tvsE5Gv4ZvTOYRFhAiuLYHEmVcCi5B2aooPZy7OAW1qR lRSdpy+QsCRLbq9rYnRBPaU6xA5XuYLOw4+/1UU0qeG+X0IXxIO0NQLVv/QLjv8a FjE+TERWZEdVB/MaBA//AD2bRBJ0SAecSKRTscnYD8GtAa78bnVDZpag7+WtCjNd GS6M6oqrTzhCB3GFdf2wIFCYcd7yyS31FhXoY90XrHFzsnyiBD4ua7tPpDUCshtf YRPozS2NtTZ3A5U= =pDBm -END PGP SIGNATURE End Message ---
Bug#988462: marked as done (trac: not ready for Debian 11)
Your message dated Sat, 10 Dec 2022 19:57:50 +0100 with message-id and subject line Re: Thank you has caused the Debian Bug report #988462, regarding trac: not ready for Debian 11 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.) -- 988462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: trac Version: 1.5.2+dfsg-2 Severity: serious IMHO, the current version of Trac is not suitable for including it in a stable release. I'll try to provide backports of future version 1.6.x for Debian 11. --- End Message --- --- Begin Message --- Closing in favour of #1024647 which is a more specific blocker for the python3 version.--- End Message ---
Processed: untag non-affected releases
Processing commands for cont...@bugs.debian.org: > tags 1008502 - bookworm sid Bug #1008502 [vdirsyncer] vdirsyncer: Unknown error occured: unmatched ')' Removed tag(s) sid and bookworm. > retitle 1008502 vdirsyncer: Fix "Unknown error occured: unmatched ')'" on > bullseye Bug #1008502 [vdirsyncer] vdirsyncer: Unknown error occured: unmatched ')' Changed Bug title to 'vdirsyncer: Fix "Unknown error occured: unmatched ')'" on bullseye' from 'vdirsyncer: Unknown error occured: unmatched ')''. > End of message, stopping processing here. Please contact me if you need assistance. -- 1008502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: RabbitVCS status?
Processing control commands: > severity -1 important Bug #979257 [rabbitvcs-gedit] rabbitvcs-gedit plugin does not load on gedit 3.8+ Severity set to 'important' from 'grave' -- 979257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979257: RabbitVCS status?
Control: severity -1 important On Mon, 21 Nov 2022 14:19:30 + Jelmer =?utf-8?Q?Vernoo=C4=B3?= wrote: tags 979257 +upstream forwarded 979257 https://github.com/rabbitvcs/rabbitvcs/issues/34 thanks There doesn't appear to be much movement on this at all in upstream, the bug has been open since 2014. There is other upstream activity though. Perhaps the best approach would be to drop this specific binary package for bookworm. This was already marked as fixed and I cannot reproduce the error description: "the plugin stays grayed out, the tooltip shows an error message (missing loader)". Would you please provide more info?
Processed: fixed 1023989 in 0.10.5-1
Processing commands for cont...@bugs.debian.org: > fixed 1023989 0.10.5-1 Bug #1023989 [pantalaimon] pantalaimon: Does not support current versions of Synapse Marked as fixed in versions pantalaimon/0.10.5-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1023989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1023971 is serious
Processing commands for cont...@bugs.debian.org: > severity 1023971 serious Bug #1023971 [pantalaimon] pantalaimon: Missing dependency on python3-pydbus Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1023971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: cpm: diff for NMU version 0.32-1.5
Processing control commands: > tags 1023917 + pending Bug #1023917 [cpm] cpm: FTBFS against libgpgme-dev >= 1.18.0-2 [checking for gpgme-config... no] Added tag(s) pending. -- 1023917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023917: cpm: diff for NMU version 0.32-1.5
Control: tags 1023917 + pending
Dear maintainer,
I've prepared an NMU for cpm (versioned as 0.32-1.5) and uploaded
it to DELAYED/12. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru cpm-0.32/debian/changelog cpm-0.32/debian/changelog
--- cpm-0.32/debian/changelog 2022-03-27 14:15:18.0 +0300
+++ cpm-0.32/debian/changelog 2022-12-10 19:42:45.0 +0200
@@ -1,3 +1,11 @@
+cpm (0.32-1.5) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add patch from Andreas Metzler to find gpgme using pkgconf.
+(Closes: #1023917)
+
+ -- Adrian Bunk Sat, 10 Dec 2022 19:42:45 +0200
+
cpm (0.32-1.4) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru cpm-0.32/debian/patches/gpgme-locate-pkgconf.patch cpm-0.32/debian/patches/gpgme-locate-pkgconf.patch
--- cpm-0.32/debian/patches/gpgme-locate-pkgconf.patch 1970-01-01 02:00:00.0 +0200
+++ cpm-0.32/debian/patches/gpgme-locate-pkgconf.patch 2022-12-10 19:18:36.0 +0200
@@ -0,0 +1,34 @@
+--- cpm-0.32.orig/configure.in
cpm-0.32/configure.in
+@@ -353,29 +353,12 @@ PKG_CHECK_MODULES([LIBXML], [libxml-2.0]
+ LIBXML_XMLLINT="$exec_prefix/bin/xmllint"
+ AC_SUBST(LIBXML_XMLLINT)
+
+-AC_PATH_PROG([GPGME_CONFIG], [gpgme-config])
+-if test -z "$ac_cv_path_GPGME_CONFIG"; then
+- AC_MSG_ERROR([Could not find gpgme anywhere.])
+-fi
+-
+-LIBGPGME_VERSION="`$GPGME_CONFIG --version | cut -d '.' -f 1,2 | sed -e 's/\\.//g'`"
+-if test $LIBGPGME_VERSION -lt 10; then
+- AC_MSG_ERROR([GPGME must be version 1.0 or higher.])
+-fi
+-if test $LIBGPGME_VERSION -lt 11; then
+- AC_MSG_NOTICE([GpgME version lower than 1.1 found, recipients can't be detected automatically.])
+- WRAPPER_NECESSARY=1
+-else
+- AC_MSG_NOTICE([GpgME version 1.1+ found. Enabling automatic recipient detection.])
++PKG_CHECK_MODULES([LIBGPGME], [gpgme >= 1.1.0],
+ CFLAGS="${CFLAGS} -DGPGME_HAS_RECIPIENT"
+ WRAPPER_NECESSARY=0
+-fi
++)
+ AC_SUBST(WRAPPER_NECESSARY)
+
+-LIBGPGME_LIBS="`$GPGME_CONFIG --libs`"
+-LIBGPGME_CFLAGS="-D_FILE_OFFSET_BITS=64 `$GPGME_CONFIG --cflags`"
+-AC_SUBST(LIBGPGME_LIBS)
+-AC_SUBST(LIBGPGME_CFLAGS)
+
+ # --
+
diff -Nru cpm-0.32/debian/patches/series cpm-0.32/debian/patches/series
--- cpm-0.32/debian/patches/series 2022-03-26 13:22:26.0 +0200
+++ cpm-0.32/debian/patches/series 2022-12-10 19:38:02.0 +0200
@@ -1,3 +1,4 @@
fix-ftbfs-gcc-10.patch
libxml2.patch
posix-configure-in.patch
+gpgme-locate-pkgconf.patch
Bug#1025777: marked as done (qcustomplot: autopkgtest regression: collect2: error: ld returned 1 exit status)
Your message dated Sat, 10 Dec 2022 17:35:25 + with message-id and subject line Bug#1025777: fixed in qcustomplot 2.1.0+dfsg1-3.1 has caused the Debian Bug report #1025777, regarding qcustomplot: autopkgtest regression: collect2: error: ld returned 1 exit status to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1025777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025777 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qcustomplot Version: 2.1.0+dfsg1-3 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of qcustomplot the autopkgtest of qcustomplot fails in testing when that autopkgtest is run with the binary packages of qcustomplot from unstable. It passes when run with only packages from testing. In tabular form: passfail qcustomplotfrom testing2.1.0+dfsg1-3 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=qcustomplot https://ci.debian.net/data/autopkgtest/testing/amd64/q/qcustomplot/29128978/log.gz -- The CXX compiler identification is GNU 12.2.0 -- 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 -- Configuring done -- Generating done -- Build files have been written to: /tmp/tmp.nJIgKdAyYp/build [ 16%] Automatic MOC and UIC for target plots [ 16%] Built target plots_autogen [ 33%] Building CXX object CMakeFiles/plots.dir/plots_autogen/mocs_compilation.cpp.o [ 50%] Building CXX object CMakeFiles/plots.dir/main.cpp.o [ 66%] Building CXX object CMakeFiles/plots.dir/mainwindow.cpp.o [ 83%] Building CXX object CMakeFiles/plots.dir/axistag.cpp.o [100%] Linking CXX executable plots /usr/bin/ld: CMakeFiles/plots.dir/mainwindow.cpp.o: in function `MainWindow::MainWindow(QWidget*)': mainwindow.cpp:(.text+0x13e): undefined reference to `QCustomPlot::QCustomPlot(QWidget*)' /usr/bin/ld: mainwindow.cpp:(.text+0x182): undefined reference to `QCPAxis::setTickLabels(bool)' /usr/bin/ld: mainwindow.cpp:(.text+0x1eb): undefined reference to `QCPLayerable::setVisible(bool)' /usr/bin/ld: mainwindow.cpp:(.text+0x203): undefined reference to `QCustomPlot::axisRect(int) const' /usr/bin/ld: mainwindow.cpp:(.text+0x215): undefined reference to `QCPAxisRect::addAxis(QCPAxis::AxisType, QCPAxis*)' /usr/bin/ld: mainwindow.cpp:(.text+0x22d): undefined reference to `QCustomPlot::axisRect(int) const' /usr/bin/ld: mainwindow.cpp:(.text+0x23f): undefined reference to `QCPAxisRect::axis(QCPAxis::AxisType, int) const' /usr/bin/ld: mainwindow.cpp:(.text+0x24c): undefined reference to `QCPAxis::setPadding(int)' /usr/bin/ld: mainwindow.cpp:(.text+0x264): undefined reference to `QCustomPlot::axisRect(int) const' /usr/bin/ld: mainwindow.cpp:(.text+0x276): undefined reference to `QCPAxisRect::axis(QCPAxis::AxisType, int) const' /usr/bin/ld: mainwindow.cpp:(.text+0x283): undefined reference to `QCPAxis::setPadding(int)' /usr/bin/ld: mainwindow.cpp:(.text+0x2a6): undefined reference to `QCustomPlot::axisRect(int) const' /usr/bin/ld: mainwindow.cpp:(.text+0x2b8): undefined reference to `QCPAxisRect::axis(QCPAxis::AxisType, int) const' /usr/bin/ld: mainwindow.cpp:(.text+0x2d5): undefined reference to `QCustomPlot::addGraph(QCPAxis*, QCPAxis*)' /usr/bin/ld: mainwindow.cpp:(.text+0x311): undefined reference to `QCustomPlot::axisRect(int) const' /usr/bin/ld: mainwindow.cpp:(.text+0x323): undefined reference to `QCPAxisRect::axis(QCPAxis::AxisType, int) const' /usr/bin/ld: mainwindow.cpp:(.text+0x340): undefined reference to `QCustomPlot::addGraph(QCPAxis*, QCPAxis*)' /usr/bin/ld: mainwindow.cpp:(.text+0x3b2): undefined reference to `QCPAbstractPlottable::setPen(QPen const&)' /usr/bin/ld: mainwindow.cpp:(.text+0x417): undefined reference to `QCPAbstractPlottable::setPen(QPen const&)' /usr/bin/ld: CMakeFiles/plots.dir/mainwindow.cpp.o: in function `MainWindow::timerSlot()': mainwindow.cpp:(.text+0x884): undefined reference to `QCPGraph::addData(double, double)' /usr/bin/ld: mainwindow.cpp:(.text+0x991): undefined reference to `QCPGra
Processed: owner 1025836
Processing commands for cont...@bugs.debian.org: > owner 1025836 ! Bug #1025836 [src:byte-buddy] byte-buddy: build-depends on dropped package Owner recorded as tony mancill . > thanks Stopping processing here. Please contact me if you need assistance. -- 1025836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025836: byte-buddy: build-depends on dropped package
Hi Peter, On Sat, Dec 10, 2022 at 09:17:50AM +, Peter Green wrote: > Source: byte-buddy > Version: 1.8.2-2 > Severity: serious > Tags: bookworm, sid > Justification: rc policy - "Packages must be buildable within the same > release" > User:debian...@lists.debian.org > Usertags: edos-uninstallable > > byte-buddy build-depends on libasm-java-doc which is longer built by the asm > source > package. It is still present in unstable as a cruft package, but is > completely gone > from testing. This means that byte-buddy in testing is in violation of the rc > policy. Thank you for the bug report. I will upload an update to byte-buddy that drops its -doc package, and since nothing depends on it, that should stop the cascade... $ reverse-depends -b libbyte-buddy-java-doc No reverse dependencies found Cheers, tony
Bug#1025406: tpm2-pytss: FTBFS in sid
On Tue, 6 Dec 2022 13:39:32 +0100 Claudius Heine wrote: I created a MR to tpm2-tss to add these missing files: https://salsa.debian.org/debian/tpm2-tss/-/merge_requests/7 As long as this is not merged you should disable running test_fapi.py.
Bug#1025777: qcustomplot: autopkgtest regression: collect2: error: ld returned 1 exit status
Re: Paul Gevers > With a recent upload of qcustomplot the autopkgtest of qcustomplot fails in > testing when that autopkgtest is run with the binary packages of qcustomplot > from unstable. I uploaded the pending changes as an NMU, plus ignoring a compiler warning on stderr: [ 66%] Building CXX object CMakeFiles/plots.dir/mainwindow.cpp.o /tmp/tmp.T3AXT8d62g/src/mainwindow.cpp: In member function ‘void MainWindow::on_actionSave_Document_triggered()’: /tmp/tmp.T3AXT8d62g/src/mainwindow.cpp:127:59: warning: ‘QRect QPrinter::pageRect() const’ is deprecated: Use pageLayout().paintRectPixels(resolution()) instead. [-Wdeprecated-declarations] 127 | ui->textEdit->document()->setPageSize(printer.pageRect().size()); | ^~ In file included from /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport/qprintengine.h:45, from /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport/QtPrintSupport:14, from /usr/include/qcustomplot.h:97, from /tmp/tmp.T3AXT8d62g/src/qcpdocumentobject.h:34, from /tmp/tmp.T3AXT8d62g/src/mainwindow.h:32, from /tmp/tmp.T3AXT8d62g/src/mainwindow.cpp:26: /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport/qprinter.h:259:11: note: declared here 259 | QRect pageRect() const; | ^~~~ [ 83%] Building CXX object CMakeFiles/plots.dir/qcpdocumentobject.cpp.o NMU diff: https://salsa.debian.org/science-team/qcustomplot/-/merge_requests/5 Christoph
Bug#1022469: marked as done (python-pint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13)
Your message dated Sat, 10 Dec 2022 17:22:21 +
with message-id
and subject line Bug#1022469: fixed in python-pint 0.18-2
has caused the Debian Bug report #1022469,
regarding python-pint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-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.)
--
1022469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pint
Version: 0.18-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/__init__.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/registry.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/matplotlib.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/formatting.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/converters.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/util.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/errors.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/quantity.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/registry_helpers.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/definitions.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/babel_names.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/compat.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/numpy_func.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/context.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/_typing.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/measurement.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/unit.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/pint_eval.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> copying pint/systems.py ->
> /<>/.pybuild/cpython3_3.10_pint/build/pint
> running egg_info
> creating Pint.egg-info
> writing Pint.egg-info/PKG-INFO
> writing dependency_links to Pint.egg-info/dependency_links.txt
> writing requirements to Pint.egg-info/requires.txt
> writing top-level names to Pint.egg-info/top_level.txt
> writing manifest file 'Pint.egg-info/SOURCES.txt'
> reading manifest file 'Pint.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'BADGES.rst'
> warning: no files found matching 'version.txt'
> warning: no files found matching '*' under directory 'bench'
> no previously-included directories found matching 'docs/_build'
> no previously-included directories found matching 'docs/_themes/.git'
> warning: no previously-included files found matching '.editorconfig'
> warning: no previously-included files found matching 'bors.toml'
> warning: no previously-included files found matching
> 'pull_request_template.md'
> warning: no previously-included files found matching 'requirements_docs.txt'
> warning: no previously-included files found matching 'version.py'
> warning: no previously-included files matching '*.pyc' found anywhere in
> distribution
> warning: no previously-included files matching '*~' found anywhere in
> distribution
> warning: no previously-included files matching '.DS_Store' found anywhere in
> distribution
> warning: no previously-included files matching '*__pycache__*' found anywhere
> in distribution
> warning: no previously-included files matching '*.pyo' found anywhere in
> distribution
> warning: no previously-included files matching '.travis-exclude.yml' found
> anywhere in distribution
> adding license file 'LICENSE'
> adding license file 'AUTHORS'
> writing manifest file 'Pint.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202:
> SetuptoolsDeprecationWarning: Installing 'pint.testsuite' as dat
Bug#1025835: tiledb-py: build-depends on libtiledb-doc
On Sat, Dec 10, 2022 at 07:56:52AM -0600, Dirk Eddelbuettel wrote: > > On 10 December 2022 at 09:07, Peter Green wrote: > | Source: tiledb-py > | Version: 0.18.2-1 > | Severity: serious > | Justification: rc policy - "Packages must be buildable within the same > release" > | x-debbugs-cc: e...@debian.org > | User: debian...@lists.debian.org > | Usertags: edos-uninstallable > | > | tiledb-py build-depends on libtiledb-doc, which is no longer built by > tiledb since > | version 2.13.0-1, this removal is no mentioned in the changelog, so it's > not clear to me > | if it was deliberate or not. It is still present in unsable as a cruft > package, but is > | completely gone from testing. This means that tiledb-py in testing is in > violation of > | the rc policy. > > Good catch but that was in fact deliberate. > > The build (of a package I inherited / adopted) was giving me fits, and I as > maintainer have decided to follow a) upstreams preference for documentation > on the websites and b) simplify the build. While this is an acceptable stance, I'd really prefer if you consider to keep vendoring the documentation. I have seen a number of bug reports and also heard from many people that they'd like to have a copy of documentation offline as well, as it a) enables to work when internet is spotty for them b) Look up everything offline instead of the online source as the docs contain API that correspond to the relevant version. I understand that vendoring documentation could be extra work, but if vendoring it is not a source of nuisance for each and every update, and the build rules are constant then I don't see a lot of issue with it. For your case, did you have any particular issues/build failures while vendoring the documentation? Also, I know that you understand tiledb far better than I do, but still I'd like to offer my help for this issue, should you like it, and if you help me understand where exactly it crossed the threshold for maintainer-time-well-spent. > We should adjust tiledb-py This is easy enough to do, which would mean removing doc package from tiledb-py as well. But again, I'd like to do this only after I hear back from you. > (which needs an update for the now released 0.19.0 > anyway, and had skipped minor release 0.18.3 which is ok) accordingly. Thanks for the ping. I work on hunderds of packages and I tend to skip updates so this is helpful. -- Best, Nilesh signature.asc Description: PGP signature
Bug#1025849: marked as done (cloud-initramfs-growroot - silently breaks initramfs build)
Your message dated Sat, 10 Dec 2022 16:34:04 + with message-id and subject line Bug#1025849: fixed in cloud-initramfs-tools 0.18.debian11 has caused the Debian Bug report #1025849, regarding cloud-initramfs-growroot - silently breaks initramfs build 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.) -- 1025849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cloud-initramfs-growroot Version: 0.18.debian10 Severity: grave Installation of new kernel now silently fails: | Setting up linux-image-6.0.0-5-cloud-arm64 (6.0.10-2) ... | /etc/kernel/postinst.d/initramfs-tools: | update-initramfs: Generating /boot/initrd.img-6.0.0-5-cloud-arm64 | W: No zstd in /usr/bin:/sbin:/bin, using gzip | E: /usr/share/initramfs-tools/hooks/growroot failed with return 1. | update-initramfs: failed for /boot/initrd.img-6.0.0-5-cloud-arm64 with 1. | run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Bastian -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (700, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-0-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cloud-initramfs-growroot depends on: pn cloud-utils ii fdisk2.38.1-4 ii initramfs-tools 0.142 ii util-linux 2.38.1-4 cloud-initramfs-growroot recommends no packages. cloud-initramfs-growroot suggests no packages. --- End Message --- --- Begin Message --- Source: cloud-initramfs-tools Source-Version: 0.18.debian11 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of cloud-initramfs-tools, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated cloud-initramfs-tools 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, 10 Dec 2022 17:15:20 +0100 Source: cloud-initramfs-tools Architecture: source Version: 0.18.debian11 Distribution: unstable Urgency: medium Maintainer: Debian Cloud Changed-By: Thomas Goirand Closes: 1025849 Changes: cloud-initramfs-tools (0.18.debian11) unstable; urgency=medium . * Fix copy_exec /usr/bin/udevadm /sbin (Closes: #1025849). Checksums-Sha1: 5f298cb5b76d6a44e63031ce5e5292619c9ee679 2032 cloud-initramfs-tools_0.18.debian11.dsc 3f65d8efd42206ec02c1b1d8b5b1476034889e2c 33640 cloud-initramfs-tools_0.18.debian11.tar.xz 5f8e32ecaefd46a8f15dd5b70e3fa5bf42c45f5b 7375 cloud-initramfs-tools_0.18.debian11_amd64.buildinfo Checksums-Sha256: 34fcf570ad684a0661c894a0a61df40912bb69fc5d56aad3803d2bf08e467bf6 2032 cloud-initramfs-tools_0.18.debian11.dsc 303afeaebf9c69c7c7a85221f6df96edaed820df36614508bb0b90b35bcac641 33640 cloud-initramfs-tools_0.18.debian11.tar.xz fff74672a2378881d0104990a62b99d8d14ccb38d458b711cdcca0d5b69b81a1 7375 cloud-initramfs-tools_0.18.debian11_amd64.buildinfo Files: b9696c70aab5a68c5c33cb128deb4a5e 2032 admin optional cloud-initramfs-tools_0.18.debian11.dsc 553b5ca5426c9c47e5d01ca7cd2099f8 33640 admin optional cloud-initramfs-tools_0.18.debian11.tar.xz fc631c8b99387fd723407e86798fd8ab 7375 admin optional cloud-initramfs-tools_0.18.debian11_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmOUsRsACgkQ1BatFaxr Q/44Vw/8CppStsOHIVjUdBd2ZCUSggzM3GAzpfkoe/SdLhd9lMnBp9lObYUcYao/ duiD8sFWKmQJgormxAXVu83/yHDer2m+k6T1sD69asOcG0bYO5BxZuHG1J3qcbuU 9CZYRXOnEvwOdL2qgNsp+fNhGePLXPpiNj/gdzSkqtOncCatEaqsOrVvQZksaRe6 5gMn1EOr6Fjt+CT8/I2wktzRqe6pVIa3eJHjFuLGmtU2HoEfRXOz97rlhtIVTY06 oTSbArYdSmK6cllMT/kNB2CcV9GU9S/Lpfelf5Tw8nTBfn+jCqg0Qg3GwLacqyiV OHVmr8IsrpsCVkAeJbVvprtZ11YNi01GvCMKbCl80p5Pf/03kuTkVeAU6SQYpB2m ccJ9/ZKor4dJ5B6Yr+FZ36JQ4btP/MHTGNnojo7ALqqRNuRp2gaUu3t/VHVDaJ+d 9qXyVLbrZ8yugprsiFn0YaSmbtaiaqRzVxtOu7y4A/P2MqH37kY1lr5F5ajPsO
Processed: Bug#1022469 marked as pending in python-pint
Processing control commands:
> tag -1 pending
Bug #1022469 [src:python-pint] python-pint: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.10 returned exit code 13
Added tag(s) pending.
--
1022469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1022469: marked as pending in python-pint
Control: tag -1 pending Hello, Bug #1022469 in python-pint 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-pint/-/commit/0d02fa6dda9d8af131cc76969ecca20efafb2975 Support babel > 2.8 (Closes: #1022469) (this message was generated automatically) -- Greetings https://bugs.debian.org/1022469
Bug#1024906: marked as done (dask: (autopkgtest) needs update for python3.11: Attribute "dtype" are different)
Your message dated Sat, 10 Dec 2022 17:01:36 +0100
with message-id <05d7f585-3de4-f15c-53ef-500edbddd...@debian.org>
and subject line apparently fixed Re: dask autopkgtest fail with python 3.11
has caused the Debian Bug report #1024906,
regarding dask: (autopkgtest) needs update for python3.11: Attribute "dtype"
are different
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.)
--
1024906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dask
Version: 2022.02.0+dfsg-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python3.11 as a supported Python
version [0]. With a recent upload of python3-defaults the autopkgtest of
dask fails on armhf and i386 in testing when that autopkgtest is run
with the binary packages of python3-defaults from unstable. It passes
when run with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.10.6-3
dask from testing2022.02.0+dfsg-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists
what's new in Python3.11, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/armhf/d/dask/28718535/log.gz
=== FAILURES
===
_ test_query_with_meta
_
db = 'sqlite:tmp/tmpyge_bwo2.'
def test_query_with_meta(db):
from sqlalchemy import sql
data = {
"name": pd.Series([], name="name", dtype="str"),
"age": pd.Series([], name="age", dtype="int"),
}
index = pd.Index([], name="number", dtype="int")
meta = pd.DataFrame(data, index=index)
s1 = sql.select(
[sql.column("number"), sql.column("name"), sql.column("age")]
).select_from(sql.table("test"))
out = read_sql_query(s1, db, npartitions=2, index_col="number",
meta=meta)
# Don't check dtype for windows
https://github.com/dask/dask/issues/8620
assert_eq(out, df[["name", "age"]], check_dtype=sys.int_info.sizeof_digit
!= 2)
/usr/lib/python3/dist-packages/dask/dataframe/io/tests/test_sql.py:443:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
a =name age
number 0 Alice 33
1 Bob 40
2 Chris 22
3 Dora 16
4 Edith 53
5 Francis 30
6 Garreth 20
b =name age
number 0 Alice 33
1 Bob 40
2 Chris 22
3 Dora 16
4 Edith 53
5 Francis 30
6 Garreth 20
check_names = True, check_dtype = True, check_divisions = True
check_index = True, scheduler = 'sync', kwargs = {}
def assert_eq(
a,
b,
check_names=True,
check_dtype=True,
check_divisions=True,
check_index=True,
scheduler="sync",
**kwargs,
):
if check_divisions:
assert_divisions(a, scheduler=scheduler)
assert_divisions(b, scheduler=scheduler)
if hasattr(a, "divisions") and hasattr(b, "divisions"):
at = type(np.asarray(a.divisions).tolist()[0]) # numpy
to python
bt = type(np.asarray(b.divisions).tolist()[0]) #
scalar conversion
assert at == bt, (at, bt)
assert_sane_keynames(a)
assert_sane_keynames(b)
a = _check_dask(
a, check_names=check_names, check_dtypes=check_dtype,
scheduler=scheduler
)
b = _check_dask(
b, check_names=check_names, check_dtypes=check_dtype,
scheduler=scheduler
)
if hasattr(a, "to_pandas"):
a = a.to_pandas()
if hasattr(b, "to_pandas"):
b = b.to_pandas()
if isinstance(a, (pd.D
Bug#1025661: marked as done (rust-plotters: invalid Uploaders field: missing comma between Jelmer Vernooij and Blair Noctis)
Your message dated Sat, 10 Dec 2022 15:53:49 + with message-id and subject line Bug#1025661: fixed in rust-plotters 0.3.4-3 has caused the Debian Bug report #1025661, regarding rust-plotters: invalid Uploaders field: missing comma between Jelmer Vernooij and Blair Noctis 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.) -- 1025661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-plotters Version: 0.3.4-1 Severity: serious rust-plotters 0.3.4-1 introduced an invalid Uploaders field, that is missing a comma between Jelmer Vernooij and Blair Noctis. $ apt-cache showsrc rust-plotters | grep -E '^$|^Version|^Uploaders' Version: 0.3.4-1 Uploaders: Jelmer Vernooij Blair Noctis According to Debian policy 5.6.3 the Uploaders field must separate individual uploaders using commas: List of the names and email addresses of co-maintainers of the package, if any. ... The format of each entry is the same as that of the Maintainer field, and multiple entries must be comma separated. https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders This is causing the DDPO and BLS cron jobs to send error mails, please fix it as soon as possible. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: rust-plotters Source-Version: 0.3.4-3 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-plotters, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-plotters 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, 10 Dec 2022 15:27:12 + Source: rust-plotters Architecture: source Version: 0.3.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1025661 Changes: rust-plotters (0.3.4-3) unstable; urgency=medium . * Team upload. * Package plotters 0.3.4 from crates.io using debcargo 2.6.0 * Really fix the author list (Closes: #1025661) Checksums-Sha1: 56d9f21ed4cc99369a2f922775890efccd9ebe82 3181 rust-plotters_0.3.4-3.dsc 3b65611c642e84fb18e82306b1069e7ff19ac3e3 4688 rust-plotters_0.3.4-3.debian.tar.xz 07233c159b9842742a49922e21d55d3ec6402944 11540 rust-plotters_0.3.4-3_source.buildinfo Checksums-Sha256: b90d3e2e77357a2812294e8c9be51f50cbc39719681f57745e7eae844615c9dc 3181 rust-plotters_0.3.4-3.dsc 2b3d5828bb3b716f57d52fa64dca8de74f8337b8e2c64ae86d0c82fcdf20b07e 4688 rust-plotters_0.3.4-3.debian.tar.xz b5f7664d2cefea8aaa2ed6ef27a041aa65536f63ecbbd554a4128c406e81 11540 rust-plotters_0.3.4-3_source.buildinfo Files: 16de7674d74347d5ead8bb68be601a89 3181 rust optional rust-plotters_0.3.4-3.dsc 70d7657edc52324fb24d965d8265e466 4688 rust optional rust-plotters_0.3.4-3.debian.tar.xz 29fc14c7784da0b8c216d3aeb0b21164 11540 rust optional rust-plotters_0.3.4-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmOUpcEUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvS4w/8D84qsUYqg6i2bivXBycIwPzwQqlv dqWPPrlSh1m6OOBLqTXB32tk68QpyoH3fJokeAQmwCvgNNJd/5cbUwLQ7u0KlqRw oDw3VvyvCQLpUy8Tzen3GeJNiKs5mBy2YoUkDp8/5qMIZn/FAqdP6hhO1ASjiTtd PxwHmH77r8kHFs8Re8HmwwSmPzW+8qm8qHQJ/okeeTm3QFHdWUkm1fG6ITAkkreg pFsXIX+TfSSmWoHNiJd2YL04dvu8D8h/DXffj10Ns/K+20jCfOtj3MUYbw25OM77 lJ2W2GM9uPy48I2Rl79S8epGO/UCrGP2lEx6tZfXSBrbscU6YYJdJ/0Bp9iqztZg WvJbfTUnLaHbtL3Nk5/7rshGTIqND2rQierlRqU4YDQqePD4lNYeKkDzNJqKy8Fz zED0yBAx/njZFWe3n0yiJuGIR4bRfzm9TnA+WdqJhH7PnVeXEX4gP0GdyKswWYfx bqwPRlveYeW1ApT/L5bK1WI57pWgf9bQvN/gdyxyg43KKAt94qftXielrb4KHSHn 6MNKYMwXXE31xogZn8Yq710cy9mIEoo9JhvI0kqvlrKbEmtBcmK0XNaiv9CRNtRZ ROMNuCkP1KOmTkw+T7fo7Y09RjcV/AQPgOAvvrzyEikHWqMGmzgEZBbwYanhNZtO ZjNbYE4//Gh/bBM= =ygFC -END PGP SIGNATURE End Message ---
Bug#994212: marked as done (ROM: r-cran-gprofiler: Obsolete package, replaced with r-cran-gprofiler2)
Your message dated Sat, 10 Dec 2022 14:52:53 + with message-id and subject line Bug#994212: Removed package(s) from unstable has caused the Debian Bug report #994212, regarding ROM: r-cran-gprofiler: Obsolete package, replaced with r-cran-gprofiler2 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.) -- 994212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: r-cran-gprofiler Version: 0.7.0-2 Severity: serious X-Debbugs-Cc: nil...@debian.org Dear Maintainer, r-cran-gprofiler has been replaced with r-cran-gprofiler2 and hence the former should be kept out of testing. Cheers, -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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 r-cran-gprofiler depends on: ii r-base-core [r-api-4.0] 4.0.4-1 pn r-cran-plyr pn r-cran-rcurl r-cran-gprofiler recommends no packages. r-cran-gprofiler suggests no packages. --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: r-cran-gprofiler |0.7.0-2 | source, all --- Reason --- RoM; Obsolete package replaced by r-cran-gprofiler2 -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember 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. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 994...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/994212 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#1025311: marked as done (solvespace: missing builds on mipsel and mips64el)
Your message dated Sat, 10 Dec 2022 14:52:43 + with message-id and subject line Bug#1025311: fixed in solvespace 3.1+ds1-3 has caused the Debian Bug report #1025311, regarding solvespace: missing builds on mipsel and 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.) -- 1025311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: solvespace Version: 3.1+ds1-2 Severity: serious Tags: ftbfs Hi Maintainer The upload of solvespace 3.1+ds1-2 includes the change 'Drop s390x architecture due to test failures' [1], however the way this was done didn't only drop s390x, but also mipsel, mips64el, riscv64 and several other ports. The missing builds on mipsel and mips64el now prevent migration of solvespace to testing. Seeing that solvespace builds fine on s390x, if the failing tests cannot be fixed, you could skip them on s390x only. See my proposed debian/tests/control file below. You could also try asking on debian-s...@lists.debian.org for help. Regards Graham [1] https://salsa.debian.org/science-team/solvespace/-/commit/660e95c1d4583e078e31c5f91e7cd57f1aa1c7d1 Tests: htmlmesh stlmesh surfaces Restrictions: allow-stderr Depends: solvespace, findutils, grep Architecture: !s390x Tests: thumbnail view wireframe Restrictions: allow-stderr Depends: solvespace, findutils, grep --- End Message --- --- Begin Message --- Source: solvespace Source-Version: 3.1+ds1-3 Done: Ryan Pavlik We believe that the bug you reported is fixed in the latest version of solvespace, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ryan Pavlik (supplier of updated solvespace package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 07 Dec 2022 16:25:41 -0600 Source: solvespace Architecture: source Version: 3.1+ds1-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Ryan Pavlik Closes: 1025311 Changes: solvespace (3.1+ds1-3) unstable; urgency=medium . * Team upload. * Restore architectures, and just exclude s390x from affected tests. Thanks to Graham Inggs. Closes: #1025311 Checksums-Sha1: 0af40301afafdb4db8b5deb293596a6105166d69 2212 solvespace_3.1+ds1-3.dsc 84eedeb3648ab1aa1937334171e279211b227a05 27776 solvespace_3.1+ds1-3.debian.tar.xz 37cf641b00682c6836277ab2a003df5320014ab7 15107 solvespace_3.1+ds1-3_source.buildinfo Checksums-Sha256: caa71be567ab4dc07c50e21d12bc118793db77296c517e84b427dd18562bd514 2212 solvespace_3.1+ds1-3.dsc f873c077278c5383c043cc42374a09f317855f263bc58c9deede99a00b7d215a 27776 solvespace_3.1+ds1-3.debian.tar.xz b0a6e2fa1d93370a31abc124649c66f5f756f3416ab0a06c373c646c1d241522 15107 solvespace_3.1+ds1-3_source.buildinfo Files: 4dc4a23bc1fa896b93c6595fde6a45ea 2212 graphics optional solvespace_3.1+ds1-3.dsc 3f1555c9263814c759521a64f96d16b3 27776 graphics optional solvespace_3.1+ds1-3.debian.tar.xz 4497c211d8225b3f58f1e01e63ae9b80 15107 graphics optional solvespace_3.1+ds1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmOUj9IQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFAj9C/4nWXS+A4kracT/3Nxm+9wOF1BwG5DcEOEg 3P+JNEGUA1ZAhw3NJr09F7JcqdEncwwstohhxo7aQCWsF3HLObhD7vRlBXaKPgku Y0ShC1VVQ6/Zp7+Ppd0EkfpdSe6FL5wk1o6UzMYuOYBQ87FBXA2bRn+B3GvxW6m7 3N6ConhWaZerXDsMm+FmbRqGNVHdMrr4HKjg/5mXevWJwSygPmIBvwlYWkthnCeC r1i/ynT7IPFO1/a95L2ajkXIBPHpQwUMISVr6goS7XCIdFGFnu+p61QwKQYYF2pD 6/BjChOXWwH9tsS/zp5OFKhhDZgKOt+Z5l4xFAyu3L6D5XFVuJXlP5v5x2Yw6EsQ +4/z1n0ky340YKVnxK5r8oUDjgF51+bdwtnWi2VNGEpNTY7o1847F3pgkeoxJuvv Q2HAN/HLdeyhfYL24T23fHZDmW+eQcF+F4pUQCug8IFRziGr8lwIbGHsFjGzIt+o qQ7BLFDxEDXouCcT0MHStj1vAgzdhS0= =eI3z -END PGP SIGNATURE End Message ---
Bug#1021755: marked as done ([ROM] racon: Please remove for 32 bit architectures (armel, armhf, i386, mipsel, hppa, m68k, powerpc, sh4, x32))
Your message dated Sat, 10 Dec 2022 09:49:35 -0500 with message-id <1909070.SDCOHYvd1X@localhost> and subject line Re: [ROM] racon: Please remove for 32 bit architectures (armel, armhf, i386, mipsel, hppa, m68k, powerpc, sh4, x32) (Was: Bug#1021755: racon: build-dependencies unsatisfiable on 32-bit.) has caused the Debian Bug report #1021755, regarding [ROM] racon: Please remove for 32 bit architectures (armel, armhf, i386, mipsel, hppa, m68k, powerpc, sh4, x32) 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.) -- 1021755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: racon Version: 1.5.0-2 Severity: serious racon build-depends on libthread-pool-dev which is no longer available on 32-bit architectures, this means that the package can no longer be built on those architectures but the binaries are still in testing/unstable. In general there are three possible avenues for fixing these kinds of issues, in roughly descending order of preference. 1. Fix libthread-pool-dev to build on 32-bit architectures. 2. Eliminate the build-dependency (either generally or on those architectures) 3. Declare your package unsupportable on 32-bit architectures and file a removal request with the ftpmasters. Which of these are possible in the case of your specific package I do not know. --- End Message --- --- Begin Message --- Already removed under #1025752. Closing. Scott K On Fri, 14 Oct 2022 10:41:26 +0200 Andreas Tille wrote: > Control: retitle -1 [ROM] racon: Please remove for 32 bit architectures (armel, armhf, i386, mipsel, hppa, m68k, powerpc, sh4, x32) > Control: reassign -1 ftp.debian.org > > Hi ftpmasters, > > we have to chose option 3 mentioned below - asking for removal of > 32 bit architectures. > > Kind regards and thanks for working as ftpmaster > > Andreas. > > Am Fri, Oct 14, 2022 at 04:54:27AM +0100 schrieb Peter Green: > > Package: racon > > Version: 1.5.0-2 > > Severity: serious > > > > racon build-depends on libthread-pool-dev which is no longer available on 32-bit > > architectures, this means that the package can no longer be built on those > > architectures but the binaries are still in testing/unstable. > > > > In general there are three possible avenues for fixing these kinds of issues, > > in roughly descending order of preference. > > > > 1. Fix libthread-pool-dev to build on 32-bit architectures. > > 2. Eliminate the build-dependency (either generally or on those architectures) > > 3. Declare your package unsupportable on 32-bit architectures and file a removal > >request with the ftpmasters. > > > > Which of these are possible in the case of your specific package I do not know. > > > > ___ > > Debian-med-packaging mailing list > > debian-med-packag...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging > > > > -- > http://fam-tille.de > > &references=<407d1f58-f777-274a-7344-62e13085f...@debian.org> signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#1025848: src:kiwi: unsatisfied build dependency in testing: python3-testinfra
Hello Paul! On 12/10/22 15:13, Paul Gevers wrote: Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. I'm not sure what the point of this bug report is. If any of the build dependencies are missing because someone reported a RC bug against it, it's not really my job to fix that particular bug. There is no apparent bug in kiwi that I know of, so I don't see what the purpose of this bug report is and what I am supposed to do except maybe go talk to the maintainer of python3-testinfra to tell him to fix their bugs. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1025838: marked as done (libreflectasm-java: build-depends on dropped package)
Your message dated Sat, 10 Dec 2022 14:42:32 + with message-id and subject line Bug#1025838: fixed in libreflectasm-java 1.11.9+dfsg-3 has caused the Debian Bug report #1025838, regarding libreflectasm-java: build-depends on dropped package 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.) -- 1025838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libreflectasm-java Version: 1.11.9+dfsg-2 Severity: serious Tags: bookworm, sid Justification: rc policy - "Packages must be buildable within the same release" User:debian...@lists.debian.org Usertags: edos-uninstallable libreflectasm-java build-depends on libasm-java-doc which is longer built by the asm source package. It is still present in unstable as a cruft package, but is completely gone from testing. This means that libreflectasm-java in testing is in violation of the rc policy. --- End Message --- --- Begin Message --- Source: libreflectasm-java Source-Version: 1.11.9+dfsg-3 Done: Pierre Gruet We believe that the bug you reported is fixed in the latest version of libreflectasm-java, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre Gruet (supplier of updated libreflectasm-java package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 10 Dec 2022 14:18:59 +0100 Source: libreflectasm-java Architecture: source Version: 1.11.9+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Pierre Gruet Closes: 1025838 Changes: libreflectasm-java (1.11.9+dfsg-3) unstable; urgency=medium . * Stopping build-depending on dropped libasm-java-doc (Closes: #1025838) Checksums-Sha1: cedc068d1e2e63c8f873b4849bfa0d288aeb09d2 2327 libreflectasm-java_1.11.9+dfsg-3.dsc 2fda48923cd06fba8c14e8acc641f7a21f416e14 5808 libreflectasm-java_1.11.9+dfsg-3.debian.tar.xz 681603c745ad7ae636c953ba80b856b674a0853f 15473 libreflectasm-java_1.11.9+dfsg-3_amd64.buildinfo Checksums-Sha256: 551d7ef0776b332bdfa0e15f0781025142241e31a99490fe192c22dc3cdf0499 2327 libreflectasm-java_1.11.9+dfsg-3.dsc 3f907bd989217188ff8f0270d46026d034c35a965e1199b411be8fb9bf0c63c7 5808 libreflectasm-java_1.11.9+dfsg-3.debian.tar.xz b7c4c39cefeb7f41f574d68de36b3117c75357f9f32dd448c6b87f26c931d0d1 15473 libreflectasm-java_1.11.9+dfsg-3_amd64.buildinfo Files: 1c73179f02408e1cb911bc5fde34c7a9 2327 java optional libreflectasm-java_1.11.9+dfsg-3.dsc 1ba303642060ba2377ec98e44fa74be5 5808 java optional libreflectasm-java_1.11.9+dfsg-3.debian.tar.xz e3476bca908a21785f29ddf23f61def7 15473 java optional libreflectasm-java_1.11.9+dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEM8soQxPpC9J9y0UjYAMWptwndHYFAmOUkFwACgkQYAMWptwn dHYd4g//SCEN/zRFXkUamCXdUXC7P18IMtW7+9yfm4RE9GIrMvwBx47grUPSD8n9 +o930VakLwd2rCYRMjrq9KC9Ge92ngbxlwSAeeNxkMddS72Mhw9OCIebfaKUK0yH B9yWXEixKjvQPh3+IX+QCp857R3v4E2RJ/U9GgyaaZJlGOZd2OTkcN93z6gHRCUE mWxB1OkuuZnmw8jFgFU/fAt5R2Nde6rMUuyO3sKngnLaZeCPBqSYOpvi3G8TWile Zi12uciYfaJd+/CeJu7ua9Xz+y+0rfmKBAzm00i2XW8yZ4X6HkUMiayueXvxtSag xzxiVBEFUO1ay4vCNeaV0HvjW2KpCk5XX/9C2aWRlYRB0HwrZbesvdwLuFQKtrYy alU+tp27Oc6kpuovYSofcR7f01NLSZDqDxbpaugKLXd+yA2ES9BwJcN+alGkR0p8 DEIfRsBKQN5reQ93fp1919JGhGQLxrGMZCvKQSUFU5UAheNmn2SY38c926s7wvUr UaIdYE1aqsG5VyRAwoHcunzyg/6gRePF6a4KuzvguvMCg7FrlpyLX2vuJS8sOHXC rVo/bbkiHy6u9C4jtOXbtm1XwGKHrelxAoXYIJisnqaCkPn6Ia3Rcocb01/ZsNJl IqqpqYg4TrwUmUWdKkkGVPBhpKA6teeK/xBQIbk5HQP+ozo7+8o= =G+Ut -END PGP SIGNATURE End Message ---
Processed: tagging 1025775
Processing commands for cont...@bugs.debian.org: > tags 1025775 + pending Bug #1025775 [src:cataclysm-dda] libsdl2 breaks cataclysm-dda autopkgtest in lxc: only bottom left corner appears in screenshot Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1025775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021701: marked as done (pytest-testinfra: build dependency missing in testing: salt-common)
Your message dated Sat, 10 Dec 2022 15:15:45 +0100 with message-id and subject line autoremoval happened has caused the Debian Bug report #1021701, regarding pytest-testinfra: build dependency missing in testing: salt-common 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.) -- 1021701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-testinfra Version: 6.8.0-1 Severity: serious User: debian...@lists.debian.org Usertag: edos-uninstallable Dear maintainer(s), Dose [1] is reporting issues with your packages. Normally your build dependencies shouldn't be removed from testing without removal all reverse build dependencies too, nor should a package be allowed to migrate unless all build dependencies are candidate for migration too. However, somehow we ended up in the current state and your source package is missing some Build-Depends for some while now. Not being able to build from source in a suite is an RC bug in that suite. Can you please solve the situation by either helping the maintainer of your Build-Depends to enable migration to testing, or by working around the lack of this build dependency? Paul [1] https://qa.debian.org/dose/debcheck/src_testing_main/index.html OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Hi, This bug can be closed, because the package is currently not in testing and won't migrate back until the build depends are candidate for migration too. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1025849: cloud-initramfs-growroot - silently breaks initramfs build
Package: cloud-initramfs-growroot Version: 0.18.debian10 Severity: grave Installation of new kernel now silently fails: | Setting up linux-image-6.0.0-5-cloud-arm64 (6.0.10-2) ... | /etc/kernel/postinst.d/initramfs-tools: | update-initramfs: Generating /boot/initrd.img-6.0.0-5-cloud-arm64 | W: No zstd in /usr/bin:/sbin:/bin, using gzip | E: /usr/share/initramfs-tools/hooks/growroot failed with return 1. | update-initramfs: failed for /boot/initrd.img-6.0.0-5-cloud-arm64 with 1. | run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Bastian -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (700, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-0-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cloud-initramfs-growroot depends on: pn cloud-utils ii fdisk2.38.1-4 ii initramfs-tools 0.142 ii util-linux 2.38.1-4 cloud-initramfs-growroot recommends no packages. cloud-initramfs-growroot suggests no packages.
Processed: src:kiwi: unsatisfied build dependency in testing: python3-testinfra
Processing control commands: > block -1 by 1013872 1021317 1021920 1022530 Bug #1025848 [src:kiwi] src:kiwi: unsatisfied build dependency in testing: python3-testinfra 1025848 was not blocked by any bugs. 1025848 was not blocking any bugs. Added blocking bug(s) of 1025848: 1022530, 1021920, 1013872, and 1021317 -- 1025848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025848: src:kiwi: unsatisfied build dependency in testing: python3-testinfra
Source: kiwi Version: 9.24.49-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: edos-uninstallable Control: block -1 by 1013872 1021317 1021920 1022530 Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing. Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature Description: OpenPGP digital signature
Bug#1025835: tiledb-py: build-depends on libtiledb-doc
On 10 December 2022 at 09:07, Peter Green wrote: | Source: tiledb-py | Version: 0.18.2-1 | Severity: serious | Justification: rc policy - "Packages must be buildable within the same release" | x-debbugs-cc: e...@debian.org | User: debian...@lists.debian.org | Usertags: edos-uninstallable | | tiledb-py build-depends on libtiledb-doc, which is no longer built by tiledb since | version 2.13.0-1, this removal is no mentioned in the changelog, so it's not clear to me | if it was deliberate or not. It is still present in unsable as a cruft package, but is | completely gone from testing. This means that tiledb-py in testing is in violation of | the rc policy. Good catch but that was in fact deliberate. The build (of a package I inherited / adopted) was giving me fits, and I as maintainer have decided to follow a) upstreams preference for documentation on the websites and b) simplify the build. We should adjust tiledb-py (which needs an update for the now released 0.19.0 anyway, and had skipped minor release 0.18.3 which is ok) accordingly. CCing Nilesh who looks after tiledb-py. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1021637: rust-pyo3: autopkgtest failure
Control: block 1011155 by -1 On Wed, 12 Oct 2022 04:30:28 +0300 Adrian Bunk wrote: Source: rust-pyo3 Version: 0.16.5-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-pyo3/26874345/log.gz ... rust-pyo3:@ FAIL non-zero exit status 101 Is anyone interested in fixing this? This is the last building block for updating python-cryptography.
Processed: Re: rust-pyo3: autopkgtest failure
Processing control commands: > block 1011155 by -1 Bug #1011155 [src:python-cryptography] python-cryptography: please update to latest >= v35 releases 1011155 was blocked by: 1009235 1019378 1011155 was not blocking any bugs. Added blocking bug(s) of 1011155: 1021637 -- 1011155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011155 1021637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1025839: gsequencer: build-depends on dropped virtual package
Processing control commands:
> forcemerge 1025308 -1
Bug #1025308 {Done: Bas Couwenberg } [src:gsequencer]
gsequencer: FTBFS with fftw3 (3.3.10-1)
Bug #1025839 [src:gsequencer] gsequencer: build-depends on dropped virtual
package
1025839 was not blocked by any bugs.
1025839 was not blocking any bugs.
Added blocking bug(s) of 1025839: 1025312 and 1025324
1025839 was blocked by: 1025312 1025324
1025839 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1025839 to the same blocks
previously set
Marked Bug as done
Marked as fixed in versions gsequencer/4.4.3-1.
Added tag(s) patch and ftbfs.
Bug #1025308 {Done: Bas Couwenberg } [src:gsequencer]
gsequencer: FTBFS with fftw3 (3.3.10-1)
Added tag(s) bookworm and sid.
Merged 1025308 1025839
--
1025308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025308
1025839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1025839: gsequencer: build-depends on dropped virtual package
Control: forcemerge 1025308 -1 On 2022-12-10 09:45:03 +, Peter Green wrote: > Source: gsequencer > Version: 4.4.1-1 > Severity: serious > Tags: bookworm, sid > Justification: rc policy - "Packages must be buildable within the same > release" > User:debian...@lists.debian.org > Usertags: edos-uninstallable > > gsequence build-depends on fftw3-dev, this is a virtual package that was > previously provided by libfftw3-dev but was dropped recently. This means that > your > package cannot be built in testing or unstable. That's #1025308. Cheers -- Sebastian Ramacher
Bug#1020576: please update sage for pari 2.15.0 and gap 4.12.0
On Mon, 28 Nov 2022 21:05:07 + Tobias Hansen wrote: > On 11/27/22 19:24, Nilesh Patra wrote: > > On Sun, Nov 27, 2022 at 05:35:17PM +, Tobias Hansen wrote: > >> On 11/27/22 06:37, Nilesh Patra wrote: > >>> Tobias, since this is done, would you consider to check sagemath now and > >>> get the ball rolling? :-) > >> Hi, > >> > >> I actually tried building with the new pari and gap versions a while ago > >> (using sagemath 9.5 with upstream patches for the new pari and gap > >> versions, I pushed them to the git repo today) and got stuck with a lot of > >> errors like this (might be unrelated to pari and gap): > > I am having a hard time building/reproducing this because sage tends to > > need a lot of compute power that I currently do not have, and it takes > > forever to porter box too. > > But looking at the error, my hunch is that this is a setuptools related > > monkeypatch issue (there are similar RC bugs filed for many packages). So > > re-ordering cython import > > in sage/misc/cython.py file after setuptools along with ensuring distutils > > is imported after setuptools will (very) likely help. > > > > Here is a related link that I found for the same > > > > > > https://stackoverflow.com/questions/21594925/error-each-element-of-ext-modules-option-must-be-an-extension-instance-or-2-t > > > Thanks. The attached patch removed the error, but now there are these > warnings when cython is used in doctests: > > UserWarning: Distutils was imported before Setuptools, but importing > Setuptools also replaces the `distutils` module in `sys.modules`. Apologies for late response. I suppose the line above is the crux? setuptools monkey-patches distutils so it should be imported _before_ distutils. Somewhere in the doctests, it is other way round and hence the error. Did you get a chance to build sage yet? > This may lead to undesirable behaviors or errors. To avoid these issues, > avoid using distutils directly, ensure that setuptools is installed in the > traditional way (e.g. not an editable install), and/or make sure that > setuptools is always imported before distutils. -- Best, Nilesh signature.asc Description: PGP signature
Bug#1024898: marked as done (mozc: FTBFS on armel)
Your message dated Sat, 10 Dec 2022 11:29:21 +
with message-id
and subject line Bug#1024898: fixed in mozc 2.28.4715.102+dfsg-2.2
has caused the Debian Bug report #1024898,
regarding mozc: FTBFS on armel
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.)
--
1024898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mozc
Version: 2.28.4715.102+dfsg-2
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=mozc&arch=armel&ver=2.28.4715.102%2Bdfsg-2&stamp=1669203429&raw=0
FAILED: ibus_mozc
/usr/bin/g++ -Wl,-z,relro -Wl,--as-needed -lstdc++ -pthread -o ibus_mozc
-Wl,--start-group obj/unix/ibus/ibus_mozc.main.o obj/base/libbase.a
obj/base/libversion.a obj/unix/ibus/libibus_mozc_lib.a
obj/unix/ibus/libibus_mozc_metadata.a obj/base/libbase_core.a
obj/base/libclock.a obj/base/libsingleton.a obj/base/libhash.a
obj/base/libnumber_util.a obj/base/libjapanese_util.a obj/client/libclient.a
obj/ipc/libipc.a obj/ipc/libipc_protocol.a obj/protocol/libcommands_proto.a
obj/protocol/libcandidates_proto.a obj/protocol/libconfig_proto.a
obj/protocol/libengine_builder_proto.a
obj/protocol/libuser_dictionary_storage_proto.a
obj/session/libime_switch_util.a obj/config/libconfig_handler.a
obj/base/libconfig_file_stream.a obj/session/libkey_info_util.a
obj/composer/libkey_event_util.a obj/composer/libkey_parser.a
obj/session/libkeymap.a obj/unix/ibus/libibus_config_proto.a
obj/unix/ibus/libibus_property_handler.a obj/unix/ibus/libmessage_translator.a
obj/unix/ibus/libpath_util.a obj/protocol/librenderer_proto.a
obj/unix/ibus/libgtk_candidate_window_handler.a
obj/renderer/librenderer_client.a obj/unix/ibus/libselection_monitor.a
-libus-1.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lxcb -lxcb-xfixes -labsl_base
-labsl_int128 -labsl_base -labsl_hash -labsl_city -labsl_flags_reflection
-labsl_raw_hash_set -labsl_str_format_internal -labsl_throw_delegate
-labsl_time_zone -labsl_hashtablez_sampler -labsl_synchronization -labsl_time
-labsl_strings_internal -labsl_strings -labsl_spinlock_wait -labsl_status
-labsl_statusor -labsl_flags_internal -labsl_flags_usage_internal
-labsl_flags_marshalling -labsl_flags_parse -lprotobuf -Wl,--end-group
/usr/bin/ld: obj/unix/ibus/ibus_mozc.main.o: undefined reference to symbol
'__atomic_load_8@@LIBATOMIC_1.0'
/usr/bin/ld: /usr/lib/arm-linux-gnueabi/libatomic.so.1: error adding symbols:
DSO missing from command line
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File "/<>/src/build_mozc.py", line 892, in
sys.exit(main())
File "/<>/src/build_mozc.py", line 877, in main
BuildMain(cmd_opts, cmd_args)
File "/<>/src/build_mozc.py", line 617, in BuildMain
BuildWithNinja(options, targets)
File "/<>/src/build_mozc.py", line 591, in BuildWithNinja
RunOrDie([ninja, '-v', '-C', build_arg, target_name])
File "/<>/src/build_tools/util.py", line 96, in RunOrDie
raise RunOrDieError('\n'.join(['',
build_tools.util.RunOrDieError:
==
ERROR: ninja -v -C out_linux/Release ibus_mozc
==
make[1]: *** [debian/rules:44: build_dynamic_link] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:30: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: mozc
Source-Version: 2.28.4715.102+dfsg-2.2
Done: Gunnar Hjalmarsson
We believe that the bug you reported is fixed in the latest version of
mozc, 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 1024...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gunnar Hjalmarsson (supplier of updated mozc 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, 10 Dec 2022 11:44:49 +0100
Source: mozc
Built-For-Profiles: noudeb
Architecture: source
Version: 2.28.4715.102+dfsg-2.2
Distribution:
Bug#1025739: Is an autogenerated configure shell script non-editable source (Was: Bug#1025739: hmmer2: missing source for configure)
On 2022-12-09 Andreas Tille wrote: [...] > Thanks to Alexander Sulfrian who pointed out the Git repository > featuring old tags that were obviously taken over from SVN I was proven > wrong with the statement that there is no configure.ac any more. > Unfortunately this is no simple drop-in with modern autoconf tools > and my weak attempt in Git to use this failed.[1] [...] Hello, I have given this a a little bit of time. This seems to work: 1. Copy configure.ac from upstream's 2.3.2h2 branch. 2. Add 'export AUTOHEADER = true' to debian/rules. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1025840: deepin-log-viewer: build-depends on dropped virtual package
Source: deepin-log-viewer Version: 5.9.7+ds1-1 Severity: serious Tags: bookworm, sid Justification: rc policy - "Packages must be buildable within the same release" User:debian...@lists.debian.org Usertags: edos-uninstallable deepin-log-viewer build-depends on libfftw3-3, this was previously a transitional package, depending on the single, double and (where available) long double versions of fftw3, but has since been dropped. Please investigate which version(s) of fftw3 your package needs and update your build-dependencies accodingly.
Bug#1025839: gsequencer: build-depends on dropped virtual package
Source: gsequencer Version: 4.4.1-1 Severity: serious Tags: bookworm, sid Justification: rc policy - "Packages must be buildable within the same release" User:debian...@lists.debian.org Usertags: edos-uninstallable gsequence build-depends on fftw3-dev, this is a virtual package that was previously provided by libfftw3-dev but was dropped recently. This means that your package cannot be built in testing or unstable. I suspect that your build-dependency should simply be changed to libfftw3-dev.
Bug#1025838: libreflectasm-java: build-depends on dropped package
Source: libreflectasm-java Version: 1.11.9+dfsg-2 Severity: serious Tags: bookworm, sid Justification: rc policy - "Packages must be buildable within the same release" User:debian...@lists.debian.org Usertags: edos-uninstallable libreflectasm-java build-depends on libasm-java-doc which is longer built by the asm source package. It is still present in unstable as a cruft package, but is completely gone from testing. This means that libreflectasm-java in testing is in violation of the rc policy.
Bug#1025739: Is an autogenerated configure shell script non-editable source
Am Fri, Dec 09, 2022 at 11:58:56AM -0800 schrieb Russ Allbery: > The real problem in this case is less about the DFSG and more about the > practical problems of maintaining Debian as a software distribution: if we > can't regenerate configure using software in Debian, there are a lot of > porting tasks and some bug-fixing tasks that we can't do, and that's a > problem for us. But I'm dubious that it's a *software freedom* problem; > it's more of a *software maintenance* problem, and thus the bug severity > should be based on how much of a problem that is in practice. The situation of hmmer2 is that upstream went to hmmer3 which is despite its same name something different. The Debian Med team keeps on maintaining that old code since scientists need this to have comparable results with former research. I guess its simple enough to even craft a new configure.ac (or backport the one for hmmer3) if needed and the fact that Helmit stumbled upon it to enhance pkg-config compatibility is a good reason for a bug report with severity somewhere between wishlist and important. We try to fix any bug (no matter what severity) and in the current Debian Med Advent bug squashing party we try to approach this. However, since we can not guarantee that the bug is solved quickly a serious bug might have the consequence that the package might not be shipped with bookworm which is definitely not in the interest of our users. So far for the actual case (bug report in CC). For the general case I somehow understand the consensus here on the list that a missing configure.ac can be considered a bug but the severity serious is not really rectified. If I understood this correctly I would reset the severity to important at the beginning of next week. Kind regards Andreas. -- http://fam-tille.de
Bug#1025837: docopt: build-depends on dropped virtual package
Source: docopt Version: 0.6.2-4 Severity: serious Tags: bookworm, sid Justification: rc policy - "Packages must be buildable within the same release" User:debian...@lists.debian.org Usertags: edos-uninstallable docopt build-depends on dh-sequence-python2, this is a virtual package that was previously provided by dh-python but was dropped recently. This means that your package cannot be built in testing or unstable. I suspect this build-dependency is a leftover from before python 2 support was removed from your package.
Bug#1025836: byte-buddy: build-depends on dropped package
Source: byte-buddy Version: 1.8.2-2 Severity: serious Tags: bookworm, sid Justification: rc policy - "Packages must be buildable within the same release" User:debian...@lists.debian.org Usertags: edos-uninstallable byte-buddy build-depends on libasm-java-doc which is longer built by the asm source package. It is still present in unstable as a cruft package, but is completely gone from testing. This means that byte-buddy in testing is in violation of the rc policy.
Bug#1025835: tiledb-py: build-depends on libtiledb-doc
Source: tiledb-py Version: 0.18.2-1 Severity: serious Justification: rc policy - "Packages must be buildable within the same release" x-debbugs-cc: e...@debian.org User: debian...@lists.debian.org Usertags: edos-uninstallable tiledb-py build-depends on libtiledb-doc, which is no longer built by tiledb since version 2.13.0-1, this removal is no mentioned in the changelog, so it's not clear to me if it was deliberate or not. It is still present in unsable as a cruft package, but is completely gone from testing. This means that tiledb-py in testing is in violation of the rc policy.
Bug#1024955: marked as done (loguru: (autopkgtest) needs update for python3.11: got an unexpected keyword argument 'follow_symlinks')
Your message dated Sat, 10 Dec 2022 09:01:43 + with message-id and subject line Bug#1024955: fixed in loguru 0.6.0-3 has caused the Debian Bug report #1024955, regarding loguru: (autopkgtest) needs update for python3.11: got an unexpected keyword argument 'follow_symlinks' 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.) -- 1024955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: loguru Version: 0.6.0-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of loguru fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 loguru from testing0.6.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/l/loguru/28726240/log.gz tests/test_filesink_rotation.py::test_size_rotation[64b] PASSED [ 59%] tests/test_filesink_rotation.py::test_time_rotation[13-hours0] 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 187, in console_main code = main() ^^ File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 164, in main ret: Union[ExitCode, int] = config.hook.pytest_cmdline_main( File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265, in __call__ return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult) File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80, in _hookexec return self._inner_hookexec(hook_name, methods, kwargs, firstresult) ^ File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 60, in _multicall return outcome.get_result() File "/usr/lib/python3/dist-packages/pluggy/_result.py", line 60, in get_result raise ex[1].with_traceback(ex[2]) File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 39, in _multicall res = hook_impl.function(*args) ^ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 315, in pytest_cmdline_main return wrap_session(config, _main) ^^^ File "/usr/lib/python3/dist-packages/_pytest/main.py", line 303, in wrap_session config.hook.pytest_sessionfinish( File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 265, in __call__ return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult) File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 80, in _hookexec return self._inner_hookexec(hook_name, methods, kwargs, firstresult) ^ File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 55, in _multicall gen.send(outcome) File "/usr/lib/python3/dist-packages/_pytest/terminal.py", line 798, in pytest_sessionfinish outcome.get_result() File "/usr/lib/python3/dist-packages/pluggy/_result.py", line 60, in get_result raise ex[1].with_trac
Bug#1024417: marked as done (kgpg FTBFS: Did not find GPGME)
Your message dated Sat, 10 Dec 2022 08:52:29 + with message-id and subject line Bug#1024417: fixed in kgpg 4:22.12.0-1 has caused the Debian Bug report #1024417, regarding kgpg FTBFS: Did not find GPGME 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.) -- 1024417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kgpg Version: 4:22.04-2.2 Severity: serious Tags: ftbfs X-Debbugs-Cc: Debian GnuPG Maintainers kgpg fails to build from source in unstable. The relevant portion is: | -- No usable gpgme flavors found. | CMake Error at cmake/FindGpgme.cmake:367 (message): | Did not find GPGME | Call Stack (most recent call first): | CMakeLists.txt:61 (find_package) | | | -- Configuring incomplete, errors occurred! I think this is due to gpgme having dropped its gpgme-config tool in favour of providing a .pc file. I think the change is good in principle, but the transition is executed in a bad way. gpgme-config was always difficult for cross compilation while .pc just works. In any case, this puts kgpg into a difficult spot. I hope you can deal with it somehow. I've put the gpgme maintainers in the loop for assistance. Helmut --- End Message --- --- Begin Message --- Source: kgpg Source-Version: 4:22.12.0-1 Done: Debian Qt/KDE Maintainers We believe that the bug you reported is fixed in the latest version of kgpg, 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 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Debian Qt/KDE Maintainers (supplier of updated kgpg 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, 24 Nov 2022 13:11:06 +0100 Source: kgpg Architecture: source Version: 4:22.12.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Debian Qt/KDE Maintainers Closes: 1024417 Changes: kgpg (4:22.12.0-1) UNRELEASED; urgency=medium . [ Aurélien COUDERC ] * New upstream release (22.08.3). * Update build-deps and deps with the info from cmake. * Add patch to fix lookup of GPGME with recent versions. (Closes: #1024417) * New upstream release (22.11.90). * Update build-deps and deps with the info from cmake. * New upstream release (22.12.0). Checksums-Sha1: 5b293d311b10ffe721ff42c01c5d68bb2f7ebf2b 2966 kgpg_22.12.0-1.dsc 55621bb333bb7a0d9c0a9d23f627e6e513304536 3036848 kgpg_22.12.0.orig.tar.xz 07b3bc332299d35001813be069316e7145e5d344 833 kgpg_22.12.0.orig.tar.xz.asc be45ecf2bf14d9f8e1719bcd5cd610943a63ef1c 16280 kgpg_22.12.0-1.debian.tar.xz cfe4cac7a1bb073d254b7c73c6153d5a69bdf0d1 19394 kgpg_22.12.0-1_amd64.buildinfo Checksums-Sha256: ca3240a8abded253b2599f333bc0e6d1893482b70a9d4118a89ecf678a302a19 2966 kgpg_22.12.0-1.dsc fe5f83caa52693a7d2e120eb79e1f17f999db42d0fbb66b612fae1f83e80b155 3036848 kgpg_22.12.0.orig.tar.xz 36305b4e1dac152e4d00dafc6eeef3b98f40009b121071734bd87eaa3f52fbdc 833 kgpg_22.12.0.orig.tar.xz.asc dd4306dd302d03282a2c183a3689fd9a2e378e71fc355422a44812d254d08379 16280 kgpg_22.12.0-1.debian.tar.xz 206be6102f1a07cf53db2334ff5054b1f4ca663aeda88c6605c79c174de1d7ef 19394 kgpg_22.12.0-1_amd64.buildinfo Files: 2cee251ee75c272df363cb88dad0f29c 2966 kde optional kgpg_22.12.0-1.dsc 5816cf0474e35c190e7d81bf409185ab 3036848 kde optional kgpg_22.12.0.orig.tar.xz 1f2ac9bfc4d22d9de044e7318d874d4b 833 kde optional kgpg_22.12.0.orig.tar.xz.asc a93edb5fc3b900d0bc2f5bfee67b1822 16280 kde optional kgpg_22.12.0-1.debian.tar.xz da6a844b6b00de0bcb25e68eeca5c304 19394 kde optional kgpg_22.12.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmOTy5oTHGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJFEwD/9wFtsYZjKfoc30hg/tVhz2zt03Zbr8 hemM1cbpkLWTKNC/PYDA/dUfYJH7T5AKhPsHGQKeaE0Yv8PeH4qpaOUYR60EBxyu A7uw6RvRnARu+EmsD8PWw8UokgADzAnKLMeCf6769+nyJYerCoNU2ryVdjrTbmVv 2b88ADWq6d1bT9zuamZ0cBqzyDMkJeFd1R33snsBpYH81Ykvl5ex3++4dOxTtAzU C+onoifZi16djFqc82U7H5OMMf4pj2D/f4hri17Eqqe0H+0uGF8P+3zZxLZZs7Wh Vjy6SDYcBByflyAecQpavXenMvtTPo8d5mDbhac+gTmZVdshCkTDnsZgMwzRtAuR hsiIi50qurptx8ONkE/24/Dew1eDyvOAQ8DlvlwgYzLh4vs+YLw
Bug#1024912: marked as done (flask-caching: (autopkgtest) needs update for python3.11: Address already in use)
Your message dated Sat, 10 Dec 2022 08:38:18 + with message-id and subject line Bug#1024912: fixed in flask-caching 2.0.1-3 has caused the Debian Bug report #1024912, regarding flask-caching: (autopkgtest) needs update for python3.11: Address already in use 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.) -- 1024912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flask-caching Version: 2.0.1-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of flask-caching fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 flask-caching from testing2.0.1-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/f/flask-caching/28726230/log.gz + trap cleanup EXIT ++ py3versions -s + for p in $(py3versions -s) + echo 'Testing with python3.11...' Testing with python3.11... + echo 2183 + python3.11 debian/tests/testapp.py + sleep 3 * Serving Flask app 'testapp' (lazy loading) * Environment: production WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead. * Debug mode: off * Running on http://127.0.0.1:5000/ (Press CTRL+C to quit) + curl http://127.0.0.1:5000/ + grep '^counter=1$' 127.0.0.1 - - [27/Nov/2022 17:13:31] "GET / HTTP/1.1" 200 - counter=1 + curl http://127.0.0.1:5000/ + grep '^counter=1$' 127.0.0.1 - - [27/Nov/2022 17:13:31] "GET / HTTP/1.1" 200 - counter=1 + curl http://127.0.0.1:5000/ + grep '^counter=1$' 127.0.0.1 - - [27/Nov/2022 17:13:31] "GET / HTTP/1.1" 200 - counter=1 + sleep 10 + curl http://127.0.0.1:5000/ + grep '^counter=2$' 127.0.0.1 - - [27/Nov/2022 17:13:41] "GET / HTTP/1.1" 200 - counter=2 + curl http://127.0.0.1:5000/ + grep '^counter=2$' 127.0.0.1 - - [27/Nov/2022 17:13:41] "GET / HTTP/1.1" 200 - counter=2 + for p in $(py3versions -s) + echo 'Testing with python3.10...' Testing with python3.10... + echo 2201 + python3.10 debian/tests/testapp.py + sleep 3 * Serving Flask app 'testapp' (lazy loading) * Environment: production WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead. * Debug mode: off Traceback (most recent call last): File "/tmp/autopkgtest-lxc.op2ybvu9/downtmp/build.R2l/src/debian/tests/testapp.py", line 39, in app.run() File "/usr/lib/python3/dist-packages/flask/app.py", line 920, in run run_simple(t.cast(str, host), port, self, **options) File "/usr/lib/python3/dist-packages/werkzeug/serving.py", line 1010, in run_simple inner() File "/usr/lib/python3/dist-packages/werkzeug/serving.py", line 950, in inner srv = make_server( File "/usr/lib/python3/dist-packages/werkzeug/serving.py", line 782, in make_server return ThreadedWSGIServer( File "/usr/lib/python3/dist-packages/werkzeug/serving.py", line 688, in __init__ super().__init__(server_address, handler) # type: ignore File "/usr/lib/python3.10/socketserver.py", line 452, in __init__ self.server_bind() File "/usr/lib/python3.10/http/server.py", line 136, in server_bind socketserver.TCPServer.server_bind(self) File "/usr/lib/python3.10/socketserver.py", line 466, in server_bind self.socket.bind(self.server_address) OSError: [Errno 98] Address already in use + curl http://127.0.0.1:5000/ + grep '^counter=1$' 127.0.0.1 - - [27/Nov/2022 17:13:44] "GET / HTTP/1.1" 200 - + cleanup ++ cat /tmp/autopkgtest-lxc.op2ybvu9/downtmp/autopkgt
