Bug#1038866: marked as done (cbmc FTBFS on !x86: Failed test: __asm_fstcw-01)
Your message dated Mon, 26 Jun 2023 05:20:44 + with message-id and subject line Bug#1038866: fixed in cbmc 5.84.0-6 has caused the Debian Bug report #1038866, regarding cbmc FTBFS on !x86: Failed test: __asm_fstcw-01 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.) -- 1038866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cbmc Version: 5.84.0-5 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=cbmc=5.84.0-5 (m68k builds with nocheck) ... [31mTests failed[0m 1 of 453 tests failed, 350 tests skipped Failed test: __asm_fstcw-01 CBMC version 5.84.0 (cbmc-5.76.1) 64-bit arm64 linux Parsing msvc.i Converting Type-checking msvc Generating GOTO Program Adding CPROVER library (x86_64) gcc: error: unrecognized command-line option ‘-m64’ GCC preprocessing failed Removal of function pointers and virtual functions Generic Property Instrumentation Running with 8 object bits, 56 offset bits (default) Starting Bounded Model Checking WARNING: no body for function __asm_fstcw Runtime Symex: 0.0018543s size of program expression: 32 steps simple slicing removed 7 assignments Generated 2 VCC(s), 2 remaining after simplification Runtime Postprocess Equation: 2.5e-05s Passing problem to propositional reduction converting SSA Runtime Convert SSA: 0.000565307s Running propositional reduction Post-processing Runtime Post-process: 9.22e-06s Solving with MiniSAT 2.2.1 with simplifier 148 variables, 138 clauses SAT checker: instance is SATISFIABLE Runtime Solver: 0.000284463s Runtime decision procedure: 0.000977351s ** Results: msvc.i function main [main.assertion.1] line 5 default rounding mode: FAILURE [main.assertion.2] line 9 round upwards: FAILURE ** 2 of 2 failed (2 iterations) VERIFICATION FAILED EXIT=10 SIGNAL=0 Failed msvc.desc lines: ^EXIT=0$ [FAILED] ^VERIFICATION SUCCESSFUL$ [FAILED] make[4]: *** [Makefile:12: test] Error 1 --- End Message --- --- Begin Message --- Source: cbmc Source-Version: 5.84.0-6 Done: Michael Tautschnig We believe that the bug you reported is fixed in the latest version of cbmc, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tautschnig (supplier of updated cbmc 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, 25 Jun 2023 20:14:35 +0100 Source: cbmc Binary: cbmc cbmc-dbgsym jbmc jbmc-dbgsym Architecture: source Version: 5.84.0-6 Distribution: unstable Urgency: low Maintainer: Michael Tautschnig Changed-By: Michael Tautschnig Description: cbmc - bounded model checker for C and C++ programs jbmc - bounded model checker for Java programs Closes: 1038866 Changes: cbmc (5.84.0-6) unstable; urgency=low . * Fix further portability problems (Closes: #1038866) Checksums-Sha1: 963f5f7c07aabc5deb153054b27525eb98037437 2962 cbmc_5.84.0-6.dsc 1b7e99078453e76ea7815a0546b57a1292d51e34 56280 cbmc_5.84.0-6.debian.tar.xz Checksums-Sha256: dea00926498044150e7e11417eecd3dd84bbcb10f5465b1a7cc94deae5eb1cbb 2962 cbmc_5.84.0-6.dsc ad9a0908a6673092701b1ff42a8aaca5c54b0753f49ef72a7daf3cf6ff25e039 56280 cbmc_5.84.0-6.debian.tar.xz Files: 876111401564d8ea6639a56eff662452 2962 science optional cbmc_5.84.0-6.dsc 611f6c94df4427f6af9e413d166c671a 56280 science optional cbmc_5.84.0-6.debian.tar.xz -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQJCBAEBCAAsFiEErKbD9OEAOYbzU4gEO7+DkzbsqTEFAmSZGmIOHG10QGRlYmlh bi5vcmcACgkQO7+DkzbsqTHHZA//aj7Hr/8Ph+2wUx/ACzB0rhzMxu1n5GBePFuz ikQEAO4/HB4bvY5VEGfuIWtW+JNy1dLcmdc+65WBnEw3pUTRTLdmXbTXlNeiznf2 /1oQp2CC82VIhPkROnUyR5mc2qgDS05GAU2A4O+AT1ZhQTMJjtQYfgm1BIJjrOqd 5w/kZRbEYataDReXh/jmTlnzFCFm3kkvS1shQOhLIBKAXXbOJaXQAR5t2QgvUNC6 A6Xre0I6NEZ5A69tuB0BsM6I1vNGz2ZXGqubM8MuR3PtwzVUjo4Lfj3dgN4Uz2cf xy0U68j8TVFTmL3gf/Yqe5sIKwjH7YdJP7RDbS8ztGOvIFegDfrs2Qxr7rsFf+JF 9ba0l1CrkWzdKsYjSiFEvBz+s3ZDCTgHE4V3ZP4txlKKlncIAkQ6k/DDzmI1OBQA 52DgXhfB7kjv5MrX15cMLT4t1IPvdsIw6bmVTkdSRyZsPvlzjHGTYQFPM9oJQSAt RuEHYFdSbxPnY8FMddGZFzlPl1HAiMdyPlsrS7E0h6nPTauoDDOyPJSF5xXyrk7p
Bug#1039119: marked as done (darktable: use packaged lua)
Your message dated Mon, 26 Jun 2023 06:40:37 +0200 with message-id <87bkh2q1iy@tethera.net> and subject line Re: Bug#1039119: darktable: use packaged lua has caused the Debian Bug report #1039119, regarding darktable: use packaged lua 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.) -- 1039119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: darktable Version: Use packaged lua Severity: serious Justification: embded code copy Dear Maintainer, It appear that your package embded and compile lua Could you: - use the packaged lua lib - repack in order to avoid accidental reintroduction of compiling lua rouca -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel Kernel: Linux 6.1.0-9-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Control: severity -1 important > Source: darktable > Version: Use packaged lua That's not a version that the BTS understands, BTW. > Severity: serious > Justification: embded code copy I don't think that's really what policy says. It's not RC just to embed (appropriately licensed) software, even if it is actually used. In this case % ldd /usr/bin/darktable | grep lua liblua5.4.so.0 => /lib/x86_64-linux-gnu/liblua5.4.so.0 (0x7f015155c000) so I'm closing the bug. If you find that the embedded lua really is being used, feel free to re-open at a non-RC severity, or provide a different justification. As I said in my previous message, repacking doesn't seem warranted here, as the risk of accidentally using the embedded lua is trumped by the wanting to use unmodified upstream sources. signature.asc Description: PGP signature --- End Message ---
Bug#1039119: darktable: use packaged lua
Bastien Roucariès writes: > Source: darktable > Version: Use packaged lua > Severity: serious > Justification: embded code copy > > Dear Maintainer, > > It appear that your package embded and compile lua > > Could you: > - use the packaged lua lib > - repack in order to avoid accidental reintroduction of compiling lua > > rouca Since upstream already checks for the system lua (unless that changed) repackaging seems unecessary. Do you have some evidence (build logs ?) that the build is not using the system lua? d
Bug#886087: marked as done (alarm-clock-applet: Depends on gconf)
Your message dated Mon, 26 Jun 2023 03:33:45 + with message-id and subject line Bug#886087: fixed in alarm-clock-applet 0.4.1-4 has caused the Debian Bug report #886087, regarding alarm-clock-applet: Depends on gconf 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.) -- 886087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: alarm-clock-applet Version: 0.3.4-1 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gconf Tags: sid buster Your package depends or build-depends on gconf, but gconf will be removed from Debian soon. gconf's last release was about 5 years ago. It has been replaced by gsettings (provided in Debian by source glib2.0 ) References -- https://developer.gnome.org/gio/stable/ch34.html https://developer.gnome.org/gio/stable/GSettings.html On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Source: alarm-clock-applet Source-Version: 0.4.1-4 Done: Chow Loong Jin We believe that the bug you reported is fixed in the latest version of alarm-clock-applet, 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 886...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chow Loong Jin (supplier of updated alarm-clock-applet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 26 Jun 2023 11:20:27 +0800 Source: alarm-clock-applet Built-For-Profiles: noudeb Architecture: source Version: 0.4.1-4 Distribution: unstable Urgency: medium Maintainer: Chow Loong Jin Changed-By: Chow Loong Jin Closes: 886087 Changes: alarm-clock-applet (0.4.1-4) unstable; urgency=medium . * [5525748] Drop gconf-migration bits gconf is getting removed from Debian (Closes: #886087) Checksums-Sha1: a36b100fefc6aa8721c86b73492f71841d4571f5 2182 alarm-clock-applet_0.4.1-4.dsc 8d0eaeb5fa02aab0dd6ae08dcf1948514b7c8d9b 6700 alarm-clock-applet_0.4.1-4.debian.tar.xz b088f64e8dfdc40732f872874b4437f63d55e34c 18855 alarm-clock-applet_0.4.1-4_source.buildinfo Checksums-Sha256: b1bb140c7ac81c712a5c872f55372757d789774e8505000a10c6742d6119313d 2182 alarm-clock-applet_0.4.1-4.dsc 18ee1d183b2f6aeaf2df3926c141f1c353ffb0825b77077f7940222438f0a308 6700 alarm-clock-applet_0.4.1-4.debian.tar.xz 19170d391e4c10c849295c994712c9160c99cfdf200ec8d8b465ba00be6d98a3 18855 alarm-clock-applet_0.4.1-4_source.buildinfo Files: c265061a00cf4bcd5a05320103ab5c52 2182 gnome optional alarm-clock-applet_0.4.1-4.dsc 044387ec7f7ee9fb91d60316273d982d 6700 gnome optional alarm-clock-applet_0.4.1-4.debian.tar.xz f1329b22f5af70da8c4c58f49132c980 18855 gnome optional alarm-clock-applet_0.4.1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEEuDQnfs/9/dZ027Q+9UiW1iHUqEFAmSZBIkACgkQ+9UiW1iH UqF9zQ//ZCXRONMM2WMn016Dw4LI9+zTdJMbvQJh7A+Zxp1Q34E6FOEpMwkE3oVf WjJa9gqmmXxtw4BmahpJA1nFZDYi7ILNxR6YbJGnHe3n/Mgf6m/wrYEarEETDuI4 4LV5Tg6YMlJul4TpUazOYhMhlb1jlJHc1q4y7UOkdMXE+37Gkqzd+lmGB9TO9p5P 4p/wpYNoffKqjpi66Go3cIHJd6AyZA0/OV9Z9MqFaVLAIH/2SnYQ8O06oCXk/JEW +qGrmzS4GQx765wx0RDiI7MmxmP49Hg6EvcB7UqJg0ld1f7t1mmaPSOH6SF0CHAa yq+cZtRXW+WmOWsv8j4QUQJVy6j7tAlBy/uS6Fmc8GYjCC47hCKdnhr0Tsp1nYwy SkSkMPmlKg04qGwG9EYFagVJAWH1+HdHrVh5VCLxb46Afgm+X7z0/r8PuTSjlkh3 kFBmEQpiC3MI6GgmNFzSNM/tec0+CbQClgOC8dzPfrf9PJV7yiQAHOT2iP45fGYy jMdvjIB51syO6uoQy8EGLuBQIMtBzPqD37SfgS4enxzuNl03LGvkHez8pGeth2Ce m7gJ98B/uq3UI96h+zFwLdZlYBF14LPIqSSIwaDyV63iLbdoKNFUCFGgTzX7myk5 DfO0nHVih6CSX1nxsRNYCjdGVvnXohyEHT5HjLBgdomM46EgGSA= =iKhK -END PGP SIGNATURE End Message ---
Processed: (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path.
Processing commands for cont...@bugs.debian.org: > affects 999227 + xterm gdm3 Bug #999227 [src:xfonts-cyrillic] xfonts-cyrillic: missing required debian/rules targets build-arch and/or build-indep Added indication that 999227 affects xterm and gdm3 > thanks Stopping processing here. Please contact me if you need assistance. -- 999227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999227: (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path.
affects 999227 + xterm gdm3 thanks Any progress? As of now, Debian stable 12 does NOT contain xfonts-cyrillic, which is suggested by xterm 379-1. Further, gdm-x-session from gdm3 43.0-3 still warns us: Jun 25 20:25:25 AnonymizedMachineName dbus-daemon[973]: [session uid=119 pid=973] Activating systemd to hand-off: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=119 pid=961 comm="/usr/libexec/tracker-extract-3") Jun 25 20:25:25 AnonymizedMachineName /usr/libexec/gdm-x-session[977]: (==) No Layout section. Using the first Screen section. Jun 25 20:25:25 AnonymizedMachineName /usr/libexec/gdm-x-session[977]: (==) No screen section available. Using defaults. Jun 25 20:25:25 AnonymizedMachineName /usr/libexec/gdm-x-session[977]: (**) |-->Screen "Default Screen Section" (0) Jun 25 20:25:25 AnonymizedMachineName /usr/libexec/gdm-x-session[977]: (**) | |-->Monitor "" Jun 25 20:25:25 AnonymizedMachineName /usr/libexec/gdm-x-session[977]: (==) No monitor specified for screen "Default Screen Section". Jun 25 20:25:25 AnonymizedMachineName /usr/libexec/gdm-x-session[977]: Using a default monitor configuration. Jun 25 20:25:25 AnonymizedMachineName /usr/libexec/gdm-x-session[977]: (==) Automatically adding devices Jun 25 20:25:25 AnonymizedMachineName /usr/libexec/gdm-x-session[977]: (==) Automatically enabling devices Jun 25 20:25:25 AnonymizedMachineName /usr/libexec/gdm-x-session[977]: (==) Automatically adding GPU devices Jun 25 20:25:25 AnonymizedMachineName /usr/libexec/gdm-x-session[977]: (==) Automatically binding GPU devices Jun 25 20:25:25 AnonymizedMachineName /usr/libexec/gdm-x-session[977]: (==) Max clients allowed: 256, resource mask: 0x1f Jun 25 20:25:25 AnonymizedMachineName dbus-daemon[973]: [session uid=119 pid=973] Successfully activated service 'org.freedesktop.systemd1' Jun 25 20:25:25 AnonymizedMachineName /usr/libexec/gdm-x-session[977]: (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Jun 25 20:25:25 AnonymizedMachineName /usr/libexec/gdm-x-session[977]: Entry deleted from font path.
Bug#1038935: marked as done (ruby-activerecord: missing Conflicts: ruby-arel)
Your message dated Sun, 25 Jun 2023 23:04:10 + with message-id and subject line Bug#1038935: fixed in rails 2:6.1.7.3+dfsg-2 has caused the Debian Bug report #1038935, regarding ruby-activerecord: missing Conflicts: ruby-arel 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.) -- 1038935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: schleuder Version: 4.0.3-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster' to 'bullseye' to 'bookworm'. It installed fine in 'buster', and upgraded to 'bullseye' successfully, but then the upgrade to 'bookworm' failed. >From the attached log (scroll to the bottom...): Setting up schleuder (4.0.3-7) ... Installing new version of config file /etc/postfix/schleuder_sqlite.cf ... Installing new version of config file /etc/schleuder/schleuder.yml ... rake aborted! NoMethodError: undefined method `preparable=' for #, @right=#> collector.preparable = true ^ /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/connection_adapters/abstract/database_statements.rb:27:in `to_sql_and_binds' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/connection_adapters/abstract/database_statements.rb:64:in `select_all' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/connection_adapters/abstract/query_cache.rb:103:in `select_all' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/relation/calculations.rb:200:in `block in pluck' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/relation.rb:861:in `skip_query_cache_if_necessary' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/relation/calculations.rb:196:in `pluck' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/schema_migration.rb:46:in `all_versions' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1282:in `load_migrated' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1278:in `migrated' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1314:in `ran?' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1260:in `block in runnable' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1260:in `reject' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1260:in `runnable' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1302:in `migrate_without_lock' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1253:in `migrate' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1086:in `up' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1061:in `migrate' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/tasks/database_tasks.rb:237:in `migrate' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/railties/databases.rake:92:in `block (3 levels) in ' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/railties/databases.rake:90:in `each' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/railties/databases.rake:90:in `block (2 levels) in ' Tasks: TOP => db:migrate (See full trace by running task with --trace) dpkg: error processing package schleuder (--configure): installed schleuder package post-installation script subprocess returned error exit status 1 This does not happen on the bullseye -> bookworm upgrade path. This is unrelated to bug #1036950: "schleuder: fails to upgrade from 'buster': insufficient dependency on ruby-activerecord (>= 2:6)", i.e. it is reproducible even if that bug is fixed in bullseye. cheers, Andreas schleuder_4.0.3-7.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: rails Source-Version: 2:6.1.7.3+dfsg-2 Done: Georg Faerber We believe that the bug you reported is fixed in the latest version of rails,
Bug#1039438: enigma: Embded and use lua copy (outdated)
Source: enigma Severity: serious Tags: security Justification: embded X-Debbugs-Cc: Debian Security Team Dear Maintainer, You ship a outdated and embed lua: - could you use the system library - repack in order to avoid compiling accidentally the embded version Bastien -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel Kernel: Linux 6.1.0-9-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1039119: darktable: use packaged lua
Source: darktable Version: Use packaged lua Severity: serious Justification: embded code copy Dear Maintainer, It appear that your package embded and compile lua Could you: - use the packaged lua lib - repack in order to avoid accidental reintroduction of compiling lua rouca -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel Kernel: Linux 6.1.0-9-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1039064: marked as done (binutils-msp430: file conflict with binutils-x86-64-linux-gnu)
Your message dated Sun, 25 Jun 2023 21:34:14 + with message-id and subject line Bug#1039064: fixed in binutils-msp430 2.24~ti3 has caused the Debian Bug report #1039064, regarding binutils-msp430: file conflict with binutils-x86-64-linux-gnu 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.) -- 1039064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: binutils-msp430 Version: 2.24~ti2 Severity: serious Justification: Policy 7.6.1 libdeb.so is both in binutils-x86-64-linux-gnu and binutils-msp430 in the same location. This was not the case in ~ti1, where libdeb.so was in /usr/lib/bfd-plugins/libdep.so. Thus the upgrade fails: Preparing to unpack .../binutils-msp430_2.24~ti2_amd64.deb ... Unpacking binutils-msp430 (2.24~ti2) over (2.24~ti1) ... dpkg: error processing archive /var/cache/apt/archives/binutils-msp430_2.24~ti2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/bfd-plugins/libdep.so', which is also in package binutils-x86-64-linux-gnu 2.40.50.20230622-1 Errors were encountered while processing: /var/cache/apt/archives/binutils-msp430_2.24~ti2_amd64.deb -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-rc7 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages binutils-msp430 depends on: ii libc6 2.36-9 ii libzstd1 1.5.5+dfsg2-1 ii msp430mcu 20120406-2.3 binutils-msp430 recommends no packages. binutils-msp430 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: binutils-msp430 Source-Version: 2.24~ti3 Done: Vagrant Cascadian We believe that the bug you reported is fixed in the latest version of binutils-msp430, 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 1039...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vagrant Cascadian (supplier of updated binutils-msp430 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 25 Jun 2023 14:06:39 -0700 Source: binutils-msp430 Architecture: source Version: 2.24~ti3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Vagrant Cascadian Closes: 1039064 Changes: binutils-msp430 (2.24~ti3) unstable; urgency=medium . * debian/rules: Pass libdir to configure. (Closes: #1039064) * debian/control: Apply "wrap-and-sort -st" to Build-Depends. * Remove needless debian/dirs file. * Remove empty patchlist file. * debian/rules: Drop unused VERSION variable. Checksums-Sha1: dd5f61570f34d313cb84b674b2bf2e837ac02ab5 1190 binutils-msp430_2.24~ti3.dsc 747cc2c322081cd46a09fda68e798a0df96079d5 3424 binutils-msp430_2.24~ti3.tar.xz Checksums-Sha256: b0eb34b6af8338f5eb1c17279686a4ab174ca742291eee3c014fcbab6799ddbc 1190 binutils-msp430_2.24~ti3.dsc ad0fb9c21d558a8917b66b3d2dc189cbbaa73fa1cf827f1c9886cc02543a56cd 3424 binutils-msp430_2.24~ti3.tar.xz Files: ad4b9997579b49765d3a25ada9c454c2 1190 devel optional binutils-msp430_2.24~ti3.dsc 954bec48377e2564a501db0960f6968a 3424 devel optional binutils-msp430_2.24~ti3.tar.xz -BEGIN PGP SIGNATURE- iJYEARYKAD4WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCZJitZyAcdmFncmFudEBy ZXByb2R1Y2libGUtYnVpbGRzLm9yZwAKCRDcUY/If5cWqm9rAP9F1x5uijN0jSAm 4eMtIp0JYrdEsiC/GZyWpYDg6PcedgD6As/vdDPpFHUXYfVWGMGXDsMmAOqanacP LU0ISVvqdQQ= =uWnx -END PGP SIGNATURE End Message ---
Processed: severity of 1032830 is serious
Processing commands for cont...@bugs.debian.org: > severity 1032830 serious Bug #1032830 [src:gnumail] gnumail: FTBFS with pantomime/1.4.0 Bug #1038734 [src:gnumail] src:gnumail: FTBFS with pantomime/1.4.0: MailboxManagerController.m:801:33: error: ‘struct CWFolder’ has no member named ‘allMessages’ Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1032830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032830 1038734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1039064: binutils-msp430: file conflict with binutils-x86-64-linux-gnu
On 2023-06-25, Ingo Saitz wrote: > libdeb.so is both in binutils-x86-64-linux-gnu and binutils-msp430 in > the same location. This was not the case in ~ti1, where libdeb.so was in > /usr/lib/bfd-plugins/libdep.so. Thus the upgrade fails: > > Preparing to unpack .../binutils-msp430_2.24~ti2_amd64.deb ... > Unpacking binutils-msp430 (2.24~ti2) over (2.24~ti1) ... > dpkg: error processing archive > /var/cache/apt/archives/binutils-msp430_2.24~ti2_amd64.deb (--unpack): > trying to overwrite '/usr/lib/x86_64-linux-gnu/bfd-plugins/libdep.so', which > is also in package binutils-x86-64-linux-gnu 2.40.50.20230622-1 > Errors were encountered while processing: > /var/cache/apt/archives/binutils-msp430_2.24~ti2_amd64.deb Thanks for the report! My bad, this points to some even deeper problems with the updates to this package... live well, vagrant signature.asc Description: PGP signature
Processed: closing 1023370
Processing commands for cont...@bugs.debian.org: > close 1023370 Bug #1023370 [php-parser] [php-parser] Failing tests with PHP 8.2 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1023370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038883: marked as done (dolfin: autopkgtest failure due to bytes as docstring)
Your message dated Sun, 25 Jun 2023 16:50:03 + with message-id and subject line Bug#1038883: fixed in dolfin 2019.2.0~legacy20230609.8b85e9d.ar-1 has caused the Debian Bug report #1038883, regarding dolfin: autopkgtest failure due to bytes as docstring 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.) -- 1038883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dolfin Version: 2019.2.0~git20230116.bd54183-2 Severity: serious Tags: patch X-Debbugs-Cc: debian-pyt...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, your package fails the autopkgtest with the new pytest 7.3 because python/test/unit/function/test_function_space.py uses a bytes object (b""" literal) as module docstring, and pytest crashes while looking for the "PYTEST_DONT_REWRITE" marker. As far as I understand, using a bytes() object as docstring violates PEP-257, which is why I am filing this as a dolfin bug and not a pytest regression. I have Cc'd the debian-python mailing list for a second opinion, but I believe this bug should be resolved by getting rid of the erroneous "b" prefix. Cheers Timo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmSUVIMACgkQ+C8H+466 LVlDnwwAvkNiICYQNkEcEL6b8cCBs5omarn94D+xGVDAILX/LZvOJxzpL2fklo4Y 4cdyjdiq3Kye5j/tQ5C4CE76jEBt3Y/JCXKJnet8PpM2mrD1mBJR9m5yxznrgxer 9jZPGx9I8F2/E/O211cSMC+5WgX5OePD9mIlVDINmXRRU6NGgm1KIMaFhG5rS0qW 6OG0cjX6UrzlEbiD+xZbt56dlfZz3o1FvRqSaGmRwNVsDeRuNdrYiN15FVnqOw88 0sy+wgE/x74hCCNgqkDeHQiZfO+fw9sIn0g0NU4pa2HqZHO7yRjJrctohvPkfHTd U1R7yfZZOeSJVVC2+RyRBjOYudG9p4C3qraGnfRlZ9s64ok5rwVruZ6mK9eWClMU VJcIpLVrSIWyuYdGsu2Cj/mmdfypDDsPk7Yp+U21g+EThv2CI9vlgwnKwhTNBtwa fT4oKTn+odfYLUzv3+tSd1FdYyGZB71m4X4i7ckzShf8uL4zMiYB7WhFhm+9QCfs 9+rI0cvw =gZ+8 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: dolfin Source-Version: 2019.2.0~legacy20230609.8b85e9d.ar-1 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of dolfin, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated dolfin 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, 25 Jun 2023 13:24:37 +0200 Source: dolfin Architecture: source Version: 2019.2.0~legacy20230609.8b85e9d.ar-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Drew Parsons Closes: 1038883 Changes: dolfin (2019.2.0~legacy20230609.8b85e9d.ar-1) unstable; urgency=medium . * snapshot of upstream ufl_legacy branch - source tarball generated with git archive to catch git-lfs files - applies debian ufl_legacy renaming patches * document use of ufl_legacy in debian/NEWS and in README.Debian. Install README.Debian in libdolfin-dev, python3-dolfin, dolfin-doc. * debian patch docstring_not_byte.patch fixes docstring. The byte string broke pytest 7.3 (PYTEST_DONT_REWRITE). Thanks Timo Röhling. Closes: #1038883. Checksums-Sha1: c1ee875c913ab9c444667741dc53379adbbe803f 3949 dolfin_2019.2.0~legacy20230609.8b85e9d.ar-1.dsc c4f6e38bf19f507d8e84f701a3309e974aa669b1 10888794 dolfin_2019.2.0~legacy20230609.8b85e9d.ar.orig.tar.gz a56d185c03e456798ef3bca470f0cc4912f3db33 41796 dolfin_2019.2.0~legacy20230609.8b85e9d.ar-1.debian.tar.xz Checksums-Sha256: b8372b161db01823ea44b2abcd125db4a1cf87a6c08fead2034e3ab3887715c0 3949 dolfin_2019.2.0~legacy20230609.8b85e9d.ar-1.dsc 3d86f4f7ec4a27d5a6a976d360bf28057c08a41a705f6f02e50b11d7c85437a4 10888794 dolfin_2019.2.0~legacy20230609.8b85e9d.ar.orig.tar.gz 995be21c50cb2b17006dade37d1cbbc9ce18b2dc9b2c37d3f56ea9336e0a447d 41796 dolfin_2019.2.0~legacy20230609.8b85e9d.ar-1.debian.tar.xz Files: cdb149f238bde36d9038b88d10bb8c6f 3949 math optional dolfin_2019.2.0~legacy20230609.8b85e9d.ar-1.dsc 60f0dc08904c6690aa803dacc7662962 10888794 math optional dolfin_2019.2.0~legacy20230609.8b85e9d.ar.orig.tar.gz 91ac40da41de687b1bdbf26bfcefe7d9 41796 math optional
Bug#1039088: whitedb: embed yajl
Source: whitedb Version: embed yajl Severity: serious Justification: devref Dear Maintainer, Your package embed a copy of yajl. Could you: - compile against debian yajl package - remove by repacking the yajl code copy in order to accidentally compile the embed code copy Thanks Rouca -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel Kernel: Linux 6.1.0-9-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1039087: epic-base: embed yajl
Source: epic-base Severity: serious Justification: devref Dear Maintainer, Your package embed a copy of yajl. Could you: - compile against the packaged yajl package - remove by repacking the embded code copy in order to avoid accidental compilation of the embed code copy Thanks Rouca -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel Kernel: Linux 6.1.0-9-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1039086: collada2gltf: Embed yajl
Source: collada2gltf Severity: serious Justification: devref Dear Maintainer, Your package embed a copy a yajl Could you: - build against yajl package - remove by repacking the code copy in order to avoid in the future accidental code compilation against the embed code copy Thanks Bastien -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel Kernel: Linux 6.1.0-9-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1039085: burp: embed yajl
Source: burp Severity: serious Justification: devref Dear Maintainer, Your package embed a code copy of yajl. Could you: - build against yajl debian package - repack your package removing the emded code copy in order to avoid accidental compilation in future. Thanks rouca -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel Kernel: Linux 6.1.0-9-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1039083: crun: Embed yajl
Source: crun Severity: serious Justification: embed code copy devref Dear Maintainer, Your package include an embed code copy of yajl Could you please: - deembed - the repack (+ds source if needed) in order to be sure it will be not compiled in by accident in newer release Thanks Bastien -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel Kernel: Linux 6.1.0-9-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: Re: postgresql-plsh REMOVED from testing
Processing control commands:
> fixed -1 1.3-4
Bug #593999 {Done: Christoph Berg } [src:postgresql-plsh]
postgresql-plsh: missing /usr/share/doc/postgresql-plsh/
Marked as fixed in versions postgresql-plsh/1.3-4.
> notfixed -1 1.3-2
Bug #593999 {Done: Christoph Berg } [src:postgresql-plsh]
postgresql-plsh: missing /usr/share/doc/postgresql-plsh/
No longer marked as fixed in versions 1.3-2.
--
593999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#593999: postgresql-plsh REMOVED from testing
Control: fixed -1 1.3-4 control: notfixed -1 1.3-2 On 25/06/2023 10.43, Christoph Berg wrote: you revived a bug from 2008 that had been fixed in 2010, yet that just caused postgresql-plsh to get removed from testing. Not sure why I had to spend time on that now. The fixing version (1.3-3.1) is not (any longer?) an ancestor of the version in sid according to the changelog, therefore the BTS considered to issue as unfixed after I added an affects in the binary package name at the time the bug existed ... closing it with the next upload (after the fixing NMU) that is part of the history of sid. Andreas
Processed: unarchiving 928226, found 928226 in iceweasel/1:52.9.0esr-1~deb8u1, closing 928226 ...
Processing commands for cont...@bugs.debian.org:
> unarchive 928226
Bug #928226 {Done: Andreas Beckmann }
[firefox-esr-dev,iceweasel-l10n-ak,iceweasel-l10n-csb,iceweasel-l10n-ku,iceweasel-l10n-lg,iceweasel-l10n-nso,iceweasel-l10n-ta-lk,iceweasel-l10n-zu,iceweasel-l10n-be,firefox-esr-l10n-en-za,iceweasel-l10n-mai,iceweasel-l10n-ml,firefox-esr-l10n-or,iceweasel-l10n-as,firefox-esr-l10n-mai,iceweasel-l10n-or,firefox-esr-l10n-as,iceweasel-dev,firefox-esr-l10n-bn-bd,iceweasel-l10n-en-za,firefox-esr-l10n-ml,firefox-esr-l10n-bn-in]
uninstallable cruft package from src:firefox-esr
Warning: Unknown package 'firefox-esr-dev'
Warning: Unknown package 'iceweasel-l10n-ak'
Warning: Unknown package 'iceweasel-l10n-csb'
Warning: Unknown package 'iceweasel-l10n-ku'
Warning: Unknown package 'iceweasel-l10n-lg'
Warning: Unknown package 'iceweasel-l10n-nso'
Warning: Unknown package 'iceweasel-l10n-ta-lk'
Warning: Unknown package 'iceweasel-l10n-zu'
Warning: Unknown package 'firefox-esr-l10n-en-za'
Warning: Unknown package 'iceweasel-l10n-mai'
Warning: Unknown package 'iceweasel-l10n-ml'
Warning: Unknown package 'firefox-esr-l10n-or'
Warning: Unknown package 'iceweasel-l10n-as'
Warning: Unknown package 'firefox-esr-l10n-mai'
Warning: Unknown package 'iceweasel-l10n-or'
Warning: Unknown package 'firefox-esr-l10n-as'
Warning: Unknown package 'iceweasel-dev'
Warning: Unknown package 'firefox-esr-l10n-bn-bd'
Warning: Unknown package 'iceweasel-l10n-en-za'
Warning: Unknown package 'firefox-esr-l10n-ml'
Warning: Unknown package 'firefox-esr-l10n-bn-in'
Unarchived Bug 928226
Warning: Unknown package 'firefox-esr-dev'
Warning: Unknown package 'iceweasel-l10n-ak'
Warning: Unknown package 'iceweasel-l10n-csb'
Warning: Unknown package 'iceweasel-l10n-ku'
Warning: Unknown package 'iceweasel-l10n-lg'
Warning: Unknown package 'iceweasel-l10n-nso'
Warning: Unknown package 'iceweasel-l10n-ta-lk'
Warning: Unknown package 'iceweasel-l10n-zu'
Warning: Unknown package 'firefox-esr-l10n-en-za'
Warning: Unknown package 'iceweasel-l10n-mai'
Warning: Unknown package 'iceweasel-l10n-ml'
Warning: Unknown package 'firefox-esr-l10n-or'
Warning: Unknown package 'iceweasel-l10n-as'
Warning: Unknown package 'firefox-esr-l10n-mai'
Warning: Unknown package 'iceweasel-l10n-or'
Warning: Unknown package 'firefox-esr-l10n-as'
Warning: Unknown package 'iceweasel-dev'
Warning: Unknown package 'firefox-esr-l10n-bn-bd'
Warning: Unknown package 'iceweasel-l10n-en-za'
Warning: Unknown package 'firefox-esr-l10n-ml'
Warning: Unknown package 'firefox-esr-l10n-bn-in'
> found 928226 iceweasel/1:52.9.0esr-1~deb8u1
Bug #928226 {Done: Andreas Beckmann }
[firefox-esr-dev,iceweasel-l10n-ak,iceweasel-l10n-csb,iceweasel-l10n-ku,iceweasel-l10n-lg,iceweasel-l10n-nso,iceweasel-l10n-ta-lk,iceweasel-l10n-zu,iceweasel-l10n-be,firefox-esr-l10n-en-za,iceweasel-l10n-mai,iceweasel-l10n-ml,firefox-esr-l10n-or,iceweasel-l10n-as,firefox-esr-l10n-mai,iceweasel-l10n-or,firefox-esr-l10n-as,iceweasel-dev,firefox-esr-l10n-bn-bd,iceweasel-l10n-en-za,firefox-esr-l10n-ml,firefox-esr-l10n-bn-in]
uninstallable cruft package from src:firefox-esr
Warning: Unknown package 'firefox-esr-dev'
Warning: Unknown package 'iceweasel-l10n-ak'
Warning: Unknown package 'iceweasel-l10n-csb'
Warning: Unknown package 'iceweasel-l10n-ku'
Warning: Unknown package 'iceweasel-l10n-lg'
Warning: Unknown package 'iceweasel-l10n-nso'
Warning: Unknown package 'iceweasel-l10n-ta-lk'
Warning: Unknown package 'iceweasel-l10n-zu'
Warning: Unknown package 'firefox-esr-l10n-en-za'
Warning: Unknown package 'iceweasel-l10n-mai'
Warning: Unknown package 'iceweasel-l10n-ml'
Warning: Unknown package 'firefox-esr-l10n-or'
Warning: Unknown package 'iceweasel-l10n-as'
Warning: Unknown package 'firefox-esr-l10n-mai'
Warning: Unknown package 'iceweasel-l10n-or'
Warning: Unknown package 'firefox-esr-l10n-as'
Warning: Unknown package 'iceweasel-dev'
Warning: Unknown package 'firefox-esr-l10n-bn-bd'
Warning: Unknown package 'iceweasel-l10n-en-za'
Warning: Unknown package 'firefox-esr-l10n-ml'
Warning: Unknown package 'firefox-esr-l10n-bn-in'
The source iceweasel and version 1:52.9.0esr-1~deb8u1 do not appear to match
any binary packages
Marked as found in versions iceweasel/1:52.9.0esr-1~deb8u1 and reopened.
Warning: Unknown package 'firefox-esr-dev'
Warning: Unknown package 'iceweasel-l10n-ak'
Warning: Unknown package 'iceweasel-l10n-csb'
Warning: Unknown package 'iceweasel-l10n-ku'
Warning: Unknown package 'iceweasel-l10n-lg'
Warning: Unknown package 'iceweasel-l10n-nso'
Warning: Unknown package 'iceweasel-l10n-ta-lk'
Warning: Unknown package 'iceweasel-l10n-zu'
Warning: Unknown package 'firefox-esr-l10n-en-za'
Warning: Unknown package 'iceweasel-l10n-mai'
Warning: Unknown package 'iceweasel-l10n-ml'
Warning: Unknown package 'firefox-esr-l10n-or'
Warning: Unknown package 'iceweasel-l10n-as'
Warning: Unknown package 'firefox-esr-l10n-mai'
Warning: Unknown package 'iceweasel-l10n-or'
Warning: Unknown package 'firefox-esr-l10n-as'
Warning:
Bug#1034577: Bug exists also for banks using Fiducia
Hi S. Seide, Am 27.05.23 um 22:04 schrieb S. Seide: As this problem affects a lot of german users - is there a change to promote this package to stable to fix this false security warning? Meanwhile Debian Bookworm got released as latest stable release, so I'd recommend users still on the now oldstable release (Bullseye) to upgrade to the latest stable release, where this bug is fixed. Best regards, Micha
Bug#1038152: marked as done (supertuxkart: Supertuxkart does not start - missing NotoColorEmoji.ttf)
Your message dated Sun, 25 Jun 2023 14:28:25 +0200 with message-id and subject line Re: Bug#1038152: supertuxkart: Supertuxkart does not start - missing NotoColorEmoji.ttf has caused the Debian Bug report #1038152, regarding supertuxkart: Supertuxkart does not start - missing NotoColorEmoji.ttf 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.) -- 1038152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: supertuxkart Version: 1.4+dfsg-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: matta2...@gmail.com Dear Maintainer, after clean apt install, STK does not start. [info ] SharedGPUObjects: Hardware Skinning enabled, method: TBO, max bones: 1024 [info ] ShaderFilesManager: Compiling shader: /usr/share/games/supertuxkart/data/shaders/screenquad.vert [info ] ShaderFilesManager: Compiling shader: /usr/share/games/supertuxkart/data/shaders/motion_blur.frag [info ] ShaderFilesManager: Compiling shader: /usr/share/games/supertuxkart/data/shaders/lightning.frag [info ] ShaderFilesManager: Compiling shader: /usr/share/games/supertuxkart/data/shaders/primitive2dlist.vert [info ] ShaderFilesManager: Compiling shader: /usr/share/games/supertuxkart/data/shaders/transparent.frag [info ] ShaderFilesManager: Compiling shader: /usr/share/games/supertuxkart/data/shaders/texturedquad.vert [info ] ShaderFilesManager: Compiling shader: /usr/share/games/supertuxkart/data/shaders/uniformcolortexturedquad.frag [info ] ShaderFilesManager: Compiling shader: /usr/share/games/supertuxkart/data/shaders/texturedquad.frag [info ] ShaderFilesManager: Compiling shader: /usr/share/games/supertuxkart/data/shaders/coloredquad.vert [info ] ShaderFilesManager: Compiling shader: /usr/share/games/supertuxkart/data/shaders/coloredquad.frag [info ] ShaderFilesManager: Compiling shader: /usr/share/games/supertuxkart/data/shaders/colortexturedquad.vert [info ] ShaderFilesManager: Compiling shader: /usr/share/games/supertuxkart/data/shaders/colortexturedquad.frag [info ] irr_driver: GLSL supported. [info ] GUI: Loading skin data from file: /usr/share/games/supertuxkart/data/skins/peach/stkskin.xml [fatal ] [FileManager]: Can not find file 'NotoColorEmoji.ttf' in '/usr/share/games/supertuxkart/data/ttf/' Can not find file 'NotoColorEmoji.ttf ' in '/usr/share/games/supertuxkart/data/ttf/' /usr/share/games/supertuxkart/data/ttf> ls -la total 4588 drwxr-xr-x 2 root root4096 May 29 11:15 . drwxr-xr-x 20 root root4096 May 29 11:15 .. lrwxrwxrwx 1 root root 58 Feb 28 23:00 Cantarell-Regular.otf -> ../../../../fonts/opentype/cantarell/Cantarell-Regular.otf lrwxrwxrwx 1 root root 50 Feb 28 23:00 NotoColorEmoji.ttf -> ../../../../fonts/truetype/noto/NotoColorEmoji.ttf lrwxrwxrwx 1 root root 61 Feb 28 23:00 NotoNaskhArabicUI-Regular.ttf -> ../../../../fonts/truetype/noto/NotoNaskhArabicUI-Regular.ttf lrwxrwxrwx 1 root root 58 Feb 28 23:00 NotoSansHebrew-Regular.ttf -> ../../../../fonts/truetype/noto/NotoSansHebrew-Regular.ttf lrwxrwxrwx 1 root root 61 Feb 28 23:00 NotoSansMalayalam-Regular.ttf -> ../../../../fonts/truetype/noto/NotoSansMalayalam-Regular.ttf lrwxrwxrwx 1 root root 56 Feb 28 23:00 NotoSansThai-Regular.ttf -> ../../../../fonts/truetype/noto/NotoSansThai-Regular.ttf -rw-r--r-- 1 root root 50384 Oct 31 2022 SigmarOne.otf -rw-r--r-- 1 root root 4626376 Oct 31 2022 wqy-microhei.ttf /usr/share/games/supertuxkart/data/ttf> ls -la ../../../../fonts/truetype/noto/NotoColorEmoji.ttf bash: ../../../../fonts/truetype/noto/NotoColorEmoji.ttf: No such file or directory Maybe there is a dependency issue, missing a noto package to install NotoColorEmoji.ttf Do you mind checking it? Thanks, -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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 supertuxkart depends on: ii libbluetooth3 5.66-1 ii libc6 2.36-9 ii libcurl3-gnutls7.88.1-10 ii libfreetype6 2.12.1+dfsg-5 ii libgcc-s1 12.2.0-14 ii libharfbuzz0b 6.0.0+dfsg-3 ii libjpeg62-turbo1:2.1.5-2 ii libmbedcrypto7 2.28.3-1 ii libmcpp0 2.7.2-5 ii libopenal1
Bug#1039064: binutils-msp430: file conflict with binutils-x86-64-linux-gnu
Package: binutils-msp430 Version: 2.24~ti2 Severity: serious Justification: Policy 7.6.1 libdeb.so is both in binutils-x86-64-linux-gnu and binutils-msp430 in the same location. This was not the case in ~ti1, where libdeb.so was in /usr/lib/bfd-plugins/libdep.so. Thus the upgrade fails: Preparing to unpack .../binutils-msp430_2.24~ti2_amd64.deb ... Unpacking binutils-msp430 (2.24~ti2) over (2.24~ti1) ... dpkg: error processing archive /var/cache/apt/archives/binutils-msp430_2.24~ti2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/bfd-plugins/libdep.so', which is also in package binutils-x86-64-linux-gnu 2.40.50.20230622-1 Errors were encountered while processing: /var/cache/apt/archives/binutils-msp430_2.24~ti2_amd64.deb -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-rc7 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) Versions of packages binutils-msp430 depends on: ii libc6 2.36-9 ii libzstd1 1.5.5+dfsg2-1 ii msp430mcu 20120406-2.3 binutils-msp430 recommends no packages. binutils-msp430 suggests no packages. -- no debconf information
Bug#1039048: marked as done (php-doctrine-cache: unsatisfiable build dependency)
Your message dated Sun, 25 Jun 2023 09:07:02 + with message-id and subject line Bug#1039048: fixed in php-doctrine-cache 2.2.0-2 has caused the Debian Bug report #1039048, regarding php-doctrine-cache: unsatisfiable build dependency 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.) -- 1039048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: php-doctrine-cache Version: 2.2.0-1 Severity: serious Tags: trixie, sid php-doctrine-cache build-depends on php-nrk-predis which was a transitional dummy package in bookworm and no longer exists in trixie or sid. Presumablly the build-dependency should be changed to php-predis. --- End Message --- --- Begin Message --- Source: php-doctrine-cache Source-Version: 2.2.0-2 Done: David Prévot We believe that the bug you reported is fixed in the latest version of php-doctrine-cache, 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 1039...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Prévot (supplier of updated php-doctrine-cache 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, 25 Jun 2023 10:21:00 +0200 Source: php-doctrine-cache Architecture: source Version: 2.2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: David Prévot Closes: 1039048 Changes: php-doctrine-cache (2.2.0-2) unstable; urgency=medium . * Drop now useless build-dependency * Drop unused php-predis (Closes: #1039048) * Update standards version to 4.6.2, no changes needed. Checksums-Sha1: e3ff466d12840c25695ecd3fa08525052b87dec9 2186 php-doctrine-cache_2.2.0-2.dsc 3cb6edaa1b76439cfc6640e562fb55153b1337e5 14908 php-doctrine-cache_2.2.0-2.debian.tar.xz 46795142b2275c6353e2f78c8c5bfb64f818fe5a 8947 php-doctrine-cache_2.2.0-2_amd64.buildinfo Checksums-Sha256: dbdeae13b24f04109a796e266c1863392b69b4f4fa594971c364c92d925771c0 2186 php-doctrine-cache_2.2.0-2.dsc 0921bd4736f1f43f77f90948c6da368e488a117053dffd7b8f9c881789be91f4 14908 php-doctrine-cache_2.2.0-2.debian.tar.xz f53d8c5ff7d978398dbe367c3586230ad1f84846382ea0853dbd5371b894d160 8947 php-doctrine-cache_2.2.0-2_amd64.buildinfo Files: 8b398813d5c16b5c8176917b2aed6705 2186 php optional php-doctrine-cache_2.2.0-2.dsc 07e76d829ce4cd7c0caebf8b2f3db771 14908 php optional php-doctrine-cache_2.2.0-2.debian.tar.xz 7b95356c22c325edd42ddedf46a419c7 8947 php optional php-doctrine-cache_2.2.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQFGBAEBCAAwFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAmSX/OESHHRhZmZpdEBk ZWJpYW4ub3JnAAoJEAWMHPlE9r08rcUH/ip+Hlc3popnpjQG5XCcZZRZsMjUt4i8 /COLy2iCRtNOlfqWSuyQts3AzE1CIkYVGE33fBQe5EbqM1Ms1yloYxZQ0cPFIF9N a6BZGW0FMGR1XsQ1UiKcfdaGC72dxyDFO6TBGBCKdF3+bn3PosRegxLv0a9bV+wp 3eEQU/jpPp1VzNDAD2oJOKI5GycvZBsMV3wotP8g7byNcbW1mkR0M2Xo5pPbz6Po vsgv4Qe1jYca7TDBDt0hGblahhMckSTPLe1ZogByLKJWSzwrIQRPUScVv2edHRPn jWe8hcRNGGuf3ugfhMNdgEjkxG1SI9kZ+RT/y/nzyo3crMAvYjwI16s= =+8WU -END PGP SIGNATURE End Message ---
Bug#593999: marked as done (postgresql-plsh: missing /usr/share/doc/postgresql-plsh/)
Your message dated Sun, 25 Jun 2023 10:43:00 +0200
with message-id
and subject line Re: postgresql-plsh REMOVED from testing
has caused the Debian Bug report #593999,
regarding postgresql-plsh: missing /usr/share/doc/postgresql-plsh/
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.)
--
593999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-plsh
Version: 1.3-3
Severity: serious
Tags: patch
Justification: Policy 2.3, 12.7
/usr/share/doc/postgresql-plsh/ is missing on non-i386 architectures:
$ debdiff postgresql-8.4-plsh_1.3-3_i386.deb postgresql-8.4-plsh_1.3-3_amd64.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in first .deb but not in second
-
-rw-r--r-- root/root /usr/share/doc/postgresql-8.4-plsh/NEWS.gz
-rw-r--r-- root/root /usr/share/doc/postgresql-8.4-plsh/README
-rw-r--r-- root/root /usr/share/doc/postgresql-8.4-plsh/README.Debian
-rw-r--r-- root/root /usr/share/doc/postgresql-8.4-plsh/changelog.Debian.gz
-rw-r--r-- root/root /usr/share/doc/postgresql-8.4-plsh/copyright
Control files: lines which differ (wdiff format)
Architecture: [-i386-] {+amd64+}
Depends: libc6 (>= [-2.2),-] {+2.2.5),+} postgresql-8.4
Installed-Size: [-80-] {+56+}
--
Jakub Wilk
diff -u postgresql-plsh-1.3/debian/rules postgresql-plsh-1.3/debian/rules
--- postgresql-plsh-1.3/debian/rules
+++ postgresql-plsh-1.3/debian/rules
@@ -46,6 +46,7 @@
binary-arch: install
dh_testdir
dh_testroot
+ dh_installdocs -a
dh_install -a
dh_link -a
dh_strip -a
@@ -58,20 +59,7 @@
dh_builddeb -a
-binary-indep: install
- dh_testdir
- dh_testroot
- dh_installdocs -a
- dh_install -i
- dh_link -i
- dh_compress -i
- dh_fixperms -i
- dh_installdeb -i
- dh_gencontrol -i
- dh_md5sums -i
- dh_builddeb -i
- dh_installchangelogs
-
+binary-indep:
binary: binary-arch binary-indep
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1.3-2
Re: Debian testing watch
> FYI: The status of the postgresql-plsh source package
> in Debian's testing distribution has changed.
>
> Previous version: 1.20220917-1
> Current version: (not in testing)
> Hint:
> Bug #593999: postgresql-plsh: missing /usr/share/doc/postgresql-plsh/
Hi Andreas,
you revived a bug from 2008 that had been fixed in 2010, yet that just
caused postgresql-plsh to get removed from testing. Not sure why I had
to spend time on that now.
Christoph--- End Message ---
Processed: limit source to php-doctrine-cache, tagging 1039048
Processing commands for cont...@bugs.debian.org: > limit source php-doctrine-cache Limiting to bugs with field 'source' containing at least one of 'php-doctrine-cache' Limit currently set to 'source':'php-doctrine-cache' > tags 1039048 + pending Bug #1039048 [php-doctrine-cache] php-doctrine-cache: unsatisfiable build dependency Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1039048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1039054: miniupnpd-nftables: Fails to start: /etc/miniupnpd/nft_init.sh: 75: -f: not found
Package: miniupnpd-nftables Version: 2.3.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, In the hope of fixing miniupnpd breakage on my system (different problem to #1033012 BTW), I switched from the xtables backend to nftables. Unfortunately, like miniupnpd-iptables, the systemd configuration seems to be in a "could never have worked" state. Line 75 of /etc/miniupnpd/nft_init.sh is: $NFT -f /tmp/miniupnpd.nft Nothing in miniupnpd or miniupnpd-nftables defines $NFT! Okay, so I add 'NFT=nft' to miniupnpd_functions.sh. I then discover that neither $TABLE, $NAT_TABLE, $CHAIN, $PREROUTING_CHAIN, or $POSTROUTING_CHAIN are set either. I worked around all this by setting all of the above from within miniupnpd_functions.sh, but I expect the correct fix would also take into account table/chain names specified in miniupnpd.conf -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldoldstable-updates'), (500, 'oldoldstable-debug'), (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable'), (460, 'unstable') Architecture: i386 (i686) Kernel: Linux 6.1.0-9-686-pae (SMP w/1 CPU thread; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages miniupnpd-nftables depends on: ii libc6 2.36-9 ii libmnl0 1.0.4-3 ii libnftnl11 1.2.4-2 miniupnpd-nftables recommends no packages. miniupnpd-nftables suggests no packages. -- no debconf information
Bug#1035416: marked as done (openjdk-21-jre: breaks ca-certificates-java)
Your message dated Sun, 25 Jun 2023 08:02:03 +0200 with message-id and subject line Re: openjdk-21-jre: breaks ca-certificates-java has caused the Debian Bug report #1035416, regarding openjdk-21-jre: breaks ca-certificates-java 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.) -- 1035416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openjdk-21-jre Version: 21~7ea-1 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 ca-certificates-java (20230103) ... Exception in thread "main" java.lang.InternalError: Error loading java.security file at java.base/java.security.Security.initialize(Security.java:105) at java.base/java.security.Security.lambda$static$0(Security.java:84) at java.base/java.security.AccessController.doPrivileged(AccessController.java:319) at java.base/java.security.Security.(Security.java:83) at java.base/sun.security.jca.ProviderList.(ProviderList.java:179) at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:96) at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:94) at java.base/java.security.AccessController.doPrivileged(AccessController.java:319) at java.base/sun.security.jca.ProviderList.fromSecurityProperties(ProviderList.java:93) at java.base/sun.security.jca.Providers.(Providers.java:55) at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:156) at java.base/java.security.cert.CertificateFactory.getInstance(CertificateFactory.java:193) at org.debian.security.KeyStoreHandler.(KeyStoreHandler.java:50) at org.debian.security.UpdateCertificates.(UpdateCertificates.java:65) at org.debian.security.UpdateCertificates.main(UpdateCertificates.java:51) dpkg: error processing package ca-certificates-java (--configure): installed ca-certificates-java package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of openjdk-21-jre-headless:amd64: openjdk-21-jre-headless:amd64 depends on ca-certificates-java (>= 20190405~); however: Package ca-certificates-java is not configured yet. dpkg: error processing package openjdk-21-jre-headless:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of openjdk-21-jre:amd64: openjdk-21-jre:amd64 depends on openjdk-21-jre-headless (= 21~7ea-1); however: Package openjdk-21-jre-headless:amd64 is not configured yet. dpkg: error processing package openjdk-21-jre:amd64 (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.36-9) ... Processing triggers for ca-certificates (20230311) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Errors were encountered while processing: ca-certificates-java openjdk-21-jre-headless:amd64 openjdk-21-jre:amd64 This works fine with earlier jre versions. cheers, Andreas openjdk-21-jre_21~7ea-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- that should be fixed now.--- End Message ---
