Yes, it was a bad goof up with the replaces line, but hopefully it was a blessing in disguise -- There were some other flaws with that kernel too, so hopefully it stopped people using it.
The original line there was replaces kernel26scsi, Which I didnt remove properly, leaving kernel26. Oops :/ Sorry for the mess up, a new pkg is uploading as I speak, 2/3rds uploaded. It's been fixed and has a few other improvements too. iphitus On 1/18/06, Simo Leone <[EMAIL PROTECTED]> wrote: > On Tue, Jan 17, 2006 at 02:31:54PM -0800, Judd Vinet wrote: > > On Tue, Jan 17, 2006 at 10:18:52PM +0100, Attila wrote: > > > I have [community] in my pacman.conf active and so i recognize at the > last > > > sync with pacman and abs that the new PKBUILD have judd as maintainer > and a > > > replaces line for the currnet kernel26. So my question is will arch > switch to > > > the archck kernel? > > It was an error, I let iphitus know and went and did some preliminary > fixes, like removing the replaces line and fixing the maintainer line. > > > > > No, I don't think so. We try to stick to vanilla if possible, it seems > > to keep things simpler. > > > > The CK kernel shouldn't have to replace kernel26 though, as long as it > > uses different filenames in /boot. The vanilla one uses System.map26, > > kconfig26, and vmlinuz26. If the CK package appended a 'ck' to those > > names, it should get away without any file conflicts. > > > > I did mark it conflicts, however, but Judd you bring up a good point. > Iphitus, if you happen to read this, you can change that conflicts and > just leave the provides on the next release. > > -S > > -- iphitus - ArchCK Maintainer, Arch Trusted User. Home:iphitus.loudas.com _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
