News for hackers. Stuff that matters.
Re:From xz to ibus: more questionable tarballs by atlasduo on Tuesday April 02, 2024 @04:32AM (#39903504)
Tags can be changed. To actually pin the source code revision, they should pin to a specific commit hash.
Re:From xz to ibus: more questionable tarballs by viraptor on Tuesday April 02, 2024 @04:38AM (#39903535)
Sometimes they get changed for a silly reason (someone just didn't think of the consequences). Sometimes they get changed because they have to - if I remember correctly it was Asterisk that needed to drop some copyrighted music samples and retagged old versions.
Re:From xz to ibus: more questionable tarballs by gunapologist99 on Tuesday April 02, 2024 @08:09AM (#39904825)
That shouldn't matter, then; it should just result in a new release.
Re:From xz to ibus: more questionable tarballs by viraptor on Tuesday April 02, 2024 @08:28AM (#39904944)
You can't distribute the old versions with copyright violation. The problem doesn't go away just because you released a new version.
Re:From xz to ibus: more questionable tarballs by nilamo on Tuesday April 02, 2024 @09:27AM (#39905513)
But then you have two different things (with and without copyrighted data) both with the same version. Wouldn't it be better to just remove the bad release, and publish a new one? They are, after all, not the same things, and shouldn't have the same release.
Re:From xz to ibus: more questionable tarballs by andersa on Tuesday April 02, 2024 @04:41AM (#39903550)
Good point, that would make sense. But same difference. Why is that not how it works?