Bug#1032104: linux: ppc64el iouring corrupted read
Any updates on this one? I am still seeing the main.index_merge_innodb failure in https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&ver=1%3A10.11.2-2%7Eexp1&stamp=1678728871&raw=0 and rebuild https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&ver=1%3A10.11.2-2%7Eexp1&stamp=1679174850&raw=0. Logs show: Kernel: Linux 5.10.0-21-powerpc64le #1 SMP Debian 5.10.162-1 (2023-01-21) ppc64el (ppc64le)
Bug#1031657: marked as done (swe-basic-data: missing Breaks+Replaces: swe-standard-data (<< 4.0))
Your message dated Sun, 19 Mar 2023 04:34:15 + with message-id and subject line Bug#1031657: fixed in swe-data 4.0-2022-2 has caused the Debian Bug report #1031657, regarding swe-basic-data: missing Breaks+Replaces: swe-standard-data (<< 4.0) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1031657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: swe-basic-data Version: 4.0-2022-1.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'bullseye'. It installed fine in 'bullseye', then the upgrade to 'bookworm' fails 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...): Preparing to unpack .../swe-basic-data_4.0-2022-1.1_all.deb ... Unpacking swe-basic-data (4.0-2022-1.1) ... dpkg: error processing archive /var/cache/apt/archives/swe-basic-data_4.0-2022-1.1_all.deb (--unpack): trying to overwrite '/usr/share/libswe/ephe/seas_18.se1', which is also in package swe-standard-data 4-1.1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/swe-basic-data_4.0-2022-1.1_all.deb The following files were moved from standard to basic: usr/share/libswe/ephe/seas_18.se1 usr/share/libswe/ephe/seasnam.txt usr/share/libswe/ephe/semo_18.se1 usr/share/libswe/ephe/sepl_18.se1 cheers, Andreas swe-standard-data=4-1.1_swe-basic-data=4.0-2022-1.1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: swe-data Source-Version: 4.0-2022-2 Done: Jaldhar H. Vyas , We believe that the bug you reported is fixed in the latest version of swe-data, 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 1031...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jaldhar H. Vyas , (supplier of updated swe-data 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: Mon, 27 Feb 2023 10:21:27 +0100 Source: swe-data Architecture: source Version: 4.0-2022-2 Distribution: unstable Urgency: medium Maintainer: Stanislas Marquis Changed-By: Jaldhar H. Vyas , Closes: 1031657 Changes: swe-data (4.0-2022-2) unstable; urgency=medium . * Add Replaces+Breaks info to swe-standard-data (closes: #1031657). * Add multiarch hints to swe-basic-data, swe-sat-data. Checksums-Sha1: e8c35d13fa80646b1661038af0a9a642f4740e26 1771 swe-data_4.0-2022-2.dsc c4ea72befb290a45522ce3b5f4c875072fa06072 7600 swe-data_4.0-2022-2.debian.tar.xz 49274515dff974e76a1c1fbb97c1fa9825f3ee6e 6599 swe-data_4.0-2022-2_amd64.buildinfo Checksums-Sha256: 47f9720ca72296c3872399669dc7fa419d808885bbcb763735f1a27ba8ad2a61 1771 swe-data_4.0-2022-2.dsc cfd5269c4ce80a17753f0da50ee7c7fd5d256a72d5aef45f14f6e44b7ea88f1c 7600 swe-data_4.0-2022-2.debian.tar.xz c16f8ac913d84bfc4090e801282620be4023baca22e2f53d83844f724bdc5030 6599 swe-data_4.0-2022-2_amd64.buildinfo Files: 6a8a229f73e1c6e2c2582c4f81be2d70 1771 libs optional swe-data_4.0-2022-2.dsc a2e02a5320b70d99232bbe5f4c83e7d9 7600 libs optional swe-data_4.0-2022-2.debian.tar.xz 38f24112f3b78b9f35ccb92bac10826d 6599 libs optional swe-data_4.0-2022-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEN+9bAhnDDG5HslHQ6qY4+sR5Ta8FAmQWirsACgkQ6qY4+sR5 Ta+dsQf+N9Rdn/vEsldmkYdpvYqhDjm1KaVOYbeLi45k/166AAX0qVyTzgKQrsOh cDjls+OLZDIEPLJqSCJY6er6JTtGWKv1Ae7znf+1OpC5ojZa8v9rISyFBLub+pvd cmnqM8lKbHCRTttdr9nYg54JrOIV6lv8myRTd1+7coCV+O7TkF/qC3yhjdKp2/OT KaCOFjAogAWIUYWwFCn987zN/4tBXx74/KVqDES5GIks+0FkIWcnPqbkJ5aLLUJB KCS+uI9wKSxmTw8tvrsQY1KgEQAEZg5FbcfmaprDGDBzx252rfsK3ez1i1TMmP5P cCZARfDgm9WkfdatnDXhNzWUXFQV3g== =fP9c -END PGP SIGNATURE End Message ---
Processed: Re: Bug#1033175: FTBFS: setup.py install is deprecated
Processing control commands: > notfound -1 0.0.26-3 Bug #1033175 [0ad] FTBFS: setup.py install is deprecated No longer marked as found in versions 0ad/0.0.26-3. > close -1 Bug #1033175 [0ad] FTBFS: setup.py install is deprecated Marked Bug as done -- 1033175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033175: FTBFS: setup.py install is deprecated
Control: notfound -1 0.0.26-3 Control: close -1 On Sat, Mar 18, 2023 at 4:48 PM David W. Kennedy wrote: > > Package: 0ad > Version: 0.0.26-3 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the > past) > X-Debbugs-Cc: dav...@reasoned.us > > Hello, > > When I try to build 0ad version 0.0.26-3 in Debian unstable with > python3.11 and python3-virtualenv, build fails. > > I think that the key error message is > "/usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build > and pip and other standards-based tools." > > The commands that I use to build the package: > > # apt-get update > # apt-get build-dep 0ad > $ apt-get source 0ad > $ cd 0ad-0.0.26 > $ debuild 0ad/0.0.26-3 builds fine for me with an up-to-date pbuilder sid chroot. I highly recommend building packages in a clean chroot environment, using tools such as pbuilder or sbuild. Packages failing to build from source in a dirty environment is not a RC bug and I can't really help you debug why it's not working in your particular environment. Regards, Vincent
Bug#1033167: usrmerge: messes with /etc/shells
On Mar 18, Helmut Grohne wrote: > I think that it is quite obvious that /etc/shells is debianutils' > territory. When I found that on some systems /etc/shells was out of sync > with /var/lib/shells.state, I was quite puzzled until I noticed that > usrmerge messes with this file. This really is debianutils' It is expected that /etc/shells can be edited by system administrators, I have been doing that forever in my career as a professional system administrator and until now I was not even aware of these programs from debianutils. Hence my reasoning that having convert-etc-shells modify the file would not be harmful, and so far I am not aware of any practical problem that this has ever caused. I also see that you wrote update-shells in 2021, but convert-etc-shells was added to usrmerge in 2016. > If and only if usrmerge is used, convert-etc-shells turns /bin/sh into > /usr/bin/sh. So whenever we start out merged and use usr-is-merged, > /usr/bin/sh goes missing. Right. But both update-shells and usr-is-merged are new to bookworm, and I remember that having the /usr/ paths in /etc/shells is not usually needed, so this explains why nobody has reported actual problems so far. > I think the best solution here would be merging convert-etc-shells into > update-shells. No objections if you can do the work, I will not miss it. > Whenever we run update-shells, it should check whether > the system is already merged and when it is, perform the equivalent to > convert-etc-shells. Then usrmerge can just install an empty (except for > a comment) /usr/share/debianutils/shells.d/usrmerge to trigger > update-shells and things become fully reproducible in all cases, because OK. (Also, would you mind moving /var/lib/shells.state to /var/lib/misc/?) -- ciao, Marco signature.asc Description: PGP signature
Bug#1033175: FTBFS: setup.py install is deprecated
Package: 0ad Version: 0.0.26-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: dav...@reasoned.us Hello, When I try to build 0ad version 0.0.26-3 in Debian unstable with python3.11 and python3-virtualenv, build fails. I think that the key error message is "/usr/lib/python3/dist-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools." The commands that I use to build the package: # apt-get update # apt-get build-dep 0ad $ apt-get source 0ad $ cd 0ad-0.0.26 $ debuild Here is an excerpt of the output. [...] patching file python/mozbuild/mozbuild/preprocessor.py patching file python/mozbuild/mozbuild/util.py Creating Python 3 environment /usr/lib/python3/dist-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools. warnings.warn( created virtual environment CPython3.11.2.final.0-64 in 139ms creator CPython3Posix(dest=/home/myusername/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/_virtualenvs/init_py3, clear=False, global=False) seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/myusername/.local/share/virtualenv) added seed packages: pip==20.2.2, setuptools==49.6.0, wheel==0.35.1 activators BashActivator,CShellActivator,FishActivator,PowerShellActivator,PythonActivator,XonshActivator Traceback (most recent call last): File "/home/myusername/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/../js/src/../../configure.py", line 181, in sys.exit(main(sys.argv)) ^^ File "/home/myusername/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/../js/src/../../configure.py", line 52, in main sandbox.run(os.path.join(os.path.dirname(__file__), 'moz.configure')) [...]
Bug#1033170: libitext-rups-java: Does not work at all
Package: libitext-rups-java Version: 2.1.7-13 Severity: grave Justification: renders package unusable X-Debbugs-Cc: jorge.moral...@gmail.com Dear Maintainer, The package does not work at all. Based on the following Ubuntu bug report it appears the version packaged is too old to work: https://bugs.launchpad.net/ubuntu/+source/libitext-java/+bug/802021 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (800, 'testing'), (500, 'testing-security'), (50, 'experimental'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 libitext-rups-java depends on: ii libitext-java 2.1.7-13 libitext-rups-java recommends no packages. libitext-rups-java suggests no packages. -- no debconf information
Bug#1032902: genx won't start: TypeError: Pen(): arguments did not match any overloaded call
On Mon, Mar 13, 2023 at 07:58:48PM +0100, s3v wrote: > File "/usr/lib/python3/dist-packages/genx/datalist.py", line 350, in > _CreateBmpIcon > dc.SetPen(wx.Pen(color_data,0.0)) > ^^ > TypeError: Pen(): arguments did not match any overloaded call: This part should likely be fixed by https://sourceforge.net/p/genx/git/ci/221e3207b045e7d3a59de1876a675ce017312d9c (I haven't checked if it helps and if there are no more errors).
Bug#1033167: usrmerge: messes with /etc/shells
Package: usrmerge Version: 25 Severity: serious Justification: violates policy section 10.7.4 Control: affects -1 + debianutils dash X-Debbugs-Cc: jo...@debian.org, cl...@debian.org, andre...@debian.org, debian-rele...@lists.debian.org Hi, I think that it is quite obvious that /etc/shells is debianutils' territory. When I found that on some systems /etc/shells was out of sync with /var/lib/shells.state, I was quite puzzled until I noticed that usrmerge messes with this file. This really is debianutils' configuration file and usrmerge has no business in touching it in uncoordinated ways. Refer to policy section 10.7.4 for details, so usrmerge is technically rc-buggy. However, usrmerge does have reason to touch it, so the solution is not simply to drop convert-etc-shells with no replacement. Let us dive a bit into how an essential system can come to be. 1. We start either merged (e.g. debootstrap or mmdebstrap with --hook-dir=.../merged-usr) or unmerged (mmdebstrap without hook or an old debootstrap --no-merged-usr). 2. We either install usrmerge or usr-is-merged. Though we cannot combine starting unmerged with usr-is-merged for obvious reasons. 3. The last invocation of update-shells happens before or after usrmerge.postinst. (Not relevant in case of usr-is-merged) So what happens in these cases? If and only if usrmerge is used, convert-etc-shells turns /bin/sh into /usr/bin/sh. So whenever we start out merged and use usr-is-merged, /usr/bin/sh goes missing. If usrmerge is used, the order of entries in /etc/shells depends on whether update-shells is run after it or not. Likewise /var/lib/shells.state also depends. This is not some mmdebstrap-specific problem. You can easily observe this with debootstrap --no-merged-usr and installing usrmerge vs just doing debootstrap. This is bad from a reproducibility point of view and it is rooted in usrmerge not cooperating with other packages, but instead doing things behind their back, which happens to violate policy. So how to fix this? For one thing, the /bin/sh difference is rooted in the fact that /bin/sh is a standard value of debianutils and not managed using shells.d even though dash ships plain /bin/sh these days. I think dash should just add /bin/sh to /usr/share/debianutils/shells.d/dash and we'd be done as all entries in shells.d are correctly managed wrt. merged-/usr by update-shells. The next thing is that convert-etc-shells needs to go away from usrmerge. In the age of systems with usr-is-merged, there is no convert-etc-shells (as there is no usrmerge), so it must work without somehow anyway. When you run update-shells after a merge, it will pick up the merged shell locations (for shells managed in shells.d) and add them to /etc/shells. So usrmerge should ensure that update-shells is called after having performed the merge. This is the only way to get reproducibility. (That doesn't quite answer yet when to run it, how to run it, nor whether that makes convert-etc-shells unnecessary though.) Then we still have add-shell and remove-shell and most packages using them induce policy violations (reverting admin changes on upgrade), so we want to change them to the shells.d mechanism in the long run, but that's not where we are today and especially not what we can rely on in bookworm. So for these entries, we still do need convert-etc-shells and indeed we cannot just delete it. convert-etc-shells compensates for the difference in behaviour of add-shell pre-merge vs post-merge. I think the best solution here would be merging convert-etc-shells into update-shells. Whenever we run update-shells, it should check whether the system is already merged and when it is, perform the equivalent to convert-etc-shells. Then usrmerge can just install an empty (except for a comment) /usr/share/debianutils/shells.d/usrmerge to trigger update-shells and things become fully reproducible in all cases, because no matter how we started, we will run update-shells post merge and that'll do the right thing. And since usrmerge now uses the tools provided by debianutils, this fully resolves the policy violation. Also note that usr-is-merged does not have to invoke the trigger as debianutils is configured after /usr is merged. So unless I am mistaken, this leads to the following action items: * update-shells absorbs convert-etc-shells. * dash adds /bin/sh to shells.d/dash. * usrmerge creates an empty shells.d/usrmerge file. * usrmerge depends on a version of debianutils that has absorbed convert-etc-shells. Does that make sense to you? I haven't actually implemented and tested this yet. Do you see any obvious flaws in the arguments or the proposed solution? I'm Ccing release managers as it looks like we're starting a transition of an essential package right in the middle of the freeze. Not good, but this looks still manageable to me. Helmut
Processed: usrmerge: messes with /etc/shells
Processing control commands: > affects -1 + debianutils dash Bug #1033167 [usrmerge] usrmerge: messes with /etc/shells Added indication that 1033167 affects debianutils and dash -- 1033167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 1032104 in 5.10.0-21-powerpc64le, found 1032104 in 5.10.162-1
Processing commands for cont...@bugs.debian.org: > # invalid version > notfound 1032104 5.10.0-21-powerpc64le Bug #1032104 [src:linux] linux: ppc64el iouring corrupted read The source 'linux' and version '5.10.0-21-powerpc64le' do not appear to match any binary packages No longer marked as found in versions linux/5.10.0-21-powerpc64le. > # according to the bug > found 1032104 5.10.162-1 Bug #1032104 [src:linux] linux: ppc64el iouring corrupted read Marked as found in versions linux/5.10.162-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1032104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: add forwarded info
Processing commands for cont...@bugs.debian.org: > forwarded 1032551 https://github.com/ManageIQ/kubeclient/issues/609 Bug #1032551 [src:ruby-kubeclient] ruby-kubeclient: FTBFS in testing: ERROR: Test "ruby3.1" failed. Set Bug forwarded-to-address to 'https://github.com/ManageIQ/kubeclient/issues/609'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1032551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032104: linux: ppc64el iouring corrupted read
On Mon, 6 Mar 2023 13:25:36 +1100 Daniel Black wrote: Since revering to linux-image-5.10.0-20 we've been free of the same errors. On ci.debian.net I upgraded all ppc64el hosts to bookworm on 2023-03-09. debian@ci-worker-ppc64el-04:~$ uname -a Linux ci-worker-ppc64el-04 6.1.0-5-powerpc64le #1 SMP Debian 6.1.12-1 (2023-02-15) ppc64le GNU/Linux Can you check if the errors are still the same (yes, there's still intermittent failures). Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: as long as redis doesn't migrate, lets ignore for bookworm
Processing commands for cont...@bugs.debian.org: > # both redis and python-fakeredis are key packages, so no autoremoval > # happens; as redis can't migrate, this is no issue for bookworm at this > # stage of the freeze > tag 1030600 bookworm-ignore Bug #1030600 [src:redis, src:python-fakeredis] redis breaks python-fakeredis autopkgtest: Connection refused Added tag(s) bookworm-ignore. > thank Stopping processing here. Please contact me if you need assistance. -- 1030600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030595: dkms autoinstall fails if headers are not available but a module could be built
Hi Andreas, [Release Team member question] On Mon, 6 Feb 2023 13:14:01 +0100 Andreas Beckmann wrote: This is actually a regression from bullseye: If foobar-dkms is installed and linux-image-foo, but not linux-headers-foo gets installed, dkms will on bullseye) emit a warning about the missing headers and exit 0 on bookworm) emit a warning about the missing headers and exit 11 making the linux-image-foo installation fail in bookworm. This is probably the same issue in all the similar bug reports that were reassigned against dkms. I'm trying to understand this bug and what it means for the bookworm release. How bad do you judge this issue to be? Is there any solution in sight? Shouldn't any foobar-dkms (or dkms helpers) depend on linux-headers? Or doesn't that work the way linux-headers-* are setup? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1029588: bts: Changes in libio-socket-ssl-perl 2.078 make bts fail to send mail to mail-server via SSL/TLS - hostname verification failed
On Tue, 14 Feb 2023 22:21:26 +0100 Lee Garrett wrote: > Bumped severity as this makes bts currently unusable, and probably > breaks for quite a few DDs their workflow. This does not break on my system where bts is connected to local sendmail (which is the default setup). Which hints at a workaround: have bts connect to local sendmail and have sendmail forward the mail to the SMTPS server. The change mentioned by Daniel affects only a setup where the host if configured via its IP address, not via a host name: See the change in SSL.pm in commit https://github.com/noxxi/p5-io-socket-ssl/commit/c0a063b70f0a3ad033da0a51923c65bd2ff118a0 Which is not the case here: $ perl -S -MDevel::SimpleTrace bts --smtp-host smtps://mail.wgdd.de usertag 1029588 + dod-test-with-tls bts: failed to open SMTPS connection to smtps://mail.wgdd.de (hostname verification failed) at main::send_mail(mail.wgdd.de) at main::mailbtsall(/usr/bin/bts:2839) at main::(/usr/bin/bts:825) Unfortunately, I can no longer investigate this issue as it looks like that my IP address is now blacklisted on Daniel's server: $ perl -MDevel::SimpleTrace scripts/bts.pl --smtp-host smtps://mail.wgdd.de usertag 1029588 + dod-test-with-tls bts.pl: failed to open SMTPS connection to smtps://mail.wgdd.de (Connection refused) at main::send_mail(mail.wgdd.de) at main::mailbtsall(scripts/bts.pl:2849) at main::(scripts/bts.pl:834) On a hunch, I would guess that Daniel's server is configured to handle STARTTLS, which is not supported by bts. But I cannot verify this. In any case this does not explain why Daniel sees bts working with libio-socket-ssl-perl 2.077 but not with 2.078. All the best
Bug#1031368: marked as done (php8.2: CVE-2023-0567 CVE-2023-0568 CVE-2023-0662)
Your message dated Sat, 18 Mar 2023 16:23:16 +0100 with message-id and subject line Accepted php8.2 8.2.4-1 (source) into unstable has caused the Debian Bug report #1031368, regarding php8.2: CVE-2023-0567 CVE-2023-0568 CVE-2023-0662 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.) -- 1031368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php8.2 Version: 8.2.2-3 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for php8.2, making the bureport RC to ideally have those fixed before bookworm release goes out. CVE-2023-0567[0]: | PHP: Password_verify() always return true with some hash CVE-2023-0568[1]: | PHP: 1-byte array overrun in common path resolve code CVE-2023-0662[2]: | PHP: DOS vulnerability when parsing multipart request body If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-0567 https://www.cve.org/CVERecord?id=CVE-2023-0567 [1] https://security-tracker.debian.org/tracker/CVE-2023-0568 https://www.cve.org/CVERecord?id=CVE-2023-0568 [2] https://security-tracker.debian.org/tracker/CVE-2023-0662 https://www.cve.org/CVERecord?id=CVE-2023-0662 Regards, Salvatore --- End Message --- --- Begin Message --- Source: php8.2 Source-Version: 8.2.4-1 Hi Ondrej, This update fixes as well #1031368, closing manually. Can you make sure the release team can accept it to bookworm? If you do not forget, please as well mention the CVE id's fixed with the upload, that makes tracking it much easier :) REgards, Salvatore - Forwarded message from Debian FTP Masters - From: Debian FTP Masters Resent-From: debian-devel-chan...@lists.debian.org Reply-To: debian-de...@lists.debian.org Date: Thu, 16 Mar 2023 15:52:30 + To: debian-devel-chan...@lists.debian.org Subject: Accepted php8.2 8.2.4-1 (source) into unstable Message-Id: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 16 Mar 2023 15:24:40 +0100 Source: php8.2 Architecture: source Version: 8.2.4-1 Distribution: unstable Urgency: medium Maintainer: Debian PHP Maintainers Changed-By: Ondřej Surý Changes: php8.2 (8.2.4-1) unstable; urgency=medium . * New upstream version 8.2.4 Checksums-Sha1: 1c3a3f94ff8082b8813a429f9c0af6f5f07ed2df 5684 php8.2_8.2.4-1.dsc d564d284a5d2982e12b6108961b53cd67a5a5d3a 11991796 php8.2_8.2.4.orig.tar.xz ca31239391a1606ff7ead4b800dd7b0937544ad8 833 php8.2_8.2.4.orig.tar.xz.asc 02ce04c2a19626b23f9ceb42c7e0364e1e99cd99 68464 php8.2_8.2.4-1.debian.tar.xz c6dedb3419e9d6ca098aa8d4beb897c54b7e0ccd 32425 php8.2_8.2.4-1_amd64.buildinfo Checksums-Sha256: 82a80c1d577a94ce2bc42007458629b45699f3ff5e0cf0642dcc86c7a9d4fb38 5684 php8.2_8.2.4-1.dsc bc7bf4ca7ed0dd17647e3ea870b6f062fcb56b243bfdef3f59ff7f94e96176a8 11991796 php8.2_8.2.4.orig.tar.xz d06a3c1d62347e07538a68c4cacc3adffdfc687800fb21226a166ff061f8a20e 833 php8.2_8.2.4.orig.tar.xz.asc 0ce2de0825cb73f300f0ef989ccdf88d328d4ab04433e3dfc74c11c5c9c6dca9 68464 php8.2_8.2.4-1.debian.tar.xz 607293d0352a7f5bfe3f40428f1f4ec4a8b7536f99549b8dd90a7821485a646a 32425 php8.2_8.2.4-1_amd64.buildinfo Files: e8175b9ad40d765b7c49428d016e562c 5684 php optional php8.2_8.2.4-1.dsc 43c5fa2cf3428e9692cd9d424e71664f 11991796 php optional php8.2_8.2.4.orig.tar.xz 9a3209241530ae9673bbc89f06589465 833 php optional php8.2_8.2.4.orig.tar.xz.asc ce69c5c515bb48b1b4ff25e97bcd1fbc 68464 php optional php8.2_8.2.4-1.debian.tar.xz 634b068125bbf68e013adb4c7c469561 32425 php optional php8.2_8.2.4-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmQTNORfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u WcLQ/w//VBvPkvlDopic6Bv0xzTtClz+hjDmGdlYSQW5jJQtQwGCoXecPwVE505o sMnyfpjl3mDNlSbIF4yYvlMxvFz0+SVapTVSkqgQ0HnFAKNOKhBJCL0b6tZdFxyW zcisyir8tO7lHHKSYCllICZg/iZOiz5Of9NUGHzO9qhNmv8mQEKhRkS/5aP43VU4 qWIthvOD3lRP2do/ReGU9HkH/7hE85cuyTAUB3fF49OrkDyZy82LVCmmjSWUr6Uw k0dr++ZJxjIcTsBx/HpGDUhaD2+YitK3Nb89PeGK67TvyO913N6Ey9NUtl2+s1/f J9jnhuuYc5Hx5Xx17T3qRihoixOSm0jQz32lir4Iqlz8GApH7IHcmRaZsRkk3n61 td6fOS0xSzccBVgY/RCsmy9qCP4axkIdTPfuAKog03QmegvI3s4saqvwwqa7Zwmb AwhOviv217WDcqr5et8yRnd+bS0AMY5h6tE3QGokTbBPQLiBMwWSYWkKYREst+Rv XXQMEzUC3pLIRSEq36ZBAFqlzXj1aobFd9jH7Rj1RW5E41OZ4hwh+CGDh/bPbL
Bug#1031368: Accepted php8.2 8.2.4-1 (source) into unstable
Source: php8.2 Source-Version: 8.2.4-1 Hi Ondrej, This update fixes as well #1031368, closing manually. Can you make sure the release team can accept it to bookworm? If you do not forget, please as well mention the CVE id's fixed with the upload, that makes tracking it much easier :) REgards, Salvatore - Forwarded message from Debian FTP Masters - From: Debian FTP Masters Resent-From: debian-devel-chan...@lists.debian.org Reply-To: debian-de...@lists.debian.org Date: Thu, 16 Mar 2023 15:52:30 + To: debian-devel-chan...@lists.debian.org Subject: Accepted php8.2 8.2.4-1 (source) into unstable Message-Id: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 16 Mar 2023 15:24:40 +0100 Source: php8.2 Architecture: source Version: 8.2.4-1 Distribution: unstable Urgency: medium Maintainer: Debian PHP Maintainers Changed-By: Ondřej Surý Changes: php8.2 (8.2.4-1) unstable; urgency=medium . * New upstream version 8.2.4 Checksums-Sha1: 1c3a3f94ff8082b8813a429f9c0af6f5f07ed2df 5684 php8.2_8.2.4-1.dsc d564d284a5d2982e12b6108961b53cd67a5a5d3a 11991796 php8.2_8.2.4.orig.tar.xz ca31239391a1606ff7ead4b800dd7b0937544ad8 833 php8.2_8.2.4.orig.tar.xz.asc 02ce04c2a19626b23f9ceb42c7e0364e1e99cd99 68464 php8.2_8.2.4-1.debian.tar.xz c6dedb3419e9d6ca098aa8d4beb897c54b7e0ccd 32425 php8.2_8.2.4-1_amd64.buildinfo Checksums-Sha256: 82a80c1d577a94ce2bc42007458629b45699f3ff5e0cf0642dcc86c7a9d4fb38 5684 php8.2_8.2.4-1.dsc bc7bf4ca7ed0dd17647e3ea870b6f062fcb56b243bfdef3f59ff7f94e96176a8 11991796 php8.2_8.2.4.orig.tar.xz d06a3c1d62347e07538a68c4cacc3adffdfc687800fb21226a166ff061f8a20e 833 php8.2_8.2.4.orig.tar.xz.asc 0ce2de0825cb73f300f0ef989ccdf88d328d4ab04433e3dfc74c11c5c9c6dca9 68464 php8.2_8.2.4-1.debian.tar.xz 607293d0352a7f5bfe3f40428f1f4ec4a8b7536f99549b8dd90a7821485a646a 32425 php8.2_8.2.4-1_amd64.buildinfo Files: e8175b9ad40d765b7c49428d016e562c 5684 php optional php8.2_8.2.4-1.dsc 43c5fa2cf3428e9692cd9d424e71664f 11991796 php optional php8.2_8.2.4.orig.tar.xz 9a3209241530ae9673bbc89f06589465 833 php optional php8.2_8.2.4.orig.tar.xz.asc ce69c5c515bb48b1b4ff25e97bcd1fbc 68464 php optional php8.2_8.2.4-1.debian.tar.xz 634b068125bbf68e013adb4c7c469561 32425 php optional php8.2_8.2.4-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmQTNORfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u WcLQ/w//VBvPkvlDopic6Bv0xzTtClz+hjDmGdlYSQW5jJQtQwGCoXecPwVE505o sMnyfpjl3mDNlSbIF4yYvlMxvFz0+SVapTVSkqgQ0HnFAKNOKhBJCL0b6tZdFxyW zcisyir8tO7lHHKSYCllICZg/iZOiz5Of9NUGHzO9qhNmv8mQEKhRkS/5aP43VU4 qWIthvOD3lRP2do/ReGU9HkH/7hE85cuyTAUB3fF49OrkDyZy82LVCmmjSWUr6Uw k0dr++ZJxjIcTsBx/HpGDUhaD2+YitK3Nb89PeGK67TvyO913N6Ey9NUtl2+s1/f J9jnhuuYc5Hx5Xx17T3qRihoixOSm0jQz32lir4Iqlz8GApH7IHcmRaZsRkk3n61 td6fOS0xSzccBVgY/RCsmy9qCP4axkIdTPfuAKog03QmegvI3s4saqvwwqa7Zwmb AwhOviv217WDcqr5et8yRnd+bS0AMY5h6tE3QGokTbBPQLiBMwWSYWkKYREst+Rv XXQMEzUC3pLIRSEq36ZBAFqlzXj1aobFd9jH7Rj1RW5E41OZ4hwh+CGDh/bPbLvV R+j3bGTdSFMU9dRqNEy++68XtQ9veYuMJsztN0rrH8PqIzAGOBg441f8s62r+W9f sp71zHObJzVPSO9NDI4zC0mpNm8z+me06lVS1WhXm29hOtHXYhs= =+GM0 -END PGP SIGNATURE- - End forwarded message -
Processed: tagging 1031476
Processing commands for cont...@bugs.debian.org: > tags 1031476 + trixie Bug #1031476 [src:ruby-celluloid-io] ruby-celluloid-io: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: Added tag(s) trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033039: kde-config-flatpak: Verified
Package: kde-config-flatpak Version: 5.27.2-1 Followup-For: Bug #1033039 Dear Maintainer, I can verify this bug. I have installed the kde-config-flatpak package and I can access the "Flatpak Permissions Settings", but when I select an application from the list all I get is "Select an application from the list to view it's permissions here". I also cannot find any information on a missing dependecy or setting that might be preventing me from accessing the permissions. Matthew -- System Information: Debian Release: bookworm/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-5-amd64 (SMP w/12 CPU threads; PREEMPT) 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 kde-config-flatpak depends on: ii libc6 2.36-8 ii libflatpak0 1.14.3-1 ii libglib2.0-02.74.6-1 ii libkf5configcore5 5.103.0-1 ii libkf5coreaddons5 5.103.0-1 ii libkf5i18n5 5.103.0-1 ii libkf5quickaddons5 5.103.0-1 ii libqt5core5a5.15.8+dfsg-3 ii libqt5qml5 5.15.8+dfsg-3 ii libstdc++6 12.2.0-14 ii systemsettings 4:5.27.2-1 kde-config-flatpak recommends no packages. kde-config-flatpak suggests no packages. -- no debconf information
Processed: tagging 987355 ...
Processing commands for cont...@bugs.debian.org: > tags 987355 - fixed-upstream Bug #987355 [phpldapadmin] CVE-2020-35132 Removed tag(s) fixed-upstream. > forwarded 987355 https://github.com/leenooks/phpLDAPadmin/issues/130 > https://github.com/leenooks/phpLDAPadmin/issues/137 Bug #987355 [phpldapadmin] CVE-2020-35132 Changed Bug forwarded-to-address to 'https://github.com/leenooks/phpLDAPadmin/issues/130 https://github.com/leenooks/phpLDAPadmin/issues/137' from 'https://github.com/leenooks/phpLDAPadmin/issues/130'. > thanks Stopping processing here. Please contact me if you need assistance. -- 987355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033077: keys from /usr/share/keyrings/debian-archive-keyring.gpg are missing from /etc/apt/trusted.gpg.d
Hi, On Fri, Mar 17, 2023 at 01:07:17PM +0100, Johannes Schauer Marin Rodrigues wrote: > could you give me a quick notice whether the missing keys are intentional or > an > oversight? If it's the former, I need to start working on a way for mmdebstrap > to cope with this situation which will be a bit tricky because the part of the > code that relies on it is quite complex and was already the source of a number > of bugs in the past... Intentional, but consequences unintended. Sorry about the disruption. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Processed: severity of 1033077 is serious
Processing commands for cont...@bugs.debian.org:
> # breaks other software
> severity 1033077 serious
Bug #1033077 {Done: Jonathan Wiltshire }
[debian-archive-keyring] keys from
/usr/share/keyrings/debian-archive-keyring.gpg are missing from
/etc/apt/trusted.gpg.d
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1033077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1010667: marked as done (ruby-xmlhash: CVE-2022-21949 - Improper Restriction of XML External Entity Reference)
Your message dated Sat, 18 Mar 2023 08:22:52 + with message-id and subject line Bug#1010667: fixed in ruby-xmlhash 1.3.6-3.1 has caused the Debian Bug report #1010667, regarding ruby-xmlhash: CVE-2022-21949 - Improper Restriction of XML External Entity Reference to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1010667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-xmlhash Version: 1.3.6-2 Severity: important Tags: security X-Debbugs-Cc: codeh...@debian.org, Debian Security Team Hi, The following vulnerability was published for ruby-xmlhash. CVE-2022-21949[0]: | A Improper Restriction of XML External Entity Reference vulnerability | in SUSE Open Build Service allows remote attackers to reference | external entities in certain operations. This can be used to gain | information from the server that can be abused to escalate to Admin | privileges on OBS. This issue affects: SUSE Open Build Service Open | Build Service versions prior to 2.10.13. The vulnerable code is in https://github.com/coolo/xmlhash and is fixed in version 1.3.8 of ruby-xmlhash. 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-21949 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21949 Please adjust the affected versions in the BTS as needed. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: ruby-xmlhash Source-Version: 1.3.6-3.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of ruby-xmlhash, 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 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated ruby-xmlhash package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 16 Mar 2023 17:28:19 +0200 Source: ruby-xmlhash Architecture: source Version: 1.3.6-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Adrian Bunk Closes: 1010667 Changes: ruby-xmlhash (1.3.6-3.1) unstable; urgency=medium . * Non-maintainer upload. * CVE-2022-21949: Improper Restriction of XML External Entity Reference (Closes: #1010667) Checksums-Sha1: cb8bfb875e4e5085e267948e51c6d5c1c4bc7481 2054 ruby-xmlhash_1.3.6-3.1.dsc cc0147d89ef4acad47625cd88dc25eb29cd6e447 3264 ruby-xmlhash_1.3.6-3.1.debian.tar.xz Checksums-Sha256: ed1c20e2cfd41b3da074d450aa78d626380ba1ffcd42fbc35d7a3fe68a58efe8 2054 ruby-xmlhash_1.3.6-3.1.dsc 79eb5a82d4edf57e9fb82c6accfe1e2bbeb4e4b504d7b57c1ef376de6476ef84 3264 ruby-xmlhash_1.3.6-3.1.debian.tar.xz Files: ab760ca3cab32900b9abeffdd4b40b03 2054 ruby optional ruby-xmlhash_1.3.6-3.1.dsc 92b3e30fa20744c6586af50446c581c6 3264 ruby optional ruby-xmlhash_1.3.6-3.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmQTNvUACgkQiNJCh6LY mLGlsg/+IsFjlxs3fecgxzfV/0NDtnAj4IAEWqXOLw/eXHFGO1aY0DWQBYiC6xtq wUkqI/LJGgqLpE0APqbqLqQVxL6ZuihiVw11LThOTrOkKvbqLe9rfewJR4AqC5AT pEsSuxq8whWZC0909WcmlsnbUEV6uBBkGFfb95r7nJGp+/8MQeb23dQnsdg3DFf3 B2bbRSSaWHidCadrwUXW163B9PvVLTbIcCj0ltU7K/jArFNUZ4G/a43DqW4fZftA de3KZFtzYyUUGL3zE3CiGnx842MA9wihX8tbY/o5x4BQ4Gv4yUPITT7MaMAX2qEZ pBoIphgDHi/NDvul5fMAkisMSuNlp9oN93/IOxgu0HSun+NTR3d/nYljdNf3XKhd +KEt6/TRVpTTQZwN1UYxiawWfpp1YCt275CGjj3nklumyunX3UKN53R1SAfmIdhN eRcQ1jLbvsbLwW02PPrk4mdrrlER3SGDaFijjCSHlZXBUpaa7MyldfYHjJUjn/1X vDl3EiTpq3RD4Lg61+OIVoH/KtneyXjGxRhiKYyLWezLfa4Zp473otHQN8/PH0yO T1Vz8Wb5UkjXjj8wxE/FYDtA4OJMZpHpCHRnUe/iyWCQea9WzxYiFo3jbVW0JXgH REC7NnP4f1TOlTQ0lfZJ
Processed: tagging 1030905
Processing commands for cont...@bugs.debian.org: > tags 1030905 + patch Bug #1030905 [src:sardana] sardana: FTBFS (cannot import name 'getargspec' from 'sphinx.util.inspect') Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1030905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1031479
Processing commands for cont...@bugs.debian.org: > tags 1031479 + trixie Bug #1031479 [src:ruby-eye] ruby-eye: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'celluloid' (~> 0.16.0) among 108 total gem(s) (Gem::MissingSpecError) Added tag(s) trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1031468
Processing commands for cont...@bugs.debian.org: > tags 1031468 + trixie Bug #1031468 [src:ruby-rubydns] ruby-rubydns: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'celluloid' (= 0.16.0) among 111 total gem(s) (Gem::MissingSpecError) Added tag(s) trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1001144
Processing commands for cont...@bugs.debian.org: > tags 1001144 + patch Bug #1001144 [odbc-mdbtools] odbc-mdbtools: Missing dependency on odbcinst Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1001144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1031439
Processing commands for cont...@bugs.debian.org: > tags 1031439 + pending Bug #1031439 [src:gcc-sh-elf] gcc-sh-elf: FTBFS: make[6]: *** No rule to make target '../libsframe/libsframe.la', needed by 'libbfd.la'. Stop. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
