Hello, Hartmut Goebel <h.goe...@crazy-compilers.com> skribis:
> On Fri, 09 Mar 2018 23:59:26 +0100 l...@gnu.org (Ludovic Courtès) wrote: >> >>> Good catch! I implemented what you suggest above in commit >>> 464f5447396fcec9b43f7eab71d5d42b522a157f. > > Thanks, this solved the issue only partially: On my "kde-plasma" branch: > > $ ./pre-inst-env guix graph plasma-workspace | grep autoconf > "133094208" [label = "autoconf-wrapper-2.69", shape = box, fontname = > Helvetica]; > "133094976" [label = "autoconf-2.69", shape = box, fontname = Helvetica]; > "152772352" [label = "autoconf-wrapper-2.69", shape = box, fontname = > Helvetica]; > "152420544" [label = "autoconf-2.69", shape = box, fontname = Helvetica]; > > There are other packages, which are duplicate but don't have a factory > AFAIK: > > $ ./pre-inst-env guix graph plasma-workspace | grep kbus > "130257472" [label = "kdbusaddons-5.42.0", shape = box, fontname = > Helvetica]; > "148171200" [label = "kdbusaddons-5.42.0", shape = box, fontname = > Helvetica]; That stems from the use of ‘package-mapping’ or ‘package-input-rewriting’ (maybe via ‘package-with-python2’), which can create distinct package objects mapping to the same derivation. I don’t have a good solution here. Thanks, Ludo’.
