Summary: | emerge gives "fmt: invalid width: `10000'" messages after sync | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | ta2002 <throw_away_2002> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED NEEDINFO | ||
Severity: | minor | ||
Priority: | Low | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
ta2002
2006-06-02 04:06:48 UTC
grep -Rni fmt /usr/local/portage; post the output. k3b in your overlay, by chance? :P > k3b in your overlay, by chance? :P
Sounds like you know about this. :)
$ grep -Rni fmt /usr/local/portage
/usr/local/portage/app-cdr/k3b/k3b-0.11.17.ebuild:45:MAKE_PO=$(echo "${LINGUAS} ${LANGS}" | fmt -w 1 | sort | uniq -d | fmt -w 10000)
/usr/local/portage/app-cdr/k3b/k3b-0.11.17.ebuild:46:MAKE_DOC=$(echo "${LINGUAS} ${LANGS_DOC}" | fmt -w 1 | sort | uniq -d | fmt -w 10000)
/usr/local/portage/app-cdr/k3b/k3b-0.11.18.ebuild:39:MAKE_PO=$(echo "${LINGUAS} ${LANGS}" | fmt -w 1 | sort | uniq -d | fmt -w 10000)
/usr/local/portage/app-cdr/k3b/k3b-0.11.18.ebuild:40:MAKE_DOC=$(echo "${LINGUAS} ${LANGS_DOC}" | fmt -w 1 | sort | uniq -d | fmt -w 10000)
/usr/local/portage/app-cdr/k3b/k3b-0.11.24.ebuild:48: MAKE_PO=$(echo $(echo "${LINGUAS} ${LANGS}" | fmt -w 1 | sort | uniq -d))
/usr/local/portage/app-cdr/k3b/k3b-0.11.24.ebuild:49: MAKE_DOC=$(echo $(echo "${LINGUAS} ${LANGS_DOC}" | fmt -w 1 | sort | uniq -d))
/usr/local/portage/app-cdr/k3b/k3b-0.12.4a.ebuild:59: MAKE_LANGS=$(echo $(echo "${LINGUAS} ${LANGS}" | fmt -w 1 | sort | uniq -d))
Obviously, I can remove the old ebuilds from the overlay.
If you have a few seconds (and I know you don't), can you explain what causes the messages, why they only showed up after the portage upgrade, and why they only happen on the first emerge after a sync (call me curious, but that represents a big reason why I use Gentoo :) )?
Thank you very much.
(In reply to comment #2) > If you have a few seconds (and I know you don't), can you explain what causes > the messages, why they only showed up after the portage upgrade, and why they > only happen on the first emerge after a sync (call me curious, but that > represents a big reason why I use Gentoo :) )? See Bug 104680. Such stuff like 'fmt -w' does not belong to global scope, should never only be used enclosed in some of the ebuild functions. Otherwise, it gets sourced and portage chokes on it on every cache regen (which happens after every emerge --sync). |