Skip to content
This repository has been archived by the owner on May 31, 2018. It is now read-only.

"Could not connect to the AUR", but cower works fine #458

Closed
justinnhli opened this issue Mar 29, 2016 · 2 comments
Closed

"Could not connect to the AUR", but cower works fine #458

justinnhli opened this issue Mar 29, 2016 · 2 comments

Comments

@justinnhli
Copy link

Since a couple days ago I noticed that pacaur consistently fails to connect the AUR, giving the "Could not connect to the AUR" message. I have looked at #141, #264, and #295, and but none of the causes of those problems apply (curl works fine, and there are no permission issues in /tmp/pacaur-$username). Running cower seems to have no problems, and both cower and pacaur are up to date.

Here's a transcript: http://pastebin.com/NfVpxRct

And here's the debug output of bash -x $(which pacaur) -Sua: http://pastebin.com/tN087yM4

@rmarquis
Copy link
Owner

Looking at your debug output, it is indeed cower that can't connect. Check out #451, you might have the very same issue.

@rmarquis rmarquis added this to the 4.6.x - new features milestone Mar 29, 2016
@justinnhli
Copy link
Author

You're absolutely right - I had aliased pacaur to pacaur --domain aur4.archlinux.org, and removing that flag solved the problem. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants