It’s been some months, and kdenlive is still listed as orphaned. Anyone know how packages become un-orphaned?
Also, if anyone else is having the same problems, this fork worked for me (the missing dependency is glaxnimate
.
https://github.com/classabbyamp/void-packages.git new/glaxnimate
I had no idea it was orphaned, I figured it was a KDE project. I used it yesterday and it still works. Crazy!
I just mean the package on Void.
xbps-query --show kdenlive
The maintainer is listed as ‘orphaned’, i.e. it has no maintainer. So void doesn’t have the latest version.
What OS are you running it on??
Void.
Package being orphaned means that there isn’t someone taking care of it and actually taking care of it / maintaining it.
Usually the more active maintainers sometimes update orphaned packages.
Probably a good use for flatpaks as it doesn’t seem to be a simple package to maintain…
If you are an active user of the package I can have a look at it and try to open a PR with the update
I’m definitely an active user of Kdenlive. If you could get it working, that would be wonderful.
I cannot believe I spent two hours learning xbps-src instead of just installing via flatpak…it never crossed my mind.
I did take a quick lock and there only seems to be 2 minor releases behind, 23.04.0 -> 23.04.2 were there any changes/bug fixes that makes you need the latest version ?
No, I just need it to start. It insta-crashes with a note about
glaxnimate
missing.Oh didn’t notice that, I would advise you to open an issue on GitHub then. They should be fast with it :)
It looks like the github bot closed the issue due to lack of testing.
I’ve commented that the branch works, but it’d be great if someone who understands xbps better could verify that it builds correctly.
however, the “missing component” message should be nonfatal.
Doesn’t work for you ?
No, I’m afraid it crashes. I’ve pulled up a VM to check again - same result. It crashes, noting ‘mediainfo’ and ‘glaxnimate’ are missing. I can install mediainfo from the repos, but not glaxnimate:
I hit ‘okay’, and it’s gone. Here’s the full error message:
Just want to let you know that the issue was fixed! Thanks for reporting (next time open a GitHub issue instead of commenting on a PR)
I’d usually open an issue, but the issue already existed, and was closed by the Github bot.