Skip to content
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

rua upgrade sometimes responds with non-AUR packages #155

Closed
amcooper opened this issue Mar 25, 2021 · 5 comments
Closed

rua upgrade sometimes responds with non-AUR packages #155

amcooper opened this issue Mar 25, 2021 · 5 comments
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@amcooper
Copy link

rua upgrade sometimes tells me about non-AUR packages. Today, for example:

$ rua upgrade
Package                    Current Latest 
haskell-haddock-library1.9 1.9.0-3 NOT FOUND, ignored 

This is a regular (non-AUR) package that was actually installed as a dependency of another regular package.

@vn971
Copy link
Owner

vn971 commented Mar 25, 2021

@amcooper this is intended behavior in fact, make the user aware of this no-more-installable package. If you'd design it for yourself, what would be the action you'd like to see? Completely ignore the package? Ask? Error out? List but ignore for actual upgrade?

@amcooper
Copy link
Author

Completely ignore. I'm expecting rua to concern itself only with packages from the AUR.

Here's the whole flow:

$ rua upgrade                     
Package                    Current Latest 
haskell-haddock-library1.9 1.9.0-3 NOT FOUND, ignored 

Do you wish to upgrade them? [O]=ok, [X]=exit. o

And the following AUR packages will need to be built and installed:


Proceed? [O]=ok, Ctrl-C=abort. o

$

And then the same again, if I run it again. If rua wants to make me aware of this package's status, I suppose that's fine. If rua can't upgrade this package, it shouldn't offer me that option.

@vn971 vn971 added bug Something isn't working good first issue Good for newcomers labels Mar 25, 2021
@vn971
Copy link
Owner

vn971 commented Mar 25, 2021

@amcooper understood! Seems like an obvious bug actually, understood it now, acknowledging.

Would you want / have time to fix it?

@amcooper
Copy link
Author

It would be a while before I could get to it, but I'll fix it if no one else has by that time.

@vn971
Copy link
Owner

vn971 commented Mar 26, 2021

@amcooper hey, no worries, I'll pick this up, it's a very small change that I know where to do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants