You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the various Linux package manager upgradeable tables to not have the ability to know if a package update is being held back for any reason. There are some more commands we can shell out to for this data.
An example is apt's apt-cache policy {package} to get the pinning priorities and distribution properties of the package.
The text was updated successfully, but these errors were encountered:
Since pinning a package is end user controlled, I'm not sure we should skip the check creation for it
This was mostly to ignore phased updates, but I was thinking of making a check option to ignore pinned/phased updates similar to the homebrew check option.
How do you anticipate using that data?
Since pinning a package is end user controlled, I'm not sure we should skip the check creation for it
This was mostly to ignore phased updates, but I was thinking of making a check option to ignore pinned/phased updates similar to the homebrew check option.
I can see it as an option... Mostly I'm expecting linux users to quickly figure out that they can simply pin things and then skip needing to upgrade
Currently the various Linux package manager upgradeable tables to not have the ability to know if a package update is being held back for any reason. There are some more commands we can shell out to for this data.
An example is apt's
apt-cache policy {package}
to get the pinning priorities and distribution properties of the package.The text was updated successfully, but these errors were encountered: