| Summary: | Fedora 9 update repositories not usable in Anaconda | ||
|---|---|---|---|
| Product: | Infrastructure | Reporter: | John Beranek <john> |
| Component: | General | Assignee: | Thorsten Leemhuis <fedora> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | lxtnow, matthias |
| Priority: | P5 | ||
| Version: | NA | ||
| Hardware: | All | ||
| OS: | GNU/Linux | ||
| namespace: | |||
| Attachments: |
Anaconda error in Fedora 9 kickstart
Anaconda error in Fedora 9 kickstart - repository config |
||
|
Description
John Beranek
2009-04-09 12:48:48 CEST
Clicking 'Edit' shows that it is trying to add the 'rpmfusion-free-updates' repository of ours, which is at the following location on our mirror server: /sites/download1.rpmfusion.org/free/fedora/updates/9/i386/ we had to disable the comps.xml creation for F9 and F10 temporary due to https://bugzilla.rpmfusion.org/show_bug.cgi?id=496 I guess that's the reason for your problems (albeit I would have assumed it works for F10 if the Everything repo is enabled). Anyway, hopefully above bug can be fixed soon (In reply to comment #2) > we had to disable the comps.xml creation for F9 and F10 temporary due to > https://bugzilla.rpmfusion.org/show_bug.cgi?id=496 > > I guess that's the reason for your problems (albeit I would have assumed it > works for F10 if the Everything repo is enabled). > > Anyway, hopefully above bug can be fixed soon OK, thanks for verifying the problem - I'll just hang on tight for the fix. While I'm here, is it expected that you can't added the Fedora 9 rpmfusion _release_ repositories into a kickstart configuration? A while ago this stopped working, so I was forced to disable the empty release repo's. (In reply to comment #3) > (In reply to comment #2) > > we had to disable the comps.xml creation for F9 and F10 temporary due to > > https://bugzilla.rpmfusion.org/show_bug.cgi?id=496 applied a different workaround which should fix this bug but might hurt those with proxys a bit... > While I'm here, is it expected that you can't added the Fedora 9 rpmfusion > _release_ repositories into a kickstart configuration? A while ago this stopped > working, so I was forced to disable the empty release repo's. Not sure, but I guess it should work -- I need a more detailed description to know what's wrong. But note, those repos are empty anyway so there is no real point in adding them. Hmm, that doesn't fix our kickstart here. It still produces the same error when it comes to adding the 'free-updates' and 'nonfree-updates' repositories. Our mirror of download1.rpmfusion.org _does_ have comps.xml and comps.xml.gz though... /me confused But whatever. I applied the real createrepo fix half an hour ago and new repodata for the updates-testing repos is uploading right now; if no problems show up over the next 24 hours I'll recreate the repodata for the main repos, Then this problem hopefully vanishes... Made subject more explicit OK, thanks - I mid-air-collisioned changing the subject ;) Does it work now? (Note that another repo push is in progress right now) (In reply to comment #9) > Does it work now? (Note that another repo push is in progress right now) > Unfortunately not - still failing with the same error. I've ensured our repository was synced up too. Turned on debug logging in Anaconda, but couldn't find any more information in the logs to help diagnose the problem. :( (In reply to comment #10) > > Unfortunately not - still failing with the same error. I've ensured our > repository was synced up too. > > Turned on debug logging in Anaconda, but couldn't find any more information in > the logs to help diagnose the problem. :( Odd. Just to get things straight: can you please post the error message once more and show how you enabled RPM Fusion in the kickstart file? (In reply to comment #11) > (In reply to comment #10) > > > > Unfortunately not - still failing with the same error. I've ensured our > > repository was synced up too. > > > > Turned on debug logging in Anaconda, but couldn't find any more information in > > the logs to help diagnose the problem. :( > > Odd. Just to get things straight: can you please post the error message once > more and show how you enabled RPM Fusion in the kickstart file? > OK, I'll attach 2 screenshots. The anaconda config is shown below, note how I've disabled the release repositories, as I've said they don't work when enabled and are unnecessary anyway. ## base #repo --name=rpmfusion-free --baseurl=http://mirror.office.example.com/sites/do wnload1.rpmfusion.org/free/fedora/releases/9/Everything/i386/os/ #repo --name=rpmfusion-nonfree --baseurl=http://mirror.office.example.com/sites /download1.rpmfusion.org/nonfree/fedora/releases/9/Everything/i386/os/ ## updates repo --name=rpmfusion-free-updates --baseurl=http://mirror.office.example.com/sites/download1.rpmfusion.org/free/fedora/updates/9/i386/ repo --name=rpmfusion-nonfree-updates --baseurl=http://mirror.office.example.com/sites/download1.rpmfusion.org/nonfree/fedora/updates/9/i386/ Apologies for the line-wrapping. Created attachment 160 [details]
Anaconda error in Fedora 9 kickstart
Created attachment 161 [details]
Anaconda error in Fedora 9 kickstart - repository config
does it work right now? I ran into more problems with the latest createrepo and went back to a old one for F9 and F10; I guess that might fix this bug as well, but I have no easy way to test (In reply to comment #15) > does it work right now? I ran into more problems with the latest createrepo and > went back to a old one for F9 and F10; I guess that might fix this bug as well, > but I have no easy way to test > Sorry, for the delay - I'd implemented a workaround (rpm -ivh on the release RPMs in the %post section) so I wasn't feeling the pain. Just did a clean kickstart with the repositories added and it's got through to installing packages. Excellent, many thanks. After your latest update on https://bugzilla.redhat.com/show_bug.cgi?id=494951 I guess you've moved to the updated 'createrepo'...and that's made this problem come back. :( I've gone back to my workaround. (In reply to comment #17) > I guess you've moved to the updated 'createrepo'...and that's made this problem > come back. :( Can you give it one more try please? I think I've found and worked around the last problem (yet one more yum fix I had to import as it is not yet in rawhide) (In reply to comment #18) > (In reply to comment #17) > > I guess you've moved to the updated 'createrepo'...and that's made this problem > > come back. :( > > Can you give it one more try please? I think I've found and worked around the > last problem (yet one more yum fix I had to import as it is not yet in rawhide) > Working again for me too - thanks! |