Bug 926004
| Summary: | Live composes fail when espeak 1.47.03-1.fc19 is in the package set | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> |
| Component: | espeak | Assignee: | Jaroslav Škarvada <jskarvad> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | dennis, jskarvad, kevin, kparal, packaging-team-maint, pbrobinson, robatino, satellitgo |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-24 22:03:52 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Proposing as Alpha blocker for the 'breaks compose' problem, obviously. Not marking as automatic blocker as it's still _possible_ I'm doing something weird somehow, and this won't affect the official builders. (In reply to comment #0) See bug 924660 comment 7. > which seemed instructive. After a bit of trial and error, I came up with > this work of sheer engineering brilliance: > > deps = self.ts.check() > if len(deps) != 0: > for msg in deps: > print(msg) > raise CreatorError("Dependency check failed!") > > and was rewarded with the following perfectly clear error message: > > (('espeak', '1.47.03', '1.fc19'), ('/bin/sh', ''), 0, 0, None) > Please file this (probably against python-imgcreate) as RFE, I think this functionality should be there out of the box. Fixed in espeak-1.47.03-2.fc19 espeak-1.47.03-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/espeak-1.47.03-2.fc18 (In reply to comment #2) > Please file this (probably against python-imgcreate) as RFE, I think this > functionality should be there out of the box. Filed as bug 927304. espeak-1.47.03-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/espeak-1.47.03-4.fc18 Fixed wrt F19, so dropping blocker nomination. espeak-1.47.03-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |
So today all my attempts to compose F19 live images were failing with the cryptic error: "Error creating Live CD : Dependency check failed!" Which doesn't help you fix the problem, much. So I poked about, in my inexpert monkey way, in yuminst.py , and found the code that raises that error is this: deps = self.ts.check() if len(deps) != 0: raise CreatorError("Dependency check failed!") So being an idiotic monkey who codes by invoking Google, I invoked Google on ts.check, and came across: http://lists.baseurl.org/pipermail/yum-devel/2011-February/007861.html which seemed instructive. After a bit of trial and error, I came up with this work of sheer engineering brilliance: deps = self.ts.check() if len(deps) != 0: for msg in deps: print(msg) raise CreatorError("Dependency check failed!") and was rewarded with the following perfectly clear error message: (('espeak', '1.47.03', '1.fc19'), ('/bin/sh', ''), 0, 0, None) So...that's something to do with espeak-1.47.03-1.fc19 and /bin/sh, then. Indeed, espeak-1.47.03-1 introduces a dependency on /bin/sh that the previous build did not have (thanks, autoqa!): http://autoqa.fedoraproject.org/results/541549-autotest/virt06.qa/rpmguard/results/espeak-1.47.03-1.fc2.html but I can't quite see how that torpedoes live CD creation. Lots of other packages depend on /bin/sh - a simple 'rpm -q --whatrequires /bin/sh' shows that. Still, clearly it does, somehow or other. I took espeak-1.47.03-1.fc19 out of the side repo I had it in, and boom, my live composes go through again. But as soon as 1.47.03-1 lands in the repos, presumably, we're going to be in trouble. CCing bcl and the yum maintainers - can anyone figure out this mess? I don't _think_ I'm doing anything silly, but it's always possible, of course.