On Fri, 8 Nov 2013 16:38:15 +0100 Manfred Hollstein <manfre...@gmx.net> wrote: > I was just trying to update to the latest version of MPlayer on > openSUSE-12.3 (x86_64): > > $ rpm -Uvh --test > > /nobackup/update-mirror/packman/suse/12.3/Essentials/x86_64/MPlayer-1.1.1+r36500-1.2.x86_64.rpm > > error: Failed dependencies: > libartsc.so.0()(64bit) is needed by > MPlayer-1.1.1+r36500-1.2.x86_64 > > "zypper in MPlayer-1.1.1+r36500-1.2" would of course pull in any > needed packages, but, to be honest, I'd rather stay away from having > this arts stuff back on my systems... Also, arts will pull in qt3... > This doesn't look proper to me.
Yes, RedDwarf also found this and initiated a change in our build environment (see his post "Disabling aRts"). Newer builds should not require aRts anymore. > Another thing I saw is that zypper believes that my currently > installed version of MPlayer "1.1+35127-4.1" has a higher version > number than the newer one: > > $ zypper in MPlayer-1.1.1+r36500-1.2 > Loading repository data... > Reading installed packages... > The selected package 'MPlayer-1.1.1+r36500-1.2.x86_64' from > repository 'packman' has lower version than the installed one. Use > 'zypper install --oldpackage MPlayer-1.1.1+r36500-1.2.x86_64' to > force installation of the package. Resolving package dependencies... > > Nothing to do. > > From what I can tell, 1.1.1+r36500-1.2 looks larger/higher to me than > 1.1+35127-4.1 Yes, fscking rpm number comparison (OK, it's not rpm's fault). Our new version number "1.1.1..." is smaller than "1.1+...", although the 1.1.1 is the newer package. We should switch to a different version name. I opened a bug (PM-92) in https://bugs.links2linux.org. > Looking at the package's ChangeLog shows interesting stuff: > > $ rpm > -qp > /nobackup/update-mirror/packman/suse/12.3/Essentials/x86_64/MPlayer-1.1.1+r36500-1.2.x86_64.rpm > --changelog > * Tue Nov 05 2013 joerg.loren...@ki.tng.de > - update to version 1.1.1+r36500 > * build against external libx264 > * build internal ffmpeg-2.1 (build against external ffmpeg also > possible) > * update Blue to version 1.8 > * update Clearlooks to version 1.5 > * added several patches from distro Mageia > * (nearly) complete rewrite of specfile > > The "(nearly) complete rewrite of specfile" looks quite suspicious to > me; could it be the source for suddenly require'ing libartsc again, as > my current version of MPlayer "1.1+35127-4.1" did not require it. As said, the currently compiled MPlayer does not require arts anymore. Greetings, Stefan -- Stefan Botter zu Hause Bremen
signature.asc
Description: PGP signature
_______________________________________________ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman