=== maclin1 is now known as maclin [09:50] I have uploaded a source package and then found out that my key was missing. A day later, I have uploaded the key now. [09:50] On https://help.launchpad.net/Packaging/UploadErrors it says there is a "PPA build status page" but I cannot find it for my ppa. [09:50] dput says the package is already there, but I don't know where to look for the build status. [09:52] Oh, never mind. I think I found the problem. [11:46] hanno: If LP rejected your upload due to a missing key, it won't automatically reprocess the upload once the key appears - you'll need to reupload for it. [11:46] Yes, thank you. I fixed it by now. [11:46] Now I'm with a different problem. Is it okay to ask packaging questions here or is there a better channel? [11:47] * hanno is fighting with .deb [11:47] hanno: I think there's #ubuntu-packaging or some such [11:47] It's not dreadful to ask here, but there may be better places. [11:47] ok, thx. === dpm is now known as dpm-afk [13:50] cjwatson: nobody in ubuntu-packaging. Dead channel? [13:53] hanno: I don't know, sorry [13:53] I did say "or some such", not remembering exactly [13:55] hanno: Feel free to ask, anyway, we can find somewhere to redirect you if it ends up being too much [14:19] What I'm looking for is a good tutorial on how to populate the debian/patches directory. [14:19] I can get a simple package ready by now, but don't know how to patch the original source tree. [14:25] hanno: perhaps https://wiki.debian.org/UsingQuilt will help [14:27] or https://raphaelhertzog.com/2012/08/08/how-to-use-quilt-to-manage-patches-in-debian-packages/ [14:28] thx. === dpm-afk is now known as dpm === BradCrittenden is now known as Guest42648 [16:46] "source has expired binaries" [16:46] what's this? [17:18] sergio-br2: Context is a helpful thing [17:19] sergio-br2: But you're probably trying to copy a package that hasn't been published anywhere for a while and so has had its binaries garbage-collected. [17:19] hey cjwatson [17:20] yup, I was trying to copy [17:20] from toolchain PPA [17:20] gcc 4.9.3 from trusty [17:24] sergio-br2: I haven't managed to pick out the exact cause, but my bet is that, although most of it is still published, one of the gazillion binaries produced by gcc-4.9 has been superseded by one of the other gcc-* source packages in that same PPA [17:24] sergio-br2: and as a result LP no longer has all the binaries from that source and so can't do a copy-with-binaries [17:24] sergio-br2: if you need that specific version then the only thing you can do is to copy-without-binaries and rebuild it [17:25] weird, I can see the binaries... [17:25] there's gcc-4.9 and gcc 5.0 [17:25] different packages [17:28] Right, but one of the many individual binaries probably has the same name in a higher-versioned source package and thus was taken over by it [17:56] ok, let's try to build then [17:56] will take a day heh [22:41] I'm reading the documentation for https://help.launchpad.net/API/Webhooks and it looks like I cannot use webhooks unless I'm in a special group and the event is a VCS push? Is that still correct? [22:58] sigmavirus24: we just lifted the team restriction today - I've edited the docs to remove that bit [22:58] sigmavirus24: VCS push and merge proposal changes [23:02] cjwatson: okay, I was hoping for issue event changes on a project [23:02] Thanks for the info though cjwatson [23:02] sigmavirus24: please do file bugs for specific other use cases you have [23:03] sigmavirus24: it's not too difficult for us to extend webhooks to more objects now that we've done the hard work of building the infrastructure for it [23:06] cjwatson: bugs.launchpad.net/launchpad is the right place for that, correct? (My first time filing a bug against Launchpad) [23:06] sigmavirus24: yep [23:07] thanks cjwatson! === sigmavirus24 is now known as sigmavirus24_awa