Bug 476992
| Summary: | Custom F10 spins leads to revisor crash due to F10-buildinstall | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jean Visagie <jean.visagie> | ||||||
| Component: | revisor | Assignee: | Jeroen van Meeuwen <vanmeeuwen+fedora> | ||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 10 | CC: | jonathansteffan, vanmeeuwen+fedora | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i386 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-04-15 07:34:08 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Jean Visagie
2008-12-18 15:09:11 UTC
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Please run: yum -d9 -c /path/to/modified/conf list Where /path/to/modified/conf is the path to the modified YUM configuration file probably somewhere in /etc/revisor/conf.d/ Created attachment 338314 [details]
Modified buildinstall
script failed because of missing buildinstall function import. Also removed repo command line option because it is not used in rest of script, or stuff broke (can't remember which)
I actually made custom distro using just buildinstall, but I had to modify the buildinstall in the 'anaconda-11.4.1.62-1.i386' package. Please find it attached. Sorry, this new buildinstall doesn't work for Revisor.
If you're looking to change something, it'll probably be in this section:
==
UPD_INSTROOT=./upd-instroot
MK_IMAGES=./mk-images
MK_TREEINFO=./maketreeinfo.py
MK_STAMP=./makestamp.py
BUILDINSTALL=./buildinstall
BUILDINSTALL_FUNCTIONS=./buildinstall.functions
for f in $UPD_INSTROOT $MK_IMAGES $MK_STAMP $MK_TREEINFO $BUILDINSTALL $BUILDINSTALL_FUNCTIONS; do
if [ -n "$UPDATES" -a -f $UPDATES/usr/lib/anaconda-runtime/$f ]; then
cp -a $UPDATES/usr/lib/anaconda-runtime/$f* $BUILDINSTDIR/
elif [ ! -f $f ]; then
cp -a $BUILDINSTDIR/usr/lib/anaconda-runtime/$f* $BUILDINSTDIR/
else
cp -a $f* $BUILDINSTDIR/
fi
done
UPD_INSTROOT=$BUILDINSTDIR/upd-instroot
MK_IMAGES=$BUILDINSTDIR/mk-images
MK_TREEINFO=$BUILDINSTDIR/maketreeinfo.py
MK_STAMP=$BUILDINSTDIR/makestamp.py
BUILDINSTALL=$BUILDINSTDIR/buildinstall
==
Also, please attach the changes you made using diff or something, not the entire file.
Here are the diffs 76c76 < if [ -z "$REPO" ]; then --- > #if [ -z "$REPO" ]; then 78,80c78,80 < else < EXTRA_REPOS="$EXTRA_REPOS $1" < fi --- > #else > # EXTRA_REPOS="$EXTRA_REPOS $1" > #fi 179a180 > BUILDINSTALL_FUNCTIONS=./buildinstall.functions 181c182 < for f in $UPD_INSTROOT $MK_IMAGES $MK_STAMP $MK_TREEINFO $BUILDINSTALL; do --- > for f in $UPD_INSTROOT $MK_IMAGES $MK_STAMP $MK_TREEINFO $BUILDINSTALL $BUILDINSTALL_FUNCTIONS; do Is buildinstall used at all for anaconda image creation? Or are the anaconda images created by hand? buildinstall and buildinstall.functions are essential to the anaconda image creation process. |