On 14.06.2012 15:05, Dominique Leuenberger a.k.a DimStar wrote:
Quoting Stephan Kulow <coolo(a)suse.de>de>:
On 14.06.2012 14:50, Dominique Leuenberger a.k.a
It's maintained by SUSE and from what I can
say, SUSE fixed the problem.
I would have just preferred if this fixing happened as a side project
instead of having a broken zypper for so long. The question is if this
is realistic - if SUSE would have put so much effort into it
if it wasn't already broken in factory. And this applies to all
maintainers of all components.
This is actually exactly what was observed: the problem was reported
(before making 4.7 the default), ignored, escalated, ignored...
Worse, it wasn't ignored - but libzypp got changed to compile with the
old compiler. Only after accepting 4.7 as default (which I didn't do
before I was told "zypp is working with it") it was figured out that
this mix between gcc 4.6 and 4.7 won't do it.
The problem here was clearly that we built all packages against 4.7 on
their own instead of trying a full distro built on it.
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org