Probably take time since alot of users post RC bugs while having mix of
packages sarge/unstable/experimental.
What are done with bugreports like that?
Should there be a rule perhaps?
Seen a few...
And there is still things to be done for the installer etc, probably were
the "battle" will be.
What is discussed here, should not this apply to kernel 2.4.27 wich is soon
out the door as well, also has had a looong test run, yes know it`s summer,
but 2.6 and 2.4- what`s comming seems like better than 2.4.26 and 2.6.7, and
yes one can always go on and say the next will be better d`oh, but
What is discussed here, should not this apply to kernel 2.4.27 wich is soon
out the door as well, also has had a looong test run, yes know it`s summer,
but 2.6 and 2.4- what`s comming seems like better than 2.4.26 and 2.6.7, and
yes one can always go on and say the next will be better d`oh, but
On Tue, Jul 27, 2004 at 12:38:37PM +, Thomas Skybakmoen wrote:
>Hi a question from a "normal" debian user:
>
>As sarge is comming to a server near me..
>I wounder why certian packages are so old when some are bleading new.
>bind (9.2.3) wich in debian is: 8.4.4
Hi a question from a "normal" debian user:
As sarge is comming to a server near me..
I wounder why certian packages are so old when some are bleading new.
bind (9.2.3) wich in debian is: 8.4.4
dhcp (3.0.1) wich in debian is: 2.0pl5
iptables (1.2.11) 1.2.9
modutils (2.4.27) 2.4.26 etc
I under
Must say I agree on alot here, that something has to change with the state
of unstable/testing?
Unstable is to be unstable: why have experimental?
All packages make their way into unstable, after maintainer have done some
work on it.
Some point I wanna make:
-Unstable should be frozen on a
6 matches
Mail list logo
