> On 13 Oct 2016, at 18:01, Daniel Quinn wrote:
>
> On 13/10/16 02:36, wabe wrote:
>> Since the update process is dead slow anyway and I really don't care
> about a few minutes less ore more, I always use --backtrack=999.
>
> Unfortunately yes. I took your advice just now and it's still
> comp
On Thu, 13 Oct 2016 18:17:18 +0100, Daniel Quinn wrote:
> > Because the ebuild says so. The question you should be asking is
> > "why", especially as none of the other gtk+ ebuilds contain this
> > DEPEND. And that's a question that is probably best asked on b.g.o.
>
> Sorry, but what's "b.g.o.
> Because the ebuild says so. The question you should be asking is "why",
> especially as none of the other gtk+ ebuilds contain this DEPEND. And
> that's a question that is probably best asked on b.g.o.
Sorry, but what's "b.g.o."? Are you saying that this might be a bug?
On Thu, 13 Oct 2016 18:01:53 +0100, Daniel Quinn wrote:
> Unfortunately yes. I took your advice just now and it's still
> complaining about circular dependencies. Maybe I'm missing something,
> but how can gtk+ *depend* on gtk-engines-adwaita?
Because the ebuild says so. The question you should
On 13/10/16 02:36, wabe wrote:
> Since the update process is dead slow anyway and I really don't care
about a few minutes less ore more, I always use --backtrack=999.
Unfortunately yes. I took your advice just now and it's still
complaining about circular dependencies. Maybe I'm missing somethin
Daniel Quinn wrote:
> Have any of you seen this before? This is on a fresh install. I
> can't get anything GNOME-based to install as it looks like
> gnome-keyring is bringing in an older version of gtk+ which somehow
> depends on gtk-engines-adwaita which in turn depends on gtk+.
>
> Details:
6 matches
Mail list logo