On Sun, Mar 03, 2024 at 09:25:41PM +0100, hwspeedy wrote: > Hi Simon Quiqley, (CC: debian-devel) > > I'm trying to figure out how to get the hardinfo2 - release 2.0.12 into > debian repository. > hardinfo2 is a community fork of hardinfo and should continue as hardinfo > package, currently maintained in debian by Simon Quiqley. Then the logical way forward is to ask Simon to switch the package to hardinfo2 and continue maintaining it (if they are still interested, as the last maintainer upload was in 2018).
> Salvo Tomaselli suggested to do ITP Only if you want to package and maintain it yourself, and only if it should be a new package separate from the existing hardinfo one. > - But the pro's on "#debian-mentors on oftc" are so out of my league. - I am > missing the overview - eg. how to test the debian build system with packages If you want to make and maintain the package yourself you should start at https://mentors.debian.net/intro-maintainers > do I need a salsa git? No, it's just encouraged. > - Is this for project maintainers also? No, anyone can have a salsa account. > Why does CPack not work with debian build system I don't know if it can even generate source packages (generating a source package, let alone a proper Policy-compliant one, is likely out of scope for it), but even if it does, you still need to make it correct, Policy-compliant and uptodate. Making trivial source package is the easiest part of maintainership anyway. > - could a small script fix it > like: > https://github.com/hardinfo2/hardinfo2/blob/master/tools/create_debian_source.sh It doesn't really make sense to make a script that creates the initial source package as you only need to do that once. And no, you cannot just ship debmake results that you didn't even try to build. -- WBR, wRAR
signature.asc
Description: PGP signature
