Your message dated Thu, 23 Feb 2023 16:49:02 +0000
with message-id <[email protected]>
and subject line Bug#1030434: fixed in opensc 0.23.0-0.2
has caused the Debian Bug report #1030434,
regarding rauc: FTBFS: tests failed writing: Error opening file
?/tmp/tmp.I4dlWcaK4g/notexisting/out.raucb?: No such file or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1030434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030434
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rauc
Version: 1.8-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: [email protected]
Usertags: ftbfs-20230203 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
The full build log is available from:
http://qa-logs.debian.net/2023/02/03/rauc_1.8-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;[email protected]
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230203&[email protected]&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: opensc
Source-Version: 0.23.0-0.2
Done: Bastian Germann <[email protected]>
We believe that the bug you reported is fixed in the latest version of
opensc, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Germann <[email protected]> (supplier of updated opensc 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 13 Feb 2023 17:13:20 +0100
Source: opensc
Architecture: source
Version: 0.23.0-0.2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSC Maintainers <[email protected]>
Changed-By: Bastian Germann <[email protected]>
Closes: 1030434
Changes:
opensc (0.23.0-0.2) unstable; urgency=medium
.
* Non-maintainer upload
* Fix rauc build (Closes: #1030434)
Checksums-Sha1:
903ae6f2dd4d5f482ff426c013490230e00f9ac3 2008 opensc_0.23.0-0.2.dsc
76c59162de318e6369f71d321f4ad10a98e75a84 15040 opensc_0.23.0-0.2.debian.tar.xz
047b72dd4f7cdcae44932255cb6a09fa552462a6 6093
opensc_0.23.0-0.2_source.buildinfo
Checksums-Sha256:
5946e460fa7fe9499945c435b50089d2bae17b0a5413854a42a90aafd9a22735 2008
opensc_0.23.0-0.2.dsc
4c33b8e9e1ebaee0acc595e4e862cf83253c3fcd9f9b40684f1390000e9691ea 15040
opensc_0.23.0-0.2.debian.tar.xz
b3bf7bfeb18bba44f45333a9a698863c11d3f2f1a7c02df9e5366f00d252a357 6093
opensc_0.23.0-0.2_source.buildinfo
Files:
2711a742d61a14f8e1950a1db89e0dc5 2008 utils optional opensc_0.23.0-0.2.dsc
21ab2f77f6bb18326a6f0ab664560c88 15040 utils optional
opensc_0.23.0-0.2.debian.tar.xz
27667f2498dfa13c41bb7a85dc2642cf 6093 utils optional
opensc_0.23.0-0.2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmPqYgkQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFCoLC/92qn1h/JZ61Eg3JxE1rHRrAL638tFdXVUT
GXzN8LrpU0APdmY1017t6DbWhpzD/XjlxoH8jREuOvpVuyO+W8kiPELx8VgZVR1l
65kH1OC/D36efx71wMxGWkw0lQjzlbtK4W9/TxYq5vTKiEVDpdyKGGfF9LbzPhwv
kdegF3cvpnC+9N/dMdg2QqeRkHHXXPL1U/flfnFEVtGIR/f0SXjR9/bkdoqfhW/n
Ww/dlwFKvfdJ8CuiN1+Q3q84T0b8IyjhibGBiKhN0d2bsKcbEbbPS734xS8lm8wy
9DGnuVGkFvQLYs29BylrjgOH/+aWvQj6RrSLBL2Qc5U3XMlN96sulSuCmixCZhf4
CrYbPWC7i3PkPURWhKX9DYfECwP8rGpSmvWFdenixotUOdtuFTzh5ojUpFfentm9
FYi7u6P0iQ8h02DsCJBAcInb4mEMxXPL22FMzALDGbkRiLmIBBxBbZfdCPb/qH3B
ywwJ0sscnDHC1igOFSe0TdhsO6tSGCU=
=qWHE
-----END PGP SIGNATURE-----
--- End Message ---
