On 12/01/2018 02:45, Andreas Beckmann wrote:
I don't see such behavior in sid on amd64/i386/armhf - is this specific
to Ubuntu?
Sorry for not checking that. Indeed, this is specific to Ubuntu where
libgtk2.0-0.symbols gained a bunch of symbols like:
g_cclosure_marshal_VOID__*@Base 2.24.31
...and libnvidia-gtk2.so built in Ubuntu imports
g_cclosure_marshal_VOID__POINTER and g_cclosure_marshal_VOID__VOID
The most generic solution would probably be to split nvidia-settings
into three packages: nvidia-settings, libnvidia-gtk2, libnvidia-gtk3
and drop any gtk dependency magic we currently have.
That would work, but I still don't like the idea as these "shared
libraries" or "plugins" are only used by nvidia-settings and aren't
shared with anything else and would just waste in the archive metadata.
Besides, I expect the gtk2 version to fall away at some point.
So, although no change is needed in Debian right now, I do think the
regexes on (>= 2.8.0) and (>= 3.0.0) are a little fragile and either
should be relaxed, or should fail if no match is found so at least an
unexpected change can be caught.
