[gnome-disk-utility/kailueke/fix-libaio-checksum] Fix sha256 checksum of libaio
- From: Kai Lüke <kailueke src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-disk-utility/kailueke/fix-libaio-checksum] Fix sha256 checksum of libaio
- Date: Sat, 23 Nov 2019 17:11:06 +0000 (UTC)
commit 3c2fde573a4e8eecd6bc30e5a937b7407f85f944
Author: Kai Lüke <kailueke riseup net>
Date: Sat Nov 23 18:06:21 2019 +0100
Fix sha256 checksum of libaio
Somehow the checksum changed for the file
libaio-libaio-0.3.111.tar.gz to a new one,
and anyway neither the new one nor the previous
one are the one listed on the website in
https://releases.pagure.org/libaio/CHECKSUMS
Since we just use these checksums for the CI
and local development, there is no big security
impact but I wonder goes wrong.
flatpak/org.gnome.DiskUtility.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
diff --git a/flatpak/org.gnome.DiskUtility.json b/flatpak/org.gnome.DiskUtility.json
index a04a8776..b8879b18 100644
--- a/flatpak/org.gnome.DiskUtility.json
+++ b/flatpak/org.gnome.DiskUtility.json
@@ -100,7 +100,7 @@
{
"type" : "archive",
"url" : "https://pagure.io/libaio/archive/libaio-0.3.111/libaio-libaio-0.3.111.tar.gz",
- "sha256": "1e7c9f70fb1dacd685affa1989fed44519f6b60b5d7b73d70960f5d9e88a3a99"
+ "sha256": "e6bc17cba66e59085e670fea238ad095766b412561f90b354eb4012d851730ba"
}
]
},
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]