Bug 377051
| Summary: | Miro-0.9.9.9-1.fc8 rpm requires firefox 2.0.0.9 (which does not exist in fedora 8 repo) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jack Deslippe <jdeslip> |
| Component: | Miro | Assignee: | Alex Lancaster <alex> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 8 | CC: | alex, luis |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Miro-0.9.9.9-1.fc8 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-11-16 06:36:03 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: | |||
|
Description
Jack Deslippe
2007-11-12 04:24:45 UTC
Yes, it's a mess, basically firefox's fault. A new Miro was rebuilt against the new firefox and pushed to make sure the update for firefox 2.0.0.9 worked out of the box (i.e. that Miro would also smoothly update). Unfortunately the firefox maintainers decided to pull the firefox update at the last moment and didn't also keep back the updated dependencies that were rebuilt for it (like Miro). Of course this all happened the day after F-8 was released, and then came the weekend, and no pushes seem to happen on the weekend because only one person can actually do the push. To make matters worse, on F-8 the firefox update *was* pushed but the Miro update wasn't. Basically, firefox updates really screw up the system and the firefox maintainers don't really communicate exactly what is going to happen or co-ordinate with downstream package managers properly. So apologies for that but I can't do anything about it until new updates are pushed. Meantime, the best I can suggest is simply disable the updates repo for when installing Miro from the update until the new firefox is pushed (hopefully Monday), e.g.: yum --disablerepo=updates install Miro and then: yum --exclude=Miro updates for subsequent updates. Hopefully this will all be sorted out soon. Bug confirmed. pts/0 root@hammer:~# yum update Loading "protectbase" plugin Loading "protect-packages" plugin Loading "changelog" plugin Loading "fastestmirror" plugin Loading mirror speeds from cached hostfile 0 packages excluded due to repository protections Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package Miro.x86_64 0:0.9.9.9-1.fc8 set to be updated --> Processing Dependency: gecko-libs = 1.8.1.9 for package: Miro --> Finished Dependency Resolution Error: Missing Dependency: gecko-libs = 1.8.1.9 is needed by package Miro Isn't this exactly what updates-testing is supposed to prevent? (In reply to comment #3) > Isn't this exactly what updates-testing is supposed to prevent? It is usually, but firefox is normally pushed direct to stable (because they are security updates) and therefore the deps have to be pushed to stable ASAP as well, to avoid breakage. However, in this particular case, the firefox update was pulled at the last second, but the dependent packages weren't mainly because the firefox maintainers didn't keep track of the dependent packages and hold them back from going to stable too. I was finally able to update Miro today so this particular bug can be closed. However I will next open another bug due to some crap with DBus and Python hating each other. Thanks for fixing the dependency issue. Yep, thanks for the resolution of this bug/ |