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

pkgin upgrade or full-upgrade isn't possible if one package is no longer availble #79

Closed
drscream opened this issue Oct 18, 2017 · 1 comment
Assignees

Comments

@drscream
Copy link

Environment

  • Uname: Darwin havanna.local 16.7.0 Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64 x86_64 i386 MacBookPro12,1 Darwin
  • Version: pkgin 0.9.4 for Darwin-13.4.0 x86_64 (using SQLite 3.20.1)
  • Repositories: https://pkgsrc.joyent.com/packages/Darwin/trunk/x86_64/All

Details

I'm using the trunk Darwin repository from Joyent. The repository provides rolling updates for packages. I mostly run an pkgin update and pkgin upgrade or pkgin fug, but if one package is no longer available on the remote site a upgrade or fug isn't possible.

Example

Update the local database:

 » pkgin update
processing remote summary (https://pkgsrc.joyent.com/packages/Darwin/trunk/x86_64/All)...
database for https://pkgsrc.joyent.com/packages/Darwin/trunk/x86_64/All is up-to-date

Run an upgade which result in the error vim-lang has no associated repository:

 » pkgin upgrade
calculating dependencies... done.
pkgin: vim-lang-8.0.1096 has no associated repository

A workaround or maybe regular way is to remove the package, in this case vim-lang to run an upgrade after that. This works fine!

Recommendation

pkgin could handle this case so it will inform the user if he like to remove the package and run the upgrade.

Also the best case would be the package will be removed exactly at the time when it's needed to be removed. Because otherwise if you remove the package at the beginning and wait before the upgrade you may have broken dependencies or missing features in one or more application.

@jperkin jperkin self-assigned this Aug 1, 2023
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
@jperkin
Copy link
Contributor

jperkin commented Aug 18, 2023

I think this was fixed earlier, but if not then it should be with 23.8.0.

@jperkin jperkin closed this as completed Aug 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants