| Summary: | [PATCH] patch for creating rpm's on x86_64 | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Lee Thompson <bm55b> |
| Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
| Status: | VERIFIED FIXED | ||
| Severity: | enhancement | CC: | carenas, ps.m |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
ebuild.sh patch
use `uname -m` |
||
Created attachment 42459 [details, diff]
ebuild.sh patch
Attempt to fix issue. Could be enhanced for more platforms like ppc, ppc64,
etc
This is surely a feature request for portage devs. Redirecting... Would prefer this to be an $ARCH translation, rather then a specific exemption for amd64 ~= x86_64. Up for it? Created attachment 55566 [details, diff]
use `uname -m`
This one uses uname -m which is more generic.
as the generated SPEC doesn't include "ARCH" hints, rpm will use the main supported architecture to generate the package even if not needed (as on a noarch package which doesn't contain any binaries) which will default to x86_64 on amd64 machines, i386 on x86 machines and so. using `uname -m` as proposed then will let `ebuild rpm` complete correctly on any supported architecture. it is important to stress that the original bug report didn't scope the problem correctly, as it is not specific to x86_64 but to any architecture other than i386 thanks to the hardcoded architecture path and so the subject should be rather "patch for creating rpm's on platforms other than i386" Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;) Reopening for consideration. tracked at https://bugs.launchpad.net/rpm/+bug/634206 This seems to have been fixed for a couple of years now: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=12db02c2d286057968a37159da7e6f651a53de6a Then close the bug please. I'm not very interested in >5 year old already fixed rpm bugs. nor is anyone else. Thanks I can see already RESOLVED FIXED. |
The command ebuild /path/to/ebuild rpm Fails on the x86_64 version of linux due to hard coding of "i386" in ebuild.sh Reproducible: Always Steps to Reproduce: 1.run "ebuild /path/to/ebuild rpm" Actual Results: command created /usr/src/redhat/RPMS/x86_64/<ebuild>.x86_64.rpm successfully command fails to recreate rpm in /usr/portage/rpm due to "i386" coding Expected Results: Created /usr/portage/rpm file