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

[Luca Capello]

Hi Simon,

On Thu, 08 Dec 2016 23:23:05 +0100, Simon Josefsson wrote:
> Den Thu, 8 Dec 2016 22:31:05 +0100
> skrev Re: [Pkg-auth-maintainers] Missing branches on Git repositories
> > 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).

Fair enough, thank you for the explanation.

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

Done, Daniel authorized me, thanks!

> > 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.

From the lintian description:

  Note this tag may trigger for packages built with debhelper before
  version 9.20151004. In such case, a simple rebuild will often be
  sufficient to fix this issue.

And, currently:

  debhelper | 10.2.2~bpo8+1 | http://apt.infomaniak.ch/debian/ jessie-backports/main amd64 Packages
  debhelper | 9.20150101+deb8u2 | http://apt.infomaniak.ch/debian/ jessie/main amd64 Packages
  
However, <https://backports.debian.org/Contribute/> says:

  * Make sure that you have a proper build environment that only
    contains the suite for which the backport is for (e.g. jessie if you
    want to upload to jessie-backports) and no unneeded backports.
    Maybe you want to consider pbuilder or cowbuilder for building
    packages.

Given the above, libu2f-server0 uploaded to jessie-backports, pam-u2f
will follow as soon as the former will enter the archive.

> > > 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.

So do I.

I will wait a bit more for Nicolas' feedback and then start to rescue
the current Alioth repository.

Thx, bye,
Gismo / Luca

-- 
Luca Capello
Administrateur GNU/Linux

Infomaniak Network SA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-auth-maintainers/attachments/20161215/7f8ca7c9/attachment.sig>