Project

General

Profile

Bug #16607

FTBFS with "repository '/amnesia.git/.git/modules/submodules/aufs4-standalone' does not exist"

Added by segfault 6 months ago. Updated 6 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Build system
Target version:
-
Start date:
03/23/2019
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

Today when I tried to build devel it failed with

+ git clone --shared /amnesia.git/.git/modules/submodules/aufs4-standalone
fatal: repository '/amnesia.git/.git/modules/submodules/aufs4-standalone' does not exist

I was able to fix it by changing the permission of the submodules directories and the parent directories from 700 to 755:

chmod 755 .git/modules .git/modules/submodules .git/modules/submodules/*

This seems to be caused by df8a338ea6e078113ef6a03d7e3fbb3ffc7467d1. We should somehow make sure that the vagrant user actually has read access to the submodules directory. I don't know why it had permission 700 on my system.


Related issues

Related to Tails - Bug #16476: Allow building a branch using unpublished Git submodule changes Resolved 02/21/2019
Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed

History

#1 Updated by segfault 6 months ago

I'm having this issue repeatedly, the permissions are somehow changed between builds. I didn't spend any time trying to debug this. My revised command to fix this is

chmod -R go+rX .git/modules/submodules

#2 Updated by intrigeri 6 months ago

  • Related to Bug #16476: Allow building a branch using unpublished Git submodule changes added

#3 Updated by intrigeri 6 months ago

Indeed, looks like #16476 caused this regression. Perhaps our Rakefile should set the permissions that the rest of our build system needs.

#4 Updated by intrigeri 6 months ago

  • Category set to Build system

#5 Updated by intrigeri 5 months ago

Also available in: Atom PDF