Release of source code are republished with the same version number

Seafile Client
1

hello,

source code of seafile 7.0.8 has been (re)released twice (https://github.com/haiwen/seafile/releases)

This is really annoying (as a packager for a linux distribution), because an immutable/numbered tarball release of source is essential to packaging it: well known version, immutable source code version.
It also breaks the fingerprint of the source code, that is really frustating since fingerprint is the 1st basic security measure when packaging software.

This already happened in the past (see [1])

Could the project consider to not re-release source code that has been already released ?
In this particular case: release 7.0.8, then 7.0.8.1 for instance.

Thanks and please keep going on this nice software !

[1] Libsearpc: need a numbered release with python3 support

3 Likes
2

Hopefully, this was a one time thing: Windows Defender SmartScreen

3

It also happened in the past.

3 Likes
4

Yup, there is an Arch Linux Package and quite often the checksums are incorrect due to the ‘same’ seafile version being re-released.