query: mock + libselinux-mock.so LD_PRELOAD... why?
by Michael E Brown
I need a little bit of help understanding what the
'libselinux-mock.so' LD_PRELOAD was supposed to be doing. I released and
pushed out mock-0.8 without this. I have rebuilt most of rawhide with
this new mock version and have not seen anything that I directly can say
was a failure due to this being missing, so I am sort of not seeing the
point.
I have searched around as much as I can to try to understand why
this was put into place. From what I can understand, it was only put in
in the FC2 timeframe to fix some problems with the selinux policy on the
host machine. These *appear* to have been fixed in the host selinux
policy, so again, i dont see a reason to keep this around.
Jesse mentioned on IRC, though, that this might be needed, so I pose
this question. I've a local branch set up with the 0.8.x code and the
LD_PRELOAD put back in. So, I can quickly spin a new release with this
back in if it is actually needed. So far, I havent convinced myself it
is needed, though...
Could somebody please enlighten me?
--
Michael
16 years, 3 months
F8 rawhide, error from method.py during kickstart install from cdrom
by Martin Steinmann
F8 RAWHIDE updated. I get the following error from anaconda doing a kickstart install from cdrom:
File "/usr/lib/python2.5/site-packages/pykickstart/commands/method.py", line 81, in parse
(opts, extra) = op.parse_args(args=args)
AttributeError: 'NoneType' object has no attribute 'parse_args'
install exited abnormally [1/1]
This happens right after anaconda started the X server.
The kickstart file used looks fairly straight forward. Could this be a known error?
thanks
--martin
ks.cfg:
#--- Installation method (install, no upgrade) and source (CD-ROM)
install
cdrom
#--- Debugging (uncomment next line to debug in the interactive mode)
#interactive
#--- Language and input support
lang en_US.UTF-8
##langsupport --default=en_US.UTF-8 en_US.UTF-8
keyboard us
##mouse generic3ps/2
#--- X-Windows (use "skipx" directive to skip X-Windows configuration)
skipx
#--- Network configuration
# Add some default or else Anaconda will pop a window and ask
network --device eth0 --bootproto static --ip 192.168.1.176 --netmask 255.255.255.0 --gateway 192.168.1.1 --nameserver 192.168.1.145 --hostname sipx.example.com
#--- Authentication and security
rootpw setup
firewall --disabled
selinux --disabled
authconfig --enableshadow --enablemd5
#--- Time zone
timezone America/New_York
#--- Boot loader
bootloader --location=mbr
#--- Partitioning
#--- NON_RAID Disk partitioning (LVM)
zerombr yes
clearpart --all --initlabel
part /boot --fstype ext3 --size=128
part swap --size=1024
part /recovery --fstype ext3 --size=1024
part / --fstype ext3 --size=4096
part /var --fstype ext3 --size 1 --grow
#--- Reboot the host after installation is done
reboot
#--- Package selection
%packages --resolvedeps
e2fsprogs
<snip>
16 years, 4 months
Mock 0.8.x available
by Michael E Brown
Mock users,
I have posted a new version of mock for review and comments.
RPM download: http://linux.dell.com/libsmbios/download/mock/mock-0.8.1/
Git repository: http://linux.dell.com/git/mock-v2.git
Compatibility:
-- Mock 0.8.x+ has been written on Fedora 7 and is intended for use
on Fedora 7 and higher. A limited amount of testing has been done on
FC6, so please report any FC6-specific bugs and we will make
best-effort attempts to fix them.
-- I have tried to maintain a high degree of compatibility with mock
0.7 in cmdline args and
New stuff:
-- plugin system to better modularize things
-- new plugins:
-- Yum cache
-- root cache
-- ccache
-- bind mount
-- root cache (formerly called autocache) is now significantly
smaller in size
-- speed increases: mock 0.8 is now in almost every case minutes
faster than 0.7, especially for multiple builds.
-- uses python logging.py module for increased logging flexibility
-- new command: 'mock install PACKAGE' to run a 'yum install
PACKAGE' inside the buildroot
-- expanded command: 'mock installdeps RPM_FILE' can now install
deps for a local binary RPM. Formerlly, only SRPMS were
supported.
-- new option: "--cleanup-after" that can be used with
"--resultdir". This will do a cleanup of the buildroot after the
build. This is enabled by default such that any '--resultdir'
builds will be automatically cleaned up
-- All of the config files delivered with mock have been tested and
should work. (The test case compiles mock using each of the
config files delivered with mock.)
Changed:
-- cmdline requires "rebuild" argument when rebuilding srpms.
Previously you could just pass srpm name.
-- output has slightly changed. Mock is now slightly more verbose.
-- formerly /dev from the host was bind-mounted into the chroot.
This is now not enabled by default, but can be configured easily
per-chroot using the bind plugin. See the 'defaults.cfg' files
for config details.
-- '-r CONFIG' option can no longer accept full config filenames
("config.cfg"). Leave off the '.cfg' for mock 0.8+. Formerly,
config ('-r' option) could be specified using either
"config.cfg" or
"config" and mock would look for /etc/mock/config.cfg,
automatically
adding the '.cfg', if necessary.
-- logs are not overwritten or truncated for --no-clean or
--resultdir builds.
-- cmdline options removed:
--autocache, --rebuild-cache: use "--enable-plugin" or
"--disable-plugin" instead
--verbose, --debug, --quiet: the log files contain all the
information. --verbose could possibly return.
--statedir: statedir didnt have much point in life and has gone
away
Config files:
-- Old config files will, by and large, still work. There are
several options in the old config files that are no longer
applicable now that 'mock-helper' has went away. The next
release of mock should have warnings enabled if it sees that
your config file has obsolete options.
Internal Changes:
-- now modularized
-- mock-helper is gone. Instead there is a setuid-wrapper that calls
mock.py. This vastly simplifies development.
Plugin Notes:
-- the plugin system is somewhat rudimentary at this time. If this
becomes something that is truly useful for out-of-tree plugins or
third-parties, we can formalize the interface some more. As of now,
the plugin interface should have most of the hooks to do useful
stuff, but some other things like the 'conduit' interface that yum
uses for plugins is not present. This would formalize the interface
a bit more and make sure the plugins dont grope too badly into
internals they shouldnt.
Future plans:
-- Upstream mock git will be updated to this version next week after
we sort out branching for the 0.7 release.
-- This version of mock will be checked into Fedora 9 next week.
-- yum integration: plan to try to use the yum API rather than the
cmdline. this will enable several optimizations and speed ups
due to not redownloading the yum metadata multiple times.
-- config file format change: at some future point, we probably will
switch to an .ini format config file.
SPECIAL SECURITY WARNING:
1) default /usr/bin/mock owner is root:mock with permissions 4550
(-rwsrwx---). Thus, it may only be run by the 'root' user or members of
the 'mock' group. DO NOT PUT UNTRUSTED USERS IN THE 'MOCK' GROUP! The
current code (as well as all previous versions) has many easily-used
mechanisms that an untrusted user could use to elevate their local
privileges. IT IS NOT THE GOAL OF THE MOCK DEVELOPERS TO MAKE MOCK A
TOOL THAT CAN BE USED BY UNTRUSTED LOCAL USERS.
2) All 'rpmbuild' commands, as well as the 'rpm' command to install and
unpack the to-be-built SRPM are run as the user running 'mock' with no
elevated privileges. These 'rpm' and 'rpmbuild' commands are run in the
chroot environment with these lower privileges. Thus, it should be
relatively safe to use mock to compile code from untrusted sources. That
being said, MOCK HAS NOT BEEN THOROUGHLY AUDITED TO GUARANTEE THE SAFETY
OF THIS.
--
Michael
16 years, 5 months
RFC - Patch - koji SCM generalization
by Rob Myers
attached is a patch that attempts to generalize checking out the
components used to build an SRPM. this patch supports CVS, GIT, and
SVN, but only CVS and SVN have been tested. the idea is to provide the
infrastructure for different SCM systems to be configured at run-time so
that users can choose their favorite system.
is there a better approach? did i miss something obvious? general
comments?
thanks.
rob.
16 years, 5 months
Makefile.common patch to remove deprecated mock syntax
by Michael E Brown
Attached is a small patch against makefile.common to remove use of
deprecated mock syntax. This will work with both old mock (0.7.x) and
new mock (0.8.x).
-- dont specify '.cfg' in mock config
-- specify 'rebuild' cmdline arg
Tested by doing a 'make mockbuild' of mock.
--
Michael
16 years, 5 months
pungi problem
by Sergio Monteiro Basto
Hi,
pungi is chipping 2 kdepim without any apparent reason
can someone explain why ?
thanks
INFO:yum.verbose.pungi:Checking deps of kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.6-4.fc7.i386 to require
for libkcal_groupwise.so.1
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libkcal_groupwise.so.1
INFO:yum.verbose.pungi:Added kdepim.i386 for kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.6-4.fc7.i386 to require
for libkpilot.so.0
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libkpilot.so.0
INFO:yum.verbose.pungi:Added kdepim.i386 for kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.6-4.fc7.i386 to require
for libkcal_resourceremote.so.1
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libkcal_resourceremote.so.1
INFO:yum.verbose.pungi:Added kdepim.i386 for kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.6-4.fc7.i386 to require
for libkabc_slox.so.0
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libkabc_slox.so.0
INFO:yum.verbose.pungi:Added kdepim.i386 for kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.6-4.fc7.i386 to require
for libkgantt.so.0
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libkgantt.so.0
INFO:yum.verbose.pungi:Added kdepim.i386 for kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.6-4.fc7.i386 to require
for libkode.so.1
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libkode.so.1
INFO:yum.verbose.pungi:Added kdepim.i386 for kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.6-4.fc7.i386 to require
for libknotes_xmlrpc.so.1
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libknotes_xmlrpc.so.1
INFO:yum.verbose.pungi:Added kdepim.i386 for kdepim-devel.i386
DEBUG:yum.verbose.YumBase:Matched kdepim - 6:3.5.7-3.fc7.i386 to require
for libkitchensync.so.0
16 years, 5 months
Koji SPEC
by Oscar Bacho
Hi List
I have one question.
where define $PYDIR of file koji-1.2/hunb/Makefile?
thanks
16 years, 5 months
cvs-1.11.22-12.fc8 rebuild in mock
by Jiri Moskovcak
I tried to rebuild this package in mock without any problems. According
to log it seems that it failed because of missing "krb5-devel" package,
but this is in BuildRequires, so I don't think it's the fault of wrong
spec file.
jirka
16 years, 5 months
Minimal system created with Pungi
by Martin Steinmann
I am trying to create a minimal system of F8 rawhide with pungi, where
anaconda runs in graphics mode (with the X server) during installation,
but the installed system does not have an X server.
I am using a pungi config file like the one below. It turns out that the
packages for the X server have to be included so that they can be used
during stage2 of the install. However, they also end up in the RPM
repository on the CD. Is there a way to avoid this?
--martin
%packages --nobase
kernel
xorg-x11-fonts-ISO8859-1-75dpi
busybox-anaconda
dejavu-lgc-fonts
memtest86+
xorg-x11-drivers
selinux-policy-targeted
selinux-policy-mls
anaconda-runtime
man
nano
grub
openssh-server
dhclient
rpcbind
sendmail
vixie-cron
sudo
rootfiles
16 years, 6 months
no initrd generated with custom kernel
by Sean Langford
Hello,
I'm using pungi to spin a custom distribution with some installation
automations using the anaconda kickstart mechanism. This mailing list
has been invaluable to accomplish what I have thusfar.
However, I have a need to include a patched fedora kernel. I've
followed the guide here:
http://fedoraproject.org/wiki/Docs/CustomKernel
and included the resulting kernel rpm in the build manifest and in my
local repo, tagged with my own invented distro tag;. Pungi correctly
packages and then anaconda installs and boots this kernel but pungi does
not seem to include an initrd. The logs seem to indicate that it
created one:
>From pungi log:
> Found keymap override, using it
> No i586 kernel, trying i686...
> unpacking
> /opt/build/work/analyzer-os/src/uos/output/7/Everything/i386/os/g4k/kernel-2.6.22.9-3268.il8.i686.rpm.i686
> Building initrd.img
> Wrote /tmp/makebootdisk.initrdimage.19125 (3528k compressed)
> Building isolinux directory
however anaconda does not seem to be installing it. Its not clear to me
how the pungi-anaconda-kernel-initrd relationship is all mapped out.
Can anyone point me in the right direction?
Thanks
Sean
16 years, 6 months