#11206: pkgman update doesn't work anymore -------------------------+---------------------------- Reporter: axeld | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: 11330 Has a Patch: 0 | Platform: All -------------------------+---------------------------- Changes (by bonefish): * owner: bonefish => nobody * component: Kits/Package Kit => - General Comment: Replying to [comment:6 waddlesplash]: > But now we're stuck with: what should the package manager do when there are packages that cannot be upgraded? Should it deactivate these packages, or show an error and not continue? Unless I'm mistaken it already works such that if you ask to update a specific package and it cannot be updated because that would break another package, these two problem solutions (don't update or uninstall problematic package) are offered. However, if you ask to update all packages that can be updated -- as in this case -- not getting all the possible options is exactly what should happen, since eventually there might be an awful lot of them (due to mutually exclusive alternatives, additional (e.g. "patented") repositories that replace certain packages, etc.). Anyway, this is not a problem on the package manager side. The problem is that the package repository is in an inconsistent state. On a related note, we should develop a strategy what to do in case of updating a package to a binary incompatible version -- both regarding the packaging aspect (the package should probably get another name) and regarding the question what we want to happen with third-party software that uses such a package. -- Ticket URL: <https://dev.haiku-os.org/ticket/11206#comment:7> Haiku <https://dev.haiku-os.org> Haiku - the operating system.