Bug#788703: d-i/cdebconf vs. gtk3/libepoxy?
kibi at debian.org
Mon Jan 11 03:41:27 UTC 2016
Cyril Brulebois <kibi at debian.org> (2016-01-11):
> Emilio Pozuelo Monfort <pochu at debian.org> (2015-06-14):
> > gtk+ 3.0 now depends on libepoxy, so we need a libepoxy udeb.
> The attached patch seems to do the trick. With it I was able to rebuild
> gtk+3.0 so that its udeb gets the proper dependency, and to build a
> netboot-gtk mini.iso Debian Installer image with the resulting udebs.
> I'm getting a black screen at start-up though, which might just be
> insufficient or incorrect porting in the cdebconf gtk frontend when
> built against gtk3. This will be discussed on debian-boot@:
There was an issue in cdebconf indeed, see report at:
Next issue: It seems we need libGL.so.1 so that something built against
gtk3 has a chance of being displayed (through libepoxy presumably, given
its purpose/description) → now getting ENOENT and a retry loop, which is
a different kind of black screen in d-i.
If that was at all possible, it would be nice if we could avoid pulling
mesa inside d-i, and maybe disable libepoxy in src:gtk+3.0 for its udeb.
libepoxy doesn't seem to be optional there though…
If that can't be done, sticking with gtk2 might be an option… :(
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: Digital signature
More information about the pkg-gnome-maintainers