synaptic on 17.10
On Thu, 2018-02-01 at 20:05 +0100, Ralf Mardorf wrote:
> On Thu, 1 Feb 2018 18:58:16 +0100, Liam Proven wrote:
> > I wouldn't call that a bug.
> Full ACK. Upstream of apps should care about changes of dependencies,
> even if upstream makes idiotic changes, such as /usr/bin/enchant moving
^^^^^^^^^of the dependencies
> to /usr/bin/enchant-2, but they need to give upstream of those apps a
> chance to make such transitions, or at least package maintainers should
> be able to fix such issues by patches, without hard time pressure.
> However, remember that pulseaudio developers blaimed ALSA developer for
> drivers, that worked with all sound servers and plain ALSA, but were
> blamed to be the culprit, when they didn't work with pulseaudio or
> remember that even Linus was not willing to include selfish changes of
> [snip names], let alone to make user space things that breaks much, to
> become part of the kernel. Now it's again something GNOMEish that does
> cause issues. Actually synaptic works with X, while appart from the
> Wayland issue a lot of useful GTK based apps and themes are rendered
> useless. The GNOME/GTK folks are not dominating Linux, neither to the
> good, let alone to the bad. Remember that the NVIDI floss driver made
> a transition to nouveau, when nouveau still was completely broken. A
^^^^^^^ Yes, not an issue related to the GNOME folks,
but an example fore something similar idiotic.
> community is based upon arrangements. Making Wayland the default, while
> some machines even could not run GNOME with X, at a time when many
> important GUIs still require uncomplicated root access is the failur of
> distro maintainers, as well as GNOME maintainers. If Ubuntu's concern
> is about security, then Ubuntu should start to tidy up the universe
> repository and remove siomething vulnerable as libwebkitgtk-1.0-0,
> before switching from X to Wayland.