On Thu, Dec 05, 2002 at 08:28:20PM +1100, Daniel Stone wrote:
> Nope - the 3.0.x packages just were not ready to go into sid. Any
> package where the upgrade strategy is to purge the old and install the
> new just doesn't work. 3.1.x will be the first packages where upgrades
> from 2.2.x are clean.
On Thu, Dec 05, 2002 at 10:02:34AM +0100, Michael Meskes scrawled:
> On Thu, Dec 05, 2002 at 05:17:19PM +1100, Daniel Stone wrote:
> > Secondly, ftpmasters have to add overrides for new packages, in case you
> > didn't realize. That takes time: their time adding them, and our time
> > waiting. We'r
On Thu, Dec 05, 2002 at 05:17:19PM +1100, Daniel Stone wrote:
> First thing: KDE 3.1 will not be released this week. Expect a public
> announcement on this soon, but until then, I can say no more. Sorry, but
> it's out of my control.
I know what you're talking about as I just talked to Ralf.
> Se
[Excuse the dodgy quality, I'm trying to construct a reply from DWN].
On Fri, 29 Nov 2002 15:03:05 +0100, Michael Meskes scrawled:
> but since gcc 2.95 is still standard in Debian I guess the switch to 3.2
> will take much longer than the release of KDE 3.1 which is due next
> week.
>
> And the e
On Sat, Nov 30, 2002 at 10:53:40AM +0100, Mateusz Papiernik wrote:
> You're right. Packages from kde.org are very stable, and I think -
> correctly created, I'm using them for long time (about three months),
AFAIK the debian dirs are in KDE cvs anyway.
> and I didn't notice any problems with them
> temporar breakage. So it would be good to change them anyways. And
> looking so, the existing KDE3 packages could also go into Sid _now_.
You're right. Packages from kde.org are very stable, and I think -
correctly created, I'm using them for long time (about three months),
and I didn't notice a
#include
* Colin Watson [Fri, Nov 29 2002, 02:14:35PM]:
> > to see a good reason for not compiling KDE3 on gcc 2.95 as this
> > definitely works or else there wouldn't be a single KDE3 for woody
> > package on kde.org.
>
> The good reason is that all the KDE library sonames have to be changed
>
On Fri, Nov 29, 2002 at 02:57:32PM +, Paul Cupis wrote:
> > The matter of the fact is that almost all Debian/KDE users are already
> > using ftp.kde.org to get the KDE packages.
>
> Um, how do you know this?
Sorry, I of course don't know all Debian/KDE users. I was just
extrapolating. I talke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 29 November 2002 09:12, Michael Meskes wrote:
> The matter of the fact is that almost all Debian/KDE users are already
> using ftp.kde.org to get the KDE packages.
Um, how do you know this?
Paul Cupis
- --
[EMAIL PROTECTED]
-BEGIN PG
On Fri, Nov 29, 2002 at 03:05:46PM +0100, Michael Meskes wrote:
> Frankly, I can see the transition taking some more time, but still fail
> to see a good reason for not compiling KDE3 on gcc 2.95 as this
> definitely works or else there wouldn't be a single KDE3 for woody
> package on kde.org.
The
On Fri, Nov 29, 2002 at 11:07:15AM +0100, JÃrÃme Marant wrote:
> AFAIK, both gcc-3.2 and binutils have to be checked on every
> architecture and
> the transition will start once all architectures are ready for the
> transition.
And of course we have to create a plan for this transition before we
On Fri, Nov 29, 2002 at 09:52:52AM +, Tom Badran wrote:
> The plan as i understand it is to supply gcc 3.2 built packages once kde 3.1
> is released, and never supply gcc 2.95 ones in debian
but since gcc 2.95 is still standard in Debian I guess the switch to 3.2
will take much longer than th
Tom Badran wrote:
On Friday 29 Nov 2002 9:12 am, Michael Meskes wrote:
Hi,
I was just being told that we won't get any KDE3 packages until the
whole Debian project is moved to gcc 3.2. Is this correct? If so, why?
And is there a timetable? Is it a problem to compile the packages with
gcc 2.95?
T
On Friday 29 Nov 2002 9:12 am, Michael Meskes wrote:
> Hi,
>
> I was just being told that we won't get any KDE3 packages until the
> whole Debian project is moved to gcc 3.2. Is this correct? If so, why?
> And is there a timetable? Is it a problem to compile the packages with
> gcc 2.95?
>
> The ma
Hi,
I was just being told that we won't get any KDE3 packages until the
whole Debian project is moved to gcc 3.2. Is this correct? If so, why?
And is there a timetable? Is it a problem to compile the packages with
gcc 2.95?
The matter of the fact is that almost all Debian/KDE users are already us
15 matches
Mail list logo
