incompatability with modules from -2 version of same package

[Debian Bug Importer]

Automatically imported from Debian bug report #284356 http://bugs.debian.org/284356

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 5 Dec 2004 15:21:17 -0500
From: Joey Hess <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: incompatability with modules from -2 version of same package

--AhhlLboLdkugWU4S
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: kernel-image-2.4.27-1-386
Version: 2.4.27-6
Severity: grave
Tags: d-i

Loading a module from the -2 version of this package when the -6 version
of the kernel is running fails for at least all the ide chipset modules
and for the ide generic module, with many missing symbols:

~ # uname -a =20
Linux donkey 2.4.27-1-386 #1 Wed Dec 1 19:43:08 JST 2004 i686 unknown
~ # modprobe generic
insmod: /lib/modules/2.4.27-1-386/kernel/drivers/ide/ide-core.o: unresolved=
 symbol blk_init_queue_R140d40ee =
         =20
insmod: /lib/modules/2.4.27-1-386/kernel/drivers/ide/ide-core.o: unresolved=
 symbol proc_symlink_R7165fa10 =
         =20
insmod: /lib/modules/2.4.27-1-386/kernel/drivers/ide/ide-core.o: unresolved=
 symbol remove_proc_entry_R0a4291c8 =
         =20
insmod: /lib/modules/2.4.27-1-386/kernel/drivers/ide/ide-core.o: unresolved=
 symbol devfs_mk_dir_R9c2c983a =
         =20
insmod: /lib/modules/2.4.27-1-386/kernel/drivers/ide/ide-core.o: unresolved=
 symbol blk_cleanup_queue_R741c7da6 =
         =20
insmod: /lib/modules/2.4.27-1-386/kernel/drivers/ide/ide-core.o: unresolved=
 symbol add_gendisk_Rf957a44e =
         =20
insmod: /lib/modules/2.4.27-1-386/kernel/drivers/ide/ide-core.o: unresolved=
 symbol end_that_request_first_Rafbe0bbc =20
insmod: /lib/modules/2.4.27-1-386/kernel/drivers/ide/ide-core.o: unresolved=
 symbol devfs_register_blkdev_R7e5f30a4 =
     =20
insmod: /lib/modules/2.4.27-1-386/kernel/drivers/ide/ide-core.o: unresolved=
 symbol blk_queue_bounce_limit_Re74e8980
insmod: /lib/modules/2.4.27-1-386/kernel/drivers/ide/ide-core.o: unresolved=
 symbol mem_map_Rc7a5c379

Since I uploaded udebs for d-i built from this new kernel build, this has
broken netboot installs on i386 using the daily builds, since such a netboot
install boots the -6 kernel, then downloads -2 udebs from testing. It seems
that unless this imcompatability is fixed, we won't be able to update d-i
in testing to use the new kernel without breaking netboot and floppy instal=
ls
using the d-i rc2 images.

This proably also breaks third party modules in debian that are built
against version -2, doesn't it?

I think that this is a bug in this build of the kernel. If the changed
symbols are for some reason unavoidable, the kernel package name should be
changed to kernel-image-2.4.27-1-386. Of course that would suck and leave
us with d-i problems and so I hope you can just fix it..

-- System Information:
Debian Release: 3.1
  APT prefers unstable
 ...

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Sun, 05 Dec 2004 11:43:08 -1000
From: Edwin Lim Aun Whei <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: kernel-image-2.4.27-1-k7: nvidia-kernel-2.4.27-1-k7 is broken

Package: kernel-image-2.4.27-1-k7
Version: 2.4.27-6
Followup-For: Bug #284356

I suppose I'll confirm that this third party kernel package is broken.

biff# uname -a
Linux biff.limnet.pnet 2.4.27-1-k7 #1 Wed Dec 1 20:12:01 JST 2004 i686 GNU/Linux
biff# modprobe nvidia
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: /lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol irq_stat_R180940a9
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: /lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol proc_root_driver_Ra36f876c
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: /lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol devfs_register_chrdev_R703a15c9
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: /lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol devfs_register_Re02370a4
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: /lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol devfs_unregister_R29602a1c
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: /lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol change_page_attr_R04098f96
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: /lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol __pollwait_R87156f10
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: /lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol mem_map_Rdb8be4fa
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: /lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol create_proc_entry_Ra185990c
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: /lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol remove_proc_entry_R4a81d799
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: /lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol init_mm_R6257a2b2
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o:
Hint: You are trying to load a module without a GPL compatible license
      and it has unresolved symbols. The module may be trying to access
      GPLONLY symbols but the problem is more likely to be a coding or
      user error. Contact the module supplier for assistance, only they
      can help you.

/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: insmod /lib/modules/2.4.27-1-k7/nvidia/nvidia.o failed
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: insmod nvidia failed

Cheers,
e.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages kernel-image-2.4.27-1-k7 depends on:
ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
ii fileutils 5.2.1-2 The GNU file management utilities
ii initrd-tools 0.1.74 tools to create initrd image for p
ii modutils 2.4.26-1.1 Linux module utilities

-- no debconf information

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 6 Dec 2004 09:33:54 +0100
From: Christoph Hellwig <email address hidden>
To: Edwin Lim Aun Whei <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: kernel-image-2.4.27-1-k7: nvidia-kernel-2.4.27-1-k7 is broken

On Sun, Dec 05, 2004 at 11:43:08AM -1000, Edwin Lim Aun Whei wrote:
> Package: kernel-image-2.4.27-1-k7
> Version: 2.4.27-6
> Followup-For: Bug #284356
>
>
> I suppose I'll confirm that this third party kernel package is broken.

We don't support propritary modules.

[Debian Bug Importer (debzilla)]

Message-Id: <1102350007.25052.98.camel@thanatos>
Date: Mon, 06 Dec 2004 17:20:08 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Cc: <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>
Subject: New release changed symbols thus rendering modules unloadable

reopen 284356
severity 284356 important
reassign 284356 kernel-image-2.4.27-i386
reassign 284371 kernel-image-2.4.27-i386
severity 284463 important
tags 284463 - pending
reassign 284463 kernel-image-2.4.27-i386
severity 284181 important
tags 284181 - pending
reassign 284181 kernel-image-2.4.27-i386
merge 284356 284371 284463 284181
thanks

Christoph Hellwig wrote:
> We don't support propritary modules.

The original report (#284356) was submitted by Joey Hess and made no
reference to proprietary modules. This affects modules shipped by
Debian too.

The problem is that a new Debian release of the "same" kernel (2.4.27-1)
has changed symbol version suffixes, thus breaking modules that were
compiled against earlier releases of this kernel.

--
Thomas Hood

[Debian Bug Importer (debzilla)]

Message-Id: <20041206162021.4712A10D588@localhost>
Date: Mon, 6 Dec 2004 17:20:21 +0100 (CET)
From: <email address hidden> (Thomas Hood)
To: <email address hidden>
Subject: tagging 284356

tags 284356 - d-i

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 6 Dec 2004 13:16:27 -0500
From: Joey Hess <email address hidden>
To: <email address hidden>
Subject: Re: Bug#284356: New release changed symbols thus rendering modules unloadable

--cNdxnHkX5QqsyA0e
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

This bug is release critical. Please do not downgrade it. (But thanks for
reopening it.)

--=20
see shy jo

--cNdxnHkX5QqsyA0e
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBtKH7d8HHehbQuO8RAnN/AJ4yxYKn3BWEluvbEwVFcXPkjh1avQCguC7T
z0phvr5bvfjRlFadMRJ+NRY=
=+hpN
-----END PGP SIGNATURE-----

--cNdxnHkX5QqsyA0e--

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Mon, 6 Dec 2004 13:15:36 -0500
From: Joey Hess <email address hidden>
To: <email address hidden>
Subject: severity of 284356 is grave

# Automatically generated email from bts, devscripts version 2.8.5
severity 284356 grave

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Mon, 6 Dec 2004 13:16:40 -0500
From: Joey Hess <email address hidden>
To: <email address hidden>
Subject: tagging 284356

# Automatically generated email from bts, devscripts version 2.8.5
tags 284356 d-i

[Debian Bug Importer (debzilla)]

Message-Id: <1102358869.25052.112.camel@thanatos>
Date: Mon, 06 Dec 2004 19:47:50 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: Re: [Pkg-alsa-devel] Bug#284485: failed loading alsa driver

severity 284356 grave
tags 284356 d-i
reassign 284356 kernel-image-2.4.27-i386
merge 284485 284356
thanks

> depmod: *** Unresolved symbols

Kernel bug.

--
Thomas Hood

[Debian Bug Importer (debzilla)]

Message-Id: <1102359543.25052.120.camel@thanatos>
Date: Mon, 06 Dec 2004 19:59:03 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: Re: [Pkg-alsa-devel] Bug#284485: failed loading alsa driver

severity 284485 grave
tags 284485 d-i
reassign 284485 kernel-image-2.4.27-i386
merge 284485 284356
thanks

> depmod: *** Unresolved symbols

Kernel bug.

--
Thomas Hood

[Debian Bug Importer (debzilla)]

Message-Id: <1102359706.25052.124.camel@thanatos>
Date: Mon, 06 Dec 2004 20:01:47 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: merge

severity 284253 grave
reassign 284253 kernel-image-2.4.27-i386
merge 284253 284356
thanks

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Mon, 6 Dec 2004 14:06:23 -0500
From: Joey Hess <email address hidden>
To: <email address hidden>
Subject: reassign 284356 to kernel-image-2.4.27-1-386, merging 284356 284253

# Automatically generated email from bts, devscripts version 2.8.5
reassign 284356 kernel-image-2.4.27-1-386
merge 284356 284253

[Debian Bug Importer (debzilla)]

Message-Id: <1102711776.25052.424.camel@thanatos>
Date: Fri, 10 Dec 2004 21:49:36 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: merge

reassign 284683 kernel-image-2.4.27-1-386
tags 284683 d-i
merge 284683 284485
thanks

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Mon, 13 Dec 2004 11:07:25 -0500
From: Andres Salomon <email address hidden>
To: Horms <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: New release changed symbols thus rendering modules unloadable

On Mon, 13 Dec 2004 21:46:56 +0900, Horms wrote:

[...]
>=20
> Hi,
>=20
> I think that I have discovered the cause of the problem.
>=20
> It seems to be caused by the 093_tty_lockup.diff patch which was applie=
d
> to resolve CAN-2004-081, a security bug relating to race
> conditions in the TTY subsystem. The patch was sourced from
> Jason Baron from Red Hat. I have attached it for reference.
>=20
> In testing I found that the problem lies in the following change
> in include/linux/tty.h
>=20
> -extern struct tty_ldisc ldiscs[];
> +extern struct tty_ldisc tty_ldiscs[];
>=20
> Backing out this change then runing something along the lines of
> make mrproper
> cp some_path/some_config .config
> make oldconfig
> make dep
>=20
> yields the same symbols.
>=20
> (This test was done using the 686-smp config from=20
> kernel-image-i386-2.4.27 -6 and examining the=20
> proc_mkdir symbol which is found in include/linux/modules/root.ver)
>=20
> Of course this does not compile because my change is bogus,
> but I think it does establish the cause of the symbol problem.
>=20
>=20
> I believe that there are serveral different fixes for this problem, and
> in particular the one that was incoporated in 2.6 is somewhat different=
.
> I am not sure if they cause the problem.

As far as 2.6 is concerned, I can successfully compile images against
kernel-source 2.6.8-8 that work with the official kernel-image modules
that are built against 2.6.8-10 (that is, kernel-image 2.6.8-10).=20
However, using the official kernel-image package built against 2.6.8-8
(that is, kernel-image 2.6.8-5) does not work w/ modules built against
2.6.8-10. This leads me to believe that the 2.6 problems are toolchain
related, some change made to sid between Nov 12 and Nov 22, or a change i=
n
the build environment used to create -9 and -10 (joshk, mind doing
some testing?). There was a new module-init-tools package uploaded on No=
v
20; I'll start looking there.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 15 Dec 2004 13:28:50 +0900
From: Horms <email address hidden>
To: Thomas Hood <email address hidden>, <email address hidden>
Cc: <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: New release changed symbols thus rendering modules unloadable

On Mon, Dec 13, 2004 at 09:46:56PM +0900, Horms wrote:
> On Mon, Dec 06, 2004 at 05:20:08PM +0100, Thomas Hood wrote:
> >
> > The original report (#284356) was submitted by Joey Hess and made no
> > reference to proprietary modules. This affects modules shipped by
> > Debian too.
> >
> > The problem is that a new Debian release of the "same" kernel (2.4.27-1)
> > has changed symbol version suffixes, thus breaking modules that were
> > compiled against earlier releases of this kernel.
>
> Hi,
>
> I think that I have discovered the cause of the problem.
>
> It seems to be caused by the 093_tty_lockup.diff patch which was applied
> to resolve CAN-2004-081, a security bug relating to race
> conditions in the TTY subsystem. The patch was sourced from
> Jason Baron from Red Hat. I have attached it for reference.

I regret to report that my previous analysis (which I have snipped but
you can find at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=84356)
appears to be incorrect.

On further analysis I believe that the problem lies in the following
portion of the 093_tty_lockup.diff patch at the bottom of this message.

This adds a refcount element to struct tty_ldisc.
Unforunately struct tty_struct includes a element and in turn
struct task_struct includes a struct tty_struct element,
so this change ends up all over the place.

To make matters worse this field appears to be fundamental to
the fix, which I will reiterate at this point is a security fix
for CAN-2004-081.

I checked 2.6 upstream and the refcount field is present.
Curiously upstream 2.4 seems to neither include this field nor
a fix for CAN-2004-0814 (N.B not CAN-2004-081 as I misquoted above).
If anyone can correct me there I would be most grateful.

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0814

As it stands it seems whe have two choices.

1. Back out the CAN-2004-081 patch.
   This is trivial and would resolve the symbol problem.
2. Bump the SO name
   i.e. kernel-{build,headers,image,pcmcia-modiles}-2.4.27-1*
     -> kernel-{build,headers,image,pcmcia-modiles}-2.4.27-2*
   This is not fun, but is probably my prefered option at this point.

Theroretically we might be able to do 1+2 but it looks painful at best.
We may also be able to find a way to fix CAN-2004-081 and avoid
introducing this symbol problem, but I am skeptical.

--
Horms

--- linux-2.4.27/include/linux/tty_ldisc.h.bak Thu Sep 23 17:43:51 2004
+++ linux-2.4.27/include/linux/tty_ldisc.h Thu Sep 23 17:44:24 2004
@@ -129,6 +129,7 @@ struct tty_ldisc {
           char *fp, int count);
  int (*receive_room)(struct tty_struct *);
  void (*write_wakeup)(struct tty_struct *);
+ int refcount;
 };

 #define TTY_LDISC_MAGIC 0x5403

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 15 Dec 2004 11:04:40 +0000
From: Martin Michlmayr <email address hidden>
To: Horms <email address hidden>
Cc: Thomas Hood <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: New release changed symbols thus rendering modules unloadable

* Horms <email address hidden> [2004-12-15 13:28]:
> I checked 2.6 upstream and the refcount field is present.
> Curiously upstream 2.4 seems to neither include this field nor
> a fix for CAN-2004-0814 (N.B not CAN-2004-081 as I misquoted above).
> If anyone can correct me there I would be most grateful.

Thanks for the analysis. Maybe you could contact upstream and ask why
it hasn't been included and also mention this compatibility problem.
--
Martin Michlmayr
http://www.cyrius.com/

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 15 Dec 2004 12:46:29 +0100
From: Christoph Hellwig <email address hidden>
To: Martin Michlmayr <email address hidden>, <email address hidden>
Cc: Horms <email address hidden>, Thomas Hood <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: New release changed symbols thus rendering modules unloadable

On Wed, Dec 15, 2004 at 11:04:40AM +0000, Martin Michlmayr wrote:
> * Horms <email address hidden> [2004-12-15 13:28]:
> > I checked 2.6 upstream and the refcount field is present.
> > Curiously upstream 2.4 seems to neither include this field nor
> > a fix for CAN-2004-0814 (N.B not CAN-2004-081 as I misquoted above).
> > If anyone can correct me there I would be most grateful.
>
> Thanks for the analysis. Maybe you could contact upstream and ask why
> it hasn't been included and also mention this compatibility problem.

It's not a problem. Linux doesn't gurantee any ABI stability.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 16 Dec 2004 13:35:23 +0900
From: Horms <email address hidden>
To: Thomas Hood <email address hidden>, <email address hidden>
Cc: <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: New release changed symbols thus rendering modules unloadable

On Wed, Dec 15, 2004 at 01:28:50PM +0900, Horms wrote:

<snip>

> As it stands it seems whe have two choices.
>
> 1. Back out the CAN-2004-081 patch.
> This is trivial and would resolve the symbol problem.
> 2. Bump the SO name
> i.e. kernel-{build,headers,image,pcmcia-modiles}-2.4.27-1*
> -> kernel-{build,headers,image,pcmcia-modiles}-2.4.27-2*
> This is not fun, but is probably my prefered option at this point.
>
> Theroretically we might be able to do 1+2 but it looks painful at best.
> We may also be able to find a way to fix CAN-2004-081 and avoid
> introducing this symbol problem, but I am skeptical.

I have built packages that implement each of these plans.

Please take a look if you are interested.
I am still in favour of option 2.

http://debian.vergenet.net/testing/kernel-2.4.27/

--
Horms

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 16 Dec 2004 13:24:28 +0900
From: Horms <email address hidden>
To: Christoph Hellwig <email address hidden>
Cc: Martin Michlmayr <email address hidden>, <email address hidden>, Thomas Hood <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: New release changed symbols thus rendering modules unloadable

On Wed, Dec 15, 2004 at 12:46:29PM +0100, Christoph Hellwig wrote:
> On Wed, Dec 15, 2004 at 11:04:40AM +0000, Martin Michlmayr wrote:
> > * Horms <email address hidden> [2004-12-15 13:28]:
> > > I checked 2.6 upstream and the refcount field is present.
> > > Curiously upstream 2.4 seems to neither include this field nor
> > > a fix for CAN-2004-0814 (N.B not CAN-2004-081 as I misquoted above).
> > > If anyone can correct me there I would be most grateful.
> >
> > Thanks for the analysis. Maybe you could contact upstream and ask why
> > it hasn't been included and also mention this compatibility problem.

I will contact Marcello, but I am not confident of a reply.

> It's not a problem. Linux doesn't gurantee any ABI stability.

Agreed.

--
Horms

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 17 Dec 2004 11:37:23 +0900
From: Horms <email address hidden>
To: Martin Michlmayr <email address hidden>
Cc: Christoph Hellwig <email address hidden>, <email address hidden>, Thomas Hood <email address hidden>,
 <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: New release changed symbols thus rendering modules unloadable

On Thu, Dec 16, 2004 at 01:24:28PM +0900, Horms wrote:
> On Wed, Dec 15, 2004 at 12:46:29PM +0100, Christoph Hellwig wrote:
> > On Wed, Dec 15, 2004 at 11:04:40AM +0000, Martin Michlmayr wrote:
> > > * Horms <email address hidden> [2004-12-15 13:28]:
> > > > I checked 2.6 upstream and the refcount field is present.
> > > > Curiously upstream 2.4 seems to neither include this field nor
> > > > a fix for CAN-2004-0814 (N.B not CAN-2004-081 as I misquoted above).
> > > > If anyone can correct me there I would be most grateful.
> > >
> > > Thanks for the analysis. Maybe you could contact upstream and ask why
> > > it hasn't been included and also mention this compatibility problem.
>
> I will contact Marcello, but I am not confident of a reply.

Hi Martin,

I shouldn't have been so pesemistic. I did indeed get a reply.
Several in fact.

http://lkml.org/lkml/2004/12/15/299

In a nutshell:
  1. This patch wasn't put into 2.4.28 because it was quite
     intrusive and came out to late in the 2.4.28 cycle
  2. It is planed for inclusion (in 2.4.29 I assume)
  3. There are some updates to the patch both available and pending,
     I will make sure we get those, but broadly speaking
     the patch is unchanged. Actually, I notice that one of the
     uptades will most likely introduce a futher ABI change
     by adding "struct semaphore termios_sem;" to strut tty_struct.
     It would be good to get that in if we are going to increment
     the so number.

     http://lkml.org/lkml/2004/11/7/106

--
Horms

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 17 Dec 2004 12:09:08 +0900
From: Horms <email address hidden>
To: Andres Salomon <email address hidden>
Cc: <email address hidden>, <email address hidden>,
 <email address hidden>, <email address hidden>
Subject: Re: SONAME bumping and d-i

On Thu, Dec 16, 2004 at 02:44:43PM -0500, Andres Salomon wrote:
> This is from #debian-boot, regarding bumping the SONAME and reverting the
> CAN-2004-081 patch (see #284356 for details):
>
> <dilinger> joeyh: have you talked to horms about his incrementing of the
> 2.4.27 SONAME stuff yet?
> <joeyh> I haven't. I've seen his mail
> <joeyh> if ya gotta do it, ya gotta do it, but it will of course cause a
> certian amount of d-i pain
> <dilinger> he's trying to decide whether he should revert the patch in -1,
> and make a -2
> <dilinger> well, at this point...
> <dilinger> a) we've already broken the ABI. to revert it will break the
> ABI again, and
> <dilinger> b) if it's a large hassle for d-i to switch kernel package names,
> is it really worth reverting? i assume d-i will want to use the kernel w/
> security patches
> <dilinger> we'll probably have to do the same for 2.6, of course
> <joeyh> oh, so you're talking about us just continuing in with the broken abi
> <dilinger> yes, if we think that's the better solution. at this point, i
> don't know
> <joeyh> it seems to me that either approach will probably end up breaking rc2
> at some point.
> <joeyh> not changing the soname seems more likely to me to break it though
> <dilinger> ok
> <joeyh> if the package name changes, we have to update rootskel and the
> initrds, iirc that should be all
> <dilinger> so you're a fan of bumping the SONAME and reverting for -1, then
> <joeyh> hmm, let me think about it some more
> <joeyh> if we bump the soname, the kernel udebs package names will also change
> <dilinger> ok. i'm going to quote this and post to the (d-k) list, just
> follow up w/ what you decide. horms and i talked about it on irc last night,
> it would be good to get a discussion on the list

Andres, thanks for passing this my way.
Joey, thanks for the indirect feedback,
it is very much appreciated.

My position is that the patch probably should be included.
However it is still pending incusion upstream and from that
I deduce that 1) it is a bit scary and 2) the world doesn't fall
appart if you don't have it. Please see, http://lkml.org/lkml/2004/12/15/299

With that in mind, while I would still like to see the patch
included and thus bumping to -2, I do accept that it may well be
more pain than it is worth. As far as I see there seem to three main
options being discussed at this time, Joey and the d-i team, I am
really looking to you to help decide which way to go.

1. Release a new set of -1 binary packages with the ABI changed reversed
   This means an updated kernel-source-2.4.27 and an updated
   kernel-image-2.4.27-<arch>

2. Release a set of -2 binary packages with the ABI change included
   Again, this means an updated kernel-source-2.4.27 and an updated
   kernel-image-2.4.27-<arch>. I believe that it also means that
   the -1 binary packages will end up being removed from the archive.

3....

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 16 Dec 2004 18:33:31 -0500
From: Joey Hess <email address hidden>
To: <email address hidden>
Subject: Re: SONAME bumping and d-i

--6sX45UoQRIJXqkqR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Looking at how these proposed fixes would affect d-i and existing rc2
images:

a. If the SONAME is left unchanged and the new ABI remains, and things
   are updated to use the new ABI:
    - Installs from a rc2 netinst CD will keep working, but you'll get a
      kernel with the old ABI. Installs of "third-party" (ie, alsa)
      kernel modules that use the new ABI will then fail. Until you
      upgrade your kernel..
    - Installs from a rc2 businesscard CD will be ok.
    - The rc2 netboot and floppy images will stop working once udebs
      built with the new ABI reach sarge.
    - We won't need to make any other changes to d-i aside from putting
      those udebs in sarge and rebuilding the d-i images.
    - However we won't be able to easily/widely test netboot or floppy
      installs using the new ABI kernels until the udebs reach sarge.
      The daily builds would need to be hacked to pull udebs from sid to
      do any significant testing.
b. If the SONAME is increased and the ABI changes reverted for -1:
     - All rc2 images will keep working until/unless the udebs from the -1
       kernels are removed from sarge, when the netboot and floppy images w=
ill
       break.
     - We'll need to build new udebs for the -2 kernels, while keeping
       the udebs from the -1 kernels. This will either mean some ugly
       linux-kernel-di packages that build both from one package, or the
       even more ugly splitting off of a linux-kernel-di-i386-2 for the
       -2 kernels. Nasty nasty nasty.
     - Changes will be needed in debian-cd to drop the -1 stuff from
       CDs to avoid space issues.
     - At the moment I think that d-i/anna will do the right thing WRT
       using the -2 udebs if the -2 kernel is running. However we've
       never been in this situation before, so something could fail.
     - Changes will be needed in rootskel to install the -2 kernel
       images. Some arches may also need base-installer changes.
     - Not sure how this affects "third party" modules in debian, do they
       have to build modules for both kernel SONAMEs? Do they drop -1
       debs? If so rc2 gets subtly broken.
     - Simply increasing the number of udebs in sarge with -2 kernel
       udebs will change d-i's memory usage, which could break 20 mb
       installs. I think we have a big gap before we need to worry about
       32 mb installs. Still we'd need to retest everything for lowmem
       again, or remove the -1 kernel udebs before the next d-i release.

I keep seeming to come up with new issues with approach b. Leaning toward
a..

--=20
see shy jo

--6sX45UoQRIJXqkqR
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBwhtLd8HHehbQuO8RAgQ1AJ9N2UtQVbFl+SrGxub...

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 17 Dec 2004 12:22:25 +0900
From: Horms <email address hidden>
To: Joey Hess <email address hidden>
Cc: <email address hidden>
Subject: Re: SONAME bumping and d-i

Hi Joey,

On Thu, Dec 16, 2004 at 06:33:31PM -0500, Joey Hess wrote:
> Looking at how these proposed fixes would affect d-i and existing rc2
> images:
>
> a. If the SONAME is left unchanged and the new ABI remains, and things
> are updated to use the new ABI:
> - Installs from a rc2 netinst CD will keep working, but you'll get a
> kernel with the old ABI. Installs of "third-party" (ie, alsa)
> kernel modules that use the new ABI will then fail. Until you
> upgrade your kernel..
> - Installs from a rc2 businesscard CD will be ok.
> - The rc2 netboot and floppy images will stop working once udebs
> built with the new ABI reach sarge.
> - We won't need to make any other changes to d-i aside from putting
> those udebs in sarge and rebuilding the d-i images.
> - However we won't be able to easily/widely test netboot or floppy
> installs using the new ABI kernels until the udebs reach sarge.
> The daily builds would need to be hacked to pull udebs from sid to
> do any significant testing.
> b. If the SONAME is increased and the ABI changes reverted for -1:

It is my understading that releasing -2 packages would result
in the -1 packages being removed from the debian archive as
regardless of weather the binary packages are -1, -2, or -X,
the source package is infact kernel-image-2.4.27-<arch>.

Are you proposing that we should add a new source package,
kernel-image-2.4.27-<arch>-2 which produces SONAME=2 binary packages
and leave kernel-image-2.4.27-<arch> providing the SONAME=1 packages.
Or are you suggesting that the -1 binary packages will just hang
around in the archive for a while?

> - All rc2 images will keep working until/unless the udebs from the -1
> kernels are removed from sarge, when the netboot and floppy images will
> break.
> - We'll need to build new udebs for the -2 kernels, while keeping
> the udebs from the -1 kernels. This will either mean some ugly
> linux-kernel-di packages that build both from one package, or the
> even more ugly splitting off of a linux-kernel-di-i386-2 for the
> -2 kernels. Nasty nasty nasty.
> - Changes will be needed in debian-cd to drop the -1 stuff from
> CDs to avoid space issues.
> - At the moment I think that d-i/anna will do the right thing WRT
> using the -2 udebs if the -2 kernel is running. However we've
> never been in this situation before, so something could fail.
> - Changes will be needed in rootskel to install the -2 kernel
> images. Some arches may also need base-installer changes.
> - Not sure how this affects "third party" modules in debian, do they
> have to build modules for both kernel SONAMEs? Do they drop -1
> debs? If so rc2 gets subtly broken.
> - Simply increasing the number of udebs in sarge with -2 kernel
> udebs will change d-i's memory usage, which could break 20 mb
> ...

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Fri, 17 Dec 2004 14:32:13 -0500
From: Andres Salomon <email address hidden>
To: Horms <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: SONAME bumping and d-i

On Fri, 17 Dec 2004 12:22:25 +0900, Horms wrote:
[...]
>=20
> A sounds fine from my point of view, as it involves the least effort.
> Although as I discovered this morning, there seems to be a second ABI
> change relating to the same patch, so we should get that out ASAP.
>=20
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D284356#msg68

Hm, you're referring to the addition of termios_sem (which was already
added to 2.6), or something else?

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 20 Dec 2004 12:23:01 +0900
From: Horms <email address hidden>
To: Andres Salomon <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#284356: SONAME bumping and d-i

On Fri, Dec 17, 2004 at 02:32:13PM -0500, Andres Salomon wrote:
> On Fri, 17 Dec 2004 12:22:25 +0900, Horms wrote:
> [...]
> >
> > A sounds fine from my point of view, as it involves the least effort.
> > Although as I discovered this morning, there seems to be a second ABI
> > change relating to the same patch, so we should get that out ASAP.
> >
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=284356#msg68
>
> Hm, you're referring to the addition of termios_sem (which was already
> added to 2.6), or something else?

Yes, that is the one.

--
Horms

[Debian Bug Importer (debzilla)]

Message-Id: <1103520166.5726.1.camel@localhost>
Date: Mon, 20 Dec 2004 00:22:46 -0500
From: Andres Salomon <email address hidden>
To: Horms <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#284356: SONAME bumping and d-i

--=-SCui1wdIK9i0SWMOf/sD
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2004-12-20 at 12:23 +0900, Horms wrote:
> On Fri, Dec 17, 2004 at 02:32:13PM -0500, Andres Salomon wrote:
> > On Fri, 17 Dec 2004 12:22:25 +0900, Horms wrote:
> > [...]
> > >=20
> > > A sounds fine from my point of view, as it involves the least effort.
> > > Although as I discovered this morning, there seems to be a second ABI
> > > change relating to the same patch, so we should get that out ASAP.
> > >=20
> > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D284356#msg68
> >=20
> > Hm, you're referring to the addition of termios_sem (which was already
> > added to 2.6), or something else?
>=20
> Yes, that is the one.
>=20

Joeyh doesn't seem to care which we do (he said it's the same amount of
effort for him both ways, he just asked that whatever we decide be
consistent for 2.4 and 2.6. So, I'm going to recommend reverting the
tty locking patch and bumping the SONAME. For 2.4, this makes sense
since the kernel w/ the broken ABI hasn't propogated to sarge yet. For
2.6, this is a bit more painful, since the broken ABI is already in
sarge, but.. *shrug*.

--=20
Andres Salomon <email address hidden>

--=-SCui1wdIK9i0SWMOf/sD
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBxmGl78o9R9NraMQRAiniAKCdVXa4ilrL7oS8jB5HBb8az3CzBACgyfEo
x9mp4K7UaEyTiwtMU0qLwt8=
=O5lb
-----END PGP SIGNATURE-----

--=-SCui1wdIK9i0SWMOf/sD--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 20 Dec 2004 15:09:56 +0900
From: Horms <email address hidden>
To: Andres Salomon <email address hidden>
Cc: <email address hidden>
Subject: Incompatable ABI checker

--GvXjxJ+pjyke8COw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Here is a script that I wrote to compare the symbols provided by two
kernel-headers (2.4) packages. It is just rough at this stage but I
plan to put it into my build process to warn of this kind of problem in
the future. Please feel free to use/mangle/update at will.

--
Horms

--GvXjxJ+pjyke8COw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=kernel_symbol_check

#!/bin/bash
######################################################################
# kernel_symbol_check December 2004
# Horms <email address hidden>
#
# kernel_symbol_check
# Check the symbols in two kernel-headers Debian packages and
# repot if they do not match and a diff of the symbols.
# Probably only works with 2.4 kernels
#
# Copyright (C) 2004 Horms
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License as
# published by the Free Software Foundation; either version 2 of the
# License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA
# 02111-1307 USA
######################################################################

NAME="kernel_symbol_check"

set -e

clean ()
{
 rm -rf "$TMP";
}

TMP="$(mktemp -d)"
trap clean EXIT

if [ $# -ne 2 ]; then
 echo "usage $NAME deb1 deb2" 1>&2
 echo " where deb1 and deb2 are the full path to " 1>&2
 echo " (different) 2.4 kernel header packages" 1>&2
 echo 1>&2
 echo " e.g. $NAME \\" 1>&2
 echo " kernel-headers-2.4.27-1-686_2.4.27-2_i386.deb \\" 1>&2
 echo " kernel-headers-2.4.27-1-686_2.4.27-6_i386.deb" 1>&2
 echo 1>&2
 exit 1
fi

PKG1="$1"
PKG2="$2"

PKG1_FILE="${PKG1##*/}"
PKG1_BASE="${PKG1_FILE%%_*}"

PKG2_FILE="${PKG2##*/}"
PKG2_BASE="${PKG2_FILE%%_*}"

rm -rf "$TMP/1/" "$TMP/2/"
mkdir "$TMP/1/" "$TMP/2/"
dpkg -x "$PKG1" "$TMP/1/"
dpkg -x "$PKG2" "$TMP/2/"

find "$TMP/1/usr/src/$PKG1_BASE/include" -name "*.ver" -type f | \
 xargs cat | sort > "$TMP/1.sym"
find "$TMP/2/usr/src/$PKG2_BASE/include" -name "*.ver" -type f | \
 xargs cat | sort > "$TMP/2.sym"

if diff -u "$TMP/1.sym" "$TMP/2.sym"; then
 echo "No Changes"
 STATUS=0
else
 echo '!!!Symbol Changes, as above. Incompatible ABI!!!'
 STATUS=1
fi

exit $STATUS

--GvXjxJ+pjyke8COw--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 20 Dec 2004 15:09:10 +0900
From: Horms <email address hidden>
To: Andres Salomon <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#284356: SONAME bumping and d-i

On Mon, Dec 20, 2004 at 12:22:46AM -0500, Andres Salomon wrote:
> On Mon, 2004-12-20 at 12:23 +0900, Horms wrote:
> > On Fri, Dec 17, 2004 at 02:32:13PM -0500, Andres Salomon wrote:
> > > On Fri, 17 Dec 2004 12:22:25 +0900, Horms wrote:
> > > [...]
> > > >
> > > > A sounds fine from my point of view, as it involves the least effort.
> > > > Although as I discovered this morning, there seems to be a second ABI
> > > > change relating to the same patch, so we should get that out ASAP.
> > > >
> > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=284356#msg68
> > >
> > > Hm, you're referring to the addition of termios_sem (which was already
> > > added to 2.6), or something else?
> >
> > Yes, that is the one.
> >
>
> Joeyh doesn't seem to care which we do (he said it's the same amount of
> effort for him both ways, he just asked that whatever we decide be
> consistent for 2.4 and 2.6. So, I'm going to recommend reverting the
> tty locking patch and bumping the SONAME. For 2.4, this makes sense
> since the kernel w/ the broken ABI hasn't propogated to sarge yet. For
> 2.6, this is a bit more painful, since the broken ABI is already in
> sarge, but.. *shrug*.

Andres and I discussed this on IRC and as the SONAME=2 packages
are produced by the same source package as the SONAME=1 packages
once the SONAME=2 are accepted the SONAME=1 will go away. In
a nutshell this means the update SONAME=1 then upload SONAME=2
approach doesn't help any more than just uploading SONAME=2.
So we have more or less decided to do that for both 2.4 and 2.6
and we are going to work on making that happen.

--
Horms

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 22 Dec 2004 12:00:28 +0900
From: Horms <email address hidden>
To: Soren Hansen <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#286444: kernel-source-2.4.27: Version symbols mismatch with
 kernel-image-2.4.27-1-686-smp

reassign 284356 kernel-source-2.4.27
reassign 284356 kernel-source-2.4.27
reassign 284371 kernel-source-2.4.27
reassign 284463 kernel-source-2.4.27
reassign 284181 kernel-source-2.4.27
merge 286444 284356 284356 284371 284463 284181
tag 286444 +pending
thanks

Thanks,

This is a duplicate of bugs 284356, 284356, 284371, 284463 and 284181.
A fix is on its way in the form of bumbing the SONAME to 2.

--
Horms

[Debian Bug Importer (debzilla)]

Marking as duplicate based on debbugs merge (284181,284356)

This bug has been marked as a duplicate of bug 11368.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 22 Dec 2004 22:39:58 +0900
From: Horms <email address hidden>
To: Andres Salomon <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: SONAME bumping and d-i

Hi,

I have put together the packages that I would like to upload as
kernel-source-2.4.27 2.4.27-7 and kernel-image-2.4.27-i386 2.4.27-7.

This includes increasing the SONAME to 2.
Could anyone who is interesetd please take a look.

http://debian.vergenet.net/pending/

Andreas, let me know when you are ready to go with 2.6.

--
Horms

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 23 Dec 2004 13:28:08 +0100
From: Thiemo Seufer <email address hidden>
To: Horms <email address hidden>, <email address hidden>
Cc: Andres Salomon <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: SONAME bumping and d-i

Horms wrote:
> Hi,
>
> I have put together the packages that I would like to upload as
> kernel-source-2.4.27 2.4.27-7 and kernel-image-2.4.27-i386 2.4.27-7.
>
> This includes increasing the SONAME to 2.
> Could anyone who is interesetd please take a look.

Builds fine on mips.

Thiemo

[Debian Bug Importer (debzilla)]

Message-ID: <20041224004550.GA25207@jale>
Date: Thu, 23 Dec 2004 17:45:50 -0700
From: dann frazier <email address hidden>
To: Horms <email address hidden>, <email address hidden>
Cc: Andres Salomon <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: SONAME bumping and d-i

On Wed, Dec 22, 2004 at 10:39:58PM +0900, Horms wrote:
> Hi,
>
> I have put together the packages that I would like to upload as
> kernel-source-2.4.27 2.4.27-7 and kernel-image-2.4.27-i386 2.4.27-7.
>
> This includes increasing the SONAME to 2.
> Could anyone who is interesetd please take a look.

fyi, I noticed this in my build log:

tar jxf /usr/src/kernel-source-2.4.27.tar.bz2
cd kernel-source-2.4.27; \
        /usr/src/kernel-patches/all/2.4.27/apply/debian 2.4.27-6
tac: /usr/src/kernel-patches/all/2.4.27/debian/series/2.4.27-7: Permission denied
--> 2.4.27-7 fully unapplied.

$ ls -l /usr/src/kernel-patches/all/2.4.27/debian/series/2.4.27-7
-rw------- 1 root root 344 Dec 21 19:39 /usr/src/kernel-patches/all/2.4.27/debian/series/2.4.27-7

Are those perms correct?

[Debian Bug Importer (debzilla)]

Message-ID: <20041224165533.GA11330@jale>
Date: Fri, 24 Dec 2004 09:55:33 -0700
From: dann frazier <email address hidden>
To: Horms <email address hidden>, <email address hidden>
Cc: Andres Salomon <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: SONAME bumping and d-i

On Thu, Dec 23, 2004 at 05:45:50PM -0700, dann frazier wrote:
> $ ls -l /usr/src/kernel-patches/all/2.4.27/debian/series/2.4.27-7
> -rw------- 1 root root 344 Dec 21 19:39 /usr/src/kernel-patches/all/2.4.27/debian/series/2.4.27-7
>
> Are those perms correct?

builds fine on ia64 otherwise

[Debian Bug Importer (debzilla)]

Message-Id: <1103909728.5994.10.camel@localhost>
Date: Fri, 24 Dec 2004 12:35:28 -0500
From: Andres Salomon <email address hidden>
To: Horms <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Bug#284356: SONAME bumping and d-i

--=-uQCRKsVvpHrFJbutmRpq
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2004-12-22 at 22:39 +0900, Horms wrote:
[...]
>=20
> http://debian.vergenet.net/pending/
>=20
> Andreas, let me know when you are ready to go with 2.6.
>=20

Heeeere's Johnny!
http://www.acm.rpi.edu/~dilinger/kernel-image-2.6.8-i386/
http://www.acm.rpi.edu/~dilinger/kernel-image-2.6.9-i386/

--=20
Andres Salomon <email address hidden>

--=-uQCRKsVvpHrFJbutmRpq
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBzFNg78o9R9NraMQRAiUDAKCWV0ganhylVf6beGEfGEfQmBb9OQCgjIVn
P51Ki2IzaO7nBBaqxRZGj2E=
=Tfox
-----END PGP SIGNATURE-----

--=-uQCRKsVvpHrFJbutmRpq--

[Debian Bug Importer (debzilla)]

Message-Id: <20041225144929.8917C10F0C6@localhost>
Date: Sat, 25 Dec 2004 15:49:29 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: merging 287153 284356

# Automatically generated email from bts, devscripts version 2.8.5
merge 287153 284356

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 30 Dec 2004 19:26:43 +0900
From: Horms <email address hidden>
To: Andres Salomon <email address hidden>
Cc: <email address hidden>, <email address hidden>,
 Joshua Kwan <email address hidden>
Subject: Re: Bug#284356: SONAME bumping and d-i

On Wed, Dec 22, 2004 at 10:39:57PM +0900, Horms wrote:
> Hi,
>
> I have put together the packages that I would like to upload as
> kernel-source-2.4.27 2.4.27-7 and kernel-image-2.4.27-i386 2.4.27-7.
>
> This includes increasing the SONAME to 2.
> Could anyone who is interesetd please take a look.
>
> http://debian.vergenet.net/pending/
>
> Andreas, let me know when you are ready to go with 2.6.

I have uploaded these to d.o incorporating a sparc-only
patch that joshk added to the kernel-source package.

Let the rotting in new games begin.

--
Horms

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Thu, 30 Dec 2004 14:03:58 -0500
From: Simon Horman <email address hidden>
To: <email address hidden>
Subject: Bug#284356: fixed in kernel-image-2.4.27-i386 2.4.27-7

Source: kernel-image-2.4.27-i386
Source-Version: 2.4.27-7

We believe that the bug you reported is fixed in the latest version of
kernel-image-2.4.27-i386, which is due to be installed in the Debian FTP archive:

kernel-build-2.4.27-2_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-build-2.4.27-2_2.4.27-7_i386.deb
kernel-headers-2.4.27-2-386_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-386_2.4.27-7_i386.deb
kernel-headers-2.4.27-2-586tsc_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-586tsc_2.4.27-7_i386.deb
kernel-headers-2.4.27-2-686-smp_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-686-smp_2.4.27-7_i386.deb
kernel-headers-2.4.27-2-686_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-686_2.4.27-7_i386.deb
kernel-headers-2.4.27-2-k6_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-k6_2.4.27-7_i386.deb
kernel-headers-2.4.27-2-k7-smp_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-k7-smp_2.4.27-7_i386.deb
kernel-headers-2.4.27-2-k7_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2-k7_2.4.27-7_i386.deb
kernel-headers-2.4.27-2_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-headers-2.4.27-2_2.4.27-7_i386.deb
kernel-image-2.4.27-2-386_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-2-386_2.4.27-7_i386.deb
kernel-image-2.4.27-2-586tsc_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-2-586tsc_2.4.27-7_i386.deb
kernel-image-2.4.27-2-686-smp_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-2-686-smp_2.4.27-7_i386.deb
kernel-image-2.4.27-2-686_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-2-686_2.4.27-7_i386.deb
kernel-image-2.4.27-2-k6_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-2-k6_2.4.27-7_i386.deb
kernel-image-2.4.27-2-k7-smp_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-2-k7-smp_2.4.27-7_i386.deb
kernel-image-2.4.27-2-k7_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-2-k7_2.4.27-7_i386.deb
kernel-image-2.4.27-i386_2.4.27-7.dsc
  to pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-i386_2.4.27-7.dsc
kernel-image-2.4.27-i386_2.4.27-7.tar.gz
  to pool/main/k/kernel-image-2.4.27-i386/kernel-image-2.4.27-i386_2.4.27-7.tar.gz
kernel-pcmcia-modules-2.4.27-2-386_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-pcmcia-modules-2.4.27-2-386_2.4.27-7_i386.deb
kernel-pcmcia-modules-2.4.27-2-586tsc_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4.27-i386/kernel-pcmcia-modules-2.4.27-2-586tsc_2.4.27-7_i386.deb
kernel-pcmcia-modules-2.4.27-2-686-smp_2.4.27-7_i386.deb
  to pool/main/k/kernel-image-2.4...

[Debian Bug Importer (debzilla)]

Message-Id: <1105267578.19133.5.camel@thanatos>
Date: Sun, 09 Jan 2005 11:46:18 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: merge

unmerge 284181
unmerge 284463
unmerge 284485
unmerge 284683
unmerge 287153
merge 284181 284463 284485 284683 287153
reassign 284181 alsa-modules-i386
reopen 284181
tags 284181 - d-i
merge 284181 287483
thanks

--
Thomas Hood <email address hidden>