mbox series

[bug#51888,0/1] import: opam: Warn instead of leave when fetching fails.

Message ID 20211116101043.58471-1-zimon.toutoune@gmail.com
Headers show
Series import: opam: Warn instead of leave when fetching fails. | expand

Message

zimoun Nov. 16, 2021, 10:10 a.m. UTC
Hi,

It is possible to use another OPAM repository when importing, for instance
"guix import opam --repo=https://coq.inria.fr/opam/released" -- although Coq
packages are generally not built using OCaml or Dune build-system, another
story. :-)  Or even, a package using OCaml or Dune build system but not
included in Opam repositories supported by Guix.

However, if this package uses OCaml or Dune build system, then 'refresh'
leaves which is annoying.  For instance, consider:

--8<---------------cut here---------------start------------->8---
$ guix lint -L /tmp/pkgs example
/tmp/pkgs/mine.scm:8:2: example@0 : champ de licence invalide
/tmp/pkgs/mine.scm:23:14: example@0 : le synopsis ne devrait pas commencer par un nom de paquet
/tmp/pkgs/mine.scm:22:15: example@0 : Erreur de certificat TLS : X.509 server certificate for 'exmaple.org' does not match: C=US,ST=California,L=test,O=testexample,OU=testexample,CN=testexp


guix lint: erreur : le paquet « example » est introuvable
--8<---------------cut here---------------end--------------->8---

The trivial patch instead turns this error to a warning which allows to run
all the checkers:

--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix lint -L /tmp/pkgs example
/tmp/pkgs/mine.scm:8:2: example@0: invalid license field
/tmp/pkgs/mine.scm:23:14: example@0: synopsis should not start with the package name
/tmp/pkgs/mine.scm:22:15: example@0: TLS certificate error: X.509 server certificate for 'exmaple.org' does not match: C=US,ST=California,L=test,O=testexample,OU=testexample,CN=testexp


guix lint: warning: opam: package 'example' not found
/tmp/pkgs/mine.scm:12:6: warning: failed to fetch Git repository for example
/tmp/pkgs/mine.scm:12:6: example@0: updater 'opam' failed to find upstream releases
/tmp/pkgs/mine.scm:12:6: example@0: scheduled Software Heritage archival
--8<---------------cut here---------------end--------------->8---

here 'archival'.  Note that the failure is correctly handled by 'lint' when
the early leave skips.

Note that it could be better that 'opam-fetch' raises an error in order to be
catched by caller and thus make all the UI consistent.  However, this requires
a revamp of all inporters...


Cheers,
simon


Example of file /tmp/pkgs/mine.scm:

--8<---------------cut here---------------start------------->8---
(define-module (mine)
  #:use-module (guix packages)
  #:use-module (guix build-system ocaml)
  #:use-module (guix git-download))

(define-public example
  (package
    (name "example")
    (version "0")
    (source
      (origin
        (method git-fetch)
        (uri (git-reference
              (url "https://example.org")
              (commit (string-append "v" version))))
        (file-name (git-file-name name version))
        (sha256
         (base32
          "0m5si9dsv96z92gy4xaqz8mzyz8zp7j1sp542l0wzsp5xgyfpc7i"))))
    (build-system ocaml-build-system)
    (home-page "https://exmaple.org")
    (synopsis "Example")
    (description "This is an exmaple.")
    (license #f)))
--8<---------------cut here---------------end--------------->8---


zimoun (1):
  import: opam: Warn instead of leave when fetching fails.

 guix/import/opam.scm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


base-commit: 122396075f12b013b6bde56dafb895587b95bc9d

Comments

Julien Lepiller Nov. 16, 2021, 1:02 p.m. UTC | #1
Le Tue, 16 Nov 2021 11:10:43 +0100,
zimoun <zimon.toutoune@gmail.com> a écrit :

> Hi,
> 
> It is possible to use another OPAM repository when importing, for
> instance "guix import opam --repo=https://coq.inria.fr/opam/released"
> -- although Coq packages are generally not built using OCaml or Dune
> build-system, another story. :-)  Or even, a package using OCaml or
> Dune build system but not included in Opam repositories supported by
> Guix.
> 

Hi,

I already had a patch for that, which is a bit more complex, at
https://issues.guix.gnu.org/51091. WDYT?
zimoun Nov. 16, 2021, 3:33 p.m. UTC | #2
Hi,

On Tue, 16 Nov 2021 at 14:03, Julien Lepiller <julien@lepiller.eu> wrote:

> I already had a patch for that, which is a bit more complex, at

Sorry, I missed it.

> https://issues.guix.gnu.org/51091. WDYT?

Your patch LGTM.  I am not convinced that all the complexity is worth;
compared to the proposed trivial change. ;-)
From my opinion, the way is a common error for the all importers and
raise it; all the catch happening in 'guix/scripts/'.  That's another
story. :-)

One minor comment, in 'latest-release' I would write "opam: package
'~a' not found~%" otherwise the message "guix lint: warning: package
'example' not found" looks odd (at least to me :-)).

Feel free to close this issue and the other once you pushed a fix.

Cheers,
simon
Julien Lepiller Nov. 19, 2021, 11:59 a.m. UTC | #3
Pushed to master as b5d51bb19e790baee9b16a3325397ec92d8e7625, thanks!
Julien Lepiller Nov. 19, 2021, noon UTC | #4
Forgot to close.