On 18-07-2025 15:44, Matthias Geiger wrote:
On Fri, 18 Jul 2025 04:39, Aryan Karamtoth <aryankmmiv@outlook.com> wrote:That is expected since autopkgtest pulls from unstable, and does not know how to pull in the exp packages.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_cleandpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 debian/rules clean dh clean dh_auto_clean --buildsystem=rustdh_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 25dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2Any 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, werdahiasHi 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].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
Hi Matthias,Does this mean that I don't have to worry about autopkgtests failing? All of the other lintian tests pass. I had to stall piuparts tests because of those autopkgtests.
If they're not to be concerned about, I will sign and upload my package to mentors.debian.net for further reviews.
-- Regards, Aryan Karamtoth Debian Contributor IRC: SpaciousCoder78 GPG Fingerprint: 7A7D 9308 2BD1 9BAF A83B 7E34 FE90 07B8 ED64 0421
Attachment:
OpenPGP_0xFE9007B8ED640421.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature