Your message dated Wed, 1 Oct 2025 19:43:00 -0400
with message-id
<o7jjd77irwngqh4rt3q4l7gggrjreziehbcqnee6cxwkgxjufl@k6u4b6xhssyw>
and subject line Re: Bug#1116702: librust-tree-sitter-dev: rustc dependency
breaks cross building
has caused the Debian Bug report #1116702,
regarding librust-tree-sitter-dev: rustc dependency breaks cross building
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.)
--
1116702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116702
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: librust-tree-sitter-dev
Version: 0.22.6-8
User: [email protected]
Usertags: cross-satisfiability
Control: affects -1 + src:hx src:sdml src:tree-sitter-c src:tree-sitter-lua
src:tree-sitter-markdown src:tree-sitter-query src:tree-sitter-sdml
src:tree-sitter-vim src:tree-sitter-vimdoc src:turtlefmt
The affected packages cannot be cross built from source, because they
have unsatisfied cross Build-Depends. Since rustc is a multitarget
compiler, they all depend on the build architecture rust compiler in one
way or another. librust-tree-sitter-dev has a dependency on "rustc".
This implicitly refers to the host architecture compiler. In a cross
compilation setting, we're unable to execute that and in all of the
cases at hand, it poses an unresolvable conflict with the build
architecture compiler.
I'm not sure why there is a rustc dependency here. It is versioned, so
maybe the version is the important part. Generally though rust crates do
not depend on a compiler much like C libraries do not depend on a C
compiler. For instance, the rust compiler package may be named rustc-web
as is happening in some suites. We also don't impose a minimum gccrs
version. Can we drop the compiler dependency? Failing that, can we turn
it into Breaks: rustc (<< 1.65)? Failing that, can we annotate it with
:any?
Thanks for considering
Helmut
--- End Message ---
--- Begin Message ---
Version: 0.25.4-1
On Wed, Oct 01, 2025 at 07:07:29AM -0400, James McCoy wrote:
On Tue, Sep 30, 2025 at 01:32:22PM +0200, Helmut Grohne wrote:
Generally though rust crates do
not depend on a compiler much like C libraries do not depend on a C
compiler. For instance, the rust compiler package may be named rustc-web
as is happening in some suites. We also don't impose a minimum gccrs
version. Can we drop the compiler dependency? Failing that, can we turn
it into Breaks: rustc (<< 1.65)? Failing that, can we annotate it with
:any?
Looking at how we handle this in the debcargo side, we only express this
relationship in the source package, not the binary packages.
I can adjust tree-sitter's packaging to do the same.
In fact, that's already happened in the version currently in
experimental.
Cheers,
--
James (he/him)
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--- End Message ---
