Bug 1300437 - Update spec file to build with new packaging tools
Update spec file to build with new packaging tools
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: krb5 (Show other bugs)
6.8
All Linux
urgent Severity low
: rc
: ---
Assigned To: Robbie Harwood
BaseOS QE Security Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-20 15:01 EST by Robbie Harwood
Modified: 2016-08-01 14:14 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-08-01 14:14:30 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Robbie Harwood 2016-01-20 15:01:11 EST
Upon upgrading to f23, the rhel6 version of the krb5 spec file will no longer build.  That is to say,

[rharwood@thriss krb5.rhel]$ cat /etc/fedora-release 
Fedora release 23 (Twenty Three)
[rharwood@thriss krb5.rhel]$ rhpkg prep
error getting product information for rhel-6.8, assuming it's unreleased
error: line 731: Trigger fired by the same package is already defined in spec file: %post workstation

Could not execute prep: Command 'rpmbuild --define '_sourcedir /home/rharwood/krb5.rhel' --define '_specdir /home/rharwood/krb5.rhel' --define '_builddir /home/rharwood/krb5.rhel' --define '_srcrpmdir /home/rharwood/krb5.rhel' --define '_rpmdir /home/rharwood/krb5.rhel' --define 'dist .el6' --define 'rhel 6' --define 'el6 1' --nodeps -bp /home/rharwood/krb5.rhel/krb5.spec' returned non-zero exit status 1
[rharwood@thriss krb5.rhel]$ 

Next time this package gets touched, this will need to be fixed in order for me to use it.  I've been working on fc22, but that won't be sustainable going forward.
Comment 1 Robbie Harwood 2016-08-01 14:14:30 EDT
(Already fixed this because a CVE needed to be fixed earlier; forgot to close.)

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