[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
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
Hello
Steve Langasek suggested me I re-upload my gnustep packages without the binary
package rename. I know they happened late, but I think it's good they happened
now. The latest GNUstep tarball release got an update that is binary
incompatible to
the old ones. So all needed a rebuild, great
Please can you identify the packages in the new queue, which are
currently in testing, and which are new (not in testing)?
Thanks; Matthias
Gürkan Sengün writes:
Hello
Steve Langasek suggested me I re-upload my gnustep packages without the binary
package rename. I know they happened late,
Please can you identify the packages in the new queue, which are
currently in testing, and which are new (not in testing)?
Yes of course,
New:
gnuwash
mpdcon
plopfolio
agenda
displaycalibrator
volumecontrol
helpviewer
preview
connect
Already in sid/testing:
camera
mknfonts
textedit
viewpdf
-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
Currently, sarge has adduser 0.57, sid has adduser 0.59
0.59 has been uploaded on July 30, before the freeze, and both 0.58
and 0.59 have been translation updates only without the actual code
being touched.
Can 0.59 be hinted to sarge, or should I upload a 0.60 to t-p-u?
Thanks for your
On Sun, Aug 15, 2004 at 11:34:26AM +0100, Gürkan Sengün wrote:
Steve Langasek suggested me I re-upload my gnustep packages without the binary
package rename. I know they happened late, but I think it's good they happened
now. The latest GNUstep tarball release got an update that is binary
hi, vim and vimhelp-fr need to be hinted to enter testing together
(when vimhelp-fr is old enough):
easy vim/1:6.3-013+2 vimhelp-fr/6.3.011-1
as for the vimacs-becomes-uninstallable issue (see RC bug #265435),
and given the rush, I'd ask for a remove vimacs/0.95-1.1 hint to
make
On Sun, Aug 15, 2004 at 10:21:06PM +0200, Marc Haber wrote:
Currently, sarge has adduser 0.57, sid has adduser 0.59
0.59 has been uploaded on July 30, before the freeze, and both 0.58
and 0.59 have been translation updates only without the actual code
being touched.
Can 0.59 be hinted to
* Colin Watson [EMAIL PROTECTED] [2004-08-16 00:58]:
[Sorry if you didn't want a CC; it's kind of awkward to decide whether
to treat debian-release as a role address or as a mailing list ...]
I'd treat it as a role address (with an exception for people who seem
to be obviously subscribed).
--
16 matches
Mail list logo
