Cannot nest-part into an existing directory

Bug #1644640 reported by Dmitry Shachnev
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
git-build-recipe
Fix Released
Undecided
Unassigned

Bug Description

We had a problem while trying to write a Git recipe for gnome-flashback daily builds. The upstream repository contains a submodule. As git-build-recipe does not clone the submodules, we tried to work around that by using nest-part. However nest-part complains when a target directory exists and is not a Git repository. In our case, the target directory is empty.

Example: https://code.launchpad.net/~ubuntu-gnome-flashback/+recipe/gnome-flashback-daily. To work around this bug, we currently have a dummy branch where that submodule is removed, and merge it before nest-parting. This is a huge hack, so a better fix on git-build-recipe side is needed.

Related branches

Revision history for this message
Khurshid Alam (khurshid-alam) wrote :

Old problem. lp:771568 (for bzr recipes)

nest-part can not work if target directory already exists. Other option is to dump into a directory which doesn't exist and then use "run cp" command to copy it into proper path. Although I am not sure if git build recipes can execute run.

Revision history for this message
Colin Watson (cjwatson) wrote :

git-build-recipe (0.3.4) unstable; urgency=medium

  [ Dmitry Shachnev ]
  * Make pull_or_clone work when the target dir exists and is empty. This
    allows one to use the nest command as a replacement for submodules
    (LP: #1644640).

 -- Colin Watson <email address hidden> Tue, 29 Nov 2016 13:41:32 +0000

Also rolled out to the Launchpad build farm.

Changed in git-build-recipe:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.