Mike McIntyre <mikemci@xxxxxxxxxx> writes: > Our yum repository is located on a SUSE Linux Enterprise Server 10 (i586) > patchlevel 2 server using Novell Subscription Management Tool (SMT) > to download the updated rpms. create repo from Novell is > createrepo-0.4.6-39.5 with command executed createrepo > /suserpm/srv/www/htdocs/repo. > > Repository of rpms > /suserpm/srv/www/htdocs/repo/$RCE # find . -name '*audiofile*'|grep x86_64 > ./SLES10-SP2-Updates/sles-10-x86_64/rpm/x86_64/audiofile-0.2.6-17.2_17.6.x86_64.delta.rpm > ./SLES10-SP2-Updates/sles-10-x86_64/rpm/x86_64/audiofile-0.2.6-17.6.x86_64.rpm > ./SLES10-SP2-Updates/sles-10-x86_64/repodata/patch-slesp2-audiofile-5948.xml Right, this isn't going to work because createrepo is going to see the .delta.rpm file and think it's an rpm (and it acts enough like one that this "works"). > The yum files on the client SUSE Linux Enterprise Server 10 (x86_64) > Patchlevel 2 are from [...] > yum-3.2.20-2.1 [...] > Please let me know how I can resolve this problem. Do I need yum-presto > installed on the client or is this a way I can turn off using the delta > rpm files? You have two easy-ish options: 1. [easy] Pass --excludes='*.delta.rpm' to createrepo. The repo will work but the clients won't get delta packages. 2. Update createrepo (and likely yum), remove all the .delta.rpm files, and run createrepo with the --deltas --oldpackagedirs options. Createrepo will now generate .drpm files in drpms/ relative to the basedir. ... and if the yum-presto plugin is installed, the plugin will apply these deltas for yum (if the plugin isn't installed, the repo will still work as well as in #1). ...doing #2 so that you don't have to regenerate the deltas is likely possible, but will require more work (likely you'll need to generate the deltainfo.xml file yourself). -- James Antill -- james@xxxxxxx _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum
