Your message dated Fri, 11 Apr 2025 11:50:03 +0000
with message-id <e1u3ctx-003qwd...@fasolo.debian.org>
and subject line Bug#1102539: fixed in libstdc++-riscv64-unknown-elf 4+nmu1
has caused the Debian Bug report #1102539,
regarding libstdc++-riscv64-unknown-elf-dev fails to install
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1102539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libstdc++-riscv64-unknown-elf-dev
Version: 14.2.0+4
Severity: serious
https://piuparts.debian.org/sid/fail/libstdc++-riscv64-unknown-elf-dev_14.2.0+4.log
...
Preparing to unpack .../libstdc++-riscv64-unknown-elf-dev_14.2.0+4_all.deb ...
Unpacking libstdc++-riscv64-unknown-elf-dev (14.2.0+4) ...
Setting up libstdc++-riscv64-unknown-elf-dev (14.2.0+4) ...
update-alternatives: error: error creating symbolic link
'/usr/lib/riscv64-unknown-elf/include.dpkg-tmp': No such file or directory
dpkg: error processing package libstdc++-riscv64-unknown-elf-dev
(--configure):
installed libstdc++-riscv64-unknown-elf-dev package post-installation script
subprocess returned error exit status 2
Errors were encountered while processing:
libstdc++-riscv64-unknown-elf-dev
E: Sub-process /usr/bin/dpkg returned an error code (1)
--- End Message ---
--- Begin Message ---
Source: libstdc++-riscv64-unknown-elf
Source-Version: 4+nmu1
Done: Adrian Bunk <b...@debian.org>
We believe that the bug you reported is fixed in the latest version of
libstdc++-riscv64-unknown-elf, 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 1102...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk <b...@debian.org> (supplier of updated
libstdc++-riscv64-unknown-elf 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, 11 Apr 2025 12:07:28 +0300
Source: libstdc++-riscv64-unknown-elf
Architecture: source
Version: 4+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Keith Packard <kei...@keithp.com>
Changed-By: Adrian Bunk <b...@debian.org>
Closes: 1102539
Changes:
libstdc++-riscv64-unknown-elf (4+nmu1) unstable; urgency=medium
.
* Non-maintainer upload.
* Ship an empty /usr/lib/riscv64-unknown-elf. (Closes: #1102539)
* Remove the alternative in the prerm.
Checksums-Sha1:
bbe5a93b161d81284779eabe724eb4fb53851648 2192
libstdc++-riscv64-unknown-elf_4+nmu1.dsc
fe7d755639ed45b03824494ccf3edd52aa49f38d 89463888
libstdc++-riscv64-unknown-elf_4+nmu1.tar.xz
Checksums-Sha256:
288a37ebc7f99d41f2084b2a555fc9d8607ec11344163b3ff720dcdb805effef 2192
libstdc++-riscv64-unknown-elf_4+nmu1.dsc
97aece0ec7b009767562690d96d57ca07413002590121467e858feb491421c7c 89463888
libstdc++-riscv64-unknown-elf_4+nmu1.tar.xz
Files:
0dd6c029b4c0c860ca387fa374ee3228 2192 devel optional
libstdc++-riscv64-unknown-elf_4+nmu1.dsc
369c59597dc8123aff35b66b24d2f218 89463888 devel optional
libstdc++-riscv64-unknown-elf_4+nmu1.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmf4/ycACgkQiNJCh6LY
mLHV1BAAopTH3CCayLBhwIrDE45izMCga7SXQdoRyJRenKQkZDINss21niFvl/Kx
SurMXF06Zzi5abEKXfT82Nc+Imo8PmUCwi+dnb4Ut5VFY2pUVSnkhK5E/ZS0cWpt
oJOeI0FjfLfeg/cuNWZCKI5PzfNlJm0hW/KbubB32x0PT0x9fiGju0MlZX5G398/
BzAHRcAwrbESmamJ5uktzqaKyO8WsgC8iz3d5/8pLtkKYC6B+axWQ/f0DoImONrj
LP8vL7yD99cNg1jYZluhs1zBeOn0j0vuxzuBn0WsDgwEPlex72kGmQupd7nr9NQu
OmtjzSV5APCsea9wGefhVE/tbn1ao2q0unNizkvUa2Mlxntma4scodTXtTetu1RV
S6hWmTDIT61gSUfhkDvWxb+oQ867LJoMoNU/Ke6Mmc6QsBp2OoxJYkUJpw8YxDIW
Gayz7LFm36omvf9sh3J9zfgR9maIYenahoHxpqQmXrjLdjXcBtJcX+Uh/EevykWV
7UqohskAP4QgT0MGd3E+nxpAihKVBXEjpRz1bJqDl4Nx/a9vRRVmuLE5P+QlYhDb
AnrZPN4y+yFeq8oUwVDyEsO8otWhPnGAYhMQa6ZIGbbGRrcMIc+OktvfiMhzEel0
vIEnczz2OZ0gcriGpGPoEsBzAwOITpc4MPqgzerYJmmIXcE7g3Y=
=LNwZ
-----END PGP SIGNATURE-----
pgpjrHFIDOloi.pgp
Description: PGP signature
--- End Message ---
