Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11786
| From | Joseph Herlant <aerostitch@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python, linux.debian.devel.release |
| Subject | Re: dh-python and pylint |
| Date | 2019-09-11 19:50 +0200 |
| Message-ID | <yFeUF-2gO-5@gated-at.bofh.it> (permalink) |
| References | <yBbC2-2b6-13@gated-at.bofh.it> <yBDyi-3xR-9@gated-at.bofh.it> <yBDRE-3IG-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
Hi! > thanks a lot, but what about backports. On backports we still need this mapping. Aren't the backports built using the dh-python version of the platform they are ported to? In this case it shouldn't really matter right? I see that Ubuntu released a new dh-python with this exact fix. It seems to work fine. Right now the packages we push with the pylint3 dependency renamed still end up with pylint3 as dependency, so should we hold off on the auto-pylint transition until https://salsa.debian.org/python-team/tools/dh-python/merge_requests/9 is merged and release? Or is an automatic rebuild of the packages having that problem planned when that fix in dh-python is release? Thanks, Joseph
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread
dh-python and pylint PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2019-08-31 15:30 +0200
Re: dh-python and pylint Sandro Tosi <morph@debian.org> - 2019-09-01 21:20 +0200
RE:dh-python and pylint PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2019-09-01 21:40 +0200
Re: dh-python and pylint Joseph Herlant <aerostitch@debian.org> - 2019-09-11 19:50 +0200
csiph-web