=== chihchun_afk is now known as chihchun [02:44] it seems I've been caught in a timezone failure [02:44] so I asked here: https://answers.launchpad.net/launchpad/+question/660750 [02:45] I'll leave irssi open, feel free to answer either there or here; that said I don't have a notification system, so I'll check back every few hours === JanC_ is now known as JanC === JanC_ is now known as JanC === JanC is now known as Guest67213 === JanC__ is now known as JanC === JanC__ is now known as JanC [07:02] "Launchpad encountered an internal error during the following operation: emailing a code review comment. It was logged with id OOPS-5014c34142512235b399ec82f1577680. Sorry for the inconvenience." [07:02] https://oops.canonical.com/?oopsid=OOPS-5014c34142512235b399ec82f1577680 [07:02] * rbasak is somewhat amused that Launchpad managed to email him about a problem emailing him === ePierre is now known as ePierre-afk [16:11] wgrant, even if we remove all z/vm builders; can we keep like three of them around? [16:11] wgrant, we may need z/vm builder in launchpad, for livefs builders, for a project we are estimating. [21:51] Question about preserving PATH like I do with `debuild --preserve-envvar PATH -sd -b`. Is there a way to ask for this in launchpad? [22:08] pivotal: No. If you need some particular elements in PATH then you should modify PATH as necessary in your packaging (e.g. debian/rules). [22:09] Ok, thanks, will do. It will be a little repetitive, but at least we have the answer :) [22:11] pivotal: You wouldn't be able to rely on the builder having anything in particular in PATH anyway. [22:11] Other than the obvious things that will already be present when your package is built. [23:11] xnox: Not really. Can you explain your requirements in more detail? [23:11] Is it just that bootloader userspace installation tools don't like running on different types of block devices?