[Bug] `4.5.0.25` is missing at the SailfishOS:Chum and SailfishOS:Chum-Testing repositories

[Olf0]

trafficstars

4.5.0.24_{aarch64|armv7hl|i486} is currently the most recent, supported SailfishOS release. Hence @rinigus / @piggz please …

• Add the three targets 4.5.0.25_{aarch64|armv7hl|i486} to the SailfishOS:Chum repository
• Replace the three targets 4.5.0.24_{aarch64|armv7hl|i486} by 4.5.0.25_{aarch64|armv7hl|i486} at the SailfishOS:Chum-Testing repository

Alternatively you might grant me the right to perform these regularly required actions (i.e. each time a new version of SailfishOS is released).

[rinigus]

As far as I understood, 4.5.0.25 is made via HTTP alias to 4.5.0.24. So, while OBS target is missing, repo should be there already. See https://repo.sailfishos.org/obs/sailfishos:/chum/4.5.0.25_armv7hl/

[Olf0]

Thanks, yes, that appears to be the case. Hence closing.

P.S.: I wonder why @lbt does not also link / redirect other point release repos to their final point release; at least for SailfishOS:Chum. This would save some storage space and reduce the build targets for SailfishOS:Chum by eliminating eight target releases with each three architectures (i486, armv7hl, aarch64), i.e. 24 (!) build targets:

• 4.3.0.12_* → 4.3.0.15_*
• 4.4.0.58_*, 4.4.0.64_*, 4.4.0.68_* → 4.4.0.72_*
• 4.5.0.16_*, 4.5.0.18_*, 4.5.0.19_*, 4.5.0.21_* → 4.5.0.24_*

While I am a strong proponent of letting the users decide when and if (at all) they update their SailfishOS installations (due to the lack of backward compatibility of SailfishOS for much software outside of Jolla's RPM repositories), I see no point in staying on an older point release (because functionality and app compatibility stays the same). Still such links / redirects would be much nicer if some users really want that. _{Alternatively the version override in the SailfishOS:Chum GUI app could be utilised by setting it to the final point release (and in theory the aforementioned non-final point release repos deleted, as it is already the case for SailfishOS:Chum:Testing), but that would break the SailfishOS:Chum community repository for those users in the first place, requiring them to understand what happened and deploy this workaround.}