Failed to parse .SRCINFO
Getting this on several packages:
% aura -A ros-noetic-desktop
aura :: Determining dependencies...
aura :: There were multiple errors during dependency resolution.
- Failed to parse .SRCINFO: /home/user/.cache/aura/packages/ros-noetic-smach/.SRCINFO
- Failed to parse .SRCINFO: /home/user/.cache/aura/packages/ros-noetic-rqt-py-common/.SRCINFO
- Failed to parse .SRCINFO: /home/user/.cache/aura/packages/ros-noetic-rqt-topic/.SRCINFO
- Failed to parse .SRCINFO: /home/user/.cache/aura/packages/ros-noetic-qt-gui-py-common/.SRCINFO
- Failed to parse .SRCINFO: /home/user/.cache/aura/packages/ros-noetic-rqt-plot/.SRCINFO
% aura -A bauerbill
aura :: Determining dependencies...
aura :: There were multiple errors during dependency resolution.
- Failed to parse .SRCINFO: /home/user/.cache/aura/packages/python3-xcgf/.SRCINFO
- Failed to parse .SRCINFO: /home/user/.cache/aura/packages/python3-xcgf/.SRCINFO
- Failed to parse .SRCINFO: /home/user/.cache/aura/packages/python3-xcpf/.SRCINFO
- Failed to parse .SRCINFO: /home/user/.cache/aura/packages/python3-xcgf/.SRCINFO
- Failed to parse .SRCINFO: /home/user/.cache/aura/packages/python3-memoizedb/.SRCINFO
- Failed to parse .SRCINFO: /home/user/.cache/aura/packages/python3-xcpf/.SRCINFO
- Failed to parse .SRCINFO: /home/user/.cache/aura/packages/python3-xcpf/.SRCINFO
There are occasionally git clone failures when many are attempted at the same time. I haven't yet implemented a retry policy but plan to for such cases. Usually if you try again it works. If you notice that a directory (say, python3-xcgf) has appeared in ~/.cache/aura/packages/ but it is empty, then it will need to be deleted manually. Note that aura check can also detect such failed clones.
Any thoughts?
I don't have any empty directories in ~/.cache/aura/packages.
% pwd
/home/user/.cache/aura/packages
% tree | wc -l
431
% tree --prune | wc -l
431
aura check output: https://paste.xinu.at/UH1M
edit: I no longer have the errors with 4.0.4, but the diagnostics should be improved. "Failed to parse .SRCINFO" could mean any number of issues (missing file, unexpected fields, wrong indentation, etc)
I have noticed two things:
- There is currently no retry policy for lookups.
- For packages with large, AUR-based dependency graphs that highly inter-depend, it may be that a lookup failed on one branch but succeeded on another, which generates spurious error messages.