Bug 803763 - since 5.6 imposible to use buildinstall or pkgorder
Summary: since 5.6 imposible to use buildinstall or pkgorder
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda
Version: 5.6
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-15 15:35 UTC by emmanuel.borlet
Modified: 2015-08-18 19:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-19 02:44:48 UTC
Target Upstream Version:


Attachments (Terms of Use)
patches anaconda to fix issue (950 bytes, patch)
2015-08-18 19:16 UTC, Chris
no flags Details | Diff

Description emmanuel.borlet 2012-03-15 15:35:17 UTC
hello

Description of problem:

since 5.6 imposible to use buildinstall or pkgorder

  
Actual results:

--- pkgorder
Traceback (most recent call last):
File "/usr/lib/anaconda-runtime/pkgorder", line 32, in ?
from yuminstall import YumSorter
File "/usr/lib/anaconda/yuminstall.py", line 32, in ?
from packages import recreateInitrd
File "/usr/lib/anaconda/packages.py", line 27, in ?
import fsset
File "/usr/lib/anaconda/fsset.py", line 35, in ?
import bootyutil


i have a fix, but attention i'm not a python programmer !

download the rpm source

# curl -O http://vault.centos.org/5.8/updates/SRPMS/anaconda-11.1.2.250-1.el5.centos.3.src.rpm


install the SRPM
rpm -i anaconda-11.1.2.250-1.el5.centos.3.src.rpm


unpack the anaconda-11.1.2.250.tar.bz2 (on the SOURCES folder of your build arch mine is /usr/src/redhat/SOURCES)

on the file 
bootloader.py

replace 

import booty

by
import sys
sys.path.append("/usr/lib/booty")
import booty


on the file 
fsset.py

replace 

import booty

by
sys.path.append("/usr/lib/booty")
import booty


change the
Release: 1.el5.centos.4

on the file (it was Release: 1.el5.centos.3)
/usr/src/redhat/SPECS/anaconda.spec


then repack and re-install
# rm anaconda-11.1.2.250.tar.bz2
# tar cpvjf anaconda-11.1.2.250.tar.bz2 anaconda-11.1.2.250
# rpmbuild -ba /usr/src/redhat/SPECS/anaconda.spec
# rpm -e anaconda anaconda-runtime
# rpm -ivh /usr/src/redhat/RPMS/i386/anaconda-11.1.2.250-1.el5.centos.4.i386.rpm
# rpm -ivh /usr/src/redhat/RPMS/i386/anaconda-runtime-11.1.2.250-1.el5.centos.4.i386.rpm


Copy the rpm in the path of you buildinstall command look for

Then buildinstall, the pkgorder in the build process, AND in the install stage succed

I didn't know if the
import sys
has a consequence

Comment 1 Chris Lumens 2012-03-19 02:44:48 UTC
This is fixed in the next major release of RHEL.  If you require a fix in a RHEL 5 update release, please talk with your support representative who will raise it through the appropriate channels for scheduling.  Thanks.

Comment 2 emmanuel.borlet 2012-03-19 08:03:14 UTC
You mean RHEL 5.9 ? or RHEL 6.3 ?

Comment 3 emmanuel.borlet 2013-03-20 10:39:46 UTC
strictly Ze same on 5.9…

rpm -qa | grep  -e anaconda -e booty
booty-0.80.6-10
busybox-anaconda-1.2.0-14.el5.centos
anaconda-11.1.2.259-1
anaconda-runtime-11.1.2.259-1

Comment 4 Chris 2015-08-18 19:16:20 UTC
Created attachment 1064426 [details]
patches anaconda to fix issue

Issue still exists, but this patch solves the problem. I can't take credit for it.  I found it on the CentOS forums; but it works great and solves the problem.

Without it, this issue is still present in RH511 too.


Note You need to log in before you can comment on or make changes to this bug.