FS#62687 - [python-perf] package name conflict: need rename to python-pyperf
Attached to Project:
Community Packages
Opened by Daurnimator (daurnimator) - Tuesday, 21 May 2019, 04:24 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:00 GMT
Opened by Daurnimator (daurnimator) - Tuesday, 21 May 2019, 04:24 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:00 GMT
|
Details
'perf' is the name of the python bindings to the linux
'perf' utility.
The upstream of this current python-perf package has resolved the naming conflict by renaming their project (https://github.com/vstinner/pyperf/commit/60eb936a87e287c578e85ab33b8b9a91d609ba53) to 'pyperf'. We should rename this package to make room for the linux perf tool bindings. |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:00 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/python-perf/issues/1
Saturday, 25 November 2023, 20:00 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/python-perf/issues/1
EDIT: I misread, it's not an orphan
we gonna wait until its solved properly and there is a way out, dropping is not an option its a widely used toolset to profile python.
ld;dr: gonna rename the package during this week and free up "python-perf", but we will need some "migration persion" which holds a replaces=() for some while to allow transparent migration path. If we dont want this, we need some news entry as people will end up with different packages for python-perf suddenly.
I see PKGBUILD replaces=() support versions, so what do you think of adding something like replaces=(python-perf<=1.6-5) in the new package. There no need for migration wait period, this could work as soon as the new package is released (and be kept forever).
Linux-tools base package is in version 5.11, so versioning is higher and the first release will be >1.6-5.
[1] https://github.com/archlinux/svntogit-community/commit/d48ca1ff3efc1386533ff6392390ab5c78af6881
This bug can only be closed once we rename the current `pkgname='python-perf'` to `pkgname='python-pyperf'`; thereby freeing up `python-perf` for the real thing.