Bug#1003897: marked as done (acpi: ACPI errors at startup)
Your message dated Tue, 25 Jan 2022 09:32:10 +0100 with message-id and subject line Re: Bug#1003897: acpi: ACPI errors at startup has caused the Debian Bug report #1003897, regarding acpi: ACPI errors at startup 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.) -- 1003897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: acpi Version: 1.7-1.1 Severity: grave Justification: causes non-serious data loss X-Debbugs-Cc: garraudmag...@hotmail.fr Dear Maintainer, I have moved some weeks ago from Windows to Debian. I'm almost happy with that but i still face an issue during the boot with ACPI. I have updated the Bios with latest Dell firmware without any change. Could anyone help me understanding the error bug message and how to fix it please ? Here is my config : Dell Inc. Latitude 5424 Rugged Memory : 31.2 GiB Processor : Intel® Core™ i7-8650U CPU @ 1.90GHz × 8 Graphics : AMD® Radeon 500 series / Mesa Intel® UHD Graphics 620 (KBL GT2) Disk : 1.0 TB NVME OS : Debian GNU/Linux bookworm/sid version testing OS type : 64 bits Gnome : 41.2 And here are the dmesg | grep error messages : [ 0.317572] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.317623] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.317672] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.349328] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.349375] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.349419] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.401925] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.401949] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 0.401969] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.542739] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.542846] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.542945] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.571399] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.575373] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.579438] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.657970] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.660572] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 1.663228] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Thanks in advance, -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages acpi depends on: ii libc6 2.33-2 acpi recommends no packages. acpi suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Hi, On Mon, Jan 17, 2022 at 09:10:23PM +0100, FrancoisG wrote: > Package: acpi > Version: 1.7-1.1 > Severity: grave > Justification: causes non-serious data loss > X-Debbugs-Cc: garraudmag...@hotmail.fr > > Dear Maintainer, > I have moved some weeks ago from Windows to Debian. > I'm almost happy with that but i still face an issue during the boot with > ACPI. > I have updated the Bios with latest Dell firmware without any change. > > Could anyone help me understanding
Bug#1000435: Matplotlib crashes on mips64el in lines.py
On Sat, 22 Jan 2022 18:23:13 +0800 YunQiang Su wrote: > On Sat, 22 Jan 2022 17:06:00 +0800 YunQiang Su wrote: >> On Tue, 23 Nov 2021 08:08:23 +0100 Ole Streicher wrote: >>> Source: matplotlib >>> Severity: serious >>> Version: 3.5.0-1 >>> Control: affects -1 yt >>> Control: affects -1 astropy >>> >>> With the new matplotlib version, I now have crashes with a segmentation >>> fault >>> in at least two of my packages on mips64el, which cause a FTBFS: yt and >>> astropy. On both packages, the crash happens here: >>> >>> --8< >>> File "/usr/lib/python3/dist-packages/matplotlib/lines.py", line 840 in >>> draw >>> File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in >>> draw_wrapper >>> File "/usr/lib/python3/dist-packages/matplotlib/axis.py", line 299 in draw >>> File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in >>> draw_wrapper >>> File "/usr/lib/python3/dist-packages/matplotlib/axis.py", line 1163 in >>> draw >>> File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in >>> draw_wrapper >>> File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in >>> _draw_list_compositing_images >>> File "/usr/lib/python3/dist-packages/matplotlib/axes/_base.py", line 3082 >>> in draw >>> File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in >>> draw_wrapper >>> File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in >>> _draw_list_compositing_images >>> File "/usr/lib/python3/dist-packages/matplotlib/figure.py", line 2803 in >>> draw >>> File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in >>> draw_wrapper >>> File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 73 in >>> draw_wrapper >>> File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_agg.py", >>> line 436 in draw >>> --8< >>> >>> Build log on Astropy: >>> https://buildd.debian.org/status/fetch.php?pkg=astropy&arch=mips64el&ver=5.0-1&stamp=1637626067&raw=0 >>> >>> Build log on yt: >>> https://buildd.debian.org/status/fetch.php?pkg=yt&arch=mips64el&ver=4.0.1-3&stamp=1637588650&raw=0 >>> >>> This happens on both Python 3.9 and 3.10. The I will try to create a >>> stacktrace for it. >>> >> >> It is due to gcc-11 of mips64el. >> >> -O1, -O2 may generate bad code, while -O0 and -O3 works well. >> As a workaround: we can: >> >> The attachment is a workaround patch. >> > > > > A better formatted patch with DEB__MAINT_APPEND Should I NMU this package? > >>>
Processed: tagging 1004272, severity of 1004272 is critical, affects 1004272
Processing commands for cont...@bugs.debian.org: > tags 1004272 + security Bug #1004272 [src:binutils] binutils: missing RELRO header Added tag(s) security. > severity 1004272 critical Bug #1004272 [src:binutils] binutils: missing RELRO header Severity set to 'critical' from 'serious' > affects 1004272 src:glibc Bug #1004272 [src:binutils] binutils: missing RELRO header Added indication that 1004272 affects src:glibc > thanks Stopping processing here. Please contact me if you need assistance. -- 1004272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004272 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): forcibly merging 1003847 1003875
Processing commands for cont...@bugs.debian.org:
> forcemerge 1003847 1003875
Bug #1003847 {Done: Aurelien Jarno } [glibc] binutils
breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and
others)
Unable to merge bugs because:
package of #1003875 is 'src:glibc' not 'glibc'
Failed to forcibly merge 1003847: Did not alter merged bugs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1003847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003847
1003875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 1003847 to src:glibc, forcibly merging 1003847 1003875
Processing commands for cont...@bugs.debian.org:
> reassign 1003847 src:glibc
Bug #1003847 {Done: Aurelien Jarno } [glibc] binutils
breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and
others)
Bug reassigned from package 'glibc' to 'src:glibc'.
No longer marked as found in versions glibc/2.29-1.
No longer marked as fixed in versions glibc/2.33-3.
> forcemerge 1003847 1003875
Bug #1003847 {Done: Aurelien Jarno } [src:glibc] binutils
breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and
others)
Bug #1003875 [src:glibc] binutils - autopktest fails on ppc64el: Error:
unrecognized opcode: `vspltisb'
Marked Bug as done
Added indication that 1003875 affects gcc-11,gcc-10
Added tag(s) experimental, bookworm, and sid.
Merged 1003847 1003875
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1003847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003847
1003875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found 1003847 in 2.29-1, fixed 1003847 in 2.33-3
Processing commands for cont...@bugs.debian.org:
> found 1003847 2.29-1
Bug #1003847 {Done: Aurelien Jarno } [src:glibc] binutils
breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and
others)
Bug #1003875 {Done: Aurelien Jarno } [src:glibc] binutils -
autopktest fails on ppc64el: Error: unrecognized opcode: `vspltisb'
Marked as found in versions glibc/2.29-1 and reopened.
Marked as found in versions glibc/2.29-1 and reopened.
> fixed 1003847 2.33-3
Bug #1003847 [src:glibc] binutils breaks glibc autopkgtest on ppc64el:
unrecognized opcode: `vspltisb' (and others)
Bug #1003875 [src:glibc] binutils - autopktest fails on ppc64el: Error:
unrecognized opcode: `vspltisb'
Marked as fixed in versions glibc/2.33-3.
Marked as fixed in versions glibc/2.33-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1003847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003847
1003875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 1003875
Processing commands for cont...@bugs.debian.org: > close 1003875 2.33-3 Bug #1003875 [src:glibc] binutils - autopktest fails on ppc64el: Error: unrecognized opcode: `vspltisb' Bug #1003847 [src:glibc] binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others) Ignoring request to alter fixed versions of bug #1003875 to the same values previously set Ignoring request to alter fixed versions of bug #1003847 to the same values previously set Bug #1003875 [src:glibc] binutils - autopktest fails on ppc64el: Error: unrecognized opcode: `vspltisb' Bug #1003847 [src:glibc] binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others) Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1003847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003847 1003875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995242: isc-dhcp-server: omshell returns inconsistent results or segfaults
I temporarily switched our servers to the source package version of isc-dhcp-server (4.4.2) and the same issue doesn't happens, so I assume this is a problem with the Debian version of the package. The servers are now running on Debian 11 without issues (the only problematic package in the transition from debian 10 to debian 11 was isc-dhcp-server). -- __ Andrea Turbiglio Università degli Studi dell’Insubria Centro Sistemi Informativi e Comunicazione Servizio Telecomunicazioni - Gestione Rete Dati di Ateneo Via Valleggio, 11 22100 - COMO tel. +39 031 238 9784 fax +39 031 238 9709 web www.uninsubria.it mail andrea.turbig...@uninsubria.it mail netw...@uninsubria.it
Bug#1003661: marked as done (Pillow claims GIF frame to be mode RGB instead of P)
Your message dated Tue, 25 Jan 2022 11:33:45 + with message-id and subject line Bug#1003661: fixed in img2pdf 0.4.2-2 has caused the Debian Bug report #1003661, regarding Pillow claims GIF frame to be mode RGB instead of P 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.) -- 1003661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:img2pdf Version: 0.4.2-1 Severity: serious Tags: sid bookworm img2pdf's autopkg tests fail with pillow 9.0.0, as seen at https://tracker.debian.org/pkg/img2pdf === short test summary info FAILED src/img2pdf_test.py::test_general[animation.gif-internal] - AssertionE... FAILED src/img2pdf_test.py::test_general[animation.gif-pikepdf] - AssertionEr... ERROR src/img2pdf_test.py::test_gif_animation[internal] - TypeError: object i... ERROR src/img2pdf_test.py::test_gif_animation[pikepdf] - TypeError: object is... there is a new upstream version available. --- End Message --- --- Begin Message --- Source: img2pdf Source-Version: 0.4.2-2 Done: Johannes Schauer Marin Rodrigues We believe that the bug you reported is fixed in the latest version of img2pdf, 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 1003...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Johannes Schauer Marin Rodrigues (supplier of updated img2pdf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Jan 2022 12:13:50 +0100 Source: img2pdf Architecture: source Version: 0.4.2-2 Distribution: unstable Urgency: medium Maintainer: Johannes Schauer Marin Rodrigues Changed-By: Johannes Schauer Marin Rodrigues Closes: 1003661 1004087 Changes: img2pdf (0.4.2-2) unstable; urgency=medium . * skip test breaking with Pillow 9.0.0 (closes: #1004087, #1003661) Checksums-Sha1: 0987fcedfedd4102384d3bf4a19e4eda94a5ace4 2908 img2pdf_0.4.2-2.dsc f9dadff81fdff82f817cce7ab579dfda80d1f447 11200 img2pdf_0.4.2-2.debian.tar.xz Checksums-Sha256: 7850a37c16ee1be119bd19e2c9df48bb60af9b12443a0b3387042e2ca8814c66 2908 img2pdf_0.4.2-2.dsc ca24fc2cfd1daac6f847f64aaff03760ed56c1975bad5fccffd3ab202f228fac 11200 img2pdf_0.4.2-2.debian.tar.xz Files: fccaec304cdd222a743d9340416307e0 2908 python optional img2pdf_0.4.2-2.dsc 7c800423b8000f0950f0da5af7624ceb 11200 python optional img2pdf_0.4.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmHv2+4ACgkQ8sulx4+9 g+FXMRAApESHAqFP7bNz0kMgnPPoHTr0QHEe52v/HzQVF9UfSk5MusKDKL5jgGGU bezIubqw1KnO16G0DxO22qAUNrS1KcM9yWV0J+fcaVE3rYN7cI4+ZB6cP98KbvLQ ePrXU6yAMk77q2xvjcdGWJSb0ghoWVApiCEflcUOTL72zTI6IARvYqbJDzrBqNjI bNqmgCbc1ARC0iucvW4mFfOEsLI5SWOkOkWoVQfBy2sBxMQ+Mx/ZSnjtmNk3CDMF xPO42E9KMvkpIUlAJqUS8E+Hk40x+5gbvwdwPD9gBF3pAktERVYyffX8y6aQlhPI Ea3U3M0hEJmPQjudQjAnHua8HAs6LUU20Q6bE6Tea4nwV4yfL8iZczrcshxtEbdV U6RuN98CWsqt8aICgKYDwz28+55vkxqZgu3dC+eP/bRzW4oYl/SWXHnX/Ax7ldNL 28cHFZx81nVTyaWzv6kGk7qp2jOFpWCOJ/dvRwkvGVnwXE1MkLB+B04qggIjheIW QyRpkGTZfMyEwxxbTMZucZOzCeg8juUVUVfY6WBGfs38/mfo3XbeC9+udSYIWTIn PxV5TNdga0dGCQ9xEn20+YSvBeDd7udRtj/pCNGe8/MRG4RzoPest6HO+I6E1ggy CGSdLu/nxBi0Km0I7/lijIF4oE0YL+6a1vZ1oQIHbzzY7UMQZ3k= =wroU -END PGP SIGNATURE End Message ---
Bug#1004087: marked as done (pillow breaks img2pdf autopkgtest: TypeError: object is not an array)
Your message dated Tue, 25 Jan 2022 11:33:45 +
with message-id
and subject line Bug#1004087: fixed in img2pdf 0.4.2-2
has caused the Debian Bug report #1004087,
regarding pillow breaks img2pdf autopkgtest: TypeError: object is not an array
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.)
--
1004087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pillow, img2pdf
Control: found -1 pillow/9.0.0-1
Control: found -1 img2pdf/0.4.2-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of pillow the autopkgtest of img2pdf fails in
testing when that autopkgtest is run with the binary packages of pillow
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
pillow from testing9.0.0-1
img2pdffrom testing0.4.2-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of pillow to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=pillow
https://ci.debian.net/data/autopkgtest/testing/amd64/i/img2pdf/18501325/log.gz
= test session starts
==
platform linux -- Python 3.9.9, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
rootdir: /tmp/autopkgtest-lxc.e_87xohl/downtmp/build.JA2/src
collected 301 items
src/img2pdf_test.py
[ 17%]
EE..
[ 41%]
[ 65%]
[ 89%]
.FF..
[100%]
ERRORS
ERROR at setup of test_gif_animation[internal]
tmp_path_factory = TempPathFactory(_given_basetemp=None,
_trace=,
_basetemp=PosixPath('/tmp/pytest-of-debci/pytest-0'))
gif_animation_img =
PosixPath('/tmp/pytest-of-debci/pytest-0/gif_animation_img0/in.gif')
request = test_gif_animation[internal]>>
@pytest.fixture(scope="session", params=["internal", "pikepdf"])
def gif_animation_pdf(tmp_path_factory, gif_animation_img, request):
tmpdir = tmp_path_factory.mktemp("gif_animation_pdf")
out_pdf = tmpdir / "out.pdf"
subprocess.check_call(
[
img2pdfprog,
"--producer=",
"--nodate",
"--engine=" + request.param,
"--output=" + str(out_pdf),
str(gif_animation_img),
]
)
pdfinfo = subprocess.check_output(["pdfinfo", str(out_pdf)])
assert re.search(
"^Pages: +2$", pdfinfo.decode("utf8"), re.MULTILINE
), identify.decode("utf8")
subprocess.check_call(["pdfseparate", str(out_pdf), str(tmpdir
/ "page-%d.pdf")])
for page in [1, 2]:
gif_animation_pdf_nr = tmpdir / ("page-%d.pdf" % page)
with pikepdf.open(gif_animation_pdf_nr) as p:
assert (
p.pages[0].Contents.read_bytes()
== b"q\n45. 0 0 45. 0. 0. cm\n/Im0
Do\nQ"
)
assert
p.pages[0].Resources.XObject.Im0.BitsPerComponent == 8
assert p.pages[0].Resources.XObject.Im0.ColorSpace[0] ==
"/Indexed"
E TypeError: object is not an array
src/img2pdf_test.py:4697: TypeError
ERROR at setup of test_gif_animation[pikepdf]
_
tmp_path_factory = TempPathFactory(_given_basetemp=None,
_trace=,
_basetemp=PosixPath('/tmp/pytest-of-debci/pytest-0'))
gif_animation_img =
PosixPath('/tmp/pytest-of-debci/pytest-0/gif_animation_img0/in.gif')
request = test_gif_animation[pikepdf]>>
@pytest.fixture(scope="session", params=["internal", "pikepdf"])
def gif_animation_pdf(tmp_path_factory, gif_animation_img, re
Bug#1004337: glade: FTBFS in unstable and testing
Source: glade Version: 3.38.2-6 Severity: serious Tags: ftbfs bookworm sid Hi Maintainer Since sometime around January 13, glade started to FTBFS in unstable [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/glade.html env[PKG_CONFIG_PATH]: Called `/usr/bin/pkg-config --variable=targets gdk-3.0` -> 0 x11 broadway wayland Got pkgconfig variable targets : x11 broadway wayland Configuring org.gnome.Glade.desktop.in using configuration ../data/meson.build:4:5: ERROR: Function does not take positional arguments. dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dauto_features=enabled -Dgtk_doc=true returned exit code 1 make[1]: *** [debian/rules:27: override_dh_auto_configure] Error 25 make[1]: Leaving directory '/build/1st/glade-3.38.2' make: *** [debian/rules:24: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Bug#1004337: marked as pending in glade
Control: tag -1 pending Hello, Bug #1004337 in glade 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/gnome-team/glade/-/commit/8ce10c43b346eba48c5c21fde103d400434733fe Cherry-pick proposed patches to fix build with latest meson Closes: #1004337 (this message was generated automatically) -- Greetings https://bugs.debian.org/1004337
Processed: Bug#1004337 marked as pending in glade
Processing control commands: > tag -1 pending Bug #1004337 [src:glade] glade: FTBFS in unstable and testing Added tag(s) pending. -- 1004337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004337: marked as done (glade: FTBFS in unstable and testing)
Your message dated Tue, 25 Jan 2022 12:18:40 + with message-id and subject line Bug#1004337: fixed in glade 3.38.2-7 has caused the Debian Bug report #1004337, regarding glade: FTBFS in unstable and testing 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.) -- 1004337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glade Version: 3.38.2-6 Severity: serious Tags: ftbfs bookworm sid Hi Maintainer Since sometime around January 13, glade started to FTBFS in unstable [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/glade.html env[PKG_CONFIG_PATH]: Called `/usr/bin/pkg-config --variable=targets gdk-3.0` -> 0 x11 broadway wayland Got pkgconfig variable targets : x11 broadway wayland Configuring org.gnome.Glade.desktop.in using configuration ../data/meson.build:4:5: ERROR: Function does not take positional arguments. dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dauto_features=enabled -Dgtk_doc=true returned exit code 1 make[1]: *** [debian/rules:27: override_dh_auto_configure] Error 25 make[1]: Leaving directory '/build/1st/glade-3.38.2' make: *** [debian/rules:24: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: glade Source-Version: 3.38.2-7 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of glade, 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 1004...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated glade package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Jan 2022 07:07:51 -0500 Source: glade Built-For-Profiles: noudeb Architecture: source Version: 3.38.2-7 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Closes: 1004337 Changes: glade (3.38.2-7) unstable; urgency=medium . * Cherry-pick proposed patches to fix build with latest meson (Closes: #1004337) Checksums-Sha1: 9b8312910450d4346f3ea010272a55f0e5b5a090 2926 glade_3.38.2-7.dsc 8419eafd0e0468000e558a88b206d8de27144b84 23624 glade_3.38.2-7.debian.tar.xz d30057a55df5178677c96bc5f6d21fc938bb3432 17713 glade_3.38.2-7_source.buildinfo Checksums-Sha256: 1432ebbb6ab4328da64e9dd29609c5e62ada6323faca9b8fa7d7680b9d252ab8 2926 glade_3.38.2-7.dsc 00c97172f1ef055c5014612d29d723dc566ec2e0842ddc7e14c164dc62d72db7 23624 glade_3.38.2-7.debian.tar.xz 8c6c510b0e3a9c0edb30985164be10804045d033994616006dcb788c744dc49f 17713 glade_3.38.2-7_source.buildinfo Files: 06881fbfa92efdd05b9299a1b48b5648 2926 gnome optional glade_3.38.2-7.dsc 190e90df41487f2c31123ef2677c8d18 23624 gnome optional glade_3.38.2-7.debian.tar.xz bdc9e551b59efb1863c5e09ec4be2eda 17713 gnome optional glade_3.38.2-7_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmHv6DgACgkQ5mx3Wuv+ bH2AaBAA4yGjK6crmXhVzivsLgAF3n4apNOTdCAROoZb1zWPyEdb6o96/nlHiSZm pGfPal/Jfk74GNAunAl4/WBufoq/eDalX0Fiv2ap4xDEfdIDy3G+BjaZR52FVzNK neTshsViBC7sEWuC/+fHxrxnPKJrC9BxrlcfwIEpqmFsiOYVaxt6H8P+p/UyMjeW NdCX/FdVjzI1/JpRn4NqxTDHh5e4/5qypt7QSLrlYvzU/SjFN1qlOCvDRDacMRTO dgPI+8UAbZxbB1+/cU3aSVye+48ta2rxYMwj4z7Pyc99bmEGrmPNeNagTEDOhlpL SIuKMAHYeusMNubGgQeXmIY/ONTLgzei9u6a8z0S2Bi1WR6ZY3MQ8qLgwxlc3GyT 1KeIIwWNwYiHYi0llnadq0oUoziXJDhCf5Ki9jDjDMbSpiqfpLjU1FJXnZl4qM5n fx/5LxOAIcD12hgDo5Wh06HlEFTuCKN5d2zh6svyCPmecoFy3U8NWmsveVcXmF9f ogHRgLenstzOhRXc+o5AC+miJXAskl4V39IG8rkNIyTiwsYXlJW+9JQsgQwqN5Gy dEWcueFgfnIeijQVs3UMeMz7MR/FfBhTNQ2ntLf9lARGFgYW3YoDGkDZy8AXHiv8 AETYgO/0/YMTCrgx1DuLl9BxdBiErdRPEN+VPqldjQpNZEQ+Tiw= =c6CS -END PGP SIGNATURE End Message ---
Bug#1004340: pitivi: FTBFS in unstable and testing
Source: pitivi Version: 2020.09.2-3 Severity: serious Tags: ftbfs bookworm sid Hi Maintainer Since sometime around January 15, pitivi started to FTBFS in unstable [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/pitivi.html Found pkg-config: /usr/bin/pkg-config (0.29.2) Run-time dependency python-3.9-embed found: YES 3.9 Run-time dependency gstreamer-1.0 found: YES 1.18.5 Run-time dependency cairo found: YES 1.16.0 Run-time dependency py3cairo found: YES 1.20.1 Program getenvvar.py found: YES (/build/pitivi-2020.09.2/getenvvar.py) WARNING: You should add the boolean check kwarg to the run_command call. It currently defaults to false, but it will default to true in future releases of meson. See also: https://github.com/mesonbuild/meson/issues/9300 Configuring configure.py using configuration Configuring pitivi using configuration data/meson.build:9:0: ERROR: Function does not take positional arguments. A full log can be found at /build/pitivi-2020.09.2/deb-build/meson-logs/meson-log.txt make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 1 make[1]: Leaving directory '/build/pitivi-2020.09.2' make: *** [debian/rules:12: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Bug#1004340: marked as done (pitivi: FTBFS in unstable and testing)
Your message dated Tue, 25 Jan 2022 14:36:25 + with message-id and subject line Bug#1004340: fixed in pitivi 2021.05-1 has caused the Debian Bug report #1004340, regarding pitivi: FTBFS in unstable and testing 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.) -- 1004340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pitivi Version: 2020.09.2-3 Severity: serious Tags: ftbfs bookworm sid Hi Maintainer Since sometime around January 15, pitivi started to FTBFS in unstable [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/pitivi.html Found pkg-config: /usr/bin/pkg-config (0.29.2) Run-time dependency python-3.9-embed found: YES 3.9 Run-time dependency gstreamer-1.0 found: YES 1.18.5 Run-time dependency cairo found: YES 1.16.0 Run-time dependency py3cairo found: YES 1.20.1 Program getenvvar.py found: YES (/build/pitivi-2020.09.2/getenvvar.py) WARNING: You should add the boolean check kwarg to the run_command call. It currently defaults to false, but it will default to true in future releases of meson. See also: https://github.com/mesonbuild/meson/issues/9300 Configuring configure.py using configuration Configuring pitivi using configuration data/meson.build:9:0: ERROR: Function does not take positional arguments. A full log can be found at /build/pitivi-2020.09.2/deb-build/meson-logs/meson-log.txt make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 1 make[1]: Leaving directory '/build/pitivi-2020.09.2' make: *** [debian/rules:12: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: pitivi Source-Version: 2021.05-1 Done: Sebastian Dröge We believe that the bug you reported is fixed in the latest version of pitivi, 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 1004...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Dröge (supplier of updated pitivi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Jan 2022 15:31:37 +0200 Source: pitivi Architecture: source Version: 2021.05-1 Distribution: unstable Urgency: medium Maintainer: Sebastian Dröge Changed-By: Sebastian Dröge Closes: 1004340 Changes: pitivi (2021.05-1) unstable; urgency=medium . * New upstream release. * debian/patches/0003-meson-0.61.patch: + Fix compatibility with meson 0.61 (Closes: #1004340). Checksums-Sha1: f77d4ca4b66f4967844a941b56e10a2704ed14ed 2337 pitivi_2021.05-1.dsc 41827e4b05d3a6c96b2b8b474715a11a393d6d4d 11303884 pitivi_2021.05.orig.tar.xz 5abd76a2dd211c79e143ca544f8744a041c5c56a 8632 pitivi_2021.05-1.debian.tar.xz a659138a365d70a6c95fd9f417169faaabe1aecb 22936 pitivi_2021.05-1_amd64.buildinfo Checksums-Sha256: 2e1043e4ab714d8ea5ab6445f5e6d5e2d80e12e818b2144e09423d0b748eaae7 2337 pitivi_2021.05-1.dsc cf5693c46c42ab0da14a2e59bfcf4bc880604b41e9cd3aa8d2ebdc60827b75c7 11303884 pitivi_2021.05.orig.tar.xz cef62b2965e3f93864aefa0a9a1d6fb6137345a322ca254d4f5e1a87f901a7c4 8632 pitivi_2021.05-1.debian.tar.xz bb3b79e5817f46d1f93f3d23313f64c2732d0613426a5b197d4c758be2f5bb1b 22936 pitivi_2021.05-1_amd64.buildinfo Files: d71b76aed39f919c126d3c23487d6c37 2337 gnome optional pitivi_2021.05-1.dsc fec14b7bd1822b414f371e72a4b93cc8 11303884 gnome optional pitivi_2021.05.orig.tar.xz 5fb15ecb55d2250ebd2e002a6080d334 8632 gnome optional pitivi_2021.05-1.debian.tar.xz 30ac6991076c50c23a5744f362303c8f 22936 gnome optional pitivi_2021.05-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEEf0vHzDygb5cza7/rBmjMFIbC17UFAmHwAKZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDdG NEJDN0NDM0NBMDZGOTczMzZCQkZFQjA2NjhDQzE0ODZDMkQ3QjUSHHNsb21vQGNv YXhpb24ubmV0AAoJEAZozBSGwte1jc4QANFkG+uU4uqRzc7Mt1YQtXFwuYBZ7Iq8 pzfckyQ/h6fXLXZ78rpyWrcdlqrOsqWzLXyatxvGYkY3Zt+nWow0+n+lIHoeO+jB Vy724goY8Qg4FhBk94NnsksrZibCPLX0f+kGPD/HULXu27yavveAcURLSpKv8C8i dnpL+sp2YsIHdfdicomVoNit8VTRl95T9T/5I+
Bug#997367: virt-manager: FTBFS: AssertionError: Command was: ./virt-xml test-for-virtxml --print-diff --define --add-device --host-device usb_device_4b3_4485_noserial --connect __virtinst_test__test:
Hi, I saw that remain few days for autoremoval from testing I prepared an MR with some upstream patch that solve current FTBFS with some tests and another small fix for a crash case: https://salsa.debian.org/libvirt-team/virt-manager/-/merge_requests/12 can someone merge it and do a new build upload including it please? OpenPGP_signature Description: OpenPGP digital signature
Bug#983985: bctoolbox: ftbfs with GCC-11
X-Debbugs-CC: Bastian Germann On Mon, Jan 24, 2022 at 08:18:02PM +0100, Bastian Germann wrote: > Upstream has that fixed with > https://gitlab.linphone.org/BC/public/bctoolbox/-/commit/9ac0e412c45bf28d02829e9d912342359714f638 Thanks for the effort (and the NMU). I'm currently in the process of preparing linphone 5.0.37 and dependencies which will take care of this. Regards.
Bug#1004356: ruby-gitlab-license-finder: missing Breaks+Replaces: ruby-license-finder (<< 6)
Package: ruby-gitlab-license-finder Version: 6.14.2.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package ruby-gitlab-license-finder. Preparing to unpack .../ruby-gitlab-license-finder_6.14.2.1-1_all.deb ... Unpacking ruby-gitlab-license-finder (6.14.2.1-1) ... dpkg: error processing archive /var/cache/apt/archives/ruby-gitlab-license-finder_6.14.2.1-1_all.deb (--unpack): trying to overwrite '/usr/bin/license_finder', which is also in package ruby-license-finder 2.1.2-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/ruby-gitlab-license-finder_6.14.2.1-1_all.deb ruby-license-finder (2.1.2-2) is an RC buggy stale package in sid and should probably be removed. It may be a predecessor of the newly packaged ruby-gitlab-license-finder ... The (<< 6) is based on the fact that uscan reports a new upstream 6.15.0 for src:ruby-license-finder. cheers, Andreas ruby-license-finder=2.1.2-2_ruby-gitlab-license-finder=6.14.2.1-1.log.gz Description: application/gzip
Bug#999240: sc: missing required debian/rules targets build-arch and/or build-indep
Hi all,
I've updated debian/rules and fixes this bug.
I'll wait for 10 days if no other comments.
And then start the NMU process.
The NMU will be uploaded to DELAY/10.
Attachment is the debdiff.
The following changes are made:
* Change debhelper compat version from 5 to 11. (Closes: #999240)
- Update debian/rules.
+ This also fixes FTCBFS (Closes: #884727)
- Clean files by debian/clean
* Add debian/patches/hardening: hardening format strings.
* Merge patches from Ubuntu. (Closes: #815936)
* Add autopkgtest
Yours,
Paul
diff -Nru sc-7.16/debian/changelog sc-7.16/debian/changelog
--- sc-7.16/debian/changelog2014-05-19 04:13:43.0 +0800
+++ sc-7.16/debian/changelog2022-01-26 01:22:23.0 +0800
@@ -1,3 +1,20 @@
+sc (7.16-4.1) unstable; urgency=low
+
+ [ Ying-Chun Liu (PaulLiu) ]
+ * Non-maintainer upload.
+ * Change debhelper compat version from 5 to 11. (Closes: #999240)
+- Update debian/rules.
+ + This also fixes FTCBFS (Closes: #884727)
+- Clean files by debian/clean
+ * Add debian/patches/hardening: hardening format strings.
+ * Merge patches from Ubuntu. (Closes: #815936)
+ * Add autopkgtest
+
+ [ Serge Hallyn ]
+ * lex.c: do not set notimeout (LP: #1549665)
+
+ -- Ying-Chun Liu (PaulLiu) Wed, 26 Jan 2022 01:22:23
+0800
+
sc (7.16-4) unstable; urgency=low
* debian/patches/function_definitions
diff -Nru sc-7.16/debian/clean sc-7.16/debian/clean
--- sc-7.16/debian/clean1970-01-01 08:00:00.0 +0800
+++ sc-7.16/debian/clean2022-01-25 22:44:34.0 +0800
@@ -0,0 +1,3 @@
+sc
+psc
+scqref
diff -Nru sc-7.16/debian/compat sc-7.16/debian/compat
--- sc-7.16/debian/compat 2010-05-04 04:51:06.0 +0800
+++ sc-7.16/debian/compat 2022-01-25 22:46:13.0 +0800
@@ -1 +1 @@
-7
+11
diff -Nru sc-7.16/debian/control sc-7.16/debian/control
--- sc-7.16/debian/control 2014-05-19 04:06:22.0 +0800
+++ sc-7.16/debian/control 2022-01-25 22:46:26.0 +0800
@@ -1,7 +1,7 @@
Source: sc
Section: math
Priority: optional
-Build-Depends: libncurses5-dev, bison, debhelper (>>7)
+Build-Depends: libncurses5-dev, bison, debhelper (>= 11)
Maintainer: Adam Majer
Standards-Version: 3.9.5
Vcs-Browser: http://git.debian.org/?p=collab-maint/sc.git;a=summary
diff -Nru sc-7.16/debian/patches/hardening sc-7.16/debian/patches/hardening
--- sc-7.16/debian/patches/hardening1970-01-01 08:00:00.0 +0800
+++ sc-7.16/debian/patches/hardening2022-01-26 00:26:25.0 +0800
@@ -0,0 +1,189 @@
+Description: hardening format string
+ We should not pass strings as format string directly.
+Author: Ying-Chun Liu (PaulLiu)
+Last-Update: 2021-01-26
+Index: sc-7.16/cmds.c
+===
+--- sc-7.16.orig/cmds.c
sc-7.16/cmds.c
+@@ -324,7 +324,7 @@ deleterow(register int arg)
+ rs = rs > 0 ? rs : 0;
+ (void) sprintf(buf, "Can't delete %d row%s %d row%s left", arg,
+ (arg != 1 ? "s," : ","), rs, (rs != 1 ? "s" : ""));
+- error(buf);
++ error("%s", buf);
+ return;
+ }
+ if (fr) {
+@@ -486,7 +486,7 @@ yankrow(int arg)
+ rs = rs > 0 ? rs : 0;
+ (void) sprintf(buf, "Can't yank %d row%s %d row%s left", arg,
+ (arg != 1 ? "s," : ","), rs, (rs != 1 ? "s" : ""));
+- error(buf);
++ error("%s", buf);
+ return;
+ }
+ sync_refs();
+@@ -541,7 +541,7 @@ yankcol(int arg)
+ cs = cs > 0 ? cs : 0;
+ (void) sprintf(buf, "Can't yank %d column%s %d column%s left", arg,
+ (arg != 1 ? "s," : ","), cs, (cs != 1 ? "s" : ""));
+- error(buf);
++ error("%s", buf);
+ return;
+ }
+ sync_refs();
+@@ -1212,7 +1212,7 @@ closecol(int arg)
+ cs = cs > 0 ? cs : 0;
+ (void) sprintf(buf, "Can't delete %d column%s %d column%s left", arg,
+ (arg != 1 ? "s," : ","), cs, (cs != 1 ? "s" : ""));
+- error(buf);
++ error("%s", buf);
+ return;
+ }
+ if (any_locked_cells(0, curcol, maxrow, curcol + arg - 1)) {
+Index: sc-7.16/interp.c
+===
+--- sc-7.16.orig/interp.c
sc-7.16/interp.c
+@@ -1986,7 +1986,7 @@ str_search(char *s, int firstrow, int fi
+ scxfree(s);
+ tmp = scxmalloc((size_t)160);
+ regerror(errcode, &preg, tmp, sizeof(tmp));
+- error(tmp);
++ error("%s", tmp);
+ scxfree(tmp);
+ return;
+ }
+Index: sc-7.16/sc.c
+===
+--- sc-7.16.orig/sc.c
sc-7.16/sc.c
+@@ -511,7 +511,7 @@ main (int argc, char **argv)
+ break;
+ }
+ }
+- if (redraw) printf(redraw);
++ if (redraw) printf("%s", redraw);
+ exit (0);
+ }
+
+Index: sc-7.16/screen.c
+===
+--- sc-7.16.orig/screen.c
sc-7.16/screen.c
+@@
Bug#983985: bctoolbox: ftbfs with GCC-11
X-Debbugs-CC: Andrea Pappacoda On Tue, 25 Jan 2022 18:13:01 +0100 Dennis Filder wrote: X-Debbugs-CC: Bastian Germann On Mon, Jan 24, 2022 at 08:18:02PM +0100, Bastian Germann wrote: > Upstream has that fixed with > https://gitlab.linphone.org/BC/public/bctoolbox/-/commit/9ac0e412c45bf28d02829e9d912342359714f638 Thanks for the effort (and the NMU). I'm currently in the process of preparing linphone 5.0.37 and dependencies which will take care of this. Do you mean the NMU that was uploaded at https://mentors.debian.net/package/bctoolbox? That was not uploaded by me.
Processed: archiving 1002175
Processing commands for cont...@bugs.debian.org:
> archive 1002175
Bug #1002175 {Done: Andrej Shadura } [src:docker-compose]
docker-compose: FTBFS: AttributeError: 'NoneType' object has no attribute
'split'
archived 1002175 to archive/75 (from 1002175)
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: pahole segfaults during kernel build
Processing control commands: > severity -1 serious Bug #1004311 [pahole] pahole segfaults during kernel build Severity set to 'serious' from 'normal' -- 1004311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983985: bctoolbox: ftbfs with GCC-11
X-Debbugs-CC: Andrea Pappacoda , Bastian Germann On Tue, Jan 25, 2022 at 07:07:44PM +0100, Bastian Germann wrote: > Do you mean the NMU that was uploaded at > https://mentors.debian.net/package/bctoolbox? > That was not uploaded by me. No, I actually meant the mediastreamer2 NMU last November, but thanks for putting this on my radar. @Andrea: I'm currently in the process of packaging the current AppImage's version of linphone-desktop and all its dependencies, but that will still take a couple of days (at least) before it's finished and then some time till it gets uploaded. It will however take care of #983985. If you want to participate in the on-going maintenance of linphone you can always contact us. Regards.
Processed: update bts with meta info
Processing commands for cont...@bugs.debian.org:
> reassign 1004087 src:img2pdf 0.4.2-1
Bug #1004087 {Done: Johannes Schauer Marin Rodrigues }
[src:pillow, src:img2pdf] pillow breaks img2pdf autopkgtest: TypeError: object
is not an array
Bug reassigned from package 'src:pillow, src:img2pdf' to 'src:img2pdf'.
No longer marked as found in versions pillow/9.0.0-1 and img2pdf/0.4.2-1.
No longer marked as fixed in versions img2pdf/0.4.2-2.
Bug #1004087 {Done: Johannes Schauer Marin Rodrigues }
[src:img2pdf] pillow breaks img2pdf autopkgtest: TypeError: object is not an
array
Marked as found in versions img2pdf/0.4.2-1.
> fixed 1004087 0.4.2-2
Bug #1004087 {Done: Johannes Schauer Marin Rodrigues }
[src:img2pdf] pillow breaks img2pdf autopkgtest: TypeError: object is not an
array
Marked as fixed in versions img2pdf/0.4.2-2.
> affects 1004087 src:pillow
Bug #1004087 {Done: Johannes Schauer Marin Rodrigues }
[src:img2pdf] pillow breaks img2pdf autopkgtest: TypeError: object is not an
array
Added indication that 1004087 affects src:pillow
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1004087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1004360: src:astroscrappy: fails to migrate to testing for too long: FTBFS on mipsel and autopkgtest regression
Source: astroscrappy Version: 1.0.8-1 Severity: serious Control: close -1 1.1.0-1 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1001491 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:astroscrappy has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package fails to build from source on mipsel, has an unfulfilled Build Dependency on mips64el and has an autopkgtest regressions on armhf. 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 bookworm, 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/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=astroscrappy OpenPGP_signature Description: OpenPGP digital signature
Processed: src:astroscrappy: fails to migrate to testing for too long: FTBFS on mipsel and autopkgtest regression
Processing control commands:
> close -1 1.1.0-1
Bug #1004360 [src:astroscrappy] src:astroscrappy: fails to migrate to testing
for too long: FTBFS on mipsel and autopkgtest regression
Marked as fixed in versions astroscrappy/1.1.0-1.
Bug #1004360 [src:astroscrappy] src:astroscrappy: fails to migrate to testing
for too long: FTBFS on mipsel and autopkgtest regression
Marked Bug as done
> block -1 by 1001491
Bug #1004360 {Done: Paul Gevers } [src:astroscrappy]
src:astroscrappy: fails to migrate to testing for too long: FTBFS on mipsel and
autopkgtest regression
1004360 was not blocked by any bugs.
1004360 was not blocking any bugs.
Added blocking bug(s) of 1004360: 1001491
--
1004360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1000435: Matplotlib crashes on mips64el in lines.py
Sandro, Looks like Yunqiang has a patch that fixed the problem. Can you add this patch and upload? Would you allow them to NMU? (See the mail below) Thanks, -Nilesh On Tue, 25 Jan 2022 16:58:34 +0800 Yunqiang Su wrote: > On Sat, 22 Jan 2022 18:23:13 +0800 YunQiang Su wrote: > > On Sat, 22 Jan 2022 17:06:00 +0800 YunQiang Su wrote: > >> On Tue, 23 Nov 2021 08:08:23 +0100 Ole Streicher > >> wrote: > >>> Source: matplotlib > >>> Severity: serious > >>> Version: 3.5.0-1 > >>> Control: affects -1 yt > >>> Control: affects -1 astropy > >>> > >>> With the new matplotlib version, I now have crashes with a segmentation > >>> fault > >>> in at least two of my packages on mips64el, which cause a FTBFS: yt and > >>> astropy. On both packages, the crash happens here: > >>> > >>> --8< > >>> File "/usr/lib/python3/dist-packages/matplotlib/lines.py", line 840 in > >>> draw > >>> File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in > >>> draw_wrapper > >>> File "/usr/lib/python3/dist-packages/matplotlib/axis.py", line 299 in > >>> draw > >>> File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in > >>> draw_wrapper > >>> File "/usr/lib/python3/dist-packages/matplotlib/axis.py", line 1163 in > >>> draw > >>> File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in > >>> draw_wrapper > >>> File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in > >>> _draw_list_compositing_images > >>> File "/usr/lib/python3/dist-packages/matplotlib/axes/_base.py", line > >>> 3082 in draw > >>> File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in > >>> draw_wrapper > >>> File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in > >>> _draw_list_compositing_images > >>> File "/usr/lib/python3/dist-packages/matplotlib/figure.py", line 2803 > >>> in draw > >>> File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in > >>> draw_wrapper > >>> File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 73 in > >>> draw_wrapper > >>> File > >>> "/usr/lib/python3/dist-packages/matplotlib/backends/backend_agg.py", line > >>> 436 in draw > >>> --8< > >>> > >>> Build log on Astropy: > >>> https://buildd.debian.org/status/fetch.php?pkg=astropy&arch=mips64el&ver=5.0-1&stamp=1637626067&raw=0 > >>> > >>> Build log on yt: > >>> https://buildd.debian.org/status/fetch.php?pkg=yt&arch=mips64el&ver=4.0.1-3&stamp=1637588650&raw=0 > >>> > >>> This happens on both Python 3.9 and 3.10. The I will try to create a > >>> stacktrace for it. > >>> > >> > >> It is due to gcc-11 of mips64el. > >> > >> -O1, -O2 may generate bad code, while -O0 and -O3 works well. > >> As a workaround: we can: > >> > >> The attachment is a workaround patch. > >> > > > > > > > > A better formatted patch with DEB__MAINT_APPEND > > Should I NMU this package? signature.asc Description: PGP signature
Bug#1000435: Matplotlib crashes on mips64el in lines.py
> It is due to gcc-11 of mips64el. > > -O1, -O2 may generate bad code, while -O0 and -O3 works well. > As a workaround: we can: > > The attachment is a workaround patch. is there a bug against gcc-11 that i can track so that i dont have to keep this workaround forever but just until it's fixed in the right package? thanks -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Processed: tagging 1004285, tagging 1004340, tagging 1002246
Processing commands for cont...@bugs.debian.org:
> tags 1004285 + sid bookworm
Bug #1004285 [davical] davical: problems after upgrade to php 8, calendar
clients reports "500"
Added tag(s) sid and bookworm.
> tags 1004340 + experimental
Bug #1004340 {Done: Sebastian Dröge } [src:pitivi] pitivi:
FTBFS in unstable and testing
Added tag(s) experimental.
> tags 1002246 + experimental
Bug #1002246 {Done: Shengjing Zhu } [src:containerd]
containerd: FTBFS:
src/github.com/containerd/containerd/vendor/k8s.io/client-go/util/workqueue/default_rate_limiters.go:24:2:
cannot find package "golang.org/x/time/rate"
Added tag(s) experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002246
1004285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004285
1004340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: update bts with meta info
Processing commands for cont...@bugs.debian.org:
> reassign 1002532 src:ruby-pygments.rb 1.2.1-2
Bug #1002532 {Done: Mattia Rizzolo } [src:pygments,
src:ruby-pygments.rb] pygments breaks ruby-pygments.rb autopkgtest: UTF-8 !=
ASCII-8BIT
Bug reassigned from package 'src:pygments, src:ruby-pygments.rb' to
'src:ruby-pygments.rb'.
No longer marked as found in versions ruby-pygments.rb/1.2.1-2 and
pygments/2.10.0+dfsg-1.
No longer marked as fixed in versions ruby-pygments.rb/2.3.0+ds-1.
Bug #1002532 {Done: Mattia Rizzolo } [src:ruby-pygments.rb]
pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT
Marked as found in versions ruby-pygments.rb/1.2.1-2.
> fixed 1002532 2.3.0+ds-1
Bug #1002532 {Done: Mattia Rizzolo } [src:ruby-pygments.rb]
pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT
Marked as fixed in versions ruby-pygments.rb/2.3.0+ds-1.
> affects 1002532 src:pygments
Bug #1002532 {Done: Mattia Rizzolo } [src:ruby-pygments.rb]
pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT
Added indication that 1002532 affects src:pygments
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1004194: marked as done (loguru: CVE-2022-0329)
Your message dated Tue, 25 Jan 2022 21:26:18 + with message-id and subject line Bug#1004194: fixed in loguru 0.5.3-5 has caused the Debian Bug report #1004194, regarding loguru: CVE-2022-0329 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.) -- 1004194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: loguru Version: 0.5.3-4 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/Delgan/loguru/issues/563 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for loguru. CVE-2022-0329[0]: | Code Injection in PyPi loguru prior to and including 0.5.3. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-0329 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0329 [1] https://github.com/Delgan/loguru/issues/563 [2] https://github.com/delgan/loguru/commit/4b0070a4f30cbf6d5e12e6274b242b62ea11c81b Regards, Salvatore --- End Message --- --- Begin Message --- Source: loguru Source-Version: 0.5.3-5 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of loguru, 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 1004...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated loguru package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 26 Jan 2022 02:06:39 +0530 Source: loguru Architecture: source Version: 0.5.3-5 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Nilesh Patra Closes: 1004194 Changes: loguru (0.5.3-5) unstable; urgency=medium . * Team Upload. * Add patch to fix code injection vulnerability (Closes: #1004194) + Fixes CVE: CVE-2022-0329 Checksums-Sha1: 9b4f5f18e83b0fc825b745132d066f4dfc75d1e7 2179 loguru_0.5.3-5.dsc a19035e2fa8597795821deca6c9a9cbd5c3d51e6 4984 loguru_0.5.3-5.debian.tar.xz 0adbe08736708d27ed072bb1815914bd5d33a867 7460 loguru_0.5.3-5_amd64.buildinfo Checksums-Sha256: 4cd19a4a215a51846650b3578a897c399801481b10a4b2733428ff7d5c4aadaa 2179 loguru_0.5.3-5.dsc e48b6bfb817bbedf9ecaa9629405a13dbffe2f10a5018abafeec0ad319cc4e24 4984 loguru_0.5.3-5.debian.tar.xz cd59ede0b257527bdf655359fd1e4de54d5e15e07339d7e6c4996af732e202ff 7460 loguru_0.5.3-5_amd64.buildinfo Files: 9c7219dc73cfea6740d888ba7c2edd29 2179 python optional loguru_0.5.3-5.dsc d6e0e6eef4c28b6804efa53dbf62eebf 4984 python optional loguru_0.5.3-5.debian.tar.xz 4028e541b879e19a8afea680b60367a0 7460 python optional loguru_0.5.3-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmHwYqISHG5pbGVzaEBk ZWJpYW4ub3JnAAoJEAC650s0M2nxE7sP/1BK7jNU6LVZTGpx2dL8Cw1GGIKBIpgo ++WQk/f/Md8MOqjfdyb559KNjiO+rteedttc6J17C9i3P1en/0zPqqLw7H0nI+XB jPwDj4t3GMm7tXJGvEdudM7DnlNUY5GzLiaMnGWUjo87tA1yoU363HZ+Gz7GVw+X QGkyVUb+KvesW6AlKxVORAXy+PU9gXPndS+ibhw4e5x2LUl0/Kza/0dCc7WR4Qhn APr3BWv7fxl9f0UTW/XwDlwunI0C3oDYGAXbofZwIWc3TBryz8qWHBnlSsm4acBL 6quLrqYd/g9IgosBjaEcI0FjFItx4bRpjYGt6llGHQwBXU33u8B4KIG83ZCAm42s k8pLuxg9i721xst/RDuPOKOgwtyOL6YVZplglbqbySEKD9s0MxlYSDtO78eRJGT6 HizndiE0pm5FiWZbebschvPyQkg45ghAVIaHYkrCpW8G48acFUXacWxpthYcBC+I AMy4/2QTFoAUGCLh+WZS8EumjRjLVRzHvcJ+rdSuIFUpTeHCF8Z4bVs2bkExhL3g drPY2/41HmJxucUjzD71Vf5cJaD/v36Pzl64jIIACGtNSsVKjAlt/7GEdK6VPlII 7N8K0YkqyLZgjWABcSIigDnh+lHi317VxQnHmjp7we4TJD/MIKwdj0RBDLqeuYsx lxUhuUBolyf0 =v5Cw -END PGP SIGNATURE End Message ---
Bug#1003979: arachne-pnr build-depends on removed package
Hi peter, On Tue, 18 Jan 2022 21:10:35 + peter green wrote: > Package: arachne-pnr > Version: 0.1+20190728gitc40fb22-2 > Tags: bookworm, sid > Severity: serious > > arachne-pnr build-depends on fpga-icestorm-chipdb which is no longer built by > the fpga-icestorm source package, Admittedly, I do not understand this very well, I do see this binary package being built by the buildd machine here: https://buildd.debian.org/status/fetch.php?pkg=fpga-icestorm&arch=all&ver=0%7E20220102git3b7b199-3&stamp=1642690494&raw=0 > it is still present in unstable as a cruft > package, but is completely gone from testing. I do see the binary package in testing as well: https://packages.debian.org/bookworm/fpga-icestorm-chipdb I even see this in testing $ sudo apt-get --simulate install fpga-icestorm-chipdb Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libc-devtools libu2f-udev Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: fpga-icestorm-chipdb 0 upgraded, 1 newly installed, 0 to remove and 1138 not upgraded. Inst fpga-icestorm-chipdb (0~20220102git3b7b199-3 Debian:testing [all]) Conf fpga-icestorm-chipdb (0~20220102git3b7b199-3 Debian:testing [all]) Could you please clarify this bug report a little? Regards, Nilesh signature.asc Description: PGP signature
Bug#999240: sc: missing required debian/rules targets build-arch and/or build-indep
On 1/25/22 18:48, Ying-Chun Liu (PaulLiu) wrote: I've updated debian/rules and fixes this bug. I'll wait for 10 days if no other comments. You are more than welcome to upload without delay queue. The patch looks good, especially the work you did to isolate the messages from the format parser. Thanks! - Adam
Processed: affects 1004311
Processing commands for cont...@bugs.debian.org: > affects 1004311 + src:linux Bug #1004311 [pahole] pahole segfaults during kernel build Added indication that 1004311 affects src:linux > thanks Stopping processing here. Please contact me if you need assistance. -- 1004311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1000435 marked as pending in matplotlib
Processing control commands: > tag -1 pending Bug #1000435 [src:matplotlib] Matplotlib crashes on mips64el in lines.py Bug #1000774 [src:matplotlib] python3-matplotlib: Segfault on mips64el in draw Added tag(s) pending. Added tag(s) pending. -- 1000435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000435 1000774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000435: marked as pending in matplotlib
Control: tag -1 pending Hello, Bug #1000435 in matplotlib 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/matplotlib/-/commit/39ef996d3ceefa42fa7858db68ec4fe25b22b49d workaround a gcc-11 on mips64* architectures by passing -O3; patch by YunQiang Su; Closes: #1000435 (this message was generated automatically) -- Greetings https://bugs.debian.org/1000435
Bug#1000435: marked as done (Matplotlib crashes on mips64el in lines.py)
Your message dated Tue, 25 Jan 2022 22:19:39 + with message-id and subject line Bug#1000435: fixed in matplotlib 3.5.1-2 has caused the Debian Bug report #1000435, regarding Matplotlib crashes on mips64el in lines.py 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.) -- 1000435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: matplotlib Severity: serious Version: 3.5.0-1 Control: affects -1 yt Control: affects -1 astropy With the new matplotlib version, I now have crashes with a segmentation fault in at least two of my packages on mips64el, which cause a FTBFS: yt and astropy. On both packages, the crash happens here: --8< File "/usr/lib/python3/dist-packages/matplotlib/lines.py", line 840 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/matplotlib/axis.py", line 299 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/matplotlib/axis.py", line 1163 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in _draw_list_compositing_images File "/usr/lib/python3/dist-packages/matplotlib/axes/_base.py", line 3082 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in _draw_list_compositing_images File "/usr/lib/python3/dist-packages/matplotlib/figure.py", line 2803 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 73 in draw_wrapper File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_agg.py", line 436 in draw --8< Build log on Astropy: https://buildd.debian.org/status/fetch.php?pkg=astropy&arch=mips64el&ver=5.0-1&stamp=1637626067&raw=0 Build log on yt: https://buildd.debian.org/status/fetch.php?pkg=yt&arch=mips64el&ver=4.0.1-3&stamp=1637588650&raw=0 This happens on both Python 3.9 and 3.10. The I will try to create a stacktrace for it. --- End Message --- --- Begin Message --- Source: matplotlib Source-Version: 3.5.1-2 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of matplotlib, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated matplotlib 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: Tue, 25 Jan 2022 16:55:24 -0500 Source: matplotlib Architecture: source Version: 3.5.1-2 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Closes: 1000435 Changes: matplotlib (3.5.1-2) unstable; urgency=medium . * debian/rules - workaround a gcc-11 on mips64* architectures by passing -O3; patch by YunQiang Su; Closes: #1000435 Checksums-Sha1: 1a0d4a1022b1d33d2434523576e7a5895c05f328 3557 matplotlib_3.5.1-2.dsc 7ce65176a50f8da83258f1671105c2d1cafca093 32024 matplotlib_3.5.1-2.debian.tar.xz 85d914798d0ab0a460b7a3af526004fd9d22da8c 24560 matplotlib_3.5.1-2_source.buildinfo Checksums-Sha256: e0813648a2420a753fb3da50d658087c3240539446046356077d21080476df6d 3557 matplotlib_3.5.1-2.dsc 33520210b45f706be66eed4e9461ec7323a89be136d14be8eab695e09333163b 32024 matplotlib_3.5.1-2.debian.tar.xz c3e3b18ab622923ce58b58b0cc04d4774e1dd903b6ecaa6a0036cf5b011c4e6c 24560 matplotlib_3.5.1-2_source.buildinfo Files: b7f1f005b42c625b0f96aa8fef92d890 3557 python optional matplotlib_3.5.1-2.dsc 40339d9c9b72e13ab1d92cf12c74de32 32024 python optional matplotlib_3.5.1-2.debian.tar.xz 2504d4d212db35a0d3f8f38e3eff34be 24560 python optional matplotlib_3.5.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTG
Bug#1000774: marked as done (python3-matplotlib: Segfault on mips64el in draw)
Your message dated Tue, 25 Jan 2022 22:19:39 + with message-id and subject line Bug#1000435: fixed in matplotlib 3.5.1-2 has caused the Debian Bug report #1000435, regarding python3-matplotlib: Segfault on mips64el in draw 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.) -- 1000435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-matplotlib Version: 3.5.0-2 Severity: serious Justification: FTBFS Affects: deap deap FTBFS on mips64el, in matplotlib, I'd assume this is a matploptlib regression on mips64el: Current thread 0x00fff7382010 (most recent call first): File "/usr/lib/python3/dist-packages/matplotlib/collections.py", line 422 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/matplotlib/collections.py", line 989 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/mpl_toolkits/mplot3d/art3d.py", line 532 in draw File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in _draw_list_compositin g_images File "/usr/lib/python3/dist-packages/matplotlib/axes/_base.py", line 3082 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/mpl_toolkits/mplot3d/axes3d.py", line 469 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 132 in _draw_list_compositin g_images File "/usr/lib/python3/dist-packages/matplotlib/figure.py", line 2803 in draw File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 50 in draw_wrapper File "/usr/lib/python3/dist-packages/matplotlib/artist.py", line 73 in draw_wrapper File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_agg.py", line 436 in draw File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_agg.py", line 540 in print_ png File "/usr/lib/python3/dist-packages/matplotlib/_api/deprecation.py", line 412 in wrapper File "/usr/lib/python3/dist-packages/matplotlib/backend_bases.py", line 1643 in wrapper File "/usr/lib/python3/dist-packages/matplotlib/backend_bases.py", line 2314 in print_figure File "/usr/lib/python3/dist-packages/matplotlib/figure.py", line 3012 in savefig File "/usr/lib/python3/dist-packages/matplotlib/sphinxext/plot_directive.py", line 647 in re nder_figures File "/usr/lib/python3/dist-packages/matplotlib/sphinxext/plot_directive.py", line 789 in ru n File "/usr/lib/python3/dist-packages/matplotlib/sphinxext/plot_directive.py", line 259 in ru n File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 2147 in run_directive File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 2097 in directive File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 2355 in explicit_construct File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 2343 in explicit_markup File "/usr/lib/python3/dist-packages/docutils/statemachine.py", line 451 in check_line File "/usr/lib/python3/dist-packages/docutils/statemachine.py", line 239 in run File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 197 in run File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 282 in nested_parse File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 394 in new_subsection File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 328 in section File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 2770 in underline File "/usr/lib/python3/dist-packages/docutils/statemachine.py", line 451 in check_line File "/usr/lib/python3/dist-packages/docutils/statemachine.py", line 239 in run File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 197 in run File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 282 in nested_parse File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 394 in new_subsection File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 328 in section File "/usr/lib/python3/dist-packages/docutils/parsers/rst/states.py", line 3009 in text File "/usr/lib/python3/dist-packages/docutils/statemachine.py", line 451 in check_line File "/usr/lib/python3/dis
Bug#1003979: marked as done (arachne-pnr build-depends on removed package)
Your message dated Tue, 25 Jan 2022 22:25:23 + with message-id <1a6a09f8-ecf2-6fdc-80d1-299cdf38c...@p10link.net> and subject line Re: arachne-pnr build-depends on removed package has caused the Debian Bug report #1003979, regarding arachne-pnr build-depends on removed package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1003979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: arachne-pnr Version: 0.1+20190728gitc40fb22-2 Tags: bookworm, sid Severity: serious arachne-pnr build-depends on fpga-icestorm-chipdb which is no longer built by the fpga-icestorm source package, it is still present in unstable as a cruft package, but is completely gone from testing. --- End Message --- --- Begin Message --- On 25/01/2022 21:47, Nilesh Patra wrote: Could you please clarify this bug report a little? Doing some further investigation, it seems I was right about the package being missing from testing at the time I filed the bugs against arachne-pnr and nextpnr, but I was wrong about why it was missing from testing. Specifically, It looks like the arch all builds for versions 0~20220102git3b7b199-1 and 0~20220102git3b7b199-2 of the fpga-icestorm source package failed. I would have expected this to result in the testing migration of fpga-icestorm being blocked, but instead it seems britney decided to migrate version 0~20220102git3b7b199-1 to testing and remove the the outdated fpga-icestorm-chipdb from testing, leaving the build-depends of arachne-pnr and nextpnr unsatisfiable in testing. Since I filed the bugs, version 0~20220102git3b7b199-3 of the fpga-icestorm source package was uploaded fixing the arch all build, this has now migrated to testing and so the build-dependencies of arachne-pnr and nextpnr are once again satisfiable in testing. Closing the bugs.--- End Message ---
Bug#1003981: marked as done (nextpnr build-depends on removed package)
Your message dated Tue, 25 Jan 2022 22:25:23 + with message-id <1a6a09f8-ecf2-6fdc-80d1-299cdf38c...@p10link.net> and subject line Re: arachne-pnr build-depends on removed package has caused the Debian Bug report #1003981, regarding nextpnr build-depends on removed package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1003981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nextpnr Version: 0.0~git20210102.9b96280-1 Tags: bookworm, sid Severity: serious nextpnr build-depends on fpga-icestorm-chipdb which is no longer built by the fpga-icestorm source package, it is still present in unstable as a cruft package, but is completely gone from testing. --- End Message --- --- Begin Message --- On 25/01/2022 21:47, Nilesh Patra wrote: Could you please clarify this bug report a little? Doing some further investigation, it seems I was right about the package being missing from testing at the time I filed the bugs against arachne-pnr and nextpnr, but I was wrong about why it was missing from testing. Specifically, It looks like the arch all builds for versions 0~20220102git3b7b199-1 and 0~20220102git3b7b199-2 of the fpga-icestorm source package failed. I would have expected this to result in the testing migration of fpga-icestorm being blocked, but instead it seems britney decided to migrate version 0~20220102git3b7b199-1 to testing and remove the the outdated fpga-icestorm-chipdb from testing, leaving the build-depends of arachne-pnr and nextpnr unsatisfiable in testing. Since I filed the bugs, version 0~20220102git3b7b199-3 of the fpga-icestorm source package was uploaded fixing the arch all build, this has now migrated to testing and so the build-dependencies of arachne-pnr and nextpnr are once again satisfiable in testing. Closing the bugs.--- End Message ---
Bug#993559: marked as done (ganeti-3.0 unable to remove a dpkg-divert during postrm when 2.16 is still there)
Your message dated Tue, 25 Jan 2022 22:48:50 + with message-id and subject line Bug#993559: fixed in ganeti 3.0.1-3 has caused the Debian Bug report #993559, regarding ganeti-3.0 unable to remove a dpkg-divert during postrm when 2.16 is still there 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.) -- 993559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ganeti-3.0 Version: 3.0.1-2 Severity: normal Hello, I've just performed an upgrade of a ganeti cluster from buster+2.16 to bullseye+3.0 and hit a problem during the upgrade. The procedure that I used was to: 1. install ganeti 3.0 from buster-backports and upgrade the cluster 2. run OS upgrade from buster to bullseye (I had not removed ganeti 2.16) During the upgrade to bullseye, ganeti was upgraded from the 3.0 backports package to the same one from bullseye. At that point, dpkg stopped with an error. Running "apt -f install" to fix the situation did not clear things up. Running "apt purge ganeti-2.16 ganeti-haskell-2.16 ganeti-htools-2.16" was jammed on a conflict of configuration files with 3.0: # apt -f install Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: at-spi2-core bsdmainutils libapt-inst2.0 libevent-core-2.1-6 libevent-pthreads-2.1-6 libhogweed4 libnftables0 libprocps7 libreadline5 python3-asn1crypto python3.7 python3.7-minimal Use 'apt autoremove' to remove them. The following additional packages will be installed: ganeti-3.0 The following packages will be upgraded: ganeti-3.0 1 upgraded, 0 newly installed, 0 to remove and 497 not upgraded. 323 not fully installed or removed. Need to get 0 B/876 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Reading changelogs... Done Preconfiguring packages ... (Reading database ... 64433 files and directories currently installed.) Preparing to unpack .../ganeti-3.0_3.0.1-2_all.deb ... Unpacking ganeti-3.0 (3.0.1-2) over (3.0.1-1~bpo10+1) ... Removing 'diversion of /usr/share/ganeti/2.16/ganeti/utils/version.py to /usr/share/ganeti/2.16/ganeti/utils/version.py.orig by ganeti-3.0' dpkg-divert: error: rename involves overwriting '/usr/share/ganeti/2.16/ganeti/utils/version.py' with different file '/usr/share/ganeti/2.16/ganeti/utils/version.py.orig', not allowed dpkg: warning: old ganeti-3.0 package post-removal script subprocess returned error exit status 2 dpkg: trying script from the new package instead ... Removing 'diversion of /usr/share/ganeti/2.16/ganeti/utils/version.py to /usr/share/ganeti/2.16/ganeti/utils/version.py.orig by ganeti-3.0' dpkg-divert: error: rename involves overwriting '/usr/share/ganeti/2.16/ganeti/utils/version.py' with different file '/usr/share/ganeti/2.16/ganeti/utils/version.py.orig', not allowed dpkg: error processing archive /var/cache/apt/archives/ganeti-3.0_3.0.1-2_all.deb (--unpack): new ganeti-3.0 package post-removal script subprocess returned error exit status 2 Removing 'diversion of /usr/share/ganeti/2.16/ganeti/utils/version.py to /usr/share/ganeti/2.16/ganeti/utils/version.py.orig by ganeti-3.0' dpkg-divert: error: rename involves overwriting '/usr/share/ganeti/2.16/ganeti/utils/version.py' with different file '/usr/share/ganeti/2.16/ganeti/utils/version.py.orig', not allowed dpkg: error while cleaning up: new ganeti-3.0 package post-removal script subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/ganeti-3.0_3.0.1-2_all.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) In order to get out of that situation, we had to modify the postrm script in /var/lib/dpkg/info/ganeti-3.0.postrm to comment out the dpkg-diver --remove command. That permitted the package to finish upgrading and the os upgrade to complete. Once the upgrade was completed, I was able to purge ganeti 2.16 (and I had to manually remove the diversion that was left behind) I'm guessing this happened because the ganeti 2.16 packages were still in place. But it was a situation quite difficult to work around of. I'm wondering if something can be done to avoid this situation. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CP
Bug#997053: marked as done (ganeti FTBFS: doc/index.rst:94:duplicated entry found in toctree: design-location)
Your message dated Tue, 25 Jan 2022 22:48:50 + with message-id and subject line Bug#997053: fixed in ganeti 3.0.1-3 has caused the Debian Bug report #997053, regarding ganeti FTBFS: doc/index.rst:94:duplicated entry found in toctree: design-location 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.) -- 997053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ganeti Version: 3.0.1-2 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/logs.php?pkg=ganeti&ver=3.0.1-2%2Bb1 ... Linking src/hluxid ... cp -pf src/hluxid src/ganeti-luxid PYTHONPATH=. ./autotools/run-in-tempdir \ /<>/./autotools/build-bash-completion --compact > doc/examples/bash_completion PYTHONPATH=. ./autotools/run-in-tempdir \ /<>/./autotools/build-bash-completion > doc/examples/bash_completion-debug Warning, treated as error: /tmp/gntbuild.EVcbAb3N/doc/index.rst:94:duplicated entry found in toctree: design-location make[2]: *** [Makefile:4241: doc/html/index.html] Error 2 --- End Message --- --- Begin Message --- Source: ganeti Source-Version: 3.0.1-3 Done: Apollon Oikonomopoulos We believe that the bug you reported is fixed in the latest version of ganeti, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Apollon Oikonomopoulos (supplier of updated ganeti 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, 16 Dec 2021 14:22:41 +0200 Source: ganeti Architecture: source Version: 3.0.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Ganeti Team Changed-By: Apollon Oikonomopoulos Closes: 993559 997053 140 Changes: ganeti (3.0.1-3) unstable; urgency=medium . * postrm: remove diversion only on package removal (Closes: #993559) * Restore the diversion on postinst in case it was accidentally removed due to #993559. * Fix FTBFS by removing duplicate index entry. Thanks to Marius Bakke (Closes: #997053) * d/control: remove unnecessary B-D on libpcre3-dev (Closes: #140) * Fix FTBFS with sphinx >= 2.1. Thanks to Sascha Lucas Checksums-Sha1: 3e7d58fead9d7273906206a87e1bd4a1c9107cea 3339 ganeti_3.0.1-3.dsc 59e43d2d341c838e2294c3a9169bfc994a177aee 48208 ganeti_3.0.1-3.debian.tar.xz d12a4062770961c360a9525ac7e7c66d9f60bb72 15744 ganeti_3.0.1-3_amd64.buildinfo Checksums-Sha256: 65737b0c126f6421be06a3f66fc2d5e55ecab9833658a5e0678c998fa397f3d8 3339 ganeti_3.0.1-3.dsc 640583bf40342eb9d661889dd49a8d0273ee449c36f2af29ba8f98839985bb69 48208 ganeti_3.0.1-3.debian.tar.xz fa8f6c3da72ba588cd1e8f0d3841f4c55a2b04bff8aa2d6d8ec72dfdbb968f2c 15744 ganeti_3.0.1-3_amd64.buildinfo Files: 97b8215bd63a2f35baafda722ec53bfa 3339 admin optional ganeti_3.0.1-3.dsc bdf67c7ac931d7ac25d24b8ea3d3cc20 48208 admin optional ganeti_3.0.1-3.debian.tar.xz 3995938f989f4f5b507076ffc3eab6b3 15744 admin optional ganeti_3.0.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEPgL9ZlYpWVIRC6uZ9RsYxyAkgiQFAmHwcKAACgkQ9RsYxyAk giRexRAAswl2IhyQFpE2wo2FTbY+ySae9iiN9wwH1Yz7u2+Ni3rU+dP7U0ewSHke 6ABFPYPXCPE0tHAtyfUiDBgAmy9UKEB7VDOBC3eACaCcgwGb3g9izSYHNdU5PEnO bWiGXm89z6ojEyN6MsSVLr8ZHFzfNAhfM2yM+myUipK4FpHZ6mE66e+8MJgQda2q KFQdISIbnqxmaDXO58gUSsCUQMXK35YwQXLJaVB4jaOt3Nz52ZRn66sz1I6PfDPz FbT3yYHshsYp++s8wGyMlQcFGah7c7EcwR8BbcVHCg08vLcAZ0fgbFcR2zs6cdQA 0H6gNrZ8utfdHfbFekglYkJuEOt6KIbiUljP4xhTw6jNStPNl7Kckk77cYURuOT7 UuRUSpL6KpLIcc97qZd14I264KditnGMWM5+CvTEn0uuFwSk8z601vTq41IFBImO qm69HQrpkZw1Vv2vFjQjy8G95IL9hiO66i2vMRJ22tLbUwfLFuickQFSAzfPTBns VCTiWjJwxRhwFO3bNABWvTqO6BP6RrNCQ7m7eInZ7d0bC1EnAt/lYtYarRUltjwl 27d5QIEi5+RKYQ60gPVCEDHBNYj5I+JiwJ1rtQwcc2TOs8DjyJHVSqIc2b30Rs+m 5FjFbBarYyV7kWd626Ofk95q2XNC2cHdxnJM/RidBYkU7ytXJ8E= =EM/n -END PGP SIGNATURE End Message ---
Bug#1003275: marked as done (mir: FTBFS: /<>/src/client/lttng/input_receiver_report.cpp:80:1: internal compiler error: maximum number of generated reload insns per insn achieved (90))
Your message dated Tue, 25 Jan 2022 23:04:14 + with message-id and subject line Bug#1003275: fixed in mir 1.8.2+dfsg-1 has caused the Debian Bug report #1003275, regarding mir: FTBFS: /<>/src/client/lttng/input_receiver_report.cpp:80:1: internal compiler error: maximum number of generated reload insns per insn achieved (90) 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.) -- 1003275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mir Version: 1.8.0+dfsg1-19 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org mir FTBFS on amd64: | [ 48%] Building CXX object src/client/lttng/CMakeFiles/mirclientlttng-static.dir/shared_library_prober_report.cpp.o | cd /<>/build-amd64/src/client/lttng && /usr/bin/c++ -DCLIENT_PLATFORM_VERSION=\"MIR_CLIENT_PLATFORM_5\" -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_CLIENT_PLATFORM_PATH=\"/usr/lib/x86_64-linux-gnu/mir/client-platform/\" -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"mirclient\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=2 -DMIR_VERSION_MINOR=7 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-amd64/src/capnproto -I/<>/build-amd64/src/protobuf -I/<>/build-amd64/src/client -I/<>/include/platform -I/<>/include/client -I/<>/src/include/client -I/<>/src/include/cookie -I/usr/include/libdrm -I/<>/src/client/lttng -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Wall -fno-strict-aliasing -Wnon-virtual-dtor -Wextra -fPIC -Wno-mismatched-tags -Wno-psabi -flto -ffat-lto-objects -Wno-error=missing-field-initializers -Wno-error=unused-function -std=c++14 -MD -MT src/client/lttng/CMakeFiles/mirclientlttng-static.dir/shared_library_prober_report.cpp.o -MF CMakeFiles/mirclientlttng-static.dir/shared_library_prober_report.cpp.o.d -o CMakeFiles/mirclientlttng-static.dir/shared_library_prober_report.cpp.o -c /<>/src/client/lttng/shared_library_prober_report.cpp | during RTL pass: reload | /<>/src/client/lttng/input_receiver_report.cpp: In member function ‘mir::client::lttng::InputReceiverReport::report_touch(MirInputEvent const*) const’: | /<>/src/client/lttng/input_receiver_report.cpp:80:1: internal compiler error: maximum number of generated reload insns per insn achieved (90) |80 | } | | ^ | 0x7f68588597ec __libc_start_main | ../csu/libc-start.c:332 | Please submit a full bug report, | with preprocessed source if appropriate. | Please include the complete backtrace with any bug report. | See for instructions. See https://buildd.debian.org/status/fetch.php?pkg=mir&arch=amd64&ver=1.8.0%2Bdfsg1-19%2Bb2&stamp=1641511010&raw=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: mir Source-Version: 1.8.2+dfsg-1 Done: Marius Gripsgard We believe that the bug you reported is fixed in the latest version of mir, 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 1003...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marius Gripsgard (supplier of updated mir package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 24 Jan 2022 04:06:33 +0100 Source: mir Architecture: source Version: 1.8.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Mir Team Changed-By: Marius Gripsgard Closes: 1003275 Changes: mir (1.8.2+dfsg-1) unstable; urgency=medium . * New upstream release (v1.8.2) * debian/patches: Drop upstreamed patches + 0001_Fix-Rawhide-FTBFS.patch 0002_Delete-obsolete-gmock-hack.patch 0003_Instantiate-parameterized-test-suite-DisplayOrientat.patch 0004_Add-mis
Bug#1001371: pytest-twisted: (autopkgtest) needs update for python3.10: E {'warnings': 2} != {'warnings': 1}
The upstream report at https://github.com/pytest-dev/pytest-twisted/issues/146 was closed as the additional warning is produced by Twisted. The Twisted fix isn't merged yet. It looks like the twisted fix has now been merged upstream, does it make sense to apply it as a patch to the Debian twisted patch to solve this bug? The removal of pytest-twisted from testing has caused two packages to have uninstallable build-dependencies in testing, graphql-relay and python-promise
Bug#1000818: marked as done (python3-ulmo: if rebuilt now, missing python3-suds dependency)
Your message dated Wed, 26 Jan 2022 00:36:38 + with message-id and subject line Bug#1000818: fixed in python-ulmo 0.8.8+dfsg1-1 has caused the Debian Bug report #1000818, regarding python3-ulmo: if rebuilt now, missing python3-suds dependency to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-ulmo Version: 0.8.5+dfsg1-1 Severity: serious Tags: patch The current binary package has a python3-suds dependency, but the result of building the current source package in current unstable does not. As suds is required to even import ulmo, this causes the autopkgtest to fail. I don't know why this happened, or whether it's likely to affect other packages. The other Depends didn't change. The obvious quick fix is to add an explicit Depends to debian/control. --- End Message --- --- Begin Message --- Source: python-ulmo Source-Version: 0.8.8+dfsg1-1 Done: Kurt Kremitzki We believe that the bug you reported is fixed in the latest version of python-ulmo, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kurt Kremitzki (supplier of updated python-ulmo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Jan 2022 17:07:58 -0600 Source: python-ulmo Architecture: source Version: 0.8.8+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Kurt Kremitzki Closes: 974476 1000818 Changes: python-ulmo (0.8.8+dfsg1-1) unstable; urgency=medium . * [37d3df1] Correct broken d/watch file * [ece673b] New upstream version 0.8.8+dfsg1 * [a04be3c] Add python3-suds runtime dep (Closes: #1000818) * [48e159e] Use @debian.org address for my Uploaders d/control entry * [ca92d60] Run offline upstream tests as autopkgtest (Closes: #974476) * [ec94483] New upstream version 0.8.8+dfsg1 * [465e0a7] Refresh fix-docs-path.patch Checksums-Sha1: df333d27935573418d00634d2b67344c029409ca 2557 python-ulmo_0.8.8+dfsg1-1.dsc 7898c785fc18cdd4fcc8e1f2c79687ddfb89ff06 279752 python-ulmo_0.8.8+dfsg1.orig.tar.xz 24ee75ce6a8b5e4b0355ca3db5033f4560f75151 4620 python-ulmo_0.8.8+dfsg1-1.debian.tar.xz 8eb1b8ba78c9b989f156288fafad6e624de741db 10648 python-ulmo_0.8.8+dfsg1-1_source.buildinfo Checksums-Sha256: e146bf7a1ab4db12e82358bf807a6c39f9615af7a1a52d6ab8d7ee78249b6b02 2557 python-ulmo_0.8.8+dfsg1-1.dsc c2b6efe98ccc45297a82ab240d70a8e280373f2f7ea7284321cf73f7a53f28b8 279752 python-ulmo_0.8.8+dfsg1.orig.tar.xz 6a5a98d4b23111ae81d029d093ece32842b4d53a57458961c379ba32aba6fb92 4620 python-ulmo_0.8.8+dfsg1-1.debian.tar.xz cd35f31ead71da32cdb45807b41fba7c39349e1ffc58863e08efb18c8ea6 10648 python-ulmo_0.8.8+dfsg1-1_source.buildinfo Files: d944d95f497e63eacff3e4676d0d6ae3 2557 python optional python-ulmo_0.8.8+dfsg1-1.dsc f9977cd13c0d64108db777ad8de7cba8 279752 python optional python-ulmo_0.8.8+dfsg1.orig.tar.xz 23e39a9a70508411f557dc6a48c2376a 4620 python optional python-ulmo_0.8.8+dfsg1-1.debian.tar.xz 55109d7e99c59cc5140e66d03936fc59 10648 python optional python-ulmo_0.8.8+dfsg1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEh8RU7HmiYTD5HEfrKUghB0bfc8AFAmHwkM0WHGtrcmVtaXR6 a2lAZGViaWFuLm9yZwAKCRApSCEHRt9zwC72D/46KWSH/hpfVizApPZ6kN3jt8+0 wHgBUFme4yhIDdjZEpvo5EUKmbAjomnzNszMeqRPUjknMisXZNVTzFrfNIGheXSt MmZaJKXeK1j3TvpeyfP35rF5jM5U+WpiJscE7ArZFKloQSp77fYrx4okj8GyXl15 g+IZKCioaAxrkhWOiyw46P401kU74P3Jc3el3pAI5qlUZXOpT2aB7cEwrbBt+NRo /8upIxaX+o+KXlYnN9rwoMDcwTGK8jLdjYTuxnWdJDaWBsPq0KxNzjIbd8oT2ror 4NT+qJobohM6kxXmGP4Hl1geTngd0Yt2PhI83FtaZKeM7TxmcIVVp82jaCxqsJRV wUxnFTAQXhVi7sxHsByVniUrNLcFD0vjmlWNBFDE80ViFxPkyHWkWs5YqQ3q3llt MLrUQDPCP0qJ07ShQg3Pi3od6cg+nsyzl4u8LqtmYll0h2HSQWeCxoUpBUvtsqOz X9qm954zYt1QIIvNDGXOm3mIOZ4NDX8DYXIv6ZWDyCg+/Clcj29MRfL3haJg/sQk qrMn8hzyEZUMmqHWBY2HaZk++mL+V/2mbS24guI4wq3rhHMFz2QSQiLzLJsnjY4S jguRF0FMqKQbjOLL3ZLInjK+VEuKxsSoBil9jnidsaPvf4FyUkKrj1nFF7n+WNXt 08W7vCDClnJ85IBajA== =Oe41 -END PGP SIGNATURE End Messag
Bug#1002090: marked as done (gr-soapy: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create')
Your message dated Wed, 26 Jan 2022 00:39:24 + with message-id and subject line Bug#1004322: Removed package(s) from unstable has caused the Debian Bug report #1002090, regarding gr-soapy: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create' 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.) -- 1002090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gr-soapy Version: 2.1.3.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: CMakeFiles/cmTC_00bf7.dir/src.c.o: in function `main': > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to > `pthread_create' > /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:12: undefined > reference to `pthread_detach' > /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:13: undefined > reference to `pthread_cancel' > /usr/bin/ld: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:14: undefined > reference to `pthread_join' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2021/12/20/gr-soapy_2.1.3.1-1_unstable.log 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 marking 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 --- Version: 2.1.3.1-1+rm Dear submitter, as the package gr-soapy has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1004322 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1004311: [PATCH] add_cmake_libbpf_enabled_option.patch: Only check the macro HAVE_BPF
Control: tag -1 patch
The patch add_cmake_libbpf_enabled_option.patch is indeed the problem,
because it doesn't consistently use the same macro name. The fix is
below.
If you're not able to upload with this today, can I please NMU to
unblock linux?
Ben.
--- a/debian/patches/add_cmake_libbpf_enabled_option.patch
+++ b/debian/patches/add_cmake_libbpf_enabled_option.patch
@@ -5,6 +5,8 @@ Non-linux systems also can make good use of these tools. This
patch
adds option LIBBPF_ENABLED (default: on) so to opt-out BPF when needed.
Signed-off-by: Domenico Andreoli
+[bwh: Only check the macro HAVE_BPF, not HAVE_BTF]
+Signed-off-by: Ben Hutchings
---
CMakeLists.txt | 61
+
dwarves.c |2 ++
@@ -193,7 +195,7 @@ Index: b/pahole.c
cu__fprintf_ptr_table_stats_csv(cu, stderr);
}
-+#ifdef HAVE_BTF
++#ifdef HAVE_BPF
if (btf_encode) {
static pthread_mutex_t btf_lock = PTHREAD_MUTEX_INITIALIZER;
@@ -241,7 +243,7 @@ Index: b/pahole.c
type_instance__delete(header);
header = NULL;
-+#ifdef HAVE_BTF
++#ifdef HAVE_BPF
if (btf_encode) {
err = btf_encoder__encode(btf_encoder);
if (err) {
@@ -257,7 +259,7 @@ Index: b/pahole.c
#ifdef DEBUG_CHECK_LEAKS
cus__delete(cus);
structures__delete();
-+#ifdef HAVE_BTF
++#ifdef HAVE_BPF
btf__free(conf_load.base_btf);
conf_load.base_btf = NULL;
#endif
signature.asc
Description: PGP signature
Processed: [PATCH] add_cmake_libbpf_enabled_option.patch: Only check the macro HAVE_BPF
Processing control commands: > tag -1 patch Bug #1004311 [pahole] pahole segfaults during kernel build Added tag(s) patch. -- 1004311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003490: u-boot: FTBFS on arch:all with qemu-ppce500 target
A bug in Debian is causing a build failure of the qemu-ppce500 target:
https://bugs.debian.org/1003490
I've CCed u-boot in case they're not aware of the issue.
Some background follows...
On 2022-01-15, Aurelien Jarno wrote:
> On 2022-01-11 16:40, Vagrant Cascadian wrote:
>> On 2022-01-11, Lennart Sorensen wrote:
>> > On Mon, Jan 10, 2022 at 05:10:04PM -0800, Vagrant Cascadian wrote:
>> >> Something in the toolchain recently changed which causes u-boot arch:all
>> >> build to FTBFS... I suspect binutils, as building in "bookworm" still
>> >> works fine where binutils hasn't yet migrated.
>> >>
>> >> On arch:all builds the qemu-ppce500 target is cross-compiled.
>> >>
>> >> Full log:
>> >>
>> >>
>> >> https://buildd.debian.org/status/fetch.php?pkg=u-boot&arch=all&ver=2022.01%2Bdfsg-1&stamp=1641860624&raw=0
>> >>
>> >> The hopefully relevent lines from the build log:
>> >>
>> >> powerpc-linux-gnu-gcc -Wp,-MD,arch/powerpc/cpu/mpc85xx/.tlb.o.d
>> >> -nostdinc -isystem /usr/lib/gcc-cross/powerpc-linux-gnu/11/include
>> >> -Iinclude -I/<>/include
>> >> -I/<>/arch/powerpc/include -include
>> >> /<>/include/linux/kconfig.h
>> >> -I/<>/arch/powerpc/cpu/mpc85xx -Iarch/powerpc/cpu/mpc85xx
>> >> -D__KERNEL__ -D__UBOOT__ -Wall -Wstrict-prototypes -Wno-format-security
>> >> -fno-builtin -ffreestanding -std=gnu11 -fshort-wchar -fno-strict-aliasing
>> >> -fno-PIE -Os -fno-stack-protector -fno-delete-null-pointer-checks
>> >> -Wno-pointer-sign -Wno-stringop-truncation -Wno-zero-length-bounds
>> >> -Wno-array-bounds -Wno-stringop-overflow -Wno-maybe-uninitialized
>> >> -fmacro-prefix-map=/<>/= -g -fstack-usage
>> >> -Wno-format-nonliteral -Wno-address-of-packed-member
>> >> -Wno-unused-but-set-variable -Werror=date-time -Wno-packed-not-aligned
>> >> -D__powerpc__ -ffixed-r2 -m32 -fno-ira-hoist-pressure -Wa,-me500
>> >> -msoft-float -mno-string -fpic -mrelocatable -ffunction-sections
>> >> -fdata-sections -mcall-linux -msingle-pic-base -fno-jump-tables -pipe
>> >> -DKBUILD_BASENAME='"tlb"' -DKBUILD_MODNAME='"tlb"' -c -o
>> >> arch/powerpc/cpu/mpc85xx/tlb.o
>> >> /<>/arch/powerpc/cpu/mpc85xx/tlb.c
>> >> ...
>> >> {standard input}: Assembler messages:
>> >> {standard input}:127: Error: unrecognized opcode: `tlbre'
>> >> {standard input}:418: Error: unrecognized opcode: `tlbre'
>> >> {standard input}:821: Error: unrecognized opcode: `msync'
>> >> {standard input}:821: Error: unrecognized opcode: `tlbwe'
>> >> {standard input}:884: Error: unrecognized opcode: `tlbsx'
>> >> make[4]: *** [/<>/scripts/Makefile.build:253:
>> >> arch/powerpc/cpu/mpc85xx/tlb.o] Error 1
>> >> make[3]: *** [/<>/Makefile:1810: arch/powerpc/cpu/mpc85xx]
>> >> Error 2
>> >> make[3]: *** Waiting for unfinished jobs
>> >> powerpc-linux-gnu-gcc -Wp,-MD,arch/powerpc/lib/.traps.o.d -nost
...
>> The binutils versions appear to be:
>>
>> succeeding, bookworm 2.37-10.1
>> failing, sid 2.37.50.20220106-2
>>
>
> Yep, this is due to commit b25f942e18d6ecd7ec3e2d2e9930eb4f996c258a on
> the binutils side [1], which changes the behavior of `.machine`
> directives to override, rather than augment, the base CPU. GCC is called
> with -Wa,-me500 to enable PowerPC e500 instructions on the assembler
> side, but as the default GCC machine is ppc, a `.set machine ppc` is
> emitted at the beginning of the assembly code.
>
> One option would be to force the CPU to e500 on the GCC side, however
> support for it has been removed. The options is therefore to force the
> machine in the assembly code. This is what the attached patch does.
Somehow I missed that you had attached a patch! I will try to get this
tested and uploaded to Debian soon...
live well,
vagrant
> --- u-boot-2022.01+dfsg.orig/arch/powerpc/cpu/mpc85xx/tlb.c
> +++ u-boot-2022.01+dfsg/arch/powerpc/cpu/mpc85xx/tlb.c
> @@ -50,7 +50,10 @@ void read_tlbcam_entry(int idx, u32 *val
> u32 _mas1;
>
> mtspr(MAS0, FSL_BOOKE_MAS0(1, idx, 0));
> - asm volatile("tlbre;isync");
> + asm volatile(".machine push;\n"
> + ".machine e500;\n"
> + "tlbre;isync;\n"
> + ".machine pop;\n");
> _mas1 = mfspr(MAS1);
>
> *valid = (_mas1 & MAS1_VALID);
> @@ -109,7 +112,10 @@ void init_used_tlb_cams(void)
> /* walk all the entries */
> for (i = 0; i < num_cam; i++) {
> mtspr(MAS0, FSL_BOOKE_MAS0(1, i, 0));
> - asm volatile("tlbre;isync");
> + asm volatile(".machine push;\n"
> + ".machine e500;\n"
> + "tlbre;isync;\n"
> + ".machine pop;");
> if (mfspr(MAS1) & MAS1_VALID)
> use_tlb_cam(i);
> }
> @@ -183,7 +189,10 @@ void disable_tlb(u8 esel)
> #ifdef CONFIG_ENABLE_36BIT_PHYS
> mtspr(MAS7, 0);
> #endif
> - asm volatile("isync;msync;tlbwe;isync");
> + asm volatile(".machine push;\n"
> + ".machine e500;\n"
> +
Bug#1000435: Matplotlib crashes on mips64el in lines.py
Sandro Tosi 于2022年1月26日周三 05:16写道： > > > It is due to gcc-11 of mips64el. > > > > -O1, -O2 may generate bad code, while -O0 and -O3 works well. > > As a workaround: we can: > > > > The attachment is a workaround patch. > > is there a bug against gcc-11 that i can track so that i dont have to > keep this workaround forever but just until it's fixed in the right > package? thanks > Yes. I cloned this bug as: #1004184 > -- > Sandro "morph" Tosi > My website: http://sandrotosi.me/ > Me at Debian: http://wiki.debian.org/SandroTosi > Twitter: https://twitter.com/sandrotosi -- YunQiang Su
Bug#1003490: u-boot: FTBFS on arch:all with qemu-ppce500 target
On 2022-01-25, Vagrant Cascadian wrote:
> On 2022-01-15, Aurelien Jarno wrote:
>> On 2022-01-11 16:40, Vagrant Cascadian wrote:
>>> On 2022-01-11, Lennart Sorensen wrote:
>>> > On Mon, Jan 10, 2022 at 05:10:04PM -0800, Vagrant Cascadian wrote:
>>> >> Something in the toolchain recently changed which causes u-boot arch:all
>>> >> build to FTBFS... I suspect binutils, as building in "bookworm" still
>>> >> works fine where binutils hasn't yet migrated.
>>> >>
>>> >> On arch:all builds the qemu-ppce500 target is cross-compiled.
>>> >>
>>> >> Full log:
>>> >>
>>> >>
>>> >> https://buildd.debian.org/status/fetch.php?pkg=u-boot&arch=all&ver=2022.01%2Bdfsg-1&stamp=1641860624&raw=0
>>> >>
>>> >> The hopefully relevent lines from the build log:
...
>>> >> {standard input}: Assembler messages:
>>> >> {standard input}:127: Error: unrecognized opcode: `tlbre'
>>> >> {standard input}:418: Error: unrecognized opcode: `tlbre'
>>> >> {standard input}:821: Error: unrecognized opcode: `msync'
>>> >> {standard input}:821: Error: unrecognized opcode: `tlbwe'
>>> >> {standard input}:884: Error: unrecognized opcode: `tlbsx'
>>> >> make[4]: *** [/<>/scripts/Makefile.build:253:
>>> >> arch/powerpc/cpu/mpc85xx/tlb.o] Error 1
>>> >> make[3]: *** [/<>/Makefile:1810: arch/powerpc/cpu/mpc85xx]
>>> >> Error 2
>>> >> make[3]: *** Waiting for unfinished jobs
>>> >> powerpc-linux-gnu-gcc -Wp,-MD,arch/powerpc/lib/.traps.o.d -nost
> ...
>>> The binutils versions appear to be:
>>>
>>> succeeding, bookworm 2.37-10.1
>>> failing, sid 2.37.50.20220106-2
>>>
>>
>> Yep, this is due to commit b25f942e18d6ecd7ec3e2d2e9930eb4f996c258a on
>> the binutils side [1], which changes the behavior of `.machine`
>> directives to override, rather than augment, the base CPU. GCC is called
>> with -Wa,-me500 to enable PowerPC e500 instructions on the assembler
>> side, but as the default GCC machine is ppc, a `.set machine ppc` is
>> emitted at the beginning of the assembly code.
>>
>> One option would be to force the CPU to e500 on the GCC side, however
>> support for it has been removed. The options is therefore to force the
>> machine in the assembly code. This is what the attached patch does.
>
> Somehow I missed that you had attached a patch! I will try to get this
> tested and uploaded to Debian soon...
Your patch fixed building qemu-ppce500, but now I think we have a
potentially similar problem with qemu-riscv64 and qemu-riscv64_smode:
/<>/arch/riscv/cpu/cpu.c: Assembler messages:
/<>/arch/riscv/cpu/cpu.c:94: Error: unrecognized opcode
`csrs sstatus,a5'
/<>/arch/riscv/cpu/cpu.c:95: Error: unrecognized opcode
`csrw 0x003,0'
make[4]: *** [/<>/scripts/Makefile.build:254:
arch/riscv/cpu/cpu.o] Error 1
make[3]: *** [/<>/Makefile:1810: arch/riscv/cpu] Error 2
make[3]: Leaving directory
'/<>/debian/build/qemu-riscv64_smode'
live well,
vagrant
>> --- u-boot-2022.01+dfsg.orig/arch/powerpc/cpu/mpc85xx/tlb.c
>> +++ u-boot-2022.01+dfsg/arch/powerpc/cpu/mpc85xx/tlb.c
>> @@ -50,7 +50,10 @@ void read_tlbcam_entry(int idx, u32 *val
>> u32 _mas1;
>>
>> mtspr(MAS0, FSL_BOOKE_MAS0(1, idx, 0));
>> -asm volatile("tlbre;isync");
>> +asm volatile(".machine push;\n"
>> + ".machine e500;\n"
>> + "tlbre;isync;\n"
>> + ".machine pop;\n");
>> _mas1 = mfspr(MAS1);
>>
>> *valid = (_mas1 & MAS1_VALID);
>> @@ -109,7 +112,10 @@ void init_used_tlb_cams(void)
>> /* walk all the entries */
>> for (i = 0; i < num_cam; i++) {
>> mtspr(MAS0, FSL_BOOKE_MAS0(1, i, 0));
>> -asm volatile("tlbre;isync");
>> +asm volatile(".machine push;\n"
>> + ".machine e500;\n"
>> + "tlbre;isync;\n"
>> + ".machine pop;");
>> if (mfspr(MAS1) & MAS1_VALID)
>> use_tlb_cam(i);
>> }
>> @@ -183,7 +189,10 @@ void disable_tlb(u8 esel)
>> #ifdef CONFIG_ENABLE_36BIT_PHYS
>> mtspr(MAS7, 0);
>> #endif
>> -asm volatile("isync;msync;tlbwe;isync");
>> +asm volatile(".machine push;\n"
>> + ".machine e500;\n"
>> + "isync;msync;tlbwe;isync;\n"
>> + ".machine pop;\n");
>>
>> #ifdef CONFIG_ADDR_MAP
>> if (gd->flags & GD_FLG_RELOC)
>> @@ -193,7 +202,11 @@ void disable_tlb(u8 esel)
>>
>> static void tlbsx (const volatile unsigned *addr)
>> {
>> -__asm__ __volatile__ ("tlbsx 0,%0" : : "r" (addr), "m" (*addr));
>> +__asm__ __volatile__ (".machine push;\n"
>> + ".machine e500;\n"
>> + "tlbsx 0,%0;\n"
>> + ".machine pop;\n"
>> + : : "r" (addr), "m" (*addr));
>> }
>>
>> /* return -1 if we didn't find anything */
signature.asc
Description: PGP signature
Bug#995356: python-parameterized: autopkgtest regression: AssertionError in tearDownModule
> If nobody is going to fix this issue, I am going to upload the package > removing the autopkgtest soon. I took your NMU diff and made it a team upload, thanks! > This issue is blocking migration to > testing for too long. The package can't be easily removed because it's a > key package. is there a publicly available list of key packages? Thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#965802: marked as done (rig: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Wed, 26 Jan 2022 05:50:13 + with message-id and subject line Bug#965802: fixed in rig 1.11-1.1 has caused the Debian Bug report #965802, regarding rig: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rig Version: 1.11-1 Severity: normal Usertags: compat-5-6-removal Hi, The package rig uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: rig Source-Version: 1.11-1.1 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of rig, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated rig 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, 07 Jan 2022 16:18:35 +0800 Source: rig Architecture: source Version: 1.11-1.1 Distribution: unstable Urgency: low Maintainer: Norbert Veber Changed-By: Ying-Chun Liu (PaulLiu) Closes: 946277 965802 999011 Changes: rig (1.11-1.1) unstable; urgency=low . * Non-maintainer upload. * Change debhelper from 5 to 11. (Closes: #965802) - Update debian/rules. (Closes: #999011) + This should also fix FTCBFS (Closes: #946277) - Clean files by debian/clean * Change source package to DebSrc3.0 with quilt. - Split diff.gz to quilt patches. * debian/control: Change priority from extra to optional. * debian/copyright: Change to dep5 machine-readable format. * Add autopkgtest Checksums-Sha1: 74bc5a24b3c035422729d068d72ed0a8030b90d4 1696 rig_1.11-1.1.dsc 21f1237318ba0dd36c8199f0a6dbb9eeb5877268 2996 rig_1.11-1.1.debian.tar.xz 3e830ea053e7d20439c11fe69dd55c9fa117cf6c 6107 rig_1.11-1.1_source.buildinfo Checksums-Sha256: ebf7008647920d3c81d0b3d486bac420f2e495948f283a851ffcbd6930a1cb70 1696 rig_1.11-1.1.dsc 88c177bd84aefe2bed1dac40aa6a0f1ee3a7e8b07a2fb93cb0dd1340787db8a7 2996 rig_1.11-1.1.debian.tar.xz 46c86137ded442407a4bc457bd21235846c5dfef396aee1e7bb999135dd4e6c2 6107 rig_1.11-1.1_source.buildinfo Files: 11308f962453f47c52deb3248094c2d3 1696 misc optional rig_1.11-1.1.dsc c7f45c45a1794452f82fe4cdd7bc3523 2996 misc optional rig_1.11-1.1.debian.tar.xz 2c71b15a88d4162a2c9a5c724c612908 6107 misc optional rig_1.11-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmHjpO8THHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiHtGD/914qQNbI/UUJ8uj1BhYW1NsjKDKEAs bB497UdJqM5W6oeMxq5FRzfdO4XoqKRMBwSdYcZOpGS+89Sak5exmSPyHc+G+D9z LgkQGlbU0dLkHlP8RKKwzeAOV55vdHPbijPTF8YV0Ns+xn84OxWpDL2eNc3LeBcU Xu0MpUIIquA1EI/vinLSwDZ31POlU1OV1AbPrF/Vn7qdQWNacAG4DRSwCAdm783q iPxlH8GaisHDmfdLRhFxmv6HCebt4O6Jp/rjedPaJan4zDFrK4lfSx2YTLGjgKal 6YX1i6ZwyXBNPlMbjjjnb1pMCTRmaPCSNOn9jcDMLOryw2XlMvi5tjyl94eN4kdR D66GmN/lqXSZxjWozwDNPy053UZURCuoNtUkeS21MZkEurNFImTB5t1bFF9tXGVC PxbC5LAoeVw0fWbh28dwq4pJJ/bDX4Pz9QpRbalC4OpqmhXKMwy0Um2Li+4fBnWm WnII4ChiM+X42Y
Bug#999011: marked as done (rig: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Wed, 26 Jan 2022 05:50:13 + with message-id and subject line Bug#999011: fixed in rig 1.11-1.1 has caused the Debian Bug report #999011, regarding rig: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rig Version: 1.11-1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: rig Source-Version: 1.11-1.1 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of rig, 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. Ying-Chun Liu (PaulLiu) (supplier of updated rig 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, 07 Jan 2022 16:18:35 +0800 Source: rig Architecture: source Version: 1.11-1.1 Distribution: unstable Urgency: low Maintainer: Norbert Veber Changed-By: Ying-Chun Liu (PaulLiu) Closes: 946277 965802 999011 Changes: rig (1.11-1.1) unstable; urgency=low . * Non-maintainer upload. * Change debhelper from 5 to 11. (Closes: #965802) - Update debian/rules. (Closes: #999011) + This should also fix FTCBFS (Closes: #946277) - Clean files by debian/clean * Change source package to DebSrc3.0 with quilt. - Split diff.gz to quilt patches. * debian/control: Change priority from extra to optional. * debian/copyright: Change to dep5 machine-readable format. * Add autopkgtest Checksums-Sha1: 74bc5a24b3c035422729d068d72ed0a8030b90d4 1696 rig_1.11-1.1.dsc 21f1237318ba0dd36c8199f0a6dbb9eeb5877268 2996 rig_1.11-1.1.debian.tar.xz 3e830ea053e7d20439c11fe69dd55c9fa117cf6c 6107 rig_1.11-1.1_source.buildinfo Checksums-Sha256: ebf7008647920d3c81d0b3d486bac420f2e495948f283a851ffcbd6930a1cb70 1696 rig_1.11-1.1.dsc 88c177bd84aefe2bed1dac40aa6a0f1ee3a7e8b07a2fb93cb0dd1340787db8a7 2996 rig_1.11-1.1.debian.tar.xz 46c86137ded442407a4bc457bd21235846c5dfef396aee1e7bb999135dd4e6c2 6107 rig_1.11-1.1_source.buildinfo Files: 11308f962453f47c52deb3248094c2d3 1696 misc optional rig_1.11-1.1.dsc c7f45c45a1794452f82fe4cdd7bc3523 2996 misc optional rig_1.11-1.1.debian.tar.xz 2c71b15a88d4162a2c9a5c724c612908 6107 misc optional rig_1.11-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmHjpO8THHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiHtGD/914qQNbI/UUJ8uj1BhYW1NsjKDKEAs bB497UdJqM5W6oeMxq5FRzfdO4XoqKRMBwSdYcZOpGS+89Sak5exmSPyHc+G+D9z LgkQGlbU0dLkHlP8RKKwzeAOV55vdHPbijPTF8YV0Ns+xn84OxWpDL2eNc3LeBcU Xu0MpUIIquA1EI/vinLSwDZ31POlU1OV1AbPrF/Vn7qdQWNacAG4DRSwCAdm783q iPxlH8GaisHDmfdLRhFxmv6HCebt4O6Jp/rjedPaJan4zDFrK4lfSx2YTLGjgKal 6YX1i6ZwyXBNPlMbjjjnb1pMCTRmaPCSNOn9jcDMLOryw2XlMvi5tjyl94eN4kdR D66GmN/lqXSZxjWozwDNPy053UZURCuoNtUkeS21MZkEurNFImTB5t1bFF9tXGVC PxbC5LAoeVw0fWbh28dwq4pJJ/bDX4Pz9QpRbalC4OpqmhXKMwy0Um2Li+4fBnWm WnII4ChiM+X42YVZuGYGdEYfvE5cdsl5/0nB+NHkYHSC7JTCYrSt9cyTPLo1A99r NmRfZCWfHOj7/8q9N1YpL6luhoKRRJt2LCjfpk7hOuLaGQNReKhsIr/S4m2ZWMOI JG+ee3sUYfDAoMpXb1t7/VPjWSKkF8CEd2KRCA7y6ntPUV2X0EiOMgj3Tq5/Ar1Y pmBgwNuM8O9/SA== =Xi9p -END PGP SIGNATURE End Message ---
Bug#998749: firmware-misc-nonfree: i915 freezes randomly in X especially when playing videos
severity 998749 important thanks Hi, * Jonibek Ander uulu [Sun Nov 07, 2021 at 09:45:52PM +0600]: > Package: firmware-misc-nonfree > Version: 20210315-3 > Severity: grave > Justification: renders package unusable I'd assume this bug report needs further information so it can be handled by the kernel team. Furthermore this RC bug ended up removing all src:firmware-nonfree packages from Debian/testing, so I'll hereby downgrade the severity of this bug. regards -mika- signature.asc Description: PGP signature
Processed: Re: Bug#998749: firmware-misc-nonfree: i915 freezes randomly in X especially when playing videos
Processing commands for cont...@bugs.debian.org: > severity 998749 important Bug #998749 [firmware-misc-nonfree] firmware-misc-nonfree: i915 freezes randomly in X especially when playing videos Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 998749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990201: singularity-container: CVE-2021-33622
Hi, just for the record: This CVE is fixed only in the Pro edition[1] but there is no record that the CE edition which we can package is fixed yet. Kind regards Andreas. [1] https://support.sylabs.io/support/solutions/articles/4287130-3-5-8-security-release-cve-2021-33622- -- http://fam-tille.de
Bug#1003490: u-boot: FTBFS on arch:all with qemu-ppce500 target
On 2022-01-25 19:04, Vagrant Cascadian wrote:
> On 2022-01-25, Vagrant Cascadian wrote:
> > On 2022-01-15, Aurelien Jarno wrote:
> >> On 2022-01-11 16:40, Vagrant Cascadian wrote:
> >>> On 2022-01-11, Lennart Sorensen wrote:
> >>> > On Mon, Jan 10, 2022 at 05:10:04PM -0800, Vagrant Cascadian wrote:
> >>> >> Something in the toolchain recently changed which causes u-boot
> >>> >> arch:all
> >>> >> build to FTBFS... I suspect binutils, as building in "bookworm" still
> >>> >> works fine where binutils hasn't yet migrated.
> >>> >>
> >>> >> On arch:all builds the qemu-ppce500 target is cross-compiled.
> >>> >>
> >>> >> Full log:
> >>> >>
> >>> >>
> >>> >> https://buildd.debian.org/status/fetch.php?pkg=u-boot&arch=all&ver=2022.01%2Bdfsg-1&stamp=1641860624&raw=0
> >>> >>
> >>> >> The hopefully relevent lines from the build log:
> ...
> >>> >> {standard input}: Assembler messages:
> >>> >> {standard input}:127: Error: unrecognized opcode: `tlbre'
> >>> >> {standard input}:418: Error: unrecognized opcode: `tlbre'
> >>> >> {standard input}:821: Error: unrecognized opcode: `msync'
> >>> >> {standard input}:821: Error: unrecognized opcode: `tlbwe'
> >>> >> {standard input}:884: Error: unrecognized opcode: `tlbsx'
> >>> >> make[4]: *** [/<>/scripts/Makefile.build:253:
> >>> >> arch/powerpc/cpu/mpc85xx/tlb.o] Error 1
> >>> >> make[3]: *** [/<>/Makefile:1810:
> >>> >> arch/powerpc/cpu/mpc85xx] Error 2
> >>> >> make[3]: *** Waiting for unfinished jobs
> >>> >> powerpc-linux-gnu-gcc -Wp,-MD,arch/powerpc/lib/.traps.o.d -nost
> > ...
> >>> The binutils versions appear to be:
> >>>
> >>> succeeding, bookworm 2.37-10.1
> >>> failing, sid 2.37.50.20220106-2
> >>>
> >>
> >> Yep, this is due to commit b25f942e18d6ecd7ec3e2d2e9930eb4f996c258a on
> >> the binutils side [1], which changes the behavior of `.machine`
> >> directives to override, rather than augment, the base CPU. GCC is called
> >> with -Wa,-me500 to enable PowerPC e500 instructions on the assembler
> >> side, but as the default GCC machine is ppc, a `.set machine ppc` is
> >> emitted at the beginning of the assembly code.
> >>
> >> One option would be to force the CPU to e500 on the GCC side, however
> >> support for it has been removed. The options is therefore to force the
> >> machine in the assembly code. This is what the attached patch does.
> >
> > Somehow I missed that you had attached a patch! I will try to get this
> > tested and uploaded to Debian soon...
>
> Your patch fixed building qemu-ppce500, but now I think we have a
> potentially similar problem with qemu-riscv64 and qemu-riscv64_smode:
>
> /<>/arch/riscv/cpu/cpu.c: Assembler messages:
> /<>/arch/riscv/cpu/cpu.c:94: Error: unrecognized opcode
> `csrs sstatus,a5'
> /<>/arch/riscv/cpu/cpu.c:95: Error: unrecognized opcode
> `csrw 0x003,0'
> make[4]: *** [/<>/scripts/Makefile.build:254:
> arch/riscv/cpu/cpu.o] Error 1
> make[3]: *** [/<>/Makefile:1810: arch/riscv/cpu] Error 2
> make[3]: Leaving directory
> '/<>/debian/build/qemu-riscv64_smode'
I guess this is due to:
http://lists.infradead.org/pipermail/linux-riscv/2022-January/011728.html
Unfortunately as the change has been done in a not yet released binutils
version, there is no way for the fix to have been done upstream yet.
Note that this also breaks at least linux and opensbi.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
signature.asc
Description: PGP signature
