Bug 265984 - [exp-run] identify IPPROTO_DIVERT use in ports
Summary: [exp-run] identify IPPROTO_DIVERT use in ports
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Ports Framework (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Gleb Smirnoff
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-22 01:13 UTC by Gleb Smirnoff
Modified: 2022-10-04 15:39 UTC (History)
1 user (show)

See Also:
antoine: exp-run+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gleb Smirnoff freebsd_committer freebsd_triage 2022-08-22 01:13:25 UTC
In the test system please remove IPPROTO_DIVERT definition from /usr/include/netinet/in.h This needs to be done after world, cause world won't build without the definition.

Please check if any ports fail to build due to lack of IPPROTO_DIVERT. Thanks!
Comment 2 Gleb Smirnoff freebsd_committer freebsd_triage 2022-08-31 04:47:45 UTC
Thanks a lot Antoine!

In a couple weeks I'd need this run to be repeated. What is preferred: keep this bug open or close it and later open a new one?
Comment 3 Antoine Brodin freebsd_committer freebsd_triage 2022-08-31 07:18:44 UTC
(In reply to Gleb Smirnoff from comment #2)
it can be the same bug
Comment 4 Gleb Smirnoff freebsd_committer freebsd_triage 2022-09-28 15:24:17 UTC
Hi! With all the identified ports patched, can you please do this exp-run again with the fresh main ports branch?
Comment 6 Gleb Smirnoff freebsd_committer freebsd_triage 2022-09-30 17:11:08 UTC
My bad, I didn't specify that the test needs to be done on fresh CURRENT. May I ask to fix that and repeat once again?
Comment 7 Antoine Brodin freebsd_committer freebsd_triage 2022-10-04 08:16:16 UTC
Exp-run looks fine
Comment 8 Gleb Smirnoff freebsd_committer freebsd_triage 2022-10-04 15:39:06 UTC
Thanks a lot!