•  
      request #44813 Wrong SVN access file after project import when the the project doesn't use SVN default permissions
    Infos
    #44813
    Aurélien Tisné (atisne)
    2025-09-10 17:01
    2025-09-10 17:01
    46515
    Details
    Wrong SVN access file after project import when the the project doesn't use SVN default permissions

    After importing a project that does not use the default SVN permission (and redefine a [/] section), the generated SVN access file is like:

    # BEGIN CODENDI DEFAULT SETTINGS - DO NOT REMOVE
    [groups]
    
    [/]
    * =
    @members = rw
    # END CODENDI DEFAULT SETTINGS
    [/]
    * = 
    @members = r
    

    Which is not a valid file.

    Here, the source project has deactivated the Use default permissions option to replace permissions by the custom definition:

    [/]
    * = 
    @members = r
    

    Steps to reproduce:

    As a project administrator,

    1. On a project using an SVN repository, goto the SVN repository 'Access control' tab
    2. Uncheck the option 'Use default permissions'
    3. Set new custom permissions
    4. Save a new version of the permission

    As a site admin,

    1. Export this project using src/utils/php-launcher.sh src/utils/export_project_xml.php
    2. Import this archive on a new instance using tuleap import-project-xml
    3. Check the content of the file /var/lib/tuleap/svn_plugin/<project_id>/<repo_name>/.SVNAccessFile

    Note: The file src/common/xml/resources/project/svn-definition.rng does not seem to support the option 'Default permissions'.

    Import | Export
    16.11
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    New
    Empty
    Attachments
    Empty
    References
    References list is empty