[Bug 282826] security/nss: fix build with net/mpich

2025-02-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282826 --- Comment #9 from Laurent Chardon --- Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 282826] security/nss: fix build with net/mpich

2025-02-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282826 Robert Clausecker changed: What|Removed |Added Resolution|--- |FIXED Status|In Pr

[Bug 282826] security/nss: fix build with net/mpich

2025-02-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282826 Robert Clausecker changed: What|Removed |Added Status|Open|In Progress Assignee

[Bug 282826] security/nss: fix build with net/mpich

2025-02-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282826 Mikhail T. changed: What|Removed |Added CC||freebsd-2024@virtual-estate

[Bug 282826] security/nss: fix build with net/mpich

2025-02-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282826 --- Comment #6 from Robert Clausecker --- (In reply to Kurt Jaeger from comment #5) I don't know what the state of the individual teams is. I previously assumed the same about desktop@, but then got scolded for committing patches against

[Bug 282826] security/nss: fix build with net/mpich

2025-02-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282826 Kurt Jaeger changed: What|Removed |Added Status|New |Open --- Comment #5 from Kurt Jaeger

[Bug 282826] security/nss: fix build with net/mpich

2025-02-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282826 --- Comment #4 from Robert Clausecker --- (In reply to Laurent Chardon from comment #3) Sounds reasonable. However, it's gecko@ that needs to make the decision and I'm not on that team. -- You are receiving this mail because: You are on

[Bug 282826] security/nss: fix build with net/mpich

2025-02-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282826 --- Comment #3 from Laurent Chardon --- (In reply to Robert Clausecker from comment #2) I think that adding a CONFLICTS_BUILD is the wrong way to go, as it prevents something that otherwise is perfectly fine. It's unfortunate that one of t

[Bug 282826] security/nss: fix build with net/mpich

2025-02-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282826 --- Comment #2 from Robert Clausecker --- (In reply to Kurt Jaeger from comment #1) Building without Poudriere is a supported configuration. We can also solve this by adding a CONFLICTS_BUILD on mpich. -- You are receiving this mail bec

[Bug 282826] security/nss: fix build with net/mpich

2025-02-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282826 Kurt Jaeger changed: What|Removed |Added CC||p...@freebsd.org --- Comment #1 from

[Bug 282826] security/nss: fix build with net/mpich

2024-11-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282826 Robert Clausecker changed: What|Removed |Added Assignee|ports-b...@freebsd.org |ge...@freebsd.org

[Bug 282826] security/nss: fix build with net/mpich

2024-11-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282826 Bug ID: 282826 Summary: security/nss: fix build with net/mpich Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: