Auto-add correct "-v" argument to "bzr builddeb"

[Daniel Hahler]

"bzr builddeb -S" should default to using "-v" and adding the version from the last known upload (in the same "series"?)

So, when doing "bzr bd -S" for a merge from Debian, it includes all changes since the last ubuntu revision, automatically.

Currently you have to look at debian/changelog to find the version since when changes should get added/used.

Drawback: you have to explicitly use "-v $previous_version" to get the previous default behavior.

I think it should look at the last tags, which also "bzr mark-upoaded" uses to get the last (relevant) upload. This should be as easy as looking for the last Ubuntu upload.

[Jelmer Vernooij (jelmer)]

On Thu, 2010-04-15 at 18:47 +0000, Daniel Hahler wrote:
> "bzr builddeb -S" should default to using "-v" and adding the version
> from the last known upload (in the same "series"?)
>
> So, when doing "bzr bd -S" for a merge from Debian, it includes all
> changes since the last ubuntu revision, automatically.
>
> Currently you have to look at debian/changelog to find the version since
> when changes should get added/used.

> Drawback: you have to explicitly use "-v $previous_version" to get the previous default behavior.
>
> I think it should look at the last tags, which also "bzr mark-upoaded"
> uses to get the last (relevant) upload. This should be as easy as
> looking for the last Ubuntu upload.
A series is not the same thing as an archive. It is possible to upload
to different archives but the same series.

For example, it may be possible for me to upload one revision of a
package to the Maverick series in a PPA and then upload the next
revision to the Ubuntu Maverick archive.

Cheers,

Jelmer

[Robert Collins (lifeless)]

I'm not clear why you want this?

[Daniel Hahler (blueyed)]

It's simply to have the full list of changes in the *_source.changes file automatically.

Since I often forget to add "-v $LAST_UBUNTU_VERSION" myself, this would help me, at least.

[James Westby (james-w)]

Hi,

I'd like to see this, but I'm not convinced it can be done correctly.

I'd love to be proved wrong :-)

Thanks,

James

[Dimitri John Ledkov (xnox)]

On 16 April 2010 00:24, Robert Collins <email address hidden> wrote:
> I'm not clear why you want this?
>

Such that all correct bug reports will be closed for example if there
were a few debian uploads, you do a merge with an ubuntu revision and
then upload to launchpad and debian maintainer closes LP:# bugs. I new
developer who was only been sponsored before might miss that....

Me too would like to see this done right ;-)

Because I maintain my packages both in debian & ubuntu and some
uploads that make it to ubuntu don't make to debian and vice-versa
(very rarely but do) so I will need granularity with respect to upload
series.

And you have corner case where last ubuntu version is higher than one
of the new merged debian revisions and has LP: # in it.

Including everything -v $FIRST_EVER_VERSION in bzr history won't do it
either because you will accidently close reopened bugs which were
"fixed" with Closes:# by a old upload where bug was still present.

So really we will have to do $ bzr missing lp:$distro/$series/$package
and use python-apt magic to hand-craft the changes file using changlog
entries from introduced entries.

[Daniel Hahler (blueyed)]

For starters:
$ dpkg-parsechangelog --format rfc822 --count 1000 | grep '^Version: ' | grep ubuntu | head -n2 | tail -n1

I have not understand the bit about series from above, but that might get added to the pipeline, e.g. filtering out anything containing "ppa".

[Daniel Hahler (blueyed)]

The above is missing " | sed 's/^Version: //'"

[Jelmer Vernooij (jelmer)]

On Fri, 2010-05-28 at 18:56 +0000, Daniel Hahler wrote:
> For starters:
> $ dpkg-parsechangelog --format rfc822 --count 1000 | grep '^Version: ' | grep ubuntu | head -n2 | tail -n1
>
> I have not understand the bit about series from above, but that might
> get added to the pipeline, e.g. filtering out anything containing "ppa".
I'm still not convinced this is the right way to go, but in either case
this code seems more in place in e.g. debuild, there isn't anything
bzr-specific about it.

Cheers,

Jelmer

[Jelmer Vernooij (jelmer)]

Does --package-merge perhaps do what you want?

[Daniel Hahler (blueyed)]

Not interested in this bug anymore, sorry.
Feel free to just close it.