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 y
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=265852&repeatmerged=no.
> > Sho
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 pac
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 your
-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
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
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
> cour
> 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
On Sat, Aug 14, 2004 at 09:50:52PM -0700, Steve Langasek wrote:
> [Please cc: debian-release on replies.]
>
> As some of you probably already know, a number of packages from KDE 3.3
> have been uploaded today to unstable. This upload of a major new
> upstream release was not discussed with the re
[Please cc: debian-release on replies.]
As some of you probably already know, a number of packages from KDE 3.3
have been uploaded today to unstable. This upload of a major new
upstream release was not discussed with the release team prior to
upload; actually, it's caused quite a bit of consterna
10 matches
Mail list logo
