possibility of regulation (and turnoff) for pkg_has_updates / monopolization of pkg by pkgng via pkg-version #91
Comments
olevole
pushed a commit
to olevole/puppet-pkgng
that referenced
this issue
Feb 6, 2019
Using of ports tree (even with the presence of INDEX-XX) to determine outdated packages is incredibly slow. In addition ports may have the updated version while pkg still not. Since we work with pkg and not the ports we need to fix the source to repo Fixes for issue voxpupuli#91
|
That is a lot of packages. My largest box has 263. +1 to this change. |
olevole
pushed a commit
to olevole/puppet-pkgng
that referenced
this issue
Feb 13, 2019
related to issue voxpupuli#91
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For system with lot of packages execution of:
https://github.com/xaque208/puppet-pkgng/blob/2.1.1/lib/facter/pkg_updates.rb#L8:
for pkg_has_updates facts always lock pkg for a long time and user can do anything with pkg. The problem is the slow 'pkg version' execution when ports not installed (and fetchindex not performed).
For example, on a PC with desktop role (KDE5) and 1746 packages this operation may take ~ 20 minutes (no ssd, one hdd).
More details: freebsd/pkg#1739
it would be nice to regulate this behavior and be able to turn off. Or try to find another solution, for example pkg dry-run:
pkg upgrade -Unqor
pkg version -RUThe text was updated successfully, but these errors were encountered: