| 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
| ||
|
Message-ID: <AANLkTin01j5oTUdh6fAgs--Gi46BZOWZCdypUPd8uhm4@mail.gmail.com> Date: Thu, 18 Nov 2010 13:13:24 -0500 From: Patrick LeBoutillier <patrick.leboutillier@...il.com> To: linux-kernel@...r.kernel.org Subject: [PATCH] Bug in scripts/package/mkspec? Hi all, I've been building RPMs for the Linux kernel for a while now and only recently noticed that the RPM Release field is always set to 1. After a bit of searching I found the offending line in scripts/package/mkspec. Here is a patch that worked for me, but perhaps this could be fixed in better way by someone knowledgeable of the kernel build process...: --- ./mkspec.next 2010-11-18 13:08:56.000000000 -0500 +++ mkspec 2010-11-18 13:10:13.000000000 -0500 @@ -29,7 +29,7 @@ echo "Version: $__KERNELRELEASE" # we need to determine the NEXT version number so that uname and # rpm -q will agree -echo "Release: `. $srctree/scripts/mkversion`" +echo "Release: `cd $srctree && ./scripts/mkversion`" echo "License: GPL" echo "Group: System Environment/Kernel" echo "Vendor: The Linux Community" Note: Please cc: me on replies as I'm not subscribed to the list. Thanks, Patrick -- ===================== Patrick LeBoutillier Rosemère, Québec, Canada -- 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