Arnaud Gomes-do-Vale (arnaud...@ircam.fr)

"Lanny Marcus" <lannyma@gmail.com> writes:

> error: unpacking of archive failed on file
> /opt/picasa/lib/libfreetype.so;4730c479: cpio: symlink failed -
> Operation not permitted

After ruling out the obvious (is /opt full?), check your logs (most
probably dmesg and/or /var/log/messages).

Now a wild guess: what file system are you using for /opt? Does it
support symlinks?

Niki Kovacs <contact@kikinovak.net> writes:

> Q: how can I switch off the power on a machine with just a basic install?

Use "poweroff" or "halt -p".

"CentOS List" <centoslist@gmail.com> writes:

> Well, it does the trick for openssl-devel.. But there are other
> packages which still require openssl i386. What should i do?

It really depends if you need 32 bit compatibility. I tend to do "yum
remove glibc.i686" to get rid of it entirely.

"CentOS List" <centoslist@gmail.com> writes:

> Why does a x86 structure requires i386 package?

It doesn't -- just "yum install openssl-devel.x86_64".

"Akemi Yagi" <amyagi@gmail.com> writes:

> I mirror the updates directory and, if I'm not mistaken, it works as
> such. No need to run repodata locally. Maybe your yum is not
> pointing to the correct directory??

It is. Actually yum itself works in the usual case, the only failures
I can see are when building mock chroots. As far as I understand, when
invoked from mock, yum can pick packages from updates, but it cannot
track dependencies within the updates repo.