=== Spads_ is now known as Spads [04:24] The bug tracker location listed for workrave at https://bugs.launchpad.net/bugs/bugtrackers/workrave-bugzilla/+edit is wrong. The value currently is "http://issues.workrave.org/cgi-bin/bugzilla/" but that is "Not Found". The url http://issues.workrave.org/ works, but launchpad won't let me change it. Please update this and make sure it pulls in all the new bugs (none since 2009 that I see in Launchpad, vs many current bugs in the bugzilla) [04:34] nealmcb: Launchpad doesn't automatically import all bugs on the remote tracker, but I've updated the URL. [11:02] so, we have https://launchpad.net/~scribus/+archive/ubuntu/ppa/+sourcepub/5080381/+listing-archive-extra — is there a way to ask lp to do a ppc64el build without re-uploading? [11:14] mapreri: I'm not completely sure if this works, but one thing you can try is a self-copy: copy-package -A ppa:scribus/ubuntu/ppa --from-suite trusty --to-suite trusty -e 0.0.1-1~ubuntu14.04~ppa1 -b scribus [11:15] mapreri: oh, add --force-same-destination [11:15] cjwatson: copy-package ain't in ubuntu-dev-tools (at least in debian) [11:16] mapreri: lp:ubuntu-archive-tools [11:16] * mapreri mumbles: why splitting this stuff... [11:18] Different maintenance needs [11:19] Maybe some of it could stand to migrate to ubuntu-dev-tools at some point, but I really haven't had the effort and it would require rather more SRUs [11:21] "Launchpad encountered an error during the following operation: copying a package. libpagemaker 0.0.1-1~ubuntu14.04~ppa1 in trusty (same version already has published binaries in the destination archive)" [11:23] oh, with -b worked! [11:23] though I'm not sure why "copy related binaries" would allow this [11:38] that seems to have worked, and sorry I typoed the package name [11:39] right, without -b, it thinks you want to rebuild the source, which you can't because there are already binaries there [11:39] that stage of the copy process is actually uninteresting and you just want to bypass it, which -b does [11:39] the useful effect of the copy is to hit the "create missing builds" step right at the end [11:50] I'd have never thought of using copy-packages (though I'd have used the webui) to trigger such thing... [11:50] so thank you :) [11:50] yeah the same thing in the web UI should have worked too, I just find CLIs easier to teleoperate :) [11:50] eheh [14:10] Odd_Bloke: your git merge proposal comment issue from the other day is fixed now [14:11] cjwatson: Thanks! [14:13] cjwatson: Oh, and I just got to use the easy copy-paste for removing a known SSH host for the first time; thanks for that too! <3 [14:14] cool [22:26] Question - was there a change recently that caused arch. independent packages to be built on i386 instead of amd64? [22:29] other way around [22:29] they'll build on amd64 on newer Ubuntu releases [22:31] Ah, so on Trusty they build on i386 and Vivid, amd64? [22:31] (At least that's what I've observed.) [22:31] I can't remember when it changed [22:32] Okay, I only ask because I have an identical build for both Trusty and Vivid and it's failing on Trusty for some reason. It would appear to be arch-related. [22:46] On an unrelated note: I have some daily builds that seem to be stuck. [22:46] https://code.launchpad.net/~george-edison55/+recipe/hectane-daily [22:50] that I can't help with :) [22:51] If it runs much longer, I'll just cancel them and try again. [23:42] Does anyone know if there is a way to tell backportpackage not to include source in an upload?