Hello,
Quoting Steve Langasek [EMAIL PROTECTED]:
Yes, Qt3.3 is slated for sarge; we're just waiting for it to be in
sync on all architectures.
Ok, sounds good.
Is this incompatibility documented in the BTS? Is your package the
only one affected?
The good news is that the bug was fixed in
On Mon, Aug 16, 2004 at 05:13:41PM -0400, Christopher Martin wrote:
KDE 3.3 is out, which is fine, but is Qt 3.3 planned for Sarge? It's been
in Sid for a while, so a lot has been built against it.
Yes, Qt3.3 is slated for sarge; we're just waiting for it to be in sync
on all architectures.
On Sun, Aug 15, 2004 at 04:33:47PM +0200, Rene Engelhard wrote:
Chris Cheney wrote:
I did not upload KDE 3.3 to try to have a nice shiny new release in
sarge, it just seemed to lesser of the evils and considering the current
ah, and breaking other packages and the release plan with your
to delay the freeze for KDE3.3. After
discussing with Ben Burton, it is clear that allowing only part of
KDE
3.3 into sarge so close to the freeze is likely to lead to new bugs,
and
that any attempt to get all of KDE3.3 into sarge at this point would
unacceptably delay the release schedule
discussing with Ben Burton, it is clear that allowing only part of KDE
3.3 into sarge so close to the freeze is likely to lead to new bugs, and
that any attempt to get all of KDE3.3 into sarge at this point would
unacceptably delay the release schedule.
If you maintain KDE-related packages
I estimate it would only
take a couple days to get all of KDE 3.3 ready for release, besides
being built.
Well, speak for yourself. :)
I had assumed that 3.2 was going to ship with sarge (given how close the
upstream 3.3 release was to the freeze, and given that the 3.3 upload to
unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Steve Langasek wrote:
still outstanding requirement to get rid of libtiff3g for sarge. Ben
Burton has already expressed his willingness to NMU these packages if
necessary; Chris, if you are available to work on this yourself, I am of
course
Hi,
Rene Engelhard wrote:
Should that be upgraded to serious and then tagged sarge-ignore since it
only is something with KDE 3.3?
will do this and will tag all other bugs wrt that sarge-ignore.
(no, I don't plan another upload to fix this bug before 1.1.3 or so)
and fix this conflict
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Cheney wrote:
I did not upload KDE 3.3 to try to have a nice shiny new release in
sarge, it just seemed to lesser of the evils and considering the current
ah, and breaking other packages and the release plan with your upload
*without warning
On Sun, Aug 15, 2004 at 03:16:35PM +0200, Rene Engelhard wrote:
Steve Langasek wrote:
still outstanding requirement to get rid of libtiff3g for sarge. Ben
Burton has already expressed his willingness to NMU these packages if
necessary; Chris, if you are available to work on this yourself,
On Sun, Aug 15, 2004 at 12:38:16PM -0700, Steve Langasek wrote:
On Sun, Aug 15, 2004 at 03:16:35PM +0200, Rene Engelhard wrote:
Steve Langasek wrote:
still outstanding requirement to get rid of libtiff3g for sarge. Ben
Burton has already expressed his willingness to NMU these packages if
On 2004-08-15 Steve Langasek [EMAIL PROTECTED] wrote:
On Sun, Aug 15, 2004 at 03:16:35PM +0200, Rene Engelhard wrote:
[...]
And kdelibs-data AGAIN caused file conflicts with
openoffice.org-mimelnk. See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=265852repeatmerged=no.
Should that be
12 matches
Mail list logo
