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

yay v12.0.1 regression: query outdated packages has additional output #2057

Closed
jonpas opened this issue Apr 3, 2023 · 5 comments · Fixed by #2060
Closed

yay v12.0.1 regression: query outdated packages has additional output #2057

jonpas opened this issue Apr 3, 2023 · 5 comments · Fixed by #2060

Comments

@jonpas
Copy link

jonpas commented Apr 3, 2023

Affected Version

yay v12.0.1 - libalpm v13.0.2

Describe the bug

yay -Qum in yay v12 outputs additional information which breaks yay -Qum | wc -l used for getting a count of outdated packages.

Reproduction Steps

  1. Run yay -Qum | wc -l.
  2. Observe output being at least 2 even if no packages are outdated.

Expected behavior

yay -Qum to output only outdated packages.

Output

v11 example output:

$ yay -Qum
:: Searching AUR for updates...
:: Searching databases for updates...
 -> linux: ignoring package upgrade (6.2.8.arch1-1 => 6.2.9.arch1-1)
 -> linux-headers: ignoring package upgrade (6.2.8.arch1-1 => 6.2.9.arch1-1)
mergerfs 2.34.1-1 -> 2.35.0-1
yay-bin 11.3.2-1 -> 12.0.1-1

v12 example output:

$ yay -Qum
mergerfs 2.34.1-1 -> 2.35.0-1
yay-bin 11.3.2-1 -> 12.0.1-1
@Jguer
Copy link
Owner

Jguer commented Apr 3, 2023

wouldn't yay -Qumq | wc -l the correct command to use?

@jonpas
Copy link
Author

jonpas commented Apr 3, 2023

I tend to agree, although most people I see on various forums are using yay -Qum.

I did try yay -Qumq as well, but in cases where you have ignored packages, it also produces output:

$ yay -Qumq
 -> linux: ignoring package upgrade (6.2.8.arch1-1 => 6.2.9.arch1-1)
 -> linux-headers: ignoring package upgrade (6.2.8.arch1-1 => 6.2.9.arch1-1)

which it did not before v12.

@Jguer
Copy link
Owner

Jguer commented Apr 3, 2023

I've checked against the output of pacman. I would not advice piping pacman -Qu neither but I see why it's being done.
Will fix it

@Jguer
Copy link
Owner

Jguer commented Apr 3, 2023

#2060 should fix it and I'll release another patched version to avoid having changes pile up.

@jonpas
Copy link
Author

jonpas commented Apr 3, 2023

Thanks!

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

Successfully merging a pull request may close this issue.

2 participants