Re: packaging pycsw
- To: firstname.lastname@example.org
- Subject: Re: packaging pycsw
- From: Angelos Tzotsos <email@example.com>
- Date: Fri, 20 Nov 2015 04:37:57 +0200
- Message-id: <[🔎] 564E8785.firstname.lastname@example.org>
- In-reply-to: <email@example.com>
- References: <CAJOp35kfsJH8Y+FuqaO_nykjHBN1GDcUhfvW4jHMUviWs0GDBw@mail.gmail.com> <558E99FA.firstname.lastname@example.org> <558E9B7A.email@example.com> <firstname.lastname@example.org>
On 10/31/2015 10:41 PM, Sebastiaan Couwenberg wrote:
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?
I have just updated the pycsw package in OSGeoLive ppa.
I would like to take this opportunity to finally learn the process to
maintain the package in Debian...
I will clone the Debian git repository and read the documentation.
Questions might follow ;)
Angelos Tzotsos, PhD
OSGeo Charter Member