maat-builder sometimes requires manual intervention for new packages #2
Labels
No Label
Blocked
Duplicate
On-hold
Peer-review
RFC
Wontfix
Blocked
Duplicate
In-progress
On-hold
Peer-review
RFC
Wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: AniNIX/Maat#2
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?
Sometimes, when Maat gets several new packages added to the repo, if the dependencies are alphabetically sorted before the package, then the package data will change and the dependencies won't install during runtime. This can be fixed with a one-time install of the dependency manually, but that's less than ideal if we can avoid it.
Symptomatic output can look like this:
This is a duplicate of #1