| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
Select latest version of package (if it is not pinned), and print
error if it cannot be installed due to other dependencies.
Together with --available, it selects the latest package which is
present at least in some repository.
This also fixes few solver issues with ordering of package selection
that got quite apparent with this flag. Namely, we cannot "lock"
a package until it's reverse dependencies are locked or not all of
the solver flags are propagated properly.
|
|
|
|
|
|
mostly useful for reboot, when all packages are not available.
|
|
- try harder to not change anything during self-upgrade
- also honor locking to packages that where earlier used in
merging common dependencies
- clarify upgrade applet help messages
|
|
Implementing basic dependency handling, install_if and awareness
of pinning.
|
|
It is internal bug, but don't segfault on it. Fixes #1576.
|
|
Solver will now never report partial solution where a conflict
constraint is not satisfied. The is because with --force we might
install the partial solution; and if conflicted packages were to
be installed we might have extra trouble.
|
|
name state could get overwritten later, so we can't use that when
generating the changeset.
|
|
* upgrade needs explicit check so we don't try self-upgrade
(which would print additional messages on screen)
* add can fix problems, so check against the new world
* merge the code in few places
|
|
regression from upgrade to the new solver system.
|
|
allow per-name solver flags to be inheritable, and use them in
self-upgrade, add -u and the fix applet. this gives more familiar
behaviour for the upgrades.
|
|
the only bit of information needed in solver commit is the "hard"
topology sorting information for trigger ordering. fixes a bug in
"apk del" which uses the state pointers to do intermediate
calculations between solution solving and commit.
|
|
fixes #738
|
|
Use it to avoid self-upgrade loops in case something fails during
the initial upgrade attempt.
|
|
|
|
|
|
|
|
still todo:
- 'fix' is missing
- 'del -R' does not work
- 'upgrade' does not do self-upgrade first
... and a lot of testing.
|
|
|
|
The db parameter to apk_state_commit is not needed so we remove it.
|
|
This allows us to get apk-tools dependencies get reset at proper
time in world. As a bonus, it reduces code amount.
|
|
.. instead of the longer flag combo.
|
|
Also re-exec's apk-tools to perform rest of the upgrade using
the new apk-tools. This allows handling of new apk-tools features
properly. Fixes #140.
|
|
The version now needs to be initialized atom always, since it's
dereferenced in various places.
|
|
We we can upgrade rest of system just fine then.
|
|
|
|
Print more information why installation changeset calculation failed.
Fixes #187.
|
|
Doing "apk add file.apk" adds a versioned dependency to allow
downgrading, and sticky version. Most often this is to install
single packages from newer repository. So it would make sense
to reset them to non-versioned if doing:
apk upgrade -a
fixes #346
|
|
so user can override trusted keys directory and repositories file.
|
|
previously they might have been skipped on certain situations.
this also fixes some other reverse dependency enforcements and
implements new "pending" state for locked name.
|
|
And add some more verbosity to the help message.
|
|
That will make the upgrade prefer packages available in repositories.
This is good if one want's to downgrade packages by removing an experimental
repository. Or to force re-install of locally built vs. repository version
when the package version are same, but checksum is different. Fixes #51.
|
|
Currently just goes through all world dependencies and updates them
where possible (ref #51).
|
