[MacPorts] #62441: qBittorrent fails to build on OS X 10.10.5

[MacPorts]

#62441: qBittorrent fails to build on OS X 10.10.5
-----------------------------------+------------------------
  Reporter:  DanielSmedegaardBuus  |      Owner:  i0ntempest
      Type:  defect                |     Status:  closed
  Priority:  Low                   |  Milestone:
 Component:  ports                 |    Version:  2.6.4
Resolution:  fixed                 |   Keywords:  yosemite
      Port:  qbittorrent           |
-----------------------------------+------------------------

Comment (by DanielSmedegaardBuus):

 I know, right? Very strange. I'm attaching the `libtorrent-rasterbar` log
 — I assume that's the interesting one, since it's the one that fails,
 right?

 I notice in this log it says:

 {{{
 :debug:configure boost176 is installed with the following variants:
 +no_single+no_static+python38
 :debug:configure   required: python39, forbidden:
 :debug:configure   rejected, because required variant python39 is missing
 :error:configure Failed to configure libtorrent-rasterbar: boost176 must
 be installed with +python39.
 :debug:configure Error code: NONE
 :debug:configure Backtrace: boost176 must be installed with +python39.
 }}}

 That's pretty clear, though. Should've read that last night, but yeah, I'm
 not too good at the braining ATM :D

 I'm gonna try and see if I can rebuild boost176 against/for python39 as it
 indicates it wants. Still confused about how libtorrent 2.x gets pulled in
 even when building from this older commit, but really, I've never
 uninstalled and cleaned `boost176`, just `boost`, so it kinda makes sense
 that I can't get rid of this issue, assuming that that's the culprit.
 Questions though, would be what triggered the `boost176` (re)build with
 that configuration to make the qbt build sad, and if it should really have
 that requirement for `boost176` in the first place (that is, being built
 for python39), seeing as how it apparently works fine with one built for
 python38.

 About libtorrent 2.x being pulled in even when at this older commit, is
 there someplace outside of the macports-ports repo that gets to co-decide
 which dependency versions get pulled in? Pretty curious about that one :)

 Anyway, I'll attach the log, try to rebuild boost176 for python39 and see
 what happens.

-- 
Ticket URL: <https://trac.macports.org/ticket/62441#comment:49>
MacPorts <https://www.macports.org/>
Ports system for macOS