You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Repository configurations for fedora support using repo variables (see the docs). Those variables would make it easier to use the repo. Especially when upgrade to a newer fedora version, no manual actions must be performed. Furthermore when uploading the repo config file, the setup would be even easier. A good example would be the docker repo for fedora (repo and docs). The following example would map this to the tuxedo repo:
Note the missing skip_if_unavailable=False. Unless there is a good reason for adding this line, I would suggest removing it since otherwise one could only update to newer fedora versions as soon as you support it (BTW: you currently not support fedora 40 which is on the horizon, see the schedule - at least the tuxedo-drivers work on fedora 40, the rest I have not installed) and if your web server is down, users could not update their packages.
Furthermore I used a more readable name for the gpg key without multiple copies of the same within the version subdirectories. If there is a reason of copying the same key into the different subdirectories, one could use the line gpgkey=https://rpm.tuxedocomputers.com/fedora/$releasever/gpg.
To provide backwards compatibility the subdirectories 37, 38, and 39 should still contain the gpg key with the old name, but 40 should not.
The content of the file then should be uploaded to https://rpm.tuxedocomputers.com/fedora/tuxedo.repo. These changes would make it possible to set up the repo as simple as running the command:
When installing a package from this repo, the gpg key will automatically be imported (after the user accepted the key). The fingerprint of the key should be included in your docs so that the user is able to check if everything is good (like docker does it, see).
The text was updated successfully, but these errors were encountered:
Repository configurations for fedora support using repo variables (see the docs). Those variables would make it easier to use the repo. Especially when upgrade to a newer fedora version, no manual actions must be performed. Furthermore when uploading the repo config file, the setup would be even easier. A good example would be the docker repo for fedora (repo and docs). The following example would map this to the tuxedo repo:
The content of
tuxedo.repo
:Note the missing
skip_if_unavailable=False
. Unless there is a good reason for adding this line, I would suggest removing it since otherwise one could only update to newer fedora versions as soon as you support it (BTW: you currently not support fedora 40 which is on the horizon, see the schedule - at least thetuxedo-drivers
work on fedora 40, the rest I have not installed) and if your web server is down, users could not update their packages.Furthermore I used a more readable name for the gpg key without multiple copies of the same within the version subdirectories. If there is a reason of copying the same key into the different subdirectories, one could use the line
gpgkey=https://rpm.tuxedocomputers.com/fedora/$releasever/gpg
.To provide backwards compatibility the subdirectories
37
,38
, and39
should still contain the gpg key with the old name, but40
should not.The content of the file then should be uploaded to
https://rpm.tuxedocomputers.com/fedora/tuxedo.repo
. These changes would make it possible to set up the repo as simple as running the command:$ sudo dnf config-manager --add-repo https://rpm.tuxedocomputers.com/fedora/tuxedo.repo
When installing a package from this repo, the gpg key will automatically be imported (after the user accepted the key). The fingerprint of the key should be included in your docs so that the user is able to check if everything is good (like docker does it, see).
The text was updated successfully, but these errors were encountered: