You are not logged in.
Yes, I do love a good 'just updated and have an issue' scenario.
getting expert through forced motivation can be essential for some, perhaps.
I'm now even better at understanding symlinks.
Yes, it's jst a temporary fix after todays fantastic new update, of lots!
thanks devs!
Here's what I did. basic, though I enjoyed it. Will delete the 2 symlinks when proper fix/update is out.
ln -s /usr/lib/libssl.so.1.0.0 /usr/lib/libssl.so.0.9.8
then
ln -s /usr/lib/libcrypto.so.1.0.0 /usr/lib/libcrypto.so.0.9.8
mutt boots!
amazing how happy I am about that. fits in with a few other learning curvers I'm having.
great! ... and thank again for ARCH brilliance everywhere here.
Last edited by yvonney (2010-04-09 05:49:48)
Offline
Symlinking libraries is very, very bad. You may break things without realising it until too late.
Switch to a more up-to-date mirror and do the update.
Offline
- - - - - - -
OH! great to know there is one.
I was sure there would be though took the opportunity to learn something that I was only average at.
a bit absurd as symlinks are "linux 201", though I have gaps in my ability and symlinks is one of them.
so... um, mutt 1.5.20 is looking for the old libssl ... hmmm... looks like I'll be learning more on this.
Would not mutt need to be updated OR there's something else to know specifically. Interesting.
thanks.
- - - - - - -
UPDATE: oh, lots more updates now. So, would a break of something not be reversable simply be deleting the symlinks?
just thinking out loud on that, no reply asked for particularly.
Or perhaps something could break badly that deleting the symlinks would not fix?
deleting now due to big additional updates including core stuff.
ADDITIONAL COMMENT: turns out is a 'bash' update only.
keeping symlinks for a bit I guess.
I DID read on the dev list, ust now, what was said in a joking sort of way, that:
"well that's done, the mirrors will be updated someday"
so likely that the last big update today was, um BIG, so I should think more updated are on the way!
thank you again for advisement.
Last edited by yvonney (2010-04-09 06:55:20)
Offline
Symlinking libraries is very, very bad. You may break things without realising it until too late.
Switch to a more up-to-date mirror and do the update.
i know that simlinking is bad...but there is no other choice if you want a working pacman right now .i guess there is no more up-to-date pacman since i've used "sudo pacman -U ftp://ftp.archlinux.org/core/os/i686/pacman-3.3.3-5-i686.pkg.tar.gz" for update and it's still want 0.9.8 libcrypto
[m@mlaptop lib]$ pacman
pacman-color: error while loading shared libraries: libcrypto.so.0.9.8: cannot open shared object file: No such file or directory
[m@mlaptop lib]$ sudo ln -s libcrypto.so.1.0.0 libcrypto.so.0.9.8
[m@mlaptop lib]$ pacman
chyba: nebyla specifikována operace (použijte -h pro nápovědu)Last edited by marvn (2010-04-09 07:28:27)
core i5 4590, x86_64, nvidia 970
Offline
Wrong! remove your alias from pacman to pacman-color...
Offline
ooops. ok, i suck. sorry ![]()
core i5 4590, x86_64, nvidia 970
Offline
hehehe, me too!
nice to have your firm kind guidance Allan!:)
Offline
An alternative solution
http://aur.archlinux.org/packages.php?ID=36308
Could this be recommended by the developers?
Offline
No, because it is not needed... Completely update your system with an up-to-date mirror and rebuild any unsupported packages that need it.
Offline
An alternative solution
http://aur.archlinux.org/packages.php?ID=36308
Could this be recommended by the developers?
Don't use this; it's broken. The engine libs of openssl are not compatible!
Offline
Offline
to follow up on what Ghost said, i posted an updated PKGBUILD on the mutt-sidebar aur page. it's just the repo mutt's PKGBUILD with only the sidebar patch applied. it makes cleanly and i'm using now without issues.
/edit: i just realized how similar our sigs are... not on purpose *i swear*
Last edited by brisbin33 (2010-04-09 19:18:00)
//github/
Offline