Re: Need help with packaging tree-sitter-verilog

[Matthias Geiger <werdahias@riseup.net>]

On Fri, 18 Jul 2025 04:39, Aryan Karamtoth <aryankmmiv@outlook.com> wrote:
> On 17/07/25 22:50, Matthias Geiger wrote:
> > On Thu, 17 Jul 2025 15:10, Aryan Karamtoth <aryankmmiv@outlook.com> 
> > wrote:
> > > Ok I fixed those apt errors and got as far as initially running 
> > > sbuild but then I encountered some issues with dh_auto_clean
> > >
> > >
> > >  dpkg-source --before-build .
> > > dpkg-buildpackage: info: host architecture amd64
> > >  debian/rules clean
> > > dh clean
> > >    dh_auto_clean --buildsystem=rust
> > > dh_auto_clean: error: Failed to resolve crate 
> > > "tree-sitter-verilog-0.24.0" in cargo metadata for virtual library 
> > > package "librust-tree-sitter-verilog-dev".
> > > make: *** [debian/rules:9: clean] Error 25
> > > dpkg-buildpackage: error: debian/rules clean subprocess returned exit 
> > > status 2
> > >
> > > Any advice on this? You can check my work on salsa [1]
> > Hi,
> >
> > this happens because dh-cargo translates -dev dependencies literally; 
> > also your Provides: was wrong. I attached a patch that should work ;)
> >
> > Note that you need to build for experimental like this:
> > $ sbuild --build-dep-resolver=aspcud -d experimental
> >
> > best,
> >
> > werdahias
>
>
> Hi Matthias,
>
> I added the patches you sent and it does build the package now with the 
> sbuild flags you suggested but autopkgtests fail for some reason. I 
> tried fiddling around with it for an hour but it still fails no matter 
> how many times I change things. I'm attaching the autopkgtest fail log 
> paste here[1].
That is expected since autopkgtest pulls from unstable, and does not 
know how to pull in the exp packages.
> I have also added experimental repository to my apt sources before 
> this.
No need; sbuild does all the magic.
> I'm also attaching a paste of my debian/tests/control [2] for better 
> context.
>
> I also noticed that the json files and parser.c in src/ get deleted when 
> running sbuild, is it a normal behavior?
yes, since they are in the clean target.
> Also, I wish to build this for unstable since I heard that my Rust CLI 
> app that I want to package also needs to be in experimental if this 
> tree sitter package is in experimental. Can we rebuild it to unstable 
> down the line even if we do it for experimental now?
As long as your package depends on exp packages it must stay in exp. We 
are still in the freeze; trixie will release ~10th August; I expect the 
tree-siiter* stack to hit unstable after that. Nothing wrong with 
staging things in experimental, in fact it's the recommended thing to do 
during the freeze.

best,

werdahias