Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#6461 - dependancy issues installing mplayer

Attached to Project: Arch Linux
Opened by Scott (Mashi) - Tuesday, 20 February 2007, 16:14 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

My first bug report, sorry if it doesn't have loads of detail! Went like this:

Trying to install mplayer from extra repository:

1.
file conflict installing dependancy libstdc++5, forced it with 'pacman -Sf libstdc++5'
'pacman -S mplayer' completes.

2.
starting mplayer, libdb not found, resolved with 'pacman -S db'.


3.
"./mplayer: /lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by /usr/lib/libldap-2.3.so.0)"
resolved with 'pacman -S glibc'

mplayer works.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 21 February 2007, 22:14 GMT
Reason for closing:  Works for me
Comment by Pierre Schmitz (Pierre) - Wednesday, 21 February 2007, 10:12 GMT
Did you ever upgrade your system using "pacman -Syu"?
Comment by Jan de Groot (JGC) - Wednesday, 21 February 2007, 10:22 GMT
No he didn't, he's using glibc 2.3.x, which doesn't export the required GLIBC_2.4 versioned symbols. Then the libstdc++ dependency with file conflicts, which points to an old gcc package that had libstdc++ included (he'll get issues with other packages also in the future, libldap, smbclient, postgresql-libs, libmysqlclient, etc).

The problem we have here is that when upgrading packages in the repositories, we assume people run pacman -Syu to update the whole system. In that case, all works fine. We can't use versioned conflicts (yet?), so we can't force the user to upgrade their packages to a non-conflicting version.

Comment by Scott (Mashi) - Wednesday, 21 February 2007, 18:20 GMT
This is correct of course, my system wasn't up to date and that was the cause of the issues I had. Did a new install today, updated and mplayer installed with no issues.

I'll be sure to keep my system up to date from now on! Sorry guys!

Loading...