=== jamesh__ is now known as jamesh === ahayzen_ is now known as ahayzen [23:33] trainguards: choo choo [23:35] justinmcp: all aboard! [23:36] heya [23:36] was wondering if you could help with Oxide again robru ? [23:37] justinmcp: could do. You need it copied? Where from/to? [23:38] yup, from Oxide master to 2165 [23:41] justinmcp: cab you link me? On mobile [23:41] https://bileto.ubuntu.com/#/ticket/2165 [23:42] justinmcp: i mean link the source ppa [23:43] there's no ppa.. the source is at https://code.launchpad.net/~oxide-developers/oxide/+git/oxide/+ref/master [23:45] justinmcp: can you put together a changelog at least? [23:46] I don't want Oxide released outside it's usual cycle.. I need the MH part released [23:46] There's always this catch-22 type thing here [23:47] Oxide has a regular cadence, one option is just to wait until the relevant change makes release, then resubmit that ticket [23:47] justinmcp: that source tree doesn't even have a debian directory, i can't do anything with that. I need you to prepare the package you want as you want it, then I'll upload that for you. [23:48] justinmcp: I'm not really following you here. You want to do a release but you don't want to do a release. [23:48] Yes, wonderful isnt it.. I need a changed Oxide to get that MH fix to pass [23:49] but Oxide has its own release cycle [23:49] I think I'll just wait, I've already waited a while to get this through [23:49] sorry for bothering [23:49] justinmcp: well we work on the level of debs. If there's a bug in the deb, make a new deb with a fix, and release it. [23:50] justinmcp: sorry if I'm sounding combative, happy to help, just need you to prepare the deb you want [23:51] robru: Nope, I understand where you're coming from - I just have competing processes to deal with [23:51] I am going to wait for the new release [23:51] Alright [23:51] enjoy your day :) [23:51] You too!