Package: wnpp
Followup-For: Bug #1056068
X-Debbugs-Cc: noisyc...@tutanota.com, eam...@yaerobi.com, 
debian-r...@lists.debian.org, n...@debian.org

Hi all,

While working on ITP #948483 I repackaged usvg and resvg v0.42 as dependencies
of broot, without knowing they were already being built by src:resvg. Before
doing so I had looked for rust-{u,re}svg on the tracker, but found nothing.
Additionally, I used `cargo debstatus`, which lists both as being absent (i.e.
not just outdated, but wholly absent) from Debian (perhaps because they were
removed from testing?).

Right now src:rust-usvg and src:rust-resvg are in NEW and will probably be
rejected since they build librust-{u,re}svg-dev, which albeit having been
removed from testing are still in unstable. The sources I uploaded (thanks to
my sponsor) can build the resvg binary, although I disabled the binary because
I was only interested in the library.

Jonas, I apologize for the duplicated work. Since you've been working on this
for a long time I am more than willing to step down from {u,re}svg once the
sources are rejected. I am no user of resvg and I am not interested in
maintaining it other than to provide the rust library. However, since
apparently there's interest in having librust-{u,re}svg-dev as dependencies of
other packages (at least broot and iced need them), and building resvg is as
easy as removing one `bin = false` line from debcargo-conf, if someone from the
Rust Team (in cc) wanted to maintain resvg we could also remove src:resvg from
unstable and go forward with my (sponsored) uploads. I am ok with both
solutions, but I would like Jonas to have the final word on this given his
longstanding interest in resvg.

Cc'ing the Rust Team ML because `cargo debstatus` listing usvg and resvg as not
present in Debian, while in fact they are, is probably undesired behavior. But
the situation is a bit unusual here (removal from testing, still in unstable),
so I'd like to hear from someone more experienced than me before filing an
actual bug.

Thanks to Blair Noctis for noticing the duplication.

Reply via email to