On Thu, Jun 2, 2016 at 8:57 AM, Hartmut Goebel <h.goe...@crazy-compilers.com> wrote: > Hi, > > I just try (force-) rebuilding some package (python-scikit-learn), I do > not succeed: > > - guix build … simply fetches the package from hydra > - guix build --no-substitutes … rebuilds an lot of other stuff , e.g. > fontforge-dist > - guix build --check … does not provide a meaningful build log > - guix build --check --log-file … does not provide a meaningful build > log either > guix gc -d /gnu/store/*python-scikit-learn* does not change this > > Any help?
You are misundering many things about Guix here. First, why do you think you want to "force rebuild" something? If you've made a change to a build recipe, then that will naturally change the identity of the build, thus getting a new build. If you haven't changed the package recipe, but want to build *just* that package from source for some reason, you could try the following hack: guix environment --search-paths python-scikit-learn guix build --no-substitutes python-scikit-learn The first command will fetch all the dependencies for the package, taking advantage of substitutes. The second command will then build python-scikit-learn without substitutes, but it won't build anything except python-scikit-learn because you just got all the necessary dependencies with the prior command. Finally, if the package build is already present in the store, then you need to use the garbage collector to remove it. - Dave