On Mon, Aug 10, 2009 at 4:20 PM, James Westby<james.wes...@canonical.com> wrote: > Celso Providelo wrote: >> Resurrecting an old question: do you know why building remote branches >> is not functional in jaunty ? `bzr bd -r REV BRANCH_URL` > > I didn't know it was broken, could you file a bug with the trace please?
Sure, https://bugs.edge.launchpad.net/bzr-builddeb/+bug/411642 >> Also, how can we cope with the feature-set variation of bzr-builddeb >> across the supported suites ? Should we: >> >> 1. Always build branches on the development chroot >> 2. Use the chroot for the target suite + officially backported > bzr-builddeb >> 3. Use the chroot for the target suite + an PPA overlay with the >> semi-official bzr-builddeb backports > > 4. Use a separate chunk of code that just takes the parts you need and > want to support, rather than all the functionality. > > I was assuming you would work that way, but we can work on packages if > that is what you would like. Packages are much nicer, IMO. First because it's easier to install 'packages' in a chroot, second because having packages available will help people to reproduce problems that we may find during this journey. We would go for a mix of 3 & 4 I think, hosting the minimal/supported version of bzr-builddeb in a special PPA. -- Celso Providelo <celso.provid...@canonical.com> IRC: cprov, Jabber: cp...@jabber.org, Skype: cprovidelo 1024D/681B6469 C858 2652 1A6E F6A6 037B B3F7 9FF2 583E 681B 6469 _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
