On 05/18/2010 10:55 AM, Andy Whitcroft wrote:
> On Tue, May 18, 2010 at 10:25:58AM -0600, Tim Gardner wrote:
>> git://kernel.ubuntu.com/rtg/ubuntu-lucid.git lts-backport-maverick
>> See helper script debian.maverick/etc/update-from-maverick-master
>> for automation help. Thoughts?
> I think we decided that although the source package name is unique, the
> binary package names are not. Therefore if you just mush this to
> linux-maverick in lucid-proposed we will end up building binary packages
> in lucid and maverick with the same names:
> I believe this will cause issues in the archive. I think were leaning
> towards appending ~lucid1 to the end of the version number as well to
> stop this?
Yeah, I was just looking at that. We definitely need to make the binary
package names unique.
> I do wonder if we should just ignore the ABI tracking always for these
> kernels. We know if we needed a bump we have one as we handled it for
> the original maverick version. If we were willing to do that I recon
> we actually could just make this automated.
I guess that makes sense. In that event the script could just create the
ABI directory and populate it with ignore files. That gets rid of 2
command line options.
> I see you copy a lot of stuff over to debian.maverick, I assume this
> is to maintain the branch config is in debian.<branch> semantics? But I
> do not see you changing debian.env to match. Perhaps we could do this
> more like:
> git mv debian.master debian.maverick
> echo "DEBIAN=debian.maverick">debian/debian.env
> git add debian/debian.env
Actually, the initial backport commit 'UBUNTU: [Config] Initial Maverick
LTS backport' does the topic branch BS that'll never change. I may go
back and clean up some of that patch and pare it down to the bare
minimum. There are also still a few abstraction gotchas in debian.master
that I had to munge. I'll send you some patches for that eventually.
Tim Gardner firstname.lastname@example.org
kernel-team mailing list