Re: Is Gnome working in teesting?
On Mon, Aug 25, 2003 at 12:47:49AM +0100, Colin Watson wrote:
> On Sun, Aug 24, 2003 at 02:01:47PM -0400, stan wrote:
> > On Sun, Aug 24, 2003 at 05:27:26PM +0100, Colin Watson wrote:
> > > If it's filed in the bug tracking system, at the moment you just have to
> > > look at the bug every so often, although there's some work outstanding
> > > on letting you subscribe to bugs.
> > >
> > > If it's not, then you just have to look every so often. In the case of
> > > GNOME, reading the debian-gtk-gnome mailing list would probably be your
> > > best bet, if you aren't prepared to keep a very close eye on the state
> > > of testing (which I try to do for other reasons).
> > Is sound still also broken in testing?
> [Please don't send me private copies of list mail. I read the list.]
Sorry, my mailer insists on sending mail back to the originator. I thinks
it's because of the way the mailheaders come from the list :-(
O catually have to explictly cc the list to get it sent there.
> I don't know the problem you're referring to, so I have no idea ...
smokey:~# apt-get upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages have been kept back
aspell aspell-en audacity avifile-mad-plugin avifile-mjpeg-plugin
avifile-player avifile-vorbis-plugin avifile-win32-plugin
avifile-xvid-plugin avview black-box bubblemon criticalmass debconf
freeciv-gtk gcompris gcompris-data gcompris-sound-en gedit glunarclock
gnome-applets gnome-mud gnome-panel gnome-panel-data gnome-session
gnome-spell gnome-utils gnumeric gnumeric-python initrd-tools j2re1.3
libguppi16 libgwrapguile1 libopenal0 libsdl-mixer1.2 mc mp3blaster
mplayer-k6 mysql-navigator pan penguin-command rockdodger sidplay-base
simplecdrx soundtracker sox timidity tuxpaint vegastrike vorbis-tools
wenglish xchat-common xine-ui xmms-modplug xmms-osd-plugin xmms-qbble
xmms-sid xpenguins-applet 0 packages upgraded, 0 newly installed,
0 to remove and 58 not upgraded.
> > And a followup question, if I want to install a new system, what should I
> > do, just install stable, and accept that it will not be nearly as current
> > as my machines which have been tracking testing for a while?
> That depends what you're looking for. My server runs stable; my laptop
> (which is also my main development machine) runs unstable; my
> workstation at work ran stable up until late last week, and now runs
> testing because I wanted mozilla-firebird with anti-aliased fonts.
How did you get it upgraded to testing, given all teh current breakeage in
> Right now, systems running testing are actually substantially out of
> date with respect to unstable, due to problems holding up chunks of
> GNOME 2 and all of KDE 3, and more recently problems with glibc 2.3.2.
> Once the latter is resolved I expect the former two to follow reasonably
Great, so much for trying KDE to see if it's better than the new Gnome :-(
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin