I dont understand the fixation with the term ‘default’ here.
‘Default’ can be applied to various levels and circumstances.
I am speaking to the normal operation of pamac, as it can be expected to do in all other unconfigured cases, when the AUR is enabled.
If you dont want to call it default, thats fine I guess.
“If pamacs normal mode of operation, when the AUR is enabled, is to build AUR packages first, alongside repository packages, or in any order other than dead last and after all repository packages have been synced then it is doing it wrong.”
If Enable AUR support is turned on in pamac GUI, user is expected to be aware of the risks and responsibilities and familiar with the build process
Pamac GUI can build AUR packages with just this one option enabled, but Check for updates must also be turned on to update Respository and AUR packages at the same time
If Pamac GUI has both options enabled, users should check the package list before agreeing to update and un-check any AUR packages
Or update Respository packages in CLI - pamac update
It would have prevented this Testing branch user from opening their own package manager & refreshing the databases, only to be scratching their head as they wondered why the dependency change to mhwd hadn’t appeared.
The first thing I do when a member’s post piques my interest is click on their forum avatar to see what branch they are on & the type of system (AMD/Intel/Plasma etc) they are running.
Ah, so, part of the reason for mincing words here was because of the second option?
The assertion is that if only “Enable AUR Support” is enabled the user will not be offered AUR upgrades at all?
Maybe so. Again, please recall that this thread is in response to a users experience.
This still does not change the following facts;
The user here was confused by the sequence of events and the status of the involved packages. And this confusion was also aided by the next points.
Pamac, when used to upgrade both repository and AUR packages, will not make distinctions between the two, nor preference, seemlessly replacing repository packages with AUR counterparts if the name matches.
Pamac, when used to upgrade both repository and AUR packages, does not follow best practices for ALPM in regards to the order of operations. That is in all circumstances Repository packages should be synced and upgraded first and third party packages only after that has succeeded, but Pamac fails to do this.
What happened seems logical regarding the options apparently set in Pamac. It has already been pointed out what an informed user should have done in this case:
If a user enables AUR and enables AUR updates, in this situation I assume it is logical that it updates the now unneeded dependency from the AUR if the user just blindly updates the systems with all these options enabled in Pamac. It is also logical that the user can not remove the dependency before the package requiring it still requires it.
I’m frequently jumping between testing and unstable. Currently, I’m on unstable mainly because I’m eagerly waiting for some upstream bugs to be fixed. Some of Plasma bugs were indeed fixed in recent updates. However, those are minor things.
The biggest pain I have is the kernel 6.11 issue I am experiencing, a visual stutter on the screen that starts happening randomly from time to time, making this kernel series (and probably all above) unusable (no issue on 6.6). Latest updates made appearing this issue to be less frequent but haven’t fixed it completely.
When the situation is more stable, I will move to testing again.
Anyway, jumping between branches is easy and quick, and when I do it, I don’t remember to change the profile. I can update it now, but during next jump I probably won’t update it either… so or so, this will most often be not actual info.
However, if I’m on an unstable branch and have some feedback, I post on unstable update thread. If I’m on testing, I’m posting on testing thread.
Yeah, I got it. When I said “dropped” I first thought it was done by Arch, but then saw replays clarifying it, so later when I meant dropped by you/Manjaro as this is something you have influence on.
Yeah, you may be right about that. There was no issue here and everything worked as intended. I just noticed that the update has “new AUR package” - which was obvious that it disappeared from the repos. That means, this package is no longer needed, so I wanted to REMOVE IT PRIOR THE UPDATE, but since UPDATE HASN’T HAPPENED YET, removal triggered dependency error.
Because I didn’t know that mhwd after the update drops this dependency, I thought this is an oversight, but it wasn’t. I was just too proactive, trying to remove package aboout to be orphaned before it being orphaned ;).
All in all, you and @Yochanan are right, all is good.
Still, I disagree with some things you said about pamac, but that is a diffrent conversation and this is probably pointless to disucss here or right now, although some here are doing it, but I don’t feel like joing at the moment.