Your message dated Fri, 16 Oct 2026 09:03:36 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-rust-maintainers] Bug#1134157: rustc-src: impossible 
to satisfy crate  dependencies
has caused the Debian Bug report #1134157,
regarding rustc-src: impossible to satisfy crate dependencies
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.)


-- 
1134157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1134157
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rustc
Version: 1.94.1+dfsg1-1~exp3
Severity: grave

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

In package rust-src, /usr/src/rustc-1.94.1/Cargo.lock and
usr/src/rustc-1.94.1/library/Cargo.lock are locked at crate
versions unsatifiable in Debian, e.g. rustc-demangle 0.1.26 and
object 0.37.3.

Also, /usr/src/rustc-1.94.1/library/std/Cargo.toml requires
newer-than-Debian crate including object 0.37.1, and
missing-in-Debian crates including dlmalloc and wasi.

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

iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmnh3qsMHGRyQGpvbmVz
LmRrAAoJECx8MUbBoAEhEzkP/RgkBQ2/JRyt44fYgC83/3PhvdGfzddGi0jqOVK7
DbdS9je5FBAhW8gobZwQ/PrFvH4r4q4HfFFt7MZeZngVOjF/Ytb7tRVC8xbpSM1F
qcspa8xYxJm8mVcGYH1fqzSYkCASanh67+PmRsmrVPCypOGPXkQtd51RZhuRM+0H
8nxdHSkSwVFvQO4abRU6GupBWtKNBB9Qi3CfoikRP2MERe4zZppe00DMAfBiwgh7
Yyz1OOxEkmOO4mcBC93WNxHhfw4mKnBhYQnVyHASHeLxYqNSG0V/E8Qx109jF/Wo
sJHq8tnGQMOSs2WfMQl4xEVT80vHNVl8N/XDTXLyo4kD3NVCMtsX/VEZjHIFOmFM
vtqWZC+433OV4l1/O6MgtCY2kIj0jyDzwSvuHUIzsh9GBbuw/tjY/4Miw1WlH1Aw
eGB9IcGUynMG+WYGDDFZRSWwdAIF67inkh33Nv95FG4ub9gnYNAcq5gPJutPXPp3
XFfEqyoZ90/wqLetgXaOibceYRxUa6SkMPihNcJ2T1Kbrz0c75lOtS+IpOpzFUOM
fBRLKxztdkDxvcUrvMko4gBWll3gEykj1qgDs8wKCc6fPw5mTXKWV9NM1UTCtVeu
tdADU82qEliwriQrybWWSxeLJcvtOa6HoS68eW2z1TW3Y+S5T3JXTaZu2yq1X7qQ
8GIM
=xWTE
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
Version: 1.95.0+dfsg1-1

On Thu, 14 May 2026 12:43:49 +0200 Fabian =?utf-8?Q?Gr=C3=BCnbichler?= 
<[email protected]> wrote:
> Control: tag -1 +pending
> 
> On Sat, 18 Apr 2026 10:08:37 +0200 =?UTF-8?Q?Fabian_Gr=C3=BCnbichler?= 
> <[email protected]> wrote:
> > On Fri, Apr 17, 2026, at 11:05 PM, Jonas Smedegaard wrote:
> 
> > [..]
> 
> > > It sounds like there is no bug here at all. Feel free to close this if
> > > that's how you see it.
> > 
> > I think I'll leave it open to track maybe finding a way to support
> > -Zbuild-std in packaging context as well (e.g., to unlock some firmware
> > building usecase in the future, that might require a custom libstd).
> > 
> > It's a bit of a tough nut to crack though, because there can only be one
> > replacement for crates.io (which we already use for packaged crates), so
> > we'd probably need to ship a copy of the vendored crates as part of
> > rust-src, and adapt all the dependencies to be path dependencies, and so
> > on.
> 
> It turned out that this is actually easier than I thought.
> 
> Starting with the next rustc upload, rust-src will ship a copy of the
> few vendored crates needed to rebuild std/core/alloc. If you make them
> available to cargo (i.e. by linking them into the fake registry), a lot
> of build-std variants already work (some targets will of course require
> extra setup or dependencies, like special linkers or LLVM bits).
> 
> Upstream will start doing that as well:
> 
> https://github.com/rust-lang/rust/pull/156196
> 
> and plans to later switch build-std over to automatically pick those up,
> at which point even linking them into the registry would no longer be
> required.

build-std should now work, rust-src ships the vendored crates required
for building std/core/.. in /usr/src/rustc-1.X.Y/library/vendor/ and
there is an autopkgtest ensuring it doesn't regress:

https://salsa.debian.org/rust-team/rust/-/blob/debian/sid/debian/tests/create-and-build-crate-with-build-std
https://ci.debian.net/packages/r/rustc/unstable/amd64/76230036/#S10

as well as packages in the wild using it:

https://sources.debian.org/src/m1n1/2.0.0-1~exp1/debian/rules

there will likely be further developments upstream that will allow us to
skip the manual symlinking of vendored crates, with cargo automatically
picking them for building std/..

Fabian

--- End Message ---

Reply via email to