On Thursday 14 February 2008, Modestas Vainius wrote:
> Hi,
>
> As of writing, libqt3-mt ABI breakage caused serious 16 bugs (#464946 &
> friends) to be reported by our users. So I think it's high time we took
> some action today or tommorow to unbreak software affected. I'm concerned
> about Debia
Hi,
2008 m. February 16 d., Saturday, Matthew Rosewarne rašė:
> I've looked through all C++ packages (libsdtc++6 rdepends), and I think I
> have a complete list of broken pacakges. They are:
>
> digikam
> k3b
> kcontrol
> kdirstat
> kexi
> konq-plugins
>
Sune Vuorela <[EMAIL PROTECTED]> writes:
[...]
> Recomendations:
>
> Take libqt4-core, split off libqtscript4 and libqtdbus4 to its own packages
> and rename libqt4-core to libqtcore4
>
> keep libqt4-gui as is
>
> rework libqt4-sql to make it plugin based, which it supports and enable the
> rest
On Sat, Feb 16, 2008 at 08:08:17AM +, Matthew Rosewarne wrote:
> On Thursday 14 February 2008, Modestas Vainius wrote:
> > Hi,
> >
> > As of writing, libqt3-mt ABI breakage caused serious 16 bugs (#464946 &
> > friends) to be reported by our users. So I think it's high time we took
> > some act
Hi,
2008 m. February 16 d., Saturday, Pierre Habouzit rašė:
> Okay that's quite a few, so the "Conflict" option sucks. Here is
> another plan, tell me what you think, we put a debian specific hack in
> the glibc to reenable the extern inlines for _ONLY_ the packages that
> ask for it, for lenny,
On Sat, Feb 16, 2008 at 10:52:01AM +, Modestas Vainius wrote:
> Hi,
>
> 2008 m. February 16 d., Saturday, Pierre Habouzit rašė:
> > Okay that's quite a few, so the "Conflict" option sucks. Here is
> > another plan, tell me what you think, we put a debian specific hack in
> > the glibc to ree
On Sat, Feb 16, 2008 at 10:58:13AM +, Pierre Habouzit wrote:
> I absolutely don't understand how that can be true. I mean it doesn't
> make sense, ktorrent gets the symbol from the libc6, and it just emits
> an undefined symbol because qt3 provides it at the time, there is no way
> it gets it
On Sat, Feb 16, 2008 at 01:22:31PM +, Pierre Habouzit wrote:
> We should still look in the archive if other libraries have the
> symbols and deal on a per case basis. It seems c++ libraries are the one
> affected, C ones usually arent as extern inline has a different meaning
> in C (especiall
