[00:00] <micahg> build-essential is installed on the buildds
[00:59] <TheLordOfTime> which means it isnt needed as a build dep
[00:59] <TheLordOfTime> although as a dependency for some packages, it may need it.
[01:09] <TheLordOfTime> ... okay, perhaps i should have just requested hte backport to precise, and killed two birds with one stone, but since i didn't, should I remove quantal backports as a target on https://bugs.launchpad.net/quantal-backports/+bug/1085760?
[01:10] <TheLordOfTime> since i already have a separate quantal backport bug.
[01:10] <TheLordOfTime> (which is https://bugs.launchpad.net/quantal-backports/+bug/1085731)
[02:21] <micahg> TheLordOfTime: sure, that's fine
[07:09] <alo21> hi
[07:09] <alo21> I have an issue upgrading doc-ubuntu
[07:10] <alo21> I got this error: ERROR: Cannot find ~/debian/www/webwml/english to regenerate the sources. Please read the TODO.
[07:10] <alo21> can someone help me please?
[07:52] <dholbach> good morning
[07:53] <sladen> morgen
[07:54] <dholbach> hi sladen
[15:16] <psusi> rather than subscribe ubuntu-sponsors to upload an SRU to quantal-proposed, would the UDD thing to do be to propose merging a branch into quantal-proposed instead?
[15:16] <tumbleweed> the quantal-proposed branch often doesn't exist
[15:16] <tumbleweed> (it only exists if there was a previous SRU)
[15:17] <tumbleweed> and if you propose merging into quantal, then only tech-board members can change the status of your merge proposal
[15:17] <tumbleweed> also, SRUs need tracking bugs anyway.
[15:23] <psusi> have bug, just wondering if I need to subscribe ubuntu-sponsors to check out the bzr branch, build the source deb, and upload it to quantal-proposed, or if there's a UDD way to do that
[15:23] <psusi> in this case, grub does appear to have a quantal-proposed branch
[15:24] <tumbleweed> a merge proposal is the UDD way
[15:24] <psusi> so propose merge to quantal, or quantal-proposed?
[15:25] <tumbleweed> -proposed
[15:25] <micahg> the UDD way is useless for SRUs for packages that don't have a -proposed branch unless you like the bzr workflow since your changes will be lost
[15:26] <psusi> what do you mean?
[15:26] <micahg> s/changes/iterations/ (the whole point of the VCS)
[15:26] <tumbleweed> the uploader can't create the -proposed branch, so your commits will never be merged. The uploaded source package will be imported
[15:28] <psusi> ahh... but in this case, someone has created the proposed branch already, so just propose merge to it?
[15:28] <tumbleweed> sure
[15:28] <psusi> ok
[16:00] <alo21> hi