Re: Fwd: Re: Help with new package version?
Hi,
short notice before I'll be basically offline: I've recreated the
packaging repository (please do a fresh git clone), injected latest
upstream version and uploaded.
I'll leave it for you once you release the next version. ;-)
Have a nice weekend
Andreas.
On Fri, Apr 20, 2018 at 03:32:05PM +0200, Andreas Tille wrote:
> Hi Benjamin,
>
> On Fri, Apr 20, 2018 at 08:47:08AM -0400, Benjamin Redelings wrote:
> > Sorry for the delay in responding. To clarify, I wasn't thinking
> > of maintaining the /debian/ directory in upstream git, but more that I
> > was trying to follow the directions here:
> > https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.upstream-git.html
>
> Ahh, OK. May be you was attracte by "When upstream uses Git" headline.
>
> > If I understand you correctly, it is easier to simply import
> > tarballs into the salsa repo than to somehow use git to pull upstream
> > commits into the salsa repo.
>
> What is easy depends from your workflow and what you are used to. Since
> by far not all upstreams are using Git a large team (according to the
> number of packages) can cooperate better if there is only a single
> workflow. Thus we settled with the more generic one which does not
> depend from the specific feature that upstream uses Git (despite that
> becomes more and more popular).
>
> > This has the downside that I have to
> > actually make source tarballs solely for this purpose.
>
> No you don't. Github is just doing this for you once you are tagging
> a release. You can download this very easily by just doing
>
> uscan --verbose
>
> (that's what is the debian/watch file is written for).
>
> > But on the
> > positive side it would establish a clear namespace separation between
> > e.g. the upstream tags and the debian tags. Also it would be the
> > standard workflow for debian-med. Am I understanding things correctly here?
>
> Yes (except that you have to do extra work to create a tarball which is
> not needed).
>
> > Pending answer to the above question, yes, can you please create a
> > pure packaging-related repository?
>
> I'll do so.
>
> > Once I understand how to perform the
> > gbp magic on this new repository I can be more helpful in releasing new
> > versions.
>
> Its described in Debian Med team policy[1] (seek for git)
>
> > I will probably ask more questions, but you seem to respond
> > pretty quickly, so I guess I should just ask.
>
> Perfectly fine. As a warning: I'll be less responsive this weekend
> (probably starting soon) but I'll let you know when I finished the
> refactoring of the packaging Git and usually this list has also other
> competent people to answer.
>
> > thank you for your help!
>
> You are welcome.
>
> Kind regards
>
> Andreas.
>
> [1] https://debian-med.alioth.debian.org/docs/policy.html
>
> --
> http://fam-tille.de
>
>
--
http://fam-tille.de
Reply to: