[Ma-linux] TAGS: libc6 ldconfig PATH visudo

[Kevin Cole]

Although I don't know the cause or cure, I can provide further clues...

On Thu, Mar 15, 2012 at 12:40, Jobuntu LLC | Tech Support for Humans <
joseph at jobuntu.net> wrote:

> I've got a problem with apt-get.  I cannot do install (with or without
> -f), upgrade, dist-upgrade.  I also run into the same problem with dpkg.
> When I do apt-get -f install, I get
>
> Can't exec "locale": No such file or directory at
> /usr/share/perl5/Debconf/Encoding.pm line 16.
>

locale is part of the libc-bin package.


> Use of uninitialized value $Debconf::Encoding::charmap in scalar chomp at
> /usr/share/perl5/Debconf/Encoding.pm line 17.
> Preconfiguring packages ...
> dpkg: warning: 'ldconfig' not found in PATH or not executable.
> dpkg: error: 1 expected program not found in PATH or not executable.
> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and
> /sbin.
> E: Sub-process /usr/bin/dpkg returned an error code (2)
>

ldconfig is part of the libc-bin package as well.


> I've tried editing the PATH in sudoers with visudo.  I've tried
> reinstalling (first w/o formating the partition, then formatting the
> partition (altho not the /home partition).  It seems I'm missing a folder
>

Eh?  Reinstalling the whole shebang?  From an official CD (or ISO image)?
You said you have a separate home partition.  Any other partitions? Or is
it basically / and /home?

Any help here?
>

$ ls /var/lib/dpkg/info/libc-bin.*

should show you the following files, if you've got the libc-bin package
installed:

/var/lib/dpkg/info/libc-bin.conffiles
/var/lib/dpkg/info/libc-bin.md5sums
/var/lib/dpkg/info/libc-bin.triggers
/var/lib/dpkg/info/libc-bin.list
/var/lib/dpkg/info/libc-bin.postinst

These are all text files and, with practice, almost readable. ;-) I often
find that broken packages can be fixed by understanding them.  For example,
".postinst" files are scripts that are run... post installation.  In other
words, after all the files have been extracted from a package and placed in
their respective directories. And for some packages there's any combination
of .preinst, .prerm and .postrm scripts to go along with .postinst.
(Nothing says there'll always be a .postinst either.) I leave it as an
exercise for the reader to figure out when the other three are run. ;-)

.list is just what it sounds like: A list of the files in a package.
.conffiles are a list of configuration files. .md5sums are the official MD5
checksum values for the files listed. (You can generate an md5sum for a
file and compare it to the expected value to see if they match.  If they
don't then the file has been changed since installation. Not always a bad
thing, as configuration files and such are often changed by the admin, or
other legitimate proxies.)  Dunno what .trigger files do.  I never found
them helpful in diagnosing my package troubles in the past.

Not much to go on, but I hope it's a start for you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://calypso.tux.org/pipermail/ma-linux/attachments/20120315/c38c8f7b/attachment.html