Before any such ideas continue, I think rpmautospec should have more
decent documentation. Unfortunately it does not have even manual page
for rpmautospec command, core of its functionality. I find that missing.
While I think rpmautospec is great idea, I do not think it is ready
universally.
Correct me if I am wrong, but I think there is no way to make rightmost
bump as done by rpmdev-bumpspec -r. We use it a lot for RHEL minor
version updates. But there does not seem to be a way to mark some
commit, after which only rightmost bumps should occur. While I have
intentionaly converted many my packages, I am keeping some more
complicated intentionally the old way. Especially because it allows me
to rebuild those packages for CentOS/RHEL and compare their functionality.
Is there full support for rpmautospec in COPR for example? I don't know.
I have not seen it mentioned in docs. It seems too early for any MUST
related with this.
On 07. 04. 24 17:15, Zbigniew Jędrzejewski-Szmek wrote:
Hi everyone,
I'm revisting the topic of rpmautospec because I was doing some work
on various packages, and it's annoying that some packages are using
rpmautospec and others are not.
All my packages have been converted, so in day-to-day work, I don't
even think about %changelog. When working with other packages, I'll
forget to update the Relase and/or %changelog. Today I was rebasing
some pull requests in pagure, and the _only_ conflicts that I had were
about Release and %changelog.
I think it's time to switch to rpmautospec completely.
Thus, the proposal:
- new packages MUST use rpmautospec
I think this still be SHOULD. AFAIK rpmfusion does not work with
rpmautospec and other distributions may not as well. Forcing this to
everyone does not seem reasonable to me, although I would recommend it
everywhere where possible.
- packagers SHOULD convert their packages
- provenpackagers MAY convert existing packages
(e.g. when they want to push some fix or separately from other
work)
No, please don't. provenpackagers should not make significant changes to
packages without communication with their maintainers. rpmautospec
conversion requires change of workflow and should never be done without
maintainer agreement. PR are okay, but not direct commits.
- people submitting pull requests against src.fp.o MAY also
include a conversion in the pull request and packagers SHOULD
merge it.
(FTR, 'rpmautospec convert' does the conversion, incl. the commit
to dist-git. Manual conversion should not be used.)
Zbyszek
This again should be documented in installed package. Sadly it does not
contain even README doc file with very basic information. Or it does in
python3-rpmautospec, which is where I doubt those information is usually
expected.
I think easy to find documentation with skip changelog [1] instructions
should be easy to find on the installed system. I do not think it is.
1.
https://fedora-infra.github.io/rpmautospec-docs/autochangelog.html#skipping-changelog-entries
--
Petr Menšík
Software Engineer, RHEL
Red Hat,http://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
