aboutsummaryrefslogtreecommitdiff
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>2020-05-23 22:57:12 +0100
commit6d6fdf639baf91c0fdc9a1cc8a7ba03046a51fda (patch)
treec1d61be198458ab24de57914f115733d4a1dce5f
parent7c39082fd0b00e8ee79f1c846f2009fc62d1ff29 (diff)
downloadgnu-guix-6d6fdf639baf91c0fdc9a1cc8a7ba03046a51fda.tar
gnu-guix-6d6fdf639baf91c0fdc9a1cc8a7ba03046a51fda.tar.gz
Have the GitHub updater just use Git tags
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 8ba5b5192d..6639ff6119 100644
--- a/guix/import/github.scm
+++ b/guix/import/github.scm
@@ -159,12 +159,7 @@ empty list."
`((Authorization . ,(string-append "token " (%github-token))))
'())))
- (match (json-fetch 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 tag-url #:headers headers))
- (x x)))
+ (json-fetch 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