NLSPATH
"Collins, Eric S." <[email protected]> Tue, 19 Nov 2002 17:41:16 -0600
| Newsgroups | gmane.linux.redhat.release.guinness |
|---|---|
| Message-ID | <CFC80EECB4A4D6118DF800D0B7C9B52B038E40@ntcr1107.apacteleservices.com> |
Hi all,
Ok, I was in need of a rpm package checker, so one of my colleagues
in the UNIX group recommended red carpet. Well, dependencies nailed me. I
needed some lib updates. I decided to update all the glib packages, cpp, gcc
and lib packages. I have 2.2.16-22smp kernel on my linux box. I was able to
upgrade many of the packages, but at a certain point I had a dependency
issue. glibc-devel-2.2.4-18.7.0.8.i386.rpm wanted
glibc-2.2.4-18.7.0.8.i686.rpm and vise versa. I ended up doing a rpm -Uvh
--nodeps on the glibc-2.2.4-18.7.0.8.i686.rpm and then the
glibc-devel-2.2.4-18.7.0.8.i386.rpm upgraded without complaining.
My issues are as follows -
1. I ran red-carpet in KDE and entered my configuration for it to
connect. It has been unable to connect and I cannot change the settings as
of yet. I have uninstalled that package and re-installed it, without luck. I
even looked for red*,etc for config files. Does anyone know how I can change
the connect settings? I searched the knowledge base on www.ximian.org
<http://www.ximian.org> , however I couldn't find any related topics.. even
after searching with different combinations.
2. Whenever I should man a manpage that doesn't exist, I receive this
error -
[escollin@minion oldrpm]$ man d
man: No such file or directory
Failed to open the message catalog man on the path NLSPATH=<none>
No manual entry for d
[escollin@minion oldrpm]$
I believe the NLSPATH correlates to language selection, but I have
no idea how to correct this issue. This issue is probably due to my updates,
since it worked correctly prior to them. I can still man existing man pages,
this is driving me nuts. Any suggestions would be helpful. I searched
redhat.com / ximian.org and the web (google) for a possible fix. I have not
found anything that has pointed me in the right direction, yet.
The only message I recieved when doing these updates is
warning: /etc/localtime has been saved as /etc/localtime.rpmnew . I
backed up localtime to locatime.orig and mv localtime.rpmnew to localtime,
which did absolutely nothing I have noticed. I appreciate your time
Thanks,
Eric