[MacPorts] #63274: notmuch: build conflict declared against itself, forcing users to deactivate before updating
MacPorts
noreply at macports.org
Wed Jul 21 20:10:47 UTC 2021
#63274: notmuch: build conflict declared against itself, forcing users to
deactivate before updating
---------------------+-----------------------
Reporter: mascguy | Owner: rseichter
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: | Port: notmuch
---------------------+-----------------------
When attempting to update this port today, it failed with the following:
{{{
---> Configuring notmuch
Error: notmuch cannot be built while another version of notmuch is active.
Error: Please forcibly deactivate the existing copy of notmuch, e.g. by
running:
Error:
Error: sudo port -f deactivate notmuch
Error:
Error: Then try again.
Error: Failed to configure notmuch: notmuch is active
}}}
Reviewing the portfile, the following is declared for `conflicts_build`:
{{{
conflicts_build ${name} xcbuild
}}}
Since this port declares a build conflict with itself, users have to
deactivate it - forcibly, if a dependent like `astroid` is also installed
- simply to update it.
Is this intentional? If not, I'm happy to commit a quick fix.
Also, does this port truly have a build conflict with `xcbuild`?
--
Ticket URL: <https://trac.macports.org/ticket/63274>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list