Bug 77592
| Summary: | cannot use JBJ test RPM rpm-4.1-9.i386.rpm | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Raw Hide | Reporter: | R P Herrold <herrold> |
| Component: | rpm | Assignee: | Jeff Johnson <jbj> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2002-11-16 14:39:13 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
R P Herrold
2002-11-09 22:42:51 UTC
subtext might be: JBJ rpm-4.1-10.src.rpm test candidate requested as JBJ
rpm-4.1-9.src.rpm is not yielding any new information that I can see from
Bugzilla reports ...
Another instance of being unable to build the JBJ test candidate on a 7.2
chassis -- this time my host: router/basement -- rpm-4.1-9.src.rpm
I am having up2date issues on this unit as well, and just filed ticket 77975
-- tried building the JBJ rpm-4.1-9 test candidate -- had to comment out the
python-devel BuildDependency; the box is that python, python2-devel/python2
wierd mix transition mixture; added libelf package, and am still missing the
apidocs build toolchain cruft
really frustrating after 1.5 hr rpm build, trying to revive a wounded host to
rule out rpm database issues on the up2date Attribute error. ....
Please consider issuing a -2 on the test candidate, with:
1. the 'release correct' elf buildrequire
2. a conditional rpm-devel build if the toolchain is not all present.
3. a python-devel / python2-devel variant present buildrequire
...
+ cp -pr apidocs /var/tmp/rpm-root/usr/share/doc/rpm-devel-4.1
cp: cannot stat `apidocs': No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.8878 (%doc)
PreReq: /sbin/ldconfig /sbin/ldconfig
<snip[>
Requires: libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1.3)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.8878 (%doc)
[root@router dl]#
---------------
-- RPH
FWIW, -9 is to fix a missed SIGCHLD, dunno "release candidate" even now. the segfault will not happen if you are using packages produced by rpm-4.1, which checks signatures/digests whenever a header is read. W/o a signature/digest, only a sanity check is possible, and that is not perfect. 1) take out the build require, it was necessary only for a transition (0.8.2 adds gelf API) within the 8.0 release. 2) presumably you want rpm configure to just deal with what's installed. that leads to packages w/o apidocs if doxygen happens not to be installed, not good. there's switch(s) to disable apidocs/perl if/when necessary 3) there are so much variant python/python2 packaging that it's hard to insure the right thing happens for all cases. I've chosen to fail immediatley, rather than discover rpm is miscompiled later. there's switches in the spec file to set the python path. FWIW, I'm not at all sure that python bindings are fully functional if not python > 2.0, current bindings use new fangled 2.x features. Ditto with up2date, there's enough subtle churn that you're probably best off getting over your transition, rather than trying to figger up2date needs. |