You are not logged in.
I tried to run makepkg, while pacman was downloading a package, and I got the following error:
error: unable to lock pacman database.
if you're sure pacman is not already running, you
can remove /tmp/pacman.lck
==> ERROR: Dependency Check Failed:
Maybe a "dependency check failure" is not the appropriate error message?
makepkg should perhaps handle the case where pacman is already running (or that there is an existing lock file)?
Sorry for disturbing everyone, it is just a detail...
Offline
well the first stage of makepkg is to check dependencies, so actualy that is the point if fails at..
Offline
so stage 0 should be
if (pacman.lck) {
cout << "error: unable to lock pacman database.
if you're sure pacman is not already running, you
can remove /tmp/pacman.lck "
exit(0);
}
don't mind the syntax, it's a combination of c and java
apt-get install arch
Offline
In fact, makepkg is using pacman to check dependencies:
msg "==> Checking Dependencies..."
missdep=`pacman -T ${depends[@]}`
ret=$?
if [ "$ret" != "0" ]; then
if [ "$ret" = "127" ]; then
msg "==> ERROR: Dependency Check Failed:"
...
else
msg "==> ERROR: pacman returned a fatal error."
fi
exit 1
fi
If the returned value is 127, it displays "==> ERROR: Dependency Check Failed:"
The problem is that pacman can return an error code of 127 in 2 cases: "dependency failure" OR "pacman already locked".
I think pacman should return an error different from 127 when there is already a lock.
As a consequence, without changing makepkg, we would have: "ERROR: Dependency Check Failed" when dependencies checking fails and: "ERROR: pacman returned a fatal error" for other cases.
Offline