Bug 734845
Summary: | repoclosure failure in 16-Beta.TC1 DVDs | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andre Robatino <robatino> |
Component: | mozvoikko | Assignee: | Dennis Gilmore <dennis> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | awilliam, jlaska, vpvainio |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | AcceptedBlocker | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-09-09 21:18:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 713564 |
Description
Andre Robatino
2011-08-31 15:29:51 UTC
I thought this was already fixed, the new Firefox and other gecko packages were pushed to F-16 stable a couple of days ago. Discussed at 2011-09-02 blocker review meeting. Accepted as blocker under criterion "There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies during a media-based (DVD) install". This is a bit odd, note - why did the fc15 mozvoikko package turn up on an f16 compose? is this another case of bad inheritance? the f15 update may have been pushed stable before the f16 one, I guess. Ref: https://admin.fedoraproject.org/updates/thunderbird-6.0-1.fc16,xulrunner-6.0-1.fc16,firefox-6.0-1.fc16,mozvoikko-1.9.0-6.fc16 (f16 update) https://admin.fedoraproject.org/updates/perl-Gtk2-MozEmbed-0.09-1.fc15.2,mozvoikko-1.9.0-6.fc15,xulrunner-6.0-2.fc15,firefox-6.0-1.fc15,gnome-python2-extras-2.25.3-33.fc15 (f15 update) Adding AcceptedBlocker whiteboard field in accordance with agreement in comment#2 Dennis, any ideas here? will this be OK for TC2? Adam this should be fine for TC2. its because there had not previously been a f16 build so when the f15 update when to stable it showed up. ive tagged all the inherited builds into f16 i do need to make a mash change but at this point only new packages will show up and not updates. The repoclosure and file conflicts tests pass for 16 Beta TC2. Can this be closed? yes: based on comment #5 and #6, looks fine to close this. |