You are not logged in.
Well, I did a pacman -Suy. But does this mean that I broke the entire pacman. Or just packages from the testing repo? (that are dependent on openssl).
Offline
There's a thread on this already, but I thought it was fixed. sveinemann, I mean this is the best possible regards but if you read the documentation (like the pacman wiki page) it says that those that use testing are highly recommended to follow the mailing list. Personally, I only believe that developers should use testing and then that only if they are highly experienced. Testing means 'Testing' it can and sometimes will break things.
Setting Up a Scripting Environment | Proud donor to wikipedia - link
Offline
First question: why are you using [testing]?
Second question: what packages were updated?
Third question: have you tried downgrading (manually if required)?
Personally, I only believe that developers should use testing and then that only if they are highly experienced. Testing means 'Testing' it can and sometimes will break things.
Who'd do the actual 'testing' then ?
Last edited by ngoonee (2010-04-08 07:52:19)
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
First question should be what was broken... Nothing in [testing] should break anything now.
Offline
I'm using testing because I need kernel*33 for TRIM support for my SSD. Texmaker is one of the programs that is broken.
texmaker: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory
Offline
I'm using testing because I need kernel*33 for TRIM support for my SSD. Texmaker is one of the programs that is broken.
texmaker: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory
if you enable testing, you _need_ to enable community-testing as well.
Give what you have. To someone, it may be better than you dare to think.
Offline
I have done so, and they are in the correct order too. That's why I'm a little lost. The system is fully updated to.
I'm trying to recompile with abs, both texmaker and openssl. Will see if that makes a change.
Seems like when I'm trying to rebuild texmaker from abs community testing it stops because it wants an older version of openssl. Grrr. Downgrade of texmaker or openssl seems to be a solution.
Last edited by sveinemann (2010-04-08 08:15:05)
Offline
Would probably been easier to just roll your own 2.6.33
Offline
FYI texmaker 1.9.9-3 from community-testing runs fine for me against openssl 1.0.0-2 from testing.
Offline
Would probably been easier to just roll your own 2.6.33
This. The kernel (and xorg, to some extent) is quite dependency-free, except for whatever modules you need. Rolling your own would be a better option than using [testing] when you're not prepared to deal with what will happen.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
What will roll my own say? Just downloading pkgbuild for it instead of activating testing?
Offline
There is nothing broken with testing atm as we are about to move those packages to core/extra soon. Make sure yur repos are in correct order, you're not using any third party repos or packages from AUR, your mirror is up to date and you have run -Syu twice.
Offline
To be really sure, could you show us the repo part your /etc/pacman.conf ? Or if you don't want to, here's mine, so you can compare
[xorg18]
# hal deprecation ftw
Include = /etc/pacman.d/mirrorlist
[testing]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist
[core]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist
[extra]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist
[xyne-any]
Server = http://xyne.archlinux.ca/repos/xyne-any
[community-testing]
## Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist
[community]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist
#[archaudio-stable]
#Server = http://repos.archaudio.org/stable/i686
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#Server = file:///home/custompkgs
Using [xorg18] is not recommended for you at the moment, so just forget that it's in there. Having [xyne-any] in there is also optional, I like Xyne's stuff, so I use his repo, if you don't use it, don't put it in there.
Offline
that happened to you because of the testing openssl package.
i had exactly the same issue. I managed to solve the problem by temporarily ln -s the openssl.so(and libcrypt if i remember correctly) to the newer file. pacman became functional again and what i did after was to reinstall stable openssl package.
Mikes on AUR
Offline
... temporarily ln -s the openssl.so.....
The definition is a symlink .
“Talent you can bloom. Instinct you can polish.” — Haikyuu!! (adapted)
“If everybody thought alike, no one would be thinking very much.” — Walter Lippmann (adapted)
“The important thing is to be able, at any moment, to sacrifice what we are for what we could become.” — Charles Dubois
Offline