On Wed, 15 Jun 2005 04:35:39 -0400 Robert Kerr <rrkrr@xxxxxxxxxxx> wrote:
snip...although this worked okay with fedora core 3, it fails with core 4:
issuing:
[root@localhost ~]# up2date --get-source kernel
*****************
Anyone know what this means?
It means you should look at the release notes...
"Fedora Core 4 does not include the kernel-source package provided by older versions. Instead, configured sources are available as described in Section 6.2.2.2, ___Kernel Flavors___. Users that require access to Fedora Core original kernel sources can find them in the kernel .src.rpm package. To create an exploded source tree from this file, perform the following steps:"
http://fedora.redhat.com/docs/release-notes/fc4/errata/#sn-kernel
Regards,
Jim H
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : https://www.redhat.com/archives/fedora-list/attachments/20050615/d5fb4e5d/attachment.bin
From the very next Section (6.2.2.3) of the Release notes:
1.
Obtain the kernel-/<version>/.src.rpm file from one of the
following sources:*
The SRPMS directory on the appropriate /SRPMS/ CD iso image.
*
The FTP site where you got the kernel package.
*
By running the following command:
*up2date /--get-source/ kernel*
I'm just noting that the latter method doesn't seem to work for me, and results in cryptic error messages in the up2date log.
Could this have something to do with the unsigned (GPG) files that up2date finds when updating files that are already installed?
Robert Kerr
