caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Fabrice Le Fessant <fabrice.le_fessant@origin-labs.com>
To: David Allsopp <david@allsopps.net>
Cc: Martin DeMello <martindemello@gmail.com>,
	caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] How do I get opam to show me why two packages conflict?
Date: Sun, 6 Dec 2020 13:59:01 +0100	[thread overview]
Message-ID: <CAHvkLrMFDLvj3zJsomaUnpp0JU81F8kvgo1-Z-YUJ=XVd8Chfw@mail.gmail.com> (raw)
In-Reply-To: <6f4e51b5b5f34dcb83d4929737c96843@metastack.com>

Then, I don't understand the fix in the opam-repository:
opam-file-format does conflict with core_kernel when they are included
in the same executable, but not when they are just in the same switch.
Conflicts in the opam-repository are for installation conflicts, not
for linking conflicts, no ?

On Sun, Dec 6, 2020 at 1:19 PM David Allsopp <david@allsopps.net> wrote:
>
> opam-file-format 2.1.1 conflicts core-kernel because of https://github.com/ocaml/opam-file-format/pull/34. 2.1.2 (which should be being released soon along with opam 2.1 beta4) will include that fix.
>
> It's not perhaps the greatest UI for it, but the reasons for such changes can occasionally be clear from the git blame on opam-repository: https://github.com/ocaml/opam-repository/blame/master/packages/opam-file-format/opam-file-format.2.1.1/opam#L13
>
> The change in opam-repository was only merged yesterday.
>
> All best,
>
>
> David
>
> > -----Original Message-----
> > From: caml-list-request@inria.fr <caml-list-request@inria.fr> On Behalf Of
> > Fabrice Le Fessant
> > Sent: 06 December 2020 09:41
> > To: Martin DeMello <martindemello@gmail.com>
> > Cc: caml users <caml-list@inria.fr>
> > Subject: Re: [Caml-list] How do I get opam to show me why two packages
> > conflict?
> >
> > Hi Martin,
> >
> >   I have a 4.09.1 switch with both core_kernel.v0.14.1 and drom.0.2.0
> > installed with no conflict. Did you try to install with dev-deps ?
> >
> > Best regards
> > --
> > Fabrice
> >
> > On Sun, Dec 6, 2020 at 4:06 AM Martin DeMello <martindemello@gmail.com>
> > wrote:
> > >
> > > I tried to install drom via opam and got told that it conflicted with
> > core_kernel:
> > >
> > >   ⊘ remove  core_kernel      v0.14.1        [conflicts with opam-file-
> > format]
> > >   ↗ upgrade opam-file-format 2.1.0 to 2.1.1 [required by drom_lib]
> > >
> > > but `opam show core_kernel` lists no dependency on opam-file-format`,
> > > and `opam show opam-file-format.2.1.1` just says
> > >
> > >   depends:      "ocaml" "dune" {>= "2.0"} "alcotest" {with-test}
> > >   conflicts:    "core_kernel"
> > >
> > > with no indication as to why the conflict.
> > >
> > > martin

  parent reply	other threads:[~2020-12-06 12:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06  3:06 Martin DeMello
2020-12-06  9:41 ` Fabrice Le Fessant
     [not found]   ` <6f4e51b5b5f34dcb83d4929737c96843@metastack.com>
2020-12-06 12:59     ` Fabrice Le Fessant [this message]
2020-12-07  3:27   ` Martin DeMello
2020-12-07 11:37     ` Fabrice Le Fessant

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHvkLrMFDLvj3zJsomaUnpp0JU81F8kvgo1-Z-YUJ=XVd8Chfw@mail.gmail.com' \
    --to=fabrice.le_fessant@origin-labs.com \
    --cc=caml-list@inria.fr \
    --cc=david@allsopps.net \
    --cc=martindemello@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).