Merge python-gobject and python3-gobject.
Fixes T3904.
Details
Details
- Reviewers
JoshStrobl DataDrake - Group Reviewers
Triage Team - Maniphest Tasks
- T3904: python2 and python3 provide a same pkgconfig for gobject
Rebuilt ibus-anthy, caribou, network-manager, firewalld.
Diff Detail
Diff Detail
- Repository
- R2512 python-gobject
- Branch
- master
- Lint
No Linters Available - Unit
No Unit Test Coverage
Event Timeline
Comment Actions
You need to do a replaces on python3-gobject and python3-gobject-devel, while I ponder the meaning of life and any consequences of this merge.
Test Plan
Not needed?
Except ya know, it is? You should be compiling against this new python-gobject-devel package, as an example, across both python2 and python3 applications.
| package.yml | ||
|---|---|---|
| 2–3 | This needs to be bumped higher than python3-gobject otherwise it'll fail to land in the repo due to being same relnum (or less than). | |
Comment Actions
Except ya know, it is? You should be compiling against this new python-gobject-devel package, as an example, across both python2 and python3 applications.
OK, see ya in a few years!
Comment Actions
Nothing requires python*-gobject-devel though, gobject is only required as a rundep. I checked that with eopkg info.
Comment Actions
Nothing requires python*-gobject-devel though, gobject is only required as a rundep.
Just because nothing is marked as a revdep (which doesn't happen with python unless you explicitly make rundeps) doesn't mean the pkgconfig or the pkg names aren't marked as builddeps.
Comment Actions
❯ for file in $(find -name package.yml); do; grep -H python-gobject-devel $file; done ./ibus-anthy/package.yml: - python-gobject-devel ./caribou/package.yml: - python-gobject-devel ./network-manager/package.yml: - python-gobject-devel ./firewalld/package.yml: - python-gobject-devel # check
I'm going to rebuild these.
Comment Actions
I'm not sure whether to rebuild packages using pkgconfig(pygobject-3.0) given that it was pointing to two packages...