Hi,
On Tue, Nov 08, 2016 at 02:26:43PM +0100, chrysn wrote:
> On Tue, Nov 08, 2016 at 12:11:31PM +0100, Andreas Tille wrote:
> > > commit-wise, the package is practically ready for upload;
> >
> > Date: Wed Nov 27 15:46:33 2013 +0100
> >
> > That's lagging heavily behind uploaded packages. Are you sure you have
> > pushed to the repository mentioned in Vcs-Git?
>
> The default branch of that repository was left at master, should have
> been debian and is fixed now; `git checkout debian` should give you the
> latest state of the package.
Hmmmm, I wonder what might be the motivation to derive from well known
standards ... but I think I can deal with this.
> > If Vcs is up to date, I can do this. My personal sponsoring policy is to
> > sponsor only from Vcs.
>
> Great, let's do this :-)
>
> > Sorry, I do not understand what "above changes" you mean. I could convert
> > python-sparqlwrapper from svn to git in case this would help.
>
> That would be helpful, then I could do all the changes neeed for the new
> upstream version and ping you about a (commit-id? signed tag?) to
> sponsor.
You can now do
gbp clone ssh://git.debian.org/git/python-modules/packages/sparqlwrapper.git
I think I'm fine if you ping me about "the latest commit that can be
uploaded". Please do not tag at this point in time since its not sure
that it will be uploaded as is.
Oliver, I hope you are fine with this. Please leave some signal in SVN
that this is not used any more. In Debian Med team we drop a
README.status with a defined format.
> Thanks
> chrysn
You are welcome
Andreas.
--
http://fam-tille.de
