<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div>Yes, known. See the last ticket at<div class=""><br class=""></div><div class=""><a href="https://ports.macports.org/port/poppler/tickets" class="">https://ports.macports.org/port/poppler/tickets</a></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 25 Oct 2020, at 9:44 pm, Dave Horsfall <<a href="mailto:dave@horsfall.org" class="">dave@horsfall.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Sierra 10.12.6 (won't go any further), MacPorts 2.6.3 on a mid-2010 MacBook Pro.<br class=""><br class="">(Looks like "poppler" is part of "xpdf", my favourite PDF viewer.)<br class=""><br class="">Whenever I do my regular "port upgrade outdated" I keep seeing the following, and it's starting to annoy me:<br class=""><br class=""> ---> Configuring poppler<br class=""> Error: poppler cannot be built while another version of poppler is active.<br class=""> Error: Please forcibly deactivate the existing copy of poppler, e.g. by running:<br class=""> Error:<br class=""> Error: sudo port -f deactivate poppler<br class=""> Error:<br class=""> Error: Then try again.<br class=""> Error: Failed to configure poppler: poppler is active<br class=""><br class="">The "fix" is obvious of course, but before I file a bug report is this a known problem? Error log available upon request.<br class=""><br class="">Thanks.<br class=""><br class="">(And yes, I know that I have a number of replies to acknowledge, but I've been busy/sick lately; comes from being in my late 60s.)<br class=""><br class="">-- Dave<br class=""></div></div></blockquote></div><br class=""></div></body></html>