[Debian-med-packaging] Bug#843397: python-rdflib-jsonld: Requires python-rdflib 4.2.1 to work properly with schema.org contexts

[Andreas Tille]

On Tue, Nov 08, 2016 at 09:35:48AM +0100, chrysn wrote:
> 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;

commit 05cd8842a1696233c9aab0d0b64718741e70756e
Author: chrysn <chrysn at fsfe.org>
Date:   Wed Nov 27 15:46:33 2013 +0100

    Revert commits for local copy of pybuild
    
    as python3.3 is now in unstable, no such hacks are required any more.
    
    This reverts commit df035bb4fdb9fa2975bb96053787230acbdbb83a.
    This reverts commit 25a4cd9a92ff4b2791b80bbf8dd76d02bcd909d4.
    This reverts commit 454368fb589e1f9e39c4814cdca262c64ede354c.

That's lagging heavily behind uploaded packages.  Are you sure you have
pushed to the repository mentioned in Vcs-Git?

> 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.

I agree that DPMT would be a better place than collab-maint.

> 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).

Sorry, I do not understand what "above changes" you mean.  I could convert
python-sparqlwrapper from svn to git in case this would help.
 
> (Plus, I'll need a sponsor then for the rdflib upload).

If Vcs is up to date, I can do this.  My personal sponsoring policy is to
sponsor only from Vcs.

Kind regards

    Andreas.


-- 
http://fam-tille.de