[05:29] <mihir> Good Morning!!!
[06:10] <kalikiana> moin moin
[06:35] <rpadovani> balloons, https://code.launchpad.net/~rpadovani/ubuntu-calculator-app/fixLabel/+merge/220674
[06:39] <nik90_> morning folks :D
[06:39] <ahayzen_> o/
[07:16] <balloons> ahayzen_, vthompson http://developer.ubuntu.com/apps/platform/guides/acceptance-testing-using-the-page-object-model/
[08:26] <pkunal-parmar> renato, is there any contact EDS or other plugin for Contacts
[08:27] <renato> pkunal-parmar, yes you should use QtContacts
[08:27] <pkunal-parmar> and which manager i should use ?
[08:28] <pkunal-parmar> currently on my machine only invalid and memory is available
[08:29] <pkunal-parmar> renato, I think i need to install some plugin, can you tell me name ?
[08:29] <renato> pkunal-parmar, qtcontact5-galera
[08:29] <pkunal-parmar> ok, thanks
[08:51] <balloons> pkunal-parmar, when you get a chance to review; https://code.launchpad.net/~nskaggs/ubuntu-calendar-app/fix-ap-flo/+merge/219925
[08:51] <pkunal-parmar> sure
[08:59] <dpm> sergiusens, is it you I have to ping to release a new .click for the camera app? We did a translations fix and oSoMoN_ set up the landing, but I'm not sure what the last step is to include the click package with the fix in an image
[09:00] <dpm> I can go and grab you if you're not far away from 2B or in meetings
[09:17] <pink_> how can i install ubuntu emulator in my own laptop,which is ALREADY running ubuntu 14.04 LTS
[09:23] <elopio> balloons: can you please merge this before jenkins goes crazy again?
[09:23] <elopio> https://code.launchpad.net/~elopio/reminders-app/autopilot-add_notebook/+merge/219237
[09:37] <balloons> elopio, merging underway
[09:37] <elopio> thanks
[10:03] <t1mp> kalikiana: hello
[10:05] <kalikiana> t1mp: https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/skipFlakyUpdateAlarmRepeating/+merge/220780
[11:14] <AskUbuntu> gtkmm: Gtk::Toolbar overflow, hidden elements inaccessible | http://askubuntu.com/q/471058
[11:20] <gang651> Hello
[11:21] <gang651> I Have some problems with autopilot tests for Calendar
[11:21] <gang651> Do you know how to properly setup Calendar for Desktop
[11:21] <gang651> I'm unable to add any of Event
[11:22] <gang651> I seems that It tried to connect to some server
[11:31] <popey> balloons: http://popey.com/~alan/com.ubuntu.calculator_1.3.271_all.click
[11:49] <beuno> jdstrand, approved, not sure if the convention is that the approver merges or the proposer
[11:49] <beuno> (I'll see if I can get a jenkins instance to run tests and merge automatically in the next few weeks)
[11:57] <jdstrand> I'll merge, thanks
[13:13] <vthompson> http://paste.ubuntu.com/7504759/
[13:38] <ahayzen_> t1mp, FYI this is my WIP branch on the listitem actions
[13:38] <ahayzen_> t1mp, https://code.launchpad.net/~andrew-hayzen/music-app/listitem-actions
[13:48] <Laney> renato: I asked yesterday, but maybe you missed it - could you check the new upstream release of folks in ppa:laney/arm please?
[15:42] <oruc> hello


[00:20] <ericsnow> wallyworld_: thanks for the review on http://reviews.vapour.ws/r/549/ (I finally got around to responding)
[00:20] <wallyworld_> sure, i'll go look
[00:24] <ericsnow> wallyworld_: thanks
[00:54] <axw> wallyworld_: thanks for doing the backport - was about to do that
[00:54] <wallyworld_> axw: np, i got blocked on something else so thought i may as well
[01:12] <wallyworld_> ericsnow: what's happening with the current CI blocker?
[01:13] <ericsnow> wallyworld_: sinzui was going to add a 5 minute sleep before running backup in the script (or something like that)
[01:13] <wallyworld_> ok, thanks
[01:13] <wallyworld_> i guess we still added the wait for ha?
[01:13] <ericsnow> wallyworld_: I don't know what's going to happen with that blocker bug
[01:14] <ericsnow> wallyworld_: voidspace's patch did not go in
[01:14] <wallyworld_> oh ok
[01:14] <wallyworld_> was it rejected?
[01:14] <ericsnow> wallyworld_: incidentally, that failing test passed at least once today, so we must be relatively close on when HA is becoming ready
[01:15] <wallyworld_> mongo sorta sucks that it seems to lie to us about if it is ready
[01:15] <ericsnow> wallyworld_: yep
[01:16] <ericsnow> wallyworld_: that's the gist of the current blocker bug, if I understand correctly
[01:16] <wallyworld_> we need to find a solution
[01:16] <ericsnow> nate was talking about getting in touch with the mongo folks (I'll follow up tomorrow)
[01:17] <ericsnow> sounds like he has had some contact with them before about replica set stuff
[01:19] <ericsnow> wallyworld_: on that upload patch are you okay with me leaving the cmd tests as is (they do mock out the API client)
[01:19] <wallyworld_> yep
[01:19] <ericsnow> k
[02:17] <axw> wallyworld_: can't hear you anymore...
[02:54] <thumper> axw: FWIW, I was mostly joking about exa, yotta and zeta bytes...
[02:56] <wallyworld_> thumper: 640k is enough for anybody
[02:56] <axw> thumper: heh :)
[02:56] <thumper> for sure
[02:57] <axw> thumper: doesn't really hurt
[02:57] <axw> if someone tries it, it's likely to fail for the foreseeable future, but... may as well do the 10 minute job now and forget about it
[02:58] <axw> wallyworld_: sent out the email. I've got a workshop to go to at the school, heading off in a few
[02:58] <wallyworld_> axw: sure, tyvm
[05:09] <huwshimi> hatch: Ugh, now I have to mock classList.remove and classList.add because we don't have a dom to work with :(
[05:10] <hatch> huwshimi: wrong channel? :)
[05:10] <huwshimi> erm
[08:41] <bodie_> watching the first end-to-end run of an Action right now :)
[08:44] <bodie_> if anyone would like to play with / break it, we have a branch available at under "actions" https://github.com/juju-actions/juju/
[08:44] <bodie_> landing a commit in a moment that should make "do", "fetch", and "defined" functional, along with the charm-side stuff
[08:48] <bodie_> also some good content in the wiki at that fork
[08:58] <dimitern> bodie_, sweet \o/ I'll give it a try later today
[08:59] <bodie_> dimitern, awesome :) there's a Phoronix testing suite charm we have linked in our wiki, but marcoceppi knows more about how to use it
[08:59] <dimitern> bodie_, cool, thanks - I'll give you a shout if something is unclear :)
[09:17] <bodie_> dimitern, great, and feel free to open issues if you manage to break something
[09:17] <dimitern> bodie_, sure, no worries
[09:55] <voidspace> ericsnow: ping
[10:01] <dimitern> voidspace, jam1, standup?
[10:01] <voidspace> dimitern: ok
[10:02] <voidspace> dimitern: jam1 will be off won't he
[10:02] <dimitern> voidspace, ah, it's friday - yeah
[10:02] <voidspace> TheMue: stdup?
[10:15] <perrito666> morning
[10:18] <voidspace> perrito666: o/
[10:33] <dimitern> jamespage, ping
[10:34] <dimitern> jamespage, hey, a friendly reminder to send me that mail with request-address/interface use cases when you have time please :)
[10:34] <jamespage> on my list for today
[10:34] <dimitern> jamespage, thanks!
[12:48] <perrito666> how is the blocking status on CI?
[12:48] <rick_h_> heh, surprised no one's written an irc bot yet :) !ci-status
[12:52]  * perrito666 goes figure out if he is hearing gunshots or fireworks brb
[13:00] <perrito666> back
[13:42] <voidspace> ericsnow: ping
[14:33] <dimitern> voidspace, are you working on bug 1399277 as well?
[14:33] <mup> Bug #1399277: ensure-availability is not reliable <ci> <ha> <regression> <juju-core:In Progress> <https://launchpad.net/bugs/1399277>
[14:34] <voidspace> dimitern: yes
[14:34] <voidspace> dimitern: we hope this branch is the fix http://reviews.vapour.ws/r/583/
[14:35] <voidspace> dimitern: but it needs a review
[14:35] <voidspace> dimitern: and I'm not convinced it's sufficient but it will definitely help
[14:35] <voidspace> dimitern: I got a "ShipIt" but I added a change to go from "all healthy" to "majority healthy" which needs review
[14:35] <voidspace> dimitern: and as this changes ericsnow's code I'd really like him to see it before I merge it
[14:37] <dimitern> voidspace, ok, I'll have a look
[14:44] <voidspace> dimitern: PickNewAddress is done bar the tests, it's quite a funky little algorithm
[14:45] <voidspace> dimitern: several possible places for fence post errors, so needs careful checking
[14:46] <dimitern> voidspace, great!
[14:46] <dimitern> voidspace, you have a review btw
[14:47] <dimitern> voidspace, eww... my first comment got awkwardly formatted
[14:47] <voidspace> dimitern: I understand
[14:47] <voidspace> dimitern: and I don't know a better way than string comparison
[14:47] <voidspace> dimitern: I agree it's icky
[14:47] <voidspace> dimitern: suggestions welcomedc
[14:47] <voidspace> *welcomed
[14:48] <voidspace> dimitern: ericsnow has another PR that does the same thing but hides it in a function - I think I'll just merge that
[14:48] <dimitern> voidspace, this is an error coming from mgo, right?
[14:49] <voidspace> dimitern: right
[14:50] <sinzui> voidspace, I have also added a 5m sleep after status reports all machines has-vote. that change did improve the pass rate.
[14:50] <voidspace> sinzui: cool
[14:50] <voidspace> sinzui: only "improve", or "fixes the problem"?
[14:50] <voidspace> shame to add five minutes to the run time
[14:50] <sinzui> improved
[14:50] <voidspace> :-/
[14:51] <sinzui> a automatic retest passed. So we passed slowly
[14:51] <voidspace> if a five minute sleep doesn't solve this problem then a half hour sleep wouldn't - there's some other issue
[14:51] <voidspace> that at least is progress
[14:52] <sinzui> dimitern, how goes your work with bug 1397376
[14:52] <mup> Bug #1397376: maas provider: 1.21b3 removes ip from api-endpoints <api> <cloud-installer> <fallout> <landscape> <maas-provider> <juju-core:In Progress by dimitern> <juju-core 1.21:In Progress by dimitern> <https://launchpad.net/bugs/1397376>
[14:54] <dimitern> sinzui, I'm about to propose a fix for 1.22, just fixing a final test
[14:54] <sinzui> \o/
[14:54] <dimitern> sinzui, it took a lot of time to ensure I don't break something; live tested on maas, local, canonistack, ec2
[14:55] <sinzui> understood
[14:55] <dimitern> voidspace, ah, too bad then - go with string comparison :)
[14:59] <ericsnow> voidspace: o/
[15:32] <voidspace> ericsnow: hey, hi
[15:32] <voidspace> ericsnow: I made a change to IsReady
[15:33] <voidspace> ericsnow: I'd like your agreement before I merge
[15:33] <voidspace> ericsnow: http://reviews.vapour.ws/r/583/
[15:33] <ericsnow> voidspace: k
[15:33]  * ericsnow takes a look
[15:33] <voidspace> ericsnow: with the current implementation, if one state server in an HA environment goes down
[15:33] <voidspace> ericsnow: and *then* the user tries to backup
[15:33] <voidspace> ericsnow: IsReady will always report false and they can't backup
[15:33] <voidspace> ericsnow: so I changed IsReady to check for majority healthy rather than all healthy
[15:34] <voidspace> ericsnow: (majority healthy is the requirement a mongo replicaset has to be functioning)
[15:43] <perrito666> mm, tests dont like to be ctrl+z
[15:43] <natefinch> voidspace: why are we using health at all?    It's not at all clear what "up" means..... plus, there's a bug in the logic, because the member you're getting the status from always excludes its own value for health, so it'll default to false.
[15:43] <natefinch> voidspace: there's member status which seems much more detailed about what each state actually means.
[15:45] <alexisb> ericsnow, voidspace ping
[15:45] <voidspace> alexisb: pong
[15:45] <ericsnow> alexisb: hey
[15:46] <alexisb> hey guys, do you guys know where the April PyCon is going to be held?
[15:46] <voidspace> natefinch: interesting, that doesn't seem to happen in practise
[15:46] <alexisb> ie what location
[15:46] <voidspace> natefinch: so I think your're wrong about defaulting to false
[15:46] <ericsnow> alexisb: montreal
[15:46] <voidspace> alexisb: montreal
[15:46] <alexisb> ok thanls
[15:46] <alexisb> thanks
[15:46] <voidspace> alexisb: the proposed sprint date clashes with the pycon sprints
[15:46] <voidspace> alexisb: or is that deliberate?
[15:46] <alexisb> yep that is what I am working on
[15:46] <voidspace> alexisb: cool
[15:47] <voidspace> natefinch: if you were right, the current implementation would *always* return false
[15:47] <voidspace> natefinch: so backup could *never* work - which isn't what we're seeing
[15:52] <ericsnow> sinzui, voidspace: the current failure (connection refused) with the HA backup CI test may not be HA-related
[15:52] <ericsnow> sinzui, voidspace: see http://reviews.vapour.ws/r/590/
[15:53] <ericsnow> so, an API client is only good for a single request (and then disconnects)?
[15:53] <ericsnow> anyone ^
[15:54] <voidspace> alexisb: I have a talk and poster session on juju submitted to pycon
[15:54] <voidspace> alexisb: no idea if either has been (or will be) accepted yet
[15:54] <alexisb> voidspace, awesome
[15:54] <sinzui> ericsnow, I don't know, but I have hope that the 5m sleep gives juju a moment to gather its wits
[15:54] <voidspace> hehe
[15:54] <ericsnow> sinzui: I think it helped
[15:54] <voidspace> ericsnow: I'm merging  your PR with the better error checking for IsReady with mine
[15:55] <voidspace> just running tests
[15:55] <natefinch> voidspace: hmm that;s true.  Weird. I wonder why it doesn't work that way... since the docs definitely say the value doesn't exist for the member you get status from, and therefore the bool should default to false
[15:55] <sinzui> ericsnow, agreed, the test is still retried, but at least its odds of success are better
[15:56] <ericsnow> voidspace: I don't think we need to switch to WaitUntilReady to fix the current failures
[15:56] <voidspace> natefinch: my defence is that *that* code (in juju) pre-exists my PR which just waits for it
[15:56] <natefinch> voidspace: http://docs.mongodb.org/v2.4/reference/command/replSetGetStatus/
[15:56] <ericsnow> voidspace: though the fix to IsReady stands on its own
[15:56] <voidspace> ericsnow: I think it's an improvement and we *definitely* need to move to checking for majority healthy rather than all
[15:56] <natefinch> voidspace: oh yeah, totally... I just wondered if you knew why it was there.  I guess I should ask git who to ask
[15:56] <voidspace> ericsnow: otherwise if one state server goes down you can't backup!
[15:56] <voidspace> natefinch: it's ericsnow :-)
[15:57] <voidspace> natefinch: I did look in detail at the CurrentConfig and CurrentStatus meanings, but it was a little while ago now
[15:57] <ericsnow> natefinch: I just did what we were doing elsewhere in juju
[15:57] <voidspace> maybe mgo does helpful magic for us
[15:58] <ericsnow> natefinch: actually, the code I added just calls other code that predates mine
[15:58] <ericsnow> natefinch: that code is what does the check IIRC
[15:58] <voidspace> natefinch: in that doc I see "self" included in members with meaningful data
[15:58] <voidspace> i.e. health and state
[15:58] <voidspace> with "self": true
[15:59] <ericsnow> perrito666: here's that fix to try out: http://reviews.vapour.ws/r/590/
[15:59] <perrito666> ericsnow: going
[15:59] <voidspace> natefinch: "The members field holds an array that contains a document for every member in the replica set."
[15:59] <voidspace> natefinch: what are you reading?
[16:00] <natefinch> voidspace: replSetGetStatus.members.health
[16:00] <natefinch> The health value is only present for the other members of the replica set (i.e. not the member that returns rs.status.) This field conveys if the member is up (i.e. 1) or down (i.e. 0.)
[16:00] <voidspace> natefinch: hah, ah right
[16:01] <voidspace> natefinch: indeed, I concur with your reading
[16:01] <perrito666> ericsnow: you will need a bit of patience, this test takes a bit to run
[16:01] <voidspace> natefinch: so we should be checking for Member.self and assuming health: 1 for that member
[16:01] <voidspace> else you couldn't connect to it
[16:01] <ericsnow> perrito666: I figured as much
[16:01] <ericsnow> perrito666: thanks
[16:01] <voidspace> but looks like we don't need to in practise
[16:02] <voidspace> natefinch: ah, but see the MemberStatus struct
[16:02] <voidspace> natefinch: and specifically the Healthy field
[16:02] <voidspace>
[16:02] <voidspace>         // Healthy reports whether the member is up. It is true for the
[16:02] <voidspace>         // member that the request was made to.
[16:02] <voidspace> natefinch: so we specifically don't need to do that
[16:03] <voidspace> ericsnow: so this is my latest version: http://reviews.vapour.ws/r/583/diff/#
[16:03] <voidspace> ericsnow: my feeling is that it's only an improvement
[16:03] <voidspace> ericsnow: and so we should merge
[16:04] <natefinch> voidspace: yeah, but I wrote that, and the code does not seem to back it up (assuming the docs on mongodb are more likely to be accurate than my code comments)
[16:04] <voidspace> natefinch: yet it seems to be true in practise
[16:05] <ericsnow> voidspace: agreed
[16:05] <voidspace> ericsnow: I'm going to hit merge then, we'll see if it helps
[16:05] <ericsnow> voidspace: thanks for doing that
[16:06] <voidspace> ericsnow: we'll see...
[16:06] <voidspace> I need a break, biab
[16:08] <ericsnow> does anyone know if an API client is only good for a single request (and then disconnects)?
[16:09] <perrito666> sinzui: mgz_ abentley "ImportError: No module named boto" <-- what is boto?
[16:09] <sinzui> perrito666, it is a python lib for talking to aws
[16:10] <sinzui> perrito666, sudo apt-get install boto
[16:10] <ericsnow> voidspace: BTW, the "connection refused" condition for isConnectionNotAvailable should probably be dropped
[16:10] <perrito666> sinzui: oh ok, I though it was some internal module from ci
[16:10] <sinzui> perrito666, sudo apt-get install python-boto
[16:10] <ericsnow> voidspace: that message came from the API, not from mongo
[16:12] <ericsnow> cmars: could I get a review on http://reviews.vapour.ws/r/590/? (you're OCR, right?)
[16:12] <ericsnow> cmars: if I understood right, it should help unblock CI
[16:12] <cmars> ericsnow, yep, i'll take a look, was just reading 583
[16:12] <mgz_> perrito666: what sinzui said, but I think it's python-boto
[16:12] <perrito666> mgz_: it is
[16:12] <ericsnow> cmars: ta
[16:12] <cmars> ericsnow, ok, awesome. i know nothing about HA & replica sets, so i'll probably have lots of stupid questions
[16:13] <ericsnow> cmars: well, my patch is unrelated to HA :)
[16:13] <cmars> ericsnow, even better :)
[16:13] <ericsnow> cmars: and it's small
[16:16] <cmars> ericsnow, why can't you use an API client for more than a single request?
[16:16] <ericsnow> cmars: I haven't gotten any answer on that yet :P
[16:17] <ericsnow> cmars: I find it surprising if true (which is what perrito666 explained to me recently)
[16:17] <cmars> ericsnow, hmm. let me look a bit at NewAPIClient just to see if this mostly harmless. would i be likely to see any difference in tests passing in my dev env with vs without this patch?
[16:18] <ericsnow> cmars: in the interest of getting CI unblocked I figured I'd take the chance that the patch helped (since it doesn't hurt)
[16:18]  * cmars wishes CI could test PR branches for these kinds of experiments
[16:18] <cmars> but i don't want to be terribly difficult either
[16:19] <ericsnow> cmars: no worries
[16:19] <mgz_> cmars: it's doable
[16:19] <cmars> let me look over that api client just a few minutes & I'll let you know.
[16:19] <ericsnow> cmars: I definitely want an answer to the API client question either way :)
[16:19] <ericsnow> cmars: thanks
[16:20] <ericsnow> mgz_: that would be awesome
[16:20] <cmars> mgz_, thanks. is it difficult?
[16:20] <ericsnow> mgz_: from what perrito666 told me, it's a pain setting things up to run CI tests yourself
[16:26] <mgz_> ericsnow: it not super fun, the other option is we can send alternative branches through
[16:28] <cmars> mgz_, wasn't trying to be difficult, i was thinking of the github pull request jenkins plugin. i think it'd be able to pull something like this off (though maybe it is tricky to fit into the existing setup?)
[16:29] <mgz_> cmars: sure but if you're talking about actual ci runs rather than just the gating, that's too much to do on every push to a proposed branch
[16:29] <cmars> mgz_, ah, that's true, it'd have to be a targeted approach and maybe that's where it falls down
[16:30] <ericsnow> natefinch: on second thought, using member.Healthy in IsReady is strictly my fault
[16:31] <ericsnow> natefinch: I made the decision based on the doc comments in MemberStatus
[16:31] <ericsnow> natefinch: so I'm sure it could stand improvement :)
[16:33] <ericsnow> mgz_: for Python core development the CI is set up to allow running against a branch on a dev repo on request
[16:33] <ericsnow> mgz_: that works well
[16:35] <cmars> ericsnow, is the backups httpClient reusing the API websocket http connection to upload and download files?
[16:35] <ericsnow> cmars: nope
[16:35] <perrito666> mgz_: hit this before? http://pastebin.ubuntu.com/9384377/
[16:36] <cmars> ericsnow, where does it get its httpClient initialized?
[16:36] <mgz_> perrito666: got your ec2 creds soruced?
[16:36] <ericsnow> cmars: pretty sure its api/http.go
[16:36] <perrito666> mgz_: nope, I dont recall being required before, though it makes sense
[16:36] <cmars> ericsnow, ah, ok thanks
[16:37] <perrito666> cmars: ericsnow if you can find out why cient fails to being re-used you get each a beer on me next sprint
[16:37] <mgz_> perrito666: you can also have the ccred sin the environment.yaml name you pass
[16:37] <ericsnow> cmars: that code follows the precedent of charm download and tools upload
[16:37] <perrito666> mgz_: I am passing:  WORKSPACE=$(pwd) ./assess_recovery.py --ha-backup /home/hduran/gocode/bin  perritoec2
[16:38] <perrito666> perritoec2 being my ec2 env
[16:38] <mgz_> perrito666: so, if perritoec2 had the creds, I'd expect that excdeption not to happen
[16:38] <cmars> perrito666, do you see client re-use issues in other facades or just backups?
[16:38] <mgz_> I always just source my creds instead of putting them in the yaml
[16:38] <perrito666> mgz_: it has them, since it works :p
[16:39] <perrito666> cmars: I have not actually tried, but most likely only backups facade
[16:39] <perrito666> cmars: i first encountered this error while trying to retry actions waiting for upgrade to finish
[16:39] <ericsnow> mgz_, perrito666: ^^^ in the restore patch
[16:40] <ericsnow> (http://reviews.vapour.ws/r/298/)
[16:40] <ericsnow> perrito666: oh, right (pre-dating restore)
[16:40] <perrito666> ericsnow: ?
[16:41] <perrito666> ericsnow: I am trying your patch again now
[16:41] <ericsnow> perrito666: thanks
[16:48] <cmars> ericsnow, LGTM'd it. let's give it a shot
[16:48] <ericsnow> cmars: k
[16:49] <ericsnow> cmars: opening a bug on the api client re-use thing first
[16:50] <cmars> ericsnow, perfect
[16:50] <perrito666> ericsnow: we should write a facade call empirical test to make succesful and unsuccesful facade calls and see how the client behaves there
[16:56] <natefinch> ericsnow> natefinch: I made the decision based on the doc comments in MemberStatus
[16:56] <natefinch> ericsnow: and that's what you get for basing your implementation on my shoddy documentation ;)
[16:56] <ericsnow> natefinch:  :)
[16:57] <ericsnow> natefinch: and it was quite late and I was working on unblocking CI so perhaps I wasn't as rigorous for the sake of urgency :)
[17:05] <perrito666> ericsnow: well my test run failed for the second time without relation to your patch :p running a third one
[17:05] <ericsnow> perrito666: k :(
[17:07] <ericsnow> natefinch: want me to open a bug on IsReady?
[17:09] <natefinch> ericsnow: I don't know for sure that it needs a bug... it's entirely possible that Health is perfectly acceptable and does The Right Thing... I'm just wary of trusting vague docs :)
[17:10] <perrito666> :p MayBeReadyOrJustAlways0
[17:10] <ericsnow> natefinch: well, I'll open a bug just so we make sure we at least look into it :)
[17:10] <ericsnow> natefinch: we can easily close it
[17:10] <natefinch> ericsnow: good point
[17:18] <ericsnow> natefinch: https://bugs.launchpad.net/juju-core/+bug/1399730 (feel free to comment on the bug)
[17:18] <mup> Bug #1399730: replicaset.IsReady should check MemberStatus.State rather than Healthy. <tech-debt> <juju-core:New> <https://launchpad.net/bugs/1399730>
[17:19] <ericsnow> natefinch: in fact, feel free to pick up the bug ;)
[17:38] <rogpeppe> is there any way from the command line to get juju to print the environment UUID?
[17:41] <ericsnow> rogpeppe: the only one I know of is a little indirect: "juju backups create" :)
[17:41] <rogpeppe> ericsnow: i'm not sure i'm gonna use that one :)
[17:41] <ericsnow> rogpeppe: the env UUID in the backup metadata
[17:41] <ericsnow> rogpeppe: yeah, I figured :)
[17:41] <rogpeppe> i guess it might be good as part of juju status
[17:41] <ericsnow> rogpeppe: +1
[17:42] <rick_h_> rogpeppe: does the juju api endpoints command do it?
[17:42] <rogpeppe> rick_h_: i don't think so
[17:42] <rogpeppe> rick_h_: that just prints the api endpoint addresses
[17:42] <rick_h_> k
[17:43] <ericsnow> sinzui: both my and voidspace's fixes have landed so I'm hopeful for the HA backups CI test result
[17:43] <sinzui> rock
[17:44] <ericsnow> sinzui: keep in mind that our fixes don't really address the underlying concern we have with knowing for sure that HA is ready
[17:45] <sinzui> ericsnow, understood. I hope all our work improve the test's success.
[17:45] <ericsnow> sinzui: me too!
[17:45] <sinzui> ericsnow, CI found the new commits and has started the tests.
[17:45] <ericsnow> sinzui: cool
[17:50] <ericsnow> alexisb: we're still on in 10 minutes, no?
[17:50] <alexisb> ericsnow, yep
[17:50] <ericsnow> alexisb: k
[17:57] <perrito666> ericsnow: pre-good news, the test passes
[17:57] <ericsnow> perrito666: cool
[17:57] <ericsnow> perrito666: and it fails without the patch?
[18:00] <perrito666> ericsnow: I did not try, but I assumed so
[18:00] <perrito666> I am runing the same code as CI
[18:00] <ericsnow> perrito666: cool
[18:00] <ericsnow> perrito666: CI should be running the test in a little while
[18:00] <perrito666> ericsnow: lets hope with the same results
[18:15] <cmars> ericsnow, just LGTM'd 549
[18:30] <ericsnow> cmars: thanks!
[18:30] <alexisb> katco, mind if I take a few minutes to chat with natefinch before we meet?
[18:30] <katco> alexisb: not at all!
[18:30] <LinStatSDR> Hello All.
[18:30] <katco> alexisb: ty for asking :)
[18:32] <ericsnow> cmars: would you mind reviewing a couple more for me (http://reviews.vapour.ws/r/591/ and http://reviews.vapour.ws/r/578/)?
[18:32] <cmars> ericsnow, already on 591
[18:32] <ericsnow> cmars: http://reviews.vapour.ws/r/557/ too if you feel up to it :)
[18:32] <ericsnow> cmars: awesome
[18:37] <ericsnow> sinzui: how soon do you think we'll know on the CI results for functional-ha-backup-restore?
[18:38] <sinzui> ericsnow, about an hour. We are in the dull period where CI is publishing streams for the cloud-based tests
[18:38] <ericsnow> sinzui: k
[18:38] <voidspace> g'night all
[18:38] <voidspace> have a happy weekend
[18:39] <ericsnow> voidspace: thanks for all your help
[18:39] <voidspace> EOW
[18:39] <voidspace> ericsnow: see you on monday
[18:43] <ericsnow> sinzui: FWIW, perrito666 verified that with my patch the CI test passed on his EC2 instance
[18:44] <sinzui> fab
[18:48] <alexisb> ok katco ready and joing the hangout
[19:12] <ericsnow> cmars: thanks for those reviews
[19:23] <ericsnow> sinzui: looks like the test made it past the spot where it's been failing :)
[19:25] <cmars> ericsnow, fingers crossed :)
[19:31] <ericsnow> sinzui: so the test passed and I'm confident that it will pass in re-test
[19:32] <ericsnow> sinzui: should that blocker bug be marked as fixed-released or should the CI tag be dropped?
[19:33] <sinzui> ericsnow, I am marking it as fix released
[19:33] <ericsnow> sinzui: okay, cool
[19:33] <ericsnow> sinzui: thanks for all the help
[19:33] <ericsnow> sinzui: I think that sleep really helped
[19:56] <katco> alexisb: http://www.pvponline.com/comic/2007/12/06/kringus-risen-part-4
[19:56] <alexisb> lol nice!
[19:56] <katco> alexisb: we call our cat kringus because he likes to get in the tree :)
[20:19] <ericsnow> cmars: I'm guessing you got those errors from a header file in the mongo source...
[20:20] <ericsnow> cmars: are they exposed in mgo at all?
[20:22] <ericsnow> cmars: or are those from errno?
[20:39] <cmars> ericsnow, I grepped 'connection' out of the go stdlib :)
[20:39] <cmars> just for a sample
[20:39] <cmars> ericsnow, mgo doesn't have anything specific to connection errors, other than when trying to dial
[20:41] <ericsnow> cmars: okay, I'll go with the ones you listed (see http://golang.org/pkg/syscall/ and http://golang.org/src/pkg/syscall/zerrors_linux_amd64.go)
[20:49] <natefinch> ericsnow: beware using anything from syscall.  It should set off warning bells in your head if you ever import it.  It is explicitly not cross-platform compatible.  Sometimes the methods & types will be the same across platforms, and sometimes they won't be.  We need to at least make sure that everything compiles on all our platforms (by which of course I mean Windows)
[20:51] <ericsnow> natefinch: good point
[20:52] <ericsnow> natefinch: in this case the errnos are set up for most (all?) platforms go supports, including windows
[20:53] <ericsnow> natefinch: the errno constants are all I need
[20:53] <natefinch> ericsnow: ok, just wanted to make sure.  Syscall always gives me the heebie jeebies :)
[20:53] <ericsnow> natefinch: hey, good thinking
[21:07] <ericsnow> cmars: I've updated http://reviews.vapour.ws/r/591/ with those errnos
[21:08] <ericsnow> cmars: do you think you'll have time to look at http://reviews.vapour.ws/r/557/?
[21:08] <ericsnow> cmars: it's a large patch, but most of it is mechanical
[21:09] <ericsnow> cmars: I tried to break it down helpfully in the description
[21:13] <cmars> ericsnow, thanks. yep, i'll take at 557 next
[21:14] <ericsnow> cmars: awesome! thanks for grinding through these :)
[21:28] <cmars> ericsnow, i don't think i'm qualified to approve 557, sorry
[21:28] <ericsnow> cmars: no worries :)
[21:28] <ericsnow> cmars: thanks for taking a look
[21:30] <ericsnow> cmars: I'll see if I can talk axw into it on Monday :)
[21:44] <natefinch> ericsnow: I wonder if we shouldn't just put availabilityZone into hardware characteristics
[21:46] <ericsnow> natefinch: I considered that but from my cursory introduction to that corner of juju it didn't seem to fit quite right there
[21:46] <ericsnow> natefinch: what would be the motivation?
[21:46] <ericsnow> natefinch: other than reducing the churn in that patch :)
[21:48] <natefinch> ericsnow: reducing churn is a noble goal.  But it also just seems like something you might want to pass around with hardware characteristics.
[21:50] <ericsnow> natefinch: I suppose, but it still doesn't seem like a good fit IMHO
[21:51] <natefinch> ericsnow: at least as good a fit as "tags".  AZ can't change for the hardware anymore than the architecture can.  Where the hardware is seems like a valid piece of info about the hardware.
[21:51] <ericsnow> natefinch: FWIW, on IRC axw gave me a non-binding LGTM on the approach after a cursory review
[21:51] <natefinch> lol
[21:51] <ericsnow> natefinch: fair enough
[21:52] <natefinch> ericsnow: I think it's worth bringing it up to others first... I don't want to muck up other parts of the code if changing HW chars has other specific meaning, but from a pure code point of view, it's a lot better than adding yet another return value to all these functions.
[21:53] <ericsnow> natefinch: sounds good
[21:54] <ericsnow> natefinch: at once point I believe I had the AZ as stored on the Instance (and expected with an AvailabilityZone method)
[21:55] <ericsnow> s/expected/exported
[21:57] <natefinch> ericsnow: I thought of that too... I think HWC is slightly better.. but not 100%
[21:57] <ericsnow> natefinch: agreed; instance.Instance is more about stuff that I expect can change
[23:10] <cmars> i'm done. have a good weekend juju people


[12:59] <pavlushka> u-la-la!
[12:59] <u-la-la> pavlushka!
[14:04] <Brainstorm> Updates for Bangladesh: +54 cases, +4738 tests since a day ago


[00:00] <tsimonq2> Woaaaaaaaaaaaaaah. Cool.
[00:00] <Eickmeyer> (no relation)
[00:00] <kc2bez> https://github.com/lxqt/lxqt/issues/10#issuecomment-1759317897
[00:00] -ubottu:#lubuntu-devel- Issue 10 in lxqt/lxqt "Wayland support" [Open]
[00:00] <Eickmeyer> Isn't LWQt the Wayland version?
[00:00] <tsimonq2> I'm NACK on landing it before the LTS. After the LTS, go full ham.
[00:00] <tsimonq2> Eickmeyer: potato potato :)
[00:01] <Eickmeyer> 🤣
[00:01] <kc2bez> I don't think Tsujan plans to proceed with renaming things.
[00:02] <tsimonq2> I mean, we certainly could. I just don't want the bug reports :)
[00:03] <tsimonq2> "OMGWTFBBQ!!!1111111 my buggy obsolete Wayland session released as a tech preview on the LTS that hasn't been updated in 2 years is broken!!!!!" I can see it now
[00:03] <tsimonq2> I'd be all-for a PPA tho
[00:03] <kc2bez> 🐛🐛🐛🐛
[00:03] <tsimonq2> @arraybolt3: Whatever works, has good theming support, and doesn't regress user functionality, I'm all for :)
[00:04] <kc2bez> PPA seems reasonable to me.
[00:05] <kc2bez> labwc carries on the OpenBox config model so it might not be too bad to port.
[00:05] <kc2bez> We really need the panel to work though. That seems like the biggest challenge right now.
[00:06] <kc2bez> The time is closing in
[00:09] <tsimonq2> I've heard (privately, so don't quote me) that Red Hat has been looking to deprecate virt-manager in favor of cockpit, but hasn't pulled the plug yet for whatever reason.
[00:09] <tsimonq2> So, if you have an official announcement, let's get a ref to that before going too ham :)
[00:09] <Eickmeyer> tsimonq2: pardon the iterruption, but did you email that patch?
[00:09] <tsimonq2> Eickmeyer: Working on testing it, also no worries, you don't need to apologize :)
[00:10] <Eickmeyer> Ok, cool.
[00:10]  * Eickmeyer will no longer apologize for anything. 😁
[00:10]  * lubot [matrix] <arraybolt3> tosses Eickmeyer into a nearby pit of golden retriever puppies
[00:10] <tsimonq2> Eickmeyer: How the heck do I start this thing again?
[00:10] <wxl> what about apologizing in the first place? shouldn't you be sorry for that?
[00:11] <tsimonq2> wxl: ^^^ XDDDDD
[00:11] <tsimonq2> Hey wxl!
[00:11] <Eickmeyer> @arraybolt3: My son would call that puppy paradise.
[00:11] <wxl> oh hai
[00:11] <kc2bez> wxl !!!!
[00:11] <Eickmeyer> tsimonq2: If it's installed, it starts automatically with Plasma.
[00:11] <wxl> the gang's all here apparently
[00:11] <kc2bez> Release day fun
[00:11] <tsimonq2> wxl: Still coming to Riga?
[00:11] <arraybolt3_wc> o/
[00:11] <Eickmeyer> wxl: Sorry for being sorry? Never.
[00:12] <Eickmeyer> Oh, NOW he gets out the IRC client.
[00:12] <tsimonq2> XD
[00:12] <arraybolt3_wc> lol
[00:12] <Eickmeyer> HAHAHAHAHA
[00:12] <Eickmeyer> Ships passing.
[00:12] <wxl> tsimonq2: hoping to. still working on it. :.
[00:12] <tsimonq2> Eickmeyer: Restarting my session does nothing :P what's your test process?
[00:12] <tsimonq2> wxl: Do you have flights booked?
[00:13] <wxl> ummmmmmm
[00:13] <arraybolt3_wc> tsimonq2, Eickmeyer: What's being tested?
[00:13] <arraybolt3_wc> I missed the whole start of this convo
[00:13] <Eickmeyer> arraybolt3_wc: plasma-distro-release-notifier
[00:13] <arraybolt3_wc> ohhhhh, nice
[00:13] <tsimonq2> wxl: you better get to figuring that out XDD
[00:13] <Eickmeyer> tsimonq2: You actually have to change the dates in the system.
[00:14] <wxl> tsimonq2: i know. it's been kind of hectic here in rl.
[00:15]  * Eickmeyer ponders if it's in the spirit of the CoC to drive 6 hours round-trip to kidnap wxl...
[00:15] <tsimonq2> Eickmeyer: Right but to what :) does it only notify so far out from EOL? I enabled Prompt=regular so it'll pick up Lunar/Mantic.
[00:15] <tsimonq2> wxl: Happens. Keep me posted :)
[00:16] <tsimonq2> Eickmeyer: something something "leaders sometimes take disagreeable action to further the project" XD
[00:16] <Eickmeyer> tsimonq2: Exactly.
[00:16]  * arraybolt3_wc quietly dials 911 to report Eickmeyer
[00:17] <Eickmeyer> tsimonq2: If you're on Lunar put it at sometime mid-January, and it'll start notifying of EOL.
[00:17] <guiverc> tsimonq2, lunar/mantic isn't open; https://changelogs.ubuntu.com/meta-release doesn't yet mention 23.10/mantic as release so far is ISO for new installs. not upgrades
[00:17] <tsimonq2> Eickmeyer: ack :) note my opinion that it's stupid to do that these days :P
[00:17] <tsimonq2> arraybolt3_wc: Snitches get stitches XD
[00:17] <arraybolt3_wc> to notify of EOL?
[00:17] <tsimonq2> guiverc: Thanks for the info :)
[00:18] <arraybolt3_wc> I've seen a lot of people asking "why won't my machine upgrade?" and it's because they're unintentionally using an EOL release.
[00:18] <tsimonq2> arraybolt3_wc: Nah, to wait until a month before EOL to even notify
[00:18] <arraybolt3_wc> oh
[00:18]  * kc2bez cuts arraybolt3_wc 's phone line
[00:18] <Eickmeyer> arraybolt3_wc: Yep. That's what we're testing, a new way. Right now it just pulls from the git branch to get the date.
[00:18] <arraybolt3_wc> * has quit (K-Lined)
[00:18] <Eickmeyer> 🤣
[00:18] <kc2bez> Oops
[00:18] <arraybolt3_wc> s/K-Lined/Phone-Lined/
[00:19] <Eickmeyer> ^
[00:20] <kc2bez> tsimonq2: shouldn't that be Prompt=normal ?
[00:21] <tsimonq2> kc2bez: yeah that :)
[00:21] <kc2bez> Gotcha
[00:21] <Eickmeyer> arraybolt3_wc: plasma-distro-release-notifier literally pulls this file to know the EOL dates: https://git.launchpad.net/plasma-distro-release-notifier/plain/eol.json?h=eol
[00:21] <tsimonq2> Eickmeyer: Still no popup, where are the logs?
[00:21] <Eickmeyer> We're trying to get it to use distro-info-data instead.
[00:22] <Eickmeyer> tsimonq2: That I couldn't tell you. It only ever used online sources, even in the upstream neon version.
[00:23] <Eickmeyer> tsimonq2: Did you install it to a virtual machine or are you just running the live session?
[00:23] <tsimonq2> OH. Live session. That makes sense.
[00:23] <Eickmeyer> Yep. 💀
[00:23] <tsimonq2> gaaaaaaaaaaaaaaaaaaaaawd I forgot how slow Ubiquity was
[00:24] <Eickmeyer> Kubunu or Ubuntu Studio?
[00:24] <tsimonq2> Kubuntu, that's the ISO I had locally
[00:24] <tsimonq2> Actually, jammy-daily if that makes any difference.
[00:25] <Eickmeyer> Ah. Yeah, the Qt version is full of so much technical debt it's not even funny. Nobody has touched that code in more than half a decade.
[00:25] <Eickmeyer> Bugs get raised and tagged with "rls-xx-incoming" and Foundations says, "yeah, no."
[00:26] <tsimonq2> With Cala I can literally just spam the Next button until the partition page and it's like... less than half a second
[00:26] <Eickmeyer> I do that and Cala crashes for some reason.
[00:27] <Eickmeyer> I've also had people yell at me about the first page taking forever to come up.
[00:27] <kc2bez> It checks all the modules in the background
[00:27] <Eickmeyer> 90% of the time, in that case, they didn't verify their .iso image.
[00:28] <tsimonq2> Eickmeyer: They don't maintain Qt; *Flutter* is "Flutter is a truly cross-platform tool and is open source. If the Linux ecosystem at large picks this up there is a tremendous opportunity for massive ecosystem expansion"
[00:28] <tsimonq2> They believe in what I would consider to be, almost, its direct competitor
[00:28] <tsimonq2> *shrug* this too shall pass
[00:28] <kc2bez> 🤔
[00:29] <tsimonq2> https://ubuntu.com/blog/flutter-and-ubuntu-so-far
[00:29] <arraybolt3_wc> Qt actually works :-/
[00:29] <arraybolt3_wc> Last I looked at Flutter and Dart I was like "...yeah no"
[00:30] <tsimonq2> I talked with a freelance buddy of mine, he told me that it's amazing for mobile apps, a little more janky on desktop. Take that with a grain of salt.
[00:33] <Eickmeyer> The flutter installer isn't an installer. Subiquity is the installer. The flutter installer is merely a gui wrapper telling subiquity what to do.
[00:34] <Eickmeyer> The desktop team is making it easy for flavors to maintain: we just pick the bits we want on top of it and the dependencies are handled for us.
[00:34] <tsimonq2> I mean, technically, the Qt frontend isn't an installer either.
[00:34] <tsimonq2> Ubiquity uses random debian-installer components, actually :P
[00:35] <Eickmeyer> If you're talking about ubiquity, sure, but the technical debt there is enormous.
[00:35] <tsimonq2> So we start over :)
[00:35] <Eickmeyer> Not only would one have to maintain the GUI, but the underlying components too.
[00:36] <Eickmeyer> Because Canonical is sunsetting ubiquity. They've already said that by 24.04's release, goodbye Ubiquity. They don't want to maintain it for another LTS.
[00:37] <Eickmeyer> It'll be pushed to universe. If flavors want it, they can have it, but that means maintaining it too.
[00:37] <tsimonq2> Looks like it's my turn to drive. Hi from west Nebraska.
[00:37] <tsimonq2> Eickmeyer: Want my untested patch now?
[00:37] <Eickmeyer> tsimonq2: heh, I'll look at it.
[00:37] <tsimonq2> cool
[00:37] <kc2bez> Something web based like Redhat 🚪🏃
[00:38] <tsimonq2> Eickmeyer: Confirm you got it?
[00:38] <Eickmeyer> kc2bez: HA! You want to know the complaints I've seen with Anaconda's hub-and-spoke approach?
[00:38] <tsimonq2> kc2bez: hah
[00:38] <kc2bez> XD
[00:38] <Eickmeyer> tsimonq2: Nope.
[00:39] <tsimonq2> Telegram it is
[00:39] <tsimonq2> Licensed the same as the program / just add an entry at the top of the file for me if it goes upstream :)
[00:40] <tsimonq2> (Which it should, honestly)
[00:41] <Eickmeyer> They won't, they have different EOL dates.
[00:41] <Eickmeyer> It's Neon.
[00:43] <Eickmeyer> I'll take this patch (btw, ew 🤮 no comments in code?) and push it to a PPA and see what happens when installed in a VM.
[00:43] <Eickmeyer> tsimonq2: ^
[00:45] <Eickmeyer> tsimonq2: Just got your email. 💀 😆
[00:46] <Eickmeyer> I've never seen electrons move so slow.
 Eickmeyer: I could 4 comments hah
 *count
 Let me know how it tests
 I mean, it compiles, so it can't be that bad XD
 Eickmeyer: Also, the QNetworkReply header can be removed if it's not used anywhere else in the code
[00:55] <Eickmeyer> Probably. I'll dig.
 Anyway, even if it doesn't work, that gives you a start :) remember to add the hard dep on distro-info-data
[00:56] <Eickmeyer> Of course.
 Also, I hate the explicit declarations of QChar and QString in function parameters, and in my isolated testing script it didn't require that. If you find a way to remove those and clean up the code, even if it's just standardizing those types in some way, go for it
 @tsimonq2 https://launchpad.net/~eeickmeyer/+archive/ubuntu/pdrn (read the description)
 @tsimonq2 Did you apply the other patches prior to making this patch?
 This was the first item in the series file (re @Eickmeyer: @tsimonq2 Did you apply the other patches prior to making this patch?)
 I replaced your existing number one patch with this patch
 I apologize for any confusion
 @tsimonq2 maybe what, if anything, we publish for minimums should be suggestions or recommendations rather than actual technical requirements. 🤔
 It is something that gets asked somewhat frequently.
 Hmm... does any other flavor publish such recommendations?
 I wouldn't be opposed, but we *are* the lightest flavor
 I will do some research and give a better proposal. I feel like I have seen others with minimums posted but maybe I am mistaken.
 We are lighter than the others for sure.
[17:22] <tsimonq2> Thanks Dan :)
 Sure thing
[17:22] <tsimonq2> On *Monday*, when everyone is back from their mandatory vacation, I could use some help double checking testing results for bug 2039093
[17:22] -ubottu:#lubuntu-devel- Bug 2039093 in lxqt-sudo (Ubuntu Mantic) "[SRU] Add -E support to lxqt-sudo" [Medium, Fix Committed] https://launchpad.net/bugs/2039093
[17:26] <Eickmeyer> tsimonq2: And of course we can coordinate here. *bonks simon*
[17:28] -queuebot:#lubuntu-devel- Unapproved: rejected lubuntu-update-notifier [source] (mantic-proposed) [0.6.1]
[17:29] <Eickmeyer> tsimonq2: Looks like you have more pressing matters. ^
[17:30] -queuebot:#lubuntu-devel- Unapproved: rejected lubuntu-update-notifier [source] (lunar-proposed) [0.6.0~23.04.1]
 That moment when you've been using your desktop machine as your main machine for the past 18 months and you realize you've never had to run pristine-tar on it. 💀
[18:05] <arraybolt3_wc> A day spent away from git-buildpackage is a good day in at least one way!
 did y'all see this?  https://discourse.ubuntu.com/t/announcement-ubuntu-desktop-23-10-release-image-is-being-updated-to-resolve-a-malicious-translation-incident/39365?_ga=2.105716099.1838008497.1697195387-1302408282.1697195387
 and were we affected
 No, Lubuntu is *not* affected. It only affects those that are using the new flutter/subiquity installer.
 nice
 just making sure
 So, only Ubuntu Desktop and Ubuntu Budgie.
[18:07] <arraybolt3_wc> whoa what?
 i'm playing "chase the backlogs" today
[18:07] <arraybolt3_wc> oh grief
 thanks Erich
 BO
 er... NP
 arraybolt3: yup
 *fingers are on the right characters now*
 that was my reaction too.
[18:09] <arraybolt3_wc> For a second I thought Canonical had fallen prey to a cyberattack.
[18:09] <arraybolt3_wc> That's still sad and a mess, but at least it's not as bad as what it looked like at first.
[18:09] <Eickmeyer> Nah. It was just a bad actor on the translations team for ubuntu-desktop-installer on github.
[18:10] <Eickmeyer> They've since been banned.
[18:10] <arraybolt3_wc> :+1:
[18:11] <arraybolt3_wc> that moment you realize you're using an alternate nick since you have a different IRC client using your main nick and that you've not been logged in this whole time
 sounds like someone needs kicked from the project.  *whistles nonchalantly for reasons*
[18:12] <arraybolt3_wc> *watches teward001 collapse into his own event horizon*
 and not arraybolt for irc isues
 but the malicious one.
[18:12] <arraybolt3_wc> oh
[18:12] <arraybolt3_wc> I thought it was a joke
 nope
 cell phone lag is bad today mmhmm
[18:13] <arraybolt3_wc> I assume whoever it was already has been kicked from everything Canonical-related.
[18:13] <arraybolt3_wc> ah
 The new Budgie image is up for testing
[18:13] <Eickmeyer> I mean, considering they got banned, and they were a volunteer translator, I would assumed they got kicked from the project.
 Forwarded from fossfreedom: Everyone ... the fixed 23.10 ubuntu budgie iso is now up. So if you have some time please do help to verify all is OK. http://iso.qa.ubuntu.com/qatracker/milestones/449/builds/288483/testcases  TIA
[18:13] <arraybolt3_wc> teward001: Well I see your problem. You're using Telegram. Just use an Android IRC Client.
[18:13] <arraybolt3_wc> I'll test that.
[18:14] <Eickmeyer> I would but I have other fishes to fry, aka tsimonq2's sus plasma-distro-release-notifier patch.
[18:14] <Eickmeyer> It's a smelly fish, too.
[18:15] <arraybolt3_wc> tbf I don't speak Ukrainian so maybe I'm not the best one to do the testing...
[18:15] <Eickmeyer> arraybolt3_wc: Google Goggles.
[18:15] <arraybolt3_wc> and I don't know how to type it either so Google Translate will be difficult to use
[18:15] <Eickmeyer> Oh, no phone.
 Probably doesn't hurt to do some smoke testing in the languages you know.
[18:16] <arraybolt3_wc> That's a set of exactly one :P
[18:16] <Eickmeyer> Smoke testing is always good.
[18:16] <arraybolt3_wc> (Tried to learn Spanish, failed, tried to learn Italian, failed, tried to learn Greek, failed, tried to learn Hebrew, I didn't fail quite as badly there but still didn't pull it off)
[18:16] <Eickmeyer> And I am always up for limited Spanish and German testing when I'm feeling adventurous.
 Hey, you have me bested. I struggle with this one sometimes.
[18:16] <arraybolt3_wc> Tried to learn C# and that went smoothly :P
[18:17] <Eickmeyer> I mean... I doubt C# is a selectable language in the installer.  I don't have a phone, but I have a Chromebook tablet with Google Play support and a camera!
[18:20] <arraybolt3_wc> Google Goggles is an option!@
[18:20] <arraybolt3_wc> s/@//
[18:20] <Eickmeyer> \o/
[18:20]  * arraybolt3_wc installs the app
[18:20]  * Eickmeyer needs to get that for the Frankfurt Airport just in case he doesn't understand something
[18:21] <arraybolt3_wc> Here's hoping Google TrytoTranslate can handle Ukranian with its camera feature
 https://github.com/calamares/calamares/issues/2214
[18:26] -ubottu:#lubuntu-devel- Issue 2214 in calamares/calamares "ProcessJob and contextualprocess operate differently" [Open]
 What's that? 💀 (re @Eickmeyer: That moment when you've been using your desktop machine as your main machine for the past 18 months and you realize you've never had to run pristine-tar on it. 💀)
 @Eickmeyer At some point, I'll take a look at the logs for this puppy to try and find the segfault :) for now, yeah, I'll attend to this
 I'm running on very little sleep and we're almost to the Grand Canyon. Hopefully we can check in right at 1 so I can crash/burn
[18:28] <arraybolt3_wc> sigh, it looks like Google's decision to move the Android runtime from a container to a VM may have killed camera support for Android apps.
[18:28] <arraybolt3_wc> Translate is just telling me "Lens not available" when I try to switch to Camera mode.
[18:28] <arraybolt3_wc> oh, maybe I'm just missing a component
 It's segfaulting? Damn. (re @tsimonq2: @Eickmeyer At some point, I'll take a look at the logs for this puppy to try and find the segfault :) for now, yeah, I'll attend to this)
[18:29] <arraybolt3_wc> Good grief. Missing software dependencies on Android of all things.
[18:29] <arraybolt3_wc> You have to install Google Lens to get Google Translate's camera feature to work.
 Well, I found another problem. I forgot to update some strings in some patches, so there's another reason to SRU altogether.
[18:29] <arraybolt3_wc> I thought Android was like the one Linux distro that *didn't* have dependency problems.
 s/some patches/a patch/
 @Eickmeyer Possibly, don't know yet, can't find the logs or enablement settings
[18:33] <arraybolt3_wc> And Google Lens in turn has a software dependency on an app just called "Google" which isn't Chromebook-compatible. So now I'm installing a *third* app that might give me the functionality I need :P
 There's probably KDE docs but I'm honestly a bit tired to go through that :)
 arraybolt3_wc: Ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooof.
[18:33] <arraybolt3_wc> I'm starting to lose hope that this is possible.
 Understandable. Had no idea you were headed to Arizona. (re @tsimonq2: There's probably KDE docs but I'm honestly a bit tired to go through that :))
[18:34] <arraybolt3_wc> But anyway, worst fear confirmed, Google Play is the Android equivalent of dpkg (not apt).
[18:35] <arraybolt3_wc> there, looks like Google Go is going to work :D
[18:36] <arraybolt3_wc> yep, works
[18:37] <Eickmeyer> \o/
 https://matterbridge.lubuntu.me/f1c9e3c1/file_9974.jpg
[19:11] <arraybolt3_wc> tsimonq2: Wow, pretty!
[19:11] <arraybolt3_wc> That's where you're at now?
 @tsimonq2 that looks nice
[20:09] <arraybolt3_wc> Sigh, serious problems with the Budgie ISO.
[20:09] <arraybolt3_wc> No installer pops up upon bootup.
[20:09] <arraybolt3_wc> And the installer app in the menu is "Install RELEASE"
[20:09] <arraybolt3_wc> Not "Install Ubuntu Budgie", or "Install Ubuntu 23.10", or "Install Ubuntu Mantic", or anything.
[20:21] <arraybolt3_wc> oof, it's also very difficult to finish the last screen of the installer when your keyboard is stuck in Ukranian...
[20:21] <arraybolt3_wc> you can't use a non-ASCII computer name or username it appears, and typing ASCII text is a bit tricky like this
[20:24] <arraybolt3_wc> sheesh, took me that long to find the keyboard layout settings
[20:24] <arraybolt3_wc> So... Subiquity is not condusive to installing in languages that aren't English-like. Now we know.
[20:24] <arraybolt3_wc> Also the Ubuntu Budgie slideshow is simply absent.
[20:25] <arraybolt3_wc> Just a plain white screen.
[20:25] <arraybolt3_wc> I'll do another smoke test in English in the mean time, but this is broken.
 Make sure to log your tests arraybolt3_wc
[20:29] <arraybolt3_wc> Will do
[20:30] <arraybolt3_wc> GNOME Boxes glitched and turned my UEFI VM into a BIOS VM upon reboot (?!) so I still haven't actually gotten the new install to boot :P
 ran 2 tests on budgie 1 barebone and 1 VM no errors.. (re @lubuntu_bot: (irc) <arraybolt3_wc> GNOME Boxes glitched and turned my UEFI VM into a BIOS VM upon reboot (?!) so I still haven't actually gotten the new install to boot :P)
[20:33] <arraybolt3_wc> Leokolb: Did the slideshow appear as a plain white background for you?
[20:34] <arraybolt3_wc> If not, it's probably an issue unique to installing in Ukranian.
 no - there is discussion on Ubuntu Testers channel
 Been there. It's pretty great. (re @tsimonq2: )
 In fact, grand you might say.
 arraybolt3_wc: Are you planning on coming back full swing to development soon or are you going the gradual route?
[21:50] <arraybolt3_wc> tsimonq2: That depends on how things go, but if things go according to plan, full-swing.
[21:51] <arraybolt3_wc> I probably should get hooked back into the IRC channels and mailing lists.
[21:51] <arraybolt3_wc> (I'm in some of them but not many.)
 @teward001 @kc2bez wxl arraybolt3wc: I suggest we all meet sometime in the next week to carefully plan what gets greenlit for LTS, what doesn't, what we need to finish before then, and who does it. Pure development/technical meeting to hash out technical stuff, plus I want to get everyone up to speed with Recent Happenings
 Let me suggest... hear me out... Thursday at 2100 UTC
 XD
[21:53] <wxl> unheard of
 Sounds like a decent !standup.
[21:53] <arraybolt3> Sounds like it might work.
 I love how we did two different Doodle polls like a year apart and both times that won
[21:53] <arraybolt3> I'll definitely need to be brought up-to-speed since I missed ~everything that happened in the last six months.
[21:54] <arraybolt3> Plus this is going to be my first LTS cycle
[21:57] <arraybolt3> One thing I would *like* if we could make happen (no clue if it's possible) is to make the unofficial backports-enabled ISO. Lots of people liked Backports, and it would provide a sort-of KDE Neon experience with Lubuntu (rolling LXQt updates, stable for everything else).
[21:57] <arraybolt3> We discussed that during Kinetic and almost did it, but then didn't.
 @tsimonq2 So... there's no way to test it using Plasma's Date/time setting. There's an open bug: https://bugs.kde.org/show_bug.cgi?id=447364
[21:59] -ubottu:#lubuntu-devel- KDE bug 447364 in systemsettings "Unable to set current time manually" [Normal, Reopened]
 That's ok. timedatectl is a thing.
 @tsimonq2 This I will say though: it might be failing because Mantic isn't opened for upgrades yet, so i.e. Lunar won't report EOL.
 (no upgrade path)
 With that in mind, retest on Monday when it *might* open for upgrades.
 This is true (re @Eickmeyer: That's ok. timedatectl is a thing.)
 I've been testing on Jammy, with an upgrade to Lunar (re @Eickmeyer: @tsimonq2 This I will say though: it might be failing because Mantic isn't opened for upgrades yet, so i.e. Lunar won't report EOL.)
 so it does show as upgradable
 Ahhhhh. Didn't think to try that.
 I set the time to 2024-01-24T00:00:00 and that didn't work
 Does it have to be *after* the EOL?
 It should start warning before the EOL.
 Oh. Wait a minute...
 Jammy doesn't EOL then, Lunar does
 🤦♂
 /me tired
 is ok
 Also, we're on the same TZ for the next day or two :)
 Until after Riga.
 Oh wait... until you leave.
 /me is also tired
 Lmfao
 I'll be more tired in Riga ;)
 Jet lag is real.
 simon: time works for me, send an invite if we all are good for it


[04:52] -ubottu:#ubuntu-news- ::planet:: Ubuntu Blog: The kernel of open source: community @ https://ubuntu.com//blog/the-kernel-of-open-source-community