karthick-rn commented on pull request #381: URL: https://github.com/apache/fluo-muchos/pull/381#issuecomment-748536670
> That is weird that they changed the RPM but didn't bump the version number. Very strange. However, it does look like the RPM itself has a valid GPG signature, though I do not know what InfluxDB's official GPG key is to verify the trust chain. This new SHA512 is correct, though, for what's currently there as the 1.8.3 RPM. Yeah, it does seem strange. I've sent the below email to [email protected]. For now, I'll go-ahead and merge this change. Thanks ``` Hello, I've been using the stable Influxdb v1.8.3 from the repository. Recently, when downloading "influxdb-1.8.3.x86_64.rpm" using the Ansible yum module, it failed due to a mismatch in the checksum. I then noticed the RPM has been modified on 12 Nov 2020. This seems strange, I'd thought existing stable versions once created won't be modified and any changes will result in a new version of influxdb thereby producing a new checksum. Fortunately, I had a copy of the original RPM file which I did a cksum (1). Comparing this to the updated RPM (2), I see the file size remains the same(64097226). Do you know if anything actually changed in the updated RPM that has produced a different checksum? 1) $ cksum influxdb-1.8.3.x86_64.rpm 281633092 64097226 influxdb-1.8.3.x86_64.rpm 2) $ cksum new/influxdb-1.8.3.x86_64.rpm 2130743016 64097226 new/influxdb-1.8.3.x86_64.rpm Thanks, Karthick ``` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
