Trying to exclude kernel-PAE from spin
by Orion Poplawski
Various packages appear to be picking up kernel-PAE for reasons beyond me:
DEBUG:yum.verbose.YumBase:Matched kernel-PAE - 2.6.21-1.3194.fc7.i686 to
require for kernel
DEBUG:yum.verbose.YumBase:Matched kernel-PAE-debug -
2.6.21-1.3194.fc7.i686 to require for kernel
INFO:yum.verbose.pungi:Added kernel-PAE.i686 for vpnc.i386
INFO:yum.verbose.pungi:Added kernel-PAE-debug.i686 for vpnc.i386
DEBUG:yum.verbose.YumBase:Matched kernel-PAE - 2.6.21-1.3194.fc7.i686 to
require for kernel-drm-nouveau
DEBUG:yum.verbose.YumBase:Matched kernel-PAE-debug -
2.6.21-1.3194.fc7.i686 to require for kernel-drm-nouveau
INFO:yum.verbose.pungi:Added kernel-PAE.i686 for xorg-x11-drv-nouveau.i386
INFO:yum.verbose.pungi:Added kernel-PAE-debug.i686 for
xorg-x11-drv-nouveau.i386
DEBUG:yum.verbose.YumBase:Matched kernel-PAE - 2.6.21-1.3194.fc7.i686 to
require for kernel
DEBUG:yum.verbose.YumBase:Matched kernel-PAE-debug -
2.6.21-1.3194.fc7.i686 to require for kernel
INFO:yum.verbose.pungi:Added kernel-PAE.i686 for libraw1394.i386
INFO:yum.verbose.pungi:Added kernel-PAE-debug.i686 for libraw1394.i386
DEBUG:yum.verbose.YumBase:Matched kernel-PAE - 2.6.21-1.3194.fc7.i686 to
require for kernel
DEBUG:yum.verbose.YumBase:Matched kernel-PAE-debug -
2.6.21-1.3194.fc7.i686 to require for kernel
INFO:yum.verbose.pungi:Added kernel-PAE.i686 for fuse.i386
INFO:yum.verbose.pungi:Added kernel-PAE-debug.i686 for fuse.i386
INFO:yum.verbose.pungi:Checking deps of kernel-PAE.i686
INFO:yum.verbose.pungi:Checking deps of kernel-PAE-debug.i686
I ended up excluding them with the following in the manifest:
-kernel-PAE
-kernel-PAE-debug
Now it's pulling in kernel-debug for some reason:
DEBUG:yum.verbose.YumBase:Matched kernel-debug - 2.6.21-1.3194.fc7.i686
to require for kernel
INFO:yum.verbose.pungi:Added kernel-debug.i686 for vpnc.i386
# rpm -q --requires -p
releases/7/Everything/i386/os/Fedora/vpnc-0.4.0-2.fc7.i386.rpm
/bin/sh
/usr/bin/perl
config(vpnc) = 0.4.0-2.fc7
kernel >= 2.4
libc.so.6
libc.so.6(GLIBC_2.0)
libc.so.6(GLIBC_2.1)
libc.so.6(GLIBC_2.1.3)
libc.so.6(GLIBC_2.3.4)
libc.so.6(GLIBC_2.4)
libgcrypt.so.11
libgcrypt.so.11(GCRYPT_1.2)
libgpg-error.so.0
perl(IO::File)
perl(strict)
perl(warnings)
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rtld(GNU_HASH)
why kernel-PAE or kernel-debug rather than just kernel?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
16 years, 10 months
Pungis work directory.
by Joel Andres Granados
I ran pungi once and created a fedora iso. When I ran it again with the
same config file, and forgot to erase the previous work directory
files, pungi shows a traceback telling me that some file already exists.
I have two proposals for this situation.
1. create a timestamp directory inside the working directory for each
pungi run. The problem with this approach is that the use is left with
a bunch of directories that are named after whatever time.time() spit
out (not very pretty). But alas it does away with the ugly traceback
message.
The diff for the first solution:
--- pungi-0.3.0 2007-04-02 23:17:25.000000000 +0200
+++ pungi-0.3.1-JG 2007-04-13 14:27:22.000000000 +0200
@@ -18,6 +18,7 @@
import yum
from ConfigParser import SafeConfigParser
+from time import time
def main():
# Set some default variables, can be overrided in config file
@@ -76,7 +77,8 @@
if not opts.destdir == "*CONFFILE*":
config.set('default', 'destdir', opts.destdir)
-
+ config.set('default', 'destdir',
os.path.join(config.get('default','destdir'),
+ str(int(time()))))
destdir = config.get('default', 'destdir')
if not os.path.exists(destdir):
2. Just tell the user to erase the things he/she has in the directory.
The diff for the second solution:
--- pungi-0.3.0 2007-04-13 15:03:26.000000000 +0200
+++ pungi-0.3.1-JG 2007-04-13 15:02:22.000000000 +0200
@@ -18,6 +18,7 @@
import yum
from ConfigParser import SafeConfigParser
+from os.path import isdir
def main():
# Set some default variables, can be overrided in config file
@@ -77,7 +78,7 @@
if not opts.destdir == "*CONFFILE*":
config.set('default', 'destdir', opts.destdir)
- destdir = config.get('default', 'destdir')
+ destdir = check_destdir(config.get('default', 'destdir'))
if not os.path.exists(destdir):
try:
@@ -180,4 +181,10 @@
manifestfile.close()
return pkglist
+ def check_destdir(workpath):
+ if isdir(workpath) and len(os.listdir(workpath)) > 0:
+ print >> sys.stderr, "Please erase all items from the
directory %s before continuing." % workpath
+ exit(1)
+ return workpath
+
main()
16 years, 10 months
F7 pungi-0.3.5-1.fc7 version == Null
by Phil Meyer
For some reason pungi is setting version to Null.
See this tcpdump:
HTTP GET /mirrorlist?repo=fedora-Null&arch=i386 HTTP/1.1
I have been through the code and config files and cannot spot where its
coming from.
Any ideas?
I have added $releasever=7 to all the yum entries without any change.
I have added version = "7" to the config file with no change.
I have forced version = "7" at the near top of /usr/bin/pungi with no
change.
yum from the command line works like a charm. I have even specified
/etc/yum.conf in my config to no avail.
Puzzler!
Thanks
16 years, 11 months