Cannot connect to AUR #528

stef204 · 2019-04-05T07:18:04Z

% aura --version
                       
 __ _ _  _ _ _ __ _    Pacman v5.1.3 - libalpm v11.0.3
/ _` | || | '_/ _` |   Copyright (C) 2006-2018 Pacman Development Team
\__,_|\_,_|_| \__,_|   Copyright (C) 2002-2006 Judd Vinet
AURA Version 2.0.0     
 by Colin Woodbury     This program may be freely redistributed under
                       the terms of the GNU General Public License.
Aura Translators:      
aura: Map.!: given key is not an element in the map
CallStack (from HasCallStack):
  error, called at libraries/containers/Data/Map/Internal.hs:610:17 in containers-0.6.0.1:Data.Map.Internal

Note the error at the end.

(This package is aura-git in the AUR.)

aura can no longer connect to AUR, resulting in this error:

% sudo aura -Akuax
aura >>= Fetching package information...
aura >>= Failed to contact the AUR. Do you have an internet connection?

This error started a few days ago and is now 100% consistently present.
Can you please look into this? How can I help troubleshoot?

The text was updated successfully, but these errors were encountered:

fosskers · 2019-04-06T14:51:02Z

That's odd, let me look into this.

stef204 · 2019-04-09T08:44:56Z

I've tried to analyze packets using tcpdump and wireshark to see if anything obvious came up, but did not notice anything.
Happy to redo this step if you have detailed instructions or any other troubleshooting steps.

fosskers · 2019-04-09T12:59:35Z

I'm out of town at the moment for work, but I'm pretty sure I know what to look for. I'll check it once I'm back, later this week.

stef204 · 2019-04-24T21:15:58Z

I've tried to downgrade back to 1.4 in the meantime but that does not work for me--as, for some reason, 1.4 has long since stopped picking up new or updated versions of packages in the AUR.
(Which is what prompted me to go for the 2.0 git version.)

Still getting this:

    aura: Map.!: given key is not an element in the map
CallStack (from HasCallStack):
  error, called at libraries/containers/Data/Map/Internal.hs:610:17 in containers-0.6.0.1:Data.Map.Internal

.

fosskers · 2019-04-24T22:29:30Z

The Map issue is minor and can be fixed pretty easily.

As for 2.0 not detecting things... I'm not having that issue on my end.
Does something like aura -As aura succeed for you?

stef204 · 2019-04-26T16:17:21Z

Is the Map issue an upstream fix or something I should do here? If so, some guidance would be helpful.

Yes, aura -As aura succeeds.
So does aura -Ap and other aura commands.
But sudo aura -Akuax consistently fails, 100% of the time.

This DID work for quite some time and then, stopped suddenly, about 2 to 3 weeks ago,

Let me clarify: it is version 1.4 which fails to detect changes, updates, etc. But I've upgraded to version 2.0 which is the topic at hand. And version 2 works as expected, detecting changes, etc.

The current issue is ths error which needs fixing in aura 2.0 master branch (aura-git in AUR) is::

% sudo aura -Akuax
aura >>= Fetching package information...
aura >>= Failed to contact the AUR. Do you have an internet connection?

Sure would like to resolve this as it breaks aura and makes it unusable (for me.)
Happy to troubleshoot but not sure where to start.

stef204 · 2019-05-19T09:55:36Z

Following your recent changes, I have recompiled master branch today; and problem(s) described above still present, IOW still cannot connect to AUR with same error message, plus the internal.hs error below:

% aura --version
                       
 __ _ _  _ _ _ __ _    Pacman v5.1.3 - libalpm v11.0.3
/ _` | || | '_/ _` |   Copyright (C) 2006-2018 Pacman Development Team
\__,_|\_,_|_| \__,_|   Copyright (C) 2002-2006 Judd Vinet
AURA Version 2.0.0     
 by Colin Woodbury     This program may be freely redistributed under
                       the terms of the GNU General Public License.
Aura Translators:      
aura: Map.!: given key is not an element in the map
CallStack (from HasCallStack):
  error, called at libraries/containers/Data/Map/Internal.hs:610:17 in containers-0.6.0.1:Data.Map.Internal

fosskers · 2019-05-19T14:10:33Z

Thanks for the update.

stef204 · 2019-05-22T08:23:25Z

Just pulled and compiled again now, same 2 issues still present.
Not sure if this feedback is helpful at all. Perhaps best if you post here once you want me to test?

fosskers · 2019-05-22T14:48:45Z

I will - thanks for your patience.

msgitter · 2019-06-16T10:05:44Z

@stef204 fyi:

My problems:

I encountered similar issues with 1.4 version ("not detecting changes").
tried to switch to the 2.x master version. -> same error as you: aura >>= Failed to contact the AUR. Do you have an internet connection?.

Solution:

I added some other servers from https://www.archlinux.org/mirrorlist/ to my etc/pacman.d/mirrorlist and now aura 2.x works for me.

So I guess I found out by luck, that the problem is probably not in aura 2.x, but that the servers in my pacman mirrorlist may be the source of trouble.
(Even they worked before. But maybe that was also the reason that 1.4 did not detect any changes anymore? I did not try again with 1.4 and the new mirrorlist)

fosskers · 2019-06-16T16:33:57Z

Oh that's an excellent find @marksutt , I will note this somewhere.

stef204 · 2019-07-19T08:59:05Z

Doesn't make sense.
I have 200 working servers in my mirror list, checked with reflector
On top of that. we're talking about AUR here, not official packages. And I only use aura for the AUR, never for official packages.

stef204 · 2019-09-07T08:37:15Z

@fosskers
Just compiled new master branch, Still same error.

% sudo aura -Akuax
aura >>= Fetching package information...
aura >>= Failed to contact the AUR. Do you have an internet connection?

All of my other applications using or connecting to AUR work, pacman connects to mirrors, if I use (reluctantly) another AUR helper, it works and connects to AUR perfectly.

It looks to me like there is something hardcoded into aura 2+ which breaks this connection, either the actual url/ip addresses, etc., or perhaps it's a certificate issue, I really don't know. This error has never gone away since I opened this ticket in April 2019.

I supposed I could use a packet sniffer like tcpdump or wireshark to try to capture what is going on.
Would you like me to do that and if so, do you have any specific parameters/options you want me to use? if so please suggest a tcpdump command, etc. Thanks.

% aura -Ap someaurpackage works and displays the PKGBUILD.
% aura -Ai someaurpackage works and displays package info.
% aura -Qs someaurpackage works.
% sudo aura -Akax someaurpackage works and builds someaurpackage.

% sudo aura -Au
aura >>= Fetching package information...
aura >>= Failed to contact the AUR. Do you have an internet connection?

It looks like the use of -u causes the error.

See below.for version. Thanks.

% aura --version 
                       
 __ _ _  _ _ _ __ _    Pacman v5.1.3 - libalpm v11.0.3
/ _` | || | '_/ _` |   Copyright (C) 2006-2018 Pacman Development Team
\__,_|\_,_|_| \__,_|   Copyright (C) 2002-2006 Judd Vinet
AURA Version 2.0.2     
 by Colin Woodbury     This program may be freely redistributed under
                       the terms of the GNU General Public License.
Aura Translators:      
 (Japanese) Onoue Takuro
 (Polish) Chris Warrick
 (Croatian) Denis Kasak / "stranac"
 (Swedish) Fredrik Haikarainen / Daniel Beecham
 (German) Lukas Niederbremer / Jonas Platte
 (Spanish) Alejandro Gómez / Sergio Conde
 (Portuguese) Henry Kupty / Thiago Perrotta / Wagner Amaral
 (French) Ma Jiehong / Fabien Dubosson
 (Russian) Kyrylo Silin / Alexey Kotlyarov
 (Italian) Bob Valantin
 (Serbian) Filip Brcic
 (Norwegian) "chinatsun"
 (Indonesian) "pak tua Greg"
 (Chinese) Kai Zhang
 (Esperanto) Zachary Matthews

fosskers · 2019-09-09T16:23:35Z

Ah man, sorry about this. Can you run:

stack test -- aur

And tell me what it says?

stef204 · 2019-09-09T19:54:26Z

% stack test -- aur                      

Error: While constructing the build plan, the following exceptions were encountered:

In the dependencies for aur-6.2.0.1:
    Cabal-1.22.8.0 from stack configuration does not match >=2.2  (latest matching version is 3.0.0.0)
    base-4.8.2.0 from stack configuration does not match >=4.10 && <5  (latest matching version is 4.12.0.0)
    http-client-0.4.31 from stack configuration does not match >=0.5 && <0.7  (latest matching version is 0.6.4)
    servant-0.7.1 from stack configuration does not match ^>=0.16  (latest matching version is 0.16.2)
    servant-client-0.7.1 from stack configuration does not match ^>=0.16  (latest matching version is 0.16)
needed since aur is a build target.

Some different approaches to resolving this:

  * Set 'allow-newer: true' in /home/$USER/.stack/config.yaml to ignore all version constraints and build anyway.

  * Build requires unattainable version of base. Since base is a part of GHC, you most likely need to use a different GHC version with the matching base.

Plan construction failed.

fosskers · 2019-09-10T16:50:47Z

You're on the HEAD of master? Here's what I get:

colin@yumi ~/c/h/aura> stack test -- aur
aur> test (suite: aur-test)

RPC Calls
  info on existing package:    OK (2.55s)
  info on nonexistant package: OK (2.55s)
  search:                      OK (3.09s)

All 3 tests passed (3.09s)

aur> Test suite aur-test passed

What version of stack do you have?

stef204 · 2019-09-12T13:40:37Z

Seems there are conflicts on my box.

I have a global stack (/usr/bin/stack):

stack --version Version 2.1.3, Git revision b2e2f3d0568e6d73fc0477dee8ca7c04466ec1f6 (dirty) (7736 commits) x86_64

That is in my $PATH so the stack test -- aur I posted above uses that one.

Note: you can see all of its dependencies here.

And I have a local stack (~/.local/bin):

~/.local/bin % ./stack --version   
Version 2.1.3, Git revision 636e3a759d51127df2b62f90772def126cdf6d1f (7735 commits) x86_64 hpack-0.31.2

Using the local stack gives:

~/.local/bin % ./stack test -- aur

Error: While constructing the build plan, the following exceptions were encountered:

In the dependencies for aur-6.2.0.1:
    Cabal-1.22.8.0 from stack configuration does not match >=2.2  (latest matching version is 3.0.0.0)
    base-4.8.2.0 from stack configuration does not match >=4.10 && <5  (latest matching version is 4.12.0.0)
    http-client-0.4.31 from stack configuration does not match >=0.5 && <0.7  (latest matching version is 0.6.4)
    servant-0.7.1 from stack configuration does not match ^>=0.16  (latest matching version is 0.16.2)
    servant-client-0.7.1 from stack configuration does not match ^>=0.16  (latest matching version is 0.16)
needed since aur is a build target.

Some different approaches to resolving this:

  * Set 'allow-newer: true' in /home/stef/.stack/config.yaml to ignore all version constraints and build anyway.

  * Build requires unattainable version of base. Since base is a part of GHC, you most likely need to use a different GHC version with the matching base.

Plan construction failed.

The local stack might be using GHC 7+. (version 7.10.3).

So, the whole issue might be due to the aura 2 being built on my box with the wrong tool/deps/versions?

It does build though, using the aura-git AUR package here which uses the global stack.

I may not have thought this through all the way to the end, as it were....

Thoughts?

PS I've also just built in manually, following the procedure in the README, both using the global stack and local one and error persists.

fosskers · 2019-09-12T16:50:44Z

Ah, I see what it was doing. I had meant for you to do stack test -- aur from within a cloned copy of the aura repository.

stef204 · 2019-09-12T18:09:27Z

in the meantime, since i had not done anything Haskell for quite some time now, I nuked haskell from my box, both global (from Arch repo) and locally.

I should now start again fresh. But should probably stick to local install. Since you're the Haskell Pro (and I believe you use Arch?), which of the different ways suggested here would you recommend I do if I want to stick to local?

stef204 · 2019-09-12T19:54:32Z

In the meantime, I've installed stack locally from https://get.haskellstack.org/ and:

aur                 > test (suite: aur-test)
                   
Progress 92/93: aurRPC Calls
  info on existing package:    OK (0.83s)
  info on nonexistant package: OK (0.83s)
  search:                      OK (1.10s)

All 3 tests passed (1.10s)
                   
aur                 > Test suite aur-test passed

stef204 · 2019-09-12T20:11:26Z

And I've now compiled aura locally, using the new stack (installed locally) and....

% sudo aura -Au                         
aura >>= Fetching package information...
aura >>= Failed to contact the AUR. Do you have an internet connection?

Where do we go from there?

fosskers · 2019-09-13T17:00:33Z

Is that aura definitely the aura that stack just built? It shouldn't occur that the aur tests pass and yet aura can't access the AUR.

stef204 · 2019-09-13T21:01:33Z

I'm 100% sure since I uninstalled the aura-git package from AUR.

% which aura 
/home/$USER/.local/bin/aura

That's where stack installed it.

% file aura    
aura: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=954a73e60bbe6fbe05699bd673a5299bbfb7c652, stripped

~/.local/bin % sudo ./aura -Au
aura >>= Fetching package information...
aura >>= Failed to contact the AUR. Do you have an internet connection?

I even tried with the ./ for an unnecessary double check since which aura shows the correct path.

I've now just run the test suite again (from the cloned directory) and it passes.
Then, still from cloned directory, I built aura again--and error still there.

To be more precise, aura does connect depending on which command is used.

If I try to get aura to show me an AUR PKGBUILD I have never installed or looked at before, it fetches and displays it. It can only fetch it from the AUR by connecting to it--since that PKGBUILD is not anywhere on my box (not in /var/cache/aura/pkgbuilds/).

So there is a connection negotiated successfully with:

% aura -Ap linux-ck                     
# Maintainer: graysky <graysky AT archlinux DOT us>
# Contributor: Jan Alexander Steffens (heftig) <jan.steffens@gmail.com>
# Contributor: Tobias Powalowski <tpowa@archlinux.org>
# Contributor: Thomas Baechler <thomas@archlinux.org>

### BUILD OPTIONS
# Set these variables to ANYTHING that is not null to enable them
[snip]

It seems to be the use of -u which creates that error.

I can look at the source to see what conditions result in printing the
aura >>= Failed to contact the AUR. Do you have an internet connection? message--but that's easier for you to do.

I'm still of the opinion I need to use wireshark or tcpdump to sniff what is going on which creates that failure. Started briefly yesterday but couldn't find anything yet.

I can compare this, still using wireshark, to another aur help trizen, for example.
trizen is a great piece of software, great design IMHO, but obviously trying to stick to aura which, prior to this breakage, I have been using for years.

fosskers · 2019-09-14T16:33:08Z

Thank you for persisting, that motivates me to find the source of the issue.

Okay, some more tests. Does a single -A work on a simple package? Say aura -A pkgbuilder?

stef204 · 2019-09-15T12:00:52Z

aura -A pkgbuilder does work, fetches and builds the package.
Already mentioned above

% sudo aura -Akax someaurpackage works and builds someaurpackage

Is this issue related to issue #498?

fosskers · 2019-09-24T00:31:16Z

Shouldn't be, I fixed that bug 🤔

aura >>= Failed to contact the AUR. Do you have an internet connection?

Let me see where this is coming from, and if the error handling code is being too broad. It could be that there's another (unforeseen) reason that it's failing.

stef204 · 2019-10-29T08:22:11Z

Just compiled today, using stack.

% aura --version
                       
 __ _ _  _ _ _ __ _    Pacman v5.2.0 - libalpm v12.0.0
/ _` | || | '_/ _` |   Copyright (C) 2006-2018 Pacman Development Team
\__,_|\_,_|_| \__,_|   Copyright (C) 2002-2006 Judd Vinet
AURA Version 2.0.2     
 by Colin Woodbury     This program may be freely redistributed under
                       the terms of the GNU General Public License

Same error:

aura >>= Fetching package information...
aura >>= Failed to contact the AUR. Do you have an internet connection?

How can I help further narrowing down the problem?

Lythenas · 2019-12-02T16:33:28Z

I recently ran into the same problem.

It seems like -A pkg/-Akax pkg works fine but -Au gives that error.

Here's the complete output:

$ sudo aura -Au
aura >>= Fetching package information...
aura >>= Comparing package versions...
aura >>= AUR Packages to upgrade:
haskell-ide-engine :: 0.12.0.0-1 -> 0.13.0.0-1
nodejs-pulp        :: 12.4.2-1   -> 13.0.0-1
signal-desktop     :: 1.27.4-6   -> 1.28.0-3
zotero             :: 5.0.77-1   -> 5.0.78-1

aura >>= Saved package state.
aura >>= Determining dependencies...
aura >>= Failed to contact the AUR. Do you have an internet connection?

stef204 · 2020-02-24T15:19:26Z

% aura -Au --dryrun --log-level=debug
2020-02-24 10:17:21.717478: [debug] Interpreting CLI options.
@(exec/aura.hs:93:3)
aura >>= Fetching package information...
2020-02-24 10:17:22.070519: [debug] Considering 374 'foreign' packages for upgrade.
@(lib/Aura/Commands/A.hs:76:3)
2020-02-24 10:17:22.070675: [debug] AUR: Looking up 374 packages...
@(lib/Aura/Packages/AUR.hs:152:3)
2020-02-24 10:17:22.860837: [debug] Failed! Server said: <html>
<head><title>414 Request-URI Too Large</title></head>
<body>
<center><h1>414 Request-URI Too Large</h1></center>
<hr><center>nginx/1.16.1</center>
</body>
</html>

@(lib/Aura/Packages/AUR.hs:158:7)
aura >>= The AUR server rejected the request.

Informative.

fosskers · 2020-02-24T15:50:57Z

Ah ha! I thought that might be it. I will change the logic of that function to do calls in batches of 50 packages at a time.

fosskers · 2020-02-24T16:10:35Z

@stef204 I just pushed up a fix to that branch. Can you pull it and try again?

stef204 · 2020-02-24T18:35:39Z

% aura -Au --dryrun --log-level=debug
2020-02-24 13:34:28.346055: [debug] Interpreting CLI options.
@(exec/aura.hs:93:3)
aura >>= Fetching package information...
2020-02-24 13:34:28.632555: [debug] Considering 374 'foreign' packages for upgrade.
@(lib/Aura/Commands/A.hs:76:3)
2020-02-24 13:34:28.632686: [debug] AUR: Looking up 374 packages...
@(lib/Aura/Packages/AUR.hs:152:3)
2020-02-24 13:34:29.402120: [debug] Package lookup successful.
@(lib/Aura/Commands/A.hs:101:3)
2020-02-24 13:34:29.402219: [debug] Potential upgrades: 3
@(lib/Aura/Commands/A.hs:81:3)
2020-02-24 13:34:29.415177: [debug] Upgrade Aura first? ... No.
@(lib/Aura/Commands/A.hs:84:3)
aura >>= Comparing package versions...
aura >>= AUR Packages to upgrade:
lib32-pangox-compat   :: 0.0.2-1        -> 0.0.2-2
python2-gtkspellcheck :: 4.0.5-5        -> 4.0.5-7
vivaldi               :: 2.11.1811.38-1 -> 2.11.1811.41-1

aura >>= Determining dependencies...
aura >>= `python-sphinx` is required as a dependency, which is provided by multiple packages. Please select one:
1. python-sphinx
2. python-sphinx-1
>> 1

aura >>= Repository dependencies:
python-sphinx
python2-sphinx
aura >>= AUR Packages:
lib32-pangox-compat
python2-gtkspellcheck
vivaldi

Looks good?

fosskers · 2020-02-24T18:38:16Z

My friend, our issue is fixed :) Thank you again for your patience. I'll release Aura 2.2.0 with this fix as soon as I can.

stef204 · 2020-02-24T18:44:08Z

Great. Thanks to you (I knew it had to be something simple.) Nicely done.

fosskers · 2020-02-25T16:06:16Z

@stef204 2.2.0 has been released.

mkoloberdin · 2020-04-03T00:20:27Z

I've just encountered this same issue while trying to install themix-full-git:

$ sudo aura -Akxa --log-level=debug themix-full-git
2020-04-03 03:16:53.388469: [debug] Interpreting CLI options.
@(exec/aura.hs:93:3)
aura >>= `themix-full-git` has no stored PKGBUILD yet.
aura >>= Determining dependencies...
aura >>= Failed to contact the AUR. Do you have an internet connection?

$ aura -Q aura-git
aura-git v2.2.1.r8.g2b21b47-1

fosskers · 2020-04-03T02:05:33Z

@mkoloberdin can you try again with a fresh master ?

mkoloberdin · 2020-04-09T03:59:04Z

@mkoloberdin can you try again with a fresh master ?

$ sudo aura -Akxa --log-level=debug themix-full-git
2020-04-09 06:56:24.464202: [debug] Interpreting CLI options.
@(exec/aura.hs:90:3)
2020-04-09 06:56:24.464348: [debug] Right (AurSync (Right (PkgName {pnName = "themix-full-git"} :| [])) (fromList []))
@(exec/aura.hs:93:5)
2020-04-09 06:56:24.464381: [debug] BuildConfig {makepkgFlagsOf = fromList [], buildPathOf = Path "/tmp", buildUserOf = Just (User {user = "**REMOVED**"}), truncationOf = None, buildSwitchesOf = fromList [DeleteMakeDeps,DiffPkgbuilds,DontSuppressMakepkg]}
@(exec/aura.hs:94:5)
2020-04-09 06:56:24.464418: [debug] CommonConfig {cachePathOf = Left (Path "/var/cache/pacman/pkg/"), configPathOf = Left (Path "/etc/pacman.conf"), logPathOf = Left (Path "/var/log/pacman.log"), commonSwitchesOf = fromList []}
@(exec/aura.hs:95:5)
aura >>= `themix-full-git` has no stored PKGBUILD yet.
aura >>= Determining dependencies...
aura >>= Failed to contact the AUR. Do you have an internet connection?

$ aura -Q aura-git
aura-git v2.2.1.r29.g791281f-1

mateusfccp · 2020-04-09T11:36:05Z

@stef204 2.2.0 has been released.

Mine is working too on 2.2.0.

fosskers · 2020-04-09T14:37:33Z

@mateusfccp is the issue present for you with 2.2.1?

mateusfccp · 2020-04-09T15:09:16Z

@mateusfccp is the issue present for you with 2.2.1?

I'm fixed at 2.2.0 right now and it's working fine. Do you want me to update to 2.2.1 to see if there's regression?

fosskers · 2020-04-09T15:16:11Z

@mateusfccp Yes please.

dpatti · 2020-04-11T18:50:16Z

I'm also having this issue after a recent upgrade:

$ sudo aura -Au --log-level=debug
2020-04-11 14:48:29.194680: [debug] Interpreting CLI options.
@(exec/aura.hs:93:3)
aura >>= Fetching package information...
2020-04-11 14:48:29.448639: [debug] Considering 36 'foreign' packages for upgrade.
@(lib/Aura/Commands/A.hs:76:3)
2020-04-11 14:48:29.448797: [debug] AUR: Looking up 36 packages...
@(lib/Aura/Packages/AUR.hs:152:3)
2020-04-11 14:48:30.135408: [debug] Package lookup successful.
@(lib/Aura/Commands/A.hs:101:3)
2020-04-11 14:48:30.135569: [debug] Potential upgrades: 6
@(lib/Aura/Commands/A.hs:81:3)
2020-04-11 14:48:30.137208: [debug] Upgrade Aura first? ... No.
@(lib/Aura/Commands/A.hs:84:3)
aura >>= Comparing package versions...
aura >>= AUR Packages to upgrade:
dropbox         :: 88.4.172-1   -> 94.4.384-1
...

aura >>= Saved package state.
aura >>= Determining dependencies...
aura >>= Failed to contact the AUR. Do you have an internet connection?


$ aura --version
                       
 __ _ _  _ _ _ __ _    Pacman v5.2.1 - libalpm v12.0.1
/ _` | || | '_/ _` |   Copyright (C) 2006-2019 Pacman Development Team
\__,_|\_,_|_| \__,_|   Copyright (C) 2002-2006 Judd Vinet
AURA Version 2.2.1     
 by Colin Woodbury     This program may be freely redistributed under
                       the terms of the GNU General Public License.

I built master (791281f), tried stack test -- aur and everything succeeded. I tried running it, and it still failed. I tried checking out v2.2.0 and got the same thing. I can try poking around, but if there's something specific I should be looking for, let me know.

dpatti · 2020-04-11T18:57:05Z

Ah, here's something else. I tried installing each package independently (sudo aura -A $package) and the one that seems to be causing issues is fonts-meta-base.

Edit: The plot thickens. I installed everything except fonts-meta-base one by one successfully, and then I tried sudo aura -Au again and... it worked? So unfortunately I kind of got myself out of the broken state and don't know if I can be much help debugging. Here were the exact set of packages that I did repro a failure on:

fonts-meta-base :: 1-2          -> 1-3
pygtk           :: 2.24.0-8     -> 2.24.0-11
spotify         :: 1.0.96.181-1 -> 1:1.1.10.546-4
ttf-symbola     :: 11.00-3      -> 13.00-7

If it happens to me again, I'll try to get to the root cause.

mkoloberdin · 2020-04-12T18:54:21Z

@fosskers, @dpatti I suspect this has to do with the size of the "dependency tree" of the package, so to speak.

fosskers · 2020-04-13T16:00:29Z

Aura should be able to handle large dep trees just fine, for instance ros-lunar-desktop.

Either way I'll add some more debugging messages around the location of this issue and see if that helps us. Thanks for reporting, everyone.

mateusfccp · 2020-04-15T21:46:31Z

@fosskers I updated to 2.2.1 and still works flawlessly here.

fabiogermann · 2020-07-15T07:34:50Z

@fosskers maybe there is a regression in 3.1.4-2 (aura-bin) (pacman 5.2.2/libalpm 12.0.2)?
Just had the same behavior when installing python-validity (AUR).
My fix was to install each dependency separately/manually and after that the desired package itself. On first glance it seems like there is an issue when resolving the dependencies.

fosskers · 2020-07-15T16:14:32Z

Whoa, quite interesting. That package in particular isn't working for me either, although a usual -Au for what I have installed does work. Looking into it now.

fosskers · 2020-07-15T16:15:20Z

Oh, that package appears to be fairly few, only a few days old.

fosskers · 2020-07-15T16:54:28Z

I added a few debug statements:

2020-07-15 09:51:51.052651: [debug] -Ad: Checking dependencies.
@(lib/Aura/Install.hs:186:3)
2020-07-15 09:51:52.393245: [debug] -Ad: Initial AUR lookup successful.
@(lib/Aura/Install.hs:198:7)
2020-07-15 09:51:52.393473: [debug] resolveDeps: Entered.
@(lib/Aura/Dependencies.hs:54:3)
2020-07-15 09:51:53.928136: [debug] resolveDeps: UnliftIO.Exception.throwString called with:

Non-existant deps

fosskers · 2020-07-15T17:01:59Z

Non-existant deps: fprintd-clients

fosskers · 2020-07-15T17:09:27Z

https://aur.archlinux.org/packages/python-validity/#comment-756211

fosskers · 2020-07-15T17:09:55Z

Either way I'm patching Aura to give a better message than what you were seeing. Clearly this wasn't a connection error.

mkoloberdin · 2020-07-16T13:46:10Z

Either way I'm patching Aura to give a better message than what you were seeing. Clearly this wasn't a connection error.

Back in April I managed to track down the cause but forgot to post, sorry (I was looking into making a patch/PR but did not have the time): it is the fact that aura does not handle "provides" (e.g. themix-full-git or some of its dependencies depend on some packages which are provided only by corresponding -git packages ONLY)

EDIT: Example: themix-full-git depends on themix-plugin-base16-git which depends on themix-gui - there is no such package but there is themix-gui-git which provides themix-gui.

https://aur.archlinux.org/packages/themix-plugin-base16-git/ :

https://github.com/fosskers/aura/blob/master/aura/lib/Aura/Dependencies.hs#L142
$ bDeps b -- TODO handle "provides"?

fosskers · 2020-07-17T05:36:25Z

You raise a good point. I need to reexamine that particular part of the code, but off the top of my head I believe it isn't directly involved in the discovery of packages that satisfy a "provides" condition even when a package of that exact name doesn't exist (as was the case here with fprintd-clients.

fosskers mentioned this issue Jun 16, 2019

Document issue about stale mirrorlists #537

Closed

fosskers linked a pull request Feb 24, 2020 that will close this issue

Debug Logging #568

Merged

fosskers closed this as completed in #568 Feb 24, 2020

Cannot connect to AUR #528

Cannot connect to AUR #528

Comments

stef204 commented Apr 5, 2019 • edited Loading

fosskers commented Apr 6, 2019

stef204 commented Apr 9, 2019

fosskers commented Apr 9, 2019

stef204 commented Apr 24, 2019 • edited Loading

fosskers commented Apr 24, 2019 • edited Loading

stef204 commented Apr 26, 2019 • edited Loading

stef204 commented May 19, 2019 • edited Loading

fosskers commented May 19, 2019

stef204 commented May 22, 2019 • edited Loading

fosskers commented May 22, 2019

msgitter commented Jun 16, 2019

fosskers commented Jun 16, 2019

stef204 commented Jul 19, 2019 • edited Loading

stef204 commented Sep 7, 2019 • edited Loading

fosskers commented Sep 9, 2019

stef204 commented Sep 9, 2019 • edited Loading

fosskers commented Sep 10, 2019

stef204 commented Sep 12, 2019 • edited Loading

fosskers commented Sep 12, 2019 • edited Loading

stef204 commented Sep 12, 2019

stef204 commented Sep 12, 2019

stef204 commented Sep 12, 2019

fosskers commented Sep 13, 2019 • edited Loading

stef204 commented Sep 13, 2019 • edited Loading

fosskers commented Sep 14, 2019

stef204 commented Sep 15, 2019 • edited Loading

fosskers commented Sep 24, 2019

stef204 commented Oct 29, 2019

Lythenas commented Dec 2, 2019

stef204 commented Feb 24, 2020

fosskers commented Feb 24, 2020

fosskers commented Feb 24, 2020

stef204 commented Feb 24, 2020

fosskers commented Feb 24, 2020

stef204 commented Feb 24, 2020

fosskers commented Feb 25, 2020

mkoloberdin commented Apr 3, 2020

fosskers commented Apr 3, 2020

mkoloberdin commented Apr 9, 2020

mateusfccp commented Apr 9, 2020

fosskers commented Apr 9, 2020

mateusfccp commented Apr 9, 2020

fosskers commented Apr 9, 2020

dpatti commented Apr 11, 2020

dpatti commented Apr 11, 2020 • edited Loading

mkoloberdin commented Apr 12, 2020

fosskers commented Apr 13, 2020 • edited Loading

mateusfccp commented Apr 15, 2020

fabiogermann commented Jul 15, 2020

fosskers commented Jul 15, 2020 • edited Loading

fosskers commented Jul 15, 2020

fosskers commented Jul 15, 2020

fosskers commented Jul 15, 2020

fosskers commented Jul 15, 2020

fosskers commented Jul 15, 2020

mkoloberdin commented Jul 16, 2020 • edited Loading

fosskers commented Jul 17, 2020 • edited Loading

stef204 commented Apr 5, 2019 •

edited

Loading

stef204 commented Apr 24, 2019 •

edited

Loading

fosskers commented Apr 24, 2019 •

edited

Loading

stef204 commented Apr 26, 2019 •

edited

Loading

stef204 commented May 19, 2019 •

edited

Loading

stef204 commented May 22, 2019 •

edited

Loading

stef204 commented Jul 19, 2019 •

edited

Loading

stef204 commented Sep 7, 2019 •

edited

Loading

stef204 commented Sep 9, 2019 •

edited

Loading

stef204 commented Sep 12, 2019 •

edited

Loading

fosskers commented Sep 12, 2019 •

edited

Loading

fosskers commented Sep 13, 2019 •

edited

Loading

stef204 commented Sep 13, 2019 •

edited

Loading

stef204 commented Sep 15, 2019 •

edited

Loading

dpatti commented Apr 11, 2020 •

edited

Loading

fosskers commented Apr 13, 2020 •

edited

Loading

fosskers commented Jul 15, 2020 •

edited

Loading

mkoloberdin commented Jul 16, 2020 •

edited

Loading

fosskers commented Jul 17, 2020 •

edited

Loading