Fix building against libalpm 14 #14

Open
sudoBash418 wants to merge 2 commits from sudoBash418/pamac-classic:master into master
First-time contributor

I have zero experience with Vala, but these changes seem to be enough for pamac-classic to successfully build against pacman 6.1.0 (libalpm 14.0.0).

There seem to be a few bugs related to retrieving files - I'm not sure if they're related to this update or not, but unfortunately I do not have time to investigate them.

I have zero experience with Vala, but these changes seem to be enough for pamac-classic to successfully build against pacman 6.1.0 (libalpm 14.0.0). There seem to be a few bugs related to retrieving files - I'm not sure if they're related to this update or not, but unfortunately I do not have time to investigate them.
sudoBash418 added 2 commits 2024-04-26 18:58:53 -04:00
825f604566
Fix pamac-system-daemon for new libalpm version
Key revocation status is no longer available, so we always try
importing keys.
This pull request can be merged automatically.
You are not authorized to merge this pull request.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b sudoBash418-master master
git pull master

Step 2:

Merge the changes and update on Gitea.
git checkout master
git merge --no-ff sudoBash418-master
git push origin master
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cromer/pamac-classic#14
No description provided.