Alan McKinnon <alan.mckin...@gmail.com> [15-01-16 08:52]: > On 16/01/2015 06:15, meino.cra...@gmx.de wrote: > > Hi, > > > > again the emerge oracle has spoken to one to its lowest servants and so > > said: > > > > > > > > Diffing databases (17943 -> 17944 packages) > > [N] >> net-print/epson-inkjet-printer-escpr (~*1.4.4): Epson Inkjet > > Printer Driver (ESC/P-R) > > * Time statistics: > > 219 seconds for syncing > > 95 seconds for eix-update > > 13 seconds for eix-diff > > 330 seconds total > > Calculating dependencies... done! > > > > WARNING: One or more updates/rebuilds have been skipped due to a dependency > > conflict: > > > > dev-python/numpy:0 > > > > (dev-python/numpy-1.9.0-r1:0/0::gentoo, ebuild scheduled for merge) > > conflicts with > > > > <dev-python/numpy-1.9.0[python_targets_python2_7(-),python_targets_python3_3(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-)] > > required by (dev-python/matplotlib-1.3.0-r1:0/0::gentoo, installed) > > ^ ^^^^^ > > > > > > May the light of the greater ebuild shed some wisdom onto my > > poor soul so enlightment will struck the darkness of my knowledge... > > > > But does that mean? > > > In simple terms, you have a conflict between something new and something > old, and portage can't do it. > > In this case, portage wants to update numpy from to 1.9.0-r1, but can't. > The reason is the matplotlib ebuild requires a version of numpy <1.9.0 > (ignore for now the python_targets stuff, that's USE-like requirements > which are not relevant). > > Bottom line: with that version of matplotlib, you are pegged to the > current version of numpy, and portage is being overly complicated about > telling you this. > > If you can't update matplotlib, you can just leave things as they are - > it doesn't hurt. Train your eye to ignore that output about numpy. > > > -- > Alan McKinnon > alan.mckin...@gmail.com > >
Hi Alan, thanks for the translation! :) We should suggest Google to implement a new translation Portage->English ;))) Best regards, Meino
