Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
apk-tools
apk-tools
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 61
    • Issues 61
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 15
    • Merge Requests 15
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • alpine
  • apk-toolsapk-tools
  • Issues
  • #7250

Closed
Open
Opened Apr 27, 2017 by Ariadne Conill@kaniiniContributor

apk upgrade --available produces incomplete upgrade transactions if a package is replaced with another package

As a result of the linux-grsec to linux-hardened transition, it has been observed that in some cases it is required to run apk upgrade twice to fully make the jump.

I think the problem is that we need to verify the solution again after committing it, this allows splitting complex moves (such as linux-grsec direct package to linux-hardened [linux-grsec provider]) while making sure apk behaves sanely.

We already do similar when we upgrade apk-tools, so it seems like something we could make more genericish.

(from redmine: issue id 7250, created on 2017-04-27, closed on 2019-02-25)

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: alpine/apk-tools#7250