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
  • #8237

Closed
Open
Opened Dec 04, 2017 by Kaarle Ritvanen@kunkkuMaintainer

auto-install rules not always honored

Package py2-babel has an auto-install rule that it should be installed when both python2 and py-babel are present. However, py2-babel is purged on installation of apache2-mod-wsgi. This happens when using the latest stable repositories (v3.7) but not on edge currently. Please see the attached log for details.

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

  • Changesets:
    • Revision 8e7fd3e0 by Timo Teräs on 2017-12-12T13:16:52Z:
solver: fix potential install_if processing failure, fixes #8237

In discovery phase, there was logic to not process packages
multiple times. However, that logic failed to account the package's
depth and install_if state for the name being processed. This
caused install_if processing failure in certain topologies of the
dependency graph. Adds also a test case that should catch this
issue reliably.
  • Revision 685795f2 by Timo Teräs on 2018-01-09T07:52:56Z:
solver: fix potential install_if processing failure, fixes #8237

In discovery phase, there was logic to not process packages
multiple times. However, that logic failed to account the package's
depth and install_if state for the name being processed. This
caused install_if processing failure in certain topologies of the
dependency graph. Adds also a test case that should catch this
issue reliably.

(cherry picked from commit 8e7fd3e06f300bd76b659db1164da1ee12f16870)
  • Revision 11a523d2 by Timo Teräs on 2018-01-09T08:06:01Z:
solver: fix potential install_if processing failure, fixes #8237

In discovery phase, there was logic to not process packages
multiple times. However, that logic failed to account the package's
depth and install_if state for the name being processed. This
caused install_if processing failure in certain topologies of the
dependency graph. Adds also a test case that should catch this
issue reliably.

(cherry picked from commit 8e7fd3e06f300bd76b659db1164da1ee12f16870)
(cherry picked from commit 685795f24c7d37298c363bb70dc98e3a95ef4c81)
  • Uploads:
    • install-if-issue.txt
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: alpine/apk-tools#8237