Bug#1052220: marked as done (unrecognized option '--insert-timestamp=1686475264')
Your message dated Thu, 21 Sep 2023 05:48:59 + with message-id and subject line Bug#1052220: fixed in gcc-mingw-w64 25.3 has caused the Debian Bug report #1052220, regarding unrecognized option '--insert-timestamp=1686475264' 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.) -- 1052220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: binutils-mingw-w64-i686 Version: 2.41-4+11+nmu1 Severity: serious Tags: ftbfs X-Debbugs-Cc: ol...@debian.org, z...@debian.org The NMU binutils-mingw-w64/11+nmu1 drops specify-timestamp.patch. It causes libgcrypt20, gcc-mingw-w64 FTBFS. These packages use options like --insert-timestamp=1686475264, which is not supported in upstream implementation. I find such option is mentioned on https://wiki.debian.org/ReproducibleBuilds/TimestampsInPEBinaries It looks like Debian specific behaviour. --- End Message --- --- Begin Message --- Source: gcc-mingw-w64 Source-Version: 25.3 Done: Stephen Kitt We believe that the bug you reported is fixed in the latest version of gcc-mingw-w64, 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 1052...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Kitt (supplier of updated gcc-mingw-w64 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, 21 Sep 2023 07:23:25 +0200 Source: gcc-mingw-w64 Architecture: source Version: 25.3 Distribution: unstable Urgency: medium Maintainer: Stephen Kitt Changed-By: Stephen Kitt Closes: 1052220 Changes: gcc-mingw-w64 (25.3) unstable; urgency=medium . * Stop setting the build timestamp manually, ld takes care of that itself now. Closes: #1052220. Checksums-Sha1: 36c0db86550356f74f8dd9b87ce0dbc9d2d40fdf 6777 gcc-mingw-w64_25.3.dsc 58e3ef9f49b2321aa179dd0a113ae874dcd73f86 34976 gcc-mingw-w64_25.3.tar.xz 1e62f642195911c979f0f07720f07a47373ccb24 7500 gcc-mingw-w64_25.3_source.buildinfo Checksums-Sha256: 42423509d9eb367c05b47cf45d228b5824332f34a3b03265a798b57f95043dea 6777 gcc-mingw-w64_25.3.dsc 5c8d95850bed0067ada60396cf2adb547a78f36214d7499afe02934f64e022ba 34976 gcc-mingw-w64_25.3.tar.xz be09b96af5a9cdb67c04c100a0191db4c266513148363ec31552d20ad4aa839b 7500 gcc-mingw-w64_25.3_source.buildinfo Files: d7a5deec76f3219f61f11197637ae0e7 6777 devel optional gcc-mingw-w64_25.3.dsc 3e9e2b3d677a022c95aa0fe75471a902 34976 devel optional gcc-mingw-w64_25.3.tar.xz 6b6c86f5445cad756a3289c77e195500 7500 devel optional gcc-mingw-w64_25.3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmUL03gACgkQgNMC9Yht g5zGug//QAWxJQw2Z+x1cb1V4pspWhKeAtqFslzxG8VvlDY1L/hn7gnlu4yENhii 2XWrlg22tOIyL/Ldvx1Aq9b8iVKAHPlh8+5Lt5X5NOjio8J08q8rD8OdyTzmDCMp G89BIHK6RMRU3HmesxaCbEcUnaZ1K04oUzXuM+iioC/QRmroqOlckhStWuW5nErX QdYEHOtcSh0ysRI1dqwTPxYdS+ItQ5awTBe+Ima7FmhA9amq3VW40emqXBAsO2QR 2hTpqsoxW0RekFsGYCA0d/6/8MA0sBfbIZuuMZP4a2soVTVg+Ee3zex26Orj5Xe6 08irao/pQDwPsDqi5OUqeJLSgeAryJkleSG+iu4DTywKDZFKo0cw3JlBZ3mZ9ujP 2I9pHVr8mabO3heQPAnPV0g5t7pQvhgLE8DWmBo8anqZommwOSP0BcBJf5IcxkPk TmzTJ5b4Ats0WCk1zDp/rOXfcTCtqwyk8zgqeHdaKiV9SvEL6vNXkbykElPJyVjd zkmFfOrV8R+Ni0LBO7h/Ios7PAfAx7MvzPtx6GAWJf1K5BI0mJTAVv1mo+LVUF32 qfvgb9mSCpQrM0QgBEQstRPm5WBfpJGqSNYTC2pnE99g43soLSdn57wErkz/7HKc adMdg4/wRu+yZtcrVBJR3xIZae+HBfYPebN387B35fo4mZM9GQs= =XSM0 -END PGP SIGNATURE End Message ---
Bug#1052197: xrdp: after bullseye-security upgrade, empty turquoise screen after logging in
> No, just some kind of ABI thing, but I doubt xrdp upstream already > even guarantees stable ABIs for 0.x releases. We xrdp team already have already started effort for ABI stability but could not strictly guarantee yet. It is almost stable since July 2021 however, we haven't started taking care of ABI stability at the time xorgxrdp 0.2.12 and xrdp 0.9.12 was released. > Yes. Not applicable here, xrdp does not need xorgxrdp to provide > a significant part of use cases. xorgxrdp is a plugin that can be > added to provide the third significant use case out of three, AIUI. Right. xrdp not necessarily requries xorgxrdp but xorgxrdp requires xrdp. Just in case we broke ABI, I recommend to rebuild xorgxrdp everytime updating xrdp but it is not necessary in most cases since we already commit ABI stability. Sorry if we break something. Anyway, thanks everyone who maintain xrdp package for Debian. -- meta
Bug#1052197: xrdp: after bullseye-security upgrade, empty turquoise screen after logging in
On Thu, 21 Sep 2023, Markus Koschany wrote: >dependency problem between xrdp and xorgxrdp. If you claim that without a >rebuild of xorgxrdp a new upstream version of xrdp would be broken, then this >is a strong indication that xorgxrdp should be more than a recommendation in >Debian terms: No, just some kind of ABI thing, but I doubt xrdp upstream already even guarantees stable ABIs for 0.x releases. Probably something like the X server itself or Perl, where xrdp Provides xrdp-abi (= 0.9.21) and xorgxrdp Depends xrdp-abi (= 0.9.12) and therefore automatically needs a binNMU to get the newer one *and* lockstep upgrades are enforced by that. >From the Debian Policy "Declaring relationships between packages" > >"The Depends field should be used if the depended-on package is required for >the depending package to provide a significant amount of functionality." Yes. Not applicable here, xrdp does not need xorgxrdp to provide a significant part of use cases. xorgxrdp is a plugin that can be added to provide the third significant use case out of three, AIUI. bye, //mirabilos -- 15:41⎜ Somebody write a testsuite for helloworld :-)
Bug#1052230: marked as done ("Missing build-dependency on pkg-config")
Your message dated Wed, 20 Sep 2023 23:55:59 + with message-id and subject line Bug#1052230: fixed in ocamlnet 4.1.9-4 has caused the Debian Bug report #1052230, regarding "Missing build-dependency on pkg-config" 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.) -- 1052230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: caml-crush Version: 1.0.12-1.1 Severity: important Tags: ftbfs User: debian-ocaml-ma...@lists.debian.org Usertags: ocaml-4.14.1-transition Dear Maintainer, Your package FTBFS with OCaml 4.14.1 with the following error: > [...] > collect2: error: ld returned 1 exit status > File "caml_startup", line 1: > Error: Error during linking (exit code 1) > make[3]: *** [Makefile:15: all] Error 2 > make[3]: Leaving directory > '/tmp/build/caml-crush-1.0.12/build-SERVER/src/pkcs11proxyd' > make[2]: *** [Makefile:18: server] Error 2 > make[2]: Leaving directory '/tmp/build/caml-crush-1.0.12/build-SERVER' > dh_auto_build: error: cd build-SERVER && make -j1 > CUSTOM_SONAME=libp11clienttcpssl.so returned exit code 2 > make[1]: *** [debian/rules:45: override_dh_auto_build-SERVER] Error 25 > make[1]: Leaving directory '/tmp/build/caml-crush-1.0.12' > make: *** [debian/rules:53: binary] Error 2 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit status > 2 Packages rebuilt with OCaml 4.14.1 are available at: http://ocaml.debian.net/transitions/ocaml-4.14.1/ Cheers, -- Stéphane -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-4-amd64 (SMP w/8 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 --- Source: ocamlnet Source-Version: 4.1.9-4 Done: Stéphane Glondu We believe that the bug you reported is fixed in the latest version of ocamlnet, 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 1052...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated ocamlnet 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, 20 Sep 2023 10:40:13 +0200 Source: ocamlnet Architecture: source Version: 4.1.9-4 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Closes: 1052230 Changes: ocamlnet (4.1.9-4) unstable; urgency=medium . * Add pkg-config to Build-Depends (Closes: #1052230) Checksums-Sha1: a95b9b5ef21eb723fea02623ea05cec3827e692d 2417 ocamlnet_4.1.9-4.dsc d4e99531b47161f5a80145c391d45acf5d9f338e 16568 ocamlnet_4.1.9-4.debian.tar.xz Checksums-Sha256: 1b45d0270afc31032dd8e9beb3005833b7e16701d479995fc985c6fadc561d6f 2417 ocamlnet_4.1.9-4.dsc 9e9c77be50933a6725a707e387294dbf1bf380429c949180ab2f232c637268a9 16568 ocamlnet_4.1.9-4.debian.tar.xz Files: a41068d18630315b57c335be290138ea 2417 ocaml optional ocamlnet_4.1.9-4.dsc c652601aa428e4270f735449f027e1d3 16568 ocaml optional ocamlnet_4.1.9-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmULgNESHGdsb25kdUBk ZWJpYW4ub3JnAAoJECG47vGxiTCBrWEH/isE4hsjMrGB+bYqxSFroOqOogASYp2l rQVHPN7r2u5Nb6QU7mIRKOYe/r0Qhxwd+7yLhfSYyf394PDof4cLEIeVDk1floeg 9oL2u2k5Xi101iTUEWSGFzWQYIqstx867HP+gPP2Z6ZlGtkVeyVxYnjBEArrpImE LjigK8QS6K2aYDEiht5EL7HS5J3B4ZGOzIr6DsTDqHH78uW2kjOIY61bE7D7fZeM 36cmWrZEVMOysSEHUFmfDVZuPAa9RUgttxjmAMZG68GLnX9IM2o7K+GiedStpnwx ImuLow7AtcsAi+SYatKY+F/dhPXJmmTmo6yoOYJCOeVznqrMhmf6Mds= =17MZ -END PGP SIGNATURE End Message ---
Bug#1051374: breaks existing setups using /etc/default/mini-httpd
Hi, Quoting Alexandru Mihail (2023-09-21 01:31:23) > Hello again,> okay, I'll wait. Thank you for your quick reply! > Thank you for the wait ! > I've committed the necessary systemd service fix into a new mini-httpd > release (1.30-5). Currently waiting for sponsored upload from my mentor. if you want a sponsor, I can also upload it for you. Thanks! cheers, josch signature.asc Description: signature
Bug#1052197: xrdp: after bullseye-security upgrade, empty turquoise screen after logging in
I have just rebuilt and uploaded xorgxrdp 0.2.12-1+deb11u1 to bullseye- security. That should resolve the problem at hand. However I recommend to keep this bug report open and try to address the dependency problem between xrdp and xorgxrdp. If you claim that without a rebuild of xorgxrdp a new upstream version of xrdp would be broken, then this is a strong indication that xorgxrdp should be more than a recommendation in Debian terms: From the Debian Policy "Declaring relationships between packages" "The Depends field should be used if the depended-on package is required for the depending package to provide a significant amount of functionality." If xrdp only works with a specific version of xorgxrdp then this is true in my opinion and the recommendation should be changed to a Depends. We had a similar issue with librhino-java and shrinksafe in the recent past. librhino-java had to declare a versioned Breaks on shrinksafe and shrinksafe had to add a versioned (Build-)Depends on rhino/librhino-java. In my opinion we have the exact same situation here. In any case I leave that to the maintainers of xrdp/xorgxrdp to resolve. Regards, Markus signature.asc Description: This is a digitally signed message part
Processed: Bug#1052230 marked as pending in ocamlnet
Processing control commands: > tag -1 pending Bug #1052230 [src:ocamlnet] "Missing build-dependency on pkg-config" Added tag(s) pending. -- 1052230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052230: marked as pending in ocamlnet
Control: tag -1 pending Hello, Bug #1052230 in ocamlnet 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/ocaml-team/ocamlnet/-/commit/f08228a817e530a7497cbb3f4fe684141a4b2e66 Add pkg-config to Build-Depends (Closes: #1052230) (this message was generated automatically) -- Greetings https://bugs.debian.org/1052230
Bug#1051374: breaks existing setups using /etc/default/mini-httpd
Hello again,> okay, I'll wait. Thank you for your quick reply! Thank you for the wait ! I've committed the necessary systemd service fix into a new mini-httpd release (1.30-5). Currently waiting for sponsored upload from my mentor. Have a great one, Alexandru signature.asc Description: This is a digitally signed message part
Bug#1042415: marked as done (ruby-aws-partitions: Package missing partitions.json)
Your message dated Wed, 20 Sep 2023 22:47:00 + with message-id and subject line Bug#1042415: fixed in ruby-aws-partitions 1.653.0-2 has caused the Debian Bug report #1042415, regarding ruby-aws-partitions: Package missing partitions.json 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.) -- 1042415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby-aws-partitions Version: 1.653.0-1 Severity: grave Tags: patch Justification: renders package unusable X-Debbugs-Cc: ssg...@debian.org In version 1.653.0-1, /usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/partitions.json is not present. It is there in version 1.354.0-2 in bullseye. Without that file, any actual use of this gem fails: $ irb irb(main):001:0> require 'aws-partitions' => true irb(main):002:1* Aws::Partitions.each do |partition| irb(main):003:1* puts partition.name irb(main):004:0> end /usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:225:in `read': No such file or directory @ rb_sysopen - /usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/partitions.json (Errno::ENOENT) from /usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:225:in `defaults' from /usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:214:in `default_partition_list' from /usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:137:in `each' from (irb):2:in `' from /usr/lib/ruby/gems/3.1.0/gems/irb-1.4.1/exe/irb:11:in `' from /usr/bin/irb:25:in `load' from /usr/bin/irb:25:in `' Patch to fix is attached -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.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 ruby-aws-partitions depends on: ii ruby 1:3.1 ruby-aws-partitions recommends no packages. ruby-aws-partitions suggests no packages. -- no debconf information diff -Nru ruby-aws-partitions-1.653.0/debian/changelog ruby-aws-partitions-1.653.0/debian/changelog --- ruby-aws-partitions-1.653.0/debian/changelog2022-10-30 08:49:35.0 -0500 +++ ruby-aws-partitions-1.653.0/debian/changelog2023-07-27 17:39:10.0 -0500 @@ -1,3 +1,11 @@ +ruby-aws-partitions (1.653.0-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Change DH_RUBY_GEM_INSTALL_WHITELIST_APPEND to DH_RUBY_GEM_INSTALL_INCLUDE +in debian/rules to work with newer gem2deb + + -- Stephen Gelman Thu, 27 Jul 2023 17:39:10 -0500 + ruby-aws-partitions (1.653.0-1) unstable; urgency=medium * Team Upload diff -Nru ruby-aws-partitions-1.653.0/debian/rules ruby-aws-partitions-1.653.0/debian/rules --- ruby-aws-partitions-1.653.0/debian/rules2022-10-30 08:49:35.0 -0500 +++ ruby-aws-partitions-1.653.0/debian/rules2023-07-27 17:36:38.0 -0500 @@ -2,7 +2,7 @@ export GEM2DEB_TEST_RUNNER = --check-dependencies export DH_RUBY = --gem-install -export DH_RUBY_GEM_INSTALL_WHITELIST_APPEND := partitions.json +export DH_RUBY_GEM_INSTALL_INCLUDE := partitions.json %: dh $@ --buildsystem=ruby --with ruby --- End Message --- --- Begin Message --- Source: ruby-aws-partitions Source-Version: 1.653.0-2 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-aws-partitions, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-aws-partitions 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, 20 Sep 2023 22:59:25 +0200 Source: ruby-aws-partitions Architecture: source Version:
Bug#1037400: marked as done (spacefm: build-depends on transitional package libgdk-pixbuf2.0-dev)
Your message dated Wed, 20 Sep 2023 22:48:12 + with message-id and subject line Bug#1037400: fixed in spacefm 1.0.6-7 has caused the Debian Bug report #1037400, regarding spacefm: build-depends on transitional package libgdk-pixbuf2.0-dev 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.) -- 1037400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spacefm Version: 1.0.6-5 Severity: important Tags: trixie sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: split-gdk-pixbuf This package Build-Depends on libgdk-pixbuf2.0-dev. In Debian 11, libgdk-pixbuf2.0-dev was split into two packages: - libgdk-pixbuf-2.0-dev contains the supported gdk-pixbuf-2.0 library - libgdk-pixbuf-xlib-2.0-dev contains the deprecated, unmaintained Xlib integration layer, gdk-pixbuf-xlib-2.0 If this package only requires functionality from gdk-pixbuf-2.0.pc and , please update the build-dependency to libgdk-pixbuf-2.0-dev. If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and (unlikely), then you can also build-depend on libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove that requirement. libgdk-pixbuf-2.0-dev was present in both Debian 11 and Debian 12, so it is not necessary to have a "| libgdk-pixbuf2.0-dev" alternative dependency, even for packages that are expected to be backported. We should remove the libgdk-pixbuf2.0-dev transitional package during the Debian 13 'trixie' cycle, so this bug is likely to become RC later. Thanks, smcv --- End Message --- --- Begin Message --- Source: spacefm Source-Version: 1.0.6-7 Done: Mateusz Łukasik We believe that the bug you reported is fixed in the latest version of spacefm, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mateusz Łukasik (supplier of updated spacefm 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, 20 Sep 2023 21:00:18 +0200 Source: spacefm Architecture: source Version: 1.0.6-7 Distribution: unstable Urgency: medium Maintainer: Mateusz Łukasik Changed-By: Mateusz Łukasik Closes: 1037400 Changes: spacefm (1.0.6-7) unstable; urgency=medium . * Switch B-D to libgdk-pixbuf-2.0-dev. (Closes: #1037400) Checksums-Sha1: 5b83ce24e49790df204f99efd96ac2fb1e1e38c9 2013 spacefm_1.0.6-7.dsc 61a382b2333c365baa0389eeb56ac6da1244616f 17004 spacefm_1.0.6-7.debian.tar.xz 184b396ba57daac7b31779b9101b928b3b619a91 8109 spacefm_1.0.6-7_source.buildinfo Checksums-Sha256: 402de567221f741c889bea26f7d3181649f4ab18aa36c0e0d98ba3ed8577d404 2013 spacefm_1.0.6-7.dsc 5e21a8149556e98b599927aff472c4e4f9dde51bacd20086c18fae51f913953f 17004 spacefm_1.0.6-7.debian.tar.xz 7d87f5fcd04f2761deafa324def288e63ee9eb451cb0b58af23f2084f30ac2e0 8109 spacefm_1.0.6-7_source.buildinfo Files: 689158ae471c96ef12b307afbb8b999e 2013 utils optional spacefm_1.0.6-7.dsc 02b4a83e8cbd4d2ca26d62b9f8f8d000 17004 utils optional spacefm_1.0.6-7.debian.tar.xz b016b29561db2a0635bcf58d6c3305f2 8109 utils optional spacefm_1.0.6-7_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmULWFoQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFGZKDADds81JJxpYo7QcROSxxIdkoGXT/laPhcHa OjuAkMqX7zkJi7S0kHgUGkX2tgtyipWLbtOVoTRF9iNcHe/o2IakpyASfBsZOvjy T5moPAFAiLaLhIFuxIxWlU0lQ43eXL8Ma5dgbq+QfLvemHZVV8LHNCPhXJsNp6cg fH04TQ4txrZxBHv0K4HenoISBF5eHYoDqfBm8AzMbRVUiuFiGeMcrYdgrFRKpdl9 blk1ixhw6dZMRJlYCsa0sga/BCBI0n/6GY4Te5eBqdXTDag+Pe9ucYvidACsiPng Lr4LBHOmofMtqhGXR0UTUh4e5STeCbrg2AbIt+iXNPnF0QiM8xoLuMo+wcU2RedH 0DuSxuJBegHtfJi/jTwcxWmG55FWSAvIY4pIGujG3kU9NVUg1xwukirMfgevzTC2 gUHia1I3lf8r8FL8x+xtVW4Dh0J4/6a8gBWD9SQhzDOAsLrR0NPwpWVm9hJMAgom X+b9OUy6+koSGRS64TaouwT4j/tqWQY= =oCeG -END PGP SIGNATURE End Message ---
Processed: Bug#1042415 marked as pending in ruby-aws-partitions
Processing control commands: > tag -1 pending Bug #1042415 [ruby-aws-partitions] ruby-aws-partitions: Package missing partitions.json Added tag(s) pending. -- 1042415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042415: marked as pending in ruby-aws-partitions
Control: tag -1 pending Hello, Bug #1042415 in ruby-aws-partitions 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/ruby-team/ruby-aws-partitions/-/commit/4d45cb8396995d45ddf7161152f546655e9b3f48 reinstall partitions.json (Closes: #1042415) (this message was generated automatically) -- Greetings https://bugs.debian.org/1042415
Bug#1052355: marked as done (libwebp-dev: missing dependency on libsharupyuv-dev)
Your message dated Wed, 20 Sep 2023 20:47:53 + with message-id and subject line Bug#1052355: fixed in libwebp 1.3.2-0.2 has caused the Debian Bug report #1052355, regarding libwebp-dev: missing dependency on libsharupyuv-dev 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.) -- 1052355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libwebp Version: 1.3.2-0.1 Severity: serious X-Debbugs-CC: by...@debian.org Affects: src:gnome-contacts libwebp.pc contains this line: Requires.private: library Therefore, libwebp-dev needs to depend on libsharpyuv-dev for packages that use pkgconfig to build correctly. See this build log for instance: https://buildd.debian.org/status/package.php?p=gnome-contacts Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: libwebp Source-Version: 1.3.2-0.2 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of libwebp, 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 1052...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated libwebp 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, 20 Sep 2023 15:59:13 -0400 Source: libwebp Architecture: source Version: 1.3.2-0.2 Distribution: unstable Urgency: medium Maintainer: Jeff Breidenbach Changed-By: Boyuan Yang Closes: 1052355 Changes: libwebp (1.3.2-0.2) unstable; urgency=medium . * Non-maintainer upload. * debian/control: Add missing dependency libwebp-dev => libsharpyuv-dev. (Closes: #1052355) Checksums-Sha1: 9e5e9fddb3eed5d4c3e0d23152808e8bc41711c4 2550 libwebp_1.3.2-0.2.dsc f941661a869df7347d7ca9208acb4e6d41f614de 4162949 libwebp_1.3.2.orig.tar.gz c821d11e05b95ccf95db8d6b1126447477e50436 833 libwebp_1.3.2.orig.tar.gz.asc e679dd68547323de7b505890128d1b1cf79da141 10792 libwebp_1.3.2-0.2.debian.tar.xz 0c227c17022c76870f45921b3b7fd0a5a29c0cda 13058 libwebp_1.3.2-0.2_amd64.buildinfo Checksums-Sha256: 97f5c908a21d7f79d9e551a7253363c48ef3a7e35a950a60d428d2e2dd2b 2550 libwebp_1.3.2-0.2.dsc 2a499607df669e40258e53d0ade8035ba4ec0175244869d1025d460562aa09b4 4162949 libwebp_1.3.2.orig.tar.gz db4d388e3a2464c85eb3f84b30272754335d471472f8b64bef4b2e37f77b207d 833 libwebp_1.3.2.orig.tar.gz.asc 570caf9159d9e26c3dd43130e4287ebb33064fe6267638b5c329d5e5b363c0ef 10792 libwebp_1.3.2-0.2.debian.tar.xz 1ad970de350e9d50c74e7ea1aa2601344225c8b32c563c842580c1d63951b0b0 13058 libwebp_1.3.2-0.2_amd64.buildinfo Files: 180816f599125b4666bdd8d5be976fe4 2550 libs optional libwebp_1.3.2-0.2.dsc 34869086761c0e2da6361035f7b64771 4162949 libs optional libwebp_1.3.2.orig.tar.gz b3ec2acaa185fda608c9b8dd3e780792 833 libs optional libwebp_1.3.2.orig.tar.gz.asc a6879a39a69aa5cdb7ef66ec8179b4ba 10792 libs optional libwebp_1.3.2-0.2.debian.tar.xz 06e971399cf5f979777ce1e87f433056 13058 libs optional libwebp_1.3.2-0.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmULT/IACgkQwpPntGGC Ws4rzQ/6A2e5GzF4jOf3S9J1aGuVCYpfaLjHNZG+P990okeQ0CS1up70f1ubJK1D ACSwqk9Z7hBMx3rB4loqwVlArdJIT2e3Nh8ufAZq4ZU36gz5tAyIWizQLdkhdq82 t003rJNVmnJ12KLQE4FU2g2uWUUWjgBs3BsU1sJ7Y1ZZ5NcP7XAa0qm0dJC/Tir2 ckzhxj5TSKbC/TN/G6K+/KnKs93/K8u1rzBDSwwY7ye9ehgob4e5vGL91TMr0ClF QmVzXRo/3+baAQEeGcAU+j+j1J92YNlvOK0QnulSN34Yb/gbmVwxGcTSzXUp3ZsN kzQzy6GA1ytlcoRaJ3gfBw6iUMK4piaKs2FQY48tXC+FK4SxVlTRRSC43FyCMWp4 VbrH/ORbmfd26LMytcRHjWsqiUA8IgXoZUVwGellzBnlAez67XFmMIOq5X/zS8Qc yZmMC1vljQYvkNQveJeY7wR2k2vRaEin4xwDAnBHpWHqAF5uXfYTa9DhzDQbVzPT IVShIl8Ir5lZN/47F4YSpMGvCoqAlK8xBDsnF4459Y+TV4r1ATBegL37y1sN+OTv b+C5y0DVN9PAHsLW5ndgl/AoLBx/SAtvJzG6S4ytVeyLG9hUTeHPLLdkq6g1mXSg qJ/dMgJsE2EeqGvu/6Qdv/i24NoYIPxylU2FtdTJktFPNIDbkjg= =+grI -END PGP SIGNATURE End Message ---
Processed: Re: libwebp-dev: missing dependency on libsharupyuv-dev
Processing commands for cont...@bugs.debian.org: > tags 1052355 ftbfs Bug #1052355 [src:libwebp] libwebp-dev: missing dependency on libsharupyuv-dev Added tag(s) ftbfs. > End of message, stopping processing here. Please contact me if you need assistance. -- 1052355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052355: libwebp-dev: missing dependency on libsharupyuv-dev
Source: libwebp Version: 1.3.2-0.1 Severity: serious X-Debbugs-CC: by...@debian.org Affects: src:gnome-contacts libwebp.pc contains this line: Requires.private: library Therefore, libwebp-dev needs to depend on libsharpyuv-dev for packages that use pkgconfig to build correctly. See this build log for instance: https://buildd.debian.org/status/package.php?p=gnome-contacts Thank you, Jeremy Bícha
Bug#1050375: marked as done (libpgtcl not installed in default Tcl search path.)
Your message dated Wed, 20 Sep 2023 19:42:19 + with message-id and subject line Bug#1050375: fixed in pgtcl 1:3.0.0-2 has caused the Debian Bug report #1050375, regarding libpgtcl not installed in default Tcl search path. 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.) -- 1050375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pfm Version: 2.0.8-3 Severity: grave pfm doesn't do anything useful here, it just produces a message popup saying Connection to database foo has failed: invalid command name "pg_connect" I guess Tcl/Tk has changed since this package was last updated 10 years ago. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de:en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pfm depends on: ii itcl3 3.4.4-2 ii libpgtcl 1:3.0.0-1 ii postgresql-client 15+253.pgdg+1 ii postgresql-client-10 [postgresql- 10.23-2.pgdg+1 client] ii postgresql-client-11 [postgresql- 11.21-1.pgdg+1 client] ii postgresql-client-12 [postgresql- 12.16-1.pgdg+1 client] ii postgresql-client-13 [postgresql- 13.12-1.pgdg+1 client] ii postgresql-client-14 [postgresql- 14.9-1.pgdg+1 client] ii postgresql-client-15 [postgresql- 15.4-1.pgdg+1 client] ii postgresql-client-16 [postgresql- 16~beta2-2.pgdg+~20230807.1056.ge8386b2 client] ii postgresql-client-17 [postgresql- 17~~devel-1.pgdg+~20230820.0934.g1951d21 client] ii postgresql-client-8.2 [postgresql 8.2.23-11.pgdg+1 -client] ii postgresql-client-8.4 [postgresql 8.4.22-9.pgdg+1 -client] ii postgresql-client-9.3 [postgresql 9.3.25-9.pgdg+1 -client] ii postgresql-client-9.4 [postgresql 9.4.26-8.pgdg+1 -client] ii postgresql-client-9.5 [postgresql 9.5.25-6.pgdg+1 -client] ii postgresql-client-9.6 [postgresql 9.6.24-5.pgdg+1 -client] ii sensible-utils 0.0.20 ii tcl8.6.13 ii tk 8.6.13 pfm recommends no packages. Versions of packages pfm suggests: ii postgresql 15+253.pgdg+1 -- no debconf information Christoph --- End Message --- --- Begin Message --- Source: pgtcl Source-Version: 1:3.0.0-2 Done: Mark Hindley We believe that the bug you reported is fixed in the latest version of pgtcl, 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 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Hindley (supplier of updated pgtcl 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: Wed, 20 Sep 2023 19:35:45 +0100 Source: pgtcl Architecture: source Version: 1:3.0.0-2 Distribution: unstable Urgency: medium Maintainer: Mark Hindley Changed-By: Mark Hindley Closes: 1050375 Changes: pgtcl (1:3.0.0-2) unstable; urgency=medium . * libpgtcl: install modules in default Tcl auto_path (Closes: #1050375). * d/control: bump Standards Version (no changes). Checksums-Sha1: 3c606ecca8818861024f7c2613780ae53c2b39df 1799 pgtcl_3.0.0-2.dsc 39a1a0c5648fd6af11cec54957fc540be89e1013 4064 pgtcl_3.0.0-2.debian.tar.xz d23430938ca01785a8484b5c5439b026bb3bde2c 7473 pgtcl_3.0.0-2_amd64.buildinfo Checksums-Sha256: 31c64044613f60f80c5c4263e869c70c577c2a118736c38a0deb2fe41c63a516 1799 pgtcl_3.0.0-2.dsc 3b7ae2f39b9824d9e225cbe06c766b07ddd894ca657a2dd2f091a4a418f4b1cf 4064 pgtcl_3.0.0-2.debian.tar.xz c50994ee09bd19c8c4c146cc515df42c302ab1cc5aa2f5702ad74603eca86685 7473 pgtcl_3.0.0-2_amd64.buildinfo Files: 183732ff88044afaf570cb724f936098 1799 libs optional pgtcl_3.0.0-2.dsc 6c8cb78c530ac48de35905c0453154bd 4064 libs optional
Processed: src:ispell-czech: fails to migrate to testing for too long: uploader built arch:all
Processing control commands: > close -1 20040229-7 Bug #1052354 [src:ispell-czech] src:ispell-czech: fails to migrate to testing for too long: uploader built arch:all Marked as fixed in versions ispell-czech/20040229-7. Bug #1052354 [src:ispell-czech] src:ispell-czech: fails to migrate to testing for too long: uploader built arch:all Marked Bug as done -- 1052354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052354: src:ispell-czech: fails to migrate to testing for too long: uploader built arch:all
Source: ispell-czech Version: 20040229-5.3 Severity: serious Control: close -1 20040229-7 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:ispell-czech has been trying to migrate for 31 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=ispell-czech OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: more found
Processing commands for cont...@bugs.debian.org: > # somehow the bts is confused, let's add the current versions in testing > found 1031414 pocl/4.0-2 Bug #1031414 [src:pocl,src:libgpuarray] libgpuarray: i386 test fail with new pocl Marked as found in versions pocl/4.0-2. > # and the affected version in unstable > found 1031414 libgpuarray/0.7.6-14 Bug #1031414 [src:pocl,src:libgpuarray] libgpuarray: i386 test fail with new pocl Marked as found in versions libgpuarray/0.7.6-14. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1050375
Processing commands for cont...@bugs.debian.org: > affects 1050375 pfm Bug #1050375 [libpgtcl] libpgtcl not installed in default Tcl search path. Added indication that 1050375 affects pfm > thanks Stopping processing here. Please contact me if you need assistance. -- 1050375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052353: src:rust-i18n-embed-impl: fails to migrate to testing for too long: unsatisfied depends
Source: rust-i18n-embed-impl Version: 0.8.0-1 Severity: serious Control: close -1 0.8.0-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:rust-i18n-embed-impl has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable can't be installed. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=rust-i18n-embed-impl OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:rust-i18n-embed-impl: fails to migrate to testing for too long: unsatisfied depends
Processing control commands: > close -1 0.8.0-2 Bug #1052353 [src:rust-i18n-embed-impl] src:rust-i18n-embed-impl: fails to migrate to testing for too long: unsatisfied depends Marked as fixed in versions rust-i18n-embed-impl/0.8.0-2. Bug #1052353 [src:rust-i18n-embed-impl] src:rust-i18n-embed-impl: fails to migrate to testing for too long: unsatisfied depends Marked Bug as done -- 1052353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:mold: fails to migrate to testing for too long: FTBFS on mips64el
Processing control commands: > close -1 2.1.0+dfsg-1 Bug #1052352 [src:mold] src:mold: fails to migrate to testing for too long: FTBFS on mips64el Marked as fixed in versions mold/2.1.0+dfsg-1. Bug #1052352 [src:mold] src:mold: fails to migrate to testing for too long: FTBFS on mips64el Marked Bug as done -- 1052352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052352: src:mold: fails to migrate to testing for too long: FTBFS on mips64el
Source: mold Version: 1.11.0+dfsg-1 Severity: serious Control: close -1 2.1.0+dfsg-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:mold has been trying to migrate for 32 days [2]. Hence, I am filing this bug. The version in unstable failed to build on mips64el. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=mold OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1051066: marked as done (netatalk: 9 outstanding CVEs in Bullseye with available patches)
Your message dated Wed, 20 Sep 2023 18:49:02 + with message-id <8Tu6YOJ_SAX8T-m1LvpYfO2dl-rNra37O_u3YthO7DjBjoO7R51qZFbHhG01L2DajUqRP-o_DL7CORxl5HI53z1fRNz-CZIsWvwGILrpcRM=@mindani.net> and subject line Resolved with bullseye-security release has caused the Debian Bug report #1051066, regarding netatalk: 9 outstanding CVEs in Bullseye with available patches 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.) -- 1051066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: netatalk Version: 3.1.12~ds-8 Severity: critical Tags: patch security Justification: root security hole X-Debbugs-Cc: pkg-netatalk-de...@alioth-lists.debian.net, Debian Security Team Nine CVE security advisories were addressed in netatalk upstream releases between 3.1.13 and 3.1.15. The full list is below: CVE-2022-45188 CVE-2022-43634 CVE-2022-23125 CVE-2022-23124 CVE-2022-23123 CVE-2022-23122 CVE-2022-23121 CVE-2022-0194 CVE-2021-31439 Current status of patching these vulnerabilities: - netatalk oldoldstable has already been patched by the Security Team. - netatalk unstable has already been patched by the maintainer team. - The netatalk package was excluded from stable, no action required. - What remains is to patch oldstable, hence this ticket. A debpatch has been attached to the related Release bug ticket, where approval to proceed with an oldstable release has been requested. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049325 -- System Information: Debian Release: 11.7 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-11-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages netatalk depends on: ii init-system-helpers 1.60 ii libacl1 2.2.53-10 ii libavahi-client3 0.8-5+deb11u2 ii libavahi-common3 0.8-5+deb11u2 ii libc62.31-13+deb11u6 ii libcrack22.9.6-3.4 ii libcrypt11:4.4.18-4 ii libdb5.3 5.3.28+dfsg1-0.8 ii libdbus-glib-1-2 0.110-6 ii libevent-2.1-7 2.1.12-stable-1 ii libgcrypt20 1.8.7-6 ii libglib2.0-0 2.66.8-1 ii libgssapi-krb5-2 1.18.3-6+deb11u3 ii libkrb5-31.18.3-6+deb11u3 ii libldap-2.4-22.4.57+dfsg-3+deb11u1 ii libmariadb3 1:10.5.19-0+deb11u2 ii libpam-modules 1.4.0-9+deb11u1 ii libpam0g 1.4.0-9+deb11u1 ii libssl1.11.1.1n-0+deb11u4 ii libtalloc2 2.3.1-2+b1 ii libtdb1 1.4.3-1+b1 ii libtracker-sparql-2.0-0 2.3.6-2 ii libwrap0 7.6.q-31 ii lsb-base 11.1.0 ii netbase 6.3 ii perl 5.32.1-4+deb11u2 Versions of packages netatalk recommends: ii avahi-daemon 0.8-5+deb11u2 ii cracklib-runtime 2.9.6-3.4 ii dbus 1.12.24-0+deb11u1 ii lsof 4.93.2+dfsg-1.1 ii procps2:3.3.17-5 ii python3 3.9.2-3 ii python3-dbus 1.2.16-5 ii tracker 2.3.6-2 Versions of packages netatalk suggests: pn quota -- no debconf information --- End Message --- --- Begin Message --- The Debian Security Team pushed out this patchset to bullseye-security in: netatalk_3.1.12~ds-8+deb11u1--- End Message ---
Processed: src:canu: fails to migrate to testing for too long: unresolved RC issue
Processing control commands:
> close -1 2.2+dfsg-3
Bug #1052347 [src:canu] src:canu: fails to migrate to testing for too long:
unresolved RC issue
Marked as fixed in versions canu/2.2+dfsg-3.
Bug #1052347 [src:canu] src:canu: fails to migrate to testing for too long:
unresolved RC issue
Marked Bug as done
> block -1 by 1050388
Bug #1052347 {Done: Paul Gevers } [src:canu] src:canu: fails
to migrate to testing for too long: unresolved RC issue
1052347 was not blocked by any bugs.
1052347 was not blocking any bugs.
Added blocking bug(s) of 1052347: 1050388
--
1052347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1052347: src:canu: fails to migrate to testing for too long: unresolved RC issue
Source: canu Version: 2.0+dfsg-2 Severity: serious Control: close -1 2.2+dfsg-3 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1050388 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:canu has been trying to migrate for 33 days [2]. Hence, I am filing this bug. The version in unstable is affected by bug 1050388. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=canu OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:binutils-mipsen: fails to migrate to testing for too long: FTBFS
Processing control commands:
> close -1 10+c5
Bug #1052345 [src:binutils-mipsen] src:binutils-mipsen: fails to migrate to
testing for too long: FTBFS
The source 'binutils-mipsen' and version '10+c5' do not appear to match any
binary packages
Marked as fixed in versions binutils-mipsen/10+c5.
Bug #1052345 [src:binutils-mipsen] src:binutils-mipsen: fails to migrate to
testing for too long: FTBFS
Marked Bug as done
> block -1 by 1050431
Bug #1052345 {Done: Paul Gevers } [src:binutils-mipsen]
src:binutils-mipsen: fails to migrate to testing for too long: FTBFS
1052345 was not blocked by any bugs.
1052345 was not blocking any bugs.
Added blocking bug(s) of 1052345: 1050431
--
1052345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: src:patchelf: fails to migrate to testing for too long: FTBFS on mips64el
Processing control commands: > close -1 0.18.0-1 Bug #1052346 [src:patchelf] src:patchelf: fails to migrate to testing for too long: FTBFS on mips64el Marked as fixed in versions patchelf/0.18.0-1. Bug #1052346 [src:patchelf] src:patchelf: fails to migrate to testing for too long: FTBFS on mips64el Marked Bug as done -- 1052346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052345: src:binutils-mipsen: fails to migrate to testing for too long: FTBFS
Source: binutils-mipsen Version: 10+c4 Severity: serious Control: close -1 10+c5 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1050431 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:binutils-mipsen has been trying to migrate for 36 days [2]. Hence, I am filing this bug. As already reported in bug 1050431, the version in unstable failed to build from source. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=binutils-mipsen OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1052346: src:patchelf: fails to migrate to testing for too long: FTBFS on mips64el
Source: patchelf Version: 0.14.3-1 Severity: serious Control: close -1 0.18.0-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:patchelf has been trying to migrate for 33 days [2]. Hence, I am filing this bug. The version in unstable failed to build on mips64el. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=patchelf OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:cross-toolchain-base-mipsen: fails to migrate to testing for too long: FTBFS
Processing control commands: > close -1 26 Bug #1052344 [src:cross-toolchain-base-mipsen] src:cross-toolchain-base-mipsen: fails to migrate to testing for too long: FTBFS The source 'cross-toolchain-base-mipsen' and version '26' do not appear to match any binary packages Marked as fixed in versions cross-toolchain-base-mipsen/26. Bug #1052344 [src:cross-toolchain-base-mipsen] src:cross-toolchain-base-mipsen: fails to migrate to testing for too long: FTBFS Marked Bug as done -- 1052344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052344: src:cross-toolchain-base-mipsen: fails to migrate to testing for too long: FTBFS
Source: cross-toolchain-base-mipsen Version: 24 Severity: serious Control: close -1 26 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:cross-toolchain-base-mipsen has been trying to migrate for 36 days [2]. Hence, I am filing this bug. The version in unstable failed to build from source. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=cross-toolchain-base-mipsen OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: Re: src:python-django-pgschemas: fails to migrate to testing for too long: uploader built arch:all
Processing control commands:
> retitle -1 python-django-pgschemas fails to build from source
Bug #1052343 {Done: Paul Gevers }
[src:python-django-pgschemas] src:python-django-pgschemas: fails to migrate to
testing for too long: uploader built arch:all
Changed Bug title to 'python-django-pgschemas fails to build from source' from
'src:python-django-pgschemas: fails to migrate to testing for too long:
uploader built arch:all'.
--
1052343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1052343: src:python-django-pgschemas: fails to migrate to testing for too long: uploader built arch:all
Control: retitle -1 python-django-pgschemas fails to build from source Hi, Sorry, this report was partially non-sense. On Wed, 20 Sep 2023 20:17:09 +0200 Paul Gevers wrote: Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. No, the reason it doesn't migrate is that it didn't build yet. However, I have the suspicion that it might have been caught in the tzdata weirdness, so I requested a giveback just now. Let's see if that builds, otherwise, please look into it. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:python-django-pgschemas: fails to migrate to testing for too long: uploader built arch:all
Processing control commands: > close -1 0.15.0-1 Bug #1052343 [src:python-django-pgschemas] src:python-django-pgschemas: fails to migrate to testing for too long: uploader built arch:all The source 'python-django-pgschemas' and version '0.15.0-1' do not appear to match any binary packages Marked as fixed in versions python-django-pgschemas/0.15.0-1. Bug #1052343 [src:python-django-pgschemas] src:python-django-pgschemas: fails to migrate to testing for too long: uploader built arch:all Marked Bug as done -- 1052343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052343: src:python-django-pgschemas: fails to migrate to testing for too long: uploader built arch:all
Source: python-django-pgschemas Version: 0.14-1 Severity: serious Control: close -1 0.15.0-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:python-django-pgschemas has been trying to migrate for 38 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=python-django-pgschemas OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1052331: marked as done (libcrypt-openssl-pkcs12-perl: Testsuite failures due to higher openssl version.)
Your message dated Wed, 20 Sep 2023 18:04:38 + with message-id and subject line Bug#1052331: fixed in libcrypt-openssl-pkcs12-perl 1.9-3 has caused the Debian Bug report #1052331, regarding libcrypt-openssl-pkcs12-perl: Testsuite failures due to higher openssl 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.) -- 1052331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcrypt-openssl-pkcs12-perl Version: 1.9-2 severity: serious I reported FTBFS against openssl 3.0 in #1006386 and now it kind of falls apart again. The check in patch is | $major eq "3.1" and $minor <= 2) or ($major eq "3.0" and $minor <= 10) and I have now 3.1.3 in experimental and 3.0.11 in unstable leading to ci failures and FTBFS for libcrypt-openssl-pkcs12-perl itself. Could we please extend the version check to all major 3.0 and 3.1 versions? It looks unlikely that the password thingy will be changed within 3.0/3.1 series based on the linked bug report. And maybe even add 3.2 because from what I see in the current alpha version is, that it is ABI compatible with the current 3.0/3.1 releases. But then maybe limit the test to less than 3.0 series of openssl and enable it again once it is known that it works again. Whatever feels like less work ;) Sebastian --- End Message --- --- Begin Message --- Source: libcrypt-openssl-pkcs12-perl Source-Version: 1.9-3 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libcrypt-openssl-pkcs12-perl, 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 1052...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libcrypt-openssl-pkcs12-perl 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, 20 Sep 2023 19:43:10 +0200 Source: libcrypt-openssl-pkcs12-perl Architecture: source Version: 1.9-3 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 1052331 Changes: libcrypt-openssl-pkcs12-perl (1.9-3) unstable; urgency=medium . * Team upload. * Update openssl3.patch to skip pkcs12 password test on all OpenSSL 3.x versions. Thanks to Sebastian Andrzej Siewior for the bug report. (Closes: #1052331) Checksums-Sha1: bdef059ef5e3bd2c99f18331f73e8bfde484b36e 2710 libcrypt-openssl-pkcs12-perl_1.9-3.dsc f3fe927f51a5b5cb1f48353e17110f0599597c05 7124 libcrypt-openssl-pkcs12-perl_1.9-3.debian.tar.xz Checksums-Sha256: aa37965dfe7a60f0976d50a585ace68b6be928f6e494d2cbf08c91d38610ffb4 2710 libcrypt-openssl-pkcs12-perl_1.9-3.dsc a048399d2d9eb885c7a1e7c40d202306d41282f460ac5e74c5044fb0685301e1 7124 libcrypt-openssl-pkcs12-perl_1.9-3.debian.tar.xz Files: 7cf4179e6ceadbae390fa2336644a451 2710 perl optional libcrypt-openssl-pkcs12-perl_1.9-3.dsc 7ab75f87d77a6af244b7da5b99853869 7124 perl optional libcrypt-openssl-pkcs12-perl_1.9-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmULL8VfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZqnw//Z051ErEEDMVZSO8WfA4MHLLO6fcboaWBFDxZIAzOGI0hMYJ9dt7dAJiM 5pTv3SRP00u4uWE2VMXMjiJ0CeOtV6B1fv33A/YZorfu/RfVwRVMyZfEG5evGOWp nirE5AwnwncyVZUqbvwRQQrEm4iNXQULliigKkSBLDQHyoJZMocm47ddtiqbKiyj SQziyNNEcGOdbNOo8Juw7I5zm/QhCoGOCofsVhnAiZi6+De7bMVyGq98ulHGh7bT 5/XPjLmYW623Ms6MevlwT2+YEr1+abOn+pL1ATM0E/PXZe9ab2ZiTpPdwF2Go3vm VJjzy82mCt0YbPnSdjdLy6t6rxMNDh4R1Iq2BZt2KUI7ryCrQjHOi3cdMEuJmzpa PwVLEXibL8DqRAb9Ni/2LTiKFZgWY9VdCihPukjtVk+fNBIR8ZBmQSzMnbqYEU9m uDOgY6iuElvCVP+j6uY+QYz4ARnpq4UX47n0Lx6DqU9yk33GHT2NnWCPEXTkwp1G r1NC/SXZBwiuaCThLqr/A7hUy3o406ceR3C0cO8CmkwFP1qUL4UJqgnCpE11x7Pq eyx+/ARqcNZ59mpJyRTYrtWs4qskPYC5yj3q16+kLfSFmn34z1Kb1d6Eqz54QF8O IIx/iCLcsRgqg1xlQMRvkCbw9qzKwLhHsrW/GrC2Je1gPMTRGvo= =u9ts -END PGP SIGNATURE End Message ---
Processed: Re: Bug#1050375: Invalid command name "pg_connect"
Processing control commands: > reassign -1 libpgtcl Bug #1050375 [pfm] Invalid command name "pg_connect" Bug reassigned from package 'pfm' to 'libpgtcl'. No longer marked as found in versions pfm/2.0.8-3. Ignoring request to alter fixed versions of bug #1050375 to the same values previously set > retitle -1 libpgtcl not installed in default Tcl search path. Bug #1050375 [libpgtcl] Invalid command name "pg_connect" Changed Bug title to 'libpgtcl not installed in default Tcl search path.' from 'Invalid command name "pg_connect"'. -- 1050375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050375: Invalid command name "pg_connect"
Control: reassign -1 libpgtcl Control: retitle -1 libpgtcl not installed in default Tcl search path. On Wed, Aug 23, 2023 at 08:09:48PM +0200, Christoph Berg wrote: > Package: pfm > Version: 2.0.8-3 > Severity: grave > > pfm doesn't do anything useful here, it just produces a message popup > saying > > Connection to database foo has failed: > > invalid command name "pg_connect" Thanks. I believe this needs fixing in libpgtcl. Reassigning. Mark
Processed: Re: Bug#1052197: xrdp: after bullseye-security upgrade, empty turquoise screen after logging in
Processing commands for cont...@bugs.debian.org: > tags 1052197 + patch Bug #1052197 [xrdp] xrdp: after bullseye-security upgrade, empty turquoise screen after logging in Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1052197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:gcc-arm-none-eabi: fails to migrate to testing for too long: makes reverse dependencies non-installable
Processing control commands:
> close -1 15:12.3.rel1-1
Bug #1052340 [src:gcc-arm-none-eabi] src:gcc-arm-none-eabi: fails to migrate to
testing for too long: makes reverse dependencies non-installable
Marked as fixed in versions gcc-arm-none-eabi/15:12.3.rel1-1.
Bug #1052340 [src:gcc-arm-none-eabi] src:gcc-arm-none-eabi: fails to migrate to
testing for too long: makes reverse dependencies non-installable
Marked Bug as done
> block -1 by 1050327
Bug #1052340 {Done: Paul Gevers } [src:gcc-arm-none-eabi]
src:gcc-arm-none-eabi: fails to migrate to testing for too long: makes reverse
dependencies non-installable
1052340 was not blocked by any bugs.
1052340 was not blocking any bugs.
Added blocking bug(s) of 1052340: 1050327
--
1052340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1052340: src:gcc-arm-none-eabi: fails to migrate to testing for too long: makes reverse dependencies non-installable
Source: gcc-arm-none-eabi Version: 15:12.2.rel1-1 Severity: serious Control: close -1 15:12.3.rel1-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1050327 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:gcc-arm-none-eabi has been trying to migrate for 40 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=gcc-arm-none-eabi OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1052197: xrdp: after bullseye-security upgrade, empty turquoise screen after logging in
tags 1052197 + patch thanks On Wed, 20 Sep 2023, Thorsten Glaser wrote: >I’ll try binNMU’ing (locally) xorgxrdp, and if that doesn’t help, OK, that helped! It went fast. Installing the binNMU’d package xorgxrdp_0.2.12-1+b0.1_amd64.deb (and killing all /usr/lib/xorg/Xorg processes spawned from xrdp, visible by using :10 and higher as DISPLAY numbers) fixed this. So please ask someone (SRM, I believe) to schedule binNMUs of xorgxrdp for all oldstable architectures in oldstable. Thanks! bye, //mirabilos -- [16:04:33] bkix: "veni vidi violini" [16:04:45] bkix: "ich kam, sah und vergeigte"...
Bug#1052339: src:intel-graphics-compiler: fails to migrate to testing for too long: makes reverse dependencies uninstallable
Source: intel-graphics-compiler Version: 1.0.12504.6-1 Severity: serious Control: close -1 1.0.15136.1-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1051189 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:intel-graphics-compiler has been trying to migrate for 40 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=intel-graphics-compiler OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1025011: marked as done (Keep out of bookworm unless actively maintained)
Your message dated Wed, 20 Sep 2023 19:51:59 +0200 with message-id and subject line Re: Keep out of bookworm unless actively maintained has caused the Debian Bug report #1025011, regarding Keep out of bookworm unless actively maintained 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.) -- 1025011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netatalk Version: 3.1.13~ds-2 Severity: serious netatalk should not enter bookworm unless it gets adopted and actively maintained. Cheers, Moritz --- End Message --- --- Begin Message --- Am Mon, Nov 28, 2022 at 08:39:34PM +0100 schrieb Moritz Muehlenhoff: > Source: netatalk > Version: 3.1.13~ds-2 > Severity: serious > > netatalk should not enter bookworm unless it gets adopted and > actively maintained. With the recent bullseye prepared by Daniel Markstedt (thanks!), this can be closed for good and netatalk can re-enter testing. Cheers, Moritz--- End Message ---
Processed: src:intel-graphics-compiler: fails to migrate to testing for too long: makes reverse dependencies uninstallable
Processing control commands:
> close -1 1.0.15136.1-1
Bug #1052339 [src:intel-graphics-compiler] src:intel-graphics-compiler: fails
to migrate to testing for too long: makes reverse dependencies uninstallable
Marked as fixed in versions intel-graphics-compiler/1.0.15136.1-1.
Bug #1052339 [src:intel-graphics-compiler] src:intel-graphics-compiler: fails
to migrate to testing for too long: makes reverse dependencies uninstallable
Marked Bug as done
> block -1 by 1051189
Bug #1052339 {Done: Paul Gevers }
[src:intel-graphics-compiler] src:intel-graphics-compiler: fails to migrate to
testing for too long: makes reverse dependencies uninstallable
1052339 was not blocked by any bugs.
1052339 was not blocking any bugs.
Added blocking bug(s) of 1052339: 1051189
--
1052339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1051953: marked as done (cups: CVE-2023-32360)
Your message dated Wed, 20 Sep 2023 17:49:17 + with message-id and subject line Bug#1051953: fixed in cups 2.4.2-6 has caused the Debian Bug report #1051953, regarding cups: CVE-2023-32360 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.) -- 1051953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cups Version: 2.4.2-5 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for cups. CVE-2023-32360[0]: | An authentication issue was addressed with improved state | management. This issue is fixed in macOS Big Sur 11.7.7, macOS | Monterey 12.6.6, macOS Ventura 13.4. An unauthenticated user may be | able to access recently printed documents. Severity choosen on RC level, due to an unautnethicated user beeing able to access recently printed documents. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-32360 https://www.cve.org/CVERecord?id=CVE-2023-32360 [1] https://github.com/OpenPrinting/cups/commit/a0c8b9c9556882f00c68b9727a95a1b6d1452913 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: cups Source-Version: 2.4.2-6 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of cups, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated cups package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Sep 2023 21:20:27 +0200 Source: cups Architecture: source Version: 2.4.2-6 Distribution: unstable Urgency: medium Maintainer: Debian Printing Team Changed-By: Thorsten Alteholz Closes: 1051953 Changes: cups (2.4.2-6) unstable; urgency=medium . * CVE-2023-4504 Postscript parsing heap-based buffer overflow * CVE-2023-32360 (Closes: #1051953) authentication issue Checksums-Sha1: d86d47400714b839b865a69f662c89eff3eb3e31 3122 cups_2.4.2-6.dsc 2d8131ab57130d160e08879f11de07a012dc51e3 383340 cups_2.4.2-6.debian.tar.xz 6046b841b9492ccaef0b6b3c1c3bffab85ffa996 13522 cups_2.4.2-6_amd64.buildinfo Checksums-Sha256: b96962376db22504617caf1dbd62d5b91eaa0775ec222380366f134dc495db6a 3122 cups_2.4.2-6.dsc 34437967aa116c4cf525c8f76f82bb9ddd04fff064245cd6a7fc3190ec6221be 383340 cups_2.4.2-6.debian.tar.xz 83cc1e229b53790ac920b3104bdf8b79f6f3d41a9073c2ec96238f4c536915a3 13522 cups_2.4.2-6_amd64.buildinfo Files: 073a8106cca47c6091074c9c284d38df 3122 net optional cups_2.4.2-6.dsc f39ed57d70d2b76ff12375081b9b405e 383340 net optional cups_2.4.2-6.debian.tar.xz f56929c831caad6c6313738cc6b4818c 13522 net optional cups_2.4.2-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmUKXTFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYRxMaD/97eb9aNKRY9/3AX/vAji44XTNW270F PHkUuzNEbnu79Z1nW2Ij1vGhVnYuEkB3Rfh9x3S1LbQ2u7q5zS9WK8oNKdxE50GX oSCAIhrPltmKs5YFx9eR6yRUFwhw9w3EUfpDo2kK2vFvF3+RsNhgQ/352j62/6hg vxcozIXueQFBLRXp3ORS0oxBOgu6UbQ6DDJUTSYQU6kJ/I3qvziYVU6VaJye8e/7 hRKPss4eozRyUCIwitDbkiqXqzSMha6AS3S7E0bNRxO0mUhwGzOHHF3uTgD6XHOD Rgy73vht3sErJufrXosA9ukHqAZrVGJhK7IztUUw1v2jvrnLE6Ca/aPCQyhw8Z7E QpkBtl+t8TbnM8QY0aIw8zBYC69TrPjkqDPRpMiFiSrx0B2aCKhpO5K/odNW6RSI rI/7LwRkPM5ebUvWd0K8CzPsonTFaA5w07U7A6icRLuOB4/rt64jNHAXGR4nrSpb IX/Ng01jBCkdjdP/iXXuiFsQgjSrahuccOr64T8wC4qn0DzZjA560xp73RWcoLBq WL7CDiIUpjDCNqtvcgZbNy2M+y7bTiAw6pNlY0RG/T51Sj5lzbvY4SD5+Ya+4kW2 zgghISuWvNxzs2OqZBJvpDiROwx96o7l5Pb0MnZ5LPkWx8U3xup3UKC0tvT9ThZx 2Lq3CLGKZoN1xg== =mHD/ -END PGP SIGNATURE End Message ---
Processed: src:pycryptodome: fails to migrate to testing for too long: FTBFS nearly everywhere
Processing control commands: > close -1 3.18.0+dfsg1-1 Bug #1052336 [src:pycryptodome] src:pycryptodome: fails to migrate to testing for too long: FTBFS nearly everywhere Marked as fixed in versions pycryptodome/3.18.0+dfsg1-1. Bug #1052336 [src:pycryptodome] src:pycryptodome: fails to migrate to testing for too long: FTBFS nearly everywhere Marked Bug as done -- 1052336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052197: xrdp: after bullseye-security upgrade, empty turquoise screen after logging in
On Wed, 20 Sep 2023, Thorsten Glaser wrote: >Attached … and now with. //mirabilos -- 15:41⎜ Somebody write a testsuite for helloworld :-) buglogs.tgz Description: application/gtar-compressed
Bug#1052331: marked as pending in libcrypt-openssl-pkcs12-perl
Control: tag -1 pending Hello, Bug #1052331 in libcrypt-openssl-pkcs12-perl 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/perl-team/modules/packages/libcrypt-openssl-pkcs12-perl/-/commit/6b12b90d49e451ddb7041ba54cffe4928a6535ad Update openssl3.patch to skip pkcs12 password test on all OpenSSL 3.x versions. Thanks: Sebastian Andrzej Siewior for the bug report. Closes: #1052331 (this message was generated automatically) -- Greetings https://bugs.debian.org/1052331
Processed: Bug#1052331 marked as pending in libcrypt-openssl-pkcs12-perl
Processing control commands: > tag -1 pending Bug #1052331 [libcrypt-openssl-pkcs12-perl] libcrypt-openssl-pkcs12-perl: Testsuite failures due to higher openssl version. Added tag(s) pending. -- 1052331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:flake8-quotes: fails to migrate to testing for too long: uploader built binaries
Processing control commands: > close -1 3.3.2-1 Bug #1052337 [src:flake8-quotes] src:flake8-quotes: fails to migrate to testing for too long: uploader built binaries Marked as fixed in versions flake8-quotes/3.3.2-1. Bug #1052337 [src:flake8-quotes] src:flake8-quotes: fails to migrate to testing for too long: uploader built binaries Marked Bug as done -- 1052337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052337: src:flake8-quotes: fails to migrate to testing for too long: uploader built binaries
Source: flake8-quotes Version: 3.3.1-3 Severity: serious Control: close -1 3.3.2-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:flake8-quotes has been trying to migrate for 41 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=flake8-quotes OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1052336: src:pycryptodome: fails to migrate to testing for too long: FTBFS nearly everywhere
Source: pycryptodome Version: 3.11.0+dfsg1-4 Severity: serious Control: close -1 3.18.0+dfsg1-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:pycryptodome has been trying to migrate for 42 days [2]. Hence, I am filing this bug. The version in unstable failed to build on most architectures. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=pycryptodome OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1052197: xrdp: after bullseye-security upgrade, empty turquoise screen after logging in
Hallo Markus, >the new Bullseye version of xrdp is identical to the version in Bookworm. Thus >the underlying problem is probably more complex and I don't suspect that >something is wrong with xrdp itself but more likely with a configuration option >or related software packages which do something different than in Bookworm. either that, or xorgxrdp must also be updated, or at least rebuilt against the newer xrdp? Maybe? >I definitely need more information about your setup or xrdp in general to debug I’ve now purged and reinstalled xrdp and xorgxrdp on the machine with… less “interesting” history, but the effect is still present. Selecting previously unselected package xrdp. (Reading database ... 210637 files and directories currently installed.) Preparing to unpack .../xrdp_0.9.21.1-1~deb11u1_amd64.deb ... Unpacking xrdp (0.9.21.1-1~deb11u1) ... Selecting previously unselected package xorgxrdp. Preparing to unpack .../xorgxrdp_1%3a0.2.12-1_amd64.deb ... Unpacking xorgxrdp (1:0.2.12-1) ... Setting up xrdp (0.9.21.1-1~deb11u1) ... Generating 2048 bit rsa key... ssl_gen_key_xrdp1 ok saving to /etc/xrdp/rsakeys.ini Starting Remote Desktop Protocol server: xrdp-sesman xrdp. Setting up xorgxrdp (1:0.2.12-1) ... >this issue. Possible reasons for the behavior may be: > >1. TLS / connection problem ? Did you do "adduser xrdp ssl-cert" ? Maybe a new >TLS configuration option in 0.9.21.1? The xrdp user is not in ssl-cert, but I never used those either. >2. graphic drivers ? I read that hardware accelerated drivers may cause such What graphic drivers? xrdp+xorgxrdp runs headlessly. >/var/log/xrdp-sesman.log >/var/log/xrdp.log >~/.xsession-errors Attached, and I’ll also add /.xorgxrdp.10.log ☻ >journalctl -S -2m That won’t do much other than say command not found ;-) I don’t know that thing but I assume you’ll want to see whether there’s anything relevant in syslog. Starting at package installation, there is: Sep 20 19:32:45 tglase-edge groupadd[16356]: group added to /etc/group: name=xrdp, GID=119 Sep 20 19:32:45 tglase-edge groupadd[16356]: group added to /etc/gshadow: name=xrdp Sep 20 19:32:45 tglase-edge groupadd[16356]: new group: name=xrdp, GID=119 Sep 20 19:32:45 tglase-edge useradd[16364]: new user: name=xrdp, UID=110, GID=119, home=/run/xrdp, shell=/usr/sbin/nologin, from=/dev/pts/2 Sep 20 19:32:45 tglase-edge chage[16375]: changed password expiry for xrdp Sep 20 19:32:46 tglase-edge xrdp-sesman[16502]: [INFO ] starting xrdp-sesman with pid 16502 Sep 20 19:32:46 tglase-edge xrdp[16504]: [INFO ] address [0.0.0.0] port [3389] mode 1 Sep 20 19:32:46 tglase-edge xrdp[16504]: [INFO ] listening to port 3389 on 0.0.0.0 Sep 20 19:32:46 tglase-edge xrdp[16504]: [INFO ] xrdp_listen_pp done Sep 20 19:32:48 tglase-edge xrdp[16506]: [INFO ] starting xrdp with pid 16506 Sep 20 19:32:49 tglase-edge xrdp[16506]: [INFO ] address [0.0.0.0] port [3389] mode 1 Sep 20 19:32:49 tglase-edge xrdp[16506]: [INFO ] listening to port 3389 on 0.0.0.0 Sep 20 19:32:49 tglase-edge xrdp[16506]: [INFO ] xrdp_listen_pp done Sep 20 19:32:54 tglase-edge xrdp-sesman[16502]: [INFO ] receiving SIGHUP Sep 20 19:32:54 tglase-edge xrdp-sesman[16502]: [INFO ] configuration reloaded, log subsystem restarted Sep 20 19:32:54 tglase-edge sudo: pam_unix(sudo:session): session closed for user root Sep 20 19:33:07 tglase-edge xrdp[16506]: [INFO ] Socket 12: AF_INET6 connection received from :::172.34.0.14 port 51122 Sep 20 19:33:07 tglase-edge xrdp[17463]: [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem Sep 20 19:33:08 tglase-edge xrdp[17463]: [INFO ] Using default X.509 key file: /etc/xrdp/key.pem Sep 20 19:33:08 tglase-edge xrdp[17463]: [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied Sep 20 19:33:08 tglase-edge xrdp[17463]: [WARN ] Cannot accept TLS connections because certificate or private key file is not readable. certificate file: [/etc/xrdp/cert.pem], private key file: [/etc/xrdp/key.pem] Sep 20 19:33:08 tglase-edge xrdp[17463]: [INFO ] Security protocol: configured [RDP], requested [SSL|HYBRID|RDP], selected [RDP] Sep 20 19:33:08 tglase-edge xrdp[17463]: [INFO ] Connected client computer name: x61w Sep 20 19:33:08 tglase-edge xrdp[17463]: [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x04], keyboard_subtype:[0x00], keylayout:[0x0409] Sep 20 19:33:08 tglase-edge xrdp[17463]: [INFO ] xrdp_load_keyboard_layout: model [] variant [] layout [us] options [] Sep 20 19:33:08 tglase-edge xrdp[17463]: [INFO ] Non-TLS connection established from :::172.34.0.14 port 51122: with security level : high Sep 20 19:33:08 tglase-edge xrdp[17463]: [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor Sep 20 19:33:08 tglase-edge xrdp[17463]: [WARN ] Received [MS-RDPBCGR] TS_CONFIRM_ACTIVE_PDU - TS_CAPS_SET capabilitySetType = 27 is unknown - Ignored Sep 20 19:33:08 tglase-edge xrdp[17463]: [INFO ] Loading keymap file
Bug#1051563: Backporting mutt patches to Debian Buster
On Wed, Sep 20, 2023 at 02:35:30PM -0300, Santiago Ruano Rincón wrote: > I kept the original From, tagged the Origin as backport, and kept your > name as Author. > Hope that makes sense for you. > > Thanks a lot for your work! I saw it percolate through the updates today. Thanks very much! - Chris
Bug#1052335: src:haskell-haskell-gi-base: fails to migrate to testing for too long: blocked by other packages
Source: haskell-haskell-gi-base Version: 0.26.2-1 Severity: serious Control: close -1 0.26.4-3 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:haskell-haskell-gi-base has been trying to migrate for 49 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. 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. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=haskell-haskell-gi-base OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:haskell-haskell-gi-base: fails to migrate to testing for too long: blocked by other packages
Processing control commands: > close -1 0.26.4-3 Bug #1052335 [src:haskell-haskell-gi-base] src:haskell-haskell-gi-base: fails to migrate to testing for too long: blocked by other packages Marked as fixed in versions haskell-haskell-gi-base/0.26.4-3. Bug #1052335 [src:haskell-haskell-gi-base] src:haskell-haskell-gi-base: fails to migrate to testing for too long: blocked by other packages Marked Bug as done -- 1052335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051563: Backporting mutt patches to Debian Buster
Hi Chris, El 17/09/23 a las 21:56, Chris Frey escribió: > On Sun, Sep 17, 2023 at 08:34:57PM +0300, Santiago Ruano Rincón wrote: > > Chris, thanks for preparing the patches. Much appreciated. I have a > > question though: Why are you placing those two patches in > > debian-specific, and not in upstream/? They come from the upstream repo. > > I only put them there because I had to modify them for a clean patch. I consider placing them in debian-specific is a little counter-intuitive. However, buster already contained a debian/patches/security, and I have placed there. > I changed the headers to make it clear that I edited them, but kept > the original wording as well. That is not how I interpret DEP-3. I restored the headers structure and uploaded the package. Will send the DLA soon! > > I didn't think it was right to modify the patch contents without > changing the name of who did it. I kept the original From, tagged the Origin as backport, and kept your name as Author. Hope that makes sense for you. Thanks a lot for your work! -- Santiago signature.asc Description: PGP signature
Bug#1052334: rust-leptonica-sys - Debian and Cargo dependencies inconsistent.
Package: rust-leptonica-sys Version: 0.4.6-3 Severity: serious The Debian dependencies for rust-leptonica-sys allow versions of rust-bindgen from 0.60.x to 0.66.x, however the Cargo dependencies only allow versions from 0.64.x to 0.66.x. This is causing autopkgtest failures and blocking rust-leptonica-sys and hence rust-bindgen from migrating to testing. Please make the dependencies consistent, either by changing the Debian depndencies to match the Cargo ones or by changing the Cargo dependency to match the Debian ones.
Processed: Re: Bug#1052331: Acknowledgement (libcrypt-openssl-pkcs12-perl)
Processing commands for cont...@bugs.debian.org: > retitle 1052331 libcrypt-openssl-pkcs12-perl: Testsuite failures due to > higher openssl version. Bug #1052331 [libcrypt-openssl-pkcs12-perl] libcrypt-openssl-pkcs12-perl Changed Bug title to 'libcrypt-openssl-pkcs12-perl: Testsuite failures due to higher openssl version.' from 'libcrypt-openssl-pkcs12-perl'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1052331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052331: libcrypt-openssl-pkcs12-perl
Package: libcrypt-openssl-pkcs12-perl Version: 1.9-2 severity: serious I reported FTBFS against openssl 3.0 in #1006386 and now it kind of falls apart again. The check in patch is | $major eq "3.1" and $minor <= 2) or ($major eq "3.0" and $minor <= 10) and I have now 3.1.3 in experimental and 3.0.11 in unstable leading to ci failures and FTBFS for libcrypt-openssl-pkcs12-perl itself. Could we please extend the version check to all major 3.0 and 3.1 versions? It looks unlikely that the password thingy will be changed within 3.0/3.1 series based on the linked bug report. And maybe even add 3.2 because from what I see in the current alpha version is, that it is ABI compatible with the current 3.0/3.1 releases. But then maybe limit the test to less than 3.0 series of openssl and enable it again once it is known that it works again. Whatever feels like less work ;) Sebastian
Bug#999962: RFS to solve bug#999962 (silversearcher-ag: depends on obsolete pcre3 library)
I've moved this discussion from debian-emacsen to the relevant bug. Please remove debian-emacsen from CC and add me to CC for all follow-ups. Manphiz writes: > Manphiz writes: > >> >> Thanks Nicholas! I used licensecheck and checked manually and updated >> d/copyright accordingly in my merge request[1]. PTAL, thanks! >> >> [1] https://salsa.debian.org/debian/silversearcher-ag/-/merge_requests/1 > > Friendly ping. haha @enable_pcre2_support.patch:L478 Thanks for adding some copyright info; this will cover a "patches applied" view, but doesn't cover the "patches unapplied" source package (orig.tar, debian.tar, dsc). If you manually evaluate the rules in d/copyright you'll see that this patch becomes misattributed to the debian/* holder, which gets even more confusing since you set yourself as the patch author ;) Yes, I understand you synthesised commits, and I'm fine with that, but please finish fixing up d/copyright. changelog: Please enclose "Closes: #62" in parentheses in order to follow the style that is already in use by this package's maintainer; it's technically still Majime Mizuno's package, after all. Then finalise the changelog and build the package. Finally, learn about what an "nmudiff" is, and file one at the relevant bug. Thanks, Nicholas signature.asc Description: PGP signature
Bug#1052327: libdbd-odbc-perl: Test failure in t/rt_57957.t
Source: libdbd-odbc-perl Version: 1.61-2 Severity: serious Tags: ftbfs trixie sid Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As noticed by ci.debian.org, t/rt_57957.t started to fail at some point between 2023-09-02 and 2023-09-18. This test now also fails during build, making the package FTBFS. # Some of these tests may fail for your driver - please let me know if they do along with the strings SQLite/sqlite3odbc.so t/rt_57957.t . 1..8 ok 1 - use ODBCTEST; ok 2 - Prepare with trailing comment and named placeholder ok 3 - Prepare with leading comment and named placeholder Failed 5/8 subtests Test Summary Report - --- t/rt_57957.t (Wstat: 139 (Signal: SEGV, dumped core) Tests: 3 Failed: 0) Non-zero wait status: 139 Parse errors: Bad plan. You planned 8 tests but ran 3. Files=42, Tests=1081, 7 wallclock secs ( 0.36 usr 0.07 sys + 3.36 cusr 0.69 csys = 4.48 CPU) Result: FAIL Notable differences in the environment between the test runs on ci.debian.net: - -libsqlite3-0 3.42.0-1 - -libsqliteodbc 0.9998-3+b1 +libsqlite3-0 3.43.1-1 +libsqliteodbc 0.-1 Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmULCSJfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgadyA//dsyksGfcQ2+WchuPlsC76GAz0NANPUdnFuMNKStMq38VIJmc7ocExBr/ rv7iVEATKJxWf2gWx/wGu0TyCOiFBUFsKtvOyw2OUIzklgj6kLrkyGH6ZwtSetkI bqJiuZZMOm7dBEicAi+anKFAJZvkLJNZ/ZjHjOFxYYVEmjgiC1MiHCGDXhCgIWIe SFgbOUEdrCi29L+Iba4sURSIaOC3qMb+ljB9BmiOuhvEXdOOKqlw/kXSnvK8wruy Rwscyij5pWgEKe4v8r547EPL5Qt7TSdrQAZnxdJ9ObPmCNtTem8iQEBbXexDHdDf 9ImaORPkLQT3Gxwjs4SDuXDlt/9wghcgireVYsgXQfgVxvfoYXs4Zwy68fyvmtRa 2DXf7BBqugq2uLazPdVlQpQQ4GIJVbKmSog8BkU0E6il9bxq+8MEiAbVf0sYFjtM R4DrLEWtd1kfqoY07PGUXzVnUXwalD9CrtG6MDO6MYZTzYVHcQ8YvZSwKyjQ0SI7 //rd+M3DixkBNoS7YGTbujBtyCVBaLoHZ8GSBSi6pqzhXaPFHPMX0M5dWBs8WXZP kCMbYa/9WhtXzYMAEjHmHK8zXhR+OYtJdCbYJzA2zL0TgyEmGkMwUzmGcyr4oMNu aBEqR4OtgsWPtz4qx4h7fnCSDCuIUrGX6UwqaXnrg2jgFpFsMLc= =mgQ8 -END PGP SIGNATURE-
Processed: blocks for view3dscene
Processing commands for cont...@bugs.debian.org: > package view3dscene Limiting to bugs with field 'package' containing at least one of 'view3dscene' Limit currently set to 'package':'view3dscene' > block 1051598 by 1052321 Bug #1051598 [view3dscene] view3dscene: Hardcodes dependency on removed transitional packages 1051598 was not blocked by any bugs. 1051598 was not blocking any bugs. Added blocking bug(s) of 1051598: 1052321 > End of message, stopping processing here. Please contact me if you need assistance. -- 1051598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037602: ceph: ftbfs with GCC-13
On Tue, Sep 19, 2023 at 11:24 PM Thomas Goirand wrote: > > On 9/19/23 17:02, Bo YU wrote: > > hmm, I try the patch again, but it seems it works on amd64. > > `apt source ceph` to get ceph_16.2.11+ds-2 and debdiff-apply the patch. > > > > I guess maybe you apply the patch on salsa repo. > > Yes, I did. > > >> Also, you might have missed that I prepared the next version in the > >> debian/experimental branch. The debian/unstable only has the merge of > >> upstream tarball, nothing more, so don't use that one. It builds a lot > >> more stuff, but then it also FTBFS. Note that the upstream package > >> prepared for Ubuntu also FTBFS. > > yes, I notice it. I am trying to `git clone` the ceph source code from salsa > > in order to rebase the patch on your commit as you mention. > > But I am stuck in how to get rid of upstream tarball(18.1.2) on > > debian/unstable > > and apply my patch. Or could you tell me what your context hot to apply > > my patch and I can reproduct the FTBFS on my local machines？ > > I've "git push origin debian/unstable -f" to get a working branch. > Please clone again from scratch (I know, it's a huge repo... :/). Okay, I cloned the repo again and it seems short of one argument in d/rules to fix the changing meaning issue. Nothing else need to do on your top commit: commit 48dc08622e70877aba2095b497aece099a16cc2f (origin/debian/unstable, origin/HEAD) Author: Thomas Goirand Date: Mon Sep 18 17:49:49 2023 +0200 * Fix gcc-13 FTBFS. (Closes: #1037602): Could you try the patch again? In fact you did it/change before.:) BR, Bo > > >> I really would love to receive help here, packaging version 18, because > >> even reading the failing cmake logs is hard for me... > > > > Thanks for your hard work here. I am not sure I can help here, but i > > will do my best if possbile. > > Let's first get 16.2.11 fixed in unstable, then maybe your patch can > apply on top of 18.2.x too... > > Thanks for your help, > Cheers, > > Thomas Goirand (zigo) > 0001-add-fpermissiveto-fix-change-meaning-issue.patch Description: Binary data
Processed: tag
Processing commands for cont...@bugs.debian.org: > tags 1037404 patch pending Bug #1037404 [src:transgui] transgui: build-depends on transitional package libgdk-pixbuf2.0-dev Added tag(s) pending and patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 1037404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037404: transgui: build-depends on transitional package libgdk-pixbuf2.0-dev
I am uploading a NMU to DELAYED/10 in order fix this. The debdiff is attached.diff -Nru transgui-5.18.0+dfsg/debian/changelog transgui-5.18.0+dfsg/debian/changelog --- transgui-5.18.0+dfsg/debian/changelog 2022-05-08 22:41:20.0 +0200 +++ transgui-5.18.0+dfsg/debian/changelog 2023-09-20 12:07:04.0 +0200 @@ -1,3 +1,11 @@ +transgui (5.18.0+dfsg-3.1) unstable; urgency=medium + + * Non-maintainer upload + * Build with widgetset qt5 (Closes: #967782) + * Drop Build-Depends: libgdk-pixbuf2.0-dev (Closes: #1037404) + + -- Bastian Germann Wed, 20 Sep 2023 12:07:04 +0200 + transgui (5.18.0+dfsg-3) unstable; urgency=medium * Re-add libssl-dev dependency (LP: #1971896) diff -Nru transgui-5.18.0+dfsg/debian/control transgui-5.18.0+dfsg/debian/control --- transgui-5.18.0+dfsg/debian/control 2022-05-08 22:41:20.0 +0200 +++ transgui-5.18.0+dfsg/debian/control 2023-09-20 12:07:04.0 +0200 @@ -7,14 +7,10 @@ fp-utils, fpc, imagemagick, - lcl-gtk2, + lcl-qt5, lcl-units, lcl-utils, - libatk1.0-dev, libcairo2-dev, - libgdk-pixbuf2.0-dev, - libgtk2.0-dev, - libpango1.0-dev, libssl-dev, libx11-dev Standards-Version: 4.6.0 diff -Nru transgui-5.18.0+dfsg/debian/patches/build-with-qt5-widgetset.patch transgui-5.18.0+dfsg/debian/patches/build-with-qt5-widgetset.patch --- transgui-5.18.0+dfsg/debian/patches/build-with-qt5-widgetset.patch 1970-01-01 01:00:00.0 +0100 +++ transgui-5.18.0+dfsg/debian/patches/build-with-qt5-widgetset.patch 2023-09-20 12:07:04.0 +0200 @@ -0,0 +1,21 @@ +From: Bastian Germann +Date: Wed, 20 Sep 2023 12:44:29 +0200 +Subject: Build with qt5 widgetset + +--- + Makefile.fpc | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/Makefile.fpc b/Makefile.fpc +index 4622c4d..6ff3e1e 100644 +--- a/Makefile.fpc b/Makefile.fpc +@@ -32,7 +32,7 @@ $(info Using Lazarus dir: $(LAZARUS_DIR)) + LAZRES=$(LAZARUS_DIR)/tools/lazres$(SRCEXEEXT) + + # Widgetset +-LCL_WIDGETSET=gtk2 ++LCL_WIDGETSET=qt5 + ifneq ($(findstring $(OS_TARGET),win32,win64),) + LCL_WIDGETSET=win32 + endif diff -Nru transgui-5.18.0+dfsg/debian/patches/series transgui-5.18.0+dfsg/debian/patches/series --- transgui-5.18.0+dfsg/debian/patches/series 2022-05-08 22:41:20.0 +0200 +++ transgui-5.18.0+dfsg/debian/patches/series 2023-09-20 12:07:04.0 +0200 @@ -2,3 +2,4 @@ #fix.open.patch #force_ssl1.0.2.patch patch_connect_transmission_3.0 +build-with-qt5-widgetset.patch
Bug#1052316: udev postinst uses update-rc.d -f remove which breaks /etc.init.d/udev transition and non-systemd boot
Package: udev Version: 254.3-1 Severity: serious Justification: Breaks unrelated software, causes boot failure on some systems Dear systemd Maintainers, As reported in the follow-up to #1052116[1], udev's postinst uses update-rc.d's -f option which breaks the transition of /etc/init.d/udev to bin:initscripts and causes non-systemd systems to fail to boot. Michael, as discussed yesterday on #debian-systemd, I am very grateful for your quick commit of a fix[2]. This bug is to prevent unintended migration of the broken udev to trixie. With thanks and best wishes Mark [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052116#17 [2] https://salsa.debian.org/systemd-team/systemd/-/commit/12e2c67612f958148f0a4ca165cfb9ca1ed9d3c3 -- System Information: Debian Release: 12.0 merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#1042034: marked as done (nwchem: FTBFS: ld: cannot find -ldangchang: No such file or directory)
Your message dated Wed, 20 Sep 2023 09:52:14 + with message-id and subject line Bug#1042034: fixed in nwchem 7.0.2-5 has caused the Debian Bug report #1042034, regarding nwchem: FTBFS: ld: cannot find -ldangchang: No such file or directory 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.) -- 1042034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nwchem Version: 7.0.2-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230724 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/build-mpich/src' > /bin/sh: 1: [: Illegal number: . > /bin/sh: 1: [: Illegal number: . > make nwchem.o stubs.o > /bin/sh: 1: [: Illegal number: . > /bin/sh: 1: [: Illegal number: . > gfortran -g -O2 -ffast-math -fno-aggressive-loop-optimizations > -fno-tree-dominator-opts -std=legacy -ffast-math -Warray-bounds -std=legacy > -fdefault-integer-8 -fno-tree-dominator-opts -finline-functions -O2 -g > -fno-aggressive-loop-optimizations -fno-tree-dominator-opts -g -O -I. > -I/<>/build-mpich/src/include -I/usr/include > -I/usr/include/x86_64-linux-gnu/mpich -I/usr/include/x86_64-linux-gnu/mpich > -DLINUX -DGFORTRAN -DGFORTRAN -DCHKUNDFLW -DGCC4 -DGCC46 -DEXT_INT -DLINUX > -DLINUX64 -DSCALAPACK -DPARALLEL_DIAG -DCOMPILATION_DATE="'`date > +%a_%b_%d_%H:%M:%S_%Y`'" -DCOMPILATION_DIR="'/<>/build-mpich'" > -DNWCHEM_BRANCH="'7.0.2'" -c -o nwchem.o nwchem.F > gfortran -g -O2 -ffast-math -fno-aggressive-loop-optimizations > -fno-tree-dominator-opts -std=legacy -ffast-math -Warray-bounds -std=legacy > -fdefault-integer-8 -fno-tree-dominator-opts -finline-functions -O2 -g > -fno-aggressive-loop-optimizations -fno-tree-dominator-opts -g -O -I. > -I/<>/build-mpich/src/include -I/usr/include > -I/usr/include/x86_64-linux-gnu/mpich -I/usr/include/x86_64-linux-gnu/mpich > -DLINUX -DGFORTRAN -DGFORTRAN -DCHKUNDFLW -DGCC4 -DGCC46 -DEXT_INT -DLINUX > -DLINUX64 -DSCALAPACK -DPARALLEL_DIAG -DCOMPILATION_DATE="'`date > +%a_%b_%d_%H:%M:%S_%Y`'" -DCOMPILATION_DIR="'/<>/build-mpich'" > -DNWCHEM_BRANCH="'7.0.2'" -c -o stubs.o stubs.F > gfortran -L/<>/build-mpich/lib/LINUX64 > -L/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu -o > /<>/build-mpich/bin/LINUX64/nwchem nwchem.o stubs.o -lnwctask > -lccsd -lmcscf -lselci -lmp2 -lmoints -lstepper -ldriver -loptim -lnwdft > -lgradients -lcphf -lesp -lddscf -ldangchang -lguess -lhessian -lvib > -lnwcutil -lrimp2 -lproperty -lsolvation -lnwints -lprepar -lnwmd -lnwpw > -lofpw -lpaw -lpspw -lband -lnwpwlib -lcafe -lspace -lanalyze -lqhop -lpfft > -ldplot -lnwpython -ldrdy -lvscf -lqmmm -lqmd -letrans -lpspw -ltce -lbq -lmm > -lcons -lperfm -ldntmc -lccca -ldimqm -lnwcutil -lga-mpich -lscalapack-mpich > -llapack -lblas -larmci-mpich -larmci-mpich -lpeigs -lperfm -lcons -lbq > -lnwcutil -lscalapack-mpich -l64to32 -lblas -llapack "-llapack" "-lblas" > -L/usr/lib -L/usr/lib/x86_64-linux-gnu -lmpichfort -lmpich-larmci-mpich > -lpthread -lnwcutil -L/usr/lib/python3.11/config-3.11-x86_64-linux-gnu > -L/usr/lib/x86_64-linux-gnu -lpython3.11 -ldl -lm > /usr/bin/ld: cannot find -ldangchang: No such file or directory > /usr/bin/ld: cannot find -lnwmd: No such file or directory > /usr/bin/ld: cannot find -lcafe: No such file or directory > /usr/bin/ld: cannot find -lspace: No such file or directory > /usr/bin/ld: cannot find -lanalyze: No such file or directory > /usr/bin/ld: cannot find -lnwpython: No such file or directory > /usr/bin/ld: cannot find -ldrdy: No such file or directory > /usr/bin/ld: cannot find -lvscf: No such file or directory > /usr/bin/ld: cannot find -lqmmm: No such file or directory > /usr/bin/ld: cannot find -lqmd: No such file or directory > /usr/bin/ld: cannot find -letrans: No such file or directory > /usr/bin/ld: cannot find -ltce: No such file or directory > /usr/bin/ld: cannot find -lmm: No such file or directory > /usr/bin/ld: cannot find -ldntmc: No such file or directory > /usr/bin/ld: cannot find -lccca: No such file or directory > /usr/bin/ld: cannot find -ldimqm: No such file or directory > /usr/bin/ld: cannot find -l64to32: No such file or directory > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2023/07/24/nwchem_7.0.2-4_unstable.log All bugs filed during this archive rebuild are listed at:
Processed: Bug#1042034 marked as pending in nwchem
Processing control commands: > tag -1 pending Bug #1042034 [src:nwchem] nwchem: FTBFS: ld: cannot find -ldangchang: No such file or directory Added tag(s) pending. -- 1042034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042034: marked as pending in nwchem
Control: tag -1 pending Hello, Bug #1042034 in nwchem 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/debichem-team/nwchem/-/commit/2de418a62b358f2c1ec0db6307cc4c396f8b2fb0 add debian patch fix_py310_6384013.diff applies upstream commit 6384013 to build with python3.10 and higher. Build with set -e so as not to continue build if there are failures. The build problem was not -ldangchang as such, but attempting to link nwchem after compilation had already failed due to the changed python libraries (graminit.h) Closes: #1042034 (this message was generated automatically) -- Greetings https://bugs.debian.org/1042034
Processed: Bug#1042034 marked as pending in nwchem
Processing control commands: > tag -1 pending Bug #1042034 [src:nwchem] nwchem: FTBFS: ld: cannot find -ldangchang: No such file or directory Ignoring request to alter tags of bug #1042034 to the same tags previously set -- 1042034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042034: marked as pending in nwchem
Control: tag -1 pending Hello, Bug #1042034 in nwchem 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/debichem-team/nwchem/-/commit/2de418a62b358f2c1ec0db6307cc4c396f8b2fb0 add debian patch fix_py310_6384013.diff applies upstream commit 6384013 to build with python3.10 and higher. Build with set -e so as not to continue build if there are failures. The build problem was not -ldangchang as such, but attempting to link nwchem after compilation had already failed due to the changed python libraries (graminit.h) Closes: #1042034 (this message was generated automatically) -- Greetings https://bugs.debian.org/1042034
Bug#1052058: marked as done (apt: refuses to downgrade itself to a version that works on the system)
Your message dated Wed, 20 Sep 2023 09:03:58 + with message-id and subject line Bug#1052058: fixed in apt 2.7.6 has caused the Debian Bug report #1052058, regarding apt: refuses to downgrade itself to a version that works on the system 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.) -- 1052058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052058 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt Version: 2.7.5 Severity: important Once again we have a package that some people consider broken. That's natural, disagreements happen. That apt insists on a bad scheme not supported by dpkg has been said about elsewhere. Normally, that would be solvable by a simple downgrade. Except, in this case, apt refuses to do this: # apt install apt=2.7.3 apt-utils=2.7.3 Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: apt-doc The following packages will be DOWNGRADED: apt apt-utils 0 upgraded, 0 newly installed, 2 downgraded, 0 to remove and 2 not upgraded. E: /bin resolved to a different inode than /usr/bin E: Unmerged usr is no longer supported, install usrmerge to continue. N: See https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#a-merged-usr-is-now-required for more details. As you can see, the action I requested specifically solves the problem, yet apt considers it no good. Thus, I'd need to take steps that are not obvious to a regular user, and for this specific package risky to break the system if done wrong. Thus, apt should consider an operation that touches apt itself to be another exception for the usrmerge demand. Meow! -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "1"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$"; APT::VersionedKernelPackages ""; APT::VersionedKernelPackages:: "linux-.*"; APT::VersionedKernelPackages:: "kfreebsd-.*"; APT::VersionedKernelPackages:: "gnumach-.*"; APT::VersionedKernelPackages:: ".*-modules"; APT::VersionedKernelPackages:: ".*-kernel"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "tasks"; APT::Move-Autobit-Sections ""; APT::Move-Autobit-Sections:: "oldlibs"; APT::Architectures ""; APT::Architectures:: "amd64"; APT::Architectures:: "i386"; APT::Compressor ""; APT::Compressor::. ""; APT::Compressor::.::Name "."; APT::Compressor::.::Extension ""; APT::Compressor::.::Binary ""; APT::Compressor::.::Cost "0"; APT::Compressor::zstd ""; APT::Compressor::zstd::Name "zstd"; APT::Compressor::zstd::Extension ".zst"; APT::Compressor::zstd::Binary "zstd"; APT::Compressor::zstd::Cost "60"; APT::Compressor::zstd::CompressArg ""; APT::Compressor::zstd::CompressArg:: "-19"; APT::Compressor::zstd::UncompressArg ""; APT::Compressor::zstd::UncompressArg:: "-d"; APT::Compressor::lz4 ""; APT::Compressor::lz4::Name "lz4"; APT::Compressor::lz4::Extension ".lz4"; APT::Compressor::lz4::Binary "lz4"; APT::Compressor::lz4::Cost "50"; APT::Compressor::lz4::CompressArg ""; APT::Compressor::lz4::CompressArg:: "-1"; APT::Compressor::lz4::UncompressArg ""; APT::Compressor::lz4::UncompressArg:: "-d"; APT::Compressor::gzip ""; APT::Compressor::gzip::Name "gzip"; APT::Compressor::gzip::Extension ".gz"; APT::Compressor::gzip::Binary "gzip"; APT::Compressor::gzip::Cost "100"; APT::Compressor::gzip::CompressArg ""; APT::Compressor::gzip::CompressArg:: "-6n"; APT::Compressor::gzip::UncompressArg ""; APT::Compressor::gzip::UncompressArg:: "-d"; APT::Compressor::xz ""; APT::Compressor::xz::Name "xz"; APT::Compressor::xz::Extension ".xz"; APT::Compressor::xz::Binary "xz"; APT::Compressor::xz::Cost "200"; APT::Compressor::xz::CompressArg ""; APT::Compressor::xz::CompressArg:: "-6"; APT::Compressor::xz::UncompressArg ""; APT::Compressor::xz::UncompressArg:: "-d"; APT::Compressor::bzip2 ""; APT::Compressor::bzip2::Name "bzip2"; APT::Compressor::bzip2::Extension ".bz2"; APT::Compressor::bzip2::Binary "bzip2"; APT::Compressor::bzip2::Cost "300"; APT::Compressor::bzip2::CompressArg ""; APT::Compressor::bzip2::CompressArg:: "-6"; APT::Compressor::bzip2::UncompressArg "";
Bug#1052230: FTBFS with OCaml 4.14.1
Thanks Stephane, We are (over)due to update Caml-Crush to upstream some of the changes/patches that were made to keep it compatible with newer versions of Debian. Thanks for looking into it. Thomas On Wed, Sep 20, 2023 at 9:39 AM Stéphane Glondu wrote: > Control: reassign -1 src:ocamlnet > Control: retitle -1 "Missing build-dependency on pkg-config" > Control: affects -1 src:caml-crush > > Le 20/09/2023 à 10:19, Stéphane Glondu a écrit : > > The failure seems to be unrelated to OCaml 4.14.1, as the failure is > > reproducible in current unstable with OCaml 4.13.1... Hence, raising > > severity to serious. > > All this boils down to missing -lgnutls in nettls-gnutls, which seems to > be fixed by adding pkg-config to ocamlnet's Build-Depends. > > > Cheers, > > -- > Stéphane >
Processed: severity of 1052235 is serious, severity of 1052234 is serious
Processing commands for cont...@bugs.debian.org: > severity 1052235 serious Bug #1052235 [src:orpie] FTBFS with OCaml 4.14.1 Severity set to 'serious' from 'important' > severity 1052234 serious Bug #1052234 [src:ocaml-merlin] FTBFS with OCaml 4.14.1 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1052234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052234 1052235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052235 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037379: marked as done (gnome-nds-thumbnailer: build-depends on transitional package libgdk-pixbuf2.0-dev)
Your message dated Wed, 20 Sep 2023 08:49:17 + with message-id and subject line Bug#1037379: fixed in gnome-nds-thumbnailer 3.0.0-3 has caused the Debian Bug report #1037379, regarding gnome-nds-thumbnailer: build-depends on transitional package libgdk-pixbuf2.0-dev 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.) -- 1037379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-nds-thumbnailer Version: 3.0.0-2 Severity: important Tags: trixie sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: split-gdk-pixbuf This package Build-Depends on libgdk-pixbuf2.0-dev. In Debian 11, libgdk-pixbuf2.0-dev was split into two packages: - libgdk-pixbuf-2.0-dev contains the supported gdk-pixbuf-2.0 library - libgdk-pixbuf-xlib-2.0-dev contains the deprecated, unmaintained Xlib integration layer, gdk-pixbuf-xlib-2.0 If this package only requires functionality from gdk-pixbuf-2.0.pc and , please update the build-dependency to libgdk-pixbuf-2.0-dev. If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and (unlikely), then you can also build-depend on libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove that requirement. libgdk-pixbuf-2.0-dev was present in both Debian 11 and Debian 12, so it is not necessary to have a "| libgdk-pixbuf2.0-dev" alternative dependency, even for packages that are expected to be backported. We should remove the libgdk-pixbuf2.0-dev transitional package during the Debian 13 'trixie' cycle, so this bug is likely to become RC later. Thanks, smcv --- End Message --- --- Begin Message --- Source: gnome-nds-thumbnailer Source-Version: 3.0.0-3 Done: Laurent Bigonville We believe that the bug you reported is fixed in the latest version of gnome-nds-thumbnailer, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laurent Bigonville (supplier of updated gnome-nds-thumbnailer 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: Wed, 20 Sep 2023 09:52:30 +0200 Source: gnome-nds-thumbnailer Architecture: source Version: 3.0.0-3 Distribution: unstable Urgency: medium Maintainer: Laurent Bigonville Changed-By: Laurent Bigonville Closes: 1037379 Changes: gnome-nds-thumbnailer (3.0.0-3) unstable; urgency=medium . * debian/control: Switch BD from libgdk-pixbuf2.0-dev to libgdk-pixbuf-2.0-dev (Closes: #1037379) * debian/control: Bump Standards-Version to 4.6.2 (no further changes) * debian/watch: Bump version to 4, to please lintian Checksums-Sha1: 4b0b042240ee1132e03bbdbf6aaf2290c5b116f6 1674 gnome-nds-thumbnailer_3.0.0-3.dsc 0f35fcda4cc92ac7ff1f4371c45e067b66051a4a 2732 gnome-nds-thumbnailer_3.0.0-3.debian.tar.xz 22a49069f2be957889a6788d384059a1a67cd485 7351 gnome-nds-thumbnailer_3.0.0-3_source.buildinfo Checksums-Sha256: 67b47aa60d1dd37d2411ccfd98ff4c78cda6f13abdc0b8de24572fc17222e574 1674 gnome-nds-thumbnailer_3.0.0-3.dsc 7216c9c83ffe923bcb740d1a64713994a1304842bbe3897c307dbf4c879c1ace 2732 gnome-nds-thumbnailer_3.0.0-3.debian.tar.xz 74a15d76fb0e51a1874708f9849ba21675235988aa64b107fa1f27370c7c5118 7351 gnome-nds-thumbnailer_3.0.0-3_source.buildinfo Files: a27c7988beb69efbe095b3c38f8b7813 1674 gnome optional gnome-nds-thumbnailer_3.0.0-3.dsc aa1d335859d3a059c3362c6c87933e01 2732 gnome optional gnome-nds-thumbnailer_3.0.0-3.debian.tar.xz 86d3175e8fb72c3d4d330cef9f0f7503 7351 gnome optional gnome-nds-thumbnailer_3.0.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAmUKpTIRHGJpZ29uQGRl Ymlhbi5vcmcACgkQH8WJHrqwQ9UEOggAj5pglQMZMfYLLmZNHgVPKSxDNTUdIJOJ 6RZQdJrfy4X2dYYdFNMSr6gtKIr7oPLc2qXXqGC687NZQdP3PcZOLCU9oXlqpggm kiP6z3QF6u4VelpWaSFgjznX74viTK+guGdiyO98QnzK+oMBbvzSmMx+2HqefpAH Rs8ikcrLoqSeyQlgju80Kkp+fCucFQSYumrubjPrT8hC7AVHpFQWwLsKU6Ls97lV XC+WLzKgFQT5zf/cl1PsRbOLnLSjD0+AJwWRUMtgKp+r7baeeIjHlLFWRGEiYiKm q550ofezN4pds9ybCJOqL57JkKHGmMloVPi1P4nnGrETzHrt17L6wQ== =Di0x -END PGP SIGNATURE End Message ---
Processed: Re: FTBFS with OCaml 4.14.1
Processing control commands: > reassign -1 src:ocamlnet Bug #1052230 [src:caml-crush] FTBFS with OCaml 4.14.1 Bug reassigned from package 'src:caml-crush' to 'src:ocamlnet'. No longer marked as found in versions caml-crush/1.0.12-1.1. Ignoring request to alter fixed versions of bug #1052230 to the same values previously set > retitle -1 "Missing build-dependency on pkg-config" Bug #1052230 [src:ocamlnet] FTBFS with OCaml 4.14.1 Changed Bug title to '"Missing build-dependency on pkg-config"' from 'FTBFS with OCaml 4.14.1'. > affects -1 src:caml-crush Bug #1052230 [src:ocamlnet] "Missing build-dependency on pkg-config" Added indication that 1052230 affects src:caml-crush -- 1052230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052230: FTBFS with OCaml 4.14.1
Control: reassign -1 src:ocamlnet Control: retitle -1 "Missing build-dependency on pkg-config" Control: affects -1 src:caml-crush Le 20/09/2023 à 10:19, Stéphane Glondu a écrit : The failure seems to be unrelated to OCaml 4.14.1, as the failure is reproducible in current unstable with OCaml 4.13.1... Hence, raising severity to serious. All this boils down to missing -lgnutls in nettls-gnutls, which seems to be fixed by adding pkg-config to ocamlnet's Build-Depends. Cheers, -- Stéphane
Bug#1052197: xrdp: after bullseye-security upgrade, empty turquoise screen after logging in
Hi, xrdp developer and FreeBSD package maintainer here. As far as I looked xrdp & xorg package, xorgxrdp package is the issue. Update xorgxrdp to the latest 0.9.19 and build against xrdp 0.9.21.1. The it should work. When updating xrdp package in furure, to 0.9.23 for example, also update xorgxrdp to the latest version if available. Otherwise rebuild xorgxrdp against updated xrdp version at least. $ dpkg -l| grep xrdp ii xorgxrdp 1:0.2.12-1 amd64 Remote Desktop Protocol (RDP) modules for X.org ii xrdp 0.9.21.1-1~deb11u1 amd64 Remote Desktop Protocol (RDP) server -- meta
Processed: Bug#1052058 marked as pending in apt
Processing control commands: > tag -1 pending Bug #1052058 [apt] apt: refuses to downgrade itself to a version that works on the system Added tag(s) pending. -- 1052058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052058 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052058: marked as pending in apt
Control: tag -1 pending Hello, Bug #1052058 in apt 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/apt-team/apt/-/commit/925ada57d999a502dc2342092f32232b803be254 Downgrade unmerged-usr from error to two warnings One warning will be issued before the Y/n prompt, the other will be issued at the end after package installs have been attempted or if there were other failures, such that the last line you see is warnings about unmerged-usr I do not anticipate this to be the final version either, but there we go. Closes: #1052058 (this message was generated automatically) -- Greetings https://bugs.debian.org/1052058
Processed: severity of 969735 is normal
Processing commands for cont...@bugs.debian.org: > severity 969735 normal Bug #969735 [freespace2] freespace2-data-gog: doesn't accept the current GOG installer Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 969735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: FTBFS with OCaml 4.14.1
Processing control commands: > severity -1 serious Bug #1052230 [src:caml-crush] FTBFS with OCaml 4.14.1 Severity set to 'serious' from 'important' -- 1052230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052306: haskell-quickcheck: FTBFS on i386: 6 of 8 test suites (6 of 8 test cases) passed.
Source: haskell-quickcheck
Version: 2.14.3-1
Severity: serious
Tags: ftbfs sid trixie
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=haskell-quickcheck=i386=2.14.3-1=1693901450=0
=== prop_FromList from examples/Heap.hs:118 ===
+++ OK, passed 100 tests.
=== prop_ToSortedList from examples/Heap.hs:121 ===
*** Failed! (after 3 tests):
Exception:
QuickCheck.pick used with empty list
CallStack (from HasCallStack):
error, called at src/Test/QuickCheck/Gen.hs:312:15 in
QuickCheck-2.14.3-IcT7IGBF9jb4AGtBd4ZTHa:Test.QuickCheck.Gen
Exception thrown while showing test case:
QuickCheck.pick used with empty list
CallStack (from HasCallStack):
error, called at src/Test/QuickCheck/Gen.hs:312:15 in
QuickCheck-2.14.3-IcT7IGBF9jb4AGtBd4ZTHa:Test.QuickCheck.Gen
Test suite test-quickcheck: PASS
Test suite logged to: dist-ghc/test/QuickCheck-2.14.3-test-quickcheck.log
6 of 8 test suites (6 of 8 test cases) passed.
-e: error: debian/hlibrary.setup test --builddir=dist-ghc --show-details=direct
returned exit code 1
at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 880.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup test
--builddir=dist-ghc --show-details"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 610
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup test
--builddir=dist-ghc --show-details"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 473
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "test",
"--builddir=dist-ghc", "--show-details=direct") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 686
Debian::Debhelper::Buildsystem::Haskell::Recipes::check_recipe() called
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:163: check-ghc-stamp] Error 25
Cheers
--
Sebastian Ramacher
Bug#1052305: haskell-libbf: FTBFS on 32 bit architectures
Source: haskell-libbf Version: 0.6.6-1 Severity: serious Tags: ftbfs sid trixie 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=haskell-libbf=i386=0.6.6-1=1693660180=0 libghc-libbf-dev libghc-libbf-prof libghc-libbf-doc Running 1 test suites... Test suite libBF-tests: RUNNING... E: Build killed with signal TERM after 150 minutes of inactivity Cheers -- Sebastian Ramacher
