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. > 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. Thanks chrysn -- This may seem a bit weird, but that's okay, because it is weird. -- perldata(1) about perl variables
signature.asc
Description: PGP signature
