Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 686838 - dev-perl/Gtk2-1.249.920 - MakeMaker FATAL: prerequisites not found. Pango not installed
Summary: dev-perl/Gtk2-1.249.920 - MakeMaker FATAL: prerequisites not found. Pango...
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: build-order
  Show dependency tree
 
Reported: 2019-05-27 07:08 UTC by Alexey
Modified: 2019-07-11 05:35 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
emerge --info (file_686838.txt,19.28 KB, text/plain)
2019-05-27 07:08 UTC, Alexey 		Details
build.log (build.log,2.76 KB, text/plain)
2019-05-27 07:09 UTC, Alexey 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey 2019-05-27 07:08:05 UTC 
Created attachment 577864 [details]
emerge --info

I'm in middle of @world update, and dev-lang/perl was updated already, but dev-perl/Pango was not updated yet.

[ebuild   R    ] dev-perl/Gtk2-1.249.920::gentoo  USE="-test" 0 KiB
[ebuild   R    ] dev-perl/Pango-1.227.0::gentoo  USE="test -examples -minimal" 0 KiB

dev-perl/Gtk2 fails to build with:
MakeMaker FATAL: prerequisites not found.                                                                                                                                                                                                                                         
    Pango not installed

If I not mistake, the fix would have something to do with subslots?
Comment 1 Alexey 2019-05-27 07:09:21 UTC 
Created attachment 577866 [details]
build.log
Comment 2 Kent Fredric (IRC: kent\n) gentoo-dev 2019-07-11 05:26:16 UTC 
This is portage's problem, not much perl can do about it.

When X requires Y, portage's responsibility is to ensure Y is working before attempting installing X.

Portage is failing to do this and simply ordering the build order wrong.

So basically, what actually happens is portage tries to install X where Y is so broken its "practically not even installed".

"only" been a problem since 2007 ....