On Tue, 11 Jan 2005 12:00:37 +0100, Steve Langasek wrote:
> Wouldn't it be
> much better to actually depend on the precise kernel image that the package
> is known to be compatible with, to avoid bugs from users who install them on
> systems running custom kernels and expect them to work? (I think
On Tue, 11 Jan 2005 12:00:37 +0100, Steve Langasek wrote:
> Wouldn't it be
> much better to actually depend on the precise kernel image that the package
> is known to be compatible with, to avoid bugs from users who install them on
> systems running custom kernels and expect them to work? (I think
On Sat, Jan 08, 2005 at 04:23:16PM +0100, Thomas Hood wrote:
> On Sat, 2005-01-08 at 02:44 -0800, Steve Langasek wrote:
> > > To alleviate this problem, I request that alsa-modules-2.4.27-1* be
> > > removed from sarge.
> >
> > Is this an issue with the current version of alsa-modules-2.4.27-1 be
On Sat, Jan 08, 2005 at 04:23:16PM +0100, Thomas Hood wrote:
> On Sat, 2005-01-08 at 02:44 -0800, Steve Langasek wrote:
> > > To alleviate this problem, I request that alsa-modules-2.4.27-1* be
> > > removed from sarge.
> >
> > Is this an issue with the current version of alsa-modules-2.4.27-1 be
On Sat, 2005-01-08 at 02:44 -0800, Steve Langasek wrote:
> > To alleviate this problem, I request that alsa-modules-2.4.27-1* be
> > removed from sarge.
>
> Is this an issue with the current version of alsa-modules-2.4.27-1 being
> broken wrt the original 2.4.27-1 ABI, or is it just an issue of t
On Sat, Jan 08, 2005 at 02:44:10AM -0800, Steve Langasek wrote:
> On Wed, Jan 05, 2005 at 06:41:08AM +0100, Thomas Hood wrote:
> > You may know all of this already but in case you don't ...
> > Because of bug #284356 and the fact that kernel-image-2.4.27-1 packages
> > affected by this bug were al
On Wed, Jan 05, 2005 at 06:41:08AM +0100, Thomas Hood wrote:
> You may know all of this already but in case you don't ...
> Because of bug #284356 and the fact that kernel-image-2.4.27-1 packages
> affected by this bug were allowed into sarge, users of sarge and kernel
> 2.4.27-1 can't load module
You may know all of this already but in case you don't ...
Because of bug #284356 and the fact that kernel-image-2.4.27-1 packages
affected by this bug were allowed into sarge, users of sarge and kernel
2.4.27-1 can't load modules that were built for their kernel prior to
the symbol change. E.g.,
8 matches
Mail list logo
