-
Notifications
You must be signed in to change notification settings - Fork 904
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
outdated - every now and then lists packages with identical versions #843
Comments
I wonder if it is #580. |
No, not the same thing. I'm guessing that will show up in the logs. Same address. I think this may be a bug? |
Typically due to not being able to find a package. |
+1 this for me:
notice |
Any of these in the list pinned? I think attempting to find out what is causing the warning would be best. |
These packages all share that they are on the community repository as well. |
@ferventcoder PS C:\Users> clist "yammer-notifier" -all
Chocolatey v0.10.0 Business
0 packages found.
PS C:\Users> clist yammer-notifier -all
Chocolatey v0.10.0 Business
0 packages found.
PS C:\Users> clist yammer -lo
Chocolatey v0.10.0 Business
yammer-notifier 1.2.0.851
1 packages installed.
PS C:\Users> clist yammer -all
Chocolatey v0.10.0 Business
0 packages found. I think the issue may lie w/ exempted packages after analyzing this a bit further. And to answer your q in more detail: PS C:\Users> choco pin list
Chocolatey v0.10.0 Business
notepadplusplus|6.9.2
paint.net|4.0.6
RoboForm|7.9.10.0
SourceTree|1.9.1.1 |
I'm guessing something in the chocolatey.org codebase doesn't necessarily update the index when an exempted package is updated? So then it waits for the cache timeout to occur. |
"0 packages" != "cache timeout" ;) but that's a separate issue |
Each package gets updated in the index individually and works to update caches for that package specifically. |
choco outdated
every now and then lists packages with identical versions
We've added the switch for |
Every now and then
choco outdated
lists packages with identical versions.Here is an example, happening just now, where
ack
andAtom
are listed as outdated, with the same versions forcurrent
as well asavailable
:Admittedly, there is also a warning about the same two packages. However, it is confusing: there is no explanation about what caused the so-called "warnings".
choco outdated
should only list really outdated packages......or it should add more details about why it thinks it should print a warning message.
The text was updated successfully, but these errors were encountered: