BlueZ old releases have different checksums

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Sorry if it was covered previously, but my various searches didn't bring any 
relevant results...

On December 22/23 the entire archive of previous BlueZ/obexd/hcidump releases 
re-appeared on kernel.org after missing for long time due to the server 
compromise. Well, it looks like all the tarballs were re-created and 
re-packaged, thus they all have new checksums. Unfortunately, since filenames 
were not changed (i.e. FSF had to re-publish all releases of binutils and they 
added an 'a' suffix to filenames), this breaks Linux distributions that fetch 
and build from sources (like OpenEmbedded and Yocto based distros), since 
checksums don't match. The situation is even worse since many mirrors have old 
copies of the tarballs...

The question I have is whether this is known and was it done on purpose? What 
can be done to fix this situation for users of the old releases, besides 
upgrading to the very latest releases of BlueZ/obexd/hcidump? Thank you for 
your attention.

-- 
Denys
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux