Forwarding at it got bounced (odd?)
------ Wiadomość oryginalna ------ Temat: Re: ppas, version numbers, releases and validation.linaro.org Data: Mon, 11 Jul 2011 11:35:46 +0200 Nadawca: Zygmunt Krynicki zygmunt.krynicki@linaro.org Firma/Organizacja: Linaro Adresat: Michael Hudson-Doyle michael.hudson@linaro.org Kopia: linaro-dev@linaro.org, paul.larson@linaro.org
W dniu 11.07.2011 06:34, Michael Hudson-Doyle pisze:
Hi Paul& Zygmunt (& others),
I spent a while today fixing a couple of bugs in lava-tool and in the packaging of lava-server, and was wondering what the process should be for getting them into the ~linaro-validation ppa and onto v.l.o (although there's no particular urgency in getting these precise fixes deployed, there will be changes that are more urgent).
In some sense these are basic debian packaging questions I guess. But my understanding of the process is that it should go like this:
If there are upstream changes, make a new release (update the version in __init__.py, tag the branch, make an sdist and upload it to pypi).
Agreed
Then (whether there is an upstream change or not) it should be uploaded to a PPA. I think the part here that I don't really get is basically how to use bzr build-deb in practice. But I've just found http://jameswestby.net/bzr/builddeb/user_manual/merge.html so I think I should read that first :)
I do bzr bd && bzr bd -S followed by some pbuilder commands. Look at .bzr-builder/ in each packaging branch.
Another question I have is around version numbers. Currently we're using version numbers like 0.2-0ubuntu0~zyga1. I don't really see why the "zyga" is in there :) I think simply dropping the zyga and using versions like 0.2-0ubuntu0~1 would be fine, or if we want to know who uploaded a particular version we can use things like 0.2-0ubuntu0~2mwhudson.
In short: ~zygaN is the thing we can increment. We should KEEP and perhaps change the name to ~lava (but this has to be coordinated as ~lava < ~zyga. There are three possible scenarios which this system correctly handles:
1) We need a new release, the pattern is always the same:
${UPSTREAM}-0ubuntu0~${PACKAGE}${PACKAGE_VERSION}
Where PACKAGE is the marker (currently zyga) and PACKAGE_VERSION is reset to 0 each time UPSTREAM changes.
2) Our packages land in Ubuntu. The version becomes:
${UPSTREAM}-0ubuntu${PACKAGE_VERSION}
Where PACKAGE_VERSION is >= 1 (this is important to differentiate from all of our internal releases
3) Our packages land in Debian. The version in Debian becomes:
${UPSTREAM}-${PACKAGE_VERSION}
The version in Ubuntu becomes/changes to:
${UPSTREAM}-${PACKAGE_VERSION}ubuntu${UBUNTU_PACKAGE_VERSION}
Where PACKAGE_VERSION is the one from Debian and UBUNTU_PACKAGE_VERSION is something Ubuntu developers can increment.
Finally, I think that we should be triggerhappy about releases, and so going through the above process shouldn't take very long. I guess lava-dev-tool can help here.
Agreed. I will look at this problem this week, hopefully I'll resurrect the package builder code.
Thanks ZK
On Mon, 11 Jul 2011 11:41:17 +0200, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:
Forwarding at it got bounced (odd?)
Yeah, my fault. I always forget the "lists." in linaro-dev@lists.linaro.org...
------ Wiadomość oryginalna ------ Temat: Re: ppas, version numbers, releases and validation.linaro.org Data: Mon, 11 Jul 2011 11:35:46 +0200 Nadawca: Zygmunt Krynicki zygmunt.krynicki@linaro.org Firma/Organizacja: Linaro Adresat: Michael Hudson-Doyle michael.hudson@linaro.org Kopia: linaro-dev@linaro.org, paul.larson@linaro.org
W dniu 11.07.2011 06:34, Michael Hudson-Doyle pisze:
Hi Paul& Zygmunt (& others),
I spent a while today fixing a couple of bugs in lava-tool and in the packaging of lava-server, and was wondering what the process should be for getting them into the ~linaro-validation ppa and onto v.l.o (although there's no particular urgency in getting these precise fixes deployed, there will be changes that are more urgent).
In some sense these are basic debian packaging questions I guess. But my understanding of the process is that it should go like this:
If there are upstream changes, make a new release (update the version in __init__.py, tag the branch, make an sdist and upload it to pypi).
Agreed
OK, I've been through this process now :)
Then (whether there is an upstream change or not) it should be uploaded to a PPA. I think the part here that I don't really get is basically how to use bzr build-deb in practice. But I've just found http://jameswestby.net/bzr/builddeb/user_manual/merge.html so I think I should read that first :)
I do bzr bd && bzr bd -S followed by some pbuilder commands. Look at .bzr-builder/ in each packaging branch.
Another question I have is around version numbers. Currently we're using version numbers like 0.2-0ubuntu0~zyga1. I don't really see why the "zyga" is in there :) I think simply dropping the zyga and using versions like 0.2-0ubuntu0~1 would be fine, or if we want to know who uploaded a particular version we can use things like 0.2-0ubuntu0~2mwhudson.
In short: ~zygaN is the thing we can increment. We should KEEP and perhaps change the name to ~lava (but this has to be coordinated as ~lava < ~zyga.
Yes, your parents gave you a very inconvenient name :-)
I agree with Paul's suggestion that we change to ~lava$N when we bump the upstream version (I don't expect many packaging only changes in general).
There are three possible scenarios which this system correctly handles:
- We need a new release, the pattern is always the same:
${UPSTREAM}-0ubuntu0~${PACKAGE}${PACKAGE_VERSION}
Where PACKAGE is the marker (currently zyga) and PACKAGE_VERSION is reset to 0 each time UPSTREAM changes.
- Our packages land in Ubuntu. The version becomes:
${UPSTREAM}-0ubuntu${PACKAGE_VERSION}
Where PACKAGE_VERSION is >= 1 (this is important to differentiate from all of our internal releases
- Our packages land in Debian. The version in Debian becomes:
${UPSTREAM}-${PACKAGE_VERSION}
The version in Ubuntu becomes/changes to:
${UPSTREAM}-${PACKAGE_VERSION}ubuntu${UBUNTU_PACKAGE_VERSION}
Where PACKAGE_VERSION is the one from Debian and UBUNTU_PACKAGE_VERSION is something Ubuntu developers can increment.
... only if there are changes between Debian and Ubuntu, right?
Although I don't really expect our packages to end up in Debian or Ubuntu for a while yet...
Finally, I think that we should be triggerhappy about releases, and so going through the above process shouldn't take very long. I guess lava-dev-tool can help here.
Agreed. I will look at this problem this week, hopefully I'll resurrect the package builder code.
Would be cool, but I guess we all need to understand what's going on underneath.
Cheers, mwh
On Tue, 12 Jul 2011 08:53:29 +1200, Michael Hudson-Doyle michael.hudson@canonical.com wrote:
Then (whether there is an upstream change or not) it should be uploaded
to a PPA. I think the part here that I don't really get is basically how to use bzr build-deb in practice. But I've just found http://jameswestby.net/bzr/builddeb/user_manual/merge.html so I think I should read that first :)
I do bzr bd && bzr bd -S followed by some pbuilder commands. Look at .bzr-builder/ in each packaging branch.
OK, I think I've got a handle on this now. Two points:
1) We should build for lucid and copy to the newer series (I assume). An alternative would be to use recipes.
2) It's a right pain in the backside when the PPA queue is 11-12 hours like it is now.
Cheers, mwh
-
Michael Hudson-Doyle -
Zygmunt Krynicki