[MacPorts] #49458: kdenlive @ 0.9.10: Processing of port kdenlive failed

MacPorts noreply at macports.org
Sat Oct 31 01:59:59 PDT 2015


#49458: kdenlive @ 0.9.10: Processing of port kdenlive failed
-----------------------+------------------
  Reporter:  info@…    |      Owner:  mk@…
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:
      Port:  kdenlive  |
-----------------------+------------------

Comment (by rjvbertin@…):

 Can you do

 {{{
 > sudo find /opt/local -iname variant
 }}}

 and post the result?

 The kdenlive build fails because Nepomuk2/Variant header cannot be found.
 There are several possible reasons for that, including filename case
 aliasing. I recall that at least one port contains C++ style headers with
 uppercase letters and C style .h headers in all lowercase, with the 2
 types each in their own directories with names differing in case only.
 That is a situation which (often? tends to?) leads to errors during
 packaging on the build bots.

 > if i wanted automatic upgrades, how should i setup macports - what
 commands should i use ?

 You cannot to my knowledge have automatic upgrades that happen
 transparently behind your back without requiring any action on your part.
 You will have to do a periodic

 {{{
 > sudo port selfupdate && sudo port upgrade outdated
 }}}

 to keep your installation up to date. By default MacPorts is configured to
 run the aforementioned rev-upgrade command automatically after each
 upgrade command.

 NB: if you rely on software installed through MacPorts to do
 actual/important work, I would advise to reduce the selfupdate/upgrade
 frequency to a minimum that depends on your own needs. "If it ain't broke,
 don't fix it" ... because periodically someone will push an update to a
 port that has far-reaching side-effects. That's really a pity, because it
 evidently becomes increasingly cumbersome (= more work) if not complicated
 to upgrade, the longer you wait; IMHO this makes MacPorts a product that
 isn't really suitable for people who aren't willing to put on a
 developer's hat.

-- 
Ticket URL: <https://trac.macports.org/ticket/49458#comment:14>
MacPorts <https://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list