hi,
On May 24, 2:59pm, Juha Saarinen wrote:
> Subject: So far, so good.
> Checked out the CVS earlier today, and built the kernel plus packages. Seems
> to use less memory than 2.4.2, and it looks like the weird disk performance
> slow-down has gone, but I can't say for sure yet...
>
Good to hear.
> Found this little buglet:
>
> # rpm -Uvh xfsdump-1.0.9-0.i386.rpm
> Preparing... ###########################################
> [100%]
> 1:xfsdump ###########################################
> [100%]
> error: cannot remove /usr/man/man8 - directory not empty
>
> Shouldn't the man pages go into /usr/share/man instead?
>
The configure script makes a guess based on the man pages you
have installed already - see configure.in (pkg_man_dir), and
will fall back to using /usr/share/man.
Actually, what I would guess has happened is:
- you installed the xfsdump rpm from the xfs1.0 release
(this uses /usr/man/man8/...);
- you did a "make install" at some intermediate point;
- you installed the current xfsdump rpm, which you just
built yourself, probably via Makepkgs (this likely uses
/usr/share/man/man8/...)
am I right? what are the contents of /usr/man/man8? is
it the man pages _without_ the .gz extension? (this would
have come from a "make install", which doesn't compress).
[rpm -q -l xfsdump will confirm whether the man pages you
now have installed are in /usr/share/man or not]
The error message comes from the rpm upgrade not being
able to remove (what rpm thinks should be) an "empty" subdir
- ie. the old /usr/man/man8, since we now install into
/usr/share/man by default. This sequence has happened to
me a few times - its safe to delete the old /usr/man/man8
contents (from manual "make install"), as long as the new
rpm is using /usr/share/man.
cheers.
--
Nathan
|