-
Notifications
You must be signed in to change notification settings - Fork 41
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
Provide useful progress during upgrade #95
Comments
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this issue
Aug 16, 2023
## Version 23.8.0 (2023-08-16) This is the biggest overhaul of pkgin yet! As well as fixing many bugs, pkgin 23.8.0 runs "pkgin -n upgrade" over 2,000x faster on a test system with 12,663 packages installed compared to 22.10.0 (1.4 seconds vs over 54 minutes). * Large overhaul of dependency resolution code, fixing many upgrade issues, providing significant performance improvements, and improving code and logic readability. * Add support for SUPERSEDES. * Fix install and removal ordering. * Improve and fix handling of "keep" packages, using "pkg_add -A" to correctly install automatic packages rather than applying keep or unkeep flags afterwards. * Output improvements, sorting packages alphabetically and providing a simple progress counter. Fix unwanted output that could end up mixed with package paths in "pkgin export". * Correct handling of +REQUIRED_BY for reverse dependencies, fixing DEPENDS that use alternate matches. * Many internal code improvements, memory leaks plugged, and compiler warnings eradicated. Fixes at least the following issues: * NetBSDfr/pkgin#10 * NetBSDfr/pkgin#44 * NetBSDfr/pkgin#79 * NetBSDfr/pkgin#95 * NetBSDfr/pkgin#97 * NetBSDfr/pkgin#110 * NetBSDfr/pkgin#113 * NetBSDfr/pkgin#128 * NetBSD PR#51465 * NetBSD PR#56683
Fixed in 23.8.0, all installs and downloads now have counters. |
Works well, thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running pkgin to upgrade 250 packages (which can easily happen when switch from one branch to the next), you see a lot of lines like
but there is no way to guess how far along in the upgrade one is.
One idea would be to add "[x/y]" before the
upgrading
orinstalling
part (package numberx
from a total ofy
packages that are modified bypkgin
in this process).The text was updated successfully, but these errors were encountered: