Where to access RPM counterpart of current ISO of release?

Ask Fedora
1

Context

Discrepancy

As of +2024-08-21T22:25:38+01:00, Fedora KDE Plasma Desktop | The Fedora Project offers Fedora-KDE-Live-x86_64-40-1.14.iso. However, Koji offers solely 40-0* releases, as is visible at fedora-release | Package Info | koji.

Consequently, how can I access the compilation log for that specific ISO? I ask because it adheres to the expected naming convention, yet merely is of a version which doesn’t appear to be available via the standard GUI.

1 Like
2

You cannot, because they are unrelated.

None of the package release tags is related to the release tag of the ISO image.
The only common part they have is version, that is 40.

Leaving aside Atomic builds, Fedora has only major release versions.
There are no minor versions during release.

For RPMs, a dash is the only valid separator between version and release tags.
A period can only be part of the version or release tag.

2 Likes
3

So, koji.fedoraproject.org is our build system. Any number of builds,
for any number of reasons could be in there. koji uses a tagging system
to mark what builds are in specific tags, and then compose tooling looks
at packages in those tags to compose images, etc.

Fedora-KDE-Live-x86_64-40-1.14.iso is the image made for the fedora 40
release. It’s never changed after that. It’s released. So it will never
have newer packages in it.

Rawhide images are produced nightly, and thus (barring failues) have the
latest f42 tagged packages.

Fedora nightly compose finder has a list of those
images that last passed testing.

There is also a ‘respins’ sig that makes updated stable release images:
https://dl.fedoraproject.org/pub/alt/live-respins/
(thats the release with all updates added)

Theres a bunch more complexity here, but hopefully the above helps…

1 Like
4

@kevin, that explains a fair bit. However, the undermentioned appears to contradict it:

Those URIs both list ISOs from +2024-08-20, which is certainly an improvement. Thank you.

5

@kevin, that explains a fair bit. However, the undermentioned appears to contradict it:

[quote=“Kevin Fenzi, post:3, topic:129186, username:kevin”]
Fedora nightly compose finder has a list of those
images that last passed testing.

Those are all prerelease images. Not stable releases that have already
been released. :wink: So you will find rawhide (f42) and branched (f41)
there, but no where will there be f40/f39.

There is also a ‘respins’ sig that makes updated stable release images:
Index of /pub/alt/live-respins
(that’s the release with all updates added)
[/quote]

Those URIs both list ISOs from +2024-08-20, which is certainly an improvement. Thank you.

Yeah, they do save a ton of updates downloading for sure.

1 Like
6

@vgaetera, I forgot to ask - does that mean that the -0 and -1 are meaningless? I don’t know how else to think of the designations except as minor releases. Can you elaborate?

7

The release tag consists not only of a single digit, but also the period and the following characters up to the next dash, it helps distinguish different builds of the same version.

Image and package builds use a similar versioning scheme, but their release tags are not related, and there are no official image builds after the final release, except for respins.

2 Likes
8

Take for example bash-5.2.26-3.fc40.x86_64. This splits into

Name        : bash
Version     : 5.2.26
Release     : 3.fc40
Architecture: x86_64

The Version is the upstream version and the Release is the local build version which are changed every time a build is attempted. To see the list of bulds, see https://koji.fedoraproject.org/koji/packageinfo?packageID=1088.

1 Like