Red Hat Bugzilla – Bug 613399
packagekit-media.repo crashes yum
Last modified: 2014-01-21 18:15:39 EST
Description of problem: latest PK generates a file in /etc/yum.repos.d/ called packagekit-media.repo this files makes yum Version-Release number of selected component (if applicable): yum-3.2.27-4.fc13.noarch PackageKit-0.6.6-1.fc13.x86_64 How reproducible: always Steps to Reproduce: 1. insert F13 DVD 2. wait or open PK software sources 3. make sure you see /etc/yum.repos.d/packagekit-media.repo 4. type yum list '*yumex*' or yum --noplugins list '*yumex*' or any yum query Actual results: Error: Cannot retrieve repository metadata (repomd.xml) for repository: InstallMedia. Please verify its path and try again Expected results: disable that repo or better prompt the user to insert it
This is not a problem in yum, if a enabled repo, can't be populated with metadata, then yum will bail out as expected. I think that the packagekit-media.repo should be disabled by default, and enabled by packagekit when needed.
(In reply to comment #1) > This is not a problem in yum, if a enabled repo, can't be populated with > metadata, then yum will bail out as expected. > > I think that the packagekit-media.repo should be disabled by default, and > enabled by packagekit when needed. That's exactly what we're doing now.
(In reply to comment #2) > That's exactly what we're doing now. For the current session only ?
(In reply to comment #3) > (In reply to comment #2) > > That's exactly what we're doing now. > For the current session only ? Just when PK is using it. See http://cgit.freedesktop.org/packagekit/plain/docs/media-repo.txt
> This is not a problem in yum, if a enabled repo, can't be populated with metadata, then yum will bail out as expected. according to how I understand yum, it (or what is based on it like yum-cli or yumex or yum backend in PK) should either being able to handle media or treat it as disabled even if enabled check this line http://yum.baseurl.org/gitweb?p=yum.git;a=blob;f=yum/yumRepo.py;h=f7257d1c1ccb743fbc2ffb5611596698137387b5;hb=HEAD#l413 if len(self._urls) < 1 and not self.mediaid: raise Errors.RepoError, ...etc. abd this line http://yum.baseurl.org/gitweb?p=yum.git;a=blob;f=yum/yumRepo.py;h=f7257d1c1ccb743fbc2ffb5611596698137387b5;hb=HEAD#l740 if url and scheme != "media": in other words, it's clear that in many places of the code, yum treats media repos differently and fails gracefully while the message comes from http://yum.baseurl.org/gitweb?p=yum.git;a=blob;f=yum/yumRepo.py;h=f7257d1c1ccb743fbc2ffb5611596698137387b5;hb=HEAD#l1336 which seems to mean that although yum handles packages gracefully but not meta data with regard to media repos
patch sent upstream to fix this. tested with this .repo stanza: [mediaid] name = mediaid repo #baseurl=media:///mnt/path/of/doom/ enabled=1 gpgcheck=0 mediaid=133345505.0 metadata_expire=-1 gpgcheck=0
I have searched for it in koji < http://koji.fedoraproject.org/koji/buildinfo?buildID=184084 and it does not seem to have the patch so I got this patch from git http://yum.baseurl.org/gitweb?p=yum.git;a=commit;h=e589f437dcbd1486212d9da2f1bb146c73c45ef2 and built yum http://www.ojuba.org/downloads/updates/testing/4/x86_64/yum-3.2.27-5.oj4.noarch.rpm http://www.ojuba.org/downloads/updates/testing/4/SRPMS/yum-3.2.27-5.oj4.src.rpm and it seems to work perfectly