question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Automatically determine fedora-all, fedora-stable and fedora-development aliases

See original GitHub issue

Right now, the aliases for fedora-all, fedora-stable and fedora-development are hard-coded in packit/config/aliases.py

It would be better if this was replaced by a query to the public Bodhi REST API to get the current list of stable and development branches. For example (stable releases):

curl "https://bodhi.fedoraproject.org/releases/?exclude_archived=true&state=current" |json_reformat
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  7903  100  7903    0     0  14214      0 --:--:-- --:--:-- --:--:-- 14239
{
    "releases": [
...
        {
            "name": "F30",
            "long_name": "Fedora 30",
            "version": "30",
            "id_prefix": "FEDORA",
            "branch": "f30",
            "dist_tag": "f30",
            "stable_tag": "f30-updates",
            "testing_tag": "f30-updates-testing",
            "candidate_tag": "f30-updates-candidate",
            "pending_signing_tag": "f30-signing-pending",
            "pending_testing_tag": "f30-updates-testing-pending",
            "pending_stable_tag": "f30-updates-pending",
            "override_tag": "f30-override",
            "mail_template": "fedora_errata_template",
            "state": "current",
            "composed_by_bodhi": true,
            "create_automatic_updates": null,
            "package_manager": "dnf",
            "testing_repository": "updates-testing",
            "composes": [

            ]
        },
        {
            "name": "F31",
            "long_name": "Fedora 31",
            "version": "31",
            "id_prefix": "FEDORA",
            "branch": "f31",
            "dist_tag": "f31",
            "stable_tag": "f31-updates",
            "testing_tag": "f31-updates-testing",
            "candidate_tag": "f31-updates-candidate",
            "pending_signing_tag": "f31-signing-pending",
            "pending_testing_tag": "f31-updates-testing-pending",
            "pending_stable_tag": "f31-updates-pending",
            "override_tag": "f31-override",
            "mail_template": "fedora_errata_template",
            "state": "current",
            "composed_by_bodhi": true,
            "create_automatic_updates": false,
            "package_manager": "dnf",
            "testing_repository": "updates-testing",
            "composes": [

            ]
        },
...
    ],
    "page": 1,
    "pages": 1,
    "rows_per_page": 20,
    "total": 12
}

(The results should be restricted to those with the id_prefix of FEDORA).

For Branched and Rawhide releases:

➤ curl "https://bodhi.fedoraproject.org/releases/?exclude_archived=true&state=pending" |json_reformat
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1956  100  1956    0     0   3935      0 --:--:-- --:--:-- --:--:--  3943
{
    "releases": [
        {
            "name": "F33",
            "long_name": "Fedora 33",
            "version": "33",
            "id_prefix": "FEDORA",
            "branch": "f33",
            "dist_tag": "f33",
            "stable_tag": "f33",
            "testing_tag": "f33-updates-testing",
            "candidate_tag": "f33-updates-candidate",
            "pending_signing_tag": "f33-signing-pending",
            "pending_testing_tag": "f33-updates-testing-pending",
            "pending_stable_tag": "f33-updates-pending",
            "override_tag": "f33-override",
            "mail_template": "fedora_errata_template",
            "state": "pending",
            "composed_by_bodhi": false,
            "create_automatic_updates": true,
            "package_manager": "unspecified",
            "testing_repository": null,
            "composes": [

            ]
        },
...
        {
            "name": "F32",
            "long_name": "Fedora 32",
            "version": "32",
            "id_prefix": "FEDORA",
            "branch": "f32",
            "dist_tag": "f32",
            "stable_tag": "f32",
            "testing_tag": "f32-updates-testing",
            "candidate_tag": "f32-updates-candidate",
            "pending_signing_tag": "f32-signing-pending",
            "pending_testing_tag": "f32-updates-testing-pending",
            "pending_stable_tag": "f32-updates-pending",
            "override_tag": "f32-override",
            "mail_template": "fedora_errata_template",
            "state": "pending",
            "composed_by_bodhi": false,
            "create_automatic_updates": true,
            "package_manager": "dnf",
            "testing_repository": "updates-testing",
            "composes": [

            ]
        }
    ],
    "page": 1,
    "pages": 1,
    "rows_per_page": 20,
    "total": 3
}

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:2
  • Comments:16 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
sgallaghercommented, Jun 1, 2020

@ffoto1620 No, it is a stop-gap measure that just updates the aliases to the current stable releases.

0reactions
lachmanfrantisekcommented, Oct 1, 2020

Here is a conclusion what needs to be done:

  • Get the info about current stable/all/development versions via Bodhi REST API or via bodhi Python client.
  • Use hardcoded values if Bodhi is not available.
  • When used in Copr, check that the values are present in Copr. (You can use or get inspired by available_chroots method implemented last week by @mfocko )
Read more comments on GitHub >

github_iconTop Results From Across the Web

Upgrading to a new release of Fedora
This is the recommended upgrade method for the Fedora Workstation. In Fedora Workstation, when the next stable release is available, a graphical notification ......
Read more >
Fedora Packages of R Software
Fedora. The newest R release (including recommended packages as well as development headers and tools) can be installed by running
Read more >
Fedora
Fedora creates an innovative, free, and open source platform for hardware, clouds, and containers that enables software developers and community members to ...
Read more >
An Installation And First Look Of Fedora 35 - YouTube
I'm taking a quick look at the recently released Fedora 35. After my recent negative review of Ubuntu 21.10 with the GNOME desktop, ......
Read more >
GitHub - xsuchy/fedora-upgrade
Check if dependencies are installed and install them. This step is only needed if you download the script from GitHub. Dependencies are always...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found