Re: upstream + packaging + looms + lp != happiness
On Fri, 28 May 2010 11:44:08 Robert Collins wrote: > Its probably not had record done on it > doing 'bzr record' will do a commit sliced across the loom - it stores > the state of all the patches, merged into tip or not, and then when > you push, that recorded tip is what is pushed. If you take a look at the statements that Barry showed, he was doing a record, so most likely a bug. Tim -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: RFC on build from branch UI
On Tue, 02 Feb 2010 23:01:49 Michael Nelson wrote: > https://dev.launchpad.net/BuildBranchToArchiveUI Hi Michael, Firstly I think you have done an awesome job with the UI mock-ups. I talked with Michael Hudson today, and here is the summary of what came up. I'm not expecting you to answer all of these, but to give us notes to work from. We agreed that it is important to focus on the initial workflow of creating a new daily build of a branch into a PPA. We realised that we are missing the schedule information for the recipe itself in order to support daily builds properly. We are missing any form of UI mock-ups for the branch page itself. What changes on the branch page when a new build has been requested? How are we going to show builds in progress? What if the user wants to remove a daily build? Or just disable it? Is it really feasible to share recipes? When wanting to build into a PPA, what are we really accomplishing by choosing someone else's recipe? We are likely to have multiple recipes for each branch that is being built daily as we are going to target multiple distroseries. Am I right on this assumption? We will want some general recipe oriented views later, but what we have is a good start. Tim -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: UDD @ Portland
On Thu, 11 Feb 2010 15:18:30 Robert Collins wrote: > James Westby and I had some time together in Portland to talk about UDD > stuff. I just have two comments below: > - make downloading only some history easier/possible Shallow branches FTW. This would be awesome to focus on, and should be able to build on stacked branch work. Make bzr handle ghosts on mainline history, and enabling committing to a stacked branch. This would rock! > Another open issue is how looms might look in a colocated branch world: > would they be N branches with a metadata structure glueing them > together, or still an all-in-one structure? Specifically it would be > nice for threads to *version and propogate* some key concepts like 'bzr > pull from lp:myupstream or lp:my-redhat-patch-branch-import'. Changing looms to use co-located branches seems like a win to me. This would also bring looms and pipelines closer. I'd love to see a unified model here. Tim -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: hottest100 (was Re: Bazaar focus for 2.1 and 2.2)
On Wed, 06 Jan 2010 13:38:53 Jonathan Lange wrote: > >> So the associating development focus does not seem to have been done. > >> Again, I don't think I have access to actually change any of this stuff. > >> (And obviously neither do you, or you probably would have done it. :) > > > > Exactly. It will generally need someone in Registry Admin to do it for > > us. > > In general, it's the project "Maintainer" (and maybe the "Driver") who > can do that. You can find out who this is by looking at the project > overview page. > > Curtis, is this correct? Do you have any ideas as to how we can safely > open this up? I was talking with Curtis about this this morning. I have a branch ready to go that adds bazaar-experts and registry-experts. This will allow any CHR person to change the links rather than just a LOSA. Tim -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: hottest100 (was Re: Bazaar focus for 2.1 and 2.2)
On Wed, 06 Jan 2010 17:39:02 Jonathan Lange wrote: > On Wed, Jan 6, 2010 at 12:46 PM, Tim Penhey wrote: > > On Wed, 06 Jan 2010 13:38:53 Jonathan Lange wrote: > >> >> So the associating development focus does not seem to have been done. > >> >> Again, I don't think I have access to actually change any of this > >> >> stuff. (And obviously neither do you, or you probably would have done > >> >> it. :) > >> > > >> > Exactly. It will generally need someone in Registry Admin to do it for > >> > us. > >> > >> In general, it's the project "Maintainer" (and maybe the "Driver") who > >> can do that. You can find out who this is by looking at the project > >> overview page. > >> > >> Curtis, is this correct? Do you have any ideas as to how we can safely > >> open this up? > > > > I was talking with Curtis about this this morning. I have a branch ready > > to go that adds bazaar-experts and registry-experts. > > > > This will allow any CHR person to change the links rather than just a > > LOSA. > > CHR people aren't in bazaar-experts -- it's a tightly restricted team, > since it grants global branch write access. > > jml CHR people aren't in bazaar-experts, but they are in registry-experts. Tim -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: hottest100 (was Re: Bazaar focus for 2.1 and 2.2)
On Wed, 06 Jan 2010 13:38:53 Jonathan Lange wrote: > >> So the associating development focus does not seem to have been done. > >> Again, I don't think I have access to actually change any of this stuff. > >> (And obviously neither do you, or you probably would have done it. :) > > > > Exactly. It will generally need someone in Registry Admin to do it for > > us. > > In general, it's the project "Maintainer" (and maybe the "Driver") who > can do that. You can find out who this is by looking at the project > overview page. > > Curtis, is this correct? Do you have any ideas as to how we can safely > open this up? I was talking with Curtis about this this morning. I have a branch ready to go that adds bazaar-experts and registry-experts. This will allow any CHR person to change the links rather than just a LOSA. Tim -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Bazaar focus for 2.1 and 2.2
On Thu, 17 Dec 2009 12:01:08 you wrote: > 2009/12/17 Tim Penhey : > > I'm pretty sure there is a thinko in the algorithm somewhere. > > > > Based on the logs, it appears that it starts importing quickly, and > > rapidly slows down. > > > > I'd really like someone to look at this. > > Can you file a bug (against udd, maybe against other things) with log > snippets? Here are some relevant bugs: https://bugs.edge.launchpad.net/bzr-git/+bug/486570 - updating the git map and pulling revisions takes a very long time https://bugs.edge.launchpad.net/bzr-git/+bug/486636 - etckeeper fails to import from Git repo at git://git.kitenet.net/etckeeper https://bugs.edge.launchpad.net/bzr-git/+bug/486076 - memory leaks They would be a great start. Tim -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Bazaar focus for 2.1 and 2.2
On Thu, 17 Dec 2009 12:01:08 you wrote: > 2009/12/17 Tim Penhey : > > I'm pretty sure there is a thinko in the algorithm somewhere. > > > > Based on the logs, it appears that it starts importing quickly, and > > rapidly slows down. > > > > I'd really like someone to look at this. > > Can you file a bug (against udd, maybe against other things) with log > snippets? (Or, point out that I'm silly and there is a good bug > already.) Most people can't see those logs. Actually even logged out, I can see the logs. https://code.edge.launchpad.net/~vcs-imports/linux/trunk Here is the log file of one that failed after 10 days with EnvironmentError: [Errno 12] Cannot allocate memory http://launchpadlibrarian.net/36285369/linux-trunk-log.txt tim -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Bazaar focus for 2.1 and 2.2
On Thu, 17 Dec 2009 10:27:38 you wrote: > Tim Penhey wrote: > > On Thu, 17 Dec 2009 10:01:39 you wrote: > > Just to mention this is pretty much how all imports/conversions work. > > > >> 'starts quickly and [] slows down'. Both because the ancestry gets > >> longer, but tree size usually goes up significantly, etc. > > > > But one revision a minute? > > > > Tim > > Well, that was how long OOo used to take when we first started trying a > couple years ago. > > It would tend to happen if you do something that is O(tree) instead of > O(changes). And certainly if there is something that is O(ancestry). > > Usually we do quite a bit better. I think importing the linux kernel via > fast-import is in the 1000/min range. Slowing down to... 500/min? I > think Qt is much slower at around 40/min, but still not 1/min. Also considering that there is 150k revisions to import. As far as memory leaks go, the imports creep up to 1 gig rss and often get killed by the LOSAs. Tim -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Bazaar focus for 2.1 and 2.2
On Thu, 17 Dec 2009 04:23:24 Francis J. Lacoste wrote: > On December 15, 2009, Martin Pool wrote: > > I just had a good talk with James about what the Bazaar team could do > > to help UDD move forward. We are making progress on some particular > > bugs but the analysis feels a bit inchoate. So my theory is that we > > will be more efficient if we pick a clearer focus to do first. > > > > We talked about: > > > > * vcs imports - very visible so could be good, but not a pressing problem > > now > > Well, the linux kernel import is still not working. And that's with the > recent fixes to bzr-git by Jelmer and the improved memory usage by John. > So there are things to improve there. > I'm pretty sure there is a thinko in the algorithm somewhere. Based on the logs, it appears that it starts importing quickly, and rapidly slows down. I'd really like someone to look at this. Tim -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: your thoughts wanted on bzr team UDD focus
On Tue, 08 Dec 2009 14:49:32 Aaron Bentley wrote: > Martin Pool wrote: > > What I'm trying to get at here is the next level of detail of what we > > can be doing to help with bzr builder, imports and bugs? If a major > > cause of failing imports is lack of git submodule support, that would > > be a strategic thing for us to resolve. > > If you look at mwhudson's research: > > https://devpad.canonical.com/~mwh/values-sorted.txt > > Only five failures are due to the lack of submodule support. > > However, we can ignore svn issues because we're switching to bzr-svn. > (We hope that will solve many of our problems, but whichever problems > remain will be *different*) Well, bzr-svn can't support svn:externals properly until bzr has nested trees as well. Personally I'd like to see externals of some form supported natively in bzr. Tim -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: your thoughts wanted on bzr team UDD focus
On Tue, 01 Dec 2009 14:19:13 Martin Pool wrote: > I'd like to get a sanity check from UDD people on what the Bazaar team > is going to do for our 2.1 release, which will have a feature freeze > in February and go into Karmic. > > From the previous threads, it seems that the main large things we need > to do are: > > * get more code imports working -- investigation of failure causes is > continuing > * support imports of git submodules or svn externals -- this is not moving > yet This makes me very happy. Tim -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
Re: Things to graph for package-of-the-day work
On Wed, 18 Nov 2009 03:13:49 Barry Warsaw wrote: > On Nov 16, 2009, at 8:02 PM, Jonathan Lange wrote: > > In fact, you'd probably know better than I: If Launchpad had access to > > the branch for a source package and the branch for its latest > > upstream, what could we do that would help the average Ubuntu > > developer? > > Something that occurred to me this morning. > > As an upstream maintainer > I want Launchpad to automatically create a branch and apply a patch > sitting in a bug report, linking the bug report to this automatic branch > So that I can review and merge it easily if it makes sense and applies > cleanly, or reject the patch if it does not. > > -Barry Yes, we have talked about this exact use case. It is on the cards :) -- ubuntu-distributed-devel mailing list ubuntu-distributed-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
