Bug 193575 - [exp-run] Include gssapi_krb5 in base Kerberos
Summary: [exp-run] Include gssapi_krb5 in base Kerberos
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Ports Framework (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Port Management Team
URL:
Keywords:
Depends on:
Blocks: 156245
  Show dependency treegraph
 
Reported: 2014-09-12 00:26 UTC by Glen Barber
Modified: 2014-09-12 15:52 UTC (History)
0 users

See Also:
gjb: exp-run?


Attachments
head/crypto/heimdal/tools/krb5-config.in@r271284 diff (505 bytes, patch)
2014-09-12 00:26 UTC, Glen Barber
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Glen Barber freebsd_committer freebsd_triage 2014-09-12 00:26:55 UTC
Created attachment 147229 [details]
head/crypto/heimdal/tools/krb5-config.in@r271284 diff

I am likely being overly paranoid here, but request an exp-run against a change to stable/10 that is pending MFC for inclusion in the 10.1-RELEASE.

The original PR, 156245, suggests that certain ports would build properly prior to this change, but then would exhibit runtime failure due to the missing linkage.

I'm uncertain if this exp-run is necessary, since without the change, the affected ports would properly build, however so close to the 10.1-RELEASE am being cautious.
Comment 1 Antoine Brodin freebsd_committer freebsd_triage 2014-09-12 08:47:36 UTC
There was no new failure due to this commit when it was committed in head
(I did a comparison between  http://gohan2.ysv.freebsd.org/build.html?mastername=head-amd64-default-baseline&build=p367609_s271241  with  http://gohan2.ysv.freebsd.org/build.html?mastername=head-amd64-default-baseline&build=p367791_s271338 )
I can still do an exp-run if you want,  it will take 2 or 3 few days as we do not have a stable/10 baseline
Comment 2 Glen Barber freebsd_committer freebsd_triage 2014-09-12 15:52:12 UTC
No, if it did not cause build failures in head, then I am even less concerned than before.

Thank you for the followup.