Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1064988 - rpmbuild some macros misbehave - _rpmdir always mangled
Summary: rpmbuild some macros misbehave - _rpmdir always mangled
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rpm
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Packaging Maintenance Team
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-13 16:32 UTC by lejeczek
Modified: 2014-02-14 12:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-14 06:16:48 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description lejeczek 2014-02-13 16:32:45 UTC
Description of problem:

rpm --eval %_rpmdir
evaluates to whateverMy/path
yet!! rpmbuild forces extra arch at the end, I end up with whateverMy/path/x86_64
is it hard-coded? why?

Version-Release number of selected component (if applicable):

rpm-build-4.8.0-37.el6.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Panu Matilainen 2014-02-14 06:16:48 UTC
%_rpmdir is the "base" directory for produced binaries, %_build_name_format controls the other half. 

Please keep in mind bugzilla is a bug tracker, not a support forum.

Comment 3 lejeczek 2014-02-14 12:12:30 UTC
to keep a part of this path there? a bit confusing, no?

what would be great to have, I would encourage you developers to think of, is a coherency between the resulted output rpm-tree and what yum expects.
Simply to have data-tree in a form which when made into you repository would work straight away, by defaults, no macro tweaking no fiddling.

many thanks


Note You need to log in before you can comment on or make changes to this bug.