Your message dated Mon, 13 Oct 2025 16:04:45 +0200
with message-id <[email protected]>
and subject line RFS: rapidyaml/0.10.0+ds-1 -- C++ library to parse and emit
YAML
has caused the Debian Bug report #1117052,
regarding RFS: rapidyaml/0.10.0+ds-1 -- C++ library to parse and emit YAML
(development files)
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.)
--
1117052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1117052
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rapidyaml":
* Package name : rapidyaml
Version : 0.10.0+ds-1
Upstream contact : Joao Paulo Magalhaes <[email protected]>
* URL : https://github.com/biojppm/rapidyaml
* License : Expat, Apache-2.0
* Vcs : https://salsa.debian.org/gbarrantes/rapidyaml
Section : libs
The source builds the following binary packages:
libryml0 - C++ library to parse and emit YAML
libryml-dev - C++ library to parse and emit YAML (development files)
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/package/rapidyaml/
Alternatively, you can download the package with 'dget' using this command:
dget -x
https://mentors.debian.net/debian/pool/main/r/rapidyaml/rapidyaml_0.10.0+ds-1.dsc
Changes since the last upload:
rapidyaml (0.10.0+ds-1) unstable; urgency=medium
.
* New upstream release.
* Overwrite Lintian warning about SONAME. The ABI is not stable yet, and
the maintainer wants to use the full version in the SONAME.
Regards,
--
Gabriel Barrantes
--- End Message ---
--- Begin Message ---
There was a problem with how you imported the upstream version.
Please use `gbp import-orig --uscan --component=extcmake`.
I have fixed that in the git repository for you.
--- End Message ---
