Processed: Re: Bug#1052973: octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1
Processing control commands: > reassign -1 octave-dev 8.3.0-1 Bug #1052973 [src:octave-image] octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1 Bug reassigned from package 'src:octave-image' to 'octave-dev'. No longer marked as found in versions octave-image/2.14.0-4. Ignoring request to alter fixed versions of bug #1052973 to the same values previously set Bug #1052973 [octave-dev] octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1 Marked as found in versions octave/8.3.0-1. > affects -1 octave-image Bug #1052973 [octave-dev] octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1 Added indication that 1052973 affects octave-image > notfound -1 octave-image/2.14.0-4 Bug #1052973 [octave-dev] octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1 Ignoring request to alter found versions of bug #1052973 to the same values previously set > forwarded -1 https://savannah.gnu.org/bugs/index.php?64725 Bug #1052973 [octave-dev] octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1 Set Bug forwarded-to-address to 'https://savannah.gnu.org/bugs/index.php?64725'. -- 1052973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052973: octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1
Control: reassign -1 octave-dev 8.3.0-1 Control: affects -1 octave-image Control: notfound -1 octave-image/2.14.0-4 Control: forwarded -1 https://savannah.gnu.org/bugs/index.php?64725 * Rafael Laboissière [2023-09-26 22:00]: Control: tags -1 + confirmed upstream * Lucas Nussbaum [2023-09-26 15:46]: Source: octave-image Version: 2.14.0-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): Summary: 2073 tests, 1744 passed, 36 known failures, 0 skipped Some tests failed. Giving up... make: *** [debian/rules:12: binary] Error 1 I think that this problem is triggered by a changing in behavior of the mkoctfile program, in the way it process its arguments, between versions 8.2 and 8.3 of Octave. I will try to get to this, as time permits. As I suspected, this bug is related to Bug#1050082 and is caused by a misbehavior of mkoctfile, a tool used to build the *.oct files needed by Octave, when options -f* are given to it. I have already filed a bug report upstream and I am hereby reassigning the present bug report to the octave-dev package. Best, Rafael Laboissière
Bug#1052935: marked as done (bm-el: FTBFS: make: *** [debian/rules:4: binary] Error 25)
Your message dated Fri, 29 Sep 2023 02:49:36 + with message-id and subject line Bug#1052935: fixed in bm-el 202309-1 has caused the Debian Bug report #1052935, regarding bm-el: FTBFS: make: *** [debian/rules:4: binary] Error 25 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.) -- 1052935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bm-el Version: 201905-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Ran 13 tests, 5 results as expected, 8 unexpected (2023-09-26 06:50:47+, > 4.341812 sec) > > 8 unexpected results: >FAILED bm-bookmark--add-remove-test >FAILED bm-bookmark--add-test >FAILED bm-bookmark--bm-bookmark-remove >FAILED bm-bookmark--bm-temporary-bookmark >FAILED bm-bookmark--modeline-test >FAILED bm-bookmark--multiple-bookmarks-forward-wrapping >FAILED bm-bookmark--option-bm-temporary-bookmark >FAILED bm-bookmark--save-and-restore > > dh_elpa_test: error: emacs -batch -Q -l package --eval "(add-to-list > 'package-directory-list \"/usr/share/emacs/site-lisp/elpa\")" --eval > "(add-to-list 'package-directory-list > \"/usr/share/emacs/site-lisp/elpa-src\")" -f package-initialize -L . --eval > "(load-file \"debian/ert-helper.el\")" -l bm-tests.el --eval > \(ert-run-tests-batch-and-exit\) returned exit code 1 > make: *** [debian/rules:4: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/09/25/bm-el_201905-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: bm-el Source-Version: 202309-1 Done: Nicholas D Steeves We believe that the bug you reported is fixed in the latest version of bm-el, 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. Nicholas D Steeves (supplier of updated bm-el 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, 28 Sep 2023 22:00:25 -0400 Source: bm-el Architecture: source Version: 202309-1 Distribution: unstable Urgency: medium Maintainer: Debian Emacsen team Changed-By: Nicholas D Steeves Closes: 1052935 Changes: bm-el (202309-1) unstable; urgency=medium . * New upstream release (Closes: #1052935). * Declare Standards-Version 4.6.2 (no changes required). Checksums-Sha1: 5526f10a82bdec586a9674e5ce6f36e4053c9f66 1913 bm-el_202309-1.dsc 04c54fe52e3a87586a43036cab45225b9a476830 22160 bm-el_202309.orig.tar.xz e93f1c165e7a5c79e5cdde09228eee797002cb8c 3520 bm-el_202309-1.debian.tar.xz fc40024f6fce310502e888214105e959bc5c11b4 8810 bm-el_202309-1_amd64.buildinfo Checksums-Sha256: fbb9f9a5a2450ba9468df8fccda104b9663180b3df844322afb40bfcf1ce 1913 bm-el_202309-1.dsc 373933163844cd2e382b7e6cae35eecd6f46bcd7b5471a0de55c7b2cd2181dc0 22160 bm-el_202309.orig.tar.xz a7ed42a321de2416301f761a71e76416dc2b12c9d6e52272e187c248c9ec0130 3520 bm-el_202309-1.debian.tar.xz c03504acb8511d4e5fcb5874ab73566c7eb318f776ff353a737843d16d62b48f 8810 bm-el_202309-1_amd64.buildinfo Files: 4e6c470724bd943960bed4042481d651 1913 lisp optional bm-el_202309-1.dsc e59ea2b8d5581686e89be8998c263211 22160 lisp optional bm-el_202309.orig.tar.xz e3eace77144ae97f5a488d8e99315464 3520
Bug#1053089: lxdm.conf information
control: tags -1 + unreproducible
I cannot reprocedure the issue on my machine. Need to find a way to
reprocedure it.
--
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
https://czchen.org/
Key fingerprint = BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B
signature.asc
Description: PGP signature
Processed: Re: Bug#1053089: lxdm.conf information
Processing control commands: > tags -1 + unreproducible Bug #1053089 [lxdm] lxdm: LXDM boots to a blank black screen with no options Added tag(s) unreproducible. -- 1053089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051739: Package is uninstallable, bug unacknowledged, therefore release critical
On Thu, 21 Sep 2023 15:59:45 + Mike Gabriel wrote: Problem here is that the downloaded dropbox executable probably is still GTK-2+. I need to test this and see how easily portable to GTK-3 is. It is a PyQt5 application now. So the dependency is not needed at all. I have verified it.
Processed: found 1053182 in 1.9.0-1
Processing commands for cont...@bugs.debian.org: > found 1053182 1.9.0-1 Bug #1053182 [src:libvpx] libvpx: CVE-2023-5217 Marked as found in versions libvpx/1.9.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053182: libvpx: diff for NMU version 1.12.0-1.1
X-Debbugs-CC: Sebastian Ramacher
Control: tags 1053182 + patch
Control: tags 1053182 + pending
Dear maintainer,
I've prepared an NMU for libvpx (versioned as 1.12.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru libvpx-1.12.0/debian/changelog libvpx-1.12.0/debian/changelog
--- libvpx-1.12.0/debian/changelog 2022-07-09 15:20:25.0 +0200
+++ libvpx-1.12.0/debian/changelog 2023-09-28 23:07:11.0 +0200
@@ -1,3 +1,11 @@
+libvpx (1.12.0-1.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * encode_api_test: add ConfigResizeChangeThreadCount
+ * VP8: disallow thread count changes (CVE-2023-5217) (Closes: #1053182)
+
+ -- Salvatore Bonaccorso Thu, 28 Sep 2023 23:07:11 +0200
+
libvpx (1.12.0-1) unstable; urgency=medium
* Team upload
diff -Nru libvpx-1.12.0/debian/patches/0002-encode_api_test-add-ConfigResizeChangeThreadCount.patch libvpx-1.12.0/debian/patches/0002-encode_api_test-add-ConfigResizeChangeThreadCount.patch
--- libvpx-1.12.0/debian/patches/0002-encode_api_test-add-ConfigResizeChangeThreadCount.patch 1970-01-01 01:00:00.0 +0100
+++ libvpx-1.12.0/debian/patches/0002-encode_api_test-add-ConfigResizeChangeThreadCount.patch 2023-09-28 23:07:11.0 +0200
@@ -0,0 +1,89 @@
+From: James Zern
+Date: Mon, 25 Sep 2023 18:53:41 -0700
+Subject: encode_api_test: add ConfigResizeChangeThreadCount
+Origin: https://github.com/webmproject/libvpx/commit/af6dedd715f4307669366944cca6e0417b290282
+Bug-Debian: https://bugs.debian.org/1053182
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2023-5217
+
+Update thread counts and resolution to ensure allocations are updated
+correctly. VP8 is disabled to avoid a crash.
+
+Bug: chromium:1486441
+Change-Id: Ie89776d9818d27dc351eff298a44c699e850761b
+---
+ test/encode_api_test.cc | 50 -
+ 1 file changed, 49 insertions(+), 1 deletion(-)
+
+--- a/test/encode_api_test.cc
b/test/encode_api_test.cc
+@@ -304,7 +304,6 @@ TEST(EncodeAPI, SetRoi) {
+
+ void InitCodec(const vpx_codec_iface_t , int width, int height,
+vpx_codec_ctx_t *enc, vpx_codec_enc_cfg_t *cfg) {
+- ASSERT_EQ(vpx_codec_enc_config_default(, cfg, 0), VPX_CODEC_OK);
+ cfg->g_w = width;
+ cfg->g_h = height;
+ cfg->g_lag_in_frames = 0;
+@@ -342,6 +341,7 @@ TEST(EncodeAPI, ConfigChangeThreadCount)
+ vpx_codec_ctx_t ctx = {};
+ } enc;
+
++ ASSERT_EQ(vpx_codec_enc_config_default(iface, , 0), VPX_CODEC_OK);
+ EXPECT_NO_FATAL_FAILURE(
+ InitCodec(*iface, kWidth, kHeight, , ));
+ if (IsVP9(iface)) {
+@@ -353,6 +353,54 @@ TEST(EncodeAPI, ConfigChangeThreadCount)
+
+ for (const auto threads : { 1, 4, 8, 6, 2, 1 }) {
+ cfg.g_threads = threads;
++EXPECT_NO_FATAL_FAILURE(EncodeWithConfig(cfg, ))
++<< "iteration: " << i << " threads: " << threads;
++ }
++}
++ }
++}
++
++TEST(EncodeAPI, ConfigResizeChangeThreadCount) {
++ constexpr int kInitWidth = 1024;
++ constexpr int kInitHeight = 1024;
++
++ for (const auto *iface : kCodecIfaces) {
++SCOPED_TRACE(vpx_codec_iface_name(iface));
++if (!IsVP9(iface)) {
++ GTEST_SKIP() << "TODO(https://crbug.com/1486441) remove this condition "
++ "after VP8 is fixed.";
++}
++for (int i = 0; i < (IsVP9(iface) ? 2 : 1); ++i) {
++ vpx_codec_enc_cfg_t cfg = {};
++ struct Encoder {
++~Encoder() { EXPECT_EQ(vpx_codec_destroy(), VPX_CODEC_OK); }
++vpx_codec_ctx_t ctx = {};
++ } enc;
++
++ ASSERT_EQ(vpx_codec_enc_config_default(iface, , 0), VPX_CODEC_OK);
++ // Start in threaded mode to ensure resolution and thread related
++ // allocations are updated correctly across changes in resolution and
++ // thread counts. See https://crbug.com/1486441.
++ cfg.g_threads = 4;
++ EXPECT_NO_FATAL_FAILURE(
++ InitCodec(*iface, kInitWidth, kInitHeight, , ));
++ if (IsVP9(iface)) {
++EXPECT_EQ(vpx_codec_control_(, VP9E_SET_TILE_COLUMNS, 6),
++ VPX_CODEC_OK);
++EXPECT_EQ(vpx_codec_control_(, VP9E_SET_ROW_MT, i),
++ VPX_CODEC_OK);
++ }
++
++ cfg.g_w = 1000;
++ cfg.g_h = 608;
++ EXPECT_EQ(vpx_codec_enc_config_set(, ), VPX_CODEC_OK)
++ << vpx_codec_error_detail();
++
++ cfg.g_w = 16;
++ cfg.g_h = 720;
++
++ for (const auto threads : { 1, 4, 8, 6, 2, 1 }) {
++cfg.g_threads = threads;
+ EXPECT_NO_FATAL_FAILURE(EncodeWithConfig(cfg, ))
+ << "iteration: " << i << " threads: " << threads;
+ }
diff -Nru libvpx-1.12.0/debian/patches/0003-VP8-disallow-thread-count-changes.patch libvpx-1.12.0/debian/patches/0003-VP8-disallow-thread-count-changes.patch
--- libvpx-1.12.0/debian/patches/0003-VP8-disallow-thread-count-changes.patch 1970-01-01 01:00:00.0 +0100
+++
Bug#1053182: libvpx: CVE-2023-5217
Source: libvpx Version: 1.12.0-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for libvpx. CVE-2023-5217[0]: | Heap buffer overflow in vp8 encoding in libvpx in Google Chrome | prior to 117.0.5938.132 and libvpx 1.13.1 allowed a remote attacker | to potentially exploit heap corruption via a crafted HTML page. | (Chromium security severity: High) 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-5217 https://www.cve.org/CVERecord?id=CVE-2023-5217 [1] https://github.com/webmproject/libvpx/commit/3fbd1dca6a4d2dad332a2110d646e4ffef36d590 [2] https://github.com/webmproject/libvpx/commit/af6dedd715f4307669366944cca6e0417b290282 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1052971: marked as done (golang-github-flowstack-go-jsonschema: FTBFS: make[1]: *** [debian/rules:13: copyright-scan] Error 1)
Your message dated Thu, 28 Sep 2023 20:37:21 + with message-id and subject line Bug#1052971: fixed in golang-github-flowstack-go-jsonschema 0.1.2-2 has caused the Debian Bug report #1052971, regarding golang-github-flowstack-go-jsonschema: FTBFS: make[1]: *** [debian/rules:13: copyright-scan] Error 1 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.) -- 1052971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-flowstack-go-jsonschema Version: 0.1.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > scan-copyrights >debian/copyright-scan.new.tmp > 2>debian/copyright-scan.new.todo.tmp > (sed -e 's/^/# /' debian/copyright-scan.new.todo.tmp; echo; cat > debian/copyright-scan.new.tmp) >debian/copyright-scan.new > diff -u debian/copyright-scan debian/copyright-scan.new > --- debian/copyright-scan 2022-07-26 16:22:03.0 + > +++ debian/copyright-scan.new 2023-09-26 06:09:57.935728612 + > @@ -1,31 +1,29 @@ > -# The following files were skipped: > +# Dpkg.Copyright.Grant.ByFile Dpkg::Copyright::Grant::ByFile::_warn The > following paths are missing information: > # - .github/workflows/go.yml > +# - README.md > +# - deref_test.go > # - go.sum > -# You may want to add a line in debian/copyright-scan-patterns.yml > -# or ask the author to add more default patterns to scan > -# > -# The following paths are missing information: > -# - README.md: missing copyright and license > -# - deref_test.go: missing copyright and license > -# - helpers.go: missing copyright and license > -# - parser.go: missing copyright and license > -# - schema.go: missing copyright and license > -# - schema_refs.go: missing copyright and license > -# - schema_refs_test.go: missing copyright and license > -# - schema_test.go: missing copyright and license > -# - schema_types.go: missing copyright and license > -# - schema_types_oneof.go: missing copyright and license > -# - schemas.go: missing copyright and license > -# - testtools/testtools.go: missing copyright and license > -# - testtools/testtools_test.go: missing copyright and license > -# - validate.go: missing copyright and license > -# - validate_test.go: missing copyright and license > -# - validate_unique.go: missing copyright and license > -# - validators.go: missing copyright and license > +# - helpers.go > +# - parser.go > +# - schema.go > +# - schema_refs.go > +# - schema_refs_test.go > +# - schema_test.go > +# - schema_types.go > +# - schema_types_oneof.go > +# - schemas.go > +# - testtools/testtools.go > +# - testtools/testtools_test.go > +# - validate.go > +# - validate_test.go > +# - validate_unique.go > +# - validators.go > # You may want to add a line in debian/fill.copyright.blanks.yml > # > +# (557) > +# Generating copyright data... > +# Copyright data generation done > > Files: * > Copyright: 2021, FlowStack > License: Expat > - > make[1]: *** [debian/rules:13: copyright-scan] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/09/25/golang-github-flowstack-go-jsonschema_0.1.2-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: golang-github-flowstack-go-jsonschema Source-Version: 0.1.2-2 Done: Domenico Andreoli We believe that the bug you reported is fixed in the latest version of golang-github-flowstack-go-jsonschema, 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,
Processed: Re: Bug#1051241: headsup for gtk + pipewire update
Processing commands for cont...@bugs.debian.org: > tags 1051241 ftbfs sid trixie Bug #1051241 [helvum] headsup for gtk + pipewire update Added tag(s) trixie, sid, and ftbfs. > End of message, stopping processing here. Please contact me if you need assistance. -- 1051241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999962: silversearcher-ag: diff for NMU version 2.2.0+git20200805-1.1
Manphiz writes: > Hi Nicholas, > > Thanks for sponsoring the NMU! I have pushed the release commit to > debian/2.2.0+git20200805-1.1 in my repo[1]. Let me know if the tag name > looks OK. > > [1] > https://salsa.debian.org/manphiz/silversearcher-ag/-/tags/debian%2F2.2.0+git20200805-1.1 > You're welcome! Looks good, so I merged it to the project. --N signature.asc Description: PGP signature
Bug#999962: silversearcher-ag: diff for NMU version 2.2.0+git20200805-1.1
Nicholas D Steeves writes: > Xiyue Deng writes: > >> Control: tags 62 + pending >> >> Dear maintainer, >> >> I've prepared an NMU for silversearcher-ag (versioned as >> 2.2.0+git20200805-1.1) >> and uploaded it to mentors.debian.net. Please feel free to tell me if I >> should >> delay it longer. > > You may have noticed that the timer fired and that the upload was > accepted :) Please push a release tag to you forked remote, and then > I'll merge your work into the debian/collab-maint project. > > Best, > Nicholas > Hi Nicholas, Thanks for sponsoring the NMU! I have pushed the release commit to debian/2.2.0+git20200805-1.1 in my repo[1]. Let me know if the tag name looks OK. [1] https://salsa.debian.org/manphiz/silversearcher-ag/-/tags/debian%2F2.2.0+git20200805-1.1 -- Manphiz signature.asc Description: PGP signature
Processed: Re: Bug#1051241: headsup for gtk + pipewire update
Processing control commands: > severity -1 serious Bug #1051241 [helvum] headsup for gtk + pipewire update Severity set to 'serious' from 'important' -- 1051241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999962: silversearcher-ag: diff for NMU version 2.2.0+git20200805-1.1
Xiyue Deng writes: > Control: tags 62 + pending > > Dear maintainer, > > I've prepared an NMU for silversearcher-ag (versioned as > 2.2.0+git20200805-1.1) > and uploaded it to mentors.debian.net. Please feel free to tell me if I should > delay it longer. You may have noticed that the timer fired and that the upload was accepted :) Please push a release tag to you forked remote, and then I'll merge your work into the debian/collab-maint project. Best, Nicholas signature.asc Description: PGP signature
Bug#1052832: marked as done (python-caldav: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Thu, 28 Sep 2023 18:49:30 +
with message-id
and subject line Bug#1052832: fixed in python-caldav 0.11.0-2
has caused the Debian Bug report #1052832,
regarding python-caldav: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1052832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-caldav
Version: 0.11.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> pybuild --configure -i python{version} -p 3.11
> I: pybuild base:291: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> pybuild --build -i python{version} -p 3.11
> I: pybuild base:291: /usr/bin/python3 setup.py build
> running build
> running build_py
> file caldav.py (for module caldav) not found
> creating /<>/.pybuild/cpython3_3.11_caldav/build/caldav
> copying caldav/__init__.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav
> copying caldav/objects.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav
> copying caldav/davclient.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav
> creating /<>/.pybuild/cpython3_3.11_caldav/build/caldav/elements
> copying caldav/elements/ical.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav/elements
> copying caldav/elements/base.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav/elements
> copying caldav/elements/__init__.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav/elements
> copying caldav/elements/dav.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav/elements
> copying caldav/elements/cdav.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav/elements
> creating /<>/.pybuild/cpython3_3.11_caldav/build/caldav/lib
> copying caldav/lib/vcal.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav/lib
> copying caldav/lib/debug.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav/lib
> copying caldav/lib/python_utilities.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav/lib
> copying caldav/lib/__init__.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav/lib
> copying caldav/lib/namespace.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav/lib
> copying caldav/lib/error.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav/lib
> copying caldav/lib/url.py ->
> /<>/.pybuild/cpython3_3.11_caldav/build/caldav/lib
> running egg_info
> creating caldav.egg-info
> writing caldav.egg-info/PKG-INFO
> writing dependency_links to caldav.egg-info/dependency_links.txt
> writing requirements to caldav.egg-info/requires.txt
> writing top-level names to caldav.egg-info/top_level.txt
> writing manifest file 'caldav.egg-info/SOURCES.txt'
> file caldav.py (for module caldav) not found
> reading manifest file 'caldav.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'changelog.0.8.md'
> adding license file 'COPYING.APACHE'
> adding license file 'COPYING.GPL'
> writing manifest file 'caldav.egg-info/SOURCES.txt'
> file caldav.py (for module caldav) not found
>dh_auto_test -O--buildsystem=pybuild
> pybuild --test --test-pytest -i python{version} -p 3.11
> I: pybuild base:291: cd /<>/.pybuild/cpython3_3.11_caldav/build;
> python3.11 -m pytest tests
> = test session starts
> ==
> platform linux -- Python 3.11.5, pytest-7.4.2, pluggy-1.3.0
> rootdir: /<>
> collected 101 items / 1 error
>
> ERRORS
>
> ___ ERROR collecting .pybuild/cpython3_3.11_caldav/build/tests/test_cdav.py
>
> /usr/lib/python3/dist-packages/_pytest/runner.py:341: in from_call
> result: Optional[TResult] = func()
> /usr/lib/python3/dist-packages/_pytest/runner.py:372: in
> call = CallInfo.from_call(lambda: list(collector.collect()), "collect")
> /usr/lib/python3/dist-packages/_pytest/python.py:531: in collect
> self._inject_setup_module_fixture()
> /usr/lib/python3/dist-packages/_pytest/python.py:545: in
> _inject_setup_module_fixture
> self.obj,
Bug#1053142: chromium cannot startup after libfreetype6 upgrade to 2.12.1+dfsg-5+deb12u1
Control: affects -1 src:freetype Technically it probably should be the other way around, but I fear this will be missed otherwise. Marking freetype as affected to at least it shows up there.
Processed: Re: Bug#1053142: chromium cannot startup after libfreetype6 upgrade to 2.12.1+dfsg-5+deb12u1
Processing control commands: > affects -1 src:freetype Bug #1053142 [chromium] chromium cannot startup after libfreetype6 upgrade to 2.12.1+dfsg-5+deb12u1 Added indication that 1053142 affects src:freetype -- 1053142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052947: marked as done (yaml-el: FTBFS: make: *** [debian/rules:7: binary] Error 25)
Your message dated Thu, 28 Sep 2023 18:19:23 +
with message-id
and subject line Bug#1052947: fixed in yaml-el 0.5.4-1
has caused the Debian Bug report #1052947,
regarding yaml-el: FTBFS: make: *** [debian/rules:7: binary] Error 25
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.)
--
1052947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yaml-el
Version: 0.5.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with elpa
>dh_update_autotools_config
>dh_autoreconf
>dh_elpa_test
> emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f
> package-initialize -L . --eval "(load-file \"yaml-tests.el\")" -l
> yaml-tests.el --eval \(ert-run-tests-batch-and-exit\)
> Loading /<>/yaml-tests.el (source)...
>
> Error: error ("Test ‘yaml-parsing-scalar’ redefined")
> mapbacktrace(#f(compiled-function (evald func args flags) # -0xa70c7ce14517944>))
> debug-early-backtrace()
> debug-early(error (error "Test ‘yaml-parsing-scalar’ redefined"))
> error("Test `%s' redefined" yaml-parsing-scalar)
> ert-set-test(yaml-parsing-scalar #s(ert-test :name yaml-parsing-scalar
> :documentation "Test conversion of !!str to JSON scalar" :body (closure (t)
> nil (let* ((fn-597 #'equal) (args-598 (condition-case err (let
> ((signal-hook-function #'ert--should-signal-hook)) (list :null
> (yaml--resolve-scalar-tag "null"))) (error (progn (setq fn-597 #'signal)
> (list (car err) (cdr err))) (let ((value-599
> 'ert-form-evaluation-aborted-600)) (let (form-description-601) (if
> (unwind-protect (setq value-599 (apply fn-597 args-598)) (setq
> form-description-601 (nconc (list '(should (equal :null
> (yaml--resolve-scalar-tag "null" (list :form (cons fn-597 args-598)) (if
> (eql value-599 'ert-form-evaluation-aborted-600) nil (list :value value-599))
> (if (eql value-599 'ert-form-evaluation-aborted-600) nil (let* ((-explainer-
> (and t (ert--get-explainer 'equal (if -explainer- (list :explanation
> (apply -explainer- args-598)) nil) (ert--signal-should-execution
> form-description-601)) nil (ert-fail form-description-601))) value-599))
> (let* ((fn-602 #'equal) (args-603 (condition-case err (let
> ((signal-hook-function #'ert--should-signal-hook)) (list :false
> (yaml--resolve-scalar-tag "false"))) (error (progn (setq fn-602 #'signal)
> (list (car err) (cdr err))) (let ((value-604
> 'ert-form-evaluation-aborted-605)) (let (form-description-606) (if
> (unwind-protect (setq value-604 (apply fn-602 args-603)) (setq
> form-description-606 (nconc (list '(should (equal :false
> (yaml--resolve-scalar-tag "false" (list :form (cons fn-602 args-603)) (if
> (eql value-604 'ert-form-evaluation-aborted-605) nil (list :value value-604))
> (if (eql value-604 'ert-form-evaluation-aborted-605) nil (let* ((-explainer-
> (and t (ert--get-explainer 'equal (if -explainer- (list :explanation
> (apply -explainer- args-603)) nil) (ert--signal-should-execution
> form-description-606)) nil (ert-fail form-description-606))) value-604))
> (let* ((fn-607 #'equal) (args-608 (condition-case err (let
> ((signal-hook-function #'ert--should-signal-hook)) (list t
> (yaml--resolve-scalar-tag "true"))) (error (progn (setq fn-607 #'signal)
> (list (car err) (cdr err))) (let ((value-609
> 'ert-form-evaluation-aborted-610)) (let (form-description-611) (if
> (unwind-protect (setq value-609 (apply fn-607 args-608)) (setq
> form-description-611 (nconc (list '(should (equal t (yaml--resolve-scalar-tag
> "true" (list :form (cons fn-607 args-608)) (if (eql value-609
> 'ert-form-evaluation-aborted-610) nil (list :value value-609)) (if (eql
> value-609 'ert-form-evaluation-aborted-610) nil (let* ((-explainer- (and t
> (ert--get-explainer 'equal (if -explainer- (list :explanation (apply
> -explainer- args-608)) nil) (ert--signal-should-execution
> form-description-611)) nil (ert-fail form-description-611))) value-609))
> (let* ((fn-612 #'equal) (args-613 (condition-case err (let
> ((signal-hook-function #'ert--should-signal-hook)) (list "xtruex"
> (yaml--resolve-scalar-tag "xtruex"))) (error (progn (setq fn-612
Bug#1052955: marked as done (irony-mode: FTBFS: make: *** [debian/rules:8: binary] Error 25)
Your message dated Thu, 28 Sep 2023 18:19:06 + with message-id and subject line Bug#1052955: fixed in irony-mode 1.6.0-1 has caused the Debian Bug report #1052955, regarding irony-mode: FTBFS: make: *** [debian/rules:8: binary] Error 25 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.) -- 1052955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: irony-mode Version: 1.5.0-5+deb12u1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > [ 25%] Building CXX object > src/CMakeFiles/irony-server.dir/support/TemporaryFile.cpp.o > [ 25%] Building CXX object > src/CMakeFiles/irony-server.dir/support/CommandLineParser.cpp.o > [ 37%] Building CXX object src/CMakeFiles/irony-server.dir/TUManager.cpp.o > cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ > -I/<>/server/src -I/usr/lib/llvm-15/include -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT > src/CMakeFiles/irony-server.dir/support/CommandLineParser.cpp.o -MF > CMakeFiles/irony-server.dir/support/CommandLineParser.cpp.o.d -o > CMakeFiles/irony-server.dir/support/CommandLineParser.cpp.o -c > /<>/server/src/support/CommandLineParser.cpp > [ 50%] Building CXX object src/CMakeFiles/irony-server.dir/CompDBCache.cpp.o > [ 62%] Building CXX object src/CMakeFiles/irony-server.dir/main.cpp.o > cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ > -I/<>/server/src -I/usr/lib/llvm-15/include -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT > src/CMakeFiles/irony-server.dir/support/TemporaryFile.cpp.o -MF > CMakeFiles/irony-server.dir/support/TemporaryFile.cpp.o.d -o > CMakeFiles/irony-server.dir/support/TemporaryFile.cpp.o -c > /<>/server/src/support/TemporaryFile.cpp > cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ > -DCLANG_RESOURCE_DIR=\"/usr/lib/llvm-15/lib/clang/15.0.7\" > -I/<>/server/src -I/usr/lib/llvm-15/include -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT > src/CMakeFiles/irony-server.dir/TUManager.cpp.o -MF > CMakeFiles/irony-server.dir/TUManager.cpp.o.d -o > CMakeFiles/irony-server.dir/TUManager.cpp.o -c > /<>/server/src/TUManager.cpp > [ 87%] Building CXX object src/CMakeFiles/irony-server.dir/Command.cpp.o > [ 87%] Building CXX object src/CMakeFiles/irony-server.dir/Irony.cpp.o > cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ > -I/<>/server/src -I/usr/lib/llvm-15/include -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT > src/CMakeFiles/irony-server.dir/CompDBCache.cpp.o -MF > CMakeFiles/irony-server.dir/CompDBCache.cpp.o.d -o > CMakeFiles/irony-server.dir/CompDBCache.cpp.o -c > /<>/server/src/CompDBCache.cpp > cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ > -DIRONY_PACKAGE_VERSION=\"1.5.0\" -I/<>/server/src > -I/usr/lib/llvm-15/include -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -MD > -MT src/CMakeFiles/irony-server.dir/main.cpp.o -MF > CMakeFiles/irony-server.dir/main.cpp.o.d -o > CMakeFiles/irony-server.dir/main.cpp.o -c /<>/server/src/main.cpp > cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ > -I/<>/server/src -I/usr/lib/llvm-15/include -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT > src/CMakeFiles/irony-server.dir/Irony.cpp.o -MF > CMakeFiles/irony-server.dir/Irony.cpp.o.d -o > CMakeFiles/irony-server.dir/Irony.cpp.o -c > /<>/server/src/Irony.cpp > cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ > -I/<>/server/src -I/usr/lib/llvm-15/include -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT >
Bug#999962: marked as done (silversearcher-ag: depends on obsolete pcre3 library)
Your message dated Thu, 28 Sep 2023 18:04:27 + with message-id and subject line Bug#62: fixed in silversearcher-ag 2.2.0+git20200805-1.1 has caused the Debian Bug report #62, regarding silversearcher-ag: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 62: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=62 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: silversearcher-ag Severity: important User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian --- End Message --- --- Begin Message --- Source: silversearcher-ag Source-Version: 2.2.0+git20200805-1.1 Done: Xiyue Deng We believe that the bug you reported is fixed in the latest version of silversearcher-ag, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xiyue Deng (supplier of updated silversearcher-ag 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 23:41:55 -0700 Source: silversearcher-ag Architecture: source Version: 2.2.0+git20200805-1.1 Distribution: unstable Urgency: medium Maintainer: Hajime Mizuno Changed-By: Xiyue Deng Closes: 62 Changes: silversearcher-ag (2.2.0+git20200805-1.1) unstable; urgency=medium . * Non-maintainer upload * Enable pcre2 support to replace deprecated pcre1 (Closes: #62) - Add d/p/enable_pcre2_support.patch cherrypicked from upstream pcre2 branch - Build-Depends on libpcre2-dev instead of libpcre3-dev * Update d/copyright with copyright owners of the pcre2 patch and m4/* Checksums-Sha1: df88733a9c19c9db37652ae1a63823b374485d9c 1955 silversearcher-ag_2.2.0+git20200805-1.1.dsc 55ede66e60bd78a5230388fa869dd0ab0b508465 14944 silversearcher-ag_2.2.0+git20200805-1.1.debian.tar.xz 2c2c6ba89d24dd5adf3eea30b9fef05415d596a6 6521 silversearcher-ag_2.2.0+git20200805-1.1_amd64.buildinfo Checksums-Sha256: bbb5b0df6a6bbe6c222405a6ab5aa5194c2446a77c6ba5469c3804380a3576e5 1955 silversearcher-ag_2.2.0+git20200805-1.1.dsc 2446038aee8d98845ea1e7f8ba34a540e0ed14f0a54704de51eb80ff997306c3 14944 silversearcher-ag_2.2.0+git20200805-1.1.debian.tar.xz d414c9301336fda79eb4b2160cdcde397c07e8abf48799f7808744822dc3155d 6521 silversearcher-ag_2.2.0+git20200805-1.1_amd64.buildinfo Files: 25bf12e39580e407ecc2860b5ae033e3 1955 utils optional silversearcher-ag_2.2.0+git20200805-1.1.dsc 6507b3d84b82f38e1bdd7acc9c3fface 14944 utils optional silversearcher-ag_2.2.0+git20200805-1.1.debian.tar.xz 8abba3335dbd6f78bcfc4384150f9003 6521 utils optional silversearcher-ag_2.2.0+git20200805-1.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmUTFDEACgkQWogwR199 EGF3QxAAo8flpB/28QkU/fOjxPZnYOD22MI4DAAthRNnXk0/SEtop28r9MQ5QsUe RxaFM16xuMgzN8XfKaZZSrJOn2Vb86o/XQOHiy0u/jyaTv1okYPmlHb+Yvhj4pWs USXkkQGJyQj420rZKwQVu3KFF85krAtOPyD40n4aoGC2Q5QMtJcWFMsdjmRkaF1Z ySLqdPwQ8daxRFj5Ttv4nq8XNa6+eJGU5qYLXVkNDt3/fWMAYW3anSWdOKIBvEy+ 3PbCNAgcvJ3UYLviLd8snFLTJCL4esgUJLfRM+YgWSrsTwVFYAm0w+bLkhlD/sSF KYNV2P+lhfBU5XwY8qdG2TZtzbSu4HckkdDddD1fYFgO5CGiNdr9qkBIQ6VGUn82
Bug#1051400: marked as done (tp-smapi-dkms: update DEFINE_SEMAPHORE usage for linux 6.4+)
Your message dated Thu, 28 Sep 2023 19:17:00 +0200 with message-id <07a1c4b2-6a07-417e-84a1-afd950e72...@debian.org> and subject line Re: tp-smapi-dkms: update DEFINE_SEMAPHORE usage for linux 6.4+ has caused the Debian Bug report #1051400, regarding tp-smapi-dkms: update DEFINE_SEMAPHORE usage for linux 6.4+ 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.) -- 1051400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tp-smapi-dkms Version: 0.43-3 Severity: serious Tags: patch ftbfs Justification: fails to build from source Dear Maintainer, the problem and the solution are already described here https://groups.google.com/g/linux.debian.bugs.dist/c/SntCd-vPkEU?pli=1 -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-0.deb12.2-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tp-smapi-dkms depends on: ii dkms 3.0.10-8+deb12u1 tp-smapi-dkms recommends no packages. tp-smapi-dkms suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: tp-smapi/0.44-1 On Thu, 07 Sep 2023 13:37:56 +0200 Benjamin Rechsteiner wrote: the problem and the solution are already described here https://groups.google.com/g/linux.debian.bugs.dist/c/SntCd-vPkEU?pli=1 So this bug is obviously a duplicate because that links points to an archive of Debian bug #1038207. Please do not file bugs that you know are already existing in the Debian Bug Tracker.--- End Message ---
Bug#1053178: hg-git: incompatible with mercurial 6.5
Source: hg-git Version: 1.0.2-1 Severity: grave X-Debbugs-Cc: jcris...@debian.org Hi, hg-git looks like it needs an update for compatibility with current mercurial, see e.g. https://ci.debian.net/data/autopkgtest/testing/amd64/h/hg-git/38210693/log.gz > ** Unknown exception encountered with possibly-broken third-party extension > "hggit" unknown (dulwich 0.21.6) > ** which supports versions 6.4 of Mercurial. > ** Please disable "hggit" and try your action again. > ** If that fixes the bug please report it to > https://foss.heptapod.net/mercurial/hg-git/issues > ** Python 3.11.5 (main, Aug 29 2023, 15:31:31) [GCC 13.2.0] > ** Mercurial Distributed SCM (version 6.5.2) > ** Extensions loaded: hggit unknown (dulwich 0.21.6) > Traceback (most recent call last): > File "/usr/bin/hg", line 59, in > dispatch.run() > File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 143, in > run > status = dispatch(req) > ^ > File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 232, in > dispatch > status = _rundispatch(req) > ^ > File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 276, in > _rundispatch > ret = _runcatch(req) or 0 > ^^ > File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 457, in > _runcatch > return _callcatch(ui, _runcatchfunc) >^ > File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 467, in > _callcatch > return scmutil.callcatch(ui, func) >^^^ > File "/usr/lib/python3/dist-packages/mercurial/scmutil.py", line 153, in > callcatch > return func() >^^ > File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 447, in > _runcatchfunc > return _dispatch(req) >^^ > File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1272, in > _dispatch > return runcommand( >^^^ > File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 905, in > runcommand > ret = _runcommand(ui, options, cmd, d) > > File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1284, in > _runcommand > return cmdfunc() >^ > File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1270, in > > d = lambda: util.checksignature(func)(ui, *args, **strcmdopt) > ^ > File "/usr/lib/python3/dist-packages/mercurial/util.py", line 1881, in check > return func(*args, **kwargs) >^ > File "/usr/lib/python3/dist-packages/mercurial/commands.py", line 1992, in > clone > r = hg.clone( > ^ > File "/usr/lib/python3/dist-packages/hggit/schemes.py", line 121, in clone > srcpeer, destpeer = orig(*args, **opts) > ^^^ > File "/usr/lib/python3/dist-packages/mercurial/hg.py", line 727, in clone > srcpeer = peer(ui, peeropts, src_path) > > File "/usr/lib/python3/dist-packages/hggit/schemes.py", line 112, in peer > newpeer = orig(uiorrepo, *args, **opts) > ^ > File "/usr/lib/python3/dist-packages/mercurial/hg.py", line 286, in peer > peer = repo.peer(path=peer_path, remotehidden=remotehidden) > > TypeError: gitrepo.peer() got an unexpected keyword argument 'remotehidden' Cheers, Julien
Processed: bug 1052843 is forwarded to https://github.com/wagtail/django-modelcluster/issues/173
Processing commands for cont...@bugs.debian.org: > forwarded 1052843 https://github.com/wagtail/django-modelcluster/issues/173 Bug #1052843 [src:python-django-modelcluster] python-django-modelcluster: FTBFS: AssertionError: != Set Bug forwarded-to-address to 'https://github.com/wagtail/django-modelcluster/issues/173'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1052843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: petsc: misbuild with gcc-13
Processing control commands: > severity 1049903 important Bug #1049903 [petsc] petsc: misbuild with gcc-13 Severity set to 'important' from 'serious' > tags 1049903 moreinfo Bug #1049903 [petsc] petsc: misbuild with gcc-13 Added tag(s) moreinfo. -- 1049903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1049903: petsc: misbuild with gcc-13
Source: petsc Followup-For: Bug #1049903 Control: severity 1049903 important Control: tags 1049903 moreinfo I said previously I'd apply the patch, but I wanted to check the problem first. No problem is showing at https://tests.reproducible-builds.org/debian/rb-pkg/petsc.html even in the experimental rebuilds. I tried rebuilding in an experimental chroot on barriere.debian.org porterbox (amd64), using libc6-dev 2.38-3 with 13.2.0-4. No problem there either, even with libc6 version 28. It sounds like some problem might have entered into ubuntu mantic. I think it would be better to track down that problem rather than papering over it and ignoring it. Downgrading severity since the error is not reliably reproducible. Is Ubuntu still affected by the problem?
Processed: reassign 1053107 to src:squid, forcibly merging 1043112 1052541
Processing commands for cont...@bugs.debian.org: > reassign 1053107 src:squid 6.1-2 Bug #1053107 [squid-dbgsym] Provide squid-dbgsym packages for amd64 platform Warning: Unknown package 'squid-dbgsym' Bug reassigned from package 'squid-dbgsym' to 'src:squid'. No longer marked as found in versions squid/6.1-2. Ignoring request to alter fixed versions of bug #1053107 to the same values previously set Bug #1053107 [src:squid] Provide squid-dbgsym packages for amd64 platform Marked as found in versions squid/6.1-2. > forcemerge 1043112 1052541 Bug #1043112 [apfs-dkms] apfs-dkms: module fails to build for Linux 6.5: detected write beyond size of object Bug #1043112 [apfs-dkms] apfs-dkms: module fails to build for Linux 6.5: detected write beyond size of object Added tag(s) ftbfs. Bug #1052541 [apfs-dkms] apfs-dkms: Still not building Set Bug forwarded-to-address to 'https://github.com/linux-apfs/linux-apfs-rw/issues/49'. Marked as found in versions linux-apfs-rw/0.3.3-2. Added tag(s) fixed-upstream. Merged 1043112 1052541 > thanks Stopping processing here. Please contact me if you need assistance. -- 1043112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043112 1052541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052541 1053107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: dkms: Signature keys unexpectedly overridden
Processing control commands: > tag -1 - moreinfo + upstream Bug #1052243 [dkms] dkms: Signature keys unexpectedly overridden Removed tag(s) moreinfo. Bug #1052243 [dkms] dkms: Signature keys unexpectedly overridden Added tag(s) upstream. > severity -1 normal Bug #1052243 [dkms] dkms: Signature keys unexpectedly overridden Severity set to 'normal' from 'critical' -- 1052243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052243: dkms: Signature keys unexpectedly overridden
Control: tag -1 - moreinfo + upstream Control: severity -1 normal On 28/09/2023 17.05, Tobias Bossert wrote: > Did both files exist? Indeed, in my case the `.key` existed while the one meant for the certificate had a different extension...So as you confirmed, the observed "overwriting" behavior is intended. However, I think my point about not expecting this is still valid - as the neither the comment in the `/etc/dkms/framework.conf` nor the man page does mention this with any word. Thanks for confirming. Downgrading the severity since this is only a documentation issue. Andreas
Bug#1052243: dkms: Signature keys unexpectedly overridden
Hi Andreas > Did both files exist? Indeed, in my case the `.key` existed while the one meant for the certificate had a different extension...So as you confirmed, the observed "overwriting" behavior is intended. However, I think my point about not expecting this is still valid - as the neither the comment in the `/etc/dkms/framework.conf` nor the man page does mention this with any word. Tobias On 28.09.23 15:49, Andreas Beckmann wrote: Control: tag -1 moreinfo On Tue, 19 Sep 2023 13:37:01 +0200 Tobias Bossert wrote: Package: dkms Version: 3.0.11-3 Enrolled my own secureboot key chain (PK, KEK, db) and wanted dkms to sign kernel modules automatically. I tried to reproduce that in a sid chroot by setting mok_signing_key=/etc/dkms/mok.key mok_certificate=/etc/dkms/mok.pub in framework.conf and created them with openssl req -new -x509 -nodes -days 36500 \ -subj "/CN=DKMS module signing key" -newkey rsa:2048 \ -keyout /etc/dkms/mok.key -outform DER -out /etc/dkms/mok.pub Then I installed linux-headers-amd64 and dkms-test-dkms. That didn't modify my keys. * What exactly did you do (or not do) that was effective (or ineffective)? Set `mok_signing_key=` and `mok_certificate` in `/etc/dkms/framework.conf` to my DB.key/DB.crt and then installed the `nvidia-driver` using apt. Did both files exist? * What was the outcome of this action? My DB.key and DB.crt were overridden by some new keys. This should only have happened if one of the files was missing. And that I can reproduce in my chroot, if I rename one of the files, a new pair gets generated. * What outcome did you expect instead? Even if my configuration is wrong, I would never expect that setting `mok_signing_key=` overriddes anything. dkms doesn't know where the mok_signing_key= and mok_certificate= settings come from. The values could be * builtin defaults * distribution defaults set in framework.conf * user customized values set in framework.conf * empty, which causes a fallback to builtin defaults If either the .key or the .crt file is missing, dkms will generate a new .key and self-signed .crt in the locations pointed to by mok_signing_key= and mok_certificate= Andreas
Bug#1052908: marked as done (flexpart: FTBFS: Fatal Error: Cannot open module file 'grib_api.mod' for reading at (1): No such file or directory)
Your message dated Thu, 28 Sep 2023 15:07:22 + with message-id and subject line Bug#1052908: fixed in eccodes 2.31.2-2 has caused the Debian Bug report #1052908, regarding flexpart: FTBFS: Fatal Error: Cannot open module file 'grib_api.mod' for reading at (1): 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.) -- 1052908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flexpart Version: 9.02-26 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 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 '/<>' > gfortran -c -O2 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 > -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian > -frecord-marker=4 -I/usr/include par_mod.f90 > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > gfortran -c -O2 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 > -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian > -frecord-marker=4 -I/usr/include com_mod.f90 > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > gfortran -c -O2 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 > -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian > -frecord-marker=4 -I/usr/include conv_mod.f90 > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > gfortran -c -O2 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 > -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian > -frecord-marker=4 -I/usr/include hanna_mod.f90 > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > gfortran -c -O2 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 > -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian > -frecord-marker=4 -I/usr/include interpol_mod.f90 > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > gfortran -c -O2 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 > -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian > -frecord-marker=4 -I/usr/include cmapf_mod.f90 > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > gfortran -c -O2 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 > -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian > -frecord-marker=4 -I/usr/include unc_mod.f90 > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > gfortran -c -O2 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 > -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian > -frecord-marker=4 -I/usr/include oh_mod.f90 > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > gfortran -c -O2 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 > -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian > -frecord-marker=4 -I/usr/include xmass_mod.f90 > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > gfortran -c -O2 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 > -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian > -frecord-marker=4 -I/usr/include flux_mod.f90 > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > gfortran -c -O2 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 > -mcmodel=medium -O2 -fdefault-real-8 -fconvert=little-endian > -frecord-marker=4 -I/usr/include point_mod.f90 > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > gfortran -c -O2
Bug#1052890: marked as done (flextra: FTBFS: Fatal Error: Cannot open module file 'grib_api.mod' for reading at (1): No such file or directory)
Your message dated Thu, 28 Sep 2023 15:07:22 + with message-id and subject line Bug#1052890: fixed in eccodes 2.31.2-2 has caused the Debian Bug report #1052890, regarding flextra: FTBFS: Fatal Error: Cannot open module file 'grib_api.mod' for reading at (1): 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.) -- 1052890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052890 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flextra Version: 5.0-17 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230925 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 '/<>' > x86_64-linux-gnu-gfortran-13 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 -fPIC > -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o caldate.o > caldate.f > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > x86_64-linux-gnu-gfortran-13 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 -fPIC > -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o > openoutput.o openoutput.f > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > openoutput.f:40:72: > >40 | do 1 j=i+1,numpoint > | > 1 > Warning: Fortran 2018 deleted feature: Shared DO termination label 1 at (1) > x86_64-linux-gnu-gfortran-13 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 -fPIC > -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o > checklimits.o checklimits.f > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > x86_64-linux-gnu-gfortran-13 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 -fPIC > -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o > coordtrafo.o coordtrafo.f > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > coordtrafo.f:38:72: > >38 | 10 ypoint(i)=(ypoint(i)-ylat0)/dy > | > 1 > Warning: Fortran 2018 deleted feature: DO termination statement which is not > END DO or CONTINUE with label 10 at (1) > coordtrafo.f:63:72: > >63 | 20compoint(j-1)=compoint(j) > | > 1 > Warning: Fortran 2018 deleted feature: DO termination statement which is not > END DO or CONTINUE with label 20 at (1) > x86_64-linux-gnu-gfortran-13 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 -fPIC > -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o > orolininterpol.o orolininterpol.f > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > x86_64-linux-gnu-gfortran-13 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 -fPIC > -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o etatrafo.o > etatrafo.f > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > x86_64-linux-gnu-gfortran-13 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 -fPIC > -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o petters.o > petters.f > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > x86_64-linux-gnu-gfortran-13 > -I/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13 -fPIC > -fconvert=little-endian -frecord-marker=4 -I/usr/include -c -o eta.ecmwf.o > eta.ecmwf.f > f951: Warning: Nonexistent include directory > '/usr/lib/x86_64-linux-gnu/fortran/x86_64-linux-gnu-gfortran-13' > [-Wmissing-include-dirs] > eta.ecmwf.f:39:72: > >39 | 10plevel1=plevel2 > | > 1 > Warning: Fortran 2018 deleted feature: DO termination statement which is not > END DO or
Bug#1053170: Apache NOTICE file missing from binary package
Package: bat Version: 0.23.0-4 Severity: serious bat's upstream source and the rust-bat_0.23.0.orig.tar.gz file both contain a NOTICE file which, per the packages's Apache 2.0 license, must be preserved in derivative works. However, this NOTICE file is not present in the binary .deb packages distributed by Debian. Note that bat itself embeds the text of the NOTICE file in its own binary, and the text is displayed when running `batcat --acknowledgements`. However, Paul Wise has stated on the debian-legal mailing list that the NOTICE should still be distributed as a file in the .deb packages: https://lists.debian.org/debian-legal/2023/09/msg00012.html
Processed: Re: dkms: Signature keys unexpectedly overridden
Processing control commands: > tag -1 moreinfo Bug #1052243 [dkms] dkms: Signature keys unexpectedly overridden Added tag(s) moreinfo. -- 1052243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052243: dkms: Signature keys unexpectedly overridden
Control: tag -1 moreinfo On Tue, 19 Sep 2023 13:37:01 +0200 Tobias Bossert wrote: Package: dkms Version: 3.0.11-3 Enrolled my own secureboot key chain (PK, KEK, db) and wanted dkms to sign kernel modules automatically. I tried to reproduce that in a sid chroot by setting mok_signing_key=/etc/dkms/mok.key mok_certificate=/etc/dkms/mok.pub in framework.conf and created them with openssl req -new -x509 -nodes -days 36500 \ -subj "/CN=DKMS module signing key" -newkey rsa:2048 \ -keyout /etc/dkms/mok.key -outform DER -out /etc/dkms/mok.pub Then I installed linux-headers-amd64 and dkms-test-dkms. That didn't modify my keys. * What exactly did you do (or not do) that was effective (or ineffective)? Set `mok_signing_key=` and `mok_certificate` in `/etc/dkms/framework.conf` to my DB.key/DB.crt and then installed the `nvidia-driver` using apt. Did both files exist? * What was the outcome of this action? My DB.key and DB.crt were overridden by some new keys. This should only have happened if one of the files was missing. And that I can reproduce in my chroot, if I rename one of the files, a new pair gets generated. * What outcome did you expect instead? Even if my configuration is wrong, I would never expect that setting `mok_signing_key=` overriddes anything. dkms doesn't know where the mok_signing_key= and mok_certificate= settings come from. The values could be * builtin defaults * distribution defaults set in framework.conf * user customized values set in framework.conf * empty, which causes a fallback to builtin defaults If either the .key or the .crt file is missing, dkms will generate a new .key and self-signed .crt in the locations pointed to by mok_signing_key= and mok_certificate= Andreas
Bug#1052376: possible solution
Hello, The issue you are reporting can be fixed with patches from Bug#1052050. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052050 Mikhail Kshevetskiy
Processed: block 1031173 with 960425
Processing commands for cont...@bugs.debian.org: > block 1031173 with 960425 Bug #1031173 [arcanist-clang-format-linter] arcanist-clang-format-linter: prevents arcanist tool from working (PHP Fatal error: Uncaught Error) 1031173 was not blocked by any bugs. 1031173 was not blocking any bugs. Added blocking bug(s) of 1031173: 960425 > thanks Stopping processing here. Please contact me if you need assistance. -- 1031173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 1051858 1052731
Processing commands for cont...@bugs.debian.org: > forcemerge 1051858 1052731 Bug #1051858 [src:clazy] clazy: FTBFS with llvm-toochain-16 as default Bug #1052731 [src:clazy] clazy: FTBFS: SourceCompatibilityHelpers.h:112:24: error: ‘class std::optional’ has no member named ‘hasValue’; did you mean ‘has_value’? Merged 1051858 1052731 > thanks Stopping processing here. Please contact me if you need assistance. -- 1051858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051858 1052731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: nuget: CVE-2023-29337
Processing control commands: > fixed -1 nuget/2.8.7+md510+dhx1-1.1 Bug #1050835 [src:nuget] nuget: CVE-2023-29337 Marked as fixed in versions nuget/2.8.7+md510+dhx1-1.1. -- 1050835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050835: nuget: CVE-2023-29337
Control: fixed -1 nuget/2.8.7+md510+dhx1-1.1 You can see the fix for the oldest affected and supported product line at https://github.com/NuGet/NuGet.Client/commit/beea05411b6483ecfd8b1e4517c3dc4659bb6ac0 The affected code entered a year ago at https://github.com/NuGet/NuGet.Client/commit/a7f6bf5b417063d75a993f98b4c82c2abced2136 That version (5.11.5) is way newer than the one in Debian (2.8.7+md510+dhx1), which is actually a Mono-specific fork of the official nuget client, which has a 2.8.6. In our old version, there is nothing that seems like that code.
Bug#1053154: marked as done (mono-xsp4: needs perl dependency for postinst)
Your message dated Thu, 28 Sep 2023 12:04:52 + with message-id and subject line Bug#1053154: fixed in xsp 4.2-2.5 has caused the Debian Bug report #1053154, regarding mono-xsp4: needs perl dependency for postinst 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.) -- 1053154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mono-xsp4 Version: 4.2-2.4 Severity: serious The package does not install because postinst triggers mono-xsp4-update, which needs MD5.pm. The package has to depend on perl. --- End Message --- --- Begin Message --- Source: xsp Source-Version: 4.2-2.5 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of xsp, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated xsp 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, 28 Sep 2023 12:54:54 +0200 Source: xsp Architecture: source Version: 4.2-2.5 Distribution: unstable Urgency: medium Maintainer: Debian Mono Group Changed-By: Bastian Germann Closes: 1051045 1053154 Changes: xsp (4.2-2.5) unstable; urgency=medium . * Non-maintainer upload * mono-xsp4: Add perl dependency (Closes: #1053154) * Move Vcs fields to salsa repo * Remove retired uploader (Closes: #1051045) Checksums-Sha1: a5115192bda90c4ff48d7c22bbc0f12e8be0dcdd 2458 xsp_4.2-2.5.dsc bb1a8e98115c55562eac3db5a7c6347f8bf20b31 46500 xsp_4.2-2.5.debian.tar.xz 7909e561e53e440af75d4b38bb0f2f7cf1d39dea 17113 xsp_4.2-2.5_source.buildinfo Checksums-Sha256: 56a5e9f4a414686f60dc2a198a7ff23c18bde4dcfe69f447a65754a9a3367c81 2458 xsp_4.2-2.5.dsc a44253af866b1222f01cd0d3f0a6b5866330fdfbbda1f7686bfeafcb7a9caa0c 46500 xsp_4.2-2.5.debian.tar.xz ed7b60f61939869ac2232c1b0a2292813e10880d76072a8471916a1a76681e85 17113 xsp_4.2-2.5_source.buildinfo Files: c1befbd0aa533d4502ae722435866071 2458 web optional xsp_4.2-2.5.dsc 5b76ffaf2d9ccaece418ad236c52c974 46500 web optional xsp_4.2-2.5.debian.tar.xz 193308a3be6e2c4b42f4ec1436523d3e 17113 web optional xsp_4.2-2.5_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUVancQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFPIjC/9VBP+e/RfctvRwEGx8ZCswjVrAjmGZjFFi CBkj6q4F7Qxf6kxL/OLO24Tn0D5ZDOjMe0D843UCEd+/oDmfazNNLNWfETJGTMFq 0uNo/Qfqew9FgM8Q9+GXpSOKUv4s5mHh5uTHbr4gFrieSNny/x/Ojeo8/Y4KtFJX 9PAA1VNyE/qDOIlPODafscFz4KrDJceDkzCEuEbVOvxCkvupH8bVlNs2qpvI/Fjq Pj4KYhgL1+cT+9PnzffL0KBcsjouqBN0huoUK3MfgRN1J2ok3qdz8/ADp2/MMCrL RTZiuKmwsQv7WonZyIxGxkoJHSEnSVpBy0CTX2PyLhWXo/DnSv0SAbgZVqhGd+J2 BuFDNu1w54BVmzUlfoV9gBdH2UWVndmH4ri3CA98J7b21Ou5ZYsnNTqsizs3rWR/ sHzI1Slu3Wz4mP7h9XxK3LQQIrIqHkR3RKkp5qiRIV3EFY4ffewqX9mlylklN/tX HVcbsE/JJWXpYeJ3TCUJsb3fC8zASxo= =hZdc -END PGP SIGNATURE End Message ---
Bug#1053154: mono-xsp4: needs perl dependency for postinst
I am uploading a NMU to fix this.
The debdiff is attached.diff -Nru xsp-4.2/debian/changelog xsp-4.2/debian/changelog
--- xsp-4.2/debian/changelog2023-01-15 08:17:38.0 +0100
+++ xsp-4.2/debian/changelog2023-09-28 12:54:54.0 +0200
@@ -1,3 +1,12 @@
+xsp (4.2-2.5) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * mono-xsp4: Add perl dependency (Closes: #1053154)
+ * Move Vcs fields to salsa repo
+ * Remove retired uploader (Closes: #1051045)
+
+ -- Bastian Germann Thu, 28 Sep 2023 12:54:54 +0200
+
xsp (4.2-2.4) unstable; urgency=medium
* Non-maintainer upload.
@@ -728,7 +737,7 @@
the compatible versions is not always equal to the XSP version.
-- Debian Mono Group Wed, 17 May
2006 20:32:00 +0200
-
+
xsp (1.1.13-1) unstable; urgency=low
* New upstream release
diff -Nru xsp-4.2/debian/control xsp-4.2/debian/control
--- xsp-4.2/debian/control 2023-01-15 08:17:38.0 +0100
+++ xsp-4.2/debian/control 2023-09-28 12:54:54.0 +0200
@@ -2,7 +2,7 @@
Section: web
Priority: optional
Maintainer: Debian Mono Group
-Uploaders: Dylan R. E. Moonfire , Mirco Bauer
, Jo Shields
+Uploaders: Dylan R. E. Moonfire , Mirco Bauer
Build-Depends: debhelper (>= 7.0.50~),
po-debconf,
autotools-dev,
@@ -12,8 +12,8 @@
libnunit-cil-dev
Standards-Version: 3.9.1
Homepage: http://www.mono-project.com/ASP.NET
-Vcs-Git: git://git.debian.org/git/pkg-mono/packages/xsp.git
-Vcs-Browser: http://git.debian.org/?p=pkg-mono/packages/xsp.git
+Vcs-Git: https://salsa.debian.org/dotnet-team/xsp.git
+Vcs-Browser: https://salsa.debian.org/dotnet-team/xsp
Package: dh-xsp
Architecture: all
@@ -35,7 +35,7 @@
Package: mono-xsp4
Architecture: all
-Depends: ${misc:Depends}, ${cli:Depends}, mono-xsp4-base (=
${source:Version}), procps, lsb-base
+Depends: ${misc:Depends}, ${cli:Depends}, mono-xsp4-base (=
${source:Version}), procps, perl
Description: simple web server to run ASP.NET 4.0 applications
XSP is a simple web server written in C# that can be used to run your
ASP.NET 4.0 applications.
Processed: Re: mpi4py fails test_dynproc.TestDPM.testJoin: socket.gaierror: [Errno -2] Name or service not known
Processing control commands: > severity 1052748 important Bug #1052748 [src:mpi4py] mpi4py fails test_dynproc.TestDPM.testJoin: socket.gaierror: [Errno -2] Name or service not known Severity set to 'important' from 'serious' > tags 1052748 moreinfo Bug #1052748 [src:mpi4py] mpi4py fails test_dynproc.TestDPM.testJoin: socket.gaierror: [Errno -2] Name or service not known Added tag(s) moreinfo. -- 1052748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052748: mpi4py fails test_dynproc.TestDPM.testJoin: socket.gaierror: [Errno -2] Name or service not known
Source: mpi4py Followup-For: Bug #1052748 Control: severity 1052748 important Control: tags 1052748 moreinfo I can't reproduce this error, and debci tests at https://ci.debian.net/packages/m/mpi4py/ continue to pass So I'm downgrading severity. I figure there are two possibilities - it was a transitory error related to some other library transition - or it's triggered by the network configuration on your test system. For instance, https://github.com/mpi4py/mpi4py/issues/240 was triggered by a network configured with IPV6 only. But that issue should be resolved already in mpi4py 3.1.4 Your test log shows your network accesses http://127.0.0.1:12990 so it is using IPv4. Can you reproduce the testJoin error?
Processed: mpi4py fails test_dynproc.TestDPM.testJoin: socket.gaierror: [Errno -2] Name or service not known
Processing control commands: > retitle 1052748 mpi4py fails test_dynproc.TestDPM.testJoin: socket.gaierror: > [Errno -2] Name or service not known Bug #1052748 [src:mpi4py] mpi4py: FTBFS: ld: cannot find -llmpe: No such file or directory Changed Bug title to 'mpi4py fails test_dynproc.TestDPM.testJoin: socket.gaierror: [Errno -2] Name or service not known' from 'mpi4py: FTBFS: ld: cannot find -llmpe: No such file or directory'. -- 1052748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052748: mpi4py fails test_dynproc.TestDPM.testJoin: socket.gaierror: [Errno -2] Name or service not known
Source: mpi4py Followup-For: Bug #1052748 Control: retitle 1052748 mpi4py fails test_dynproc.TestDPM.testJoin: socket.gaierror: [Errno -2] Name or service not known The failure was incorrectly identified. The build log says the problem was in testJoin: ERROR: testJoin (test_dynproc.TestDPM.testJoin) -- Traceback (most recent call last): File "/<>/test/test_dynproc.py", line 172, in testJoin addresses = socket.getaddrinfo(host, None, 0, socket.SOCK_STREAM) ^ File "/usr/lib/python3.11/socket.py", line 962, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): ^^^ socket.gaierror: [Errno -2] Name or service not known Likely it is related to https://github.com/mpi4py/mpi4py/issues/240 concerning running the test in ipv6 networks.
Bug#1052533: marked as done (llvm-17-dev: cmake config unusable due to missing files)
Your message dated Thu, 28 Sep 2023 10:53:04 + with message-id and subject line Bug#1052533: fixed in llvm-toolchain-17 1:17.0.1-1~exp2 has caused the Debian Bug report #1052533, regarding llvm-17-dev: cmake config unusable due to missing files 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.) -- 1052533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: llvm-17-dev Version: 1:17.0.1-1~exp1 Severity: serious the following minimized CMakeLists.txt cmake_minimum_required(VERSION 3.13.4) project(LLVM_SPIRV VERSION 17 LANGUAGES CXX C) find_package(LLVM 17 REQUIRED) fails with this error: -- Could NOT find LibEdit (missing: LibEdit_INCLUDE_DIRS LibEdit_LIBRARIES) -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) -- Could NOT find zstd (missing: zstd_LIBRARY zstd_INCLUDE_DIR) -- Could NOT find CURL (missing: CURL_LIBRARY CURL_INCLUDE_DIR) CMake Error at /usr/lib/llvm-17/lib/cmake/llvm/LLVMExports.cmake:1857 (message): The imported target "omp" references the file "/usr/lib/llvm-17/lib/libomp.so.5" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/llvm-17/lib/cmake/llvm/LLVMExports.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib/llvm-17/cmake/LLVMConfig.cmake:369 (include) CMakeLists.txt:3 (find_package) -- Configuring incomplete, errors occurred! (found while preparing spirv-llvm-translator-17) Andreas --- End Message --- --- Begin Message --- Source: llvm-toolchain-17 Source-Version: 1:17.0.1-1~exp2 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of llvm-toolchain-17, 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. Gianfranco Costamagna (supplier of updated llvm-toolchain-17 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: Thu, 28 Sep 2023 11:24:39 +0200 Source: llvm-toolchain-17 Built-For-Profiles: noudeb Architecture: source Version: 1:17.0.1-1~exp2 Distribution: experimental Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Gianfranco Costamagna Closes: 1052533 Changes: llvm-toolchain-17 (1:17.0.1-1~exp2) experimental; urgency=medium . * Also remove omp from cmake file (Closes: #1052533) Checksums-Sha1: 4d9ff117f1972d52388dcee6dc1dbb8383c812c0 7931 llvm-toolchain-17_17.0.1-1~exp2.dsc 74edd3e3fec70b0b51d2190040d9b4333a3079b3 168164 llvm-toolchain-17_17.0.1-1~exp2.debian.tar.xz 9be69d5d656fea797626be05f085d8da8f532fd2 12522 llvm-toolchain-17_17.0.1-1~exp2_source.buildinfo Checksums-Sha256: e2c90d9b62572a32812d9109931140ce38f01db8024733c9323775d2a0304b86 7931 llvm-toolchain-17_17.0.1-1~exp2.dsc 934beb3beb6ce391a28353daed9766af10fbc4483ddaa0d7a93ee716a1c4ac56 168164 llvm-toolchain-17_17.0.1-1~exp2.debian.tar.xz 0e3f0ae09f9fc6a034f92fe3c66597cb851b85d6ce35376d064f6f0cbc69e741 12522 llvm-toolchain-17_17.0.1-1~exp2_source.buildinfo Files: 856d46121c5939cb7415c659cb5d44f1 7931 devel optional llvm-toolchain-17_17.0.1-1~exp2.dsc fd1f5ffbb58cc519839de420eac8100d 168164 devel optional llvm-toolchain-17_17.0.1-1~exp2.debian.tar.xz f1af0d55fbdd41fbf10536a147435103 12522 devel optional llvm-toolchain-17_17.0.1-1~exp2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmUVRqQACgkQ808JdE6f XdmACBAAqDvsMM3YtYdrMfDAzbx6CbxxoWQtprvCC+QzGrzF8PqSd5/nqrhqx/dL BW3TsuDSfl50sDZPnn3lcF95qHjkMKwqW9fTsx80DLL+Ywti7Bx9psKYX5DgBdf9 M57MAdmHA/aL7n+Z5xp+qTPHH/c2a+JZ68fVMYQmb+5PPSWSck/2f3yP0wu9GkWw 8UmfyO6P/gNId/ZRMn8/PVq7kl27K3JQF0YfPDO98lK6wQK3vbU+ME87AN4zOdI8 ntc/TWa0vGLlJTZ4/ZBsYuXdbHhC3jOmRxKPvPwoDSbtnpjhV+N7mSFyqef6KleB KEaA/79jMBxs19Ai9xJtxZ1zCJwEVA0WW43yJGEZc8dMzxm2E2MfgKEo2yRVrpRw e8yqcWKpz7+ey1nDYXN4DNGubsB9w/2bjrm0bzG/wVJL0lFGyfg/WNgamza2urXU
Processed: Re: xsp: ships sysv-init script without systemd unit
Processing control commands: > severity -1 important Bug #1039427 [xsp] xsp: ships sysv-init script without systemd unit Severity set to 'important' from 'grave' -- 1039427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039427 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1039427: xsp: ships sysv-init script without systemd unit
Control: severity -1 important I have filed a serious bug for the underlying issue. Please ignore my comments for this bug.
Bug#1053154: mono-xsp4: needs perl dependency for postinst
Package: mono-xsp4 Version: 4.2-2.4 Severity: serious The package does not install because postinst triggers mono-xsp4-update, which needs MD5.pm. The package has to depend on perl.
Bug#1043131: hcrypto: rename abort to _afscrypto_abort
> https://git.openafs.org/?p=openafs.git;a=commit;h=c4c1689 That by itself is not enough it seems: CC [M] /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.o /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.c:250:10: error: ‘struct ctl_table’ has no member named ‘child’ 250 | .child = afs_sysctl_table | ^ /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.c:250:27: error: positional initialization of field in ‘struct’ declared with ‘designated_init’ attribute [-Werror=designated-init] 250 | .child = afs_sysctl_table | ^~~~ /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.c:250:27: note: (near initialization for ‘fs_sysctl_table[0]’) /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.c:250:27: error: incompatible types when initializing type ‘enum ’ using type ‘struct ctl_table *’ /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.c: In function ‘osi_sysctl_init’: /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.c:263:18: error: implicit declaration of function ‘register_sysctl_table’; did you mean ‘unregister_sysctl_table’? [-Werror=implicit-function-declaration] 263 | afs_sysctl = register_sysctl_table(fs_sysctl_table, 0); | ^ | unregister_sysctl_table /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.c:263:16: warning: assignment to ‘struct ctl_table_header *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 263 | afs_sysctl = register_sysctl_table(fs_sysctl_table, 0); |^ cc1: some warnings being treated as errors make[5]: *** [/usr/src/linux-headers-6.5.0-1-common/scripts/Makefile.build:248: /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP/osi_sysctl.o] Error 1 make[4]: *** [/usr/src/linux-headers-6.5.0-1-common/Makefile:2057: /var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP] Error 2 make[3]: *** [/usr/src/linux-headers-6.5.0-1-common/Makefile:246: __sub-make] Error 2 make[3]: Leaving directory '/usr/src/linux-headers-6.5.0-1-amd64' FAILURE: make exit code 2 make[2]: *** [Makefile.afs:283: openafs.ko] Error 1 make[2]: Leaving directory '/var/lib/dkms/openafs/1.8.10/build/src/libafs/MODLOAD-6.5.0-1-amd64-SP' make[1]: *** [Makefile:188: linux_compdirs] Error 2 make[1]: Leaving directory '/var/lib/dkms/openafs/1.8.10/build/src/libafs' make: *** [Makefile:15: all] Error 2 Upstream commit fb31d299e6caa015f6288ba9186da6277d3d6a8d seems related, will have to test. pgpuvuYjDoEze.pgp Description: OpenPGP digital signature
Processed: reassign 1053098 to src:unadf, forcibly merging 838248 1053098, reopening 838248
Processing commands for cont...@bugs.debian.org: > reassign 1053098 src:unadf Bug #1053098 [unadf] unadf 0.7.11a-5 calls system() with unsanitized input Bug reassigned from package 'unadf' to 'src:unadf'. Ignoring request to alter found versions of bug #1053098 to the same values previously set Ignoring request to alter fixed versions of bug #1053098 to the same values previously set > forcemerge 838248 1053098 Bug #838248 [src:unadf] unadf: CVE-2016-1243 and CVE-2016-1244 Bug #1053098 [src:unadf] unadf 0.7.11a-5 calls system() with unsanitized input Marked as fixed in versions unadf/0.7.11a-3+deb8u1. Marked as found in versions unadf/0.7.11a-3 and unadf/0.7.11a-4. Added tag(s) patch. Merged 838248 1053098 > reopen 838248 Bug #838248 [src:unadf] unadf: CVE-2016-1243 and CVE-2016-1244 Bug #1053098 [src:unadf] unadf 0.7.11a-5 calls system() with unsanitized input Bug 838248 is not marked as done; doing nothing. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053098 838248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfixed 838248 in 0.7.11a-4, found 838248 in 0.7.11a-4
Processing commands for cont...@bugs.debian.org: > notfixed 838248 0.7.11a-4 Bug #838248 [src:unadf] unadf: CVE-2016-1243 and CVE-2016-1244 Bug #1053098 [src:unadf] unadf 0.7.11a-5 calls system() with unsanitized input Ignoring request to alter fixed versions of bug #838248 to the same values previously set Ignoring request to alter fixed versions of bug #1053098 to the same values previously set > found 838248 0.7.11a-4 Bug #838248 [src:unadf] unadf: CVE-2016-1243 and CVE-2016-1244 Bug #1053098 [src:unadf] unadf 0.7.11a-5 calls system() with unsanitized input Ignoring request to alter found versions of bug #838248 to the same values previously set Ignoring request to alter found versions of bug #1053098 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1053098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053098 838248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053098: unadf 0.7.11a-5 calls system() with unsanitized input
Hi,
On Wed, Sep 27, 2023 at 01:19:31PM +0300, Jani Nikula wrote:
> Package: unadf
> Version: 0.7.11a-5
> Severity: grave
> Tags: security
> Justification: user security hole
> X-Debbugs-Cc: Debian Security Team
>
> Dear Maintainer,
>
> See upstream ADFLib commit 8e973d7b8945 ("Fix unsafe extraction by using
> mkdir() instead of shell command") [1].
>
> 'unadf' passes the directory names within an ADF to system()
> unsanitized. In the most benign failure case, directory names beginning
> with '-' are interpreted as options to mkdir, and unpacking the ADF
> fails.
>
> Please update unadf to fixed upstream version.
>
> [1]
> https://github.com/lclevy/ADFlib/commit/8e973d7b894552c3a3de0ccd2d1e9cb0b8e618dd
Those are CVE-2016-1243 and CVE-2016-1244 and it looks that the
unstable upload back then, which was aiming to fix the issue,
0.7.11a-4, did not include the patch and so the issue remained unfixed
for all subsequent releases.
I'm merging this back to 838248 and updating the metadata.
Regards,
Salvatore
Processed: found 838248 in 0.7.11a-4
Processing commands for cont...@bugs.debian.org:
> found 838248 0.7.11a-4
Bug #838248 {Done: Luciano Bello } [src:unadf] unadf:
CVE-2016-1243 and CVE-2016-1244
Marked as found in versions unadf/0.7.11a-4; no longer marked as fixed in
versions unadf/0.7.11a-4 and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
838248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): unarchiving 838248, notfound 1053098 in 0.7.11a-5, forcibly merging 838248 1053098
Processing commands for cont...@bugs.debian.org:
> unarchive 838248
Bug #838248 {Done: Luciano Bello } [src:unadf] unadf:
CVE-2016-1243 and CVE-2016-1244
Unarchived Bug 838248
> notfound 1053098 0.7.11a-5
Bug #1053098 [unadf] unadf 0.7.11a-5 calls system() with unsanitized input
No longer marked as found in versions unadf/0.7.11a-5.
> forcemerge 838248 1053098
Bug #838248 {Done: Luciano Bello } [src:unadf] unadf:
CVE-2016-1243 and CVE-2016-1244
Unable to merge bugs because:
package of #1053098 is 'unadf' not 'src:unadf'
Failed to forcibly merge 838248: Did not alter merged bugs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1053098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053098
838248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1053098
Processing commands for cont...@bugs.debian.org: > tags 1053098 + upstream Bug #1053098 [unadf] unadf 0.7.11a-5 calls system() with unsanitized input Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#988462: marked as done (trac: not ready for Debian 12)
Your message dated Thu, 28 Sep 2023 08:35:27 + with message-id and subject line Bug#988462: fixed in trac 1.6-1 has caused the Debian Bug report #988462, regarding trac: not ready for Debian 12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 988462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: trac Version: 1.5.2+dfsg-2 Severity: serious IMHO, the current version of Trac is not suitable for including it in a stable release. I'll try to provide backports of future version 1.6.x for Debian 11. --- End Message --- --- Begin Message --- Source: trac Source-Version: 1.6-1 Done: Martin We believe that the bug you reported is fixed in the latest version of trac, 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 988...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin (supplier of updated trac 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, 28 Sep 2023 07:45:26 + Source: trac Architecture: source Version: 1.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Martin Closes: 988462 Changes: trac (1.6-1) unstable; urgency=medium . * New upstream version (Closes: #988462) Checksums-Sha1: 0368a4dc549451a54141298d1e3a60aa40b9b7ff 2106 trac_1.6-1.dsc 37f910e4e8a936a5349f45fcc94a58cbe4ec056a 2466176 trac_1.6.orig.tar.xz e008ec410cbad3bbe18cc851d24f61d16fc6d70d 18404 trac_1.6-1.debian.tar.xz ad148015b80187b1323085664bb74ff3cbc538dc 8397 trac_1.6-1_amd64.buildinfo Checksums-Sha256: 7e3427de322242c4660783b7f598f35a71d109725cc423135bf16843b5c5d5e5 2106 trac_1.6-1.dsc 79ca328f1061510e62c3c4d03fb141a99294829658fe98011cf27e70a3996a6d 2466176 trac_1.6.orig.tar.xz 9f148c9b375134dbb195a419e7a92f64ee04c5a8a8427c6a03fd6632c2ec8266 18404 trac_1.6-1.debian.tar.xz 29d8b1eb9941231e2c44826d8564045fdf8dd26d5c768bffdeb269a4e833c993 8397 trac_1.6-1_amd64.buildinfo Files: 8ec5905968d12c544b6f2e6902c27ab1 2106 web optional trac_1.6-1.dsc a1ffc52d9f036aa0bfe275a65c293662 2466176 web optional trac_1.6.orig.tar.xz 159026f57d86c58683bc4eb4e34e7a74 18404 web optional trac_1.6-1.debian.tar.xz e7235f19fdfc760960e6ea507dce033b 8397 web optional trac_1.6-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAmUVMegACgkQ4+Chwoa5 Y+qvcg//b7LgLRH4k1SS/coUwNm5U3eg2yQwG1NBuCVR2SVRtUHFN3Wbg2V7VS8D xlNUS3PjrBPnnbH4CRxWkyfQaWmMbKkS5L1E6JXW8QMkl3EflPx2pvO0QZXWVYFM bXLilp2FDnoGIf7tE5L4X1wWcOYjY017NroYljg38lyr+B54LsL8f5vD0SMM/z7K yeq4lsoXlSjVYqNZ7Q0AGQxGHI2tyS/yLEcn6Hv3NVcvNvTjHPKyltzncgE4BP5b n9SxWwIEY1sUwLFijnsicNQQ8bhpM7Hh7ayoDbnvjkDiEXsNfyeyULSvM1MH4PYX TObZktYcIPVV7of4UcatEJeIJlhvFm3QIi+CaWXLGkhcSO1WEkg1jz4+cranBytw V0etSgtpiQGzYnGNIFltRp0xDMlqNBrAZ007gzNNvPLPsPMVs7rgVIGKoHAn629i mRefp3YsQYD9Vbb/Y/IJxU0za6NSYvQ00KVoNkcvTIKzusVItf/NTKCGFxvjq2Mx hFgT+KxTtyW57J5jgWE93gjf4wARSI7KSHnVqLohMkpiHVgKk+lPRYmz5Fx8RUmf ZNrvDgBCPH2klyd4Az2s7ew5t0nRrh3v1vWUuoD436rKnXzo9y1re49x42O7H3vm +pKIvGRIrhQ3l0OOSB5C9JCBv6og3RXu7pHskEVRTT6mM9cavDQ= =yQrZ -END PGP SIGNATURE End Message ---
Bug#1053145: src:happy: fails to migrate to testing for too long: stuck in haskell transition
Source: happy Version: 1.20.0-1 Severity: serious Control: close -1 1.20.1.1-1 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:happy has been trying to migrate for 32 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=happy OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:happy: fails to migrate to testing for too long: stuck in haskell transition
Processing control commands: > close -1 1.20.1.1-1 Bug #1053145 [src:happy] src:happy: fails to migrate to testing for too long: stuck in haskell transition Marked as fixed in versions happy/1.20.1.1-1. Bug #1053145 [src:happy] src:happy: fails to migrate to testing for too long: stuck in haskell transition Marked Bug as done -- 1053145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:magic-haskell: fails to migrate to testing for too long: stuck in haskell transition
Processing control commands: > close -1 1.1-11 Bug #1053144 [src:magic-haskell] src:magic-haskell: fails to migrate to testing for too long: stuck in haskell transition Marked as fixed in versions magic-haskell/1.1-11. Bug #1053144 [src:magic-haskell] src:magic-haskell: fails to migrate to testing for too long: stuck in haskell transition Marked Bug as done -- 1053144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053144: src:magic-haskell: fails to migrate to testing for too long: stuck in haskell transition
Source: magic-haskell Version: 1.1-10 Severity: serious Control: close -1 1.1-11 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:magic-haskell has been trying to migrate for 32 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=magic-haskell OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#919035: elpa-persp-projectile: broken with recent elpa-perspective
Manphiz writes: > control: tags -1 patch > > I have prepared a merge request[1] as a fix. PTAL. > > [1] elpa-persp-projectile: broken with recent elpa-perspective Turned out I didn't paste the URL, silly me. Here it is: [1] https://salsa.debian.org/emacsen-team/persp-projectile/-/merge_requests/3 -- Manphiz
