Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #24152 Explicitly ask sudo to set HOME when calling gitolite
    Actions
    Infos
    #24152
    Thomas Gerbet (tgerbet)
    2021-11-19 10:57
    2021-11-18 09:08
    25696
    Details
    Explicitly ask sudo to set HOME when calling gitolite

    On systems where the sudoers configuration file has been customized, the Defaults always_set_home directive might not be present. This cause issues when interacting with gitolite because gitolite uses the HOME env variable to find its repositories.

    SCM/Git
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Thomas Gerbet (tgerbet)
    Closed
    2021-11-19
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #23428 Tuleap Releases 13.3 Delivered 2021-08-12 17:17 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #24152

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/93/24493/1' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD a2d717f69a
    User avatar Lorentz Romain (lorentzr) , 2021-11-19 10:56
    request #24152: Explicitly ask sudo to set HOME when calling gitolite 122f70da09
    User avatar Thomas Gerbet (tgerbet) , 2021-11-18 09:13
    Referenced by request #24152

    Artifact Tracker v5

    rel #23428 13.3

    Other

    gerrit #24493
    Display settings

    Follow-ups

    User avatar
    Lorentz Romain (lorentzr)2021-11-19 10:57

    integrated to Tuleap 13.2.99.45

    • Status changed from Under review to Closed
    • Connected artifacts
    • Close date set to 2021-11-19
    User avatar
    Thomas Gerbet (tgerbet)2021-11-18 09:20

    Patch under review: gerrit #24493.

    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    • Status changed from Under implementation to Under review