[01:51] <Grorco> Hi guys, I'm not a professional by any means, but I love open source and know my way around python a bit. I'd like to try to help with debugging but not sure how to get started. Can anyone help me getting set up?
[01:52] <blahdeblah> Grorco: Hang around for a while; the main devs are in EU time zones at the moment, so it might take a while for them to respond.
[01:54] <Grorco> blahdeblah, cool thanks :)
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
[10:10] <cjwatson> Grorco: Have you already looked through the relevant-to-you bits of https://dev.launchpad.net/ ?
[14:44] <oSoMoN> is there an ETA for the availability of the arm* builders?
[14:47] <cjwatson> Maaaaaaaaybe today.  But we'll see.
[14:48] <oSoMoN> cjwatson, that's good news, thanks!
[14:49] <oSoMoN> cjwatson, can I request an exception for https://launchpad.net/ubuntu/+source/chromium-browser/63.0.3239.132-0ubuntu1 ?
[14:56] <cjwatson> oSoMoN: Yep, primary archive stuff is usually OK.  Done.
[14:57] <oSoMoN> cheers
[16:27] <arpallet> Hi All,
[16:27] <arpallet> I am trying to upload equivs-build to PPA. Is it possible ?
[16:27] <arpallet> I see there is a bug related to it, https://askubuntu.com/questions/784796/ppa-upload-of-custom-kernel-package
[16:27] <arpallet> Is it fixed ? Is there a support now to upload equivs-build
[16:42] <cjwatson> arpallet: You can upload anything provided it's in the form of a source package.  We are never going to permit uploading binary packages directly
[16:42] <cjwatson> (also, askubuntu posts are not bugs)
[16:43] <cjwatson> Anyway, there seems to be an answer there that you could use
[16:43] <cjwatson> Ah, though I guess equivs-build is really not very much like a kernel package
[16:44] <arpallet> cjwatson: Sorry i pasted a wrong link there, this is the bug i was talking about https://bugs.launchpad.net/ubuntu/+source/equivs/+bug/1374090
[16:44] <ubot5> Ubuntu bug 1374090 in equivs (Ubuntu) "Add source building (for upload to a PPA)" [Undecided,Invalid]
[16:44] <cjwatson> arpallet: So, we're never going to allow you to upload the result of equivs-build directly, but you can just run debuild -S in the directory that it leaves behind
[16:47] <arpallet> equivs-build requires only control file, so i was having only control file for the package. Now as you said if i need to run debuild -S, there should be changelog and other required files. Is my understanding right ?
[16:49] <cjwatson> equivs-build creates those and 
[16:49] <cjwatson> Ah, but unfortunately it doesn't appear to leave the result behind
[16:50] <cjwatson> Sorry, you'll have to either write an actual source package yourself, or hack equivs-build to not delete its build directory, or experiment with the suggested patch to equivs-build in that bug
[16:50] <cjwatson> Since equivs-build is a single file, you could just copy it to your home directory and apply the patch locally
[16:51] <arpallet> Thanks @cjwatson, i will try that
=== epod is now known as luk3yx