FTBFS in raring-proposed (libdrm_nouveau 2)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Raring |
Fix Released
|
Medium
|
Unassigned |
Bug Description
libdrm_nouveau 2 is now in raring-proposed.
After dropping update-
Maybe we need newer plymouth? bug 1022757
It fails to build from source.
CC drm_la-
./ply-renderer-
./ply-renderer-
CC drm_la-
CC drm_la-
./ply-renderer-
compilation terminated.
make[6]: *** [drm_la-
make[6]: Leaving directory `/«PKGBUILDDIR»
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/«PKGBUILDDIR»
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/«PKGBUILDDIR»
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/«PKGBUILDDIR»
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/«PKGBUILDDIR»'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/«PKGBUILDDIR»'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
disabling all the drm renderers besides the dumb ioctl one is probably the best way to go, it should be using the generic one. Also --disable-libkms would be useful, the dumb version that was backported in quantal supersedes it and its just a useless dependency. Note: nothing actually used libkms in plymouth.
see http:// cgit.freedeskto p.org/plymouth/ commit/ ?id=8e932e9895b acf9b490e60e4be 63d8902201e5d5 for the rationale of disabling the device specific drm drivers and http:// cgit.freedeskto p.org/plymouth/ commit/ ?id=527400dc5a9 da4cd3ef8a831e7 309e1627d6b3b0 for info on the generic driver.