| Summary: | libx11_6-devel conflicts with lib64x11_6-devel | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Dane Mutters <dmutters> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | thierry.vignaud |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | https://forums.mageia.org/en/viewtopic.php?f=8&t=2283 | ||
| Whiteboard: | |||
| Source RPM: | libx11-1.4.3-1.mga1.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Dane Mutters
2012-04-22 20:13:16 CEST
On the previously-linked forum thread, doktor5000 suggested that I try doing this: [CODE] wget ftp://ftp.mandrivauser.de/mirrors/Mageia/distrib/cauldron/SRPMS/core/release/wine-1.4-1.mga2.src.rpm urpmi rpm-build urpmi --buildrequires wine-1.4-1.mga2.src.rpm rpmbuild --rebuild wine-1.4-1.mga2.src.rpm [/CODE] Unfortunately, it didn't work, since the dependencies of that WINE source rpm aren't available in the current repositories (without adding the cauldron ones and breaking glibc, among other things). Here's the output I got: [CODE] [root@orchestrator wine]# urpmi --buildrequires wine-1.4-1.mga2.src.rpm A requested package cannot be installed: wine-1.4-1.mga2.src (due to unsatisfied valgrind-devel) [/CODE] ...so, after finding that there isn't a valgrind-devel in the current repos, I downloaded and attempted to install the appropriate valgrind (which the -devel depends on) and valgrind-devel from here (cauldron versions): ftp://rpmfind.net/linux/mageia/distrib/cauldron/x86_64/media/core/release/valgrind-3.7.0-1.mga2.x86_64.rpm ftp://rpmfind.net/linux/mageia/distrib/cauldron/x86_64/media/core/release/valgrind-devel-3.7.0-1.mga2.x86_64.rpm ...and got this: [CODE] [root@orchestrator wine]# rpm -ivh valgrind* error: Failed dependencies: libc.so.6(GLIBC_2.14)(64bit) is needed by valgrind-3.7.0-1.mga2.x86_64 [/CODE] The required version of glibc isn't in any of the Mageia 1 repos, so I stopped here. I don't know if this is helpful (please let me know if I'm being too detailed), but hopefully it sheds some light on the problem. --Dane your bug in unreadable, next time use attachments instead of copy-paste Sorry about that. Should I re-do it, or can it slide this time? (I'll avoid doing that in the future.) Update: I've solved this by using the release candidate of Mageia 2, and following the steps outlined in the following post (same thread as before): https://forums.mageia.org/en/viewtopic.php?f=8&t=2283&p=16934#p18151 Since MGA2 seems to have fixed the relevant library conflicts, this bug seems to no longer be important, except for those wishing to fix it in MGA1 (if that's even possible). Have a nice day. really Status:
NEW =>
RESOLVED |