[Pkg-auth-maintainers] Missing branches on Git repositories on Alioth

[Simon Josefsson]

Den Thu, 8 Dec 2016 22:31:05 +0100
skrev Re: [Pkg-auth-maintainers] Missing branches on Git repositories
on Alioth:

> Hi Simon,
> 
> On Fri, 02 Dec 2016 14:21:49 +0100, Simon Josefsson wrote:
> > Nicolas forked these two packages and pushed them to alioth
> > and made new uploads, but didn't push these branches.  It is not
> > easy for us to use his alioth git repo since it wasn't pushed
> > correctly. Fortunately the github repositories are still available:
> > 
> > https://github.com/Yubico/libu2f-server-dpkg
> > https://github.com/Yubico/pam-u2f-dpkg
> 
> Thank you for the information, indeed I can find the pristine-tar
> branches on the two Git repositories above.
> 
> As a personal interest, may I ask why the Debian packaging got its own
> Git repository instead of using the upstream one and branches?

Mostly personal preference -- I dislike "polluting" upstream
repositories with distribution-specific stuff.  If you open for that,
there is no end to what can go into the upstream repository, and then
it becomes a size issue.  I prefer to separate "upstream" from
the many different "downstream"'s (one per distribution).

> > Luca, I'm happy to give you write access to the alioth repository
> > (and/or github repository) so you can maintain the backport in the
> > same git repository as the "real" debian packages.
> 
> Yes, please, I am gismo on Alioth.  And I try to avoid GitHub for
> personal reasons, so no account ATM.

Can you apply as member to the pkg-auth-maintainers group?  I think
that is the right way forward.

> I have planned to upload the jessie-backports before Christmas, the
> only problem ATM is the fact that I built libu2f-server0 with the
> jessie debhelper, i.e. 9.20150101+deb8u2, which generates the
> following lintian error (which would not result in a automatic reject
> from the Debian upload queue):
> 
>   E: libu2f-server0: package-must-activate-ldconfig-trigger
> usr/lib/x86_64-linux-gnu/libu2f-server.so.0.0.3
> 
>   <https://lintian.debian.org/tags/package-must-activate-ldconfig-trigger.html>

Strange, do you have any idea why?  The package use normal debhelper
stuff, which I assume invokes ldconfig automatically when needed.

> > I think it make some
> > sense to move from github to alioth for all these packages, unless
> > anyone has problems with that.
> 
> FWIW, I would have preferred to have everything (upstream + Debian
> packaging) in one place as I wrote above, if you do not want to
> "pollute" the Yubico repository we can still do that on Alioth.

I think we want to have separate repositories.  The only question is
where to host them, github or alioth, and I don't care.  The
complication is that there are now repositories on both, and they
aren't in sync.  I'm not sure if it is possible to rescue the current
alioth repositories if Nicolas doesn't complete the push.  Might be
simplest to just remove them and start from scratch.  I'm happy to do
alioth for debian packaging.

/Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signatur
URL: <http://lists.alioth.debian.org/pipermail/pkg-auth-maintainers/attachments/20161208/c502cc53/attachment.sig>