New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[python3-yaml] update to 5.4.1.1. Contributes to JB#58954 #1
Conversation
|
The current .spec packages documentation as well. If requested, I can remove those from the package (or put in a subpackage) after the version has been decided. |
|
To me updating to 5.4.1.1 makes most sense. I created an item for this in our internal bug tracker, so perhaps you could add "JB#58954" to the commit message? As for the documentation, your suggestion to separate it to a subpackage makes sense, but let's do that in a separate PR. |
b2b005a
to
a39b36f
Compare
|
Please also add 'BuildRequires pkgconfig(yaml-0.1)' so it picks up libyaml properly instead of using internal yaml implementation. |
a39b36f
to
e6d0fd3
Compare
|
dependency added and squashed |
|
rpmlint suggests to switch to BuildArch: noarch. Is it right? I'm never sure with python packages. |
I kind of wish Thaodan hadn't asked you to add the dependency, as it's a bit out of scope here. The old version wasn't using libyaml either. But anyway, since you already started moving towards that direction... Just adding pkgconfig(yaml-0.1) isn't enough. You need python3dist(cython) as well. |
Well, technically speaking, for the current package, rpmlint speaks the truth. However, once you get it to use libyaml, it will contain architecture-specific library, so after that noarch will no longer do. But I suppose rpmlint will also stop complaining. |
|
According to my tests, it seems to work. However, I would still like those commits cleaned up a bit before merging. i.e. both BuildRequirements added in a single commit, with a nice commit message with a changelog entry. e.g. |
63310e5
to
b8c865e
Compare
|
Thank you! |
There are three possible update candidates for this package:
The fork this PR originates from has branches implementing a bump for each of those. 5.4 is proposed here as a middle ground between conservative bump and security fixes gained.
For testing packages are available for each of these: https://build.merproject.org/project/show/home:nephros:sailfishos:python
The main motivation for this PR is the ability to bump the 'yq' tool (in chum) to a more recent version - which requires pyyaml >= 3.5.1.
Due to the "don't ship packages which replace system packages" agreement on Chum, we can't bump pyyaml there.
The only user of this package I am aware of is the spectacle tool, which works fine with 5.4.x, but there might be others to test.