Re: Question about capstone

Hello,

So yes, Samuel, my hope is capstone can create its own releases to avoid duplicating work for both capstone GitHub releases and using the packages within Debian packages. So I am not familiar with using " dpkg-buildpackage", how do you currently create packages currently, like what command(s) do you run in the "debian" folder? Please tell me what I would need to update on the main capstone here:

https://github.com/capstone-engine/capstone/tree/next

Or if anything, would it be possible your team could create a PR to capstone that would follow how to build the package using "dpkg-buildpackage"? I think this would be extremely helpful to avoid duplicating work, and the capstone maintainers can make sure their packaging works as intended for the Debian Maintainers. I'm more than happy to help, I'm not an expert on packaging, but I'm willing to help as this has been an interesting learning process for me.

I think the capstone team would want to have this folder updated (likely need to rename the folder from deb to debian):

https://github.com/capstone-engine/capstone/tree/next/packages/deb

I should note, the current Debian package approach does work, it was used in PANDA, a package that requires capstone to run, and the integration tests passed. Currently, this debian package has both the capstone shared object, capstone static library, headers, pkgconfig and cstool

https://github.com/panda-re/panda/pull/1562

Look forward to collaborating!

P. S.

Do you have mirroring enabled? Capstone seems to be working on a version 6, this would make life much easier to import any changes for releasing any new package

https://docs.gitlab.com/ee/user/project/repository/mirror/

Also, would it be accurate to say that in general, "dpkg-buildpackage" is what is used to create all Debian packages within Debian apt repositories?

On Sat, Dec 28, 2024 at 9:41 AM Simon Josefsson <simon@josefsson.org> wrote:

Hilko Bengen <bengen@debian.org> writes:

> * Samuel Henrique:
>
>> I'm cc'ing the team's mailing list (the main one used for discussions) and
>> Hilko, who packaged 5.0 for Debian experimental.
>>
>> Hilko, were there any issues with packaging 5.0 for unstable or is that just
>> pending someone doing the work?
>
> Last I checked, all reverse dependencies built fine with capstone 5.0,
> except for wcc which was broken because of other things.
>
> So we just have to coordinate a transition (haven't done that in a
> while) and upload.

Capstone is important for libntruprime in Debian and I'm happy to help
on getting capstone into unstable -- but of course prefer if you do it.
Capstone is fairly low-level so I have some concerns that v5 may break
libntruprime, but hopefully upstream already tested on more recent
capstone. Will you do an unstable upload?

/Simon