Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 160629 - Razor 2.71 fails to build
Summary: Razor 2.71 fails to build
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Razor-Agent
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Warren Togami
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-06-16 07:38 UTC by Warren Togami
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-06-16 20:57:49 UTC
Type: ---


Attachments (Terms of Use)
lazy patch (357 bytes, patch)
2005-06-16 12:55 UTC, Michael Schwendt
no flags Details | Diff

Description Warren Togami 2005-06-16 07:38:24 UTC
Installing /var/tmp/perl-Razor-Agent-2.71-1-root-builder/usr/bin/razor-client
Writing
/usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi/auto/razor-agents/.packlist
Appending installation info to
/var/tmp/perl-Razor-Agent-2.71-1-root-builder/usr/lib/perl5/5.8.6/i386-linux-thread-multi/perllocal.pod
/usr/bin/razor-client
make: /usr/bin/razor-client: Command not found
make: *** [install_razor_agents] Error 127
error: Bad exit status from /var/tmp/rpm-tmp.53724 (%install)

I am stretched way too thin right now.  Would really appreciate help here
because this is an important security release.

http://razor.sourceforge.net/
razor-agents-2.71

Comment 1 Michael Schwendt 2005-06-16 12:55:48 UTC
Created attachment 115536 [details]
lazy patch

Quick'n'lazy patch would be this. [For a long-term solution, somebody might
want to investigate how to run razor-client inside the buildroot, so it can
create the symlinks there.]

Comment 2 Warren Togami 2005-06-16 20:57:49 UTC
thanks


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