Hallo Andreas, On Mon, Nov 07, 2016 at 06:51:11PM +0100, Andreas Tille wrote: > what according to Vcs-Git is the place where the package is maintained. > Olivier and Christian - if you are interested in some commits helping to > solve this bug please make sure the status of Git reflects the actual > packaging.
commit-wise, the package is practically ready for upload; I'd only run final tests and change `UNRELEASED` to `unstable`, and maybe check with DPMT whether I can add the team to uploaders before the package is transitioned to DPMT practices. What's holding it back is the sparqlwrapper upload; quoteing myself in #761177: > Apart from the required uscan run, all the package needs AFAICT is > updating the copyright file with the new fourth author from AUTHORS.md, > bumping compat and standards-version (without further changes) and > `s/(Python \(.\))/\1/` on the package description lines just if you want > to make lintian very happy. > > I'm unfamiliar with the SVN workflows, so I could only offer to prepare > an NMU, but that might cause more work later in SVN than doing it right > the first time. If you want to help, this is probably where you could advance things most effectively. (I'm still reading up on the git-dpm workflow; as you're familiar with the SVN one, you could just apply the above changes staying in SVN and do a team upload). (Plus, I'll need a sponsor then for the rdflib upload). Thanks chrysn -- To use raw power is to make yourself infinitely vulnerable to greater powers. -- Bene Gesserit axiom
signature.asc
Description: PGP signature
