#22220 closed defect (wontfix)
rpm-devel failing on patch step
Reported by: | carlo.cabanilla@… | Owned by: | afb@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.8.1 |
Keywords: | Cc: | n3npq@… | |
Port: | rpm-devel |
Description
rpm-devel is failing on the patch step
Error: Target org.macports.patch returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutils_rpm-devel/work/rpm-5.3.SNAPSHOT.20090630" && /usr/bin/patch -p0 < '/opt/local/var/macports/sources/rsync.macports.org/release/ports/sysutils/rpm-devel/files/patch-macros.in'" returned error 1 Command output: patching file macros.in Reversed (or previously applied) patch detected! Assume -R? [n] Apply anyway? [n] Skipping patch. 11 out of 11 hunks ignored -- saving rejects to file macros.in.rej Error: Status 1 encountered during processing.
Attachments (2)
Change History (8)
Changed 15 years ago by carlo.cabanilla@…
Attachment: | macros.in.rej added |
---|
comment:1 Changed 15 years ago by jmroot (Joshua Root)
Cc: | n3npq@… added |
---|---|
Owner: | changed from macports-tickets@… to afb@… |
Port: | rpm-devel added |
comment:2 Changed 15 years ago by carlo.cabanilla@…
I've attached a patch that works, but now it's failing on the configure step:
configure: error: unable to find internal JavaScript library
I think it means SpiderMonkey, but when I port install SpiderMonkey, it still fails. Not sure how to proceed.
comment:3 Changed 15 years ago by afb@…
I'm thinking that the easiest way would be to delete the outdated "rpm-devel" port.
If you want to follow RPM development, it would be better to use CVS and devtool...
cd rpm . devtool.bashrc devtool checkout devtool autogen
comment:4 Changed 15 years ago by afb@…
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Removed port in r59884.
comment:5 follow-up: 6 Changed 15 years ago by carlo.cabanilla@…
The only reason I want the rpm is for the rpmbuild binary. Is there any way to just build that without having to satisfy the dependencies for the other stuff?
comment:6 Changed 15 years ago by afb@…
Replying to carlo.cabanilla@…:
The only reason I want the rpm is for the rpmbuild binary.
rpmbuild is included in any of the regular rpm ports, since ports include both runtime and developer files.
You would need to install all requirements though, if you don't want that you can use the RPM5 package.
patch rejects