kdenlive @ 0.9.10: Processing of port kdenlive failed

[info@…]

hello,

i am not able to install kdenlive on osx.

osx: 10.9.5
xcode: 5.1.1

i've uploaded the log file

[ryandesign (Ryan Carsten Schmidt)]

Please attach the file /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_kdenlive/kdenlive/main.log.

[info@…]

kdenlive log file

[info@…]

Replying to ryandesign@…:

Please attach the file /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_kdenlive/kdenlive/main.log.

i believe i've attached the right file now. thank you.

[info@…]

Replying to ryandesign@…:

Please attach the file /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_kdenlive/kdenlive/main.log.

found what you where searching for ?

[mkae (Marko Käning)]

(Wrong response removed.)

I've just verified that kdenlive builds fine for me here on 10.9.5.

[mkae (Marko Käning)]

BTW, the error in your kdepim4-log indicates, that you might not be using an up-to-date MacPorts installation, as it shows an error reported and fixed in #47087 months ago. Did you run

$ sudo port selfupdate
$ sudo port update outdated

lately?

[mkae (Marko Käning)]

Perhaps the revbump in r141767 is solving this for you after all.

[info@…]

update process

[info@…]

kdenlive log file #2

[info@…]

Replying to mk@…:

BTW, the error in your kdepim4-log indicates, that you might not be using an up-to-date MacPorts installation, as it shows an error reported and fixed in #47087 months ago. Did you run

$ sudo port selfupdate
$ sudo port update outdated

lately?

did an update (see files attached) - tried to reinstall kdenlive - still the same message

i will try updating xcode to 6.1.1 and see what happens - what version of xcode do you have on your end with osx 10.9.5 ?

[info@…]

Replying to info@…:

Replying to mk@…:

i will try updating xcode to 6.1.1 and see what happens - what version of xcode do you have on your end with osx 10.9.5 ?

before i install xcode 6.1.1 i tried to remove xcode 5.1.1. with - sudo /Developer/Library/uninstall-devtools --mode=all - i got - /Developer/Library/uninstall-devtools: command not found

any suggestions ?

[mkae (Marko Käning)]

Ooops, I see now that I must have erroneously looked at another log previously, as also the 1st was of a kdenlive build. :)

Sorry, I don't know how to remove the old xcode manually. I usually simply upgraded to the latest version and then the old one was gone automagically.

I hope you'll be able to build this port once you upgraded your xcode.

[info@…]

avidemux install

[info@…]

kdenlive error message

[info@…]

Replying to mk@…:

I hope you'll be able to build this port once you upgraded your xcode.

no problem ;) i installed xcode 6.1.1. - for a test, i changed port and installed avidemux (see screenshot). it's not xcode. seems to be a problem with kdenlive port from my end. still unable to install kdenlive (see screenshot).

[mkae (Marko Käning)]

Hmm... Is your MacPorts installation configured to automatically run rev-upgrade's?

If not, please run

$ sudo port rev-upgrade

and see what happens next.

But your avidemux-screenshot shows that there were no broken ports found, so I figure above command won't do anything on your end.
(Since kdenlive complains about nepomuk, I think that your nepomuk-core might not be up-to-date. You might try reinstalling it from the sources, compiling it yourself.)

This all might be caused by

• the recent transition of qt4-mac to its concurrent install scheme
• and the not yet done rev-bumping of all dependent ports, which nepomuk-core belongs to.

Qt4 and KDE ports need a major overhaul in this regard.

Let's see what your rev-upgrade is going to tell us.

[info@…]

No broken files found

[info@…]

Replying to mk@…:

Hmm... Is your MacPorts installation configured to automatically run rev-upgrade's?

i don't know. this is very new to me. i'm not a developer. if i wanted automatic upgrades, how should i setup macports - what commands should i use ?

If not, please run

$ sudo port rev-upgrade

and see what happens next.

i tried the commands just in case. the output gives me No broken files found (see screenshot). ?

[RJVB (René Bertin)]

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.

[info@…]

Replying to rjvbertin@…:

Can you do

> sudo find /opt/local/ -iname variant

and post the result?

see screen shot attached

---

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.

ok. got that. thanks

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.

i'm starting to see what you mean. i have kdenlive on linux in the meantime. but i find your project worth the efforts. if i can help you guys, with my non-developper's hat, i'm happy too.

[info@…]

iname variant

[RJVB (René Bertin)]

/opt/local//include/nepomuk2/Variant
                    ^

There you go, or at least I think so. That should be /opt/local/include/Nepomuk2/Variant. The "funny" thing is that if you do less /opt/local/include/Nepomuk2/Variant you will most likely see the contents of the file even in your case, but the compiler does a case-sensitive filename check instead of simply trying to open the file. You could try to rename the directory:

sudo mv /opt/local/include/nepomuk2 /opt/local/include/Nepomuk2

(or via the Finder, evidently). If my hypothesis is correct, your build error will go away. You may get others, though, because the intention of the Nepomuk authors is that you have /opt/local/include/nepomuk2/variant.h and /opt/local/include/Nepomuk2/Variant; the aforementioned 2 distinct directories for C and for C++ headers, respectively.

[RJVB (René Bertin)]

Marko: I see only 1 way around this that does not involve installing MacPorts on a case-sensitive partition (and building certain packages from source despite their existence as binary packages):

/opt/local/include/Nepomuk2 should be moved somewhere during the post-destroot, for instance into /opt/local/include/nepomuk2, and NepomukCoreConfig.cmake should be adjusted accordingly. That's something nicos c/should do...

Edit: doesn't work, at least not for kdenlive: the code supposes that the nepomuk2 and Nepomuk2 directories live next to each other in the same parent directory.

[mkae (Marko Käning)]

Oh, I see, info has MacPorts installed on a case-sensitive system...

I remember there were some issues like this with Phonon a while ago.

Didn't know that Nepomuk is another candidate for this. :-(

---

OK, so I guess one needs to contact upstream to fix this, right?!!

[RJVB (René Bertin)]

Replying to mk@…:

Oh, I see, info has MacPorts installed on a case-sensitive system...

case-INsensitive ;)

OK, so I guess one needs to contact upstream to fix this, right?!!

One would indeed, but AFAIK nepomuk is obsolete and abandoned, so I don't think anyone will be very enthusiastic about making a change that's going to break compilation of lots of legacy code when not done correctly.

[info@…]

Replying to rjvbertin@…:

Replying to mk@…:

Oh, I see, info has MacPorts installed on a case-sensitive system...

case-INsensitive ;)

just to confirm, yes, OSX 10.9.5 and Macports are installed on a Case-Sensitive HD. i didn't know it would cause any problems.

[RJVB (René Bertin)]

Ah, so in that case what you're seeing must be caused by something on the build bots. Can you try

sudo port -ns upgrade --force nepomuk-core

and after that try to build kdenlive once more?

A case-sensitive filesystem won't (shouldn't...) cause problems with MacPorts, on the contrary. A case-sensitive boot partition can cause issues with some 3rd party software though, IIRC notably from Adobe.

[info@…]

Replying to rjvbertin@…:

Ah, so in that case what you're seeing must be caused by something on the build bots. Can you try

sudo port -ns upgrade --force nepomuk-core

and after that try to build kdenlive once more?

yep! that worked. nepomuk was installed and that allowed kdenlive to be installed. (see screenshots) thank you for your help !!! let me know if you need anything else. all the best

[info@…]

force nepomuk

[info@…]

kdenlite install completed

[info@…]

kdenlive screen

[RJVB (René Bertin)]

Great!

If you're willing, it'd be nice if you re-filed this as a bug against "base".

Nepomuk may well have made some unhappy decisions in the way they name their headers, but in the end, the bug that bit you is somewhere in MacPorts' "base" code. (Or in the software that runs the buildbots.) The build bots are supposed to use case-sensitive filesystems, but this is not the first port where the binary distribution packages appear to have been made on a case-insensitive file system. That's a bug that ought to be squashed.

PS: may I ask what made you decide to install OS X on a case-sensitive filesystem? Seems like something a developer used to working on other Unices would do?

[info@…]

Replying to rjvbertin@…:

Great!

not really for nepomuk ;(

If you're willing, it'd be nice if you re-filed this as a bug against "base".

sure, i'll do that.

Nepomuk may well have made some unhappy decisions in the way they name their headers, but in the end, the bug that bit you is somewhere in MacPorts' "base" code. (Or in the software that runs the buildbots.) The build bots are supposed to use case-sensitive filesystems, but this is not the first port where the binary distribution packages appear to have been made on a case-insensitive file system. That's a bug that ought to be squashed.

ok, i'll report it.

PS: may I ask what made you decide to install OS X on a case-sensitive filesystem?

mainly for file management. i like the way things get sorted - upper vs lower case -

Seems like something a developer used to working on other Unices would do?

nope. just an artist. not a developer. and i'm not familiar with code.

ps. too bad kdenlive linux documents can't be opened on osx version... ;(

[RJVB (René Bertin)]

Replying to info@…:

ps. too bad kdenlive linux documents can't be opened on osx version... ;(

They cannot? I have never tried that, strange! If kdenlive/linux can also not open kdenlive/mac documents, you might want to report that as a bug too, on bugs.kde.org!

[info@…]

Replying to rjvbertin@…:

Replying to info@…:

ps. too bad kdenlive linux documents can't be opened on osx version... ;(

They cannot? I have never tried that, strange! If kdenlive/linux can also not open kdenlive/mac documents, you might want to report that as a bug too, on bugs.kde.org!

a kdenlive/mac osx document can be opened on kdenlive running on lubuntu 15.0.4, but not the opposite.

[mkae (Marko Käning)]

Which error message do you get in OSX/MacPorts' kdenlive when trying to open the file created on Linux?

In any case it sounds like a good idea to report this on b.k.o.! :-/

[mkae (Marko Käning)]

Replying to info@…:

Replying to rjvbertin@…:

If you're willing, it'd be nice if you re-filed this as a bug against "base".

sure, i'll do that.

If you do, please leave a note with the trac ticket number in this ticket, so that we can easily track this.

[ryandesign (Ryan Carsten Schmidt)]

Replying to mk@…:

If you do, please leave a note with the trac ticket number in this ticket, so that we can easily track this.

#49559 was filed.

[mkae (Marko Käning)]

If no one objects I close this ticket, as there is the followup on the real cause of this in #49559. Please re-open if you think this should stay open.