-
-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pacman 6.0 Alpha Throws aura #698
Comments
I'd also recommend you throw warnings on unknown options instead of erroring out. The rust crate already does this so it's sorted there. |
@Morganamilo Where is that crate? I tried searching crates.io but could not find, or did you just compile colin/rust branch? |
@Morganamilo means that this problem is auto-solved in Aura's on-going Rust Port. |
This may be related to #697. Either way I will fix both today in the Haskell, thanks for reporting. |
|
Ah, I thought you meant aura crate. I see that aura and paru use the one you linked. Thanks. |
No but aura does use it for the rust rewrite: Line 20 in f1c6233
|
@Mallchad can you paste into here the |
Here is my exact pacman.conf https://paste.rs/rAO
For the sake for redundancy the intended line, and when I first noticed it
the line was
`ParallelDownloads=5` and pacman was more than happy with it before.
Here is the source of the pacman version that uses this option (and doesn't
complain)
http://allanmcrae.com/2020/12/pacman-6-0-0alpha1/
Here is an example of one of the errors
```
m-arch-recoil% aura -Ss test
aura: Failure There was some failure.
```
I should probably mention that this is `aura-bin`
Here's an older version of `aura-bin`. 3.1.9-1 based on the
AUR versioning to be precise,
that has a slightly different output
```m-arch-recoil% aura -Ss test
Unable to parse your pacman.conf file.```
…On Tue, 9 Mar 2021 at 23:52, Colin Woodbury ***@***.***> wrote:
@Mallchad <https://github.com/Mallchad> can you paste into here the
ParallelDownloads fields *exactly* as you have it in your pacman.conf?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#698 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK5GWWNTPZUHA3QZMWMCHSTTC2RBNANCNFSM4Y3OVTXA>
.
|
Excellent, then my recent patch should have taken care of that too. I will make a release today. |
|
It works as normal! Thankyou!
Thankyou for making aura :D
…On Wed, 10 Mar 2021 at 23:13, Colin Woodbury ***@***.***> wrote:
3.2.4 has been released.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#698 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK5GWWO5ZLDHSV6YHT2JOFLTC7VHPANCNFSM4Y3OVTXA>
.
|
Hi, I realize this isn't a problem you could possibly have had to deal with up to now and I'm only getting it because
I'm running very "bleeding edge" packages here and there.
Basically with the new pacman and parallel downloads the slight difference in the
pacman.conf
file seems to throw offaura
So I run something like this
aura -Ss test
And get an output something like this
aura: Failure There was some failure.
I tried some old builds and slightly different versions and eventually got an error like
"Failed to parse pacman.conf"
And sure enough the problem goes away with the latest version if I comment the
ParallelDownloads
line.Basically I was just wondering if anything like this has happened before, or there is some suggestion for a quick fix or
a cause that I could make work with to prod at things to make it not throw a fit with the config.
Thanks.
The text was updated successfully, but these errors were encountered: