Thanks, working as expected now, but still throwing the 'invalid option '"--needed"' message when issuing "pacaur -Qua --devel --needed" but only once now instead of twice. The same behaviour doesn't happen when i issue "pacaur -Qum --devel --needed".
Thx, fixed as well.
Thanks again, everything working as expected now.
Sorry for bothering you again but it seems i may have found another bug, after today's pacaur-git updates, when i issue "pacaur -Qqum --devel --needed" or the "-Qqua" equivalent it shows 2 updates for pacaur-git(my noob guess is that it's showing one update for the bump in version to 4.7.6-1 and another due to the commits in the github repository).
The same behaviour doesn't happen when i issue "pacaur -Qum --devel --needed" or the "-Qua" equivalent.
Last edited by leosanvieira (2017-03-20 21:59:48)
@leosanvieira> Indeed. Great catch, thx! Fixed in master.
is there an equivalent flag to (makepkg) '--cleanbuild' for a clean srcdir before building a package?
Besides the general 'warning: Using existing $srcdir' some packages cannot be build with an old srcdir.
No, build is done by makepkg -od then makepkg -sefc. I might add this -C flag by default if there is no side effect with other packages. Do you have an example of such failing package?
Note pacaur won't support PKGBUILDs that don't build with makepkg -o && makepkg -e, as they usually need to be fixed by their maintainer.
Last edited by Spyhawk (2017-03-27 18:49:14)
I had an existing srcdir for natron (2.2.3-1 -> 2.2.6-2) and lib32-qt4 (4.8.7-6 -> 4.8.7-10), both failed during the normal update.
Both are building fine after removing the existing srcdir.
I'm sorry, but I can't reproduce this. Have you added the -c flag "recently"? Maybe my srcdir was a relict of a manual build…
However, see this as a feature request to prevent something like this. Workflow would be makepkg -Cod & makepkg -sefc.
Last edited by Lucki (2017-03-27 21:59:54)
No, the -c flag has been here for a long time.
Edit: Adding -C is likely to break stuff in some situation. I won't do any change until the issue is correctly identified here, and I cannot reproduce either.
Last edited by Spyhawk (2017-04-03 08:17:00)