If I don't enter the sudo password in time, apacman asks for su password (which I don't have) then sudo password again. But then it forgot where it built the package. Example (with parts snipped):
$ apacman -Su
:: Synchronizing aur database...
Aur Targets (1): atom-editor-bin
…
:: Proceed with installation? [Y/n]
…
==> Finished making: atom-editor-bin 1.2.4-1 (сре, 25 ное 18:33:58 CET 2015)
-> Status built (1): atom-editor-bin
[sudo] password for damjan:
root Password:
su: Authentication failure
[sudo] password for damjan:
loading packages...
error: '/var/cache/apacman/pkg/atom-editor-bin-1.2.4-1-x86_64.pkg.tar': could not find or read package
local database is up to date
$ sudo pacman -U /tmp/pkgbuild-1000/atom-editor-bin/atom-editor-bin-1.2.4-1-x86_64.pkg.tar
[sudo] password for damjan:
loading packages...
resolving dependencies...
looking for conflicting packages...
Packages (1) atom-editor-bin-1.2.4-1
Total Installed Size: 199,95 MiB
Net Upgrade Size: 0,01 MiB
…
as can be seen the package is built fiie in /tmp/pkgbuild-1000/atom-editor-bin/ and if I get in time to enter the sudo password the first time, it'll install it without problems.
If I don't enter the sudo password in time, apacman asks for su password (which I don't have) then sudo password again. But then it forgot where it built the package. Example (with parts snipped):
as can be seen the package is built fiie in /tmp/pkgbuild-1000/atom-editor-bin/ and if I get in time to enter the sudo password the first time, it'll install it without problems.
apacman v2.3 Pacman v4.2.1 libalpm v9.0.1