Skip to content

GitLab

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

Closed
Open
Created May 11, 2015 by anonym@anonymMaintainer

Use 'set -u' in gettextized shell scripts

Originally created by @anonym on #9371 (Redmine)

So far we’ve been avoiding it, see e.g. this comment from config/chroot_local-includes/usr/local/bin/tor-browser:

# Do not "set -u", else importing gettext.sh dies
# with "ZSH_VERSION: parameter not set".

However, we can actually set -u as long as we set:

ZSH_VERSION="${ZSH_VERSION:-}"

before sourcing gettext.sh in each such script (see git grep "\. gettext\.sh" for a list of candidates).

Feature Branch: feature/9371-set-u-in-gettextized-shell-scripts

Parent Task: #9372

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tails_2.2
Milestone
Tails_2.2 (Past due)
Assign milestone
Time tracking
None
Due date
None