Re: packaging pycsw
- To: email@example.com
- Subject: Re: packaging pycsw
- From: Sebastiaan Couwenberg <firstname.lastname@example.org>
- Date: Sat, 31 Oct 2015 21:41:55 +0100
- Message-id: <[🔎] email@example.com>
- In-reply-to: <558E9B7A.firstname.lastname@example.org>
- References: <CAJOp35kfsJH8Y+FuqaO_nykjHBN1GDcUhfvW4jHMUviWs0GDBw@mail.gmail.com> <558E99FA.email@example.com> <558E9B7A.firstname.lastname@example.org>
On 27-06-15 14:47, Angelos Tzotsos wrote:
> On 06/27/2015 03:41 PM, Sebastiaan Couwenberg wrote:
>> While looking into the new PyCSW point release, I noticed that it
>> changed the OWSlib requirement to <0.9.0. Since we have OWSlib 0.9.0 in
>> unstable, this could mean that we're unable to update the pycsw package.
>> Is this a correct assessment?
> We found out that under specific circumstances, OWSLib 0.9.0 breaks some
> of our unit tests.
> We are still investigating this, and we will fix in a future release.
Some time has passed, and now PyCSW 1.10.3 is out but still requires
OWSLib < 0.9.0, so I guess that issue still hasn't been resolved or can
we finally update the pycsw package again?
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1