X11 is down in Cauldron for i586 machines because x11-driver-input-evdev-2.7.0-2.mga3.i586 cannot be installed. urpmi --debug x11-driver-input-evdev throws: search_packages: found x11-driver-input-evdev-2.7.0-1.mga2.i586 matching x11-driver-input-evdev search_packages: found x11-driver-input-evdev-2.7.0-2.mga3.i586 matching x11-driver-input-evdev found package(s): x11-driver-input-evdev-2.7.0-1.mga2.i586 x11-driver-input-evdev-2.7.0-2.mga3.i586 opening rpmdb (root=, write=) chosen x11-driver-input-evdev-2.7.0-2.mga3.i586 for x11-driver-input-evdev|x11-driver-input-evdev selecting x11-driver-input-evdev-2.7.0-2.mga3.i586 requiring xserver-abi(xinput-13)[>= 0] for x11-driver-input-evdev-2.7.0-2.mga3.i586 chosen x11-server-common-1.11.4-4.mga3.i586 for xserver-abi(xinput-13)[>= 0] the more recent x11-server-common-1.12.2-1.mga3.i586 is installed, but does not provide xserver-abi(xinput-13)[>= 0] whereas x11-server-common-1.11.4-4.mga3.i586 does selecting x11-server-common-1.11.4-4.mga3.i586 unselecting x11-server-common-1.11.4-4.mga3.i586 unselecting x11-driver-input-evdev-2.7.0-2.mga3.i586 pterjan reported on IRC that for x86-64 packages, the module reports: xserver-abi(xinput-16) >= 0 But the error message above has: xserver-abi(xinput-13) >= 0 It looks like this package has been compiled against an older version of x11-server-common. Because of this, the other X11 packages cannot be installed.
It's OK on x86_64. Indeed it looks like the BS badly failed since it pretended See eg http://pkgsubmit.mageia.org/uploads/done/cauldron/core/updates_testing/20120531070903.tv.valstar.9260/x11-driver-input-synaptics-1.6.1-1.mga3/ Logs shows that it failed to install x11-server-1.12 more than 24 hours after its upload (compare rpm-qa for both arches). This need to be fixed by sysadmins before we can resumbit drivers. Maybe a faulty media.cfg on ia32??? # cd core/updates_testing # rpm -qp --provides x11-server-common-1.12.2-1.mga3*|fgrep abi xserver-abi(ansic-0) = 4 xserver-abi(videodrv-12) = 0 xserver-abi(xinput-16) = 0 xserver-abi(extension-6) = 0 xserver-abi(videodrv) = 12.0 # rpm -qpR x11-driver-input-evdev-2.7.0-2.mga3.x86_64.rpm |fgrep abi xserver-abi(xinput-16) >= 0
Component: Release (media or process) => BuildSystemVersion: Cauldron => unspecifiedAssignee: bugsquad => sysadmin-bugsProduct: Mageia => Infrastructure
Hint: install_deps.logs suggests that we do not have the same version of iurt on the different machines (which is a bug per se) See "please use --buildrequires or --install-src, defaulting to --buildrequires" on x86_64 but not on i586 In both cases, core/updates_testing synthesis was parsed but only on x86_64 was x11-server-devel downloaded from it
Hm, We do have the same iurt-0.6.6-1.r3264.1.mga1.infra on valstar, jonund and ecosse since March 11th, 2012 so that should be ok and same iurt config is on both buildhosts I've resubmitted evdev package to see if it happends again
CC: (none) => tmb
both packages now have requires: xserver-abi(xinput-16) >= 0
You've to rebuild all other drivers. They were all affected...
And I can definitively tell you that above message show a code difference since it was recently killed.
(In reply to comment #5) > You've to rebuild all other drivers. > They were all affected... Yeah, evdev can now be installed correctly, but X11 still fails due to the other x11-driver modules being built against the wrong version. Could someone rebuild them all, please? :)
Summary: x11-driver-input-evdev is compiled against the wrong version of x11-server-common => x11-driver-* packages are compiled against the wrong version of x11-server-common
Many modules have been rebuilt by Thierry last night, but at least x11-driver-video-vboxvideo is still missing. The current package is still built against the older version, which prevents Cauldron from running in VirtualBox.
That's a different issue. VirtualBox doesn't compile with x11-server-1.12 whereas it is supposed to.
Created attachment 2433 [details] backtrace (screenshot) Here is the backtrace I get with the following packages installed: x11-driver-video-vboxvideo-4.1.16-3.mga3 vboxadditions-kernel-3.4.1-desktop586-1.mga3-4.1.16-2.mga3 virtualbox-guest-additions-4.1.16-3.mga3
So the GUI fails when booting, but calling startx manually starts the GUI just fine, so I don't know why it cannot do it itself on boot.
Fixed a long time ago
Status: NEW => RESOLVEDComponent: BuildSystem => RPM PackagesVersion: unspecified => CauldronResolution: (none) => FIXEDAssignee: sysadmin-bugs => bugsquadProduct: Infrastructure => Mageia