-
Notifications
You must be signed in to change notification settings - Fork 236
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
Add rpmautospec plugin #1253
Add rpmautospec plugin #1253
Conversation
The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
vcs-diff-lint found more than 10 potential problems in the proposed changes. Check the Files changed tab for more details.
Thank you for your contribution! Nice. Can you please document the plugin https://rpm-software-management.github.io/mock/#plugins ? Some of the new PyLint warnings are too pedantic (I'm going to tweak the
But we also require it also host because of Have you considered calling the host tooling (on the sources stored in-chroot)? |
Also, can you please write a release notes entry, template:
|
9d613c1
to
6986b10
Compare
Can you please also add a "commented out" plugin-config into the docs file |
325f8ab
to
98503b1
Compare
Hello @nphilipp! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
Comment last updated at 2023-12-07 13:16:31 UTC |
This actually conforms to what PEP8 says about breaking lines around binary operators: https://peps.python.org/pep-0008/#should-a-line-break-before-or-after-a-binary-operator |
Two missing things:
|
I’ve set the PR to be ready for review (which I should have done a while ago already).
The new package update has been in testing for a couple of days: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-9e47a8b73c I’m trying to get karma for it 😉.
I'll do this (and squash the commits into one). |
This plugin preprocesses spec files using %autorelease and/or %autochangelog in the mock chroot prior to building SRPMs. The `rpmautospec` package will be installed into the chroot if necessary. Co-authored-by: Nils Philippsen <[email protected]> Signed-off-by: Stephen Gallagher <[email protected]> Signed-off-by: Nils Philippsen <[email protected]>
@praiskup the update should be available with the next EPEL8 compose and I’ve added the reasons for doing this in the chroot as a comment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you.
Just getting back to this; I still think this is a bad idea. The Mock's mission should be to abstract from the in-chroot nuances, and rely on "easily fixable" on-host tooling (by example, that way you can bootstrap a new distribution without having the autospec tooling built yet, or build fedora packages with autospec against distributions that do not support it). |
This plugin preprocesses spec files using %autorelease and/or %autochangelog in the mock chroot prior to building SRPMs. The
rpmautospec
package will be installed into the chroot if necessary./cc @sgallagher