[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: sbsigntool - very out of date in Debian



On Mon, Jan 21, 2019 at 04:41:03PM +0000, Steve McIntyre wrote:
> >I have a package that is almost OK (packaging files are done, I nee to
> >update/remove the quilt packages, which is the hard part).
> >After that, I should be able to do an upload quickly.
> >Let me know if that would be OK for you? I should know for sure
> >today if the patches can be easily updated.
> 
> Sure, that works.

OK, so good news is I succeeded in creating a package.
However, I'm not sure the sources are imported correctly, because
upstream does not distribute complete tarballs [1], only the git uri,
which contains submodules [2].
I had to fight and  re-create a tarball from the git - if someone knows
a better solution please tell me.
Also, the package will only be very lightly tested (it passes 'make
check' and some basic tests here).

> 
> >Independently, I think it'd be better to have team maintenance, so if I
> >can join the team so me and other maintainers can work on it that would
> >be perfect for me.
> 
> Awesome. I've just added you to the efi-team group in salsa as a
> developer right now to make that easy. If you can point me at a git
> repo for your sbsigntool stuff I'll import it into salsa now. (gitlab
> permissions don't seem to let folks with "developer" permissions in a
> group create new projects, sigh.)

I built the package for 0.9.2 here, and uploaded the packaging tree to
salsa (https://salsa.debian.org/pollux/sbsigntool). This repo is a
temporary one, for import into team repo, and/or reviews.
If the package is fine, I'll upload it (for ex tomorrow).

Regards,
Pierre



[1] lib/ccan is missing from the git tarball
[2] gbp import-orig with upstream git uri fails because of lib/ccan not
imported (submodule)


Reply to: