dmcgee@galway /home/makepkg/packages $ pacS ../valgrind-3.4.1-1-x86_64.pkg.tar.gz error: repository '..' not found error: '../valgrind-3.4.1-1-x86_64.pkg.tar.gz': no such repository
Wow, this is ugly. The problem with PM_ERR_PKG_REPO_NOT_FOUND error code, that it needs a param (which repo was not found? this info is an alpm internal), that is impossible with error codes. Imho we should remove this error code [the "repository 'foo' not found" message is printed via alpm_log()], and just use PM_ERR_PKG_NOT_FOUND instead.
dmcgee@galway /home/makepkg/packages $ pacS /home/makepkg/packages/valgrind-3.4.1-1-x86_64.pkg.tar.gz error: repository '' not found error: '/home/makepkg/packages/valgrind-3.4.1-1-x86_64.pkg.tar.gz': no such repository
I'm not sure what the "fix" is, but it definitely is odd behavior.
I suppose we could catch the leading "/" or ".."? I can't think of a case where they would be right.
Allan
To the original problem: After all PKG_NOT_FOUND errors (assuming REPO_NOT_FOUND was removed) we could do access(target, ...) in the front-end; and if found, print a "Did you mean -U?" message. Of course, this is not a perfect solution (user typo?), but I have no better idea... Bye