[06:34] ls [11:35] Wut [19:17] "The reference within the target repository that the source will be merged into." <- huh? is this supposed to be "master" ? or what? [19:19] Yes, we need a proper combined picker to make that less unclear [19:19] On the to-do list [19:19] Probably also slightly less nerdview; I should probably have written "The branch name ..." at least [19:21] yeah, if it said branch, it would have been clearer for non-git people like me [19:23] There is a slight technical difference but it's mostly irrelevant [19:23] And even given that technical difference branch is probably more accurate ... [19:23] cjwatson: in theory, does the merge tool handle any ref? [19:24] Yeah, but it's unlikely to be meaningful to target a reference that isn't a branch [19:24] cjwatson: ack, was just curious [19:24] (Well, it needs to be at least a reference that resolves to a commit ...) [19:24] cjwatson: yeah, from an actual MR process perspective, branches (or tags, i guess, although riskier) are the best well-defined references, it seems like [19:25] riskier in the sense they are more likely to move potentially [19:25] Targeting tags is probably fairly silly. LP itself doesn't actually land the merge anyway, and good luck convincing a human maintainer to merge something onto a tag [19:25] yeah :) [19:26] well, i presume when the drop-down gets implemented, it will probably be a list of branches [19:26] Indeed [22:34] does http://feeds.launchpad.net/ubuntu/latest-bugs.atom now require a login to get the feed? [22:34] or did the URL change? [22:35] hum. Works for fuel [22:35] hggdh: I think that's a bug. My guess is that there's something private in that collection that the feed is failing to filter out. [22:37] cjwatson: ah. Even if I try to login (thru the login/register button at the right) it fails because it gets to http://feeds.launchpad.net/ubuntu/latest-bugs.atom/+login [22:37] A little difficult to tell what since I don't actually have a way to log into that feed and feeds.launchpad.net doesn't have my usual debugging tools ... [22:37] and this is a 404 [22:37] Indeed [22:37] Hm, the feed *tries* to filter out private bugs. [22:38] it did succeed previously. #-bugs-announce has been feeding off it for some years now [22:39] Yeah, it will probably work again once data cycles a bit [22:40] good enough. Last successful feed was at 15:28 UTC, so I am guessing the cycle is a bit larger than 7 hours :-) [22:40] My guess is that one of the bugs in the topmost batch is either assigned to a private team or has a task on a private project [22:40] mwanwhile I will stop looking at the feeder code, and just restart the beast [22:45] Ah yes, here we go [22:45] There are several bugs in the first batch that are assigned to a private team [22:45] hggdh: Could you please file a bug about this? It shouldn't be desperately hard to fix [22:48] cjwatson: against which package/component? [22:49] hggdh: Launchpad itself [22:49] ack, on it [22:53] lib/lp/bugs/feed/templates/bug.pt should probably have a bugtask/assignee/required:launchpad.LimitedView condition in there and just redact the assignee if that condition is false. [22:54] cjwatson: https://bugs.launchpad.net/launchpad/+bug/1592186 [22:54] Launchpad bug 1592186 in Launchpad itself "feeds.launchpad.net/ubuntu/latest-bugs.atom choked" [Undecided,New] [22:54] Ta. [22:54] heh, forgot about the bot [23:19] hi everyone, [23:20] i want to package my app into a debian package ppa [23:20] can anyone help me? [23:20] i honestly don't have a clue what do I have to do [23:23] mr-k: https://wiki.debian.org/Packaging [23:23] yes, but.. it's a bit different [23:23] the app is packaged with electron [23:23] (a service like node-webkit to build hybrid html5 apps) [23:25] mr-k: afaict, electron itself is not package in ubuntu [23:25] how webupd8 got it working with popcorn-time? [23:25] popcorn-time it's a node-webkit app [23:26] mine is electron. almost the same. [23:26] mr-k: link? i don't see webupd8 in the archives [23:26] webudp8 mantains a lot of ppa's [23:26] http://www.webupd8.org/ [23:27] besides, I think slack also does it [23:27] because it's the only way to provide auto updates to our app's [23:27] and slack it's done with electron [23:27] so, there's gotta be a way [23:28] (pd: thanks for replying so fast) [23:28] mr-k: i don't need a link to their page [23:28] i need a link to their packages [23:28] https://launchpad.net/~nilarimogard/+archive/ubuntu/webupd8 ? [23:29] oh, the popcorn-time package was removed for copyright matters [23:29] but.. here: https://github.com/raelgc/scudcloud [23:29] nevermind, webupd8 was just an example that it can be done. they don't mantain the popcon ppa anymore [23:30] but look at the github link I just share [23:30] sudo apt-add-repository -y ppa:rael-gc/scudcloud [23:30] that's the ppa [23:30] ok, reading their files [23:31] they are usin dh_python3 to build, afaict [23:33] i see [23:33] mr-k: meaning the builder just invokes `setup.py install` to know what files to install [23:34] https://launchpadlibrarian.net/261749492/buildlog_ubuntu-trusty-i386.scudcloud_1.24-2_BUILDING.txt.gz [23:34] can you tell me how the ppa works, more or less? [23:34] is what i'm reading [23:35] hmm, electron does have a builder & packager as a npm module [23:35] that was very helpful, nacc. thank you (: [23:35] mr-k: i don't see any mention of electron in the PPA's build logs [23:35] mr-k: i would suggest maybe contacting the ppa owner for details on what they are doing, though (or just read their debian/* files)