i installed 0ad in rpmdrake ( selecting 0ad ) Assertion failed: "!pathname.IsDirectory()" Location: vfs_lookup.cpp:141 (vfs_Lookup) Call stack: (0x95935e) /usr/games/pyrogenesis() [0x95935e] (0x8ffc29) /usr/games/pyrogenesis() [0x8ffc29] (0x901634) /usr/games/pyrogenesis() [0x901634] (0x91d770) /usr/games/pyrogenesis() [0x91d770] (0x91638d) /usr/games/pyrogenesis() [0x91638d] (0x6cdef7) /usr/games/pyrogenesis() [0x6cdef7] (0x6869cc) /usr/games/pyrogenesis() [0x6869cc] (0x861f11) /usr/games/pyrogenesis() [0x861f11] (0x8ba090) /usr/games/pyrogenesis() [0x8ba090] (0x8bc32c) /usr/games/pyrogenesis() [0x8bc32c] (0x8bc843) /usr/games/pyrogenesis() [0x8bc843] (0x66038c) /usr/games/pyrogenesis() [0x66038c] (0x664825) /usr/games/pyrogenesis() [0x664825] (0x4361cd) /usr/games/pyrogenesis() [0x4361cd] (0x424367) /usr/games/pyrogenesis() [0x424367] (0x7fca94402050) /lib64/libc.so.6(__libc_start_main+0xf0) [0x7fca94402050] errno = 0 (No error reported here) OS error = ?
Assignee: bugsquad => rverschelde
instaling 0ad in terminal fixed the pb. Maybe the require between 0ad and 0ad-data should be stronger
I don't understand. 0ad requires 0ad-data already: http://svnweb.mageia.org/packages/cauldron/0ad/current/SPECS/0ad.spec?view=markup In comment 0 you say you installed *0ad* in rpmdrake, and in comment 1 *0ad* in the terminal. Did you mean *0ad-data* for comment 1? If so it's quite puzzling if rpmdrake let you install 0ad without the data.
Hm I think I finally get it, though you should have provided more information initially ;) Since rpmdrake shows both Release and Update versions, you likely installed the 0ad-0.0.18-1.mga5 package from Core Release, which requires "0ad-data >= %{epoch}:%{version}", so it pulled 0ad-data-0.0.19-1.mga5 from Core Updates (validated as bug 17253). So I need to change the requires to a strict =, not >=. I'll fix that as part of bug 21371.
Fixed in Cauldron and will be fixed in Mageia 6 via bug 21371 (actually it won't be until people install the new 0ad-0.0.22-1.1.mga6, so they could still reproduce your issue, but it's a corner case and easily fixed with the next run of MageiaUpdate, so it's not that critical).
Resolution: (none) => FIXEDStatus: NEW => RESOLVED