Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 938
    • Issues 938
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 29
    • Merge requests 29
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #12551

Set up a process to keep our fork of GNOME Shell's .desktop file and GDM's .session file up-to-date

Originally created by @intrigeri on #12551 (Redmine)

As noticed on #12364 (comment 43634), our own config/gdm-shell-tails.desktop (in Tails Greeter’s Git repo) tends to be behind /usr/share/applications/org.gnome.Shell.desktop as shipped in Debian. This can potentially cause serious issues, so IMO we need a process to keep it more up-to-date than what we’ve done in the past. I don’t know what’s the best way to do that, but at least a ticket per Tails release based on the next version of Debian would be a good start; completing said ticket would require creating the next one. But there are probably better ways to do so, e.g. generate our own .desktop file dynamically at package build time from the upstream one.

Same for gdm-tails.session, see f5e00d2d.

Feature Branch: feature/16912-move-greeter-to-main-git-repo+force-all-tests

Related issues

  • Related to #16288 (closed)
  • Related to #16951 (closed)
  • Blocked by #16912 (closed)
Edited May 15, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking