| Summary: | sys-apps/man-db USE=nls - tinderbox setup issues with app-text/po4a pulling in dev-lang/perl:0/5.24 blocking dev-lang/perl:0/5.26 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge output of emerge --update --newuse --changed-use --changed-deps=y --deep @system --pretend | ||
Updating just @system isn't supported, anyway, right? https://wiki.gentoo.org/wiki/Project:Portage/FAQ#Why_is_there_a_dependency_conflict_when_I_attempt_to_upgrade_a_single_package.3F Also, not heard about this since, so hopefully fixed/worked around now? |
Created attachment 519678 [details] emerge output of emerge --update --newuse --changed-use --changed-deps=y --deep @system --pretend I do often run into the blocker situation as attached, which can be circumvented by : echo "sys-apps/man-db -nls" >> img1/.../etc/portage/package.use/setup and I do wonder, if this is caused by the arbitrarily chosen USE flag setup or if there's room for improvement either in the ebuild definitions (of po4a ?) or in the resolver of portage.