> Sorry, I again mis-interpreted. What happens is that it works when my
> .bzr-builddeb/default.conf has
>
> export-upstream = lp:~serge-hallyn/user-mounts/devel
>
> Then, if I remove that line, it continues to work, but that's because
> the .orig.tar.gz has already been saved in the parent directory. If I
> erase the .orig.tar.gz, the build-area, and don't have the above line,
> then actually it doesn't work.
Right. That "works", but it's not building a native package as you are
requesting with --native.
> Ah, then it is NOT a bug, but end-user bug. I still had
> Merge = True
> in my default.conf (as had been suggested I do on irc)
Right, an inconsistent configuration has been specified. We should
either recognise this and complain, have a priority scheme to disambiguate,
or change the configuration so that only valid states can be specifed (or all
three).
I appreciate that you are keen to work out how to use the tool, but that
doesn't detract from the fact that you had these problems is a deficiency
in the tool that I want to fix. This isn't a place where confusion arising from
poor code, UI or documentation is your fault :-)
> Sorry, I again mis-interpreted. What happens is that it works when my default. conf has
> .bzr-builddeb/
>
> export-upstream = lp:~serge-hallyn/user-mounts/devel
>
> Then, if I remove that line, it continues to work, but that's because
> the .orig.tar.gz has already been saved in the parent directory. If I
> erase the .orig.tar.gz, the build-area, and don't have the above line,
> then actually it doesn't work.
Right. That "works", but it's not building a native package as you are
requesting with --native.
> Ah, then it is NOT a bug, but end-user bug. I still had
> Merge = True
> in my default.conf (as had been suggested I do on irc)
Right, an inconsistent configuration has been specified. We should
either recognise this and complain, have a priority scheme to disambiguate,
or change the configuration so that only valid states can be specifed (or all
three).
I appreciate that you are keen to work out how to use the tool, but that
doesn't detract from the fact that you had these problems is a deficiency
in the tool that I want to fix. This isn't a place where confusion arising from
poor code, UI or documentation is your fault :-)
Thanks,
James