-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Crystal installer doesn't work for Fedora 41 #868
Comments
Thanks for the feedback. Could you be more specific what you mean with "unreliable" and "behind"? Sure we can add this community repository to the installation page. Thanks for suggesting that 👍 However I did take a quick look at it and I noticed a couple of things that seem a bit off to me. Might be caused by my unfamiliarity with Fedora/COPR. Also I'm wondering is there a reason that thare is no package for Fedora Rawhide? Please forgive me if any of these questions are trivial, I really don't know much about the Fedora ecosystem. |
Basically, One cannot upgrade (to fedora 41) and trust the repos to be available on day one. This is "unreliable". I am sorry if the term isn't quite correct. English isn't my first language.
Sure thing.
The package list will show all the packages Zawertun is building for now (probably a mistake by the packager, eh? I'll report it). Yet, those pacakges aren't available in the zawertun repo. The version on the reported source repo is, indeed, lagging behind. The repo where it was built from isn't. Check the "Dist Git Repo" here: https://copr.fedorainfracloud.org/coprs/zawertun/crystal/package/crystal/ It will show you the actual repo utilized for building. The packager might've forgotten to update the repo's metadata. I will report these two issues to him, though. That said, the repo is very consistent:
|
Well, it's just a matter of postulating the package, have it reviewed and maintained within the Fedora infrastructure. Anyone can apply to it: https://docs.fedoraproject.org/en-US/packaging-guidelines/ Those are quite extensive because they cover all use cases. In general, once you're aquainted with those, it's not that hard to maintain packages. Rawhide is the "rolling release/development" repository. Scratch builds go there. Then, they get promoted to the production repos.
No worries. I am glad to answer as best as I can. |
This is the commit that generated the latest RPMs for Fedora 41. We have similar commits for Fedora 40, 39 and, also, CentOS Stream 9 and 8. |
Ok gotcha. Yeah this is indeed a nuisance. The build system we're currently using for our packages (OBS) requires manual interaction to enable a repository for a new distribution release. The lack of automation is why it lags behind 😞 |
Hello,
With respect, the Fedora repos for crystal you, guys, host have always been unreliable. They're, usually, behind.
I would like to recommend to either enroll Zawertun to do the packaging or to just rely on his COPR repo:
https://copr.fedorainfracloud.org/coprs/zawertun/crystal/
I've been using that repo for years. He's very kind, responds quickly when I email him to ask for, say, support for LLVM 17 or stuff like this.
He's always out very early. Even before crystal announces the release (due to automation probably).
In any case, I think it's a good idea, at the very least, to list him as a community provider.
https://github.com/ZaWertun
The text was updated successfully, but these errors were encountered: