Hi Both, Pleas keep me in cc as I'm not the maintainer so miss all the good stuff! I offered to fix packaging on this on fedi to help out the maintainer, this has grown beyond the scope of that already!
I had a look at this before the bug was raised, it is also magic to me how it worked in previous versions. Generally speaking, that stands for autopkgtests too, so it's a reasonable opportunity to learn a bit more. Spent an hour or so trying to do some autotools magic to get compilation to a stage where it won't compile as `ronn` is required. In my opinion, adding lots of dependencies to entirely rebuild the application so we can "test" it seems way beyond the scope of any testing. We can also see the tests run during build [1]. Is there value in repeating them? Running prove appears easier on the face of it, but I ran into a wall there too: all the tests as shipped seem to be hardcoded to `.././vcsh` or `./vcsh`, not calling the shipped binary. Is that normal? Copying them to d/tests and updating d/tests/control has so far not proved fruitful for me either, missing files errors and other things. Any hints or tips, can I even drop the whole d/tests folder to avoid having tests happen to clear the bug? [1] https://salsa.debian.org/debian/vcsh/-/jobs/7431252#L1474 -- Hibby <hi...@debian.org> Debian Developer Packet Radioist MM0RFN
signature.asc
Description: This is a digitally signed message part.
