Your message dated Fri, 17 Jul 2026 21:19:56 +0000
with message-id <[email protected]>
and subject line Bug#1119203: fixed in librcc 0.2.13+ds-3
has caused the Debian Bug report #1119203,
regarding librcc: Depends on db5.3
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.)


-- 
1119203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119203
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: librcc
Version: 0.2.13+ds-2
Severity: important
Control: block 1117120 by -1

Dear Maintainer,

your package depends or otherwise uses db5.3 ("Berkeley DB"). The
upstream of db5.3 has ceased maintaining it, and it is also orphaned
in Debian. See #987013 for discussion. Please update your package to
remove any uses of db5.3 for forky.
If necessary, provide an upgrade path in forky and remove usage in
duke.

Chris

--- End Message ---
--- Begin Message ---
Source: librcc
Source-Version: 0.2.13+ds-3
Done: Bastian Germann <[email protected]>

We believe that the bug you reported is fixed in the latest version of
librcc, 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 librcc 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: Fri, 17 Jul 2026 22:59:08 +0200
Source: librcc
Architecture: source
Version: 0.2.13+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <[email protected]>
Changed-By: Bastian Germann <[email protected]>
Closes: 1119203
Changes:
 librcc (0.2.13+ds-3) unstable; urgency=medium
 .
   * QA upload.
   * Disable Berkeley DB. (Closes: #1119203)
Checksums-Sha1:
 f733e96da05d9ed20bed76b27ab39d54068b3375 1934 librcc_0.2.13+ds-3.dsc
 af08c7b9506d4635a219456072a2159e587c2938 7328 librcc_0.2.13+ds-3.debian.tar.xz
 225df4f211e350343f89b51e4516736b4cea6e21 5903 
librcc_0.2.13+ds-3_source.buildinfo
Checksums-Sha256:
 af794ced5ebcd0ad31d85f962c11ad4adcb6cdab543116501202cee33acb0ae4 1934 
librcc_0.2.13+ds-3.dsc
 2bd21883831c859fe8ae1655a2582ef7be8f9101c0253ab92a104317dbbab795 7328 
librcc_0.2.13+ds-3.debian.tar.xz
 3d5f584f1ccb42d6e0bf35e1b8368c543c2a35499d8ba9c3b253ce366aea5196 5903 
librcc_0.2.13+ds-3_source.buildinfo
Files:
 4977ff944372fe182ebc97b65148cada 1934 libs optional librcc_0.2.13+ds-3.dsc
 2663b3c4ab7e231367c2972c6d2c06a5 7328 libs optional 
librcc_0.2.13+ds-3.debian.tar.xz
 029782d47d89561e87919bd11edfb4fe 5903 libs optional 
librcc_0.2.13+ds-3_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmpal9IQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFLvgC/4hqUSxYKC6xtKHUtoQqSfoWgdYJjCU21DS
txkz/cmNwbxyLd4AfT2kBXi4Ka402VelxXD1tRQuT74XbXdEGExjf10Rrbxj+CHd
Z4xfSYypt7oLhotGvzwnNK7pQ0OFlDp6qhwPADCaGD71CRHhH0PRdnlJ+Ze+8l1C
WuOtckOQuiyE9OGRphFjY6bvIVG8LYHtjnRHzLb/eokBynhLYatCOGrtFIl6OE05
bXuWehgvigXANzSRYrrh7K+u4YPyj1tGYhlGrxNIGbM2wIu0W648pgF7NRkiyf7H
uLPKWazIJPIYQ5KtlPR3L4CJv0VOJi37J/U+aDDCafk09eviuQAL25kI1+9YKpz2
Ien+9jHFoAweVwc5mUIDjsXoDYjb0J2Lgrnk4ZyhrmKyBFfOBkRlSn2cbY6xkymr
PPyzGVPM7N1NZ4xJnmIyzg5HPlsns7mycTci3LW9QGCj+s0p+zT5w/A6cGjxccAQ
jWqf8c2FMfaHMjtI0YUYBuTe6iDerQg=
=hSu0
-----END PGP SIGNATURE-----

Attachment: pgpmksXblvQp_.pgp
Description: PGP signature


--- End Message ---

Reply via email to