create_package_descr problem
I'm running /usr/lib/YaST2/bin/create_package_descr on my patched suse 8.1 install tree. It seems to be almost working properly now. One problem -- it somehow does not put a certain important +Prv item in the suse/setup/descr/package file. This causes the installer to complain about a dependency problem. I manually added an entry for suseseach.cgi from the susehelp updated package. Either their was a problem in the susehelp update or there is a problem with the create_package_descr script. eric ##---------------------------------------- =Pkg: susehelp 2002.09.05 28 noarch +Req: susehelp_lang suse_help_viewer htdig recode wget inf2htm fillup fileutils /bin/sh /bin/bash /usr/bin/perl rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Req: +Prq: fillup fileutils /bin/sh rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Prq: +Prv: manhtml susehilf dochost /srv/www/cgi-bin/susesearch.cgi <=========== LINE I had to add -Prv: +Obs: susehilf dochost -Obs: =Grp: Documentation/SuSE =Lic: GPL =Src: susehelp 2002.09.05 28 src =Tim: 1035815749 =Loc: 1 susehelp-2002.09.05-28.noarch.rpm =Siz: 214643 303940
* Eric Whiting <ewhiting@amis.com> [Dec 07. 2002 00:02]:
I'm running /usr/lib/YaST2/bin/create_package_descr on my patched suse 8.1 install tree.
It seems to be almost working properly now.
One problem -- it somehow does not put a certain important +Prv item in the suse/setup/descr/package file. This causes the installer to complain about a dependency problem.
I manually added an entry for suseseach.cgi from the susehelp updated package.
Either their was a problem in the susehelp update or there is a problem with the create_package_descr script.
Some information is missing in /usr/share/autoinstall/EXTRA_PROV Please use the updated file from www.suse.de/~nashif/autoinstall/EXTRA_PROV Thanks for reporting this issue. Anas
eric
##---------------------------------------- =Pkg: susehelp 2002.09.05 28 noarch +Req: susehelp_lang suse_help_viewer htdig recode wget inf2htm fillup fileutils /bin/sh /bin/bash /usr/bin/perl rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Req: +Prq: fillup fileutils /bin/sh rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Prq: +Prv: manhtml susehilf dochost /srv/www/cgi-bin/susesearch.cgi <=========== LINE I had to add -Prv: +Obs: susehilf dochost -Obs: =Grp: Documentation/SuSE =Lic: GPL =Src: susehelp 2002.09.05 28 src =Tim: 1035815749 =Loc: 1 susehelp-2002.09.05-28.noarch.rpm =Siz: 214643 303940
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Anas Nashif wrote:
* Eric Whiting <ewhiting@amis.com> [Dec 07. 2002 00:02]:
I'm running /usr/lib/YaST2/bin/create_package_descr on my patched suse 8.1 install tree.
It seems to be almost working properly now.
One problem -- it somehow does not put a certain important +Prv item in the suse/setup/descr/package file. This causes the installer to complain about a dependency problem.
I manually added an entry for suseseach.cgi from the susehelp updated package.
Either their was a problem in the susehelp update or there is a problem with the create_package_descr script.
Some information is missing in /usr/share/autoinstall/EXTRA_PROV Please use the updated file from www.suse.de/~nashif/autoinstall/EXTRA_PROV
Thanks for reporting this issue.
Anas
Anas, Thanks. I downloaded the updated EXTRA_PROV file. It fixed 2 problems. Yet now I have a similar problem with qt3-devel. It is missing a line in the +Prv: section. I had to manually add /usr/include/png.h to the +Prv: secion in suse/setup/descr/package under the qt3-devel section. Is there a different or better way to do this? Can't the create_package_descr script do a rpm -q --provides -p $rpmfile and use that data instead of the complex binary indexing stuff it is doing? I might be doing something else wrong... eric
Eric Whiting wrote:
Anas,
Thanks. I downloaded the updated EXTRA_PROV file. It fixed 2 problems. Yet now I have a similar problem with qt3-devel. It is missing a line in the +Prv: section.
I had to manually add
/usr/include/png.h
to the +Prv: secion in suse/setup/descr/package under the qt3-devel section.
Is there a different or better way to do this? Can't the create_package_descr script do a
rpm -q --provides -p $rpmfile
and use that data instead of the complex binary indexing stuff it is doing?
I might be doing something else wrong...
Replying to myself -- I was wrong on Two things... oops 1. I was wrong -- rpm -q -l -p $rpmfile works much better.. 2. I was wrong about the section -- I edited the libpng-devel section to make it work. There still must be a different/better way to do this. eric ##---------------------------------------- =Pkg: libpng-devel 1.2.4 31 i586 +Req: libpng /bin/sh rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Req: +Prq: rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Prq: +Prv: <---- ADDED /usr/include/png.h <---- ADDED -Prv: <---- ADDED =Grp: Development/Libraries/C and C++ =Lic: zlib/libpng License =Src: libpng 1.2.4 31 src =Tim: 1031598617 =Loc: 1 libpng-devel-1.2.4-31.i586.rpm =Siz: 183194 453460 ##----------------------------------------
* Eric Whiting <ewhiting@amis.com> [Dec 28. 2002 02:41]:
Eric Whiting wrote:
Anas,
Thanks. I downloaded the updated EXTRA_PROV file. It fixed 2 problems. Yet now I have a similar problem with qt3-devel. It is missing a line in the +Prv: section.
I had to manually add
/usr/include/png.h
to the +Prv: secion in suse/setup/descr/package under the qt3-devel section.
Is there a different or better way to do this? Can't the create_package_descr script do a
rpm -q --provides -p $rpmfile
and use that data instead of the complex binary indexing stuff it is doing?
I might be doing something else wrong...
Replying to myself -- I was wrong on Two things... oops
1. I was wrong -- rpm -q -l -p $rpmfile works much better.. 2. I was wrong about the section -- I edited the libpng-devel section to make it work.
There still must be a different/better way to do this.
Its strange you have problems with files provided by multiple packages. Are you using a predefined selection? Or you have your own package selection? Anas
eric
##---------------------------------------- =Pkg: libpng-devel 1.2.4 31 i586 +Req: libpng /bin/sh rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Req: +Prq: rpmlib(PayloadIsBzip2) <= 3.0.5-1 -Prq: +Prv: <---- ADDED /usr/include/png.h <---- ADDED -Prv: <---- ADDED =Grp: Development/Libraries/C and C++ =Lic: zlib/libpng License =Src: libpng 1.2.4 31 src =Tim: 1031598617 =Loc: 1 libpng-devel-1.2.4-31.i586.rpm =Siz: 183194 453460 ##---------------------------------------- -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
Anas Nashif wrote:
Its strange you have problems with files provided by multiple packages. Are you using a predefined selection? Or you have your own package selection?
I should re-state what I'm doing. I'm trying to create a patched 8.1 nfs install tree for normal installs and autoinstall. When the install finishes I don't want to run YOU. 1. I start with a clean 8.1 nfs install tree 2. I wget the 8.1 suse updates 3. I run a script to copy the updates into the clean nfs install tree 4. I run the create_package_descr script to update the packages file 5. I try a manual nfs network install to verify the install tree. 6. I select Software/Detailed Then I select every possible category (Kde/gnome/network/ldap/etc) If the suse/setup/descr/packages file is correct then the install can proceeed. If the packages file has problems then I get dependency errors. Lately I get dependency problems and I have to manually edit the packages file. Am I doing something really wrong? eric
* Eric Whiting <ewhiting@amis.com> [Dec 30. 2002 19:45]:
Anas Nashif wrote:
Its strange you have problems with files provided by multiple packages. Are you using a predefined selection? Or you have your own package selection?
I should re-state what I'm doing. I'm trying to create a patched 8.1 nfs install tree for normal installs and autoinstall. When the install finishes I don't want to run YOU.
1. I start with a clean 8.1 nfs install tree 2. I wget the 8.1 suse updates 3. I run a script to copy the updates into the clean nfs install tree 4. I run the create_package_descr script to update the packages file 5. I try a manual nfs network install to verify the install tree. 6. I select Software/Detailed Then I select every possible category (Kde/gnome/network/ldap/etc)
If the suse/setup/descr/packages file is correct then the install can proceeed. If the packages file has problems then I get dependency errors. Lately I get dependency problems and I have to manually edit the packages file.
Am I doing something really wrong?
No you are not. There are some dependencies that can't be resolved automatically and have to be solved manually. The change to the package database you have done ist just a work around and not a fix to a problem. In those cases you have to specifically select the files you need, this might resolve the problem Anas
eric
-- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada
participants (2)
-
Anas Nashif -
Eric Whiting