Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #10802
| From | Pierre-Elliott Bécue <becue@crans.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Best way to handle circular build deps to make a pypy- package |
| Date | 2018-08-15 13:10 +0200 |
| Message-ID | <wn1QC-6Qe-27@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Hi,
I was asked a long time ago to make a pypy package for nose2[1]. I realized
while considering this bug that I'd require to have a pypy package for mock
first. mock build-depends on unittest2 and pbr that are not pypy-packaged
either.
pbr is maintained in the OpenStack Team, but zigo is eager to help me should
I provide a sustainable MR. The thing is, pbr build-depends (indep) on
mock[3].
The way I see it, a solution is to:
1. Build the pypy-pbr package without the testing phase (which seems to be
the part where mock is required), and upload it.
2. Build the pypy-mock package and upload it.
3. Rebuild the pypy-pbr package with the testing phase and upload it.
But that doesn't satisfy me, because I guess sometimes I couldn't use this
subterfuge to build the packages.
So I have two questions :
1. Are there other packages with the same circular build-dep thing, and if
so, can someone provide me with examples?
2. What's the proper way to handle such packages?
Thanks a lot!
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887933
[2] https://tracker.debian.org/media/packages/p/python-mock/control-2.0.0-3
[3] https://tracker.debian.org/media/packages/p/python-pbr/control-3.1.1-4
--
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.
Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread
Best way to handle circular build deps to make a pypy- package Pierre-Elliott Bécue <becue@crans.org> - 2018-08-15 13:10 +0200
Re: Best way to handle circular build deps to make a pypy- package Ghislain Vaillant <ghisvail@gmail.com> - 2018-08-15 13:20 +0200
Re: Best way to handle circular build deps to make a pypy- package Samuel Thibault <sthibault@debian.org> - 2018-08-15 13:20 +0200
Re: Best way to handle circular build deps to make a pypy- package Pierre-Elliott Bécue <becue@crans.org> - 2018-08-15 15:20 +0200
Re: Best way to handle circular build deps to make a pypy- package Pierre-Elliott Bécue <becue@crans.org> - 2018-08-15 15:50 +0200
Re: Best way to handle circular build deps to make a pypy- package Samuel Thibault <sthibault@debian.org> - 2018-08-15 17:40 +0200
Re: Best way to handle circular build deps to make a pypy- package Thomas Goirand <zigo@debian.org> - 2018-08-20 16:30 +0200
Re: Best way to handle circular build deps to make a pypy- package Pierre-Elliott Bécue <becue@crans.org> - 2018-08-20 18:50 +0200
csiph-web