diff options
| author | Christopher Baines <christopher.baines@digital.cabinet-office.gov.uk> | 2019-05-30 18:23:02 +0100 |
|---|---|---|
| committer | Christopher Baines <christopher.baines@digital.cabinet-office.gov.uk> | 2019-05-30 18:23:02 +0100 |
| commit | e363be37fff13c8c495039e76b2b1560e57099bc (patch) | |
| tree | 3fcb7d7f9ff3bf8c715e8e1d26ff9446817eb43f | |
| parent | c6e6631e3dc9283b9386f7a0b0ef1b0e97e8fc31 (diff) | |
| download | gnu-guix-release_36.tar gnu-guix-release_36.tar.gz | |
Have the GitHub updater just use Git tagsrelease_36
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.scm | 7 |
1 files changed, 1 insertions, 6 deletions
diff --git a/guix/import/github.scm b/guix/import/github.scm index c8d3b744a9..1a59ec4f49 100644 --- a/guix/import/github.scm +++ b/guix/import/github.scm @@ -160,12 +160,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 |