-
Notifications
You must be signed in to change notification settings - Fork 20
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
Updated dino repo link to get correct repo #14
Conversation
Does the $VERSION_ID will be resolved by fedy at install time or is it possible to use the $releasever variable in the repo definition so it will be adapted across Fedora version upgrade ? |
I changed it, maybe better this way. |
Not really, he ask for it everytime to push the install button from dino. |
So I guess you still miss-understand why your patch is wrong ? |
Yes sorry
Am 13. Dezember 2019 13:47:51 MEZ schrieb "Nicolas Chauvet (kwizart)" <notifications@github.com>:
…So I guess you still miss-understand why your patch is wrong ?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#14 (comment)
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
|
$releasever is a special variable used in a repo url that will be evaluated to the appropriate fedora version whenever one decide to upgrade fedora. There is no need to hit install again to have every single repository updated to the appropriate version. This will save errors when a more appropriate package is available for a newer fedora release. |
Any update with the appropriate fix ? |
I get it now. |
It looks like dino is in fedora. Fixed as appropriate in fedy 5.0.2 BTW, looking at using $releasever doesn't seem possible with dnf config-manager, we would need another hack (like using the current version and then patching the file to use releasever instead of a hardcoded version...). |
No description provided.