Compiled packages can get out of sync with official repos #130
Labels
No Label
Roadmap
V
bug
docs
duplicate
enhancement
good first issue
help wanted
idea
invalid
question
wontfix
Idea
Roadmap
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vieter-v/vieter#130
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
An issue I've had two times now with my matrix client (nheko) is that my binary was compiled using an older version of some dynamic library, causing it to break when I update my system while the package hasn't been rebuilt yet.
I have no idea how I would go about addressing it, but it should be looked into.
A possible workaround would be adding a setting to disable the check for whether a package has to be rebuilt or not. This would cause the package to always build, making sure it never gets too far out of sync.
This could be fixed by #135. That way, the user could let their Vieter builds use the repos they use on their machines.
I don't actually know whether this is still an actual issue, as I haven't encountered this bug anymore.
Because each build now runs
pacman -Syu
, this is most likely fixed.