summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristopher Baines <christopher.baines@digital.cabinet-office.gov.uk>2019-05-30 18:23:02 +0100
committerChristopher Baines <christopher.baines@digital.cabinet-office.gov.uk>2019-10-22 23:16:43 +0100
commit7621d25e3ffafcd83d36b3f2ff0eeeeb4038a154 (patch)
treeeffaf7789d5642aadbb6b4cf8fd60654728c35be
parent79e334c2b716d5fa6f1b8916f546bef28273d32e (diff)
downloadgnu-guix-7621d25e3ffafcd83d36b3f2ff0eeeeb4038a154.tar
gnu-guix-7621d25e3ffafcd83d36b3f2ff0eeeeb4038a154.tar.gz
Have the GitHub updater just use Git tagsrelease_37
Some of the GitHub repositories used by GOV.UK have a few old releases, that mean the updater just picks the latest one of these, ignoring the more recent Git tags.
-rw-r--r--guix/import/github.scm7
1 files changed, 1 insertions, 6 deletions
diff --git a/guix/import/github.scm b/guix/import/github.scm
index ee1c1b9236..4958f9ac90 100644
--- a/guix/import/github.scm
+++ b/guix/import/github.scm
@@ -161,12 +161,7 @@ empty list."
(string-append url "?access_token=" (%github-token))
url))
- (match (json-fetch (decorate release-url) #:headers headers)
- (#()
- ;; We got the empty list, presumably because the user didn't use GitHub's
- ;; "release" mechanism, but hopefully they did use Git tags.
- (json-fetch (decorate tag-url) #:headers headers))
- (x x)))
+ (json-fetch (decorate tag-url) #:headers headers))
(define (latest-released-version url package-name)
"Return a string of the newest released version name given a string URL like