Summary: | sys-apps/man creates /var/cache/man/cat* directories without write permission for man group | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Karl Fischer <karl> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | acid.punk, brettholcomb, bugs.gentoo.org, lutz.stohlmann, mr_bones_, rockoo, stroller |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Karl Fischer
2004-02-03 15:32:44 UTC
second this (me too!). installed versions here: sys-apps/man-1.5m app-arch/bzip2-1.0.2-r3 sys-apps/baselayout-1.8.6.12-r3 replying mainly to be cc'd; I'd be happy ho help tracing this; *** Bug 40885 has been marked as a duplicate of this bug. *** I can reproduce also: $ man emerge rm: remove write-protected regular empty file `/var/cache/man/cat1/emerge.1.bz2'? n Formatting page, please wait... sh: line 1: /var/cache/man/cat1/emerge.1.bz2: Permission denied Error executing formatting or display command. System command (cd /usr/share/man && (echo ".pl 1100i"; /bin/gunzip -c '/usr/share/man/man1/emerge.1.gz'; echo; echo ".pl \n(nlu+10") | /usr/bin/gtbl | /usr/bin/nroff -Tlatin1 -c -mandoc | /bin/bzip2 > /var/cache/man/cat1/emerge.1.bz2) exited with status 1. rm: remove write-protected regular empty file `/var/cache/man/cat1/emerge.1.bz2'? $ Have just re-emerged sys-apps/man-1.5l-r6 & run the script "/etc/cron.daily/makewhatis.cron" but makes no difference. seems this only happens with new installs of man ... fixed in cvs ... just `rm -rf /var/cache/man ; emerge man` if you're too lazy to fix the perms yourself :p When it's fixed in CVS when will it show up in portage with a emerge sync? By new man install would that be one that happens when I upgrade portage? My system isn't new. Thanks. weird, it didnt happen over here on any of my boxes ... cvs -> rsync happens every 30 minutes Could always 'fix' it in pkg_postinst() ... It's still broken. I attempted a man chmod as a user and got the error. Once I ran man chmod as root it worked. I did the rm man from /var/cache and things worked for awhile but it's back again. I think it either needs to be fixed or let the ebuild handle it. We shouldn't have to fix this every time man gets updated it shouldnt be broken after you fix it once i havent seen it 'come back' on any of my boxes ... I haven't really used man from a user account for a while but it is acting up again tonight. I did the rm ... emerge thing and it works now. Spanky: it does seem to come back. I did an `emerge -U world` (for the first time in a month or 6 weeks) at the weekend & `man ls` failed today. As you'll see, I've posted to this bug before, and "fixed" this issue at that time. seems the permissions get revereted so i'll do as azarah suggested *** Bug 58536 has been marked as a duplicate of this bug. *** *** Bug 58598 has been marked as a duplicate of this bug. *** added to pkg_postinst() ... please try syncing up in a bit and re-emerging man and see if the errors go away *** Bug 59400 has been marked as a duplicate of this bug. *** I tried it as a user on several and so far it seems to work. *** Bug 60710 has been marked as a duplicate of this bug. *** *** Bug 61538 has been marked as a duplicate of this bug. *** It seems to be incorrect in the stageX tarball... i guess. Would be great if it were fixed there, I cannot test that because I do not plan to install some gentoo on a clean machine anytime soon. After fixing ownership and directory modes in /var/cache/man it works and does not break again even after remerging man-1.5xyz you dont really say which manpages but i doubt they'll get re-released it's not a major issue and should be resolved in our next round of releases err, not which manpages, but which stage files |