mkinitrd. dep (was: Re: rpms/kernel/F-7 kernel-2.6.spec, 1.3226, 1.3227)

Dave Jones davej at redhat.com
Wed Jun 13 16:02:46 UTC 2007


On Wed, Jun 13, 2007 at 04:29:46PM +0200, Thorsten Leemhuis wrote:
 > Hi!
 > 
 > On 12.06.2007 20:23, Dave Jones (davej) wrote:
 > > Author: davej
 > > 
 > > Update of /cvs/pkgs/rpms/kernel/F-7
 > > In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30425
 > > 
 > > Modified Files:
 > > 	kernel-2.6.spec 
 > > Log Message:
 > > * Tue Jun 12 2007 Dave Jones <davej at redhat.com>
 > > - Require at least version 6.0.9-7.1 of mkinitrd.
 > > [...]
 > > -%define kernel_prereq  fileutils, module-init-tools, initscripts >= 8.11.1-1, mkinitrd >= 6.0.9-1
 > > +%define kernel_prereq  fileutils, module-init-tools, initscripts >= 8.11.1-1, mkinitrd >= 6.0.9-7.1
 > > [...]
 > >  
 > >  %changelog
 > > +* Tue Jun 12 2007 Dave Jones <davej at redhat.com>
 > > +- Require at least version 6.0.9-7.1 of 	
 > > +
 > 
 > Dave, could you do me a small favor and in situations like this (and
 > more important: in the devel tree) please mention why a new mkinitrd is
 > needed (if possible without much hassle)? tia!
 > 
 > It's not that important, but would be nice to know now and then --
 > especially in situations I often run into: downloaded a new kernel on
 > machine foo, put it on a USB stick, go with it to computer bar, try to
 > install it with rpm directly because the old kernel has no network
 > support for that machine and fail because I need a new mkinitrd... if I
 > knew that a new mkinitrd is just needed for some obscure bug I then
 > might just use "--nodeps" instead of going back to machine foo to
 > download the the new mkinitrd .

It was in the changelog, which was also in the announcement.
Where else should I put it ?

	Dave

-- 
http://www.codemonkey.org.uk




More information about the Fedora-kernel-list mailing list