Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S strongswan
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • DebianDebian
  • strongswan
  • Merge requests
  • !10

Change default to charon-systemd instead of strongswan-starter

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Lucas Kanashiro requested to merge kanashiro/strongswan:change-default-to-charon-systemd into debian/master Jun 17, 2020
  • Overview 6
  • Commits 7
  • Pipelines 3
  • Changes 6

This MR makes strongswan runtime depends on charon-systemd instead of strongswan-starter from now on. This will enforce users to use the new systemd unit service file instead of the legacy one (check this comment from one of the upstream maintainers) in new installations. Nevertheless, users will still be able to use strongswan-starter if they want. A summary of the proposed changes:

  • Rename strongswan-starter to strongswan-starter-legacy. Keep the strongswan-starter as a transitional package.
  • Make strongswan runtime depend on charon-systemd

FWIW the package builds fine and autopkgtest is still happy.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: change-default-to-charon-systemd