=== pleia2_ is now known as pleia2 [05:35] odrod, arm, running xenail. how can I apt-get source from a ppa? [05:41] (which doesn't have arm builds) [05:47] oh never mind. the version I want is already in ports.ubuntu.com/ubuntu-ports [10:53] hi. i'd like to have dbgsym packages activated for a PPA of mine (https://launchpad.net/~elvstone/+archive/ubuntu/vtk7). is that possible? [10:54] estan: You can do it yourself. Go to "Change details" and check "Build debug symbols" and probably also "Publish debug symbols". [10:56] cjwatson: aha, thanks! [10:57] cjwatson: do you know if i need to do something else for it to trigger building of the debug symbols? (or is the only way to upload a new source version of the packages?) [11:01] estan: If you have existing failed builds you can retry them; otherwise you need a fresh source upload. [11:56] cjwatson: alright. thanks. === pavlushka is now known as dj3 === dj3 is now known as pavlushka [13:15] can someone please take a look? thanks https://answers.launchpad.net/launchpad/+question/295629 [13:18] renatosilva: done [13:20] cjwatson: thanks! [13:26] cjwatson: but there are two problems [13:27] one, this branch has deleted project in name still https://code.launchpad.net/~renatosilva/pidgin++/ircaway [13:27] it says lp:pidgin-ircaway, and cloning even works! but project was just deleted! [13:27] second, I cannot delete the branch [13:27] You should be more clear in your requests then! [13:28] "This branch cannot be deleted as it has 1 branch sharing revisions. " -- this branch is an old patch that is useless for all known galaxies [13:28] renatosilva: I've reactivated the projects. Please delete the code branches and then let me know. [13:28] no! [13:28] omg [13:28] such a mess [13:29] I do want to delete these two useless projects [13:29] then I went for the above branch and noticed it references a deleted project [13:29] name should be pidgin++/ircaway not lp:pidgin-ircaway [13:29] Why does it matter if the old branches are still branchable? Nothing will refer to them [13:30] this is first problem [13:30] why why why, one mess here, another there [13:30] renatosilva: You could unset the development focus on those projects. [13:30] I can't do that for you. [13:30] I assume you are pretty aware then why many people are leaving launchpad [13:31] but back to the problems, will try unset, this is for first problem or second? [13:31] ah sorry! [13:31] Look, I'm not interested in having a philosophical debate. [13:31] You can abuse me or ask me for help but not both. [13:31] bad habit of reading messages partially [13:32] "Please delete the code branches and then let me know." -- just read [13:32] well [13:32] Unsetting the development focus will stop those branches being lp:pidgin-ircaway and lp:pidgin-windev. [13:32] deleting https://code.launchpad.net/~renatosilva/pidgin++/ircaway does not work regardless if the project exists, so no need to try [13:33] gives this message regardless "This branch cannot be deleted as it has 1 branch sharing revisions. " [13:33] Yes, you already said that. [13:33] Bazaar hosting has several of these kinds of problems; we learned from this when we put together Git hosting [13:34] unset the development focus on those projects -- what exactly this will do, fix first problem? [13:34] 14:32 Unsetting the development focus will stop those branches being lp:pidgin-ircaway and lp:pidgin-windev. [13:35] * renatosilva trying... [13:36] cannot unset [13:36] it lists the series, that's all, need to pick one [13:36] What URL are you using? [13:37] https://launchpad.net/pidgin-windev/+edit [13:37] Use https://launchpad.net/pidgin-windev/+configure-code instead [13:37] Empty the text box under "Link to a Bazaar branch already in Launchpad", and press Update [13:38] Likewise for pidgin-ircaway [13:40] already empty for windev [13:41] The branch that's stacked on the former lp:pidgin-ircaway and preventing it being deleted is lp:~vlad-lesin/pidgin-ircaway/easy_build; you could contact that user and ask them to delete or unstack their branch (the latter being "bzr reconfigure --unstacked lp:~vlad-lesin/pidgin-ircaway/easy_build", though can probably only be done while the project is active), but it's probably not worth the effort [13:41] but first problem solved for ircaway :) [13:41] awesome! [13:41] it's empty now for windev; it wasn't before [13:41] I know that branch, asked him to delete [13:41] no response [13:41] asked him months ago a few times [13:42] what's interesting is [13:42] if I did not associate that ircaway branch with pidgin++, then now that you delete pidgin-ircaway project, this branch would be gone, correct? [13:43] no, we can only actually make projects inactive+invisible rather than full-scale deleteion [13:43] *deletion [13:43] ah wait, I can move it back to pidgin-ircaway, and when you re-delete, it will be gone, no? [13:43] well but I will not see the branch anywhere [13:43] it would be invisible, yes; although it would also be for most purposes invisible now, since its status is Merged [13:44] so now that it's no longer a focus branch for a project, it won't show up unless you look pretty hard for it [13:44] but you could indeed move it back to pidgin-ircaway if you like [13:44] how can I create a copy of this branch to put in pidgin++ but one that I can delete later (without stacked branches like vlad)? [13:45] selecting "any status" in filter is far from pretty hard :) [13:45] move it to something under pidgin-ircaway, and then "bzr push lp:~renatosilva/pidgin++/ircaway" [13:45] ok will do... [13:45] * renatosilva ... [13:45] "pretty hard" in this case doesn't mean "difficult", but anyway. [13:50] done, and I could delete it, awesome!! [13:50] cjwatson: now you can 'delete' both projects again, I guess [13:57] renatosilva: done [13:58] cjwatson: awesome, thanks [13:59] professional attitude despite the philosophical views :) [14:00] cjwatson: thanks for *actually* fixing the problems, good afternoon [14:03] thanks all [17:01] hi [17:02] is there a way to get mailing list archives in mbox format? [17:02] I'd like to reply to an older mail, quoting it and using a proper In-Reply-To: header [17:04] there is although it's a slightly weird one that involves us invoking sysadmins [17:04] you can ask a question on https://answers.launchpad.net/launchpad for it [17:06] well, it's probably not worth the effort just to get proper threading of list mails [17:06] but I'm going to submit a question nonetheless, so it doesn't get lost [17:07] https://answers.launchpad.net/launchpad/+question/158226 suggests that it's a reoccuring problem [17:10] that sort of thing is a little different at least in purpose [17:11] for a non-team-owner we'd probably want to extract just the message in question [17:13] mmh [17:13] as said, it's not important enough in this particular instance, but a generic solution would be nice [17:14] the most important bit for me is the Message-Id [17:15] mailman's mbox output is severely scrubbed, it just leaves From, To, Subject, In-Reply-To, References and Message-Id [17:16] that shouldn't be a problem from a data protection POV -- it'd also be okay to further obfuscate the non-list addresses [17:19] I would have to ask around [18:04] cjwatson, I appreciate your enabling s390x for me. However, my build just failed and I seem to have no log to investigate [18:07] cjwatson, does that have something to do with the arch? [18:08] kyrofa: usually means the builder crashed before creating logs [18:09] dobey, huh. It said it ran for 14 minutes [18:09] kyrofa: provide the link to the build :) [18:10] dobey, https://code.launchpad.net/~kyrofa/+snap/nextcloud/+build/1364 [18:12] kyrofa: ok, maybe it just took a long while exploding before it created logs. i'm not too familiar with building snaps on lp yet, but when this happens in PPAs, it typically means something went wrong on the builder before the logs were being created [18:13] dobey, alright thanks for taking a look. I've requested another build so we'll see what happens. Indeed, the other builders work like that, but they don't typically take so long to explode :) [18:14] well, any more info on it will have to wait for cjwatson or wgrant to take a look === mwhudson_ is now known as mwhudson [21:40] kyrofa: Looks like a firewall problem [21:40] 2016-06-27 17:49:55+0000 [-] Build log: fatal: unable to access 'https://git.launchpad.net/nextcloud-snap/': Failed to connect to git.launchpad.net port 443: Connection timed out [21:40] 2016-06-27 17:49:55+0000 [-] Build log: Revoking proxy token... [21:40] 2016-06-27 17:52:02+0000 [-] Build log: .URLError: [21:40] 2016-06-27 17:52:02+0000 [-] Iterating with success flag 1 against stage BUILD_SNAP [21:40] 2016-06-27 17:52:02+0000 [-] Returning build status: Builder failed. [21:41] kyrofa: File a bug please? I'll need to chase this down with puppet and/or sysadmins