Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fuss-client fuss-client
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • FUSS
  • fuss-clientfuss-client
  • Issues
  • #375

Closed
Open
Created Aug 07, 2017 by Paolo.Dongilli@Paolo.DongilliOwner

Sostituzione di libpam-foreground con libpam-ck-connector

Mi sono accorto che fuss-client installa

libpam-foreground
che però è un dummy package che installa

libpam-ck-connector

Propongo di sostituire il dummy package con libpam-ck-connector in
https://work.fuss.bz.it/projects/fuss-client/repository/revisions/master/entry/ansible/roles/ldap/tasks/main.yml
ed nelle dipendenze di

fuss-client-dependencies

PS: me ne sono accorto perché ieri ho voluto provare ad installare ed eseguire fuss-client su di una Debian 9.1 (https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-9.1.0-amd64-xfce.iso) ed a parte le due piccole modifiche di cui sopra, l’aggancio al server è andato liscio come l’olio. Meraviglioso!

Assignee
Assign to
Time tracking