#13672: Package sets can get into a valid but un-activatable state.
--------------------------------+----------------------------
Reporter: kallisti5 | Owner: nobody
Type: bug | Status: new
Priority: normal | Milestone: Unscheduled
Component: Kits/Package Kit | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 1 | Platform: All
--------------------------------+----------------------------
Comment (by jessicah):
That's not what appears to have happened, looking at packages.txt. I think
what's happened is that `pkgman` has updated all haiku packages except for
haiku/haiku_devel.hpkg, which are still at their original version.
Because all the other packages have upgraded, it probably looked like it
did a full upgrade, when instead it did a partial upgrade.
{{{
# not upgraded
./haiku-r1~alpha4_pm_hrev51174-1-x86_64.hpkg
./haiku_devel-r1~alpha4_pm_hrev51174-1-x86_64.hpkg
# upgraded
./haiku_loader-r1~alpha4_pm_hrev51365-1-x86_64.hpkg
./makefile_engine-r1~alpha4_pm_hrev51365-1-any.hpkg
}}}
And only when you do a `pkgman full-sync` does it then a) force the latest
haiku package to be installed, and b) install/upgrade/remove other
packages that prevented the haiku package from being upgraded in the
normal case. So it doesn't appear to be a bug, but it is non-obvious.
Perhaps what we need to do is have `pkgman` issue warnings for packages
that have newer versions available for updating, but can't because of
dependency issues, and suggest to run `pkgman full-sync` in this case.
--
Ticket URL: <https://dev.haiku-os.org/ticket/13672#comment:4>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
