| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 6 Jan 2011 13:54:12 +0100 From: Michal Marek <mmarek@...e.cz> To: Patrick LeBoutillier <patrick.leboutillier@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH] Bug in scripts/package/mkspec? On Thu, Dec 02, 2010 at 04:15:20PM -0500, Patrick LeBoutillier wrote: > Hi Michal, > > Sorry for the bad patch. Here is basically what I do: > > $ make menuconfig > $ make rpm > ... > Wrote: /root/rpmbuild/RPMS/x86_64/kernel-2.6.36.1-1.x86_64.rpm > ... > $ make menuconfig # tweak some configs > $ make rpm > ... > Wrote: /root/rpmbuild/RPMS/x86_64/kernel-2.6.36.1-1.x86_64.rpm > ... > > > My expectation (and perhaps it is incorrect) is that subsequent "make > rpm"s on the same build tree > yield rpms with increasing release numbers (2.6.36.1-1, 2.6.36.1-2, > ...). Is this how it's supposed > to work? I see the problem now, unfortunatelly I haven't yet found a fix. The problem is that the .version file is updated during build, but rpm needs to know the release number in advance. The fact that there are about four places that deal with the .version file is also not helping :-(. Michal -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists