=== signed8bit is now known as signed8bit_Zzz === signed8bit_Zzz is now known as signed8bit === signed8bit is now known as signed8bit_Zzz === signed8bit_Zzz is now known as signed8bit [02:29] I see a lot of x86{,_64} builders in the "cleaning" state for a pretty long time... is that an issue or just coincidence? https://launchpad.net/builders [02:42] Ionic: There's an issue with one of our build clouds. They should be slowly recovering. [02:42] Okay :) === signed8bit is now known as signed8bit_Zzz === signed8bit_Zzz is now known as signed8bit === maclin1 is now known as maclin [14:33] hi guys, is this perhaps fixed in the latest code, but just not pushed to pypi? https://bugs.launchpad.net/lazr.restfulclient/+bug/1695392 [14:33] Ubuntu bug 1695392 in lazr.restfulclient "cannot install under python 3" [Undecided,Confirmed] [14:40] ahasenack: very likely. it's on my to-do list [14:41] I hit it just because a lint check wanted to import an exception from lazr.restfulclient.errors [14:41] from lazr.restfulclient.errors import ClientError [19:25] do recipes support building separate packages that are subfolders in one repo? (e.g. the repo contains pkg1/ and pkg2/ which in turn have debian/ folders) [19:50] no, sorry [19:51] if I were faced with that situation I'd probably try using tools offered by the relevant revision control system to extract something rooted at the proper place that I could then build, or just do it without recipes [20:57] fair enough, thanks!