[00:01] -queuebot:#ubuntu-release- New binary: libgnatcoll-bindings [ppc64el] (noble-proposed/universe) [24.0.0-2] (no packageset)
[00:01] -queuebot:#ubuntu-release- New binary: libgnatcoll-bindings [s390x] (noble-proposed/universe) [24.0.0-2] (no packageset)
[00:18] -queuebot:#ubuntu-release- New binary: libgnatcoll-bindings [arm64] (noble-proposed/universe) [24.0.0-2] (no packageset)
[00:55] <mwhudson> uploading no change rebuilds against libcups2t64
[01:14] <mwhudson> bdmurray, RAOF: what do you think about removing the osmo stack on armhf?
[02:22] -queuebot:#ubuntu-release- New binary: adacgi [riscv64] (noble-proposed/universe) [1.6-34] (no packageset)
[02:22] -queuebot:#ubuntu-release- New binary: gcc-14-cross-ports [amd64] (noble-proposed/universe) [5ubuntu2] (i386-whitelist)
[02:30] -queuebot:#ubuntu-release- New binary: libxmlezout [riscv64] (noble-proposed/universe) [1.06.2-14] (no packageset)
[02:33] -queuebot:#ubuntu-release- New binary: libflorist [riscv64] (noble-proposed/universe) [2022.0.1~20220616-5] (no packageset)
[02:41] -queuebot:#ubuntu-release- New binary: libtemplates-parser [riscv64] (noble-proposed/universe) [24.0.0-2] (no packageset)
[02:45] -queuebot:#ubuntu-release- New: accepted gcc-14-cross-ports [amd64] (noble-proposed) [5ubuntu2]
[02:46] -queuebot:#ubuntu-release- New: accepted libgnatcoll-bindings [amd64] (noble-proposed) [24.0.0-2]
[02:46] -queuebot:#ubuntu-release- New: accepted libgnatcoll-bindings [ppc64el] (noble-proposed) [24.0.0-2]
[02:46] -queuebot:#ubuntu-release- New: accepted libgnatcoll-bindings [arm64] (noble-proposed) [24.0.0-2]
[02:46] -queuebot:#ubuntu-release- New: accepted libgnatcoll-bindings [s390x] (noble-proposed) [24.0.0-2]
[03:08] -queuebot:#ubuntu-release- New binary: gcc-14-cross [amd64] (noble-proposed/main) [4ubuntu1] (i386-whitelist)
[03:39] -queuebot:#ubuntu-release- New binary: libgtkada [riscv64] (noble-proposed/universe) [24.0.0-2] (no packageset)
[03:40] -queuebot:#ubuntu-release- New binary: linbox [riscv64] (noble-proposed/universe) [1.7.0-3.1] (no packageset)
[08:50] -queuebot:#ubuntu-release- Unapproved: cinder (jammy-proposed/main) [2:20.3.1-0ubuntu1.1 => 2:20.3.1-0ubuntu<IP_ADDRESS>.1] (openstack)
[08:50] -queuebot:#ubuntu-release- Unapproved: cinder (mantic-proposed/main) [2:23.0.0-0ubuntu1.1 => 2:23.0.0-0ubuntu<IP_ADDRESS>.1] (openstack)
[10:21] <LocutusOfBorg> doko, llvm-toolchain-18 build finished!
[11:19] <mdeslaur> I have an openssl security change to upload to noble at some point, should I wait until everything has settled down?
[11:21] <jbicha> hi, it was noticed that armhf is missing at https://cloud-images.ubuntu.com/noble/current/ do we expect it to return?
[11:38] -queuebot:#ubuntu-release- New: accepted gcc-14-cross [amd64] (noble-proposed) [4ubuntu1]
[11:59] -queuebot:#ubuntu-release- New: accepted libxmlezout [amd64] (noble-proposed) [1.06.2-14]
[11:59] -queuebot:#ubuntu-release- New: accepted libxmlezout [ppc64el] (noble-proposed) [1.06.2-14]
[11:59] -queuebot:#ubuntu-release- New: accepted libxmlezout [s390x] (noble-proposed) [1.06.2-14]
[11:59] -queuebot:#ubuntu-release- New: accepted libxmlezout [arm64] (noble-proposed) [1.06.2-14]
[11:59] -queuebot:#ubuntu-release- New: accepted libxmlezout [riscv64] (noble-proposed) [1.06.2-14]
[11:59] -queuebot:#ubuntu-release- New: accepted libtemplates-parser [amd64] (noble-proposed) [24.0.0-2]
[11:59] -queuebot:#ubuntu-release- New: accepted libtemplates-parser [ppc64el] (noble-proposed) [24.0.0-2]
[12:00] -queuebot:#ubuntu-release- New: accepted libtemplates-parser [s390x] (noble-proposed) [24.0.0-2]
[12:00] -queuebot:#ubuntu-release- New: accepted libtemplates-parser [arm64] (noble-proposed) [24.0.0-2]
[12:00] -queuebot:#ubuntu-release- New: accepted libtemplates-parser [riscv64] (noble-proposed) [24.0.0-2]
[12:05] -queuebot:#ubuntu-release- New: accepted adacgi [amd64] (noble-proposed) [1.6-34]
[12:05] -queuebot:#ubuntu-release- New: accepted adacgi [ppc64el] (noble-proposed) [1.6-34]
[12:05] -queuebot:#ubuntu-release- New: accepted adacgi [s390x] (noble-proposed) [1.6-34]
[12:05] -queuebot:#ubuntu-release- New: accepted adacgi [arm64] (noble-proposed) [1.6-34]
[12:05] -queuebot:#ubuntu-release- New: accepted adacgi [riscv64] (noble-proposed) [1.6-34]
[12:16] <doko> gtk3 uninstallable again?
[12:16] <doko> ahh, cups again
[12:23] -queuebot:#ubuntu-release- New: accepted libflorist [amd64] (noble-proposed) [2022.0.1~20220616-5]
[12:23] -queuebot:#ubuntu-release- New: accepted libflorist [ppc64el] (noble-proposed) [2022.0.1~20220616-5]
[12:23] -queuebot:#ubuntu-release- New: accepted libflorist [s390x] (noble-proposed) [2022.0.1~20220616-5]
[12:23] -queuebot:#ubuntu-release- New: accepted libgtkada [arm64] (noble-proposed) [24.0.0-2]
[12:23] -queuebot:#ubuntu-release- New: accepted libgtkada [riscv64] (noble-proposed) [24.0.0-2]
[12:23] -queuebot:#ubuntu-release- New: accepted libflorist [arm64] (noble-proposed) [2022.0.1~20220616-5]
[12:23] -queuebot:#ubuntu-release- New: accepted libgtkada [amd64] (noble-proposed) [24.0.0-2]
[12:23] -queuebot:#ubuntu-release- New: accepted libgtkada [s390x] (noble-proposed) [24.0.0-2]
[12:23] -queuebot:#ubuntu-release- New: accepted libflorist [riscv64] (noble-proposed) [2022.0.1~20220616-5]
[12:23] -queuebot:#ubuntu-release- New: accepted libgtkada [ppc64el] (noble-proposed) [24.0.0-2]
[12:30] -queuebot:#ubuntu-release- New binary: ahven [ppc64el] (noble-proposed/universe) [2.8-9] (no packageset)
[12:30] -queuebot:#ubuntu-release- New binary: libgnatcoll-db [arm64] (noble-proposed/universe) [23.0.0-6] (no packageset)
[12:30] -queuebot:#ubuntu-release- New binary: ahven [s390x] (noble-proposed/universe) [2.8-9] (no packageset)
[12:31] -queuebot:#ubuntu-release- New binary: libgnatcoll-db [amd64] (noble-proposed/universe) [23.0.0-6] (no packageset)
[12:31] -queuebot:#ubuntu-release- New binary: libgnatcoll-db [s390x] (noble-proposed/universe) [23.0.0-6] (no packageset)
[12:32] -queuebot:#ubuntu-release- New binary: libgnatcoll-db [ppc64el] (noble-proposed/universe) [23.0.0-6] (no packageset)
[12:32] -queuebot:#ubuntu-release- New: accepted ahven [ppc64el] (noble-proposed) [2.8-9]
[12:32] -queuebot:#ubuntu-release- New: accepted libgnatcoll-db [amd64] (noble-proposed) [23.0.0-6]
[12:32] -queuebot:#ubuntu-release- New: accepted libgnatcoll-db [ppc64el] (noble-proposed) [23.0.0-6]
[12:32] -queuebot:#ubuntu-release- New: accepted linbox [riscv64] (noble-proposed) [1.7.0-3.1]
[12:32] -queuebot:#ubuntu-release- New: accepted ahven [s390x] (noble-proposed) [2.8-9]
[12:32] -queuebot:#ubuntu-release- New: accepted libgnatcoll-db [s390x] (noble-proposed) [23.0.0-6]
[12:32] -queuebot:#ubuntu-release- New: accepted libgnatcoll-db [arm64] (noble-proposed) [23.0.0-6]
[12:32] -queuebot:#ubuntu-release- New: accepted linbox [s390x] (noble-proposed) [1.7.0-3.1]
[13:10] -queuebot:#ubuntu-release- New binary: poppler [i386] (noble-proposed/main) [24.02.0-1ubuntu8] (desktop-core, i386-whitelist, ubuntu-server)
[13:12] -queuebot:#ubuntu-release- New binary: poppler [amd64] (noble-proposed/main) [24.02.0-1ubuntu8] (desktop-core, i386-whitelist, ubuntu-server)
[13:12] -queuebot:#ubuntu-release- New binary: poppler [s390x] (noble-proposed/main) [24.02.0-1ubuntu8] (desktop-core, i386-whitelist, ubuntu-server)
[13:13] -queuebot:#ubuntu-release- New binary: poppler [ppc64el] (noble-proposed/main) [24.02.0-1ubuntu8] (desktop-core, i386-whitelist, ubuntu-server)
[13:15] <juliank> For investigating build dependency issues on armhf noble, feel free to use https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble.armhf/proposed.yml
[13:15] <juliank> it will show you conflicting dependency chains and missing packages
[13:16] -queuebot:#ubuntu-release- New binary: poppler [arm64] (noble-proposed/main) [24.02.0-1ubuntu8] (desktop-core, i386-whitelist, ubuntu-server)
[13:16] <juliank> Note that apt may be less clever and fail to resolve nonetheless
[13:17] <juliank> Also note the reports for the release pocket in https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble.armhf/
[13:18] <juliank> note that the .txt ones do not show conflicting dependency chains, only missing build dependencies
[13:26] <rbasak> juliank: thanks. I'm on +1 this week and really struggling to find anything useful to do.
[13:27] <rbasak> Any time I chase something down, it takes a long time and eventually I find that someone else has already submitted a retry for it (if it seems like it should now work) or an upload fixing the issue.
[13:27] <juliank> conflicts are in the .txt now as well with their dependency chains
[13:28] <juliank> So you can easily go to https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble.armhf/proposed.txt and read in there
[13:28] <juliank> in the browser
[13:28] <juliank> whereas the yaml I guess browsers don't accept the content type and download it :)
[13:34] <juliank> rbasak: So yes if you see something that is failing to build with dependency issues, you can consult the report to see if it has dependency issues and if not retry it
[13:35] <juliank> rbasak: Or you can go look at the analysis and do some other rebuild to migrate one of the conflicting chains from libfoo1 to libfoo1t64
[13:42] <juliank> Output is sorted by package failing to build now in the .txt; and the keys in the dependency chain have a proper order now
[13:53] <doko> jbicha: are you aware that poppler t64 cannot build? depending on old cups
[14:01] <jbicha> doko: hmm? https://launchpad.net/ubuntu/+source/poppler/24.02.0-1ubuntu8
[14:01] <jbicha> maybe what you're seeing is just that the cups t64 transition started late so rebuilds haven't happened yet for everything
[14:01] <rbasak> juliank: what does "status: broken" mean? Uninstallable? Is there anything else that leads to "broken"?
[14:01] <jbicha> & then I guess poppler didn't get the noble transition either
[14:03] <juliank> rbasak: yeah, look at reasons:
[14:05] <rbasak> juliank: ah - so really it's "missing:" that indicates uninstallability?
[14:06] <seb128> hum, connectivity issues, unsure if that msg went through
[14:06] <seb128> doko, https://launchpad.net/ubuntu/+source/poppler/24.02.0-1ubuntu8 uploaded 20 min ago built?
[14:09] <doko> very late merge ...
[14:09] <juliank> rbasak: missing is if the build-dep or transitive dependency is completely missing; and conflicts: if there's conflicting dependency chains
[14:09] <juliank> rbasak: The text report (with .txt) now includes both kinds and may be nicer to look at
[14:11] <rbasak> juliank: thanks. I'm still trying to understand this by looking at specific examples. I keep finding things that are supposedly broken but the builds are expected to fail on armhf. Eg. a transitive dependency on architecture-is-64-bit, or a binary package that excludes armhf from the build archs. I wonder if we could filter this somehow? For example, could we ignore anything that isn't in the
[14:11] <rbasak> release pocket already?
[14:14] <juliank> Possibly
[14:15] <juliank> It's a bit involved though
[14:15] <juliank> It's not really giving you a migration unblocking view in that sense, yeah
[14:16] <juliank> We also have https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble.armhf/proposed-against-release.txt
[14:16] <juliank> which will show you packages in proposed that fail to have their build-depends satisfied in the release pocket
[21:28] <doko> jbicha: what is this uhttpmock0 package about?
[21:31] <jbicha> doko: it's briefly explained in the debian/changelog. uhttpmock is only used for libgdata's tests. libgdata sadly still uses libsoup2.4
[21:32] <jbicha> A new library msgraph has build tests that use uhttpmock but they need the newer libsoup3 version. Also we want to get msgraph into Ubuntu main so build tests are especially important
[21:33] <jbicha> new version keeps the uhttpmock source package name, old gets an old name, uhttpmock0. Not possible for things to link against both libsoup2.4 & libsoup3
[21:34] <doko> ok, accepted
[21:34] <doko> vorlon: the queue logger->irc isn't working
[21:48] <mitchdz> Hi ubuntu-release! I'm picking this bug back up https://bugs.launchpad.net/ubuntu/+source/postgresql-12/+bug/2024019 and am going to look at starting the SRU process  to add `-moutline-atomic` to the following packages: haproxy,nginx,postgresql-12 for arm64. This would be strictly a change to increase performance and doesn't fix any bugs, so I'm curious how that would be received during an SRU. Is there a certain % in
[21:48] <mitchdz> performance increase that we look for until we say the SRU is worth the risk, or for these packages would we just say no to this type of change on a stable release?
[21:48] -ubottu:#ubuntu-release- Launchpad bug 2024019 in nginx (Ubuntu) "Add GCC atomic support (-moutline-atomics) for arm64 on Focal" [Undecided, In Progress]
[22:01] <blackboxsw> hi SRU vanguards: please reject cloud-init unapproved uploads 24.1.1 to the proposed queues for Focal, Jammy and Mantic. We will be uploading cloud-init v.24.1.2 instead which includes a couple of high-profile fixes that we'd like in stable releases.
[22:54] <bdmurray> What happened to queuebot? that's its name right?
[22:57] <bdmurray> mitchdz: I think you want ubuntu-sru for an SRU question.
[22:58] <mitchdz> that's fair. well, ubuntu-sru do you have any thoughts on my question?
[23:00] <mitchdz> Also, is ubuntu-sru an official tag for the IRC server? Maybe that should be added in https://wiki.ubuntu.com/StableReleaseUpdates
[23:02] <rbasak> I'm not aware that we have any specific policy on this. I don't think we'd rule out SRUs for performance improvements, but 1) I'd expect a good regression risk analysis and 2) a higher bar for anything older than the current LTS.
[23:02] <rbasak> For this particular bug, I don't understand why -moutline-atomics wasn't the default?
[23:03] <rbasak> https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html says it is default, though perhaps it wasn't then? If it wasn't the default, why wasn't it the default? Eg. did upstream not have confidence in it?
[23:03] <rbasak> Because from the description it sounds perfectly safe.
[23:03] <rbasak> Or will it harm performance on < 8.1 ISAs?
[23:04] <rbasak> Anyway, please put answers to all of that in the bug.
[23:05] <mitchdz> Thanks Robie, and great questions. I expected to do the regular regression risk analysis. Figured I'd ask if it was dead in the water before I start digging into it :)
[23:07] <RAOF> We have, in the past, accepted SRUs for performance (I think openssl is a recent example), but as Robie said, we'd want more confidence in the correctness of the change than a standard SRU, more detailed justification (is it 1000% performance increase on common workload? Is it 100% on uncommon workload? Is it 5% on common workload? etc).
[23:16] <bdmurray> I seem to recall a glibc performance SRU that ended up having mixed results
[23:57] <mwhudson> jbicha: so er the new vala didn't fix telepathy-glib?


[11:35] <elfy> balloons: has someone stopped whatever reports to jenkins for install tests - nothing reported for 7 days
[13:33] <pitti> jibel: FYI, I got 4 wolfes back (although slightly different numbers), setting them up now (they are totally blank)
[14:01] <pitti> jibel: err, halp -- we try to install "jenkins-slave", but that package only exists on precise
[14:01] <jibel> pitti, you can install the version from debian
[14:02] <jibel> pitti, jenkins in unmaintained in Ubuntu and has been removed
[14:02] <pitti> jibel: I wonder how we did that when we first set up these machines; I'm fairly sure it was in ubuntu
[14:02] <pitti> jibel: ooh -- perhaps it was still there in saucy, and dist-upgrade to trusty just kept the old version
[14:02] <jibel> pitti, https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu
[14:03] <jibel> pitti, yes something like that, I don't remember precisely when it has been removed
[14:03] <pitti> https://launchpad.net/ubuntu/+source/jenkins/+changelog
[14:04] <pitti> ack
[14:04] <jibel> pitti, bug 1294005
[14:12] <pitti> jibel: how do I reconfigure http://d-jenkins.ubuntu-ci:8080/computer/wolfe-06-adt/ to be wolfe-02-adt? I don't see any kind of "configure" in the menu there?
[14:14] <pitti> I might just lack the privileges to do that
[14:30] <pitti> jibel: or, I figure I might need an RT for that and let retoaded handle it?
[14:34] <retoaded> pitti, you need me to rename wolfe-06-adt as wolfe-02-adt correct?
[14:35] <pitti> retoaded: yeah, and adjust the IP
[14:36] <pitti> retoaded: i. e. wolfe-02 is now <IP_ADDRESS> (one less than wolfe-03)
[14:36] <pitti> retoaded: do you need an RT for this?
[14:36] <retoaded> pitti, nah, shouldn't take but a moment once I find where the IP is stored.
[14:38] <retoaded> pitti, the IP isn't used within Jenkins configuration. The node has been renamed and appears to be up.
[14:39] <pitti> retoaded: cool, thanks; ah, it's the node itself telling jenkins about its hostname, I figure?
[14:39] <retoaded> pitti, yes
[14:39] <pitti> cool
[14:41] <pitti> jibel: so, ppc64el boxes are back; I retried the recently failed tests
[14:42] <pitti> jibel: although they feel like a tarpit, I asked smoser about that
[15:42] <balloons> elopio, link? >you mean the AP tests for ubiquity?.
[15:42] <elopio> ->brain freeze<-
[17:32] <wxl> elfy: have you guys come up with a new input engine e.g. scim or uim as a default or what are you doing?
[17:35] <elfy> confused ...
[17:35] <wxl> elfy: you nixed ibus, no?
[17:35] <elfy> oic - we did nothing
[17:36] <wxl> oh, i guess i'm confused :)
[17:37] <elfy> we just don't have ibus by default anymore - if someone wants it they have to install it
[17:38] <wxl> ic, so what is the default?
[17:45] <elfy> no ibus installed
[17:46] <wxl> in other words, you have no input manager at all?
[17:52] <wxl> elfy: to make a long story short, i'd like to kill ibus sometime soon, but i know people need the functionality, so i'm exploring other options and wanted to see if you had any input
[23:04] <ianorlin> grr had a kernel panic while in a live session not really sure how to report the bug on this new desktop I built but haven't installed to yet for utopic
[23:10] <ianorlin> how would I report a bug in the live session of a kernel panic and get debug info?


[06:48] <cjwatson> http://blog.launchpad.net/code/git-to-git-imports
[08:20] <axino> \o/
[14:30] <sigmavirus> cjwatson: great work!
[16:17] <tabletcorry> Hi! I am trying to get a list of all versions of a package from the name of a package, but I can't find anything in the API to do this
[16:18] <tabletcorry> I can do it in the web UI, but I can't find the equivalent in the API
[16:18] <tabletcorry> Basically this page, except in API accessible form: https://launchpad.net/ubuntu/precise/amd64/libreoffice-l10n-ja
[16:19] <nacc> that's not 'all' versions of a package, though
[16:19] <nacc> that's all versions published in a series
[16:20] <tabletcorry> Not sure what you mean by series (new to this), but I am looking for all versions within an arch/ubuntu_release tuple
[16:20] <nacc> series ~ target in launchpad parlance, the various releases of ubuntu
[16:20] <tabletcorry> Thats fine. I really only want all the versions in amd64/all trusty for now
[16:21] <nacc> I'm not sure if there is a more efficient way to do it, but you can do, something like:
[16:22] <nacc> launchpad.distributions['ubuntu'].main_archive.getPublishedSources [I think there is an equivalent for binary packages]
[16:22] <nacc> and that function takes arguments like 'source_name' (to filter it)
[16:22] <nacc> and then you'd iterate over the returned objects to extract the data you want
[16:23] <tabletcorry> Hmm, I haven't been able to get the python library working yet. It seems to explode in python3
[16:23] <nacc> tabletcorry: i'm using it pretty heavily with python3
[16:23] <tabletcorry> interesting...
[16:23] <nacc> tabletcorry: have a backtrace?
[16:24] <tabletcorry> yup, just a sec. Need to scrub some details
[16:24] <nacc> tabletcorry: sure
[16:24] <nacc> tabletcorry: someone else may be able to help better than I, I'm not a LP expert, but have been using launchpadlib quite a bit lately
[16:25] <tabletcorry> It dies when I try to pip install it https://www.irccloud.com/pastebin/wBPXzzm0/
[16:26] <tabletcorry> One of it's dependencies just plain has invalid syntax for python3 :|
[16:26] <nacc> tabletcorry: are you on ubuntu now? (just wondering)
[16:27] <tabletcorry> Uh, yessss, I know where you are going. But I need this to work on osx too
[16:27] <nacc> tabletcorry: ok :)
[16:27] <tabletcorry> But that would work for seeing the calls it makes I suppose
[16:27] <nacc> tabletcorry: let me look at that dep issue
[16:27] <nacc> tabletcorry: i did fix that in ubuntu, iirc
[16:27] <nacc> tabletcorry: or suggested the fix, at least
[16:27] <tabletcorry> Your point is valid though. I can test it on ubuntu, and use tcpdump to borrow the API calls it makes
[16:28] <nacc> tabletcorry: ok, i htink it's a pip issue, but not sure
[16:28] <nacc> tabletcorry: per the changelog, upstream added python3 support in 0.13.4
[16:28] <tabletcorry> 0.13.4 isn't installable in pip for some reason. I noticed that last night
[16:28] <nacc> tabletcorry: very strange :/
[16:29] <tabletcorry> Its definitely not in pypi
[16:29] <tabletcorry> though pypi claims to have 0.13.3, which pip also doesn't see
[16:31] <nacc> tabletcorry: out of my depth again :) -- but yeah if those versions aren't available, that seems like a pretty big issue; maybe you can contact the upstream lazr maintainer?
[16:31] <cjwatson> tabletcorry: You probably want Archive.getPublishedBinaries
[16:31] <nacc> cjwatson: thanks, was going to look that up next
[16:31] <cjwatson> https://launchpad.net/+apidoc/devel.html#archive-getPublishedBinaries
[16:33] <tabletcorry> cjwatson: could you possibly give me a sample of what a working URL would look like for that endpoint? The lack of examples makes it tricky for a new user to figure out what the variables should be
[16:33] <cjwatson> And re the lazr.restfulclient python3 bug, that's indeed fixed in 0.13.4, I need to check why that didn't make it to PyPI - I think there was a further set of bug-fixes I was going to release as 0.13.5
[16:33] <cjwatson> tabletcorry: Can you use launchpadlib with Python 2 instead?  It's well-tested there
[16:33] <tabletcorry> I tend to just get unhelpful errors: "Object: <DistroSeries u'precise'>, name: u'+archive'"
[16:33] <cjwatson> And really much easier to use launchpadlib if you can
[16:33] <tabletcorry> cjwatson: I am in a python3 app, so my hands are tied there
[16:34] <cjwatson> https://help.launchpad.net/API/Hacking has general advice
[16:34] <cjwatson> https://api.launchpad.net/devel/ubuntu/+archive/primary would be the base URL for the Ubuntu primary archive
[16:36] <cjwatson> curl 'https://api.launchpad.net/devel/ubuntu/+archive/primary?ws.op=getPublishedBinaries&binary_name=libreoffice-l10n-ja&order_by_date=true' | jq     for example
[16:36] <cjwatson> but you then need to follow the next_collection_link links, since large responses are batched
[16:36] <tabletcorry> Thanks for that sample. I haven't seen an API like this before (more used to REST stuff)
[16:37] <cjwatson> It is allegedly REST, just a fairly weird implementation of it ...
[16:37] <tabletcorry> I was about to ask what the heck a custom get method was, so without that link I would never have guessed :)
[16:38] <cjwatson> ws.op specifies the method name
[16:39] <tabletcorry> Yeah, I don't really want to make this work by hand. I will try checking out the lazr package directly and use it in python if I can
[16:39] <tabletcorry> hopefully I can get it to be happy in python3
[16:39] <cjwatson> BTW, reading back, you also don't need tcpdump - you can use the profiling approach in https://help.launchpad.net/API/launchpadlib#Three_things_to_make_your_client_faster which will dump requests
[16:40] <tabletcorry> True, that would be easier. But I will leave that as a last ditch, if I can't get the library to work
[16:40] <cjwatson> I'll try to get to a lazr.restfulclient release soon.  I think the reason I hadn't was that I needed to test my fix for https://bugs.launchpad.net/lazr.restfulclient/+bug/1473577
[16:40] <ubot5`> Ubuntu bug 1473577 in lazr.restfulclient "Python 3.5 test failures" [High,In progress]
[16:41] <tabletcorry> Its odd that I can't even see 0.13.3 in pip, even though its in pypi
[16:42] <cjwatson> I think that's because it doesn't declare Python 3 support?
[16:42] <cjwatson> I bet it would show up in pip2
[16:42] <tabletcorry> does 0.13.1 declare support? Or is it going back to a null case?
[16:43] <cjwatson> There was no Python 3 support at all until 0.13.4
[16:43] <tabletcorry> Sure, just curious why pip will pull 0.13.1, but nothing newer. Its not really important though
[16:43] <cjwatson> Weird
[16:44] <cjwatson> It was done by a contributor rather than one of the core Launchpad team, so we dropped the ball a bit on the PyPI upload, then discovered that the port had some problems and wanted to chase down why they weren't caught ...
[16:44] <cjwatson> Anyway, will try to get it fixed up
[16:44] <tabletcorry> Thanks for the help! I think I am set now
[16:44] <cjwatson> Sorry for the awkwardness!
[16:44] <tabletcorry> At least you have an API :) I was having horrible flashbacks to an HTTP crawl I had to do in the past
[16:45] <cjwatson> Yeah, we're not quite that bad
[16:56] <tabletcorry> Hmm, there is another python3 break in 0.13.4's deps
[16:58] <tabletcorry> lazr.restfulclient imports oauth with is not python3 compatible
[17:00] <cjwatson> It does, but I think you can get away with that except for the test suite
[17:01] <cjwatson> That's one of the problems, we have a partial port but it's not enough to run the full test suite, which makes it difficult to ensure that everything works
[17:02] <tabletcorry> even the basic import "from launchpadlib.launchpad import Launchpad" explodes if you do or don't have oauth
[17:02] <tabletcorry> so not sure how to get around that
[17:02] <tabletcorry> may just start using the api directly
[17:31] <cjwatson> Hmm, how did this work for anyone in Ubuntu
[17:31] <cjwatson> Oh
[17:31] <cjwatson> http://launchpadlibrarian.net/179633001/python-oauth_1.0.1-3build2_1.0.1-4.diff.gz
[17:32] <cjwatson> Apparently oauth works if you shove use_2to3=True into setup.py
[17:34] <cjwatson> Yep.  So I think you just need to tell pip to use a local fork of oauth with that change
[17:35] <cjwatson> tabletcorry: ^-
[17:35] <tabletcorry> yeah, it seems ubuntu did a decent bit of massaging to make it work in ubuntu :)


[09:06] <darkxst> ricotz, hi
[09:07] <darkxst> it seems that XDG_CURRENT_DESKTOP also is being found for g-c-c when loading from overview
[09:08] <darkxst> or something just broke ;(
[09:08] <darkxst> s/is/is not/
[09:23] <ricotz> darkxst, hi, i see
[09:24] <ricotz> darkxst, are you working on g-s-d?
[09:24] <ricotz> i might take a look later to resync it with ubuntu if needed
[09:24] <ricotz> (g-c-c was quite off in this regard)
[09:24] <darkxst> ricotz, I think the displayConfig stuff should be implemented in unity
[09:25] <darkxst> g-s-d does need to be resynced
[09:25] <darkxst> 3.9 packages were based of ppa packages before saucy upload happened so will be a bit of a diff
[09:25] <ricotz> darkxst, that would be great
[09:26] <ricotz> ok, i guess i will take a look then
[09:27] <darkxst> ricotz, thanks
[09:27] <darkxst> it was actually on my todo list, but somehow I decided to try port gjs to c++
[09:28] <ricotz> oh, why is that?
[09:28] <darkxst> mozjs 24 has removed the C API
[09:28] <ricotz> ah
[09:29] <darkxst> not that its even released yet, but I can make that happen
[09:29] <ricotz> i have played it a bit with it here
[09:29] <ricotz> meaning packaging it from the repo
[09:29] <ricotz> will need a newer icu which is easy to update
[09:30] <darkxst> yeh 99% of my versioning patches are now upstream
[09:30] <ricotz> but there are a lot of patches needed to be backported from trunk to get a useful tarball
[09:31] <darkxst> hmm? they should be in 24?
[09:31] <ricotz> the 24 branch isnt is a good "standalone" shape
[09:31] <ricotz> darkxst, no i mean e.g. icu patches
[09:31] <darkxst> oh that is entirely seperate to what I am talking about!
[09:32] <ricotz> i know
[09:32] <ricotz> but it prevents to have a tarball out of the 24 branch
[09:33] <darkxst> right
[09:34] <ricotz> so some of these -- http://paste.debian.net/plain/44690
[09:35] <darkxst> ricotz, have you opened upstream bug for this?
[09:35] <ricotz> darkxst, i guess porting gjs to c++ isn't needed, but probably not the favor of upstream
[09:36] <ricotz> isn't / is
[09:36] <ricotz> darkxst, no, i haven'Tt
[09:36] <ricotz> is there even a "mozjs24 release" bug yet
[09:36] <darkxst> nope, let me make one
[09:36] <ricotz> ok, g2g for now
[09:37] <ricotz> bbl
[09:37] <darkxst> cya
[10:03] <darkxst> ricotz, https://bugzilla.mozilla.org/show_bug.cgi?id=919277, please add any other info you have there!
[12:52] <winb> The GNOME Classic session will be included in the 13.10 release ? Or just the beta?
[12:53] <winb> And where can I download the Ubuntu Gnome 12.04 ?
[12:54] <winb> It's not listed here http://cdimage.ubuntu.com/ubuntu-gnome/releases/
[14:04] <Andy80> hi guys
[14:05] <Andy80> after trying GNOME (the one available on ppa:gnome3-team/gnome3 for Ubuntu 13.04) also on a second PC I ask: why is it so instable?!
[14:05] <Andy80> every session I get "System errors"
[14:05] <Andy80> or apps that crash
[14:05] <Andy80> like tracker, evolution*
[14:05] <Andy80> gcs or something like that
[14:06] <Andy80> and note: the "staging" repository is not enabled
[15:45] <theenduser> ls -al
[15:45] <theenduser> lol I was way off
[18:21] <bjsnider> Andy80, there are known issues


[04:56] <nlsthzn> Good morning SOUTH AFRICA... today is Monday, the 7th and this will be the last 7th of this month so make it count!
[04:56] <superfly> morning nlsthzn!
[04:56] <superfly> haha
[04:58] <nlsthzn> :) I am getting pretty good and installing and configuring certain distro's (which is sad cause I never get to use them)... just setup Kubuntu 10.10 wiith KDE 4.6 again... re-configuring all chat and mail apps (again)
[05:02] <Symmetria> *sigh*
[05:02] <Symmetria> piece of advice for all of you
[05:03] <Symmetria> never, ever, ever, ever, ever buy cisco high end routers if you can avoid it
[05:03]  * Symmetria hates
[05:03] <Symmetria> I swear if I never have to order another piece of cisco gear again in my life I will be happy
[05:04] <Symmetria> big expensive pieces of crap that are full of software bugs :(
[05:04]  * Symmetria wants to replace all of them with junipers
[05:05]  * nlsthzn thought cisco was the bomb
[05:05] <superfly> Symmetria: I thought you said that cisco is the bomb
[05:09] <Symmetria> heh superfly I said cisco makes fast routers, way faster than a lot of the other cheap crap
[05:09] <Symmetria> but of late
[05:09] <Symmetria> their stuff has been giving a LOT of problems
[05:09] <Symmetria> We're buying more and more juniper gear now
[05:10] <Symmetria> the problem is, some of these issues are soooo hard to debug
[05:10] <superfly> btw, Symmetria, how's the server upgrade coming along? when are you expecting the kit to arrive?
[05:11] <Symmetria> will know that as soon as the hardware guy arrives
[05:11] <Symmetria> Im hoping this week or mid next week
[05:11] <Symmetria> Im going to get Patrick to go do full firmware upgrades on the current server today though to see if it puts an end to the prboelms we've been seeing (and the reason the server is offline right now)
[05:31] <Kilos> morning superfly and everyone else
[05:54] <Symmetria> heh gawd when you start doing really deep network debugging, there are some really... interesting commands... hidden away on routers
[05:54] <Symmetria> if you know how to turn them on that is
[05:55] <Symmetria> lol, on a cisco, type service internal and then start issuing certain show commands and it starts doing things like packet header capture off the asics for you to analyze
[06:35] <sakhi> mooning
[06:37] <superfly> aloha sakhi
[06:38] <bmg505> gmsa
[06:39] <bmg505> :)
[06:39] <superfly> morning bmg505!
[06:39] <bmg505> Symmetria, most of their undocumented feature is the source of most exploits or used to be
[07:36] <nlsthzn> you guys aware of severed fifth?
[07:41] <superfly> yes
[07:42] <nlsthzn> cool, downloaded the albums... now for some metal :)
[08:24] <Count_Janik> today a legend in rock is no more: http://www.eyewitnessnews.co.za/articleprog.aspx?id=58821
[08:24] <Count_Janik> :(
[08:30] <nlsthzn> Count_Janik: bit before my time, but sad when ones idols and legends die
[08:30] <Count_Janik> yep
[09:52] <Symmetria> sorry about that marcog/sakhi
[09:52] <Symmetria> we have a bit of a major problem we're trying to resolve
[12:41] <tumbleweed> Symmetria: marcog asks what this is in reference to
[18:36] <inetpro> guten abend
[18:36] <drubin> inetpro: hilo
[18:36] <inetpro> Maaz: coffee on
[18:36]  * Maaz washes some mugs
[18:36] <superfly> inetpro: guten abend
[18:37] <inetpro> heh drubin & superfly, how are yeah?
[18:37] <superfly> moeg
[18:38] <inetpro> superfly: why that?
[18:39] <superfly> inetpro: didn't get much sleep last night, spent the night on the couch to get a little bit of shuteye
[18:39] <drubin> baie moeg
[18:39] <inetpro> superfly: hmm... I know the feeling
[18:39] <drubin> superfly: shame... but I don't know the feeling
[18:40] <Maaz> Coffee's ready for inetpro!
[18:40] <inetpro> Maaz: baie dankie
[18:41] <Maaz> Plesier inetpro
[18:41] <inetpro> drubin: how come you are tired?
[18:42] <inetpro> should still be fully loaded with energy
[18:45] <drubin> inetpro: I just got back from cycling 30km :)
[18:46] <inetpro> drubin: very nice
[18:47]  * drubin is trying
[18:47] <drubin> it doesn't actually seem that much when I type it out, but it is an improvement on when I started
[18:49] <marcog> drubin: ta for the banner/table cloth
[18:49] <marcog> i'm sure it drew in quite a bit of attention
[18:49] <drubin> marcog: We want it back in one piece and pics!
[18:49] <marcog> for pics ask tumbleweed
[18:49] <drubin> if there isn't pics we are going to be very sad pandas
[18:49] <drubin> s/isn't/aren't/
[18:49] <marcog> one piece - hmm, that might be a bit late
[18:50] <marcog> you didn't add it in the agreement before handing it over
[18:50]  * drubin hopes marcog is joking
[18:50] <marcog> :P
[18:50] <marcog> :P
[18:50] <marcog> ofc i am :)
[18:50] <drubin> it was quite a big thing who knows
[18:50] <marcog> half the people kept thinking we had 2 banners
[18:50] <drubin> marcog: Glad it drew attention
[18:50] <marcog> not realising how massive it was
[18:51] <marcog> before unrolling that is
[18:51] <marcog> we want to try prod ctpug to get a python equivalent
[18:51] <marcog> then borrow that for AC/Umonya
[18:51] <drubin> marcog: This was sponsored by canonical... might not have the same funds in ctpug
[18:52] <marcog> tumbleweed says they're looking for things to get sponsorship for
[18:52] <drubin> marcog: Can you please ask tumbleweed for pics
[18:52] <marcog> Maaz: tell tumbleweed drubin wants pics of the stand
[18:52] <Maaz> marcog: Sure, I'll tell tumbleweed on freenode
[18:52]  * drubin honestly doesn't know his toes from his head at the moment
[18:53] <drubin> I mean he reads logs... I mean will you prod him :)
[18:53] <tumbleweed> Maaz: .
[18:53] <Maaz> tumbleweed: Huh?
[18:53] <Maaz> tumbleweed: By the way, marcog on freenode told me "tell tumbleweed drubin wants pics of the stand" 38 seconds ago
[18:53] <tumbleweed> yeah I'll post pics
[18:53] <tumbleweed> brb upgrading this box to squeeze
[18:53] <drubin> tumbleweed: \o/
[18:55] <tumbleweed> that seems to have worked
[19:07] <Kilos> evening all. found an interesting tool for fixing mbr with grub and grub2
[19:07] <Kilos> http://download2.berlios.de/supergrub/super_grub_disk_0.9799.iso
[19:07] <Kilos> cand even boot an OS that doesnt boot on its own
[19:08] <Kilos> can
[19:10] <Kilos> and i first went to an ubuntu site then got the info from there
[19:16] <inetpro> Kilos: does that mean your problems are just grub issues?
[19:19] <Kilos> yip inetpro  looks like but my 80g still giving probs
[19:20] <Kilos> install xp and works but wont take maverick
[19:20] <Kilos> will try this tool on the 80g tomorrow
[19:21] <Kilos> its actually the mbr not grub
[19:21] <Kilos> that tool fixes mbr as well
[19:21] <Kilos> there are 2 iso's for grub and grub2
[19:22] <Kilos> not sure what the site address is anymore must be that link minus the last bit hey?
[19:23] <Kilos> and i got 9.10 running on my overclocked P3 with 192m ram
[19:23] <Kilos> so if the P4 crashes i am not without contact again
[19:26] <Kilos> and i have a custom cd made with remastersys which i must still try. made here on p4 with an updated maverick
[19:26] <Kilos> took a while to work out how to get it to cd. but only 292m so dunno if it can all be there
[19:27] <Kilos> maybe its well compressed
[19:28] <Kilos> one thing about maverick i dont enjoy too much is having to install aptitude and gedit etc on their own
[19:30] <Kilos> but its much better than karmic with the close windows X on the right. kinda hard to remember where to find them when swopping from one to the other
[19:39] <Kilos> Maaz, coffee on
[19:39]  * Maaz puts the kettle on
[19:39] <Kilos> Maaz, with cremora
[19:39] <Maaz> Ah! At last someone with taste
[19:40] <Kilos> Maaz, and milk
[19:40] <Maaz> Now you're talking
[19:40] <Kilos> Maaz, coffee for all
[19:40] <Maaz> Sure thing Kilos... Hey guy's!!  Bring your mugs. I am tired of doing all the dishes on my own.
[19:43] <Maaz> Coffee's ready for Kilos!
[19:43] <Kilos> Maaz, gracias
[19:43] <Maaz> Kilos: ¡de nada!
[19:47] <Kilos> much too windy , the weeds are blowing in and out
[20:00] <Kilos> night all. sleep tight


[02:37] <vdepizzol> any chance to gaim in feisty come with tango icons? http://vdepizzol.wordpress.com/2006/12/03/landell-and-protocol-icons/
[06:18] <lapo> hi
[06:20] <troy_s> Greets lapo
[06:20] <lapo> yo troy_s, happy new year
[06:20] <troy_s> Same to you my friend
[06:20] <troy_s> and a merry xmas if you do that sort of thing
[06:28] <lapo> eheh, tnx
[09:12] <mhb> who's the leader of the Human iconset project?
[09:13] <mhb> or rather - do you know anyone who knows about it?


[00:04] <veebers> robru: ping, if you have a moment can you eyeball the packaging changes I made in this branch? https://code.launchpad.net/~veebers/autopilot/fix-upstart-rename-1330803/+merge/223486
[01:03] <robru> veebers, sorry, just got back, looking
[01:03] <veebers> robru: nw, awesome thanks
[01:16] <veebers> thanks robru :-)
[01:16] <robru> veebers, you're welcome!
[01:23] <robru> kgunn, camako: ermagerhd, is silo 16 for real? should I publish it??
[01:24] <robru> do we have any core devs around for a packaging ack? https://ci-train.ubuntu.com/job/landing-017-2-publish/lastSuccessfulBuild/artifact/packaging_changes_url-dispatcher_0.1+14.10.20140618-0ubuntu1.diff
[02:12] <kgunn> robru: packages built ok & tested ok
[02:14] <robru> kgunn, glad that's finally fixed ;-)
[02:39] <tedg> robru, Fixed the indicator-transfer stuff. Not sure what to do, should I rebuild?
[02:40] <robru> tedg, yeah, is it fixed in the same MP?
[02:41] <tedg> robru, Yeah
[02:41] <robru> tedg, yeah, just rebuild, doesn't need to retest, then I'll publish, then we can wait for a real archive admin to NEW it
[02:43] <tedg> robru, Cool, building.
[02:47] <robru> tedg, er, you're building url-dispatcher? I thought we were talking about indicator-transfer in 15
[02:47] <tedg> We were.
[02:47] <tedg> Shoot.
[02:48] <tedg> Hit the wrong one.
[02:48] <tedg> robru, Cancel or just let it build?
[02:48] <robru> tedg, ehhh, just let it go
[02:48] <tedg> Okay, kicked the right one now.
[02:49] <robru> tedg, i'd hate for that to be in a weird half-built inconsistent state
[02:49] <robru> tedg, great
[04:14] <elopio> ci-help
[04:14] <elopio> in case somebody is around, please take a look at http://q-jenkins.ubuntu-ci:8080/job/qt-release-gatekeeper/label=daily-mako/15/console
[04:14] <elopio> error: device not found
[04:43] <Mirv> robru: I don't see any particular "green light" for releasing Qt 5.3, though
[04:44] <Mirv> robru: so I'd more like think it's Thu your time if it happens
[04:44] <robru> Mirv, I was told at the landing meeting this morning (your yesterday) that today was the day for that. sil2100 said so
[04:44] <robru> Mirv, yeah, I was thinking you'd do it now and I'd wake up to the release in a few hours ;-)
[04:45] <Mirv> robru: ok, well sil2100 probably didn't follow the blockers and anyway I can't do the decision to "ship it". I don't have any e-mail or such from Pat/Ricardo/folks that it'd be good, so we need to wait at least until there's confirmation that emulator is workint etc
[04:46] <robru> Mirv, ok, well, do what you feel is right. i'm on my way to bed now.
[04:46] <Mirv> good night! I'll try to follow up on things, but I believe the landing button will be eventually pressed by someone else than me if it's not immediately in your Thu morning
[04:47] <robru> Mirv, alright, thanks. goodnight
[05:01]  * Mirv will land UITK as soon as watch only succeeds (and I'll probably need packaging acks too though)
[05:18] <cjwatson> robru,tedg: url-dispatcher packaging> would be slightly nicer to call it debian/source.apport and use dh_apport, and then you could just put "debian/url-dispatcher-crashdb.conf etc/apport/crashdb.conf.d" in debian/url-dispatcher.install and not have to use an override at all; Python code should be PEP-8 formatted too IMO.  But those are just niceties, so ack
[08:38] <Mirv> ogra_: if you happen to notice, you could kick an image build now that mir & UITK are in, to get somethin for them before Qt 5.3
[08:38] <popey> Mirv: ogra_ can you wait 30 mins until I have approved Music in the store?
[08:45] <Mirv> sure it can wait
[08:45] <popey> thanks
[08:48] <popey> ok, approved it, ogra_ if you're planning on being inside away from the lovely sun and fancy kicking an image that would be great ☻
[08:51] <Mirv> popey: so was that the 1.3.496 music-app?
[08:53] <popey> yes
[08:53] <Mirv> excellent
[08:53] <popey> the music devs and balloons works solidly for about 9 hours yesterday on it!
[08:54] <popey> so we can look at removing qtgrilo at some point
[08:56] <mhr3> Mirv, when is 5.3 planned to land?
[08:56] <Mirv> I'd give an applause to ahayzen and vthompson but they're not online
[08:57] <Mirv> mhr3: after Ricardo wakes up or so.. today probably anyway. we need emulator confirmed to be working.
[08:57] <mhr3> Mirv, asking cause i'll want to land the departments too
[08:59] <Mirv> mhr3: unity8 rebuild will not be the end of the world if it comes to that it needs landing first
[08:59] <mhr3> Mirv, sure, just giving you headsup
[08:59] <Mirv> ie if Qt 5.3 gets delayed to tomorrow for example. let's see.
[09:53] <Saviq> robru, hey, just noticed that host-upgrade removes the PPA after host-upgrade, so then host-purge doesn't work... is that on purpose?
[11:05] <popey> Mirv: please upload http://s-jenkins.ubuntu-ci:8080/job/calendar-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.calendar_0.4.328_all.click to the store when you have a moment
[11:07] <brendand> can we force PS Jenkins bot to run on a merge request?
[11:07] <brendand> or at least find it when it will run/why it isn't
[11:09] <cjwatson> http://lpbuildbot.canonical.com/changes/8394
[11:09]  * cjwatson does a happy anticipatory dance
[11:11] <ahayzen> xnox, would you be able to review this? or anyone else around? thanks https://code.launchpad.net/~andrew-hayzen/ubuntu-seeds/music-app-remove-grilo/+merge/223718
[11:16] <Mirv> popey: uploaded
[11:16] <popey> thanks Mirv
[11:17] <Mirv> cjwatson: popey was wondering a bit if you could kick an image build while ogra is away? there'll be an automated one in some amount of hours, but it'd be nice to have the results earlier with the new Mir and UI Toolkit
[11:17] <cjwatson> Mirv: Right now?
[11:17] <popey> now is good
[11:17] <Mirv> cjwatson: yes
[11:19] <cjwatson> sure, poked
[11:19] <Mirv> thanks!
[11:19] <popey> thank you cjwatson
[11:25] <imgbot> [11:26] <popey> Mirv: which will be the first qt53 image?
[11:30] <davmor2> popey: 90 with any joy :)
[11:34] <Mirv> popey: yeah 90 maybe, or if it gets autotriggered before we're ready then 91
[11:36] <popey> k
[12:03] <ricmm> Mirv: quick, maybe dumb question
[12:03] <ricmm> shouldnt unity-mir also rebuild against 5.3 ?
[12:24] <Mirv> ricmm: no, it's not strictly needed ie 5.3 is compatible enough. only those packages that have gotten the qtbase-abi-5-2-1 dependency via symbols are required
[12:45] <imgbot> [12:45] <imgbot> [12:45] <ricmm> Mirv: ah understood, perfect then
[12:46] <ricmm> cant wait for 90
[12:58] <brendand> why is there 89 without any smoketesting? http://ci.ubuntu.com/smokeng/utopic/touch/
[13:01] <t1mp> Mirv: did you see any Popovers that are black on qt 5.3?
[13:02] <t1mp> Mirv: https://www.dropbox.com/s/ojk1ag9fyff96do/Screenshot%202014-06-19%2015.02.01.png
[13:03] <mterry> robru, do you know who was working with ogra_ on some ubuntu-touch-session silo yesterday?
[13:04] <brendand> ogra_, why no smoketesting for 89?
[13:05] <mterry> brendand, I've been told ogra_ is off today
[13:06] <tedg> cjwatson, I haven't used apport like that, do you know of docs? These seem to be out-of-date https://wiki.ubuntu.com/Apport/DeveloperHowTo#Applications_not_included_in_Ubuntu.27s_repositories_but_hosted_on_Launchpad
[13:07] <brendand> ok now it's running
[13:08] <t1mp> Mirv: also the pickers are broken https://www.dropbox.com/s/9w5f3khqr74v3gk/Screenshot%202014-06-19%2015.07.43.png
[13:10] <mterry> robru, well in the absence of ogra_, can I request a silo for line 39?
[13:23] <davmor2> popey: is the google+ app still not showing the OSK for you today?
[13:24] <popey> yeah, fine at home on wifi
[13:25] <popey> i think it was the dodgy connection
[13:25] <popey> all that js used in the input fields
[13:26] <davmor2> popey: next time you are out and about then, try opening gmail instead and use g+ tab in the gmail app and see if it works better there it did for me on 3g yesterday
[13:26] <popey> kk
[13:27] <Mirv> t1mp: both problems seems specific to your config / VM, they work fine here
[13:28] <t1mp> ok
[13:37] <Mirv> mterry: I could assign one, but we're out of silos. let's see if something can be done about that.
[13:39] <davmor2> Mirv: so when is the world fixer landing?
[13:40] <Mirv> mterry: yes I can do something about it, assigning
[13:40] <Mirv> davmor2: when rsalveti wakes up and tells us emulator is working
[13:40] <mterry> Mirv for mayor!
[13:40] <davmor2> I wonder if rsalveti leaves his machine on and if we can ping him awake?
[13:41] <Mirv> davmor2: if he has audible alarm, yes we could try :)
[13:42] <davmor2> Mirv: I just hope he doesn't live in a Catholic country that celebrates whatever day off it is :)
[13:49] <mhr3> Mirv, set 014 as ready
[13:50] <Mirv> mhr3: extremely well tested? :)
[13:50] <boiko> barry: hi, would you mind merging the trunk of addressbook-app in your py3 branch?
[13:50] <mhr3> Mirv, of course :)
[13:50] <Mirv> mhr3: ok, we'd need a core dev here. or maybe #ubuntu-devel.
[13:51] <Mirv> (packaging acks)
[13:51] <mhr3> yea, there will be quite a bit of changes there
[13:51] <barry> boiko: sure thing
[13:51] <boiko> barry: thanks!
[13:53] <mhr3> Mirv, will you ping someone?
[13:53] <barry> boiko: wait, addressbook-app?  isn't that already merged into trunk?
[13:54] <boiko> barry: oups, sorry, I meant messaging-app
[13:54] <barry> boiko: gotcha
[13:54] <Mirv> mhr3: yes, generally asking on #ubuntu-devel
[13:55] <mhr3> Mirv, k, /me moves on
[13:56] <Mirv> mhr3: thostr_: actually, this is more complicated now that there's a NEW package
[13:56] <mhr3> Mirv, ehm?
[13:56] <Mirv> that might pose a timing problem
[13:56] <mhr3> what new pkg?
[13:56] <Mirv> libunity-scopes2
[13:56] <Mirv> so archive admin would need to accept that
[13:56] <mhr3> it's not new, it's upgraded
[13:56] <mhr3> from ..1
[13:57] <Mirv> sure it's not new as in new, but it's new as in it goes to new queue.. although hmm did we have autoaccept for touch only packages..
[13:57] <Mirv> anyhow, if I get acks I think it's ok, we just need 1 person more to be pinged at the right time
[13:57] <barry> boiko: merged and pushed (but untested)
[13:58] <boiko> barry: ok, let's wait to see what jenkins says about it :)
[14:02] <Mirv> mhr3: http://pastebin.ubuntu.com/7669252/
[14:03] <mhr3> seb128, yes, we'll do that once we support it, currently it wouldn't work anyway
[14:03] <seb128> mhr3, ?
[14:03] <seb128> mhr3, splitting binaries in the packaging is not something that "doesn't work currently"
[14:04] <seb128> or wouldn't work
[14:04] <mhr3> seb128, i mean even if they were split pkging-wise, they wouldn't work
[14:04] <seb128> it's just doing the cp to a different directory
[14:04] <mhr3> so what's the point
[14:04] <seb128> how wouldn't they work?
[14:04] <seb128> oh, you mean the old soname one?
[14:04] <mhr3> yes
[14:05] <seb128> mhr3, alright, it's because it's you
[14:05] <seb128> Mirv, +1
[14:05] <Mirv> thanks
[14:07] <mhr3> i feel so special now :)
[14:08] <davmor2> Mirv: rsalveti is online knobble him quick before someone else does
[14:08] <Mirv> ok, estimating it will take some time before I can m&c and start unity8 rebuild for qt5.3. but ricardo will probably need time with the emulator anyhow.
[14:08] <Mirv> davmor2: :)
[14:11]  * Mirv will start to drift to evening mode where I wait for the word to do publishing (which will take at minimum 0.5h since prepare-silo + watch_only build are needed)
[14:11] <Laney> you'd have had to do an upload of the old package with the split
[14:12] <Laney> then the transition would have been normal
[14:12] <Laney> unless I'm mistaken
[14:13] <rsalveti> haha
[14:13] <rsalveti> Mirv: were you able to test the emulator?
[14:14] <rsalveti> just got up, let me go over irc
[14:15] <rsalveti> davmor2: yeah, it's holiday today but I'm not taking it (appending post rtm)
[14:17] <davmor2> rsalveti: Who'd of guessed that a south american country would celebrate catholic holidays ;)
[14:17] <rsalveti> :-)
[14:19] <mhr3> Mirv, hm, when an image is building is it taking stuff from -proposed or only main?
[14:20] <rsalveti> only main
[14:24] <Mirv> rsalveti: no, I didn't know how to do that - or yes I tested the emulator via QtC but even though I've Qt 5.3 on the desktop it created 5.2 x86 emulator
[14:25] <rsalveti> Mirv: no worries, testing it now
[14:26] <Mirv> mhr3: only main, that's why we always wait for stuff to hit release pocket
[14:26] <mhr3> Mirv, i had that feeling, but naming the channel devel-proposed doesn't help to make it clear
[14:27] <Mirv> mhr3: that's very true. two aspects of what's proposed.
[14:27] <bfiller> Mirv: we fixed gallery-app for qt5.3 problem but I haven't released a click yet as a few AP tests are failing
[14:28] <Mirv> bfiller: yes, I noticed, thanks. and ok.
[14:28] <bfiller> brendand_: thanks for helping on the AP tests for gallery
[14:28] <bfiller> brendand_: I would have asked artmello but he's out today
[14:29] <brendand_> bfiller, i'll try and look at it today
[14:29] <bfiller> brendand_: thanks
[14:33] <cjwatson> tedg: man dh_apport
[14:34] <cjwatson> Ha, I'd forgotten writing that :)
[14:34] <cjwatson> I see the NAME section is wrong, boo
[14:34] <rsalveti> Mirv: do we need a rebuild for unity8?
[14:35] <Mirv> rsalveti: yes, I'll kick it as soon as I can M&C the department support silo
[14:36] <Mirv> the current unity8 will continue to work though until the published one migrates to release pocket
[14:38] <rsalveti> right
[14:43] <kgunn> Mirv: any way i could get a silo for line 11 ? its needed for pre-flight testing...not landing just yet.
[14:45] <Mirv> kgunn: done, landing-015
[14:45] <kgunn> Mirv: thanks a bunch!
[14:54] <rsalveti> Mirv: emulator worked fine, the only difference I noticed is that when you move back to the apps scopes, the background stays blank: http://people.canonical.com/~rsalveti/emulator-unity8.png
[14:55] <rsalveti> Mirv: before you could see the scopes in the bottom
[14:55] <rsalveti> while doing the transition
[14:55] <rsalveti> but it works fine after you dismiss the greeter completely
[14:55] <rsalveti> not sure if this is also something that is happening on the device
[14:55] <rsalveti> as the qt stack itself seems to be fine
[14:57] <Mirv> rsalveti: ok, that's good news (in general). I don't think that happens on the device if I understood the situation correctly.
[15:00] <Mirv> rsalveti: oh actually there's the backround pattern similarly only before it finishes, but that might be of course because of the other scopes work too. good catch and worth filing a bug for.
[15:01] <Mirv> and Mir also landed last night..
[15:01] <rsalveti> right
[15:01] <Mirv> that actually seems weird enough that I don't think it was there yesterday
[15:03] <rsalveti> let me update my flo to se
[15:03] <rsalveti> see
[15:22] <rsalveti> Mirv: yeah, seems to be happening only on the emulator
[15:22] <rsalveti> will open a bug for it
[15:31] <rsalveti> Mirv: working fine after a reboot, can't reproduce it anymore
[15:31] <rsalveti> so it might just be something that happened because of the upgrade
[15:31] <rsalveti> so emulator is not blocking anything anymore :-)
[15:42] <elopio> brendand: the filemanager issue comes from image 88, so it doesn't have to do with the toolkit.
[15:42] <elopio> that's good.
[15:43] <elopio> balloons: I saw dpm merging some things about places models. But he's not around. Do you know something about it?
[15:43] <balloons> rev 88 have a regression?
[15:45] <brendand> elopio, i've got a handle (kinda) on the filemanager issues
[15:45] <elopio> balloons: it doesn't seem to affect the user experience
[15:45] <elopio> balloons: but when the test is run with autopilot, the model is incomplete.
[15:45] <balloons> elopio, we pushed several updates.. landing something from dpm to fix the setPath issue, and both of your merge test cleanups
[15:46] <brendand> elopio, the objectName is not set properly
[15:46] <elopio> balloons: I was trying to test it on desktop, now I get:
[15:46] <elopio> file:///usr/share/filemanager/qml/filemanager.qml:24:1: module "com.ubuntu.PlacesModel" is not installed
[15:46] <elopio>      import com.ubuntu.PlacesModel 0.1
[15:46] <balloons> elopio, with trunk or ?
[15:46] <elopio> balloons: yes, trunk.
[15:47] <balloons> https://code.launchpad.net/~dpm/ubuntu-filemanager-app/placesmodel
[15:48] <balloons> elopio, looks like that problem never got fixed;
[15:48] <balloons> https://code.launchpad.net/~dpm/ubuntu-filemanager-app/placesmodel/+merge/223548
[15:48] <balloons> and I merged it..
[15:48] <balloons> whoops
[15:48] <brendand> 97                 objectName: model.objectName
[15:48] <brendand>  74                objectName: "place" + folderName(path).replace(/ /g,'')
[15:48] <Mirv> mhr3: it seems the landing is giving us some problems after all simply because the autopkg tester machines are buried in load
[15:49] <elopio> brendand: he kept the object names on his merge.
[15:49] <balloons> looks like a silly mistake on my part
[15:50] <brendand> elopio, how did it pass the ci testing then?
[15:50] <elopio> because it should work.
[15:51] <elopio> I'm trying to get it working here to confirm, but I can't run it.
[15:51] <brendand> elopio, why should it work? it doesn't work
[15:52] <elopio> brendand: the lines you pasted seem correct.
[15:53] <Mirv> rsalveti: I collected Qt 5.3 packaging acks in one pastebin, could you go through it or should I ask some other core-dev? http://pastebin.ubuntu.com/7668640/
[15:54] <rsalveti> sure
[15:54]  * popey hugs balloons
[15:54] <popey> balloons: does that need a merge to revert it?
[15:54] <rsalveti> let me take a look
[15:54]  * balloons waves to popey
[15:54] <popey> be nice to get it done for image #90 ☻
[15:55] <rsalveti> Mirv: for fcitx-qt5-0.1.2 we don't need to create a ubuntu version for it
[15:55] <balloons> popey, does the store let us push the last click up now or now?
[15:55] <rsalveti> just append build1
[15:55] <rsalveti> instead
[15:55] <balloons> aka, can we simply rollback on rev
[15:55] <Mirv> robru: mhr3: I'm doing m&c for landing-014 already now so that I can start landing-005 unity8 rebuild earlier.
[15:55] <rsalveti> Mirv: https://launchpad.net/ubuntu/utopic/+source/libalien-wxwidgets-perl/0.65+dfsg-2build1
[15:55] <popey> balloons: that makes no sense ☻
[15:55] <rsalveti> for example
[15:55] <rsalveti> Mirv: that way the debian auto import will still work
[15:55] <popey> balloons: we would need to make a r211 or greater.
[15:56] <balloons> popey, haha.. ok trying again. Can we push r209.click to the store or will it complain
[15:56] <robru> Mirv, cool
[15:56] <balloons> popey, ok, so if I push 209 as 211 it works, otherwise no dice
[15:56] <rsalveti> Mirv: same for gammaray
[15:56] <mhr3> Mirv, i can already see that autopkgtest for unity-scopes-api, because we forgot to update it :/
[15:56] <mhr3> Mirv, eh.... will fail
[15:56] <rsalveti> Mirv: maliit-framework seems fine (ack)
[15:56] <popey> balloons: so long as everything says 211, sure.
[15:57] <balloons> popey, or I can just grab the mp, revert it and merge
[15:57] <balloons> might be better to do that
[15:57] <rsalveti> Mirv: oxide-qt as well
[15:57] <popey> yeah
[15:57] <balloons> on it
[15:57] <Mirv> rsalveti: true. hmm, that version number would be lower than the current ubuntu1. I'm not sure if I'd now delete those two packages, how long it would take for them to properly disappear from the PPA so that build1:s could be uploaded.
[15:57] <popey> balloons: thanks!
[15:58] <mhr3> Mirv, ah, but it was the first time, so it's just "Always failed"
[15:58] <rsalveti> Mirv: right
[15:58] <Mirv> mhr3: "super well tested", right! :)
[15:58] <cjwatson> Mirv: should just take a PPA publisher run, 15 minutes or so
[15:58] <rsalveti> if so, not that much then
[15:58] <cjwatson> but I don't recall if the citrain bugs with lowering versions have been fixed
[15:58] <mhr3> Mirv, clearly ci should run our autopkgtests :P
[15:59] <brendand_> balloons, so what happened?
[15:59] <cjwatson> you'd want somebody to double-check what versions it's going to copy ...
[15:59] <Mirv> rsalveti: if there's risk involved (I know citrain has been a bit buggy in that department), I'd possibly just want to file a bug assigned to me to make sure they get back to synced status later
[15:59] <rsalveti> Mirv: right, might be easier at this point
[16:00] <Mirv> even with 5.2 funky stuff happened and didier is not around necessarily anymore at that point
[16:01] <rsalveti> Mirv: the rest seems fine as well
[16:01] <rsalveti> Mirv: yeah, just make sure that every package we added 0ubuntu1 as rebuild to get a bug
[16:01] <rsalveti> so you can clean up the sync
[16:02] <Mirv> rsalveti: ok, I'm doing that now
[16:02] <Mirv> (and kicked unity8 rebuild)
[16:02] <rsalveti> great
[16:02] <davmor2> Mirv: landing meeting, it might be wise for you to be there
[16:03] <Mirv> davmor2: uh oh, a second
[16:05] <balloons> brendand_, what happened? Well I'm reverting the merge. I was trying to merge leo's code, and I did, but it seems I merged david's code also. You can see 2 merges
[16:06] <brendand_> balloons, oh, was dpm's code not ready?
[16:06] <balloons> brendand_, no
[16:07] <brendand_> balloons, ok - cool
[16:07] <balloons> popey, https://code.launchpad.net/~nskaggs/ubuntu-filemanager-app/revert-r209/+merge/223783. Diff looks good, confirming it runs on the device
[16:16] <elopio> balloons: thanks. I reported a bug and linked to your branch.
[16:16] <elopio> brendand_: I'm looking at calendar now.
[16:17] <brendand_> elopio, read my mind :)
[16:17]  * balloons needs to to finishing fixing up the isolation on calendar
[16:18] <davmor2> popey: I got a new webcam for my main system so I wonder if that and the million web connections was having a knock on effect :)
[16:18] <elopio> brendand: oh, and the failure on the toolkit is fixed on staging
[16:18] <elopio> I never reported a bug about it. I will.
[16:40] <elopio> emacs
[16:40] <elopio> no, not that.
[16:41] <elopio> brendand: the failure on the calendar is because you reenabled the OSK, but didn't add the swipe_into_view calls needed to show the all the fields.
[16:41] <elopio> the fix is easy, but I would like to make it a little better than just patching it. The test is too big.
[16:43] <balloons> https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1268640
[16:43] <balloons> seems only clock and rss reader left
[16:45] <elopio> nice :)
[16:45] <elopio> next step is harder, to actually use it.
[16:49] <Mirv> this will be a relatively long evening...
[16:49] <robru> Mirv, bad news?
[16:49] <Mirv> robru: no, just slowness in CI Train etc
[16:49] <robru> ah
[16:50] <Mirv> unity8 rebuild should be "published" in around 20 mins. build with watch only will take around 40 mins (!).
[16:50] <Mirv> prepare-silo maybe 5 in between
[17:00] <balloons> popey, https://myapps.developer.ubuntu.com/dev/click-apps/159/changerequest/
[17:00] <popey> thanks balloons
[17:01] <Mirv> hey hmm I can parallize just slightly here
[17:03] <Mirv> yay, saved 5 mins at least
[17:03] <popey> Mirv: https://code.launchpad.net/~andrew-hayzen/ubuntu-seeds/music-app-remove-grilo/+merge/223718
[17:03] <robru> stgraber, want to assign line 41?
[17:04] <popey> are you able to ส็็༼ ຈلຈ༽ส็็ that?
[17:04] <popey> dammit, i mean "a pprove"
[17:04] <popey> stupid script
[17:04] <Mirv> popey: let me check, I'll ส็็༼ ຈلຈ༽ส็็ it if it's fine
[17:04] <popey> ta
[17:05] <stgraber> robru: when I'm back from lunch, sure
[17:05] <robru> stgraber, alright
[17:09] <popey> phew, removed it, can now say approve..
[17:09] <robru> popey, what? all I saw was ส็็༼ ຈلຈ༽ส็็
[17:10] <popey> :þ
[17:10] <robru> lol
[17:10] <davmor2> popey: what crazy keyboard setup were you in then?
[17:10] <popey> i wasn't. for some reason I thought it was a good idea to alias "approve" to ส็็༼ ຈلຈ༽ส็็
[17:10] <popey> which I came to regret after realising how much I use the word "approve"
[17:11] <robru> lol
[17:11] <davmor2> popey: haha
[17:15] <davmor2> Mirv: so how is the world fix coming?
[17:15] <davmor2> we nearly fixed yet?
[17:16] <rsalveti> ส็็༼ ຈلຈ༽ส
[17:20] <popey> i like that the second hit on google for ส็็༼ ຈلຈ༽ส็็ is a log of this irc channel from 3 months ago ☻
[17:23] <Mirv> davmor2: nearly, nearly... silo is now prepared correctly, watch only build has been running for 20 mins. if no surprises, in 15 mins or so it's time to hit publish button.
[17:30] <rsalveti> :-)
[17:31] <Mirv> world saving is in progress, let's see how it goes
[17:31] <Mirv> sorry, world fixing
[17:31] <robru> Mirv, errr mah gerrrrd
[17:34] <Mirv> "Finished: SUCCESS" \o/
[17:35] <Mirv> http://pastebin.ubuntu.com/7670340/
[17:36] <robru> Mirv, holy hell
[17:40] <popey> https://lists.ubuntu.com/archives/utopic-changes/2014-June/thread.html Mirv the spammer
[17:40] <stgraber> boiko: you've got silo 6
[17:41] <boiko> stgraber: thanks!
[17:43] <Mirv> :)
[17:56] <davmor2> robru: why were you surprised it's been tested to hell and back
[17:56] <davmor2> Mirv: \o/
[18:00] <rsalveti> Mirv: alright :-)
[18:04] <Mirv> ok it's time for me to drift off for good
[18:04] <Mirv> stuff like https://launchpad.net/ubuntu/+source/qtxmlpatterns-opensource-src/5.3.0-2 has now indeed started building, in addition to the actually landed packages that were readily built
[18:05] <Mirv> hopefully everything will go fine over the next few hours, but if not just discuss on #ubuntu-devel what's remaining to get a migration to release pocket finished
[18:05] <robru> davmor2, not surprised that it worked, just impressed that it's finally happening ;-)
[18:07] <rsalveti> yeah, I know we got new packages as well, so might need help from an archive admin
[18:08] <robru> davmor2, Mirv http://wildstar-nerds.com/wp-content/uploads/2014/03/itshappening.gif
[18:09] <robru> wow, I broke the internet
[18:41] <cjwatson> rsalveti: sadly I have not yet finished/landed the Launchpad patch to cause NEW to take effect on copies; citrain is supposed to ask for pre-review of any new packages by an archive admin for that reason
[18:42] <rsalveti> oh, got it
[18:42] <cjwatson> did that pre-review not happen then?
[18:54] <rsalveti> I'm not sure, Mirv would know, didn't follow that landing
[19:41] <rsalveti> cjwatson: https://launchpad.net/ubuntu/+source/qtgraphicaleffects-opensource-src is failing to build because qtdeclarative5-dev now depends on a new package (libqt5quickwidgets5) that is probably not yet in main
[19:41] <rsalveti> cjwatson: can you give us a hand with that?
[19:42] <rsalveti> libqt5quickwidgets5 is p rovided by qtdeclarative-opensource-src
[19:50] <cjwatson> rsalveti: moved to main (effective after next publisher run, check rmadison in half an hour or whatever)
[19:51] <rsalveti> cjwatson: great, thanks
[19:52] <cjwatson> you should be able to retry when that shows them in main
[19:53] <rsalveti> yeah
[19:53] <rsalveti> thanks :-)
[20:04] <sergiusens> robru: seems the choo choo is down?
[20:06] <sergiusens> robru: my silo on line 42 is ready never showed up
[20:06] <robru> sergiusens, sorry I'm in a meeting gimme 20
[20:06] <sergiusens> no rush
[20:06] <robru> sergiusens, i see your line 42
[20:06] <robru> stgraber, can you assign line 42?
[20:12] <stgraber> robru: yep
[20:12] <robru> stgraber, thanks
[20:13] <stgraber> sergiusens: you've got #14
[20:13] <sergiusens> ty
[20:41] <cjwatson> rsalveti: I've retried qtgraphicaleffects-opensource-src, since that override change is published
[20:41] <robru> cjwatson, sooo... just looked at excuses for the first time, seeing a lot of red around this qt5.3 landing... can I help in any way?
[20:42] <rsalveti> cjwatson: great, thanks so much
[20:43] <cjwatson> robru: suspect some of those are retriable, but I'm just briefly stopping in, not going to be able to look seriously just now
[20:43] <robru> hmm
[20:43] <robru> figures mirv's off
[20:44] <cjwatson> not sure he has autopkgtest retry privs anyway
[20:44] <robru> cjwatson, right but he knows the most about qt
[20:44] <cjwatson> have experimentally retried click-update-manager
[20:44] <robru> also it's his landing
[20:44] <cjwatson> yeah but I think several of them may just be transient uninstallabilities, so don't require qt expertise
[20:44] <robru> cjwatson, ah, i hope so
[20:45] <cjwatson> retried qtcreator-plugin-ubuntu too, but need to wander off now
[20:45] <cjwatson> if that helps I'll come back and poke more retries later
[20:45] <cjwatson> (i.e. an hour or two)
[20:45] <robru> cjwatson, great, thanks
[20:56] <cjwatson> robru: ok, I had a few more moments - they all look like temp uninstallability issues, so retried all I could see, should be better soon
[20:56] <robru> cjwatson, sweet, thanks a ton
[21:06] <jhodapp> robru: can you reconfigure silo 2 for me please?
[21:06] <robru> jhodapp, yep
[21:06] <jhodapp> thanks
[21:07] <robru> jhodapp, you're welcome
[21:07] <robru> jhodapp, rsalveti : done
[21:22] <rsalveti> robru: thanks
[21:22] <robru> rsalveti, you're welcome!
[21:39] <rsalveti> robru: not sure if you're able to help
[21:39] <rsalveti> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[21:39] <rsalveti> autopkgtest for unity-scopes-api 0.5.0+14.10.20140619-0ubuntu1: Always failed (Jenkins: public, private)
[21:39] <rsalveti> for qtbase
[21:39] <rsalveti> it's blocking quite a few packages because of this failure
[21:40] <rsalveti> https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-adt-unity-scopes-api/lastBuild/?
[21:40] <Laney> Always failed does not block migration
[21:40] <Laney> see "Valid candidate"
[21:40] <robru> rsalveti, "always failed" won't block it, it's only when it's red "regression". also note that it says valid candidate
[21:40] <robru> what laney said
[21:40] <rsalveti> oh, great
[21:40] <rsalveti> weird state though :-)
[21:40] <Laney> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt is the next stage where you should look for the real reason
[21:41] <rsalveti> so it seems everything is in a valid state
[21:41] <rsalveti> just waiting
[21:42] <rsalveti> Laney: yeah, just saw the failure and thought it would block
[21:42] <robru> rsalveti, eh, pyqt5 looks blocked and so does qtgraphcaleffects, not sure if we care much for those
[21:42] <Laney> is there a transition?
[21:42] <Laney> looks like it's not completed as far as proposed-migration is concerned
[21:43] <rsalveti> hm, qtgraphicaleffects-opensource-src is outofdate
[21:44] <cjwatson> pyqt5 is definitely an issue, you have to care
[21:44] <cjwatson> looks like wrong dependencies
[21:44] <cjwatson> libqt5gui5-gles doesn't exist on armhf
[21:45] <cjwatson> qtgraphicaleffects-opensource-src I think will clear next run
[21:45] <robru> cjwatson, yeah, sorry, I didn't mean it was ok to break that, I meant more like "it's not on the phone and not blocking the rest of qt5.3"
[21:45] <cjwatson> https://launchpad.net/ubuntu/+source/qtgraphicaleffects-opensource-src/5.3.0-2/+build/6078216 says it's built
[21:45] <cjwatson> robru: right, but it is blocking
[21:45] <cjwatson> (according to update_output)
[21:45] <cjwatson>     * i386: etm-qt, libqgsttools-p1-touch, libqt5multimedia5-touch, libqt5multimedia5-touch-plugins, pyqt5-dev-tools, pyqt5-examples, python3-pyqt5, python3-pyqt5-dbg, python3-pyqt5.qsci, python3-pyqt5.qtmultimedia, python3-pyqt5.qtmultimedia-dbg, python3-pyqt5.qtopengl, python3-pyqt5.qtopengl-dbg, python3-pyqt5.qtpositioning, python3-pyqt5.qtpositioning-dbg, python3-pyqt5.qtquick, python3-pyqt5.qtquick-dbg, python3-pyqt5.qtsensors, ...
[21:45] <cjwatson> ... python3-pyqt5.qtsensors-dbg, python3-pyqt5.qtserialport, python3-pyqt5.qtserialport-dbg, python3-pyqt5.qtsql, python3-pyqt5.qtsql-dbg, python3-pyqt5.qtsvg, python3-pyqt5.qtsvg-dbg, python3-pyqt5.qtwebkit, python3-pyqt5.qtwebkit-dbg, python3-pyqt5.qtx11extras, python3-pyqt5.qtx11extras-dbg, python3-pyqt5.qtxmlpatterns, python3-pyqt5.qtxmlpatterns-dbg, python3-windowmocker, qtdeclarative5-qtaudioengine-touch-plugin, ...
[21:45] <cjwatson> ... qtdeclarative5-qtmultimedia-touch-plugin, qtmultimedia5-touch-dbg, retext, retext-wpgen
[21:46] <cjwatson> similar on other arches
[21:46] <robru> sweet merciful jeebus
[21:46] <rsalveti> hm, it shouldn't be depending on libqt5gui5-gles
[21:46] <cjwatson> most of that is fallout from pyqt5
[21:46] <rsalveti> let me check the package
[21:46] <cjwatson> not sure about the qtmultimedia-opensource-src-touch stuff though
[21:47] <cjwatson> hm, is qtmultimedia-opensource-src-touch still a thing?  it doesn't appear to be modified in -proposed
[21:48] <robru> no idea
[21:50] <cjwatson> rsalveti: do you know?
[21:50] <robru> I gotta step out for lunch, brb
[21:50] <rsalveti> cjwatson: no, we can kill that one
[21:50] <cjwatson> ok, so removals at the same time as transitions are kinda awkward
[21:51] <cjwatson> can we kill it without breaking the current stack in utopic release?
[21:52] <rsalveti> yeah, the qtmultimedia-touch packages are not used anymore on touch
[21:52] <rsalveti> but I don't get why it's a problem for this transition
[21:53] <cjwatson>  libqgsttools-p1-touch : Depends: libqt5multimedia5-touch (>= 5.1.1+git20131205+8230c02-0ubuntu4) but it is not going to be installed
[21:53] <cjwatson>  libqt5multimedia5-touch : Depends: qtbase-abi-5-2-1
[21:53] <cjwatson> anyway, give me a reason that I can copy and paste into remove-package and I'll kill it off
[21:54] <cjwatson> preferably including what it's superseded by
[21:55] <rsalveti> cjwatson: it was needed when we were using qtmultimedia directly, as the -touch version uses gstreamer 1.0. Since we landed media-hub, the abstraction uses that instead
[21:55] <rsalveti> not using gstreamer anymore
[21:56] <rsalveti> so that's why we're not using that package anymore
[21:56] <rsalveti> and didn't update to qt 5.3
[21:56] <cjwatson> <cjwatson@amber ~>$ remove-package -m 'requested by rsalveti; Ubuntu Touch now uses media-hub rather than gstreamer; blocks Qt 5.3 transition' qtmultimedia-opensource-src-touch
[21:57] <cjwatson> ?
[21:57] <rsalveti> cjwatson: +1
[21:57] <cjwatson> bye-bye
[21:57] <rsalveti> I'm checking pyqt5, there's probably a wrong symbol in qtbase (pointing out to the wrong package)
[21:57] <cjwatson> somebody should possibly hoover up its bugs
[21:57] <rsalveti> yeah, jhodapp mind doing that?
[21:58] <rsalveti> as you owned that package
[21:58] <cjwatson> I don't see any other problems once pyqt5 is fixed, so hopefully that'll do it
[21:59] <rsalveti> great
[22:03] <sergiusens> can someone please rebuild the powerpc build for nuntium in silo 14? Having issues again
[22:06] <mterry> robru, you around?  Can you reconfigure silo 012?
[22:06] <cjwatson> sergiusens: retried
[22:14] <mterry> stgraber, can you reconfigure silo 012 for me?  I added a unity-system-compositor branch to reduce animation resources
[22:14] <sergiusens> ty
[22:17] <stgraber> mterry: sure, last thing for the day though, I EODed 15min ago
[22:17] <mterry> stgraber, oh sorry, you were still listed as the sheriff
[22:18] <stgraber> mterry: done
[22:18] <mterry> stgraber, thanks, have a good day!
[22:19] <stgraber> mterry: btw, aren't you a coredev?
[22:20] <mterry> stgraber, yes
[22:20] <stgraber> mterry: ok, so you could just have done it yourself then :)
[22:20] <mterry> stgraber, oh what?  I thought that was special landing team powers
[22:20] <mterry> Are all core devs on the landing team?
[22:21] <stgraber> mterry: nope, anyone who has write access to the spreadsheet and is in ~ubuntu-core-dev has the right to assign, reconfigure, publish, clean, ... silos
[22:21] <mterry> huh...
[22:21] <mterry> ok
[22:21] <mterry> stgraber, thanks!  Now go log off  :)
[22:21] <stgraber> Jenkins recognizes both ACLs, landing-team for the non-coredevs + ubuntu-core-dev for the rest (I'm not in the landing team LP team)
[22:23] <Laney> really?
[22:24] <robru> Laney, yeah we added all core devs to the jenkins ACLs when sil and I moved to the foundations team
[22:24] <Laney> I don't see much that's useful when I press reconfigure
[22:24] <Laney> but I don't know where to look admittedly
[22:24] <Laney> could just be all automatic from the spreadsheet
[22:25] <robru> Laney, reconfigure job is only if you're adding an MP within the same set of projects already configured. if you need to add new projects, you have to use the assign silo tool from the spreadsheet
[22:25] <Laney> Interesting, will have to try it soon
[22:26] <robru> Laney, feel free to ping sil2100 or I if you need any help with anything
[22:27] <Laney> will do, thanks
[23:12] <cjwatson> heh, a bunch of qt5 stuff just got auto-synced from Debian, I see
[23:12] <cjwatson> presumably you're cool with that or else it'd have *ubuntu* versions
[23:13] <cjwatson> pyqt5 qtquick1-opensource-src qtscript-opensource-src qttools-opensource-src qtwebkit-examples-opensource-src
[23:13] <robru> cjwatson, no idea
[23:23] <robru> cjwatson, wait, what's going on? debian just synced in a bunch of qt5.3 stuff that is conflicting with ours?
[23:25] <cjwatson> no, I wouldn't expect it to conflict, just newer versions
[23:25] <cjwatson> I'm sure it's fine, just thought I'd menion it
[23:25] <cjwatson> *mention
[23:25] <robru> cjwatson, do you know what the hold-up is at this point? are we just waiting for somebody to figure out pyqt5 still?
[23:25] <cjwatson> we had versions synced from Debian already, or they wouldn't have auto-synced
[23:25] <cjwatson> as far as I know yes
[23:26] <robru> cjwatson, any idea who I can punt that to?
[23:26] <cjwatson> sounded from the above as though rsalveti was working on it
[23:26] <robru> ah
[23:26] <robru> missed that bit
[23:26] <cjwatson> 22:57 <rsalveti> I'm checking pyqt5, there's probably a wrong symbol in qtbase (pointing out to the wrong package)
[23:26] <robru> thanks
[23:30] <cjwatson> of the Debian syncs, qtquick1/qttools are just symbols updates, qtwebkit-examples is a trivial upload-to-unstable-instead-of-experimental-because-Debian-doesn't-quite-have-copies thing, qtscript is symbols plus improving multiarch for -dev packages, pyqt5 is a fix from ScottK to fix a pyuic regression
[23:30] <cjwatson> so should all be fine


[21:40] <mup> Bug #1904064 opened: MAAS has no way to set a global, upstream proxy <MAAS:New> <https://launchpad.net/bugs/1904064>
[21:43] <mup> Bug #1904064 changed: MAAS has no way to set a global, upstream proxy <MAAS:New> <https://launchpad.net/bugs/1904064>
[21:49] <mup> Bug #1904064 opened: MAAS has no way to set a global, upstream proxy <MAAS:New> <https://launchpad.net/bugs/1904064>


[02:20] <OvenWerks> Eickmeyer[m]: it appears the latest update in 20.04 has screwed up dbus for us.
[02:21] <Eickmeyer[m]> The HWE kernel was recently released, so it's likely that.
[02:22] <OvenWerks> -controls does not work.
[02:22] <OvenWerks> al of the sudden
[02:22] <Eickmeyer[m]> I disagree. I used -controls today with no issue.
[02:22] <Eickmeyer[m]> On Focal.
[02:25] <OvenWerks> mine just started working
[02:25] <Eickmeyer[m]> Interesting
[02:35] <OvenWerks> Eickmeyer[m]: it appears that my FW device has some delay in starting
[02:36] <OvenWerks> if I take the buffer below 256 I get dbus errors
[02:36] <OvenWerks> I have had it run at 32/3 before
[02:36] <OvenWerks> I will do some hacking after I get my son some supper
[03:01] <OvenWerks> Eickmeyer[m]: interesting
[03:02] <OvenWerks> it appears the fw wire device will work fine on 32/3 if I use the ffado drivers but is limited to 256/2 with the alsa drivers
[03:09] <OvenWerks> Eickmeyer[m]: I definately need to document that the alsa FW drivers do not work well for lower latencies
[04:01] <Eickmeyer[m]> Very interesting.
[04:34] <OvenWerks> I have sent a message to the LAU ML asking if others have had this experience
[06:33] <Eickmeyer[m]> OvenWerks: Nah, I can't directly backport to the main backports repository. I just simply niglected to backport into the PPA for groovy and focal.
[13:44] <wonko> Forgot to rejoin here. :)
[13:44] <wonko> After I move I'm going to make an effort to spend more time helping out.
[17:40] <OvenWerks> Hard to remember to say things gender neutral :P  English is a pain in this, many languages have one word that covers both him and her
[17:54] <Eickmeyer[m]> Yeah, and now I'm dealing with Ralf again (I'm not engaging him directly, the CC has questions).
[18:16] <OvenWerks> RM has been kicked off of many email lists including LAU and LAD
[18:17] <OvenWerks> There has even been someone who tracked activity in these mial lists based on what RM was talking about and found his presence negatively affected membership numbers by reducing them as much as 50%
[18:18] <OvenWerks> I suspect he has a behavioral condition of some sort, either from birth or induced by something after that.
[18:19] <OvenWerks> He was left alone for a long time because once in a while he actually had something to say but at some point the negative effect of all the other times overrode that.
[18:22] <OvenWerks> similar to tom- on #ardour who some people have hidden on their irc client.
[19:35] <Eickmeyer[m]> Well, the Community Council is involved now.
[19:37] <OvenWerks> IMO it should be a no brainer, someone who doesn't even run ubuntu and hasn't for years.
[19:38] <OvenWerks> If you ever read any of his advice for doing something, you will find the absolute most convoluted method you can think of.
[19:38] <wonko> Yay, internet drama! :-D
[19:42] <OvenWerks> Eickmeyer[m]: another known MO for RM is that even after he is no longer able to post to an mailing list, he may continue to read them online from archive and answer people directly leaving the mailing list Return address intact resulting in the mailing list seeing answers to mail he has sent not to the list :P
 this is one reason the CC list is private ;)
 just saying
 @teward001 [just saying], Kind of not a good idea for the users list, but the dev list might benefit from being private in light of recent developments.
 @Eickmeyer [Kind of not a good idea for the users list, but the dev list might benefit from …], i meant specifically for CC not for your lists ;)


[07:47] <smb> morning
[07:59] <ppisati> smb: moin
[08:00]  * apw yawns
[11:15] <apw> ;;
[11:15] <apw> ppisati, i take it you are working with rob to get these patch sets for highbank in order
[11:41]  * apw does an application pass over u-k-t
[11:45] <smb>  /msg apw You should be pretty safe with today being a US holiday and the usual suspect on vacation
[11:45] <apw> heh
[12:27] <smb> infinity, apw, Just to let you know I updated bug 1218817 with some xcp/xen-api story (maybe a bit of an approach without too much motivation to dig deeper ...)
[12:27] <ubot2`> Launchpad bug 1218817 in xen (Ubuntu) "[FFE] Update to Xen-4.3 in Saucy" [High,New] https://launchpad.net/bugs/1218817
[12:27]  * henrix -> lunch
[13:01] <apw> smb, so is that saying, it was broke before, and not as broke after the 4.3 update ?
[13:03] <smb> apw, No, rather its broken as before at least for the levels I can use
[13:05] <ppisati> apw: yep, the request to pull those patches came from Rob
[13:17] <apw> ppisati, thanks
[14:24] <phillw> Hi good people,  I popped on an earlier day about possible issues with 3.11.0-4 this does not seem to be the culprit, but there are no logs available. As it is such a crash, I have to ask you how to trap the crashes.... http://pastebin.com/ACvL98hT
[14:26] <apw> phillw, welll normally if one cannot get any visible output when it occurs, we would be asking when it did work before
[14:26] <apw> phillw, if it works with some specific kernel, and not with another we can sometimes bisect for the reason
[14:29] <phillw> apw: I know one of the testers is trying to learn about bisecting. he is having an issue with LTS new release, this could be totally wrong in my reasoning, but it dies not really look like a fault of the kernel, more likely a driver. The problem is... the guys have no logs.
[14:30] <apw> jsaulisbury is our prime bisect expert, he often has a bunch of them on the go at once
[14:30] <phillw> is there a way to boot the system with backtrace>
[14:30] <apw> if the system was bugging and could tell you you owuld see it these days, it could replace the graphics
[14:31] <apw> so if it has not, you are likley broken if you have done the sysrq things when it hangs
[14:32] <phillw> sysrq?
[14:32] <apw> http://forum.pinguyos.com/Thread-REISUB-Safe-Reboot
[14:32] <apw> the alt-printscreen- plus letters
[14:34] <phillw> apw: if you read the paste... the system totally halts.
[14:35] <apw> define totally halts
[14:36] <apw> sysrq is done at a very very low level interrupt state, so it can work when the machine seems hung
[14:36] <phillw> apw: I'll suggest that to the OP
[15:30] <ppisati> brb
[17:50]  * apw calls it a day
[20:45] <nfk> what happened to xfs?


[02:07] <elky> nhaines: hi?
[02:45] <ianorlin> [#ubuntu-us-ca]
[02:45] <ianorlin> oops
[02:48] <ianorlin> hmm gah this open source bridge confrence has such good talks on youtube can't stop watching
[04:34] <nhaines> elky: hi!
[04:36] <elky> nhaines: hi, so it's meeting week :)
[04:37] <nhaines> elky: so it is!  Oh, it's Friday which means emails.
[04:37] <elky> :)
[04:37] <elky> i haven't done wiki so i'm hardly one to talk
[04:37] <elky> i'm about to do it now
[04:38] <elky> (wiki that is)
[04:38] <nhaines> I need to change my Google Calendar reminder.  It alerts me on Wednesday and Friday beforehand, but I'm just like "cool, keep Sunday night free."
[04:38] <nhaines> Yeah, I'll do the email.  Thanks for reminding me.
[04:38] <elky> np
[04:38] <ianorlin> and vivid release is Thursday
[04:50] <elky> weekees done
[04:58] <elky> and also on the slowco directory
[05:01] <nhaines> I'm very pleased because the $4 USB-OTG cable I got makes my tablet (and presumably also my phone) a very nice terminal emulator in Ubuntu.  Also Android.
[20:16] <philipballew> pleia2, Is getting a visa for Ghana a difficult process?
[20:16] <philipballew>  I am gonna help a friend out who has never left the country fill one out and apply today.


[03:15] <tigre> hello
[03:15] <tigre> group and IRC? cool
[09:13] <Bullrich> hello everyone
[14:07] <johnbristol> I'm trying to find a list of update changes to lubuntu 20.04 - is there an official file maintained online?
[18:48] <ubuntu9988> Would anyone know what command lubuntu installer uses to eject the install usb after installation?
[18:50] <ubuntu9988> I tried eject -p -m /dev/sdx; reboot; with no luck. this was in /sbin/casper-stop
[18:51] <ubuntu9988> the way the installer eject seems to disable the usb port itself so lubuntu boots from local disk not the live usb.
[18:53] <ubuntu9988> this is really interesting as only after unplugging the live usb and plugging it back in are you able to boot off of it.
[19:15] <halouxiajie> yo
[19:15] <halouxiajie> anybody around here
[19:20] <ubuntu9988> nm figured it out. efibootmgr
[21:55] <iffraff> Hi, i'm running 20.04 and I have a vpn configured.  it was working fine the after 30 mintues doing something else now I can't ssh to a remote host.  it says "no route to host"
[21:55] <iffraff> when I do a "dig" I can see that I am connected to the vpn, but for some reason it doesn't seem to connect the remote server
[22:00] <kc2bez[m]> iffraff: That seems like a question for your VPN provider. I don't know how Lubuntu has much of an impact on that if your connection is otherwise working.
[22:00] <iffraff> I see, i
[22:00] <iffraff> m  using open vpn,
[22:01] <iffraff> I've spoken with devops on the server side and others can hit the server, it seems like just my machine.
[22:01] <iffraff> it seems to have happened out of no where
[23:12] <greenonion> hi
[23:13] <greenonion> Guys Hi
[23:13] <greenonion> Wanna cry