caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Fabrice Le Fessant <fabrice.le_fessant@origin-labs.com>
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?
Date: Mon, 7 Dec 2020 12:37:00 +0100	[thread overview]
Message-ID: <CAHvkLrMGKwUGtOYOfsevpgaUEvYT1yCnzvngQJQpM04c0VOHXw@mail.gmail.com> (raw)
In-Reply-To: <CAFrFfuGWg=dYspAeLP+_3qZVR459FUhNxrV1zbxxCsFVWc8Rsg@mail.gmail.com>

I have submitted `ez_opam_file` to opam-repository, a compatibility
library for opam-file-format supporting all of its versions. Once it's
accepted, I will submit the corresponding versions of `drom` and
`opam-bin`, so they should be installable in any switch.
--
Fabrice

On Mon, Dec 7, 2020 at 4:28 AM Martin DeMello <martindemello@gmail.com> wrote:
>
> I tried on both 4.09 and 4.11 and couldn't get it to work. Also I couldn't find a `--dev-deps` flag, did you mean `--deps-only'? That didn't work either. I'll wait for the fix David Allsopp mentioned and try again.
>
> martin
>
> On Sun, Dec 6, 2020 at 1:41 AM Fabrice Le Fessant <fabrice.le_fessant@origin-labs.com> wrote:
>>
>> 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

      reply	other threads:[~2020-12-07 11:37 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
2020-12-07  3:27   ` Martin DeMello
2020-12-07 11:37     ` Fabrice Le Fessant [this message]

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=CAHvkLrMGKwUGtOYOfsevpgaUEvYT1yCnzvngQJQpM04c0VOHXw@mail.gmail.com \
    --to=fabrice.le_fessant@origin-labs.com \
    --cc=caml-list@inria.fr \
    --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).