Re: 2.6.14.5 to 2.6.15 patch

[Alistair John Strachan]

On Thursday 05 January 2006 00:08, H. Peter Anvin wrote:
> Alistair John Strachan wrote:
> > Re-read the thread. The confusion here is about "going back" to 2.6.14
> > before patching 2.6.15. This has nothing to do with "rc kernels". We have
> > this documented explicitly in the kernel but not on the kernel.org FAQ.
>
> If you can send me some suggested verbiage I'll put it in the FAQ.  We
> can also make a page that's directly linked from the "stable release",
> kind of like we have info links for -mm patches etc.

I hope somebody else here can minimise my logic; I think the verbosity is 
necessary to completely explain the "patch nightmare" to everybody concerned.

I'm getting warnings about "Reversed (or previously applied) patch detected!" 
when I attempt to patch to an -rc, -mm or -stable kernel. How should this be 
done?

*Terms*

A Linus mainline "release" kernel is given an x.y.z version number (e.g. 
2.6.14). A -stable kernel is given an x.y.z.a version number (e.g., 
2.6.14.3).

*Patching*

New -stable or -rc patches are to be applied to Linus's mainline "release" 
kernels, not -stable, -rc or -mm kernel versions.

New -mm patches are to be applied either to the "release" kernel, or the 
applicable -rc kernel (whichever is newer), which are given an x.y.z-rcN 
version number (e.g. 2.6.15-rc2).

-	If you are on a -stable kernel, you need to revert the -stable patch before
	applying either an -rc, a new -stable, or new Linus "release" patch.

-	If you are on an -rc kernel, you need to revert the -rc patch if you want to
	apply another -rc patch, a -stable patch, or a new Linus "release" patch.

-	If you are on an -mm kernel, you need to revert the -mm patch and the -rc
	patch (if applicable), before applying either an -rc, -stable or new Linus 
	"release" patch.

*Patch Process*

For example, to patch to 2.6.14-rc3-mm3, when you were previously on 2.6.13.4, 
you would need to:

-	Download the full Linux 2.6.13 "release" tarball, or reverse the 2.6.13.4
	-stable patch.

	tar jxvf linux-2.6.13.tar.bz2				OR
	bzip2 -cd ../patch-2.6.13.4.bz2 | patch -Rp1	(whilst in linux directory).

-	Apply the 2.6.14-rc3 patch.

	bzip2 -cd ../patch-2.6.14-rc3.bz2 | patch -Np1 (whilst in linux directory).

-	Apply the 2.6.14-rc3-mm3 patch.

	bzip2 -cd ../2.6.14-rc3-mm3.bz2 | patch -Np1 (whilst in linux directory).

Most users will be confused by running a -stable kernel, and not being able to 
patch to the latest Linus "release" kernel. If you are on 2.6.13.4, and you 
want to go to 2.6.14, all you need to do is:

-	Download the full Linux 2.6.14 "release" tarball. Done.

	tar jxvf linux-2.6.14.tar.bz2

-	OR, Reverse the 2.6.13.4 patch from your existing tree. This will return you
	to Linus "release" 2.6.13.

	bzip2 -cd ../patch-2.6.13.4.bz2 | patch -Rp1 (whilst in linux directory).

-	Apply the 2.6.14 patch.

	bzip2 -cd ../patch-2.6.14.bz2 | patch -Np1 (whilst in linux directory).

Alternatively, if the above is too much for you, check out Matt Mackall's 
ketchup utility. This will automate the above process.

http://www.selenic.com/ketchup/


.. Okay, after writing that maybe Greg was correct. This will easily become 
the largest FAQ entry, even if it is a complete description of the issue at 
hand.

-- 
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/