dailybuild source in subdirectory of branch

[Jared Szechy]

I have a repo branch that i have mirrored in Launchpad that I am trying to setup a daily build. The problem is that the source directory of the package is a subdirectory in the branch. When building locally it's no problem because I can just change to that directory. However with launchpad's bzr-builder it does everything from the top directory in the branch.

My current build recipe is:

    # bzr-builder format 0.3 deb-version {debupstream}-{revno}-{revno:packaging}
    lp:kegbot
    nest-part packaging lp:~szechyjs/kegbot/kegbot_debian debian debian

Ideally I would use `lp:kegbot/pykeg` but this is not possible in bzr.

Is there a easy way I can build the package in the kegbot/pykeg directory, by setting it up in my recipe or some kind of source directory variable in the rules file?

I've asked around on various support sites about this, people say what I'm trying to accomplish is not supported. Is this true that this is not possible? If so can a feature be added to implement this?

[James Westby (james-w)]

On Wed, 13 Jul 2011 19:26:12 -0000, Jared Szechy <email address hidden> wrote:
> Public bug reported:
>
> I have a repo branch that i have mirrored in Launchpad that I am trying
> to setup a daily build. The problem is that the source directory of the
> package is a subdirectory in the branch. When building locally it's no
> problem because I can just change to that directory. However with
> launchpad's bzr-builder it does everything from the top directory in the
> branch.
>
> My current build recipe is:
>
> # bzr-builder format 0.3 deb-version {debupstream}-{revno}-{revno:packaging}
> lp:kegbot
> nest-part packaging lp:~szechyjs/kegbot/kegbot_debian debian debian
>
> Ideally I would use `lp:kegbot/pykeg` but this is not possible in bzr.
>
> Is there a easy way I can build the package in the kegbot/pykeg
> directory, by setting it up in my recipe or some kind of source
> directory variable in the rules file?
>
> I've asked around on various support sites about this, people say what
> I'm trying to accomplish is not supported. Is this true that this is
> not possible? If so can a feature be added to implement this?

It is not currently supported.

Where would you want the debian directory to be placed? Presumably at
kegbot/pykeg/debian?

Thanks,

James

[Jared Szechy (szechyjs)]

Yes, I would like the debian directory to be placed at kegbot/pykeg/debian.

The package is entirely within the kegbot/pykeg directory though, so I'm not sure how to get this to build properly.

[James Westby (james-w)]

On Wed, 13 Jul 2011 20:57:32 -0000, Jared Szechy <email address hidden> wrote:
> Yes, I would like the debian directory to be placed at
> kegbot/pykeg/debian.
>
> The package is entirely within the kegbot/pykeg directory though, so I'm
> not sure how to get this to build properly.

We could extend the format to allow specifying a root directory for the
base branch, and everything would then be done relative to that.

I'm not sure how well it would work for some things, and it wouldn't
support the pristine-tar integration if you have multiple packages in a
tree, but would work for you.

Thanks,

James

[Jared Szechy (szechyjs)]

It would be great if support for this would be added.

Thanks,
Jared

On Thu, Jul 14, 2011 at 1:23 PM, James Westby <email address hidden>wrote:

> On Wed, 13 Jul 2011 20:57:32 -0000, Jared Szechy <
> <email address hidden>> wrote:
> > Yes, I would like the debian directory to be placed at
> > kegbot/pykeg/debian.
> >
> > The package is entirely within the kegbot/pykeg directory though, so I'm
> > not sure how to get this to build properly.
>
> We could extend the format to allow specifying a root directory for the
> base branch, and everything would then be done relative to that.
>
> I'm not sure how well it would work for some things, and it wouldn't
> support the pristine-tar integration if you have multiple packages in a
> tree, but would work for you.
>
> Thanks,
>
> James
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/810098
>
> Title:
> dailybuild source in subdirectory of branch
>
> Status in bzr-builder:
> New
>
> Bug description:
> I have a repo branch that i have mirrored in Launchpad that I am
> trying to setup a daily build. The problem is that the source
> directory of the package is a subdirectory in the branch. When
> building locally it's no problem because I can just change to that
> directory. However with launchpad's bzr-builder it does everything
> from the top directory in the branch.
>
> My current build recipe is:
>
> # bzr-builder format 0.3 deb-version
> {debupstream}-{revno}-{revno:packaging}
> lp:kegbot
> nest-part packaging lp:~szechyjs/kegbot/kegbot_debian debian debian
>
> Ideally I would use `lp:kegbot/pykeg` but this is not possible in bzr.
>
> Is there a easy way I can build the package in the kegbot/pykeg
> directory, by setting it up in my recipe or some kind of source
> directory variable in the rules file?
>
> I've asked around on various support sites about this, people say what
> I'm trying to accomplish is not supported. Is this true that this is
> not possible? If so can a feature be added to implement this?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/bzr-builder/+bug/810098/+subscriptions
>

[Mario Fetka (mario-fetka)]

Yes i am having the same situation now.
+1
for the subdir support