Problem using bzr-build recipe after GIT migration

Asked by Jasem Mutlaq

We recently migrated my project to Github. Since you can only import the repo all at one (vs. subversion which you can select what to import), we ended up with the complete repo here:

Now the problem is that we cannot figure out a way to make a recipe for each package as before.

Previously, the recipe for the libindi main package was:

# bzr-builder format 0.3 deb-version {debversion}+r{revno}.{revno:packaging}
nest-part cmake_module lp:~mutlaqja/libindi/cmake_modules . cmake_modules
nest-part packaging lp:~mutlaqja/libindi/packaging libindi debian

Where lp:~mutlaqja/libindi/trunk points to the libindi contents. Now, since everything is in lp:libindi, we can't make something like:

# bzr-builder format 0.3 deb-version {debversion}+r{revno}.{revno:packaging}
nest-part cmake_module lp:libindi/cmake_modules . cmake_modules
nest-part packaging lp:libindi/debian libindi debian

The above is simply not accepted. lp:libindi is the primary repo containing information for everything, and we have 15+ packages built from this one source now. We need a way so that the contents of the desired directory are fetched, and then the cmake_modules and debian directories are both fetched into the same directory.

How can this be done?

Question information

English Edit question
Launchpad itself Edit question
No assignee Edit question
Solved by:
Jasem Mutlaq
Last query:
Last reply:
Revision history for this message
Jasem Mutlaq (mutlaqja) said :

We resolved the problem by changing the debian stuff a bit