|
Bugzilla – Full Text Bug Listing |
| Summary: | chromium-ffmpeg cannot be installed | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Deleted Name <deleted> |
| Component: | X11 Applications | Assignee: | Forgotten User sM9JzehKpy <forgotten_sM9JzehKpy> |
| Status: | RESOLVED WORKSFORME | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | astieger, forgotten_sM9JzehKpy, wbauer |
| Version: | Leap 42.1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 42.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | 965566 | ||
| Bug Blocks: | |||
|
Description
Deleted Name
2016-02-15 23:07:20 UTC
chromium = 48.0.2564.109 is available. refresh your repositories if required. Now it checks. Thanks! Dear George, This can happen also in the future and there is little that we can do about it. Chromium itself is being build on the openSUSE OBS due to its size and resource requirements. chromium-ffmpeg is build on packman as that it builds an actual full blown ffmpeg library, which has certain patent and legal issues. Given that there are two build environments involved, it can always happen that one is publishing the binaries earlier than the other one. In most cases it would be the openSUSE OBS one that publish the binaries first, but this time it was packman that was first. As you noticed, this normally is resolved within a couple of hours. Raymond Thank you for explaining Raymond! If it happens with a future build I will wait a bit more then :) |