** Changed in: ldm (Debian)
Status: Unknown => Fix Released
--
ldm should depend on gtk2-engines instead of gtk2-engines-clearlooks
https://bugs.launchpad.net/bugs/299944
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
** Bug watch added: Debian Bug tracker #510204
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510204
** Also affects: ldm (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510204
Importance: Unknown
Status: Unknown
--
ldm should depend on gtk2-engines instead of gtk
can you please file this in debian then, i dont think adding an extra
delta between the packages and additional maintenance work makes any
sense here, sorry ...
** Changed in: ldm (Ubuntu)
Status: New => Invalid
--
ldm should depend on gtk2-engines instead of gtk2-engines-clearlooks
https
Well, In that case the clean way is to update the dependencies to depend
on gtk2-engines, not gtk2-engines-clearlooks, which does not exist in
the archives anymore. gtk2-engines replaces/provides/conflicts gtk2
-engines-clearlooks.
** Changed in: ldm (Ubuntu)
Status: Invalid => New
--
ldm
the clearlooks engine is used by the builtin default ltsp theme which is
used as a fallback. it must be installed in any case to provide a safe
fallback mechanism.
** Changed in: ldm (Ubuntu)
Status: New => Invalid
--
ldm should depend on gtk2-engines instead of gtk2-engines-clearlooks
ht
Hi,
Yes from technical point of view the dependency is ok. But don't you
think it's quite silly to have dependencies on packages that don't exist
any more? It's called bit rot. Besides fixing that is just a matter of
changing one line, so why not do that for the next jaunty upload?
Besides, AFAIK
gtk2-engines-clearlooks is provided by gtk2-engines so AFAIk the
dependency works fine (at least on all the system I have). Marking the
bug report Invalid.
** Changed in: ldm (Ubuntu)
Status: New => Invalid
--
ldm should depend on gtk2-engines instead of gtk2-engines-clearlooks
https://bu
