Maybe a rebuild for sord? #36
Labels
No Label
blocked upstream
bug
build-failure
duplicate
enhancement
help wanted
informational
invalid
invalid/corrupt package
packaging issue
priority: high
question
support
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ALHP/ALHP.GO#36
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I don't know if i'm the only one having this, but the current build of
sord
seem to have a bug that trow a bunch of error in the journald.After a rebuild of the package that i've done to my side, the issue seem to be gone, so a rebuild seem to be needed to avoid some issue and the spam in the journald.
I just queued it.
If you are willing to test the rebuild version once it's done: You are going to get a signature error, since your local package in cache won't match the sync repo. You can just ignore that and redownload.
You can check if it has been build on the package status page as usual (see check date and build date once its done). (One of these days I'll make it fancy with animations, fancy js and stuff, but there are more important things to work on 😄)
Seems to be good so far, i will test it more and let you know tomorrow if it is all good
Seem that the rebuild have fixed the spam log issue.
Closing this now
Hi,
after seeing this issue I remembered that all my LV2-hosting software, ardour, carla, etc crashed since recently and I forgot to think that it may be due to this.
And indeed, rebuilding sord from git source (directly from upstream) makes the crash go away ; otoh the rebuilt packages from this repo (just tried today) do not seem to work ?
Have you tried
sord
from [community]?pacman -S community/sord
If you have the same problems with the one from official sources it may be that
a) something other then
sord
needs a rebuild orb) its a bug with
sord
.You can also check if you have the rebuild version with
pacman -Qi sord
,you can compare e.g. the build date with
pacman -Si sord
:I can confirm that it works with community/sord and not with community-x86-64-v3/sord
Potentially the packages lilv, sratom, suil, lv2, serd may need a rebuild (it's a set of libs that all pretty much work together)
Just tested
ardour
, seems to work fine on my end. Could you provide steps to reproduce your crashes (not limited toardour
)?pacman -Qi ardour