On August 3, 2022 9:24 am, Christian Marillat wrote: > [...] > But debcargo deosn't find these new sources : > > debcargo package paste > debcargo failed: Could not create source directory rust-paste-1.0.7 > > debcargo package smallvec > debcargo failed: Could not create source directory rust-smallvec-1.8.1 > > debcargo package time > debcargo failed: Could not create source directory rust-time-0.3.11
yes, and the error message indicates that the output dir for the old (cached) version already exists, so if you run this in an empty dir you would get the files for the outdated version, right? > On 03 août 2022 07:09, "Debian Bug Tracking System" <ow...@bugs.debian.org> > wrote: > > of course fail if a provides the source version : > > debcargo package time 0.3.12 > debcargo failed: Couldn't find any crate matching time =0.3.12 > > debcargo package paste 1.0.8 > debcargo failed: Couldn't find any crate matching paste =1.0.8 > > debcargo package smallvec 1.9.0 > debcargo failed: Couldn't find any crate matching smallvec =1.9.0 works for me here (both the unversioned command and the versioned command fetch the same current upstream version) but there is a known issue where libgit2 sometimes gets stuck and doesn't properly update the crates.io index. the usual workaround is setting the `net.git-fetch-with-cli` option for cargo (debcargo uses cargo as a library internally), e.g. like so: CARGO_NET_GIT_FETCH_WITH_CLI=1 debcargo package .. a slightly more overreaching approach would be to clear out ~/.cargo/registry (the dir where cargo and thus debcargo keep a cached copy of the registry indices and already fetched crates, both in packaged .crate and expanded sources form). could you please report back whether either approach solves the issue for you? please also note that cargo and debcargo are currently prepared for upgrading, including upgrading the version of libgit2 they are linked with. this upgrade will also solve another issue with crate version availability affecting crates that have opted-into using new cargo features that are not compatible with the currently packaged cargo/debcargo versions - thankfully there aren't that many yet, and almost all of them are not (yet) package for Debian either. unfortunately this update is quite an involved process, so it will likely take a few more weeks at least until it will be available.
