Summary: | help2man doesn't compile because perl module Locale::gettext is required | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Steffen Bauch <steffen.bauch> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Perl team <perl> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ale.bol, alt, dertobi123, dev-portage, oc666, releng, vapier |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | help2man bugreport session log |
Description
Steffen Bauch
2006-04-17 05:31:52 UTC
Created attachment 84831 [details]
help2man bugreport session log
the problem occur with USE="nls", try to compile help2man without it. this bugreport can be related to this? http://bugs.gentoo.org/show_bug.cgi?id=120311 emerge -ep system helps, even with nls enabled hey bsd guys, think you could remove your crap ? cause it's breaking a lot of people here help2man crap -> go talk with portage guys (In reply to comment #5) > help2man crap -> go talk with portage guys Whats this have todo with portage? I suspect that by 'talk with portage guys' he means 'bug portage guys until they include package.use.mask support in 2.1'. No, I literally mean that they forced me to put that crap there as I'm not going to have the per-package use.mask that was asked 10 months ago until portage 2.2, even after asking for it recently pointing out the need of Gentoo/FreeBSD for it. (In reply to comment #8) > No, I literally mean that they forced me to put that crap there as I'm not > going to have the per-package use.mask that was asked 10 months ago until > portage 2.2, even after asking for it recently pointing out the need of > Gentoo/FreeBSD for it. I haven't seen a patch for bug 96368 yet. I suppose that if somebone writes an acceptable patch, it can go into a 2.1.1 release or something (given that 2.1 is frozen). With a little luck, it might even be possible for this hypothetical 2.1.1 release to be ready in time for 2006.1. So really, the only thing preventing bug 96368 from getting fixed is lack of manpower (people power, or whatever). I'm quite sure that yesterday genone said it had to be postponed until 2.2, after which I said that I would have used the hacky way on help2man as 2.2 is too away and help2man is in system and I needed it to be fixed one way or the other. (In reply to comment #10) > I'm quite sure that yesterday genone said it had to be postponed until 2.2, Well I'm not sure that genone's statement is final. If we've got a patch then I'd say it's worthy of further discussion. (In reply to comment #9) > I haven't seen a patch for bug 96368 yet. I suppose that if somebone writes an > acceptable patch, it can go into a 2.1.1 release or something (given that 2.1 > is frozen). Antarus had a patch ~2 weeks ago. Try http://dev.gentoo.org/~antarus/projects/portage/patches/portage-per-package-usemask.patch, and if that's not acceptable it can be cleaned up easily enough. *** Bug 133225 has been marked as a duplicate of this bug. *** temp solution until the bsd <-> portage war is over? :) /me wants to get his system up for now... There is a little workaround until this bug fixing. You can #emerge perl then #emerge dev-perl/Locale-gettext worked for me without nls use flag, on amd64 and 2006.0 live cd OK, guys. I really don't give a crap whose fault it is, you have ~ 1 month to fix it before you're blocking 2006.1, so try to get along, please. Hugs and kisses, Release Engineering emerge --sync in a few hours. The die bug has been fixed in the eclass, the dep has been fixed in perl-5.8.8-r2 directly (dropping a dup'd block and removing the dep on coreutils, which was causing the bad loop). Fixed? WFM (In reply to comment #19) > Fixed? > Fixed. K Strange, this hit me with the recent perl upgrade to 5.12.2-r1. probably because you didnt follow the perl upgrade instructions (In reply to comment #24) > probably because you didnt follow the perl upgrade instructions Aww, you're right; I remember now reading it in "eselect news" a few days ago. Anyway, I have it working now, sorry for bringing a four-years-old thread back to life. (In reply to comment #25) It's help a lot. Me too, I hadn't read it. #perl-cleaner --all Fixe it thanks |