On Mon, Apr 08, 2024 at 04:11:14PM +0200, Petr Pisar wrote:
> V Mon, Apr 08, 2024 at 11:37:48AM +0000, Zbigniew Jędrzejewski-Szmek
> napsal(a):
> > OK, so you mean that the approach with '.<minorbump>' at the end of Release
> > doesn't work. Yes, that case is not supported very well.
> >
> > There is no great solution here, but there are a few options. Which
> > one makes the most sense depends a lot on the package. But in particular:
> > - just switch to non-autorelease numbering when introducing the
> > minorbump, e.g. just do Release: 15%{?dist}.1 and then .2, etc.
> >
> > Looking at the docs again, the docs are not great, and we should
> > support this case better. This certainly needs looking into.
> >
> Now I recalled yet another downstream issue: Importing without a git history
> will reset release numbers. That hashes RPM-dependencies which refer to
> a specific release (like "Conflicts: foo < 1-20" after a package split). One
> should of course carefully check them on import, but forking whole
> distribution like that into a new downstream distribution warrants there will
> remain gems like this.
I can feel the pain, but realistically, with 31% of specs in Fedora using
rpmautospec (as discussed in another leg of the thread), any downstream will
need to solve this issue programatically. Whether it's 15%, 30%, or 90%
of packages, doesn't matter at this point… it must be handled by a script.
Essentially this ship sailed when rpmautospec was officially allowed
in Fedora and was used in the first hundred packages. At that point,
downstream has no choice but to adapt.
Zbyszek
--
_______________________________________________
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
