package/luv: update hash
PATCH 1/1 package/luv: update hash
Upstream removed (using git force-push) and recreated version 1.29.1-1 and re-uploaded the source tarball. Therefore, the hash has changed and needs to be updated.
See:
https://github.com/luvit/luv/issues/330
--- package/luv/luv.hash | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
package/luv/luv.hash +1 -1
@@ -1,3 +1,3 @@ # Locally calculated -sha256 430d5d8ad6b22e3e6284b8cdcfc7cea93e7459039bc12375a8a89bfbd034751c luv-1.29.1-1.tar.gz +sha256 572cf3887f4ca03d2761664aa8a098909b445164d8263015693893902558d4cd luv-1.29.1-1.tar.gz sha256 cfc7749b96f63bd31c3c42b5c471bf756814053e847c10f3eb003417bc523d30 LICENSE.txt
Signature · 1 line
2.21.0
PATCH 1/1 package/luv: update hash
Hi J?rg,
Quoted 3 lines · J?rg Krause
Upstream removed (using git force-push) and recreated version 1.29.1-1 and re-uploaded the source tarball. Therefore, the hash has changed and needs to be updated.
What about the file at the default backup site?
http://sources.buildroot.net/luv/luv-1.29.1-1.tar.gz
It's the old file.
baruch
Quoted 17 lines
See:
https://github.com/luvit/luv/issues/330Signed-off-by J?rg Krause <[email protected]>--- package/luv/luv.hash | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)package/luv/luv.hash +1
-1@@ -1,3 +1,3 @@ # Locally calculated -sha256 430d5d8ad6b22e3e6284b8cdcfc7cea93e7459039bc12375a8a89bfbd034751c luv-1.29.1-1.tar.gz +sha256 572cf3887f4ca03d2761664aa8a098909b445164d8263015693893902558d4cd luv-1.29.1-1.tar.gz sha256 cfc7749b96f63bd31c3c42b5c471bf756814053e847c10f3eb003417bc523d30 LICENSE.txt
Signature · 3 lines
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -PATCH 1/1 package/luv: update hash
Hi Baruch,
Quoted 8 lines · Baruch Siach
Hi J?rg,
Quoted 3 lines · J?rg Krause
Upstream removed (using git force-push) and recreated version 1.29.1-1 and re-uploaded the source tarball. Therefore, the hash has changed and needs to be updated.
Quoted 5 lines
What about the file at the default backup site?
http://sources.buildroot.net/luv/luv-1.29.1-1.tar.gz
It's the old file.
I didn't know that the files are backed up. Is it possible to replace this?
J?rg
Quoted 19 lines
Quoted 17 lines
See:
https://github.com/luvit/luv/issues/330Signed-off-by J?rg Krause <[email protected]>--- package/luv/luv.hash | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)package/luv/luv.hash +1
-1@@ -1,3 +1,3 @@ # Locally calculated -sha256 430d5d8ad6b22e3e6284b8cdcfc7cea93e7459039bc12375a8a89bfbd034751c luv-1.29.1-1.tar.gz +sha256 572cf3887f4ca03d2761664aa8a098909b445164d8263015693893902558d4cd luv-1.29.1-1.tar.gz sha256 cfc7749b96f63bd31c3c42b5c471bf756814053e847c10f3eb003417bc523d30 LICENSE.txt
PATCH 1/1 package/luv: update hash
Quoted 12 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"J?rg" == J?rg Krause <[email protected]> writes:
Hi Baruch,
Quoted 8 lines · Baruch Siach
Hi J?rg,
Quoted 3 lines · J?rg Krause
Upstream removed (using git force-push) and recreated version 1.29.1-1 and re-uploaded the source tarball. Therefore, the hash has changed and needs to be updated.
Quoted 8 lines
Quoted 5 lines
What about the file at the default backup site?
http://sources.buildroot.net/luv/luv-1.29.1-1.tar.gz
It's the old file.
I didn't know that the files are backed up. Is it possible to replace this?
Sure, I will do that right away.
Committed, thanks.
Signature · 1 line
Bye, Peter Korsgaard