No SHA256 sum for LXDE spin

There is no SHA256 sum for LXDE distro in the CHECKSUM file
https://spins.fedoraproject.org/static/checksums/Fedora-Spins-30-1.2-x86_64-CHECKSUM

How could it be?!

1 Like
$ grep -i LXDE Fedora-UNOFFICIAL-30-20190427.0-x86_64-CHECKSUM 

# Fedora-LXDE-Live-x86_64-30-20190427.n.0.iso: 1345683456 bytes
SHA256 (Fedora-LXDE-Live-x86_64-30-20190427.n.0.iso) = acb62d33424c5867334c5eb22fbc83bfc449724d078a2e696100659f20acfaa6
1 Like

https://dl.fedoraproject.org/pub/alt/unofficial/releases/30/x86_64/Fedora-UNOFFICIAL-30-20190427.0-x86_64-CHECKSUM

2 Likes

Oh, but can I ask why it’s UNOFFICIAL?

Is it not that well maintained? Unsolid? Malicious functionality, perhaps?

1 Like

This file is signed with the official GPG key and the signature is valid.
Likely it wasn’t an official release image but sort of pre-release originally.

2 Likes

Welcome to the community @today20190816. Please take a look at the informative posts in #start-here if you’ve not had the chance yet.

I think it should be there. Could someone please speak to the LXDE contributors to confirm? They can be reached on their mailing list.

PS: Since this topic is being discussed in English, I’ve moved it to the English categories.

3 Likes

If I’m not wrong, when there was the last F30 Go/No-Go meeting, it was decided that all the criteria were meet in order for the operating system to be released. But at that time, some isos have failed to build. One of these was LXDE.
So, since LXDE is not a release blocking iso, it was agreed to release it some days later as an unofficial build. Unofficial doesn’t mean that it is unmaintained, error prone, etc. Simply it was not produced following the default path.

Here you can find the Go/No-Go meeting log: https://meetbot.fedoraproject.org/fedora-meeting-1/2019-04-26/f30-final-go_no_go-meeting.2019-04-26-17.00.log.html

2 Likes

Thanks for in-depth explanation!

1 Like