[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#27271] [PATCH 0/4] Catch collisions at profile creation time

From: Ricardo Wurmus
Subject: [bug#27271] [PATCH 0/4] Catch collisions at profile creation time
Date: Sat, 17 Jun 2017 11:28:28 +0200
User-agent: mu4e 0.9.18; emacs 25.2.1

Hi Ludo,

L> These patches allow us to catch problematic collisions when computing
L> a profile derivation.  As we know, the profile builder often spits out
L> a number of warnings about collisions but that is not very useful because
L> users cannot distinguish the problematic cases from the harmless cases
L> (an example of a harmless case is when GDB and Binutils provide an
L> almost-identical .info file twice).


R> I’ll give this a try soon and report my experience with it.

I just tried it and I didn’t work the way I thought it would.

Here’s what I did:

  # install old numpy
  guix package -p /tmp/test -i 

  # install a package depending on a later version of numpy
  guix package -p /tmp/test -i bamm

It built bamm and then proceeded to build a profile, while spitting out
hundreds of lines about conflicts between python2-numpy-1.10.4 and

This is the profile’s manifest:

--8<---------------cut here---------------start------------->8---
  (version 3)
          (propagated-inputs ())
          (search-paths ()))))
      (search-paths ()))
      (propagated-inputs ())
      (search-paths ())))))
--8<---------------cut here---------------end--------------->8---

Did I do something wrong?

I also wonder if we should add a way to force Guix to build the profile
despite the detected conflict.


GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC

reply via email to

[Prev in Thread] Current Thread [Next in Thread]