Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #10086
| From | peter green <plugwash@p10link.net> |
|---|---|
| Newsgroups | linux.debian.maint.python, linux.debian.bugs.dist |
| Subject | Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref |
| Date | 2018-01-25 19:00 +0100 |
| Message-ID | <vbTYB-yG-7@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
> However, in Debian case, I do not know how this can be handled as 2 packages cannot hold the same file (even if __init__ is only an empty file), and at least one must be present (if you install only one). I'm not a python expert but I expect the least-horrible way to do this would be to ship a package that only contained the __init__. Then have all the python-backports.* packages depend on it.
Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread
Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref peter green <plugwash@p10link.net> - 2018-01-25 19:00 +0100
Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref Simon McVittie <smcv@debian.org> - 2018-01-26 01:50 +0100
Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref Piotr Ożarowski <piotr@debian.org> - 2018-01-26 10:10 +0100
csiph-web