Fabian Grünbichler writes ("Bug#1122276: FTBFS: d/control and Cargo.toml are
not in sync"):
> Hi!
Hi. Thanks for the report and sorry for the inconvenience.
I will fix it.
> Either relaxing Cargo.toml to have <0.10 as upper bound, or restricting
> Cargo.toml and d/control to pick up librust-toml-0.8+default-dev should work.
> I've attached a patch for the former.
Upstream 1.6.0 has more relaxed dependencies so I am currently trying
"let's just update" but if that doesn't work I will probably relax the
dependency.
> Please try to keep Cargo.toml and d/control consistent, or at least
> d/control more strict than Cargo.toml to avoid breakage like
> this. debcargo would (in this case, with the upper bound extended to
> <0.10) generate a Depends on "librust-toml+default-dev (<< 0.10-~~),
> librust-toml+default-dev (>= 0.5.0-~~)" which would have
> automatically switched over from 0.8 to 0.9 by virtue of
> librust-toml-dev not being provided by either librust-toml-0.5-dev
> nor librust-toml-0.8-dev.
I'm happy to try to avoid similar problems in the future but not sure
I follow.
When I uploaded 1.0.1-3, the version currently in stable, toml 0.9
didn't exist, so the Cargo.toml dependency said "<0.9". (That value
comes from upstream. The upstream package regularly relaxes its
dependencies to allow newer versions.)
I presume you don't mean to suggest that I should have, in March,
before TOML 0.9 existed, preemptively deleted the upstream upper
dependency requirement ?
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
