IRC channel logs

2023-03-03.log

back to list of logs

<oriansj>one must remember that unless you have your own source tarball repo, there is nothing stopping upstream from changing the contents of the files at any time
<rkeene>That's where hashcache comes in
<rkeene> https://chiselapp.com/user/rkeene/repository/hashcache
<rkeene> https://hashcache.rkeene.org/
<oriansj>rkeene: well it is a start but definitely not the end solution as it would only cache files that you previously requested.
<rkeene>If you never requested them... do you need them ?
<oriansj>rkeene: i was thinking more that you might request them after they have changed and you need to get the old version
<rkeene>If you know the hash, and you've fetched them before you can always fetch them
<rkeene>I use a script like this: https://kitcreator.rkeene.org/fossil/artifact/d546c4b48dfce807 as part of my build system
<rkeene>The one thing it won't tell you is if the file changed because it fetches by hash first
<vagrantc> https://hashcache.rkeene.org/
<vagrantc>shows an error, but it is not obvious what was wrong with the example
<vagrantc>but i like the idea in theory :)
<rkeene>The error is you didn't give it a hashMethod or hash value
<rkeene> http://hashcache.rkeene.org/sha1/dfc00e1a9ad78225527028db113d72c0ec8c12f8 for example will give you a file with the SHA1 of dfc00e1a9ad78225527028db113d72c0ec8c12f8
<vagrantc>right ... but i was presuming that page was showing an example ... but the error says implies it was not passed the sha1 ...
<vagrantc>i mean, i can screenshot what it says on the page
<vagrantc>just pointing out that what it says on the page does not make sense ...
<vagrantc>it is not clear if the error is from the example ... or an example error from some other url ... or ... ?
<rkeene>What URL has an error that you don't understand ?
<vagrantc>the contents of the page https://hashcache.rkeen.org ... has both an example and an error
<vagrantc>but i cannot figure out why that example would produce that error
<vagrantc>is the error unrelated to the example?
<vagrantc>e.g. simply going to that page produces an error, and it helpfully is showing me Useage and Example ... followed by the error?
<vagrantc>maybe if the error were listed first, followed by the Usage and Example it would be ... less confusing
<vagrantc>it was unclear weather the example was describing a url that produced that error ... but with some experimentation it is clear that the error is just the error for having gone to an essentially invalid URL, and has nothing to do with the presented example
<vagrantc>changing the order they are displayed in would make more sense, at least to me ... anyways ... that is a lot of words for a small, confusing bug report