Description of problem: There are updates-testing but one cannot test them in mock. This decreases the goal of updates-testing. Both for builds verification and QA tests inside mock chroots. Version-Release number of selected component (if applicable): mock-1.1.1-1.fc13.noarch How reproducible: Always. Steps to Reproduce: grep updates-testing /etc/mock/fedora-13-x86_64.cfg Actual results: nothing Expected results: [updates-testing] name=updates-testing mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-testing-f13&arch=x86_64 Additional info: It could be optional, maybe to have /etc/mock/fedora-testing-13-x86_64.cfg ? Still if there is only a single choice I find updates-testing as more appropriate for mock which is used by more technical people suitable for updates-testing.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Still a valid problem in: mock-1.1.10-1.fc14.noarch
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Still a problem in: mock-1.1.26-1.fc18.noarch
(In reply to comment #5) > Still a problem in: mock-1.1.26-1.fc18.noarch I can see us adding an updates-testing stanza to our configs, but can't really see a good way to enable/disable stanza's, other than copying the existing config, editing the yum template and then using the alternate config. Do you have any ideas on how we could do this? Just trying to do a string replace on the yum template doing a s/enable=0/enable=1/ seems fraught with peril.
For example /etc/mock/epel-6-x86_64.cfg already has: [testing] name=epel-testing enabled=0 mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=testing-epel6&arch=x86_64 failovermethod=priority but it is not present in fedora-*.cfg. Just putting such entry there would be good enough IMO. (Unrelated but what is /etc/mock/fedora-5-*-epel.cfg there?) Another possibility is to have new /etc/mock/fedora-17-testing-x86_64.cfg etc. But in such case I would already prefer more some macro-ized/assembled config files from a single template.
I vote in add repo updates-testing with enable=0 on fedora-1x
I'm ok with this. Should they be named [updates-testing] or just [testing]?
/etc/yum.repos.d/fedora-updates-testing.repo: [updates-testing] So it has to be called "updates-testing". Besides that I see now mock already incorrectly calls "updates-released" what regular yum calls as "updates".
And mock *-debug vs. yum *-debuginfo inconsistency.
(In reply to comment #10) > /etc/yum.repos.d/fedora-updates-testing.repo: > [updates-testing] > > So it has to be called "updates-testing". > > Besides that I see now mock already incorrectly calls "updates-released" > what regular yum calls as "updates". totally agree and [updates-testing-debug]
Ok, I'm going to try and clean this up for the 1.1.28 release. Here's what I *think* each yum repo file from a .cfg should have (I just picked the f16 arm file as a sample): [fedora] name=fedora mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-16&arch=arm failovermethod=priority [updates] name=updates mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f16&arch=arm failovermethod=priority [updates-testing] name=updates-testing mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-testing-f16&arch=arm failovermethod=priority [local] name=local baseurl=http://arm.fedoraproject.org/repos/f16-build/latest/arm/ cost=2000 enabled=0 [fedora-debuginfo] name=fedora-debug mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-debug-16&arch=arm failovermethod=priority enabled=0 [updates-debug-debuginfo] name=updates-debug mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-debug-f16&arch=arm failovermethod=priority enabled=0 [updates-testing-debuginfo] name=updates-testing-debuginfo mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-testing-debug-f16&arch=arm enabled=0 Acceptable?
Wups, I think that the updates-testing stanza needs to be off by default. [updates-testing] name=updates-testing mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-testing-f16&arch=arm failovermethod=priority enable=0
And a cut-n-paste error on the updates-debuginfo stanza: [updates-debuginfo] name=updates-debug mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-debug-f16&arch=arm failovermethod=priority enabled=0
And another question: should we go back to the fedorapoject mirrors for the EPEL repos or stay with centos?
talked to Kevin Fenzin on the #epel channel; doesn't seem like we need to do anything on the epel-{5,6} configs right now. As far as the fedora configs go, here's what I have for the fedora-18-x86_64.cfg file (as a representative sample): [fedora] name=fedora mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-18&arch=x86_64 failovermethod=priority [updates] name=updates mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f18&arch=x86_64 failovermethod=priority [updates-testing] name=updates-testing mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-testing-f18&arch=x86_64 failovermethod=priority enabled=0 [local] name=local baseurl=http://kojipkgs.fedoraproject.org/repos/f18-build/latest/x86_64/ cost=2000 enabled=0 [fedora-debuginfo] name=fedora-debug mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-debug-18&arch=x86_64 failovermethod=priority enabled=0 [updates-debuginfo] name=updates-debug mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-debug-f18&arch=x86_64 failovermethod=priority enabled=0 [updates-testing-debuginfo] name=updates-debug mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-testing-debug-f18&arch=x86_64 failovermethod=priority enabled=0
The "name" field does not match the [sectionname] field. [sectionname] is right, "name" is not. After fixing that it looks OK to me, thanks.
strictly speaking "name" is just a display string and is not used in calculating a URL or anything useful. That being said, probably a good idea to make them match up. I'll do that and then push out 1.1.28 for testing.
mock-1.1.28-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.1.28-1.el6
mock-1.1.28-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mock-1.1.28-1.fc18
mock-1.0.36-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/mock-1.0.36-1.el5
mock-1.1.28-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mock-1.1.28-1.fc17
mock-1.1.28-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mock-1.1.28-1.fc16
Package mock-1.1.28-1.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing mock-1.1.28-1.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-13374/mock-1.1.28-1.el6 then log in and leave karma (feedback).
mock-1.1.28-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.1.28-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.0.36-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.