Re: Adopting factory-boy

2016-05-12 Thread Christopher Baines 

On 12/05/16 15:14, Thomas Goirand wrote:

On 05/12/2016 10:13 AM, Christopher Baines wrote:

On 12/05/16 07:57, Thomas Goirand wrote:

On 05/11/2016 02:31 PM, Christopher Baines wrote:

On 11/05/16 13:19, Thomas Goirand wrote:

On 05/11/2016 11:31 AM, Christopher Baines wrote:

On 23/12/15 15:30, Christopher Baines wrote:

On 23/12/15 11:31, Thomas Goirand wrote:

I was the maintainer of this package, though I lost interest for it
because there's no reverse dependency for it.


Thanks for packaging it :)


If you want to continue maintaining it within the OpenStack PKG team,
you can do it as well. Though we're not using git-dpm, and rather a git
tag workflow, you're still free to use whatever workflow you want there,
as long as the package is well maintained.

If you need sponsoring for this package, I can review it and upload it
for you.


Great, thanks for the offer. I think I'll have to wait a couple of weeks
to see where things are for packaging this. There is at least one new
dependency for the latest release (python-fake-factory), I have packaged
that, but the tests currently don't pass. Once there is a release for
python-fake-factory, for which the tests pass, and that has been
uploaded to Debian, I'll get around to looking at factory-boy again.


Its been quite a few weeks, but the above is now done. The missing
dependency (python-fake-factory) is now in Debian, and I have updated
factory-boy to the latest upstream version [1].

Are you still open to sponsoring this zigo? I have just filled in the
alioth form to become a member of the OpenStack team.

1: http://git.cbaines.net/factory-boy/


Hi,

I added you as a member of the team. Let me know when I should sponsor
the package.


Great, I have pushed the changes to the repository and it is ready for
you to review.


Hi,

Please join #debian-openstack-commits to see the build results.
Currently, the package FTBFS in Jessie's chroot:

https://mitaka-jessie.pkgs.mirantis.com/job/factory-boy/5/console

The type of error you're seeing is most of the time due to the fact you
didn't push the upstream tags to Git.


Ok, the script in use there was not using the correct tag (it was
missing a leading "v"), but this is now fixed by modifying GIT_TAG in
the debian/rules makefile.

However, the package still fails, as fake-factory is not available in
Jessie.


Hi,

I added fake-factory as backport in that Jenkins server, and now it
builds fine.

In your Git log, I can read:

 * Add myself to Uploaders
 * Add build dependencies on fake-factory and python-ipaddress
 * Bump Standards-Version to 3.9.8 (no changes required)
 * Change the gbp.conf upstream-tag to include the v prefix, as this
   makes git-buildpackage able to find the tags

None of this appeared in the debian/changelog. I added them, pushed them
to the git, built and upload. Next time, please document all of your
packaging changes in debian/changelog.


Ah yeah, sorry about the changelog, and thanks for uploading it :)

Re: Adopting factory-boy

2016-05-12 Thread Christopher Baines 
On 12/05/16 07:57, Thomas Goirand wrote:
> On 05/11/2016 02:31 PM, Christopher Baines wrote:
>> On 11/05/16 13:19, Thomas Goirand wrote:
>>> On 05/11/2016 11:31 AM, Christopher Baines wrote:
>>>> On 23/12/15 15:30, Christopher Baines wrote:
>>>>> On 23/12/15 11:31, Thomas Goirand wrote:
>>>>>> I was the maintainer of this package, though I lost interest for it
>>>>>> because there's no reverse dependency for it.
>>>>>
>>>>> Thanks for packaging it :)
>>>>>
>>>>>> If you want to continue maintaining it within the OpenStack PKG team,
>>>>>> you can do it as well. Though we're not using git-dpm, and rather a git
>>>>>> tag workflow, you're still free to use whatever workflow you want there,
>>>>>> as long as the package is well maintained.
>>>>>>
>>>>>> If you need sponsoring for this package, I can review it and upload it
>>>>>> for you.
>>>>>
>>>>> Great, thanks for the offer. I think I'll have to wait a couple of weeks
>>>>> to see where things are for packaging this. There is at least one new
>>>>> dependency for the latest release (python-fake-factory), I have packaged
>>>>> that, but the tests currently don't pass. Once there is a release for
>>>>> python-fake-factory, for which the tests pass, and that has been
>>>>> uploaded to Debian, I'll get around to looking at factory-boy again.
>>>>
>>>> Its been quite a few weeks, but the above is now done. The missing
>>>> dependency (python-fake-factory) is now in Debian, and I have updated
>>>> factory-boy to the latest upstream version [1].
>>>>
>>>> Are you still open to sponsoring this zigo? I have just filled in the
>>>> alioth form to become a member of the OpenStack team.
>>>>
>>>> 1: http://git.cbaines.net/factory-boy/
>>>
>>> Hi,
>>>
>>> I added you as a member of the team. Let me know when I should sponsor
>>> the package.
>>
>> Great, I have pushed the changes to the repository and it is ready for
>> you to review.
> 
> Hi,
> 
> Please join #debian-openstack-commits to see the build results.
> Currently, the package FTBFS in Jessie's chroot:
> 
> https://mitaka-jessie.pkgs.mirantis.com/job/factory-boy/5/console
> 
> The type of error you're seeing is most of the time due to the fact you
> didn't push the upstream tags to Git.

Ok, the script in use there was not using the correct tag (it was
missing a leading "v"), but this is now fixed by modifying GIT_TAG in
the debian/rules makefile.

However, the package still fails, as fake-factory is not available in
Jessie.




signature.asc
Description: OpenPGP digital signature

Re: Adopting factory-boy

2016-05-11 Thread Christopher Baines 
On 11/05/16 13:19, Thomas Goirand wrote:
> On 05/11/2016 11:31 AM, Christopher Baines wrote:
>> On 23/12/15 15:30, Christopher Baines wrote:
>>> On 23/12/15 11:31, Thomas Goirand wrote:
>>>> I was the maintainer of this package, though I lost interest for it
>>>> because there's no reverse dependency for it.
>>>
>>> Thanks for packaging it :)
>>>
>>>> If you want to continue maintaining it within the OpenStack PKG team,
>>>> you can do it as well. Though we're not using git-dpm, and rather a git
>>>> tag workflow, you're still free to use whatever workflow you want there,
>>>> as long as the package is well maintained.
>>>>
>>>> If you need sponsoring for this package, I can review it and upload it
>>>> for you.
>>>
>>> Great, thanks for the offer. I think I'll have to wait a couple of weeks
>>> to see where things are for packaging this. There is at least one new
>>> dependency for the latest release (python-fake-factory), I have packaged
>>> that, but the tests currently don't pass. Once there is a release for
>>> python-fake-factory, for which the tests pass, and that has been
>>> uploaded to Debian, I'll get around to looking at factory-boy again.
>>
>> Its been quite a few weeks, but the above is now done. The missing
>> dependency (python-fake-factory) is now in Debian, and I have updated
>> factory-boy to the latest upstream version [1].
>>
>> Are you still open to sponsoring this zigo? I have just filled in the
>> alioth form to become a member of the OpenStack team.
>>
>> 1: http://git.cbaines.net/factory-boy/
> 
> Hi,
> 
> I added you as a member of the team. Let me know when I should sponsor
> the package.

Great, I have pushed the changes to the repository and it is ready for
you to review.



signature.asc
Description: OpenPGP digital signature

Updating python-django-tagging (0.4.1 -> 0.4.3)

2016-05-11 Thread Christopher Baines 
Hey,

Is anyone available to review and upload a new version of
python-django-tagging [1][2]?

The changelog is:
  * New upstream release
  * Convert debian/copyright to the DEP-5 format
  * Add myself as an uploader
  * Remove the fix_calc_tag_weight patch, as this has been merged upstream
  * Remove the fix-testsuite patch, as this is unnecessary

Thanks,

Chris

1:
https://anonscm.debian.org/cgit/python-modules/packages/python-django-tagging.git/
2: https://tracker.debian.org/pkg/python-django-tagging



signature.asc
Description: OpenPGP digital signature

Re: Adopting factory-boy

2016-05-11 Thread Christopher Baines 
On 23/12/15 15:30, Christopher Baines wrote:
> On 23/12/15 11:31, Thomas Goirand wrote:
>> I was the maintainer of this package, though I lost interest for it
>> because there's no reverse dependency for it.
> 
> Thanks for packaging it :)
> 
>> If you want to continue maintaining it within the OpenStack PKG team,
>> you can do it as well. Though we're not using git-dpm, and rather a git
>> tag workflow, you're still free to use whatever workflow you want there,
>> as long as the package is well maintained.
>>
>> If you need sponsoring for this package, I can review it and upload it
>> for you.
> 
> Great, thanks for the offer. I think I'll have to wait a couple of weeks
> to see where things are for packaging this. There is at least one new
> dependency for the latest release (python-fake-factory), I have packaged
> that, but the tests currently don't pass. Once there is a release for
> python-fake-factory, for which the tests pass, and that has been
> uploaded to Debian, I'll get around to looking at factory-boy again.

Its been quite a few weeks, but the above is now done. The missing
dependency (python-fake-factory) is now in Debian, and I have updated
factory-boy to the latest upstream version [1].

Are you still open to sponsoring this zigo? I have just filled in the
alioth form to become a member of the OpenStack team.

1: http://git.cbaines.net/factory-boy/



signature.asc
Description: OpenPGP digital signature

Re: Updating python-django-tagging

2016-03-20 Thread Christopher Baines 
On 06/03/16 13:12, Christopher Baines wrote:
> I have been looking at updating the python-django-tagging package, as it
> currently fails to build from source, and there is a new upstream
> release available (that I believe will fix this).
> 
> However, git-dpm keeps complaining in different ways when I try to do
> this (and I have tried a few different ways). I think the source of the
> issues I am having could be that the debian/.git-dpm file is out of sync
> with the rest of the repository (it seems to still refer to the 0.3.1
> version, whereas the current version is 0.4).
> 
> What is the best approach here if I am trying to update the package? I
> can try and fix the debian/.git-dpm file (manually or using some tool?),
> or I could just avoid using git-dpm (but I do need to do some patch
> changes)?

To try and move this forward, I have made an attempt at fixing the metadata.

I have not updated the python modules team remote just yet, but you can
find the updates here [1], and the specific commit for the metadata here
[2].

If I hear no objections in the next couple of days, I'll update the
repository on git.debian.org.

1: http://git.cbaines.net/python-django-tagging/
2:
http://git.cbaines.net/python-django-tagging/commit/?id=2e528690df8792b2e70248ce18712ca653ede12b




signature.asc
Description: OpenPGP digital signature

Updating python-django-tagging

2016-03-06 Thread Christopher Baines 
Hello,

I have been looking at updating the python-django-tagging package, as it
currently fails to build from source, and there is a new upstream
release available (that I believe will fix this).

However, git-dpm keeps complaining in different ways when I try to do
this (and I have tried a few different ways). I think the source of the
issues I am having could be that the debian/.git-dpm file is out of sync
with the rest of the repository (it seems to still refer to the 0.3.1
version, whereas the current version is 0.4).

What is the best approach here if I am trying to update the package? I
can try and fix the debian/.git-dpm file (manually or using some tool?),
or I could just avoid using git-dpm (but I do need to do some patch
changes)?

Thanks,

Chris



signature.asc
Description: OpenPGP digital signature

Bug#816261: RFS: django-prometheus/1.0.6-1

2016-02-29 Thread Christopher Baines 
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for "django-prometheus"

 * Package name: django-prometheus
   Version : 1.0.6-1
   Upstream Author : Uriel Corfa 
 * URL : https://github.com/korfuri/django-prometheus
 * License : Apache
   Section : python

It builds those binary packages:

  python-django-prometheus - Django middlewares to enable monitoring
with Prometheus (Python 2)
  python3-django-prometheus - Django middlewares to enable monitoring
with Prometheus (Python 3)

To access further information about this package, please visit the
following URL:

  http://mentors.debian.net/package/django-prometheus

Alternatively, one can download the package with dget using this command:

  dget -x
http://mentors.debian.net/debian/pool/main/d/django-prometheus/django-prometheus_1.0.6-1.dsc

It is also available on git.debian.org:


https://anonscm.debian.org/cgit/python-modules/packages/django-prometheus.git/

Thanks,

Chris



signature.asc
Description: OpenPGP digital signature

Updating FeinCMS

2016-02-28 Thread Christopher Baines 
I have made an attempt to get the FeinCMS package up to date. You can
now find the v1.11.4 release in the Git repository [1].

Janos, are you able to review this?

Thanks,

Chris

1:
https://anonscm.debian.org/cgit/python-modules/packages/python-django-feincms.git/

Bug#816169: RFS: fake-factory/0.5.3-1

2016-02-28 Thread Christopher Baines 
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for "fake-factory"

 * Package name: fake-factory
   Version : 0.5.3-1
   Upstream Author : Daniele Faraglia 
 * URL : http://github.com/joke2k/faker
 * License : Expat
   Section : python

It builds those binary packages:

  python-fake-factory - Faker is a Python library that generates fake
data (Python 2)
  python3-fake-factory - Faker is a Python library that generates fake
data (Python 3)

To access further information about this package, please visit the
following URL:

  http://mentors.debian.net/package/fake-factory

Alternatively, one can download the package with dget using this command:

  dget -x
http://mentors.debian.net/debian/pool/main/f/fake-factory/fake-factory_0.5.3-1.dsc

It is also available on git.debian.org:

  https://anonscm.debian.org/cgit/python-modules/packages/fake-factory.git/

Thanks,

Chris

Re: RFS: sklearn-pandas

2015-12-29 Thread Christopher Baines 
On 22/11/15 19:51, Christopher Baines wrote:
> I am looking for a sponsor for the sklearn-pandas package.
> 
> * Package name: sklearn-pandas
>   Version : 0.0.12
>   Upstream Author : Israel Saeta Pérez <israel.sa...@dukebody.com>
> * URL : https://github.com/paulgb/sklearn-pandas
> * License : Zlib
>   Programming Lang: Python
>   Description : Pandas integration with sklearn
> 
> You can find the source package in this Git repository:
>  http://git.cbaines.net/sklearn-pandas

To follow up on this, sklearn-pandas is now in the NEW queue :) [1].

1: https://ftp-master.debian.org/new/sklearn-pandas_1.1.0-1.html

Re: Updating python-jsmin

2015-12-23 Thread Christopher Baines 
On 23/12/15 00:07, gustavo panizzo (gfa) wrote:
> On Tue, Dec 22, 2015 at 05:44:53PM +0000, Christopher Baines wrote:
>> python-jsmin [1] is not currently maintained by the Python Modules Team,
>> but I have made a attempt at updating it to the latest upstream version
>> in a manor compliant with the team policy.
>
> do you have a link for the team policy?

Yes, you can find it here:
  https://python-modules.alioth.debian.org/policy.html

> You could have open a bug and I would update the pkg, or just ping me.
> to get it updated to the latest version.

Ok, getting an up to date package in Debian would be great. Are you now
planning on updating it?

>> You can find the package here [2]. Is anyone (including the current
>> maintainer CC'ed) interested in updating this package, and possibly
>> bringing it in to the team?
> 
> I'm OK moving it into the python modules team, if I don't have to change
> my workflow much, or follow another mailing list

Sounds like team maintenance is not the best option then at the moment,
as I imagine that there are significant workflow changes (the
python-jsmin package is not in Git at the moment).

Re: Updating python-jsmin

2015-12-23 Thread Christopher Baines 
On 23/12/15 10:48, gustavo panizzo (gfa) wrote:
> I will update the pkg, last updates weren't difficult so I expect to get
> it done soon.
> 
> Pkg is already on git, in collab-maint

Ah, sorry, I missed that. I just used apt-get source to get the source
package.

Re: Adopting factory-boy

2015-12-23 Thread Christopher Baines 
On 23/12/15 11:31, Thomas Goirand wrote:
> I was the maintainer of this package, though I lost interest for it
> because there's no reverse dependency for it.

Thanks for packaging it :)

> If you want to continue maintaining it within the OpenStack PKG team,
> you can do it as well. Though we're not using git-dpm, and rather a git
> tag workflow, you're still free to use whatever workflow you want there,
> as long as the package is well maintained.
> 
> If you need sponsoring for this package, I can review it and upload it
> for you.

Great, thanks for the offer. I think I'll have to wait a couple of weeks
to see where things are for packaging this. There is at least one new
dependency for the latest release (python-fake-factory), I have packaged
that, but the tests currently don't pass. Once there is a release for
python-fake-factory, for which the tests pass, and that has been
uploaded to Debian, I'll get around to looking at factory-boy again.

RFS: python-prometheus-client /0.0.13

2015-12-23 Thread Christopher Baines 
Hello,

I am looking for a sponsor for python-prometheus-client.

* Package name: python-prometheus-client
  Version : 0.0.13
  Upstream Author : Brian Brazil 
* URL : https://github.com/prometheus/client_python
* License : Apache-2.0
  Programming Lang: Python
  Description : Python client for the Prometheus monitoring system

You can find this package here:

  http://git.cbaines.net/python-prometheus-client/

I have attempted to follow the team policy when packaging this.

Currently the tests do not pass for python 3, so I have disabled them.
This is an issue with the tests that will be fixed in the next upstream
release.

Thanks,

Chris

Updating python-requests and python-urllib3

2015-12-22 Thread Christopher Baines 
I have had a go at updating python-requests to the latest upstream
release (from 2.8.1 to 2.9.1). This bundles the latest version of
python-urllib3 (1.13.1) so I have updated that also (from 1.12 to 1.13.1).

1: https://tracker.debian.org/pkg/requests
2: https://tracker.debian.org/pkg/python-urllib3

When updating python-urllib3, I also added in the DEP8 tests from
#796717 [3]. I duplicated the test, and adjusted it for python 3 (as the
patch was just python 2 only).

3: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796717

I am still getting to grips with git-dpm (previously I have just used
git buildpackage). So I may have made some mistakes when attempting to
update to the latest versions. Its also probably prudent to have the
python-requests package depend on the latest version of python-urllib3
(which I have not changed). You can find the updated repositories here
[4], [5].

4: http://git.cbaines.net/python-requests/
5: http://git.cbaines.net/python-urllib3/

Thanks,

Chris

Re: Updating python-requests and python-urllib3

2015-12-22 Thread Christopher Baines 
On 22/12/15 17:20, Daniele Tricoli wrote:
> On Tuesday, December 22, 2015 03:49:05 PM Christopher Baines wrote:
>> I have had a go at updating python-requests to the latest upstream
>> release (from 2.8.1 to 2.9.1). This bundles the latest version of
>> python-urllib3 (1.13.1) so I have updated that also (from 1.12 to 1.13.1).
> 
> I'm going to work later on them or at max tomorrow, thanks for your work.

Great :)

> For #796717, however, there is no need to use requests: I did change the test 
> a bit to use urllib3 directly but I forgot to send to the bug report. 

That makes sense. It might be worthwhile to add the tests using requests
to the requests package, such that both packages (requests and urllib3)
would have DEP8 tests?

Updating python-jsmin

2015-12-22 Thread Christopher Baines 
python-jsmin [1] is not currently maintained by the Python Modules Team,
but I have made a attempt at updating it to the latest upstream version
in a manor compliant with the team policy.

You can find the package here [2]. Is anyone (including the current
maintainer CC'ed) interested in updating this package, and possibly
bringing it in to the team?

Thanks,

Chris

1: https://tracker.debian.org/pkg/python-jsmin
2: http://git.cbaines.net/python-jsmin/

Adopting factory-boy

2015-12-19 Thread Christopher Baines 
I use python-factory-boy [1] and recently realised that it was removed
from Debian [2]. The reasoning being that it is no longer a dependency
of some OpenStack packages.

I use this (currently through a package of the latest upstream release
created with py2dsc), and would be interested in getting this back in to
Debian.

Currently I am not a member of the Python modules team (request
pending), but I would be interested in maintaining it as part of the team.

The source package can be found here [3], would it be best to try to
continue with the history in that repository and bring it in to
compliance with the team policy (use pristine-tar, use upstream tarballs
to advance the upstream branch and use git-dpm), or to just start from
scratch?

Thanks,

Chris

1: https://tracker.debian.org/pkg/factory-boy
2: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804673
3: https://anonscm.debian.org/cgit/openstack/factory-boy.git/

Re: Request to join

2015-12-19 Thread Christopher Baines 
On 13/12/15 17:02, Christopher Baines wrote:
> I would like to join the python modules team. I am currently working on
> packaging sklearn-pandas, which I would like to maintain as part of the
> team. I am also interested in getting involved in general maintenance of
> team packages.
> 
> I have read an accept https://python-modules.alioth.debian.org/policy.html.
> 
> My alioth login is cbaines-guest.

Any chance of an update on this? I have found a potential sponsor, but
moving forward is blocking on creating a Git repository for
python-sklearn-pandas, which I currently can't do as I am not a member
of the team.

Request to join

2015-12-13 Thread Christopher Baines 
I would like to join the python modules team. I am currently working on
packaging sklearn-pandas, which I would like to maintain as part of the
team. I am also interested in getting involved in general maintenance of
team packages.

I have read an accept https://python-modules.alioth.debian.org/policy.html.

My alioth login is cbaines-guest.

Thanks,

Chris

RFS: sklearn-pandas

2015-11-22 Thread Christopher Baines 
Hello,

I am looking for a sponsor for the sklearn-pandas package.

* Package name: sklearn-pandas
  Version : 0.0.12
  Upstream Author : Israel Saeta Pérez 
* URL : https://github.com/paulgb/sklearn-pandas
* License : Zlib
  Programming Lang: Python
  Description : Pandas integration with sklearn

You can find the source package in this Git repository:
 http://git.cbaines.net/sklearn-pandas

Thanks,

Chris

cairocffi possible FTBFS

2015-07-19 Thread Christopher Baines 
When I tried to build the cairocffi package, I get an error related to
sphinxdoc [2].

This bug report seems to suggest that sphinxdoc should only be used if
sphinx-build from python3-sphnix is used, and I think on my system, I am
using the binary from python-sphinx.

I am not quite sure what to do about this, I assume this must be a
common issue?

Thanks,

Chris

1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712426
2:
   dh_sphinxdoc -O--buildsystem=pybuild
dh_sphinxdoc: ignoring unknown JavaScript code:
debian/python-cairocffi-doc/usr/share/doc/python-cairocffi-doc/html/_static/underscore-1.3.1.js
dh_sphinxdoc: error: unknown JavaScript code:
debian/python-cairocffi-doc/usr/share/doc/python-cairocffi-doc/html/_static/jquery.js


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55ab5e3a.60...@cbaines.net

Re: cairocffi possible FTBFS

2015-07-19 Thread Christopher Baines 
On 19/07/15 10:12, Dmitry Shachnev wrote:
 I am not quite sure what to do about this, I assume this must be a
 common issue?

dh_sphinxdoc -O--buildsystem=pybuild
 dh_sphinxdoc: ignoring unknown JavaScript code:
 debian/python-cairocffi-doc/usr/share/doc/python-cairocffi-doc/html/_static/underscore-1.3.1.js
 dh_sphinxdoc: error: unknown JavaScript code:
 debian/python-cairocffi-doc/usr/share/doc/python-cairocffi-doc/html/_static/jquery.js
 
 underscore-1.3.1.js file is in Sphinx source, but we do not ship it in Debian.
 Do you have a custom Sphinx installation (i.e. from PyPI) somewhere?

Yes, that was it. I had forgotten that I had done that on this machine.
I now have it building properly.

Second question, I would like to work on updating this package to the
latest upstream release. Assuming that the original uploader is not
doing, or planning to do this shortly?

If this is not the case, I am beginning to work out Debian packaging
stuff in git, so I would much rather use those associated tools. I see
that there is a wiki page on this here [1], would it be possible to
avoid using svn?

1: https://wiki.debian.org/Python/GitPackaging


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55ab744a.9090...@cbaines.net

Re: cairocffi possible FTBFS

2015-07-19 Thread Christopher Baines 
On 19/07/15 14:05, Jean-Christophe Jaskula wrote:
 The latest version (0.7.1) requires python-xcffib = 0.3.2 that has not hit 
 unstable yet. I have built a package with a custom installation and I poked 
 its maintainer. 
 
 I’ll push everything in svn soon. It should be a matter of days. 

Great, thanks :D


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55aba1e5.5020...@cbaines.net

Re: Trouble with PyDist files and versioned dependencies

2015-07-14 Thread Christopher Baines 
On 14/07/15 12:38, Piotr Ożarowski wrote:
 [Christopher Baines, 2015-07-14]
 I have a python package that I want to depend on python-lxml (= 3.3.1).

 So, I have put a .pydist file in debian/ containing.
 lxml python-lxml (= 3.3.1)
 
 .pydist file is used when other packages build depend on your package.
 (i.e. if you want to control what dependency other packages get, see
 f.e. sqlalchemy source package)

The dh_python2 manpage definitely suggests otherwise:

dh_python2  tries to translate Python dependencies from requires.txt
file to Debian dependencies. Use debian/pydist-overrides or
--no-guessing-deps option to over‐ride it if the guess is incorrect. If
you want dh_python2 to generate more strict dependencies (f.e. to avoid
ABI problems) create debian/python-foo.pydist file.


The guess was correct, just not strict enough. Hence I tried using the
pydist file.

 What you want is debian/pydist-overrides file or to add correct
 Build-Dependency and wait few more days for me to fix #791433

I cannot find a description of what should be in a
debian/pydist-overrides file. I tried just moving the pydist file, and
that seemed to work.

For completeness, I have debian/pydist-overrides containing:
lxml python-lxml (= 3.3.1)


Thanks very much for your prompt and extremely useful help :)

Chris


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55a4fbb3.8070...@cbaines.net

Trouble with PyDist files and versioned dependencies

2015-07-14 Thread Christopher Baines 
I have a python package that I want to depend on python-lxml (= 3.3.1).

So, I have put a .pydist file in debian/ containing.
lxml python-lxml (= 3.3.1)

This gets installed in the package, but the package still has a
unversioned dependency on python-lxml.

Looking at the source code in /usr/share/dh-python/dhpython/pydist.py I
can't quite tell if the functionality described in the documentation [1]
is even implemented, let alone just broken. It simply just seems to only
install the pydist file, and not consult the contents when deciding the
details of the dependencies?

Does anyone know what is going on here, and does anyone know of any
packages that succeed on getting dh_python2 to make versioned dependencies?

Thanks,

Chris

[1] Relevant part of man dh_python2
   dependencies
   dh_python2  tries  to translate Python dependencies from
requires.txt file to Debian dependencies. Use debian/pydist-overrides or
--no-guessing-deps option to over‐
   ride it if the guess is incorrect. If you want dh_python2 to
generate more strict dependencies (f.e. to avoid ABI problems)  create
debian/python-foo.pydist  file.
   See  /usr/share/doc/python-doc/README.PyDist  (provided  by
python-doc package) for more information. If the pydist file contains
PEP386 flag or set of (uscan like)
   rules, dh_python2 will make the depedency versioned (version
requirements are ignored by default).


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55a4f141.1070...@cbaines.net