Bug 1734038 - Ragel 7.0.0.12 is an unstable development release with incompatible command-line syntax
Summary: Ragel 7.0.0.12 is an unstable development release with incompatible command-l...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: ragel
Version: 31
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Jason Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1734036
TreeView+ depends on / blocked
 
Reported: 2019-07-29 13:56 UTC by Kevin Kofler
Modified: 2019-08-15 09:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-15 09:53:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kevin Kofler 2019-07-29 13:56:09 UTC
Description of problem:
Ragel 7.0.0.12, which is now shipped in Rawhide and already pushed to dist-git for f30 and f29 (but not submitted in Bodhi) is an unstable development release. And unfortunately, the new release has an incompatible command-line syntax: quoting from the ChangeLog:
> Separate ragel executable files are used
> to implement the different host languages.

This breaks the Trojitá build:
ragel: -C is an invalid argument
and it is not really surprising that dependent projects' build systems are not yet ready for the development release.

Version-Release number of selected component (if applicable):
ragel-7.0.0.12-2.fc31

How reproducible:
Always

Steps to Reproduce:
1. Try to build Trojitá against Ragel 7.0.0.12.

Actual results:
ragel: -C is an invalid argument

Expected results:
Trojitá builds

Additional info:
If you really think the new version is ready for Rawhide, please at least work with the packagers of depending packages to add support for the new split executables, also upstream. And please assume that upstream will want support for both the old and the new Ragel, so it needs to be autodetected.

It is NOT nice to get an incompatible update dropped on us that way with no warning.

Comment 1 Jason Taylor 2019-07-29 14:39:07 UTC
Sorry about that Kevin. Chris, Can you fix this? Thanks!

JT

Comment 2 Christian Glombek 2019-07-29 16:44:53 UTC
We have been at 7.0.0.x for years, which are all unstable development releases.

I guess it's just that so far 7 just worked in place of 6.

I don't do much packaging at the moment - how would I go about doing this?
Modularity with 2 release streams?

There still is a ragel6 spec, see https://bugzilla.redhat.com/show_bug.cgi?id=1734036#c2

Comment 3 Kevin Kofler 2019-07-29 17:04:51 UTC
Maybe you can just revert or partially revert commit 0793d404a5ea9b955dc31a6aeea6414e03d46e54? Or should we just update Trojitá's https://cgit.kde.org/trojita.git/tree/cmake/FindRagelForTrojita.cmake to support the new release, which is probably the better long-term solution, unless we can convince Ragel upstream to retain CLI compatibility? Do you know how many other projects are affected by this incompatibility?

Whatever the problem is, Modularity is not the solution. If you have a problem and introduce Modularity, you have 2 problems. ;-)

Comment 4 Christian Glombek 2019-07-29 18:53:51 UTC
+1 for adapting trojita to support current ragel 7.

Also open to adding a ragel6 rpm (if we can do that according to guidelines, without modularity),
especially now that we cannot assume cli compat anymore.

Comment 5 Ben Cotton 2019-08-13 16:53:02 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 6 Ben Cotton 2019-08-13 18:52:48 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 7 Kevin Kofler 2019-08-15 09:53:21 UTC
The way forward is probably to handle this change in Trojitá. Closing this bug.


Note You need to log in before you can comment on or make changes to this bug.