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

Re: Git repository of kbibtex uses branches instead of tags and is most probably outdated



Will take care of it tomorrow
On Thu, Oct 4, 2018 at 11:08 AM Andreas Tille <andreas@an3as.eu> wrote:
>
> Hi again Bastien,
>
> since I think it is a good idea to fix Vcs fields in our packages and do
> a new upload of kbibtex I would volunteer to do this work.  However, I
> admit since I'm confused by the current kbibtex repository I'm tempted
> to recreate it via:
>
>     gbp import-dscs --debsnap --pristine-tar kbibtex
>
> What do you think about this?
>
> Kind regards
>
>        Andreas.
>
> On Mon, Sep 24, 2018 at 03:42:22PM +0200, Andreas Tille wrote:
> > Hi Bastien,
> >
> > I stumbled upon the Git repository of kbibtex on Salsa[1].  It is using
> > branches where tags should be used.  According to Debian Science
> > policy[2] a repository should usually look like
> >
> > $ git branch
> > * master
> >   pristine-tar
> >   upstream
> >
> > and package uploads should be marked by
> >
> >   git tag debian/<upstreamversion>-<debianrelease>
> >
> > Your repository[1] usies different branches instead which makes the life
> > of your team mates hard since the master branch does not contain a
> > debian/ dir as one would usually expect.
> >
> > Moreover the repository is lagging behind your packaging which is at
> > version
> >
> >    Version: 0.8~20170819git31a77b27e8e83836e-3
> >
> > while the repository[1] contains only 0.6* versions.  It might be that
> > the repository you commited to was not moved from alioth to salsa since
> > Vcs fields of recent uploads are pointing to collab-maint instead to
> > debian-science.  Would you be so kind to update the repository in
> > science-team to the latest packaging state?
> >
> > Thank you
> >
> >      Andreas.
> >
> >
> > [1] https://salsa.debian.org/science-team/kbibtex
> > [2] https://science-team.pages.debian.net/policy/#idm297
> >
> > --
> > http://fam-tille.de
> >
> >
>
> --
> http://fam-tille.de


Reply to: