On Tue, Aug 29, 2006 at 10:52:15PM +0200, Moritz Muehlenhoff wrote:
> David Nusinow wrote:
> >> The rough plan is to provide an alternative set of updated kernel packages
> >> and potentially also xservers (depending on how modular the new X.org
> >> modulization really is) nine months after Etch r
David Nusinow wrote:
>> The rough plan is to provide an alternative set of updated kernel packages
>> and potentially also xservers (depending on how modular the new X.org
>> modulization really is) nine months after Etch release. ian.org
>> with a subject of "unsubscribe". Trouble? Contact [EMAIL
David Nusinow wrote:
> On Sun, Aug 27, 2006 at 10:57:45PM +0200, Moritz Muehlenhoff wrote:
> > The rough plan is to provide an alternative set of updated kernel packages
> > and potentially also xservers (depending on how modular the new X.org
> > modulization really is) nine months after Etch rele
Moritz Muehlenhoff wrote:
> Martin Schulze wrote:
> > It would be good, though, especially in order to have some support for
> > hardware that has entered the market after the last Debian release, if
> > there would be an outside repository for updated kernel and installer
> > packages. However, n
On Mon, Aug 28, 2006 at 10:11:06PM +, David Nusinow wrote:
> libs or protocol headers though. The 7.1 server only requires an update of
> one lib and two protocol headers from 7.0. I'd imagine that this will be
^^^
Sorry, two libs, although one is mesa.
- David Nusinow
--
To UNSUBSCRIB
On Sun, Aug 27, 2006 at 10:57:45PM +0200, Moritz Muehlenhoff wrote:
> The rough plan is to provide an alternative set of updated kernel packages
> and potentially also xservers (depending on how modular the new X.org
> modulization really is) nine months after Etch release. ian.org
> with a subject
Martin Schulze wrote:
> It would be good, though, especially in order to have some support for
> hardware that has entered the market after the last Debian release, if
> there would be an outside repository for updated kernel and installer
> packages. However, nobody considered this important enou
On Sun, Aug 27, 2006 at 08:48:03PM +0200, Martin Schulze wrote:
> and used Debian packaging, here's what was required only to get the
> binary package installed:
>
> http://www.backports.org sarge-backports/main module-init-tools 3.2.2-2bpo1
> [79.3kB]
> http://www.backports.org sarge-backports/m
On Sun, Aug 27, 2006 at 08:48:03PM +0200, Martin Schulze wrote:
> Martin Schulze wrote:
> > > Examples of things that should happen in stable, but haven't been
> > > happening reliably:
> > >
> > > * Kernel updates with more broad hardware support
> >
> > This requires new kernel packages, new u
Martin Schulze wrote:
> > Examples of things that should happen in stable, but haven't been
> > happening reliably:
> >
> > * Kernel updates with more broad hardware support
>
> This requires new kernel packages, new utilities and a new installer.
> It a hell of an effort to get this done. Just
John Goerzen wrote:
> But I'm not trying to talk in this thread about how hard or easy it is
> technically to build stuff for stable. That level will change over
> time. (And if we really find it so much more difficult to build a
> kernel for stable than other distros do, we need to examine that
On Sat, Aug 26, 2006 at 09:03:12PM +0900, Kenshi Muto wrote:
> At Sat, 26 Aug 2006 11:52:29 +0200,
> Michael Banck wrote:
> > On Sat, Aug 26, 2006 at 08:43:53AM +0200, Martin Schulze wrote:
> > > It would be good, though, especially in order to have some support for
> > > hardware that has entered
At Sat, 26 Aug 2006 11:52:29 +0200,
Michael Banck wrote:
> On Sat, Aug 26, 2006 at 08:43:53AM +0200, Martin Schulze wrote:
> > It would be good, though, especially in order to have some support for
> > hardware that has entered the market after the last Debian release, if
> > there would be an outs
On Sat, Aug 26, 2006 at 08:43:53AM +0200, Martin Schulze wrote:
> It would be good, though, especially in order to have some support for
> hardware that has entered the market after the last Debian release, if
> there would be an outside repository for updated kernel and installer
> packages. Howe
[EMAIL PROTECTED] wrote:
>I am mainly interested in #1. I think we need to take a more expansive
>view of what constitutes a functionality problem, perhaps replacing
>"truly critical" with "serious".
I fully agree. I do not consider "volatile" a solution.
--
ciao,
Marco
--
To UNSUBSCRIBE, em
Sven Luther wrote:
> > mkinitrd
>
> mkinitrd is dead :)
Whatever... :)
> > debhelper
>
> debhelper ???
Didn't it creep in? Maybe not.
> > yard
>
> yaird is its name.
Oh well...
> > Just try to get a more recent kernel from backports.org on a sarge
> > machine and you'll see.
>
> Actually
On Sat, Aug 26, 2006 at 09:57:37AM +0200, Martin Schulze wrote:
> John Goerzen wrote:
> > On Sat, Aug 26, 2006 at 08:43:53AM +0200, Martin Schulze wrote:
> > > John Goerzen wrote:
> > > > Examples of things that should happen in stable, but haven't been
> > > > happening reliably:
> > > >
> > > >
John Goerzen wrote:
> On Sat, Aug 26, 2006 at 08:43:53AM +0200, Martin Schulze wrote:
> > John Goerzen wrote:
> > > Examples of things that should happen in stable, but haven't been
> > > happening reliably:
> > >
> > > * Kernel updates with more broad hardware support
> >
> > This requires new
On Sat, Aug 26, 2006 at 02:13:33AM -0500, John Goerzen wrote:
> On Sat, Aug 26, 2006 at 08:43:53AM +0200, Martin Schulze wrote:
> > John Goerzen wrote:
> > > Examples of things that should happen in stable, but haven't been
> > > happening reliably:
> > >
> > > * Kernel updates with more broad ha
Martin Schulze schrieb am Samstag, den 26. August 2006:
*snip*
> That's nothing for a *stable* Debian release. However, thanks to
> nobse there is the backports repository which is perfectly suited for
> such an effort. Not sure if anybody bothered to backport Mozilla and
> friends yet, though.
On Sat, Aug 26, 2006 at 08:43:53AM +0200, Martin Schulze wrote:
> John Goerzen wrote:
> > Examples of things that should happen in stable, but haven't been
> > happening reliably:
> >
> > * Kernel updates with more broad hardware support
>
> This requires new kernel packages, new utilities and a
Marc Haber wrote:
> > To start with, [1] says that a package is only uploaded to stable when
> > it meets one of these criteria:
> >
> > * it fixes a truly critical functionality problem
> >
> > * the package becomes uninstallable
> >
> > * a released architecture lacks the package
>
> I wou
John Goerzen wrote:
> Hello,
>
> The Debian stable distribution has been a thorn in our side for a long
> time. We tend to go a long time between releases, which means that
> stable grows less and less useful as time goes on. We also have a
> strict policy on what is allowed into stable.
>
> Th
Il giorno ven, 25/08/2006 alle 16.45 -0500, John Goerzen ha scritto:
> * Updates must undergo testing, ideally with peer review
This could be impossible if stable and testing distributions are
binary-incompatible (ie. using different versions of glibc), just like
sarge and etch are in this moment
On Fri, Aug 25, 2006 at 04:45:31PM -0500, John Goerzen wrote:
> I think it's time we reopen the discussion on what stable means and what
> it should mean.
>
> To start with, [1] says that a package is only uploaded to stable when
> it meets one of these criteria:
>
> * it fixes a truly critical
Hello,
The Debian stable distribution has been a thorn in our side for a long
time. We tend to go a long time between releases, which means that
stable grows less and less useful as time goes on. We also have a
strict policy on what is allowed into stable.
This policy has many merits, especiall
26 matches
Mail list logo
