Bug#1041128: marked as done (qcodeeditor FTBFS with googletest 1.13.0)
Your message dated Sun, 27 Aug 2023 04:18:53 + with message-id and subject line Bug#1041128: fixed in qcodeeditor 1.0+1gitdc644d-2 has caused the Debian Bug report #1041128, regarding qcodeeditor FTBFS with googletest 1.13.0 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.) -- 1041128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qcodeeditor Version: 1.0+1gitdc644d-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qcodeeditor.html ... In file included from /usr/include/c++/13/type_traits:35, from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:45, from /usr/include/x86_64-linux-gnu/qt5/QtGui/qtguiglobal.h:43, from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qtwidgetsglobal.h:43, from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:43, from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1, from /build/1st/qcodeeditor-1.0+1gitdc644d/include/internal/QLineNumberArea.hpp:4, from /build/1st/qcodeeditor-1.0+1gitdc644d/include/QLineNumberArea:3, from /build/1st/qcodeeditor-1.0+1gitdc644d/src/internal/QCodeEditor.cpp:2: /usr/include/c++/13/bits/c++0x_warning.h:32:2: error: #error This file requires compiler and library support for the ISO C++ 2011 standard. This support must be enabled with the -std=c++11 or -std=gnu++11 compiler options. 32 | #error This file requires compiler and library support \ | ^ ... --- End Message --- --- Begin Message --- Source: qcodeeditor Source-Version: 1.0+1gitdc644d-2 Done: Dima Kogan We believe that the bug you reported is fixed in the latest version of qcodeeditor, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dima Kogan (supplier of updated qcodeeditor package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 26 Aug 2023 20:47:59 -0700 Source: qcodeeditor Architecture: source Version: 1.0+1gitdc644d-2 Distribution: unstable Urgency: medium Maintainer: Dima Kogan Changed-By: Dima Kogan Closes: 1041128 Changes: qcodeeditor (1.0+1gitdc644d-2) unstable; urgency=medium . * Building without -ansi (Closes: #1041128) Checksums-Sha1: c57a04c0239efa78a0a9b294e0dc305ab788dd2c 2015 qcodeeditor_1.0+1gitdc644d-2.dsc b046b3438a8bdbf8db3a56d2f708dbb4a369f3ee 3572 qcodeeditor_1.0+1gitdc644d-2.debian.tar.xz 632e9ccf62df452dcfe9bdefd26730757584bc16 12115 qcodeeditor_1.0+1gitdc644d-2_amd64.buildinfo Checksums-Sha256: 4cb93c38156b0baaaf791b9f8bfbaedf0107fd99061a9b5470b9c93fdef48024 2015 qcodeeditor_1.0+1gitdc644d-2.dsc 73f759ade8cdee416131bcbade6addc4f78f33ee308bf0e4d44d6dd1248b3be1 3572 qcodeeditor_1.0+1gitdc644d-2.debian.tar.xz b5ce097522403bc93a5de27371db811d6afe6d390242b267ccafa6f0aff7ceb3 12115 qcodeeditor_1.0+1gitdc644d-2_amd64.buildinfo Files: 96e098f583a52cebbc41892240a4b9ff 2015 libdevel optional qcodeeditor_1.0+1gitdc644d-2.dsc 994b5a39b5c60a74fc65d165922e0c26 3572 libdevel optional qcodeeditor_1.0+1gitdc644d-2.debian.tar.xz 6ab9f43ed9c9a2ec4ba363426c976411 12115 libdevel optional qcodeeditor_1.0+1gitdc644d-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEteL6GQ/fmv4hiInPrMfCzzCUEYgFAmTqyDoACgkQrMfCzzCU EYj3Cw//eLy4nWej8tksRh7fXMAqYv9pzZx5r0KmLuN549GshuO3iJ6i5i0UxXMm 94hvxOYCbOsvg3qOr2TpYBQXPFsvCSLR6lsgPOPIOUFBsU0A0P5WSqANs/Hm4sGI 9C901HnkOUOWlWJ76esW9MDjV8ollOQSFcUC5QQRTPl92wLsUh0mDEesbnkT9Kis GjkioSPK9Iq0pgJ9rM4ReoNjjDF6IoaihuRRdXsoo1GldKLAt5MPENjyAqExwpDm 521Cmn0vvIyp4dHIvoeoxAIb7QHH2tXDnhtpkKhW/msMCGgvGK2zAXzgWkoHo9LU BSx8bTJOBEy57bMWMcmEy4vBM+pAgD6GampTOvmTowLbkGgPfQqRResA3LN1RfDj 21qiHrprQu10cCAOmxi8FAWD7bikMynW3yR4pR1NV4hYYRQu3zHw4xQuILeaBm3u /KEFfiRCsxYydHSpxukcHKXyla2BeQqvk1i0/a4ntaFtktDq9Q/WM1KGy5HItjMA mQgMWy7/K0S4EX3ks9jPl0lB09dLcGafG2LZTbHBjDpIr+hLtLVv7bznIpQk2SD4 HQx0vW7YIakGWactmKzEmGT93Y/H176XNCwoCm1JBu06mr6YD3IfUCsAzyG1YPTf
Bug#1041090: marked as done (valijson FTBFS with googletest 1.13.0)
Your message dated Sun, 27 Aug 2023 03:18:58 + with message-id and subject line Bug#1041090: fixed in valijson 1.0+repack-3 has caused the Debian Bug report #1041090, regarding valijson FTBFS with googletest 1.13.0 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.) -- 1041090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: valijson Version: 1.0+repack-2 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/valijson.html ... In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from /build/1st/valijson-1.0+repack/tests/test_fetch_absolute_uri_document_callback.cpp:2: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing the two -std=c++11 to -std=c++14 in CMakeLists.txt --- End Message --- --- Begin Message --- Source: valijson Source-Version: 1.0+repack-3 Done: Dima Kogan We believe that the bug you reported is fixed in the latest version of valijson, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dima Kogan (supplier of updated valijson package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 26 Aug 2023 19:55:31 -0700 Source: valijson Architecture: source Version: 1.0+repack-3 Distribution: unstable Urgency: medium Maintainer: Dima Kogan Changed-By: Dima Kogan Closes: 1041090 Changes: valijson (1.0+repack-3) unstable; urgency=medium . * Build with g++-14 (Closes: #1041090) Checksums-Sha1: c92edb37fb9bebcd91fba9bc5505708cbd225a79 2031 valijson_1.0+repack-3.dsc 4cc0354bb7b825e01fcd455c246a0dbbe755a620 6864 valijson_1.0+repack-3.debian.tar.xz a475c3220b55fe67986f27a5f8d94de3405559de 13245 valijson_1.0+repack-3_amd64.buildinfo Checksums-Sha256: 402845b7804a09588ce7b5f1121a633d7098d628bffdbfa06e5e7319e771fb91 2031 valijson_1.0+repack-3.dsc 50972b38e35e8fc047213a263408bac67f609ea50c9ca32d6c786f9cc7416df2 6864 valijson_1.0+repack-3.debian.tar.xz 09fd0309b519a95a215d3db55f7294cf4cf582b30c6296fefa1e37b805e12bea 13245 valijson_1.0+repack-3_amd64.buildinfo Files: 12e69945841da2da980afb64d7d3406d 2031 libdevel optional valijson_1.0+repack-3.dsc 657cab35b8280e3f410d104a7897a446 6864 libdevel optional valijson_1.0+repack-3.debian.tar.xz 16234cc807072bd60cb7bc3e6cc4 13245 libdevel optional valijson_1.0+repack-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEteL6GQ/fmv4hiInPrMfCzzCUEYgFAmTqvDAACgkQrMfCzzCU EYgM4Q//RUMYBGVmDXpn4KKQMx8rfqu3FPxbk1tFa9rbs2iKdRXPzcYWoQvp+rAn DFvwmQRzCLIo9xxH6fZVrVs2QBfZHVbKiLVD8XdZOX6A2zOHIAJFoyG2skVfpWEQ ErHiODmFUrsbBESeWemNj8L3wKrE5M20jXlN6lDWzS4X9Cfp2zziy9oC2uE2Im4h eIGOk4hIAR1WEuA0G3eZ8Z7EnT3+Y2zs542ruUyyrLsQpt01Cb6Ixpuhb4yEbhGM d6VLmmCT82yaocAxm+XLMH9FTYFV6GbigppHXQgztpqT7fKbg/oR6CYWJ97QNrR0 YN9l0DbVmDcSuoUb5s0d+ETI2yimCJNTe2wXYqdFc3XMjzUgnALbB+P0sIYuo6eV kBahJlKa6Pf5asirwD1Ea8AaN1KAmoVujoq71wemD7kDtteOu2PydXOkSWC/KH67 z45GCIxeGGurvB4nNlnUddobh4B2n7NetluD40XPM/yYquR/mvljSJHEblIJm28N BE9uqNhQ/ax9Hsj1qQHCL+yn+pcYluTroyyQER2sHKuJK3lG2Gh25u651u1I9J+H Xo2zyXn/0rPaTco9za89PA/ixznaFh8pyzfcrTiiy9EGwvol1Ws7H0jfK0bQmnLf 2GaCPFNtxZfcKZWcWvbJo7XOMiTooccz69y+EcMPth83XJYg+pY= =dgbU -END PGP SIGNATURE End Message ---
Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed
On Aug 26, Jon Westgate <0...@fsck.tv> wrote: > The error message it gave was "decompresson failed with status 6" Status 6 is XZ_OPTIONS_ERROR, which means "Input was encoded with settings that are not supported by this XZ decoder". So it looks like you have compressed the modules (how?) with XZ settings which are supported by the userspace loader but not by the kernel one. -- ciao, Marco signature.asc Description: PGP signature
Bug#1050607: xcb: bookworm xcb won't paste from selected cut buffer
Package: xcb Version: 2.4-8 Severity: grave Justification: renders package unusable Dear Maintainer, With standard bookworm Gnome desktop... [farlap.949] $ whence xcb 'xcb -n 33 -l v -geometry -0+0' [farlap.950] $ which xcb /bin/xcb [farlap.951] $ strings /bin/xcb | grep "^lib" libXaw.so.7 libXt.so.6 libX11.so.6 libc.so.6 1. Cut something and paste into first cut buffer. 2. Cut something different and paste into second cut buffer. 3. Single click on FIRST cut buffer box. Paste anywhere. 4. What gets pasted is the contents of the SECOND cut buffer. This bug renders xcb pretty much useless. I found the source for an old version of xcb in my archives. It's xcb-2.4 with PATCHLEVEL: 3. I compiled it from source, and tested. I got the same problem. -- 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.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xcb depends on: ii libc6 2.36-9+deb12u1 ii libx11-6 2:1.8.4-2+deb12u1 ii libxaw7 2:1.0.14-1 ii libxt61:1.2.1-1.1 xcb recommends no packages. xcb suggests no packages. -- no debconf information
Bug#1050526: marked as done (dask: autopkgtest regression on s390x)
Your message dated Sat, 26 Aug 2023 23:18:56 + with message-id and subject line Bug#1050526: fixed in dask 2023.8.0+dfsg-2 has caused the Debian Bug report #1050526, regarding dask: autopkgtest regression on s390x 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.) -- 1050526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dask Version: 2023.8.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of dask the autopkgtest of dask fails in testing on s390x when that autopkgtest is run with the binary packages of dask from unstable. It passes when run with only packages from testing. In tabular form: passfail dask from testing2023.8.0+dfsg-1 all others from testingfrom testing I copied some of the output at the bottom of this report. I note that s390x is our only big endian release architecture. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul PS: the tests on armhf and i386 architectures regressed too about 8 months ago on what seems to be an 32 bit arch test problem [1] https://qa.debian.org/excuses.php?package=dask https://ci.debian.net/data/autopkgtest/testing/s390x/d/dask/37104621/log.gz 700s === FAILURES === 700s test_with_spec_integer_method _ 700s 700s def test_with_spec_integer_method(): 700s from dask.dataframe.io.demo import ColumnSpec, DatasetSpec, with_spec 700s 700s spec = DatasetSpec( 700s npartitions=1, 700s nrecords=5, 700s column_specs=[ 700s ColumnSpec(prefix="pois", dtype=int, method="poisson"), 700s ColumnSpec(prefix="norm", dtype=int, method="normal"), 700s ColumnSpec(prefix="unif", dtype=int, method="uniform"), 700s ColumnSpec(prefix="binom", dtype=int, method="binomial", args=(100, 0.4)), 700s ColumnSpec(prefix="choice", dtype=int, method="choice", args=(10,)), 700s ColumnSpec(prefix="rand", dtype=int, random=True, low=0, high=10), 700s ColumnSpec(prefix="rand", dtype=int, random=True), 700s ], 700s ) 700s ddf = with_spec(spec, seed=42) 700s res = ddf.compute() 700s > assert res["pois1"].tolist() == [1002, 985, 947, 1003, 1017] 700s E assert [1021, 1006, 1024, 1030, 930] == [1002, 985, 947, 1003, 1017] 700s E At index 0 diff: 1021 != 1002 700s E Full diff: 700s E - [1002, 985, 947, 1003, 1017] 700s E + [1021, 1006, 1024, 1030, 930] 700s 700s /usr/lib/python3/dist-packages/dask/dataframe/io/tests/test_demo.py:338: AssertionError OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: dask Source-Version: 2023.8.0+dfsg-2 Done: Diane Trout We believe that the bug you reported is fixed in the latest version of dask, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Diane Trout (supplier of updated dask 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: Fri, 25 Aug 2023 21:22:33 -0700 Source: dask Architecture: source Version: 2023.8.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Diane Trout Closes: 1050526 Changes: dask (2023.8.0+dfsg-2) unstable; urgency=medium . * Add force-little-endian-random.patch to try and initialize random number generator on s380x the same as on x86_64 (Closes: #1050526) * Depend on dask-sphinx-theme 3.0.5-2 to avoid accidentally including googletagmanager in the
Processed: bug 1050526 is forwarded to https://github.com/dask/dask/issues/10423
Processing commands for cont...@bugs.debian.org: > forwarded 1050526 https://github.com/dask/dask/issues/10423 Bug #1050526 [src:dask] dask: autopkgtest regression on s390x Set Bug forwarded-to-address to 'https://github.com/dask/dask/issues/10423'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1050526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1050526 marked as pending in dask
Processing control commands: > tag -1 pending Bug #1050526 [src:dask] dask: autopkgtest regression on s390x Added tag(s) pending. -- 1050526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050526: marked as pending in dask
Control: tag -1 pending Hello, Bug #1050526 in dask reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/dask/-/commit/08ffea1b7b53e9c71c9a926d5786288c2e6c1b5b Add force-little-endian-random.patch to try and initialize random number generator on s380x with the same values as on x86_64 (Closes: #1050526) (this message was generated automatically) -- Greetings https://bugs.debian.org/1050526
Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed
Dear Marco, I'm using XZ if I turn off compression my initrd fails it's too big. Jon On 26/08/2023 22:25, Marco d'Itri wrote: On Aug 26, Jon Westgate wrote: Yes I am using compressed modules And are these modules compressed with xz or something else? This new code was introduced in the latest snapshot, and apparently it fails when used with kernels with compressed modules support enabled (which so far is not the default for Debian kenrels). OpenPGP_0x420652A8C309A3B2.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1050606: find: ‘/lib/systemd/system-sleep’: No such file or directory
Package: cryptsetup-suspend Version: 2:2.6.1-4 Severity: serious The cryptsetup-suspend wrapper makes unconditional use of the /lib/systemd/system-sleep directory. This directory was removed from the systemd package as a result of the discussion in https://salsa.debian.org/systemd-team/systemd/-/merge_requests/208 The failing autopkgtest of cryptsetup is now blocking the testing migration of the systemd package (thus the RC severity). Please update cryptsetup-suspend-wrapper to handle the case where the directory /lib/systemd/system-sleep is missing. Regards, Michael
Bug#1050605: linux-image-6.4.0-3-amd64: Unable to boot on 2009 13inch MacBook Pro
Package: src:linux Version: 6.4.11-1 Severity: grave Justification: renders package unusable The recent update of linux-image to version 6.4.0-3 causes this laptop unable to boot. As the boot was not successful I could not check the log through dmesg so I will attach a photo later. The relevant part of the error of the end of the boot messages when trying to boot in recovery mode is hand-typed below: , | [3.453462] ACPI Warning: \_SB.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20230331/nsarguments-61) | [3.454515] ACPI: \_SB_.PCI0.IXVE.IGPU: failed to evaluate _DSM | [3.455576] nouveau :02:00.0: enabling device (0002 -> 0003) | [3.456812] ACPI: \_SB_.PCI0.LGPU: Enabled at IRQ 18 ` After this the boot process stuck like when trying to boot normally. Using linux-image-6.4.0-2-amd64 and early kernel versions the laptop can boot without issues. I saw there is #1050460 reporting a similar error error on nVidia GPU but as my laptop cannot even boot I figured it may be better to file a separate bug and let the maintainer to decide whether to merge the bugs. Note that the system info is generated when booted with a 6.4.0-2 kernel. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Apple Inc. product_name: MacBookPro5,5 product_version: 1.0 chassis_vendor: Apple Inc. chassis_version: Mac-F2268AC8 bios_vendor: Apple Inc. bios_version:MBP55.88Z.00AC.B03.0906151708 board_vendor: Apple Inc. board_name: Mac-F2268AC8 board_version: ** PCI devices: 00:00.0 Host bridge [0600]: NVIDIA Corporation MCP79 Host Bridge [10de:0a82] (rev b1) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: nForce2_smbus Kernel modules: i2c_nforce2, nv_tco 00:03.3 RAM memory [0500]: NVIDIA Corporation MCP79 Memory Controller [10de:0a89] (rev b1) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: ohci-pci Kernel modules: ohci_pci 00:04.1 USB controller [0c03]: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller [10de:0aa6] (rev b1) (prog-if 20 [EHCI]) Subsystem: NVIDIA Corporation Apple iMac 9,1 [10de:cb79] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:06.0 USB controller [0c03]: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller [10de:0aa7] (rev b1) (prog-if 10 [OHCI]) Subsystem: NVIDIA Corporation Apple iMac 9,1 [10de:cb79] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ohci-pci Kernel modules: ohci_pci 00:06.1 USB controller [0c03]: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller [10de:0aa9] (rev b1) (prog-if 20 [EHCI]) Subsystem: NVIDIA Corporation Apple iMac 9,1 [10de:cb79] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:08.0 Audio device [0403]: NVIDIA Corporation MCP79 High Definition Audio [10de:0ac0] (rev b1) Subsystem: NVIDIA Corporation Apple iMac 9,1 [10de:cb79] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:09.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Bridge [10de:0aab] (rev b1) (prog-if 01 [Subtractive decode]) Subsystem: NVIDIA Corporation Apple iMac 9,1 [10de:cb79] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr+ DiscTmrStat- DiscTmrSERREn- Capabilities: 00:0a.0 Ethernet controller [0200]: NVIDIA Corporation MCP79 Ethernet [10de:0ab0] (rev b1) Subsystem: NVIDIA Corporation Apple iMac 9,1 [10de:cb79] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF-
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> clone 1049983 -1
Bug #1049983 {Done: Shengjing Zhu } [syncthing] panic:
connection already exists
Bug 1049983 cloned as bug 1050603
> severity -1 normal
Bug #1050603 {Done: Shengjing Zhu } [syncthing] panic:
connection already exists
Severity set to 'normal' from 'grave'
> retitle -1 syncthing: Reenable QUIC feature
Bug #1050603 {Done: Shengjing Zhu } [syncthing] panic:
connection already exists
Changed Bug title to 'syncthing: Reenable QUIC feature' from 'panic: connection
already exists'.
> tag -1 upstream fixed-upstream
Bug #1050603 {Done: Shengjing Zhu } [syncthing] syncthing:
Reenable QUIC feature
Added tag(s) fixed-upstream and upstream.
> forwarded -1 https://github.com/syncthing/syncthing/pull/9040
Bug #1050603 {Done: Shengjing Zhu } [syncthing] syncthing:
Reenable QUIC feature
Set Bug forwarded-to-address to
'https://github.com/syncthing/syncthing/pull/9040'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1049983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049983
1050603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: retitle 1050582 to kmod is broken with custom kernels with CONFIG_MODULE_COMPRESS_*=y
Processing commands for cont...@bugs.debian.org: > retitle 1050582 kmod is broken with custom kernels with > CONFIG_MODULE_COMPRESS_*=y Bug #1050582 [kmod] kmod update corrupts systemd uefi boot Bug #1050586 [kmod] kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed Changed Bug title to 'kmod is broken with custom kernels with CONFIG_MODULE_COMPRESS_*=y' from 'kmod update corrupts systemd uefi boot'. Changed Bug title to 'kmod is broken with custom kernels with CONFIG_MODULE_COMPRESS_*=y' from 'kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1050582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050582 1050586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed
On Aug 26, Jon Westgate wrote: > Yes I am using compressed modules And are these modules compressed with xz or something else? This new code was introduced in the latest snapshot, and apparently it fails when used with kernels with compressed modules support enabled (which so far is not the default for Debian kenrels). -- ciao, Marco signature.asc Description: PGP signature
Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed
Yes I am using compressed modules On 26/08/2023 18:34, Marco d'Itri wrote: On Aug 26, Jon Westgate <0...@fsck.tv> wrote: The system partially booted but systemd then prevented boot due to missing modules, The error message it gave was "decompresson failed with status 6" Are you using compressed modules? OpenPGP_0x420652A8C309A3B2.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed
CONFIG_MODULE_SIG=y # CONFIG_MODULE_SIG_FORCE is not set # CONFIG_MODULE_SIG_ALL is not set # CONFIG_MODULE_SIG_SHA1 is not set # CONFIG_MODULE_SIG_SHA224 is not set CONFIG_MODULE_SIG_SHA256=y # CONFIG_MODULE_SIG_SHA384 is not set # CONFIG_MODULE_SIG_SHA512 is not set CONFIG_MODULE_SIG_HASH="sha256" # CONFIG_MODULE_COMPRESS_NONE is not set # CONFIG_MODULE_COMPRESS_GZIP is not set CONFIG_MODULE_COMPRESS_XZ=y # CONFIG_MODULE_COMPRESS_ZSTD is not set CONFIG_MODULE_DECOMPRESS=y # CONFIG_MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS is not set CONFIG_MODPROBE_PATH="/usr/sbin/modprobe" On 26/08/2023 18:58, Marco d'Itri wrote: On Aug 26, Jon Westgate <0...@fsck.tv> wrote: Kernel: Linux 6.4.11 (SMP w/12 CPU threads; PREEMPT) I see that you are using a custom kernel. What is the status of the CONFIG_MODULE_COMPRESS_* kernel configuration options? OpenPGP_0x420652A8C309A3B2.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1050596: RM: eja -- RoQA; unmaintained; severely outdated
Source: eja Severity: serious Version: 9.5.20-1 eja does not seem to be used a lot anymore. I intend to file a RM bug. If you have any reasons to keep it in Debian please voice them here. To get people's attention, I am filing as a serious bug and will reassign to the FTP team when the package is autoremoved from testing.
Bug#1050530: marked as done (python3.11: autopkgtest needs update for new version of tzdata)
Your message dated Sat, 26 Aug 2023 19:05:36 + with message-id and subject line Bug#1050530: fixed in python3.11 3.11.5-2 has caused the Debian Bug report #1050530, regarding python3.11: autopkgtest needs update for new version of tzdata 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.) -- 1050530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python3.11 Version: 3.11.4-1 Severity: serious X-Debbugs-CC: tzd...@packages.debian.org Tags: sid trixie User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:tzdata Dear maintainer(s), With a recent upload of tzdata the autopkgtest of python3.11 fails in testing when that autopkgtest is run with the binary packages of tzdata from unstable. It passes when run with only packages from testing. In tabular form: passfail tzdata from testing2023c-10 python3.11 from testing3.11.4-1 all others from testingfrom testing I copied some of the output at the bottom of this report. I note that src:tzdata recently introduced a tzdata-legacy package although I don't know if that has to do with the failure. Currently this regression is blocking the migration of tzdata to testing [1]. Of course, tzdata shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in tzdata was intended and your package needs to update to the new situation. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=tzdata https://ci.debian.net/data/autopkgtest/testing/amd64/p/python3.11/37127326/log.gz 1107s == 1107s FAIL: test_variable_tzname (test.test_email.test_utils.LocaltimeTests.test_variable_tzname) 1107s -- 1107s Traceback (most recent call last): 1107s File "/usr/lib/python3.11/test/support/__init__.py", line 847, in inner 1107s return func(*args, **kwds) 1107s^^^ 1107s File "/usr/lib/python3.11/test/test_email/test_utils.py", line 155, in test_variable_tzname 1107s self.assertEqual(t1.tzname(), 'MSK') 1107s AssertionError: 'Europe' != 'MSK' 1107s - Europe 1107s + MSK OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python3.11 Source-Version: 3.11.5-2 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of python3.11, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated python3.11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 26 Aug 2023 20:28:17 +0200 Source: python3.11 Architecture: source Version: 3.11.5-2 Distribution: unstable Urgency: medium Maintainer: Matthias Klose Changed-By: Matthias Klose Closes: 1049963 1050530 Changes: python3.11 (3.11.5-2) unstable; urgency=medium . * libpython3.11-stdlib: Also depend on tzdata-legacy. Closes: #1050530. * Add loongarch support. Closes: #1049963. Checksums-Sha1: 1ec1d3db119a2f0fffe8ad0d68e17ac2589bffca 3636 python3.11_3.11.5-2.dsc 75103e0d159f5fdb6368cecca8cbdd2c39d5a93c 213516 python3.11_3.11.5-2.debian.tar.xz 5cd220a6f00c6e804be97418feca4f15a12c456d 9771 python3.11_3.11.5-2_source.buildinfo Checksums-Sha256: 4c931f2c3bf1aa10606da0ac18c8db2c07229e98bbaba4340c5a18e9619701b2 3636 python3.11_3.11.5-2.dsc 98e125d49aefdf28c1cdd4f8e5b82411820e747279c4f7583669f5e4b3232306 213516 python3.11_3.11.5-2.debian.tar.xz 997e9736348bfa66152ec92aefc08c0202e26b2b653929347b8db27f2f0d815f 9771 python3.11_3.11.5-2_source.buildinfo Files: 93b51f1112758bd964d56712ee1a26a0 3636 python optional python3.11_3.11.5-2.dsc efeb2ca06f62cc4a679d6c0e3504f157 213516 python optional
Bug#1050582: kmod update corrupts systemd uefi boot
Found this: # CONFIG_MODULE_COMPRESS_NONE is not set # CONFIG_MODULE_COMPRESS_GZIP is not set CONFIG_MODULE_COMPRESS_XZ=y # CONFIG_MODULE_COMPRESS_ZSTD is not set Il 26/08/23 19:57, Marco d'Itri ha scritto: On Aug 26, antonio wrote: Kernel: Linux 6.4.12-1-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT) I see that you are using a custom kernel. What is the status of the CONFIG_MODULE_COMPRESS_* kernel configuration options?
Bug#1050592: perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl
Package: perl Version: 5.36.0-8 Severity: serious X-Debbugs-Cc: debian-powe...@lists.debian.org Control: affects -1 libfile-fcntllock-perl Hi, debugging an unexpected autopkgtest failure of libfile-fcntllock-perl_0.22-4+b1 with perl_5.36.0-8 on ppc64el [1] I found it's because the old perl binary (5.36.0-7) was built with the fcntl(2) constant F_GETLK == 12, but the new one with F_GETLK == 5 [2]. There are no source or build system changes in perl that would have caused this change. The failure is currently blocking perl testing migration, so filing at 'serious'. Perl is built with -D_FILE_OFFSET_BITS=64, and I see that on bullseye this causes F_GETLK == F_GETLK64 == 12, but on bookworm and later F_GETLK == 5 while F_GETLK64 == 12 [3]. I didn't find the exact change that caused this yet. As can be expected from the above, building libfile-fcntllock-perl on bookworm against perl_5.36.0-7 makes it fail its test suite in a similar way. And rebuilding it on sid against perl_5.36.0-8 makes it pass. On amd64 the constants have stayed equal (== 5) from bullseye to sid, and _FILE_OFFSET_BITS=64 doesn't affect them. What's the deal on ppc64el? Copying the powerpc porters list. Could you please look into this? [1] https://ci.debian.net/data/autopkgtest/unstable/ppc64el/libf/libfile-fcntllock-perl/34669085/log.gz [2] perl -MPOSIX -E 'say F_GETLK' [3] printf '#include \nF_GETLK\nF_GETLK64\n' | cpp -D_FILE_OFFSET_BITS=64 | tail -2 -- Niko Tyni nt...@debian.org
Processed: perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl
Processing control commands: > affects -1 libfile-fcntllock-perl Bug #1050592 [perl] perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl Added indication that 1050592 affects libfile-fcntllock-perl -- 1050592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed
On Aug 26, Jon Westgate <0...@fsck.tv> wrote: > Kernel: Linux 6.4.11 (SMP w/12 CPU threads; PREEMPT) I see that you are using a custom kernel. What is the status of the CONFIG_MODULE_COMPRESS_* kernel configuration options? -- ciao, Marco signature.asc Description: PGP signature
Bug#1050582: kmod update corrupts systemd uefi boot
On Aug 26, antonio wrote: > Kernel: Linux 6.4.12-1-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT) I see that you are using a custom kernel. What is the status of the CONFIG_MODULE_COMPRESS_* kernel configuration options? -- ciao, Marco signature.asc Description: PGP signature
Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed
On Aug 26, Jon Westgate <0...@fsck.tv> wrote: > The system partially booted but systemd then prevented boot due to missing > modules, > The error message it gave was "decompresson failed with status 6" Are you using compressed modules? -- ciao, Marco signature.asc Description: PGP signature
Processed: forcibly merging 1050586 1050582
Processing commands for cont...@bugs.debian.org: > forcemerge 1050586 1050582 Bug #1050586 [kmod] kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed Bug #1050582 [kmod] kmod update corrupts systemd uefi boot Severity set to 'grave' from 'normal' Marked as found in versions kmod/30+20230601-1. Bug #1050586 [kmod] kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed Marked as found in versions kmod/30+20230519-1. Merged 1050582 1050586 > thanks Stopping processing here. Please contact me if you need assistance. -- 1050582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050582 1050586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050432: marked as done (rpy2: FTBFS on mips64el)
Your message dated Sat, 26 Aug 2023 16:37:36 + with message-id and subject line Bug#1050432: fixed in rpy2 3.5.13-4 has caused the Debian Bug report #1050432, regarding rpy2: FTBFS on mips64el to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1050432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rpy2 Version: 3.5.13-1 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, Since the upload version 3.5.13-1, rpy2 has been failing to build on mips64el, which is blocking migration to testing. https://buildd.debian.org/status/logs.php?pkg=rpy2=mips64el === short test summary info FAILED rpy2/tests/rinterface/test_na.py::test_R_to_NAComplex - assert False FAILED rpy2/tests/rinterface/test_vector_complex.py::test_init_from_seqr - as... FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getitem - assert (-... FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setitem - assert (-... FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getslice - assert (... FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getslice_negative FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setslice - assert (... FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setslice_negative FAILED rpy2/tests/rinterface/test_vector_complex.py::test_index - ValueError:... FAILED rpy2/tests/robjects/test_conversion_numpy.py::TestNumpyConversions::test_vector_complex Paul -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) 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 --- End Message --- --- Begin Message --- Source: rpy2 Source-Version: 3.5.13-4 Done: Dirk Eddelbuettel We believe that the bug you reported is fixed in the latest version of rpy2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dirk Eddelbuettel (supplier of updated rpy2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 26 Aug 2023 10:53:00 -0500 Source: rpy2 Architecture: source Version: 3.5.13-4 Distribution: unstable Urgency: medium Maintainer: Dirk Eddelbuettel Changed-By: Dirk Eddelbuettel Closes: 1050432 Changes: rpy2 (3.5.13-4) unstable; urgency=medium . * rpy2/tests/*: Skip several tests on mips64el where complex variables now fail the tests (Closes: #1050432) Checksums-Sha1: 80470cab8316c80aa726df9ef2a846ade2d0f98e 1934 rpy2_3.5.13-4.dsc 0226556b107b161c47f737b851d2f2c8734ed685 15432 rpy2_3.5.13-4.debian.tar.xz 4621f353fdd46ffe16b7ae8ab528055704babe7c 10427 rpy2_3.5.13-4_amd64.buildinfo Checksums-Sha256: 58020e3327f05c44819233defdb9b6ecd9f09de929128d9a7824deb555d98bab 1934 rpy2_3.5.13-4.dsc 7ad93258d6f35e0b91c29ceec4e64325a0421b195bdd556ab88a5c88999895f7 15432 rpy2_3.5.13-4.debian.tar.xz 8b90a7887366e2fd3837e15f5f7b449bf42f594e33eb5d629f22af3178623248 10427 rpy2_3.5.13-4_amd64.buildinfo Files: 3845d93dfec1a343566674fdc7a47877 1934 python optional rpy2_3.5.13-4.dsc 6277ecc9feb6e31e76bbe450b8bf648d 15432 python optional rpy2_3.5.13-4.debian.tar.xz 271dfb9c28dc72656a76f73d0ccf1650 10427 python optional rpy2_3.5.13-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIVAwUBZOokLqFIn+KrmaIaAQiwoA//QXMQD8yyJE/A927CYqQYWu3/eQq+ZdkH wxbUkldFhzBrDUfZBevwLZlnL7BdigAVlrSOGFDDEIitRbaOXS1KyjW4ccb7BCFQ zqfy+xJrLQHmlxPNp2EpxxHHjBVC9ShAZiQZm+VP8XZffcQn9lKqtoQyWwD26iss p16wbvDxbplyq/tpkgPLWjmNNB0WmfYhpoUkn6lhovzLvrrj3E1Sy9jINNymS5NI dYIUArfgeqxwjNA5UZpqAcDBd0PMxfOA3hZ8PlRAIo0QuULQ6bvgVknaFkCyOB7/ jpzmtdTHyDYlkjx81Xq64TmUHBbI5ndcD3J2MOjaCZt6qPNJMfkEDvwNCdC/0Wdz XApIKb3tA8Wud+Wns8mnAy8AELB90cudqz1b1ULZkv9LFdyCjsPJVUuGk4IKwiHk cNqIaLelUaNYNkciv03PbV1P+7ZI78ifyV3+jmYnR+3N4vshh0lXVQUxJraUxNLQ
Bug#1050432: rpy2: FTBFS on mips64el
Hi all, As the test failures for complex valued variables appeared to be systemic on the 'mips64el' platform, I buckled down, taught myself some Python ==:-) and conditioned the number of failing tests away via @pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 'little', reason="Complex tests fails for 'mips64el'.") Maybe the porters team can shed some light on why we needed it, and if this worked (the autobuilders will tell us soon enough) I can pass the patch on to Laurent for a possible inclusion upstream. Cheers, Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1050586: kmod: Updating to kmod to 30+20230601-1 results in a non booting system modules cannot be decompressed
Package: kmod Version: 30+20230601-1 Severity: grave Justification: renders system unusable Dear Maintainer, I just did a normal apt upgrade and the following packages were upgraded: kmod 30+20230519-1 to 30-2.230601-1 libkmod2 30+20230519-1 to 30-2.230601-1 The system partially booted but systemd then prevented boot due to missing modules, The error message it gave was "decompresson failed with status 6" I had to boot from a rescue usb stick, set a root password, then I was able to interact with systemd's idea of a diagnotic console - I'm not systemd's biggest fan I used another system to download the older versions of kmod and libkmod2 and as able to use dpkg to downgrade them. I installed both on another system and it does the same. I'm not sure if this effects other system's with sysvinit or non efi. Regards Jon Westgate -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.11 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages kmod depends on: ii libc6 2.37-7 ii libkmod2 30+20230601-1 ii liblzma5 5.4.1-0.2 ii libssl3 3.0.10-1 ii libzstd1 1.5.5+dfsg2-1 kmod recommends no packages. kmod suggests no packages. -- no debconf information
Bug#1050462: gtg: crashes on startup often
On Fri, Aug 25, 2023 at 08:52:49PM +0200, François Mazen wrote: > Dear Antonio, > > thanks for the crash report! I can reproduce it easily with unstable > distribution and the call stack points to pango_font_description_to_string > method. > > The issues seems to have been already reported upstream [1] and the suggested > worj around is to add "font_name = Sans 11" in the [browser] section of the > ~/.config/gtg/gtg.conf config file. Thanks, this indeed seem to work around the issue. > I've checked the fix and no more crash occurs, so it could be integrated as a > quilt patch for the Debian package. We probably want to fix the code to *not* segfault when the workaround is not in place. I'm not sure whether this is a bug in gtg itself, or in pango. signature.asc Description: PGP signature
Bug#1050584: trocla: broken by ruby-highline 2.1.0-1
Source: trocla Version: 0.5.1-1 Severity: serious Hi, I just uploaded ruby-highline 2.1.0-1. While testing reverse dependencies, I noticed that it breaks this package. Lucas
Bug#1050583: ruby-commander: broken by ruby-highline 2.1.0-1
Source: ruby-commander Version: 4.6.0-1 Severity: serious Hi, I just uploaded ruby-highline 2.1.0-1. While testing reverse dependencies, I noticed that it breaks this package. Lucas
Bug#1049886: btllib: FTBFS on armhf due to tests timing out
Hi Emanuele, Am Fri, Aug 25, 2023 at 02:33:28PM +0200 schrieb Emanuele Rocca: > > btllib (1.4.10+dfsg-1) unstable; urgency=medium > > [...] > > > So I'm wondering why this bug came up at all and closing it hereby. > > Ah yes, the reason why it came up is that btllib-tools is still Architecture: > any. The buildds are attempting to build the package, and it fails. See for > example 1.4.10+dfsg-1 on i386: > https://buildd.debian.org/status/fetch.php?pkg=btllib=i386=1.4.10%2Bdfsg-1=1685883214=0 This is perfectly sensible if the package does not build on some architecture if a precondition does not exist on that architecture. IMHO this bug should be closed. Kind regards Andreas. -- http://fam-tille.de
Bug#1050581: ruby-html-proofer: broken by ruby-nokogiri 1.15.4
Source: ruby-html-proofer Version: 3.19.2-7 Severity: serious Hi, I just uploaded ruby-nokogiri 1.15.4, and while testing reverse dependencies, noticed that it breaks this package. Lucas
Bug#1050580: ruby-roxml: broken by ruby-nokogiri 1.15.4
Source: ruby-roxml Version: 4.2.0-1 Severity: serious Hi, I just uploaded ruby-nokogiri 1.15.4, and while testing reverse dependencies, noticed that it breaks this package. Lucas
Bug#1050366: marked as done (opencolorio: FTBFS with newer yaml-cpp [PATCH])
Your message dated Sat, 26 Aug 2023 13:04:06 + with message-id and subject line Bug#1050366: fixed in opencolorio 2.1.2+dfsg1-4.1 has caused the Debian Bug report #1050366, regarding opencolorio: FTBFS with newer yaml-cpp [PATCH] 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.) -- 1050366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opencolorio Version: 2.1.2+dfsg1-4 Severity: important tags: patch Hello, looks like the new yaml-cpp version is making the embedded cmake fail to detect it. An easy workaround/patch is the following: diff -Nru opencolorio-2.1.2+dfsg1/debian/rules opencolorio-2.1.2+dfsg1/debian/rules --- opencolorio-2.1.2+dfsg1/debian/rules2022-12-04 20:34:15.0 + +++ opencolorio-2.1.2+dfsg1/debian/rules2023-08-22 16:40:28.0 + @@ -12,6 +12,10 @@ %: dh $@ -Scmake -B$(BLDDIR) --with python3 +override_dh_auto_clean: + dh_auto_clean + rm -f share/cmake/modules/Findyaml-cpp.cmake + override_dh_auto_configure: dh_auto_configure -- \ -DCMAKE_BUILD_TYPE=Release \ thanks for considering it, this bug will become serious once yaml-cpp transition is ack'd by Release Team G. OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: opencolorio Source-Version: 2.1.2+dfsg1-4.1 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of opencolorio, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated opencolorio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 26 Aug 2023 13:55:36 +0200 Source: opencolorio Built-For-Profiles: noudeb Architecture: source Version: 2.1.2+dfsg1-4.1 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Gianfranco Costamagna Closes: 1017111 1050366 1050570 Changes: opencolorio (2.1.2+dfsg1-4.1) unstable; urgency=medium . [ Gianfranco Costamagna ] * Non-maintainer upload. * Fix FTBFS with newer yaml-cpp (Closes: #1050366) * Update manpages (Closes: #1017111) . [ Olivier Gayot ] * Include header file in binary package (change in d/rules and d/python3-pyopencolorio.install) (Closes: #1050570) * d/patches/0002-fix-documentation-cmake-syntax.patch Fix generation of documentation. Checksums-Sha1: 3b533409186279d63cac908408869f7c2f4eaa54 2764 opencolorio_2.1.2+dfsg1-4.1.dsc 99cd32299e4cd3ed9d77c45fc8d9f36d205f08d1 11316 opencolorio_2.1.2+dfsg1-4.1.debian.tar.xz bcd2e4cb95ae70b975b0bbc7ddf7c9754d0e59f7 13430 opencolorio_2.1.2+dfsg1-4.1_source.buildinfo Checksums-Sha256: 5ebffe0ed99110af74c50b925ca16c490758e5859685da779987fbc41f363114 2764 opencolorio_2.1.2+dfsg1-4.1.dsc d3fadb092bd7b000ae36d484fbbe8d8813ccfee640e4a3061b0050e5c262bb15 11316 opencolorio_2.1.2+dfsg1-4.1.debian.tar.xz 5eb938268a74a3757a4d5563269455ae665122426a2e74fd21e32311286d6aa4 13430 opencolorio_2.1.2+dfsg1-4.1_source.buildinfo Files: a7ece94aa72d1823ded865b4c71e5a33 2764 libs optional opencolorio_2.1.2+dfsg1-4.1.dsc 24d64066b3fb3a030bce79e0abcf6571 11316 libs optional opencolorio_2.1.2+dfsg1-4.1.debian.tar.xz d9b0afcb81a373d9d229ab1720459073 13430 libs optional opencolorio_2.1.2+dfsg1-4.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmTp9GkACgkQ808JdE6f XdngMg/9G6UKtRbvWG2x7Mp131U5OFHZmCuIJBBB8M1/lMBILyUct32fSkuk1QcE yifMISvLcTOFzaSZa7PiuNF/rPoUrS62vku1eM4GH4QtM2Xqz3iCiOUx1CHu5CYW 0wPAE67c2W+NGvnG7AObkbcTRfoCzZebV8CcwTl/YDztD9CHot/8xOZISC3YUMF5 Ta0cWu3b3kGcn7JiM9etKgrhcgbObb/1SW+njdbvIwrL/yYZnRM3SkwfqMs7fw36 fhzdBKRZIJZfT8bLET5MbP/O+FQeIQHS7HmE6txRoXOf1jRf2ia/I7XydEKV4+W6 llwsvSDUjqCk1dz+xLRakGUpez5UU8TJr4VoxzlAaVKwvk/ihmo9tDBvscmUWhoh +9susQDePWdRE8/oN/BbF60w7CWUpxD5AwlatraOrK5TLatYwrLYKxOAk1KSGdB5 3BHWuyJ/uj5ehf+yStWxg9DuHzG3YmcpsQLnU7M2Fj21+XTwqwI19Wb2Vzb+kdsf
Bug#1050366: patch NMU ongoing
control: tags -1 patch pending Hello, attached debdiff uploaded to sid. diff -Nru opencolorio-2.1.2+dfsg1/debian/changelog opencolorio-2.1.2+dfsg1/debian/changelog --- opencolorio-2.1.2+dfsg1/debian/changelog2022-08-20 23:39:40.0 +0200 +++ opencolorio-2.1.2+dfsg1/debian/changelog2023-08-26 13:55:36.0 +0200 @@ -1,3 +1,18 @@ +opencolorio (2.1.2+dfsg1-4.1) unstable; urgency=medium + + [ Gianfranco Costamagna ] + * Non-maintainer upload. + * Fix FTBFS with newer yaml-cpp (Closes: #1050366) + * Update manpages (Closes: #1017111) + + [ Olivier Gayot ] + * Include header file in binary package (change in d/rules and +d/python3-pyopencolorio.install) (Closes: #1050570) + * d/patches/0002-fix-documentation-cmake-syntax.patch Fix generation of +documentation. + + -- Gianfranco Costamagna Sat, 26 Aug 2023 13:55:36 +0200 + opencolorio (2.1.2+dfsg1-4) unstable; urgency=medium [ Pino Toscano ] diff -Nru opencolorio-2.1.2+dfsg1/debian/manpages/ociobakelut.1 opencolorio-2.1.2+dfsg1/debian/manpages/ociobakelut.1 --- opencolorio-2.1.2+dfsg1/debian/manpages/ociobakelut.1 2022-08-11 23:25:53.0 +0200 +++ opencolorio-2.1.2+dfsg1/debian/manpages/ociobakelut.1 2023-08-26 13:55:36.0 +0200 @@ -1,4 +1,4 @@ -.TH OCIOBAKELUT "1" "August 2022" "create a new LUT or ICC profile from an OCIO config or LUT file(s)" "User Commands" +.TH OCIOBAKELUT "26" "August 2023" "create a new LUT or ICC profile from an OCIO config or LUT file(s)" "User Commands" .SH NAME ociobakelut \- create a new LUT or ICC profile from an OCIO config or LUT file(s) .PP @@ -73,89 +73,3 @@ .TP \fB\-\-copyright\fR %s a copyright field added in the file (default: "No copyright. Use freely.") -.PP -ociobakelut \fB\-\-\fR create a new LUT or ICC profile from an OCIO config or LUT file(s) -.PP -usage: ociobakelut [options] -.PP -example: ociobakelut \fB\-\-inputspace\fR lg10 \fB\-\-outputspace\fR srgb8 \fB\-\-format\fR flame lg_to_srgb.3dl -example: ociobakelut \fB\-\-lut\fR filmlut.3dl \fB\-\-lut\fR calibration.3dl \fB\-\-format\fR flame display.3dl -example: ociobakelut \fB\-\-cccid\fR 0 \fB\-\-lut\fR cdlgrade.ccc \fB\-\-lut\fR calibration.3dl \fB\-\-format\fR flame graded_display.3dl -example: ociobakelut \fB\-\-lut\fR look.3dl \fB\-\-offset\fR 0.01 \fB\-0\fR.02 0.03 \fB\-\-lut\fR display.3dl \fB\-\-format\fR flame display_with_look.3dl -example: ociobakelut \fB\-\-inputspace\fR lg10 \fB\-\-outputspace\fR srgb8 \fB\-\-format\fR icc \fI\,~/Library/ColorSync/Profiles/test.icc\/\fP -example: ociobakelut \fB\-\-lut\fR filmlut.3dl \fB\-\-lut\fR calibration.3dl \fB\-\-format\fR icc \fI\,~/Library/ColorSync/Profiles/test.icc\/\fP -.PP -Using Existing OCIO Configurations -.TP -\fB\-\-inputspace\fR %s -Input OCIO ColorSpace (or Role) -.TP -\fB\-\-outputspace\fR %s -Output OCIO ColorSpace (or Role) -.TP -\fB\-\-shaperspace\fR %s -the OCIO ColorSpace or Role, for the shaper -.TP -\fB\-\-looks\fR %s -the OCIO looks to apply -.TP -\fB\-\-iconfig\fR %s -Input .ocio configuration file (default: $OCIO) -.PP -Config\-Free LUT Baking -.IP -(all options can be specified multiple times, each is applied in order) -\fB\-\-cccid\fR %s Specify a CCCId for any following LUTs -\fB\-\-lut\fR %s Specify a LUT (forward direction) -\fB\-\-invlut\fR %s Specify a LUT (inverse direction) -\fB\-\-slope\fR %f %f %f slope -\fB\-\-offset\fR %f %f %foffset (float) -\fB\-\-offset10\fR %f %f %f offset (10\-bit) -\fB\-\-power\fR %f %f %f power -\fB\-\-sat\fR %f saturation (ASC\-CDL luma coefficients) -.PP -Baking Options -.TP -\fB\-\-format\fR %s -the LUT format to bake: flame (.3dl), lustre (.3dl), Academy/ASC Common LUT Format (.clf), Color Transform Format (.ctf), cinespace (.csp), houdini (.lut), iridas_cube (.cube), iridas_itx (.itx), resolve_cube (.cube), truelight (.cub), icc (.icc) -.TP -\fB\-\-shapersize\fR %d -size of the shaper (default: format specific) -.TP -\fB\-\-cubesize\fR %d -size of the cube (default: format specific) -.TP -\fB\-\-stdout\fR -Write to stdout (rather than file) -.TP -\fB\-\-v\fR -Verbose -.TP -\fB\-\-help\fR -Print help message -.PP -ICC Options -.TP -\fB\-\-whitepoint\fR %d -whitepoint for the profile (default: 6505) -.TP -\fB\-\-displayicc\fR %s -an ICC profile which matches the OCIO profiles target display -.TP -\fB\-\-description\fR %s -a meaningful description, this will show up in UI like photoshop (defaults to "filename.icc") -.TP -\fB\-\-copyright\fR %s -a copyright field added in the file (default: "No copyright. Use freely.") -.SH "SEE ALSO" -The full documentation for -.B Invalid -is maintained as a Texinfo manual. If the -.B info -and -.B Invalid -programs are properly installed at your site, the command -.IP -.B info Invalid -.PP -should give you access to the complete manual. diff -Nru opencolorio-2.1.2+dfsg1/debian/manpages/ociocheck.1 opencolorio-2.1.2+dfsg1/debian/manpages/ociocheck.1 ---
Processed: patch NMU ongoing
Processing control commands: > tags -1 patch pending Bug #1050366 [src:opencolorio] opencolorio: FTBFS with newer yaml-cpp [PATCH] Added tag(s) pending. -- 1050366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1043500: marked as done (librust-winnow-dev: impossible to install)
Your message dated Sat, 26 Aug 2023 12:36:30 + with message-id and subject line Bug#1043500: fixed in rust-winnow 0.5.15-1 has caused the Debian Bug report #1043500, regarding librust-winnow-dev: impossible to install 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.) -- 1043500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-winnow-dev Version: 0.4.8-1+b1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Impossible to install: Depends on unavailable packages librust-anstyle-0.3+default-dev and librust-anstyle-stream-0.2+default-dev. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTXCMwACgkQLHwxRsGg ASEl4Q/+JfoD3B73fi8wQlhcHmL/QO+SoCyIcmLje+xVQweRmtMQ9IQd+8PCc3/P No4Tp0wZQ8F7r/vVhqkw4XVLQp3hCq/ghsoclbRQnH0MmMru1Bct0s6piLCoLQHu m1Z6HoMaTcy7uIRYdoph6gu8jzrfzpNRLdXniCz3/4cUlH38RAVnwOIzpFyQOD00 qXWrLGx6nT3yieO4ktXpqCgrlAnL1tgNe/kNmNRwuSGkqRzNu+pAvv+ETnaoK281 bZuR8aAI5jILbN/DXdXIXvXtet37NzmGBS4Ti4wZ7eSRvrgQdvD8C7s7myZgKIqY VGQ/J6uvf8kRbCxBtqfY9tQ7ncJFWlHvQp+u6Bb/uetP2EhSzm6fJZrd5v6Dr/48 5amIhngyF9T2X9UiRg9GneP8p2KxqRAvi/ttei2WTerDw4yxJRzJCBGWYk7nLAjZ 7bJtK9Y250txvFmn7VkoCkI+lBDrMvnmTe4MYFgonZxeeMcZyTkAwysBuBLQICgk NqC7RlQbzkB3DSnZ7Kf/RlOFFZ/gdv5V2u+iBg55C3tUe7bAFMKOEYVZCrFLnJbV j320g2aus2d8MhPKgKJiaUzSQR7wg1NqlZREz57ldnMWrcrqDTrC1D5Lil8aFC0N RobTO26VTTmZNEbG8On9qzBJppczqeFUFP7pxzPHQIiKPP7ZCII= =t0DW -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: rust-winnow Source-Version: 0.5.15-1 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-winnow, 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 1043...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-winnow package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 26 Aug 2023 12:11:45 + Source: rust-winnow Architecture: source Version: 0.5.15-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1043500 Changes: rust-winnow (0.5.15-1) unstable; urgency=medium . * Team upload. * Package winnow 0.5.15 from crates.io using debcargo 2.6.0 * Update drop-debug-feature.patch for new upstream. . [ kpcyrd ] * Package winnow 0.5.1 from crates.io using debcargo 2.6.0 . [ Fabian Grünbichler ] * Add patch to drop debug feature and associated optional dependencies. (Closes: #1043500) Checksums-Sha1: d3aaa791e1e022741892130ee3149b5ef45cec83 2477 rust-winnow_0.5.15-1.dsc 2a13bc56e5d9d752084af8648b101422c85be5a1 145621 rust-winnow_0.5.15.orig.tar.gz 67024c8e2866f4e85aefeccab705cce231a1cfa4 3248 rust-winnow_0.5.15-1.debian.tar.xz a68cb1a28ce2bf23ec8c570423212e23c72589fd 7648 rust-winnow_0.5.15-1_source.buildinfo Checksums-Sha256: 3079b64b59960109e136e597d95e119c948b6ecf4c23d8c0ae5ed09b603d1db2 2477 rust-winnow_0.5.15-1.dsc 7c2e3184b9c4e92ad5167ca73039d0c42476302ab603e2fec4487511f38ccefc 145621 rust-winnow_0.5.15.orig.tar.gz 6dcae73bfa41fa1556e7ccfbba2ee63aa5db251ea647b6c77da8bb45daae1963 3248 rust-winnow_0.5.15-1.debian.tar.xz 1a065dd90468eb8e22aac62d5b2eb7a68773eb1bf9c7b70e81f6c478aaca3000 7648 rust-winnow_0.5.15-1_source.buildinfo Files: c90d4ed4d710694d72e2fbe401f3e854 2477 rust optional rust-winnow_0.5.15-1.dsc aa116d4926d15269d9c4c14ce0c6cf0c 145621 rust optional rust-winnow_0.5.15.orig.tar.gz bccc61887fe2dbb306c70a3d632e63ad 3248 rust optional rust-winnow_0.5.15-1.debian.tar.xz cfecfb15e1a7b8ad6e3d6361a21198f1 7648 rust optional rust-winnow_0.5.15-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmTp7TIUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvFrQ//VCPTFIM+xKWtGEZskOazmqGn2lKt WQmTSzmDgYtYFVU6XFiuKwaQ2wLnWhHiitN4bGX1g5hl3WVdW2OM24SCalFR0cOr WZSeeQAtb0mhQ/753OJB2v97ymd20XamyrJI0eGjqxKohOUvSJF7PMJJdjtF2PRQ wF7pAP+am90Ol4Ckps/hciN9bxOn40I6D4tiZzgimFDauh5LbvExfRoyYyWnLWE0
Bug#1050288: nsis 3.08-3 (bookworm) generates bogus relocation information (regression)
Thank you for your detailed bug report. I built the nsis_3.09-1 and nsis-common_3.09-1 packages on Debian Bookworm, installed the resulting packages and can confirm with the two Nullsoft Installer (.nsi) scripts provided by you that the resulting installer executables no longer show the "(.reloc) is too large" error with objdump. Therefore I would appreciate if you create a "bookworm proposed updates request" by issuing the "reportbug release.debian.org" command on a Debian system. Please mention in "reportbug" this bug report, provide your observations and results of your tests and also refer to the fixed security vulnerability (Bug#1040880: nsis: CVE-2023-37378) in nsis_3.09-1.
Processed: python-ase: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Processing control commands: > severity -1 important Bug #1042048 [src:python-ase] python-ase: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Severity set to 'important' from 'serious' > tags -1 + unreproducible Bug #1042048 [src:python-ase] python-ase: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) unreproducible. -- 1042048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042048: python-ase: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Control: severity -1 important Control: tags -1 + unreproducible Hi Lucas I'm unable to reproduce this failure locally, also python-ase builds successfully on reproducible builds [1]. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/python-ase.html
Bug#1050557: marked as done (abyss: FTBFS: error: possibly dangling reference to a temporary [-Werror=dangling-reference])
Your message dated Sat, 26 Aug 2023 11:05:14 + with message-id and subject line Bug#1050557: fixed in abyss 2.3.7-2 has caused the Debian Bug report #1050557, regarding abyss: FTBFS: error: possibly dangling reference to a temporary [-Werror=dangling-reference] 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.) -- 1050557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: abyss Version: 2.3.7-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, abyss fails to build from source. From my build log on amd64: | Making all in Graph | make[4]: Entering directory '/<>/Graph' | g++ -std=c++11 -DHAVE_CONFIG_H -I. -I.. -I.. -I../Common -I/<> -isystem/usr/lib/x86_64-linux-gnu/openmpi/include-Wdate-time -D_FORTIFY_SOURCE=2 -isystem/<>/boost_1_56_0 -Wall -Wextra -Werror -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DGTEST_USE_OWN_TR1_TUPLE=0 -c -o abyss_gc-gc.o `test -f 'gc.cc' || echo './'`gc.cc | g++ -std=c++11 -Wall -Wextra -Werror -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DGTEST_USE_OWN_TR1_TUPLE=0 -L/usr/lib/x86_64-linux-gnu/openmpi/lib-Wl,-z,relro -Wl,-z,now -o abyss-gc abyss_gc-gc.o ../Common/libcommon.a -ldl -lm | g++ -std=c++11 -DHAVE_CONFIG_H -I. -I.. -I.. -I../Common -I/<> -isystem/usr/lib/x86_64-linux-gnu/openmpi/include-Wdate-time -D_FORTIFY_SOURCE=2 -isystem/<>/boost_1_56_0 -Wall -Wextra -Werror -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DGTEST_USE_OWN_TR1_TUPLE=0 -c -o abyss_todot-todot.o `test -f 'todot.cc' || echo './'`todot.cc | In file included from GraphIO.h:10, | from todot.cc:9: | GfaIO.h: In instantiation of ‘std::ostream& write_gfa2_edges(std::ostream&, const Graph&, const DistanceEst*) [with Graph = ContigGraph >; std::ostream = std::basic_ostream]’: | GfaIO.h:216:25: required from ‘std::ostream& write_gfa2(std::ostream&, Graph&) [with Graph = const ContigGraph >; std::ostream = std::basic_ostream]’ | GraphIO.h:37:20: required from ‘std::ostream& write_graph(std::ostream&, const Graph&, const std::string&, const std::string&) [with Graph = ContigGraph >; std::ostream = std::basic_ostream; std::string = std::__cxx11::basic_string]’ | todot.cc:186:14: required from here | GfaIO.h:182:27: error: possibly dangling reference to a temporary [-Werror=dangling-reference] | 182 | const EP& ep = get(edge_bundle, g, eit); | | ^~ | GfaIO.h:182:35: note: the temporary was destroyed at the end of the full expression ‘get(boost::edge_bundle, g.ContigGraph >::, DirectedGraph::edge_iterator(eit))’ | 182 | const EP& ep = get(edge_bundle, g, eit); | |~~~^ | In file included from GraphIO.h:8: | DotIO.h: In instantiation of ‘void write_edges(std::ostream&, const Graph&, typename boost::graph_traits::vertex_descriptor, const EdgeProp*) [with Graph = ContigGraph >; EdgeProp = DistanceEst; std::ostream = std::basic_ostream; typename boost::graph_traits::vertex_descriptor = ContigNode]’: | DotIO.h:110:14: required from ‘std::ostream& write_dot(std::ostream&, const Graph&, const std::string&) [with Graph = ContigGraph >; std::ostream = std::basic_ostream; std::string = std::__cxx11::basic_string]’ | DotIO.h:77:18: required from ‘std::ostream& write_dot(std::ostream&, const Graph&) [with Graph = ContigGraph >; std::ostream = std::basic_ostream]’ | DotIO.h:125:26: required from ‘std::ostream& operator<<(std::ostream&, const DotWriter > >&)’ | GraphIO.h:33:14: required from ‘std::ostream& write_graph(std::ostream&, const Graph&, const std::string&, const std::string&) [with Graph = ContigGraph >; std::ostream = std::basic_ostream; std::string = std::__cxx11::basic_string]’ | todot.cc:186:14: required from here | DotIO.h:44:43: error: possibly dangling reference to a temporary [-Werror=dangling-reference] |44 | const edge_property_type& ep = get(edge_bundle, g, e); | | ^~ | DotIO.h:44:51: note: the temporary was destroyed at the end of the full expression ‘get >(boost::edge_bundle, (* & g), DirectedGraph::out_edge_iterator(e))’ |44 | const edge_property_type& ep = get(edge_bundle, g, e); | |
Bug#1017663: marked as done (Please upgrade to llvm-toolchain-14)
Your message dated Sat, 26 Aug 2023 10:50:15 + with message-id and subject line Bug#1017663: fixed in ghc 9.4.6-1 has caused the Debian Bug report #1017663, regarding Please upgrade to llvm-toolchain-14 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.) -- 1017663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ghc Severity: important Dear Maintainer, As part of the effort to limit the number of llvm packages in the archive, it would be great if you could upgrade to -14. We are trying NOT to ship Bookworm with llvm-toolchain-13. llvm-defaults is now pointing to -14. Thanks, Sylvestre --- End Message --- --- Begin Message --- Source: ghc Source-Version: 9.4.6-1 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of ghc, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated ghc 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: Fri, 25 Aug 2023 20:12:47 +0300 Source: ghc Architecture: source Version: 9.4.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 1017663 1039474 Changes: ghc (9.4.6-1) unstable; urgency=medium . * Upload to unstable (Closes: #1017663, #1039474) Checksums-Sha1: 3d49cfc2d4764fb37c9cd8c73016e4b99ace2ae1 2626 ghc_9.4.6-1.dsc 6d6fa1fb99a7718a26c37bff2a1edaec4dfd86a9 56488 ghc_9.4.6-1.debian.tar.xz d1c0b733ca0ed77e7a7f453c6d64f92b83bf375a 13090 ghc_9.4.6-1_amd64.buildinfo Checksums-Sha256: 83e4d05fd9838636f98a1d1ba106cca772b7471ab7efe0c5f0d55247edefb509 2626 ghc_9.4.6-1.dsc 8492a665b6c411afd7cda41cbf713b931e0caee2a7f696b0ed7ea4487d0e4acc 56488 ghc_9.4.6-1.debian.tar.xz 75476a3632456d6808f0ff7dbc7cb52902a454ca9f0c46d0cc90d4e0387b3916 13090 ghc_9.4.6-1_amd64.buildinfo Files: 8c4fd1416dc8293334c4fad857e62eda 2626 haskell optional ghc_9.4.6-1.dsc 4f811a2b1155f888c46390f55e85a993 56488 haskell optional ghc_9.4.6-1.debian.tar.xz 5149361962d1da82642e58e3d684e253 13090 haskell optional ghc_9.4.6-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmTp1fkUHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDy35RAAk1MGECTA9BfNFqpDV5jJ4CIAZpnf IXJTmgcoc1BDTCAfKpu2NMMJY83GSWXr06rmgNaxDxFCtPYochBkZfbR+hwBPfMj W1PQJ76ciVvJnvLflJhNmAfSHtmy9YYVXwPS3OVQNkD0hkKnVKOYDi/XmChkl6Di s9vbDpW0ND8tWKORPi9s9wpN3sBZYKE33yMpoGX433TZat9GXKS08LVA81GdxXTm 6vT6Rbxp9P+qhmE1Mzj+eTfhZEZUONqgGbcQf2IIbA43PvJewKqAFxsymQYYTcSo Bwb/GjYMHlEvnKbCkZ466Y6JPxBK/gMxj4/wsbDUt6ePROvpaQFMdPo7YRU1u/ex tio4kk0tAph/Bjb3EJhjLwaMm+6e2uBe744VNg9x5S5mIgyddIjn2WOGqsbd7L8x +LdQVUMNQtfoefO1wwJnhLvcH1p0PbDlGLP6UNaCvbPVIxoVHs7lmWLKMSTGgdx+ 7LYkQ5S9W9QcPdGi3BF7AvI2/5zWQhYgWgJ4Vs0yA1mc5aLgFjajpztjlMbED6ci 06fqEYQv0F/6pVPG6YBt6+CDk3Lf2CQws2O5M/2WlH/woQmSPHwKLqyTgqL5mGSI sfsnabIQ11TUB2eAehUPqWidwj87Aa8aJBOYnDrs3kHbB03r+f6uNxe/KHCipeK+ HW3LOyGUoulgIbU= =h5KZ -END PGP SIGNATURE End Message ---
Processed: Bug#1050557 marked as pending in abyss
Processing control commands: > tag -1 pending Bug #1050557 [src:abyss] abyss: FTBFS: error: possibly dangling reference to a temporary [-Werror=dangling-reference] Added tag(s) pending. -- 1050557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050557: marked as pending in abyss
Control: tag -1 pending Hello, Bug #1050557 in abyss reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/abyss/-/commit/6b436c46ac14f056dec7d35f7ed70f0caeb277b0 d/rules: build with -Wno-error=dangling-reference. This fixes build failures with gcc 13. Closes: #1050557 (this message was generated automatically) -- Greetings https://bugs.debian.org/1050557
Processed: Re: [Debian-med-packaging] Bug#1050557: abyss: FTBFS: error: possibly dangling reference to a temporary [-Werror=dangling-reference]
Processing control commands: > tags -1 + confirmed Bug #1050557 [src:abyss] abyss: FTBFS: error: possibly dangling reference to a temporary [-Werror=dangling-reference] Added tag(s) confirmed. -- 1050557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050557: [Debian-med-packaging] Bug#1050557: abyss: FTBFS: error: possibly dangling reference to a temporary [-Werror=dangling-reference]
Control: tags -1 + confirmed Hi Aurélien, Aurelien Jarno, on 2023-08-26: > | GfaIO.h:182:27: error: possibly dangling reference to a temporary > [-Werror=dangling-reference] Thank you for your report, this seems to be one of those cases where the newly introduced warnings in gcc 13 are getting possibly overzealous. I did reproduce the crash on my end and consider making the warning non-fatal for the time being. This will solve the build failure on amd64, riscv64, and all the other architectures which were otherwise working with this package. Have a nice day, :) -- .''`. Étienne Mollier : :' : gpg: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/2, please excuse my verbosity `-on air: Sieges Even - Unbreakable signature.asc Description: PGP signature
Processed: affects 1050185
Processing commands for cont...@bugs.debian.org: > affects 1050185 rust-derive-builder-macro rust-derive-builder > rust-cargo-metadata rust-skeptic rust-err-derive Bug #1050185 [rust-derive-builder-core] rust-derive-builder-core - depends on old version of darling. Added indication that 1050185 affects rust-derive-builder-macro, rust-derive-builder, rust-cargo-metadata, rust-skeptic, and rust-err-derive > thanks Stopping processing here. Please contact me if you need assistance. -- 1050185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050557: abyss: FTBFS: error: possibly dangling reference to a temporary [-Werror=dangling-reference]
Source: abyss Version: 2.3.7-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, abyss fails to build from source. From my build log on amd64: | Making all in Graph | make[4]: Entering directory '/<>/Graph' | g++ -std=c++11 -DHAVE_CONFIG_H -I. -I.. -I.. -I../Common -I/<> -isystem/usr/lib/x86_64-linux-gnu/openmpi/include-Wdate-time -D_FORTIFY_SOURCE=2 -isystem/<>/boost_1_56_0 -Wall -Wextra -Werror -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DGTEST_USE_OWN_TR1_TUPLE=0 -c -o abyss_gc-gc.o `test -f 'gc.cc' || echo './'`gc.cc | g++ -std=c++11 -Wall -Wextra -Werror -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DGTEST_USE_OWN_TR1_TUPLE=0 -L/usr/lib/x86_64-linux-gnu/openmpi/lib-Wl,-z,relro -Wl,-z,now -o abyss-gc abyss_gc-gc.o ../Common/libcommon.a -ldl -lm | g++ -std=c++11 -DHAVE_CONFIG_H -I. -I.. -I.. -I../Common -I/<> -isystem/usr/lib/x86_64-linux-gnu/openmpi/include-Wdate-time -D_FORTIFY_SOURCE=2 -isystem/<>/boost_1_56_0 -Wall -Wextra -Werror -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DGTEST_USE_OWN_TR1_TUPLE=0 -c -o abyss_todot-todot.o `test -f 'todot.cc' || echo './'`todot.cc | In file included from GraphIO.h:10, | from todot.cc:9: | GfaIO.h: In instantiation of ‘std::ostream& write_gfa2_edges(std::ostream&, const Graph&, const DistanceEst*) [with Graph = ContigGraph >; std::ostream = std::basic_ostream]’: | GfaIO.h:216:25: required from ‘std::ostream& write_gfa2(std::ostream&, Graph&) [with Graph = const ContigGraph >; std::ostream = std::basic_ostream]’ | GraphIO.h:37:20: required from ‘std::ostream& write_graph(std::ostream&, const Graph&, const std::string&, const std::string&) [with Graph = ContigGraph >; std::ostream = std::basic_ostream; std::string = std::__cxx11::basic_string]’ | todot.cc:186:14: required from here | GfaIO.h:182:27: error: possibly dangling reference to a temporary [-Werror=dangling-reference] | 182 | const EP& ep = get(edge_bundle, g, eit); | | ^~ | GfaIO.h:182:35: note: the temporary was destroyed at the end of the full expression ‘get(boost::edge_bundle, g.ContigGraph >::, DirectedGraph::edge_iterator(eit))’ | 182 | const EP& ep = get(edge_bundle, g, eit); | |~~~^ | In file included from GraphIO.h:8: | DotIO.h: In instantiation of ‘void write_edges(std::ostream&, const Graph&, typename boost::graph_traits::vertex_descriptor, const EdgeProp*) [with Graph = ContigGraph >; EdgeProp = DistanceEst; std::ostream = std::basic_ostream; typename boost::graph_traits::vertex_descriptor = ContigNode]’: | DotIO.h:110:14: required from ‘std::ostream& write_dot(std::ostream&, const Graph&, const std::string&) [with Graph = ContigGraph >; std::ostream = std::basic_ostream; std::string = std::__cxx11::basic_string]’ | DotIO.h:77:18: required from ‘std::ostream& write_dot(std::ostream&, const Graph&) [with Graph = ContigGraph >; std::ostream = std::basic_ostream]’ | DotIO.h:125:26: required from ‘std::ostream& operator<<(std::ostream&, const DotWriter > >&)’ | GraphIO.h:33:14: required from ‘std::ostream& write_graph(std::ostream&, const Graph&, const std::string&, const std::string&) [with Graph = ContigGraph >; std::ostream = std::basic_ostream; std::string = std::__cxx11::basic_string]’ | todot.cc:186:14: required from here | DotIO.h:44:43: error: possibly dangling reference to a temporary [-Werror=dangling-reference] |44 | const edge_property_type& ep = get(edge_bundle, g, e); | | ^~ | DotIO.h:44:51: note: the temporary was destroyed at the end of the full expression ‘get >(boost::edge_bundle, (* & g), DirectedGraph::out_edge_iterator(e))’ |44 | const edge_property_type& ep = get(edge_bundle, g, e); | |~~~^~~ | DotIO.h: In instantiation of ‘void write_edges(std::ostream&, const Graph&, typename boost::graph_traits::vertex_descriptor, const EdgeProp*) [with Graph = ContigGraph >; EdgeProp = Distance; std::ostream = std::basic_ostream; typename boost::graph_traits::vertex_descriptor = ContigNode]’: | DotIO.h:110:14: required from ‘std::ostream& write_dot(std::ostream&, const Graph&, const std::string&) [with Graph = ContigGraph >; std::ostream = std::basic_ostream; std::string = std::__cxx11::basic_string]’ | DotIO.h:77:18: required from ‘std::ostream& write_dot(std::ostream&, const Graph&) [with Graph = ContigGraph >; std::ostream = std::basic_ostream]’ | DotIO.h:125:26: required from ‘std::ostream& operator<<(std::ostream&, const DotWriter > >&)’ | GraphIO.h:33:14: required from ‘std::ostream&
