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

repoctl status -u vs -m #19

Closed
allspark opened this issue May 12, 2016 · 8 comments
Closed

repoctl status -u vs -m #19

allspark opened this issue May 12, 2016 · 8 comments

Comments

@allspark
Copy link

Hi,
i just updated to the new version of repoctl (thx) but ;)

when i execute repoctl status -m it lists all (but 2 packages) and with status -u it lists only the 2 missing packages

python-pypdf2: !aur python-ruffus: !aur python2-imaging: !aur python2-lz4: !aur repoctl: !aur
(only a shorted list)

repoctl version 0.14 (6 October 2015)

thanks

@cassava
Copy link
Owner

cassava commented May 16, 2016

Hi @allspark, thanks for the report, I'll look into it as soon as possible.

@cassava
Copy link
Owner

cassava commented May 17, 2016

Hi @allspark, the semantics of repoctl changed significantly 😬 when I switched over to a different command line library. So perhaps I should have written up a list of the changes from the previous version.

For the status subcommand, there is no -u option though.
Can you tell me what you are expecting to see?

@allspark
Copy link
Author

oh sorry, i meant status -a (not -u)

with -a i see (atm) 3 packages
with -m i see a lot of line like repoctl: !aur

@cassava
Copy link
Owner

cassava commented May 17, 2016

You're right, -m should imply -a.

@cassava
Copy link
Owner

cassava commented May 17, 2016

I correct myself: -m should result in AUR being consulted for all the packages.

@cassava
Copy link
Owner

cassava commented May 17, 2016

Btw, you can combine -a and -m: repoctl status -am.

@cassava cassava closed this as completed May 17, 2016
@allspark
Copy link
Author

ah thx 👍

@cassava
Copy link
Owner

cassava commented Jun 2, 2016

@allspark, I released 0.15, which contains this fix among others.

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

No branches or pull requests

2 participants