[00:33] <rick_h_> heh, busy day when now is the first time I've loaded up the dell order status page fo the first time today
[00:33] <rick_h_> and still building :)
[09:08] <rbasak> bac: thank you for doing the SRU justifications for me. I'm working on the Trusty SRUs now.
[11:13] <rick_h_> morning
[11:13] <rick_h_> rbasak: awesome thanks
[11:30] <bac> morning rick_h_
[11:31] <rick_h_> bac: morning
[11:31] <rick_h_> bac: talked with wallyworld last night. They're building a CI setup for several of the small libraries around juju
[11:31] <rick_h_> bac: we talked about having the charmstore CI be located there and in the same place as the other libraries used
[11:31] <bac> rick_h_: progress this morning! axw discovered i was encountering two bugs with juju.  one just committed to trunk and the other on the critical list.
[11:31] <bac> the latter has a work-around
[11:31] <rick_h_> bac: and I think everyone is on board with that.
[11:31] <bac> rick_h_: cool
[11:31] <rick_h_> bac: oh, very cool
[11:32] <bac> rick_h_: the other bug i think only affected us east.  everyone says to use us west
[11:32] <rick_h_> bac: so I'm tempted to say our goal is to work with them to get things up for now.
[11:32] <rick_h_> bac: ugh, sounds like nutty bugs
[11:33] <bac> rick_h_: to complete my day of frustation i found my car battery dead.  and when i used my neighbor's car to jump start it, his car died and wouldn't restart.  should've stayed in bed.
[11:33] <rick_h_> ouch, taking down the neighbors with you? That's not good.
[11:33] <bac> rick_h_: is wallyworld working with anyone who overlaps with us?
[11:34] <rick_h_> bac: martin I believe is running the show from his team
[11:34] <bac> which martin?
[11:34] <bac> nicks, man. proper names due me no good.
[11:34] <rick_h_> bac: packman? /me goes to check spelling
[11:34] <bac> mgz.  cool.
[11:34] <rick_h_> I'm not sure on his nick :P
[11:34] <bac> and best, he's in a proper time zone
[11:35] <rick_h_> there you go, mgz :)
[11:35] <rick_h_> so he's doing the actual CI setup and overlaps with us.
[11:35] <bac> ok, i'll ping him when i come back.
[11:35]  * bac bbiab
[11:35] <rick_h_> have fun
[11:58] <bac> rick_h_: so the goal is to just move charmstore over there, not the others?
[11:59] <bac> hi rbasak, i've put in SRU info on the three bugs for quickstart.  can you have a look and tell me if i need to make changes?
[12:03] <rick_h_> bac: yea, the gui and private tools I think we'll keep with the current setup and be aware that we should rebuild CI at some point due to juju issues
[12:03] <rick_h_> bac: but core folks will also work on the charmstore and it makes sense to have that together with the other juju tools
[12:04] <rick_h_> bac: and rbasak is looking at the SRU, he commented before you joined irc this morning so rocking on woo!
[12:04] <bac> rick_h_: ever see this on azure?
[12:04] <bac> juju-quickstart: error: bad API response: cannot assign unit "juju-gui/0" to machine 0: unit placement is not supported with availability-sets-enabled
[12:12] <rick_h_> bac: oh hmm no. But we got CI up before the availability set support landed in juju
[12:12] <rick_h_> that's going to be interesting
[12:12] <bac> rick_h_: yeah, the old instances don't have a.s.  my new one does and it is pissy
[12:13] <rick_h_> bac: yea, I wonder how that effects machine view
[12:13] <bac> rick_h_: i'm going to tear it down and file a bug against quickstart.  we can reassign later if needed
[12:13] <rick_h_> that sounds a LOT like we need to support doing something there in order for MV to work in the GUI
[12:13] <bac> i have done some mighty fine juju QA this week.  :(
[12:15] <rick_h_> bac: https://github.com/juju/docs/issues/85 says there's some docs on the feature in juju-core/doc/azure-provider.txt
[12:16] <bac> cool
[12:17] <rick_h_> bac: yea, availability-sets-enabled is a new attribute at bootstrap time and kills manual placement
[12:17] <rick_h_> wtf
[12:27] <bac> hey, i found a work-around to a juju annoyance:
[12:27] <bac> juju destroy-environment `juju switch`
[12:28] <bac> no more juju nanny state
[12:33]  * rick_h_ relocates to the coffee shop to get over the shock of the news
[12:36] <rbasak> rick_h_, bac: I made a couple of very minor changes to meet SRU requirements for the "Support trusty environments" backport: http://paste.ubuntu.com/7710956/
[12:36] <rbasak> Just FYI. Tests still pass, and I'm happy that this should be fine.
[12:37] <rbasak> I think you've improved processes quite a bit since that commit, so this should be easier next time - just one issue per commit, please :)
[12:38] <bac> rbasak: thank you
[12:39] <bac> rbasak: so it'll go in as version 1.3.1?
[12:40] <rbasak> bac: yes - because I'm cherry-picking from trunk, and I think I'm missing at least one commit that went into 1.3.2. So I can't really call it 1.3.2.
[12:40] <bac> rt
[12:41] <rbasak> This is pretty common in SRUs - no process issue here. I just shouldn't bump the version unless I'm taking the whole new version wholesale, and I'm not doing that because it's easier for me to SRU-justify fewer changes.
[12:41] <rbasak> Well, for *you* to SRU-justify fewer changes. Thanks for doing those bugs :)
[12:43] <bac> np rbasak. i felt my 'regression rationals' were a bit weak and transparentl so.  :)
[12:44] <rbasak> bac: we'll worry about that if the SRU team object :)
[12:45] <rbasak> I've got the juju-quickstart SRU ready for upload now, but we can't get it landed or tested without the juju-core MRE SRU in place. I'll work on that now.
[13:00] <bac> rbasak: ok.  just let me know if you need anything from me.
[13:02] <bac> rick_h_: it is a little bit of a non-issue now, but i did just get a quickstart launch on azure with gui running.
[13:02] <rick_h_> bac: yay? :)
[13:03] <bac> rick_h_: while i wait on mgz i'll see if i can get a jenkins slave to work
[13:11] <rick_h_> bac: do we have bugs/links/etc for the stuff you hit that caused us grief?
[13:12] <rick_h_> bac: just want to make sure we're good citizens and when I say we've had issues they're logged
[13:13] <bac> of the two juju ones, one is fixed in trunk, the other was on the critical list for 1.20.  i have not filed one for the availability-sets impact on us
[13:14] <rick_h_> bac: yea, that'll be one of my goals to look at what we need to do for that across our tools
[13:14] <bac> rick_h_: i'll open a bug limited to quickstart just for tracking
[13:14] <rick_h_> bac: ok thanks
[13:15] <rick_h_> bac: I think the bug needs to be two-fold. One to make sure we don't colocate by default on azure (like lxc) and second that we allow that flag to override the bootstrap is part of quickstart as well.
[13:15] <rick_h_> bac: which kind of falls into an existing quickstart bug of not being able to pass extra bootstrap config already
[13:16] <bac> rick_h_: qs could look at the yaml and error if azure without that setting
[13:17] <rick_h_> bac: don't follow?
[13:17] <rick_h_> which yaml?
[13:17] <bac> environments.yaml
[13:17] <rick_h_> bac: well we want them to use availability set
[13:17] <rick_h_> sets
[13:17] <bac> azure without availability-set-enabled: false is an error
[13:17] <rick_h_> it's enabled by default because it's the only way to make sure your env doesn't fall over on yo
[13:17] <rick_h_> you
[13:17] <bac> ok
[13:18] <rick_h_> what they did makes sense, it just puts us in a bind as far as user interactions and how our tools currently work
[13:18] <bac> i shall write a descriptive bug and the proscriptive part can come later
[13:18] <rick_h_> so I can't really even argue against it, just have to get it fixed for users
[13:23] <bac> rick_h_: bug 1335121 filed, maint card created
[13:23] <_mup_> Bug #1335121: Azure availability set support causes failure <juju-quickstart:New> <https://launchpad.net/bugs/1335121>
[13:23] <rick_h_> bac: ty
[14:14] <bac> rick_h_: fwiw, i finally got jenkins and jenkins-slave up in the new azure env and the slave does show up in the config.  recall it did not on our current environment.  but the new azure uses work-arounds that are not appropriate for production.<shrug>
[14:15] <rick_h_> bac: yea
[14:15] <rick_h_> bac: ok, I think it's good that we leared a lot, we know that we need to update CI at some point, but can't today due to azure issues. Maybe we can when 1.20 hits
[14:15] <bac> rick_h_: so our current ci is a little brain dead but we dare not tear it down!  :)
[14:15] <rick_h_> bac: but should hold pattern for now and coordinate with martin/ian on CI for charmstore
[14:15] <rick_h_> :)
[14:16] <bac> rick_h_: mgz does not appear to be around today
[14:16] <rick_h_> bac: ok, let's add a tracking card to the charmstore lane and bring it up next week
[14:16] <rick_h_> maybe by email cc'ing me/ian as we had the conversation
[14:17] <rick_h_> bac: did you get rogpeppe's branch to pass tests and build properly?
[14:17] <bac> ok.  mgz works with ian and axw, so no one around until monday
[14:17] <rick_h_> bac: if so can you LGTM it and rogpeppe can land it and move forward.
[14:17] <bac> rick_h_: i'll double check
[14:17] <rick_h_> bac: sounds good (on the mgz/monday work with the net week)
[14:18] <rogpeppe> bac: make sure you pull juju-core and godeps to update its dependencies first, please
[14:18] <rogpeppe> bac: because it needs to work with juju-core's deps
[14:19] <hatch> jujugui I'm still in need of a review https://github.com/juju/juju-gui/pull/407
[14:19] <kadams54> Looking
[14:19] <rick_h_> jcastro: or Makyo or kadams54 ^ ?
[14:19] <rick_h_> sorry, jcsackett ^
[14:19] <rick_h_> thanks kadams54
[14:20] <hatch> thanks
[14:33] <rogpeppe> hmm. there's an awkward ambiguity in charm urls with respect to the store URL name space
[14:34] <rogpeppe> i was thinking that it would be logical to allow https://charmstore.com/precise/wordpress/any/file/path/in/the/zip/file
[14:34] <rogpeppe> for retrieving contents of charms
[14:35] <rogpeppe> since https://charmstore.com/precise/wordpress currently retrieves a zip file of the whole thing
[14:35] <rogpeppe> but...
[14:36] <rogpeppe> you can't tell if charmstore.com/trusty/precise/foo is a file called precise/foo in the charm called trusty, or a file called foo in the trusty version of the charm called precise
[14:37] <rogpeppe> so perhaps we're best just serving individual files from a different root
[14:37] <rogpeppe> say charmstore.com/contents/trusty/wordpress-23
[14:38] <rogpeppe> and we could accept only fully qualified URLs with a specified series and revision
[14:38] <rogpeppe> rick_h_, hatch, bac: what thinkest ye?
[14:39] <bac> rogpeppe: juju-core dependencies.tsv reference errgo but it isn't in my tree.  why doesn't 'go get -u' fetch it for me?  or is it not really required?
[14:39] <rogpeppe> bac: you probably need go get -t
[14:40] <bac> damn that -t
[14:40] <rogpeppe> bac: but godeps -f -u *.tsv
[14:40] <rogpeppe> should do the job
[14:40] <rogpeppe> bac: if you do that, you shouldn't need to use go get at all
[14:40] <bac> i didn't know of -f
[14:40] <rogpeppe> bac: it's a new flag
[14:40] <rogpeppe> bac: you might need to go get -u launchpad.net/godeps
[14:42]  * rogpeppe is minded to get rid of -f and make it the default. possibly with a -F flag to supress automatic get
[14:42] <rogpeppe> it's almost always what you want
[14:42] <rick_h_> rogpeppe: I think that we can't allow a charm to be named a series.
[14:43] <rick_h_> rogpeppe: and that will avoid any confusion/issue.
[14:43] <rogpeppe> rick_h_: is that actually enforced now?
[14:43] <rick_h_> rogpeppe: I believe it's an error on charmworld ingestion
[14:43] <rick_h_> rogpeppe: I don't know about the charmstore
[14:43] <rogpeppe> rick_h_: that does mean we can never add a series that happens to mirror an existing charm name
[14:43] <rick_h_> rogpeppe: but I think it's sane to enforce and helps us keep things clean
[14:43] <rick_h_> rogpeppe: we'll end up having a nice conversation with the charm author :)
[14:44] <bac> ok, rogpeppe, i've done all of that now.  so i'm in my GOPATH for juju/charm.  how do i fetch your version for testing?
[14:44] <rogpeppe> bac: git add remote rogpeppe git@github.com:rogpeppe/charm
[14:44] <rogpeppe> bac: git fetch rogpeppe
[14:44] <rogpeppe> bac: git checkout rogpeppe/bundledata
[14:45] <rogpeppe> bac: wait!
[14:45] <rogpeppe> bac: it's no longer in juju/charm
[14:45] <bac> rogpeppe: well i want the exact version from your pull request
[14:45] <rogpeppe> bac: it's in gopkg.in/juju/charm.v2
[14:45] <bac> rogpeppe: we're not talking about https://github.com/juju/charm/pull/9
[14:45] <rogpeppe> bac: so, first do: go get gopkg.in/juju/charm.v2
[14:45] <rogpeppe> bac: yeah, we are
[14:45] <rick_h_> rogpeppe: but I think this is why I want to do the api space spec and planning. To hammer all the rules/etc out in the merging of charmstore vs charmworld apis.
[14:45]  * bac is totally confused
[14:46] <rogpeppe> bac: gopkg.in goes to github.com to get the code
[14:46] <rick_h_> rogpeppe: because precise/wordpress doesn't return a zip in charmworld, but a json of the charmdata
[14:47] <rogpeppe> bac: the actual branch is "v2" in juju/charm
[14:47] <rogpeppe> rick_h_: i see
[14:47] <rick_h_> rogpeppe: so we need to plan out a v4 api that makes sense of both ends and update clients/etc
[14:47] <rogpeppe> rick_h_: planning the url name space is what i've been doing
[14:47] <rick_h_> rogpeppe: and I'd rather do it once vs ad-hoc
[14:47] <rogpeppe> rick_h_: yup
[14:48] <bac> rogpeppe: so do i keep $GOPATH/src/github.com/juju/charm ?
[14:48] <rogpeppe> bac: you do need to keep that for a while, because juju-core still depends on it
[14:48] <rick_h_> rogpeppe: ok, can you share out a doc then with the current store api endpoints and the charmworld ones and we can go through them in a call and resolve conflicts/plan updates that make sense?
[14:49] <rogpeppe> bac: but if you go into $GOPATH/gopkg.in/juju/charm.v2 and follow above instructions, you should get a copy of my branch for testing in the right place
[14:49] <rogpeppe> rick_h_: yup, sounds good.
[14:49] <bac> rogpeppe: ok, will do.  pulling from a rogpeppe remote seems dangerous, though, as i dont' know it is really the one under review.
[14:50] <rick_h_> rogpeppe: http://charmworld.readthedocs.org/en/latest/api.html has the info for charmworld
[14:50] <bac> rogpeppe: what if you had two branches in flight?
[14:50] <rogpeppe> bac: i suggested "git fetch", not git pull
[14:50] <rogpeppe> bac: that fetches the branch data but doesn't actually update anything
[14:51] <rogpeppe> bac: then you can check out the branch you need
[14:52] <bac> rogpeppe: ok, i didn't see that bit
[14:52] <rogpeppe> bac: of course, it's git remote add, not git add remote
[14:52] <bac> rogpeppe: yeah, i figured that out
[14:56] <rick_h_> jujugui call in 5
[14:56] <rick_h_> kanban please
[14:56] <bac> rogpeppe: http://paste.ubuntu.com/77115
[14:57] <rogpeppe> bac: The Paste you are looking for does not currently exist.
[14:57] <bac> rogpeppe: oops: http://paste.ubuntu.com/7711522/
[14:59] <Makyo> jujugui call in 2
[14:59] <rogpeppe> and that's after you've done a "godeps -u dependencies.tsv" on the latest tip of juju-core?
[15:00] <rick_h_> jujugui call now jcsackett Makyo (ant is out)
[15:01]  * bac joins
[15:06] <bac> rogpeppe: es
[15:06] <bac> s/es/yes/
[15:07] <bac> rogpeppe: yes, i'd done the updates as you requested
[15:28] <hatch> jcastro marcoceppi you can now hide the charmbrowser with a shortcut key :)
[15:39] <marcoceppi> \o/
[15:42] <hatch> marcoceppi ctrl+alt+h will hide it, you can see all the shortcuts with shift+/
[15:43] <rick_h_> hatch: or ?
[15:43] <rick_h_> I thought ? worked for shortcuts
[15:43] <hatch> well to get a ? you hit shift+/ :D
[15:44] <rick_h_> oh
[15:44] <rick_h_> well ? seems a lot easier than shift+/ :P
[15:44] <hatch> haha I always say shift+/ because I just assume people will hit / thinking of ?
[15:44] <hatch> maybe I'm the edge case :D
[15:46] <hatch> kadams54.....the test is still running......
[15:46] <hatch> lol
[16:12] <hatch> oops I ordered something from amazon from a third party....
[16:12] <hatch> darn, it's going to take a couple weeks to get here :(
[16:15] <rick_h_> whoops
[16:16] <hatch> next time I guess I should pay more attention
[16:16] <hatch> heh
[16:17] <hatch> it's just so easy to buy things sometime
[16:23]  * rick_h_ goes to get lunch
[16:39] <hatch> Makyo so I'm working on getting the ghost inspector to show on drop again and running into an issue where if you open an inspector
[16:40] <hatch> then close it, when you deploy it'll re-open that inspector
[16:40] <hatch> I remember you fixed this once before do you have any pointers?
[16:41] <Makyo> Doesn't sound familiar to me, hmm... May be in the deploy callback?
[16:45] <hatch> well you worked on the 'on deploy switch to a service inspector' bit
[16:45] <hatch> maybe it's in the inspector code
[16:46] <hatch> ahh I think that's where it is
[16:46] <hatch> go sounding board go!
[17:04] <hatch> these ads....hilarious... http://www.autoblog.com/2014/06/27/colorado-washington-pot-dui-psa-ads-video/
[17:17] <Makyo> jujugui https://github.com/juju/juju-gui/pull/406 QA steps are a little more extended now.  Works in sandbox, but requires a bit of a wait - feel free to do something else in the meantime.
[17:21] <kadams54> Makyo: I'll take a look.
[17:24]  * rogpeppe is done for the day.
[17:24] <rogpeppe> happy weekends all
[17:25] <rick_h_> have fun rogpeppe
[17:26] <hatch> cya rogpeppe  have a good weekend
[17:56] <hatch> jujugui lf a quick review/qa on https://github.com/juju/juju-gui/pull/408
[17:56] <hatch> rick_h_ any preference for another card for me?
[17:57] <rick_h_> hatch: sec looking
[17:57] <hatch> thanks
[18:03] <rick_h_> hatch: no preferences. take your pick. the bundle delay thing might be a short/sweet one in maint?
[18:04] <hatch> sure that sounds like a good small one
[18:07] <rick_h_> Makyo: branch land failed. npm bit the farm
[18:07] <Makyo> Booo
[18:11] <rick_h_> jujugui just tried to walk a person in #juju through machine view to do some work. |-| far from getting it working like he wanted
[18:16] <hatch> rick_h_ just read the backlog.... his comment about wanting to drag to the container column was something I was thinking about too (remember the hover over machine to show containers?) I think the issue we are solving is one of massive scale, if you have 10-20 containers total we can easily show them all at once
[18:16] <rick_h_> hatch: yep
[18:16] <hatch> this is a UX discussion of course
[18:16] <hatch> without UX
[18:16] <hatch> :D
[18:17] <rick_h_> hatch: definitely, I think the main thing is that there's not much unknown/new. The lxc/container syntax threw him off
[18:17] <rick_h_> hatch: and the fact that machine 0 doens't show any services because it's node 0 and has gui hulk-smashed on it I guess?
[18:17] <rick_h_> The 'root level' threw him off. So we need to correct that
[18:17] <hatch> I never really thought of this, but if you were a noob and were presented with machine view, how would you know to click on each machine to see the containers
[18:17] <hatch> ?
[18:17] <rick_h_> and some things that are in trunk that he didn't have in his gui deploy
[18:17] <hatch> definitely a UX problem there
[18:18] <rick_h_> hatch: right, but that's why we've talked about having the column just say "select a machine to view container details" or something by default
[18:18] <hatch> right right
[18:18] <hatch> but maybe showing all containers is also a possibility
[18:18] <hatch> and then when you select a machine it filters the list
[18:18] <rick_h_> overall felt good but was interesting to grab someone off the irc street and have htem walk through it :)
[18:19] <hatch> I think I'll send that idea to peeps
[18:19] <rick_h_> hatch: do me a favor, grab that chat maybe and just put it in a pastebin and put it up?
[18:19] <rick_h_> hatch: and we can break it down from there at some point
[18:19] <hatch> sure
[18:21] <hatch> hmm my client does not copy/paste well heh, investigating
[18:23] <hatch> hmm and no logs
[18:23] <rick_h_> hatch: ok, np. I can pull it.
[18:23] <rick_h_> delegation fail! :)
[18:24] <hatch> if you could that would be awesome - the logs werent' enabled for that channel for some reason
[18:24] <hatch> and copy/paste fails hard because of the layout I guess
[18:24] <hatch> it puts each thing on a new line and skips names sometimes so it's very hard to read
[18:30] <rick_h_> hatch: https://gist.github.com/9f0f521c60ca7a15fd13.git
[18:30] <hatch> thanks
[18:31] <hatch> rick_h_ do you remember if we brought up to them already about having a onboarding message in the third column?
[18:32] <rick_h_> hatch: no, but I've got a UX meeting monday and will bring it up
[18:32] <hatch> ok so I won't send this email then? Or should I send it so you have something to reference?
[18:32] <rick_h_> hatch: you can send it, we can chat about it on monday
[18:32] <hatch> ok
[18:33] <rick_h_> start a conversation and all that
[18:53] <hatch> rick_h_ email sent, sorry it's lengthy
[18:53] <hatch> :)
[18:54] <hatch> jujugui lf a quick review/qa on https://github.com/juju/juju-gui/pull/408
[18:55] <bac> rick_h_: throwing the poor new guys at amulet in the first week.  brutal.
[18:55] <hatch> bac lol
[18:55] <hatch> oo rah!
[19:00] <rick_h_> hatch: heh all good
[19:00] <rick_h_> bac: :) well I was hoping to find papercuts in charms that had amulet tests since they audit I thought there'd be a bunch
[19:01] <bac> rick_h_: it'll just be funny when the ask the rest of us about amulet and we all shrug and say "dunno, haven't really ever used it."  :)
[19:02] <rick_h_> bac: look ok overall?
[19:02] <bac> rick_h_: yeah, nice
[19:02] <bac> i think i'd be happy to get such an intro doc on my first day.
[19:03] <rick_h_> bac: cool, yea we'll see how it goes
[19:03] <hatch> it took me a year to get invited to all the right mailing lists! lol
[19:03] <hatch> that's half the fun!
[19:03] <hatch> haha
[19:09] <kadams54> hatch: still need someone to look at 408?
[19:10] <hatch> I do!
[19:10] <hatch> thanks
[19:10] <kadams54> What?
[19:10] <kadams54> Oh…
[19:10] <kadams54> No.
[19:10] <kadams54> I didn't mean I was going to look at it.
[19:10] <kadams54> ;-)
[19:11]  * rick_h_ steps away for a few
[19:12] <hatch> kadams54 hah damn uuuuu
[19:15] <kadams54> hatch: shipit
[19:15] <hatch> dun! thx
[19:37] <hatch> jujugui looking for a quick review/qa https://github.com/juju/juju-gui/pull/409
[19:43] <arosales> is lp or git the recommended way to file bugs against juju-gui?
[19:44]  * arosales doesn't see "issues" on https://github.com/juju/juju-gui
[19:44] <Makyo> arosales, lp, I believe.
[19:45] <arosales> Makyo: ok, thanks. Are you still doing proj mang. and releases out of lp?
[19:45] <hatch> yep lp plz
[19:46] <hatch> we are
[19:46] <hatch> er
[19:46] <hatch> well the charm
[19:46] <bac> hatch: you ok?
[19:46] <hatch> bac lol what?
[19:46] <Makyo> arosales, hatch the charm is through lp, but can pull gui trunk from github now
[19:46] <bac> hatch: well, that last flurry of comments made no sense.
[19:47]  * arosales will submit bug in lp -- thanks!
[19:47] <hatch> bac haha sorry
[19:48] <rick_h_> arosales: what's the issue?
[19:49] <arosales> rick_h_: I had a user report http://paste.ubuntu.com/7712762/  but I was uable to reproduce myself
[19:49] <arosales> so I was going to suggest he open a bug if it continues to plague him.
[19:49] <rick_h_> arosales: right, he filed a bug and I triaged it
[19:50] <rick_h_> arosales: it's FF only atm and filed but low atm
[19:50] <hatch> what the....
[19:50] <hatch> heh
[19:50] <rick_h_> https://bugs.launchpad.net/juju-gui/+bug/1335192
[19:50] <_mup_> Bug #1335192: Drag and drop sidebar text to itself navigates in firefox <juju-gui:Triaged> <https://launchpad.net/bugs/1335192>
[19:50] <arosales> ah ok, good to hear it was filled
[19:50] <rick_h_> yep, actually someone I know...used to work for him ages ago
[19:51] <hatch> rick_h_ ohh ok - there is a e.stopImmediatePropogation() missing somewhere there
[19:51] <rick_h_> hatch: something with drop target/etc something
[19:51] <hatch> there was an issue with that in FF before with dropping on the canvas
[19:51] <rick_h_> hatch: yea
[20:12] <hatch> stepping out for lunch bbl
[20:13] <kadams54> hatch: looking at PR 409
[20:15] <bac> jujugui: i'm toast so i'm calling it a day.  have a nice weekend
[20:15] <kadams54> bac: have a good weekend too!
[20:15] <rick_h_> bac: have a good weekend
[20:18] <Makyo> jujugui quick review, slightly longer QA: https://github.com/juju/juju-gui/pull/410
[20:19] <kadams54> Makyo: I'll take a look in just a moment.  Have a good weekend folks!
[21:13] <hatch> yo
[21:18] <hatch> kadams54 isn't confirmation the religious thing
[21:18] <hatch> vs conformation
[21:18] <hatch> or did I mix those up? hah
[21:18] <hatch> yeah I'm pretty sure it's conformation :)
[21:20] <hatch> maybe it's confirmation
[21:20] <hatch> oh, confirmation is the religious thing and the act of confirming
[21:20] <hatch> hah
[21:20] <hatch> long week I guess
[22:48] <kadams54> hatch: yeah, "confirm" is the root word, so "confirmation". Which is also a religious ceremony. Yay weekend!
[22:48] <hatch> lol


[00:12] -queuebot:#ubuntu-release- New source: rust-bindgen-0.65 (noble-proposed/primary) [0.65.1+dfsg0-0ubuntu1]
[00:17] <liushuyu> Hi, is there any AA available for reviewing the new revision of https://launchpad.net/ubuntu/noble/+queue?queue_state=0&queue_text=rust-bindgen-0.65 and reject the previous upload? Thanks!
[05:25] <arraybolt3> Question for an archive admin (since I'm not sure how I would look this up) - how exactly should the situation be handled in which a source package with one name needs to be replaced by a newer source package with a *different* name that provides newer versions of the same binary packages as the older source package?
[05:26] <arraybolt3> Like, can a source package be renamed? Or can you have two source packages that provide different versions of the same binary packages, so that the newer one sort of "takes over" the older one and then the older one can be removed at some point?
[05:29] <arraybolt3> (Reasoning behind the question - I'm working on replacing the old, out-of-date accounts-signon-qml package in Ubuntu with the newer, more up-to-date one from Debian, but the one in Debian depends on a newer version of signon-qt5, which is provided by a package named signon in Ubuntu and a package named signond in Debian.)
[05:29] <arraybolt3> *a source package named...
[06:33] <doko> upload the new one, ask for removal of the old source (only) package after the binaries are built
[06:35] -queuebot:#ubuntu-release- New: accepted qemu [amd64] (noble-proposed) [1:8.1.3+ds-1ubuntu1]
[06:35] -queuebot:#ubuntu-release- New: accepted qemu [armhf] (noble-proposed) [1:8.1.3+ds-1ubuntu1]
[06:35] -queuebot:#ubuntu-release- New: accepted qemu [s390x] (noble-proposed) [1:8.1.3+ds-1ubuntu1]
[06:35] -queuebot:#ubuntu-release- New: accepted qemu [arm64] (noble-proposed) [1:8.1.3+ds-1ubuntu1]
[06:35] <arraybolt3> doko: perfect, thanks
[06:35] -queuebot:#ubuntu-release- New: accepted qemu [ppc64el] (noble-proposed) [1:8.1.3+ds-1ubuntu1]
[08:11] -queuebot:#ubuntu-release- New: accepted rust-bindgen-0.65 [source] (noble-proposed) [0.65.1+dfsg0-0ubuntu1]
[08:13] -queuebot:#ubuntu-release- New: rejected rust-bindgen-0.65 [source] (noble-proposed) [0.65.1+dfsg0-0ubuntu1]
[08:16] -queuebot:#ubuntu-release- New binary: rust-bindgen-0.65 [amd64] (noble-proposed/none) [0.65.1+dfsg0-0ubuntu1] (no packageset)
[08:16] -queuebot:#ubuntu-release- Unapproved: alsa-ucm-conf (jammy-proposed/main) [<IP_ADDRESS>-1ubuntu1.8 => <IP_ADDRESS>-1ubuntu1.9] (core)
[08:16] -queuebot:#ubuntu-release- Unapproved: alsa-ucm-conf (mantic-proposed/main) [1.2.9-1ubuntu3 => 1.2.9-1ubuntu4] (core)
[08:16] -queuebot:#ubuntu-release- Unapproved: alsa-ucm-conf (lunar-proposed/main) [<IP_ADDRESS>-1ubuntu9.2 => <IP_ADDRESS>-1ubuntu9.3] (core)
[08:17] -queuebot:#ubuntu-release- New binary: rust-bindgen-0.65 [ppc64el] (noble-proposed/none) [0.65.1+dfsg0-0ubuntu1] (no packageset)
[08:17] -queuebot:#ubuntu-release- New binary: rust-bindgen-0.65 [arm64] (noble-proposed/none) [0.65.1+dfsg0-0ubuntu1] (no packageset)
[08:19] -queuebot:#ubuntu-release- New binary: rust-bindgen-0.65 [s390x] (noble-proposed/none) [0.65.1+dfsg0-0ubuntu1] (no packageset)
[08:27] -queuebot:#ubuntu-release- New binary: rust-bindgen-0.65 [armhf] (noble-proposed/universe) [0.65.1+dfsg0-0ubuntu1] (no packageset)
[08:47] -queuebot:#ubuntu-release- New binary: rust-bindgen-0.65 [riscv64] (noble-proposed/universe) [0.65.1+dfsg0-0ubuntu1] (no packageset)
[09:33] <artur> Hello, can someone review this SRU upload please? https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=alsa-ucm-conf
[09:34] <artur> https://launchpad.net/ubuntu/mantic/+queue?queue_state=1&queue_text=alsa-ucm-conf
[09:34] <artur> https://launchpad.net/ubuntu/lunar/+queue?queue_state=1&queue_text=alsa-ucm-conf
[09:37] -queuebot:#ubuntu-release- New: accepted rust-bindgen-0.65 [amd64] (noble-proposed) [0.65.1+dfsg0-0ubuntu1]
[09:37] -queuebot:#ubuntu-release- New: accepted rust-bindgen-0.65 [armhf] (noble-proposed) [0.65.1+dfsg0-0ubuntu1]
[09:37] -queuebot:#ubuntu-release- New: accepted rust-bindgen-0.65 [riscv64] (noble-proposed) [0.65.1+dfsg0-0ubuntu1]
[09:37] -queuebot:#ubuntu-release- New: accepted rust-bindgen-0.65 [arm64] (noble-proposed) [0.65.1+dfsg0-0ubuntu1]
[09:37] -queuebot:#ubuntu-release- New: accepted rust-bindgen-0.65 [s390x] (noble-proposed) [0.65.1+dfsg0-0ubuntu1]
[09:37] -queuebot:#ubuntu-release- New: accepted rust-bindgen-0.65 [ppc64el] (noble-proposed) [0.65.1+dfsg0-0ubuntu1]
[09:39] <artur> Hello @ahasenack, could you help to review the above when free? Thank you.
[12:21] <ahasenack> will take a look
[12:31] <ricotz> hello SRU team, please take a look at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2044019
[12:31] -ubottu:#ubuntu-release- Launchpad bug 2044019 in libreoffice (Ubuntu Mantic) "[SRU] libreoffice 7.6.3 for mantic" [Medium, In Progress]
[12:49] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (lunar-proposed/main) [2.828 => 2.828.2] (desktop-core, i386-whitelist)
[13:22] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (focal-proposed/main) [2.664.49 => 2.664.51] (desktop-core, i386-whitelist)
[14:57] -queuebot:#ubuntu-release- Unapproved: accepted gcc-9 [sync] (focal-proposed) [9.4.0-1ubuntu1~20.04.3]
[15:14] -queuebot:#ubuntu-release- New binary: efivar [amd64] (noble-proposed/main) [38-3] (core)
[15:15] -queuebot:#ubuntu-release- New binary: efivar [armhf] (noble-proposed/main) [38-3] (core)
[15:15] -queuebot:#ubuntu-release- New binary: efivar [arm64] (noble-proposed/main) [38-3] (core)
[15:28] -queuebot:#ubuntu-release- New binary: efivar [riscv64] (noble-proposed/main) [38-3] (core)
[16:49] -queuebot:#ubuntu-release- Unapproved: fonts-noto-color-emoji (jammy-proposed/main) [2.038-0ubuntu1 => 2.042-0ubuntu<IP_ADDRESS>] (i386-whitelist, ubuntu-desktop)
[16:51] -queuebot:#ubuntu-release- Unapproved: fonts-noto-color-emoji (mantic-proposed/main) [2.038-1 => 2.042-0ubuntu<IP_ADDRESS>] (i386-whitelist, ubuntu-desktop)
[16:51] -queuebot:#ubuntu-release- New: accepted efivar [amd64] (noble-proposed) [38-3]
[16:51] -queuebot:#ubuntu-release- New: accepted efivar [armhf] (noble-proposed) [38-3]
[16:51] -queuebot:#ubuntu-release- New: accepted efivar [arm64] (noble-proposed) [38-3]
[16:51] -queuebot:#ubuntu-release- New: accepted efivar [riscv64] (noble-proposed) [38-3]
[16:59] <ricotz> hello, please re-try this nodejs-mozilla build - https://launchpad.net/ubuntu/+source/nodejs-mozilla/12.22.12-0ubuntu<IP_ADDRESS>/+build/24312943
[17:03] <tsimonq2> ricotz: .
[17:04] <tsimonq2> ricotz: I would escalate to the Launchpad team; it failed again.
[17:05] <ricotz> tsimonq2, hmm, could you hit it once more?
[17:06] <tsimonq2> ricotz: .
[17:07] <ricotz> tsimonq2, thanks, I guess there is something wrong
[17:43] <jbicha> please reject fonts-noto-color-emoji 2.041 from jammy & mantic now that I have uploaded a newer version
[18:27] -queuebot:#ubuntu-release- Unapproved: accepted powerpc-utils [source] (focal-proposed) [1.3.4-0ubuntu2.1]
[21:18] -queuebot:#ubuntu-release- Unapproved: rejected fonts-noto-color-emoji [source] (jammy-proposed) [2.041-0ubuntu<IP_ADDRESS>]
[21:18] -queuebot:#ubuntu-release- Unapproved: rejected fonts-noto-color-emoji [source] (mantic-proposed) [2.041-0ubuntu<IP_ADDRESS>]
[23:29] -queuebot:#ubuntu-release- New binary: simgrid [amd64] (noble-proposed/universe) [3.35-1] (no packageset)
[23:33] -queuebot:#ubuntu-release- New binary: simgrid [arm64] (noble-proposed/universe) [3.35-1] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: simgrid [ppc64el] (noble-proposed/universe) [3.35-1] (no packageset)
[23:52] -queuebot:#ubuntu-release- New binary: simgrid [armhf] (noble-proposed/universe) [3.35-1] (no packageset)
[23:52] -queuebot:#ubuntu-release- New binary: simgrid [s390x] (noble-proposed/universe) [3.35-1] (no packageset)


[00:40] <ojwb> hmm, so i turn my old laptop on and discover it's hibernated not shut down
[00:40] <ojwb> which is interesting as hibernating didn't work last time I tried
[00:40] <ojwb> and I log in to find the shutdown confirmation dialog up
[00:40] <ojwb> I thought it counted down 60 seconds now...
[02:44] <chilts> who knows
[02:45] <chilts> I've never tried hibernation ... I just figure it won't work from within XMonad (I also have no idea how to tell it to do it either) :)
[02:48] <ojwb> chilts: well, it essentially saves the state of the whole machine, so it should work from anywhere
[02:48] <ojwb> at least if you can make it happen - I think there's a command line interface to it
[02:49] <chilts> yeah, I was thinking there must be somewhere
[02:50] <chilts> /etc/acpi/sleep.sh and /etc/acpi/hibernate.sh I believe
[02:50] <chilts> I'll try it later
[02:53] <chilts> so suspend uses a little power to keep things running, hibernate uses no power
[02:54] <chilts> wake up suspend by pressing a key or clicking the mouse, wake up hibernate by pressing the power button
[02:54] <ojwb> yes, suspend comes back in almost no time
[02:54] <chilts> that's as far as I can figure it out (for my own purposes) :)
[02:54] <chilts> cool
[02:54] <ojwb> hibernate can be a bit sluggish as stuff comes back from swap
[03:05] <chilts> looks like it just slept and once reconnected to my wireless, all looks ok :)
[03:08] <ojwb> yeah, you can expect it to work these days
[03:08] <ojwb> it used to be a bit pot luck
[03:25] <chilts> :)


[00:04] <user|33> hi guys, kernel 6.2 available on Kubuntu 23.04?
[04:09] <CraigM> I just tried out the the Kubuntu 23.04 installer: here is my feed-back. I'm looking to setup a system with disk encryption, separate user partition and and a file system that does check-summing. I've had some annoyances with my current encrypted ZFS on root setup (like lack of installer support, snapshots breaking grub configuration etc.) so I
[04:09] <CraigM> decided I'd go with something that should be more supported, Btrfs with LVM encryption. I selected the guided encrypted option (expecting it to guide me through picking a format and partitioning scheme), and noticed that the password boxes arn't labeled. I managed to guess I should put my password in there, and the button to continue to the next
[04:09] <CraigM> step wasn't enabled. Turns out theres no feedback if the two passwords don't match. Once fixed, I hit next, and it asked me if I wanted to continue warning about erasing my data and showing the partition selection. It looked like it was going to use ext4 (which I didn't want and it never let me pick), so I said not to continue. Despite requesting
[04:09] <CraigM> it not continue, my drive was formatted with the partition scheme it proposed. I then looked at the manual partitioning tool, which didn't respect window resize very well, and didn't show the vendor information for the drives (like the other view did) which would have made it easy to format the wrong one of my nvme drives (since they are hard to
[04:09] <CraigM> tell apart now that it formatted my empty one against my will). Thats a far as I decided to go with the installer for now, but I figured providing some feedback might be useful, and the website doesn't make it clear where feedback should be sent so I'm putting it here.
[04:31] <alkisg> user|33: yes
[04:47] <mmikowski> CraigM: I havem
[04:51] <mmikowski> CraigM: I haven't looked at the 23.04 installer, but it sounds like it might still be Ubiquity based. One thing I always recommend is to physically remove any drives you don't want formatted :)
[06:22] <lanskee> hello there,can i talk with some one about kioslave5 bug please? Cant send error because this button dont , i can only copy the developer information . Ty
[06:26] <kubuntu>  Hi guys, I'm having some trouble connecting to my synology nas with ubuntu. From a mac I have no problem: I go to finder>network>synology, enter credentials and I'm inside
[06:27] <kubuntu> from ubuntu > dolphin > network > shared folders (smb) > synology-ds218 and then no folder found error
[06:27] <kubuntu> what am I doing wrong?
[06:28] <kubuntu> hi lanskee what is kioslave5?
[06:30] <lanskee> that's some kde stuff, idk exactly. But this error happens while rendering in sideFx software "Houdini" i tried  22.04,22.10 and even now in 23.04 this error is still there.
[06:33] <lanskee> this error occurs after every 1 frame of rendering, i have some sequences with 240+ frames, all works but this error is overwhelming notifications area
[06:41] <kubuntu> with a little patience you will surely find someone who can give you a hand. meanwhile you could see how to hide the notification
 Wow! I just had a pop up to upgrade! I have never seen that before! Nice! Click... hmmm. : https://irc-attachments.kde.org/de1efa29/file_65263.jpg
 After I upgraded to Kubuntu 23.04 LibreOffice doesn't show up after starting it.
 Any clue?
 Ah - I startet LibreOffice (not Writer, Calc, etc...) and it shows up.
 Bug or feature?
 definitely a bug.
 Can't create new docs.
 I'll ask @libreoffice
[08:49] <Guest75> Hi I'm trying to upgrade from Kubuntu 20.04 LTS to 22.04 LTS but it fails to download libqt5widgets5_5.15.3+dfsg-2ubuntu0.2_amd64.deb. I have tried for several days now on different mirrors without any luck, what can I do ?
[08:55] <Guest75> The URL to the file in question is: http://archive.ubuntu.com/ubuntu/pool/universe/q/qtbase-opensource-src/libqt5windgets5_5.15.3+dfsg-2ubuntu0.2_amd64.deb
[08:57] <Guest75> Sorry a type sneaked inn. Correct URL: http://archive.ubuntu.com/ubuntu/pool/universe/q/qtbase-opensource-src/libqt5widgets5_5.15.3+dfsg-2ubuntu0.2_amd64.deb
[08:58] <Guest75> Can anyone else download it ?
[09:09] <Guest75> I'm I alone here ?
[09:36] <fsflp23> Hi!  I just upgraded from 20.04 to 22.04.  Firefox is now the snap version and it is not using the custom colors for the Active Titlebar and Inactive Titlebar.  Does anyone know how to configure this version of Firefox to use the colors selected in System Settings?
[12:54] <BluesKaj> Hi all
[13:14] <guiverc> fsflp23, the snap packaged firefox uses gtk themes (not Qt themes), so try setting an appropriate GTK theme is all I can offer sorry.
[13:15] <guiverc> (if you look, you'll note gtk-common-themes & gnome-3-38-2004 snaps installed; used by firefox; what Mozilla chose to use)
[13:16] <guiverc> (actually it maybe gnome-42-2204 you have installed; sorry if I was incorreect)
 Hey all
 I switched on my system and it displayed this while it was booting up,  "booting from Ubuntu failed verify it contains a 64bit UEFI OS, Press any key to continue booting"
 What might be the case here cause I don't have an idea at all
[13:58] <D4mned> hello iam having a problem with my locale everything is fine except my terminal is giving arabic output and i want that to be in english
[13:59] <D4mned> for example when i run aptitude it opens in arabic
[13:59] <D4mned> and i cant figure out how to change that
[14:02] <BluesKaj> D4mned, look in system settings/regional settings GUI
[14:03] <D4mned> i did that i have american english as default and arabic
[14:03] <D4mned> but american english is on top
[14:04] <D4mned> and when i do locale in the terminal everything is set to en_US.UTF-8
[14:05] <D4mned> but its different from whats in /etc/default/locale
[14:05] <D4mned> in etc/default/locale i got LANGUAGE=en_us:ar
[14:08] <BluesKaj> change the :ar to :en
[14:09] <D4mned> okay i guess i have to log out and then back in
[14:09] <D4mned> brb
[14:12] <D4mned> nope still the same
 ??? (re @PJtunes: Hey all
 I switched on my system and it displayed this while it was booting up,  "booting from Ubuntu failed verify it contains a 64bit UEFI OS, Press any key to continue booting")
[14:23] <tomreyn> PJtunes: i can't find this error message anywhere on the web, which suggests it is probably phrased slightly differently on your screen.
[14:24] <tomreyn> PJtunes: what it probably means is that your kubuntu installation is a 32-bit or legacy BIOS installation
[14:25] <tomreyn> and that you are booting into the UEFI variant of the grub boot loader (64-bit)
[14:28] <arraybolt3> @PJtunes: Did this system ever work before? And if so, did you change anything when this started happening?
 Yes it's a 32-bit BIOS installation (re @IrcsomeBot: <tomreyn> PJtunes: what it probably means is that your kubuntu installation is a 32-bit or legacy BIOS installation)
 Yes it works, the thing is this pops up whenever I leave the system in sleep mode for too long or when it goes off abruptly (re @IrcsomeBot: <arraybolt3> @PJtunes: Did this system ever work before? And if so, did you change anything when this started happening?)
[14:34] <tomreyn> 32-bit kubuntu hasn't been supported for some years, i'd think
[14:39] <genii> I think 16.04 or possibly 18.04
[14:43] <arraybolt3> @PJtunes: What version of Kubuntu is this? It sounds like your system supports 64-bit Kubuntu but is only running 32-bit Kubuntu, or possibly it's somehow switching between BIOS and UEFI mode.
 Oh wow!! (re @IrcsomeBot: <arraybolt3> @PJtunes: What version of Kubuntu is this? It sounds like your system supports 64-bit Kubuntu but is only running 32-bit Kubuntu, or possibly it's somehow switching between BIOS and UEFI mode.)
 It's 22.04 (re @IrcsomeBot: <genii> I think 16.04 or possibly 18.04)
 Yes it does support 64-bit but don't know how to go about running 64bit on it (re @IrcsomeBot: <arraybolt3> @PJtunes: What version of Kubuntu is this? It sounds like your system supports 64-bit Kubuntu but is only running 32-bit Kubuntu, or possibly it's somehow switching between BIOS and UEFI mode.)
[14:46] <arraybolt3> If it's 22.04, you're running a 64-bit OS already.
[14:46] <arraybolt3> @PJtunes: To be sure I understand, you start the system. It works, You put it in sleep. When you wake it up, you see this message? Or does it turn off automatically while in sleep and when you turn it on then you see this message?
[14:47] <arraybolt3> From experience, the error you're seeing is that the computer is trying to boot Kubuntu and can't find GRUB.
 Yes you get it, sometimes when I wake it up it just displays dark or cursor won't be moving, I'll have to forcefully shut it down, then whenever I reboot again it shows this, but it doesn't show that everytime tho (re @IrcsomeBot: <arraybolt3> @PJtunes: To be sure I understand, you start the system. It works, You put it in sleep. When you wake it up, you see this message? Or does it turn off automatically while in sleep and when you turn it o
 Ohh
 Is there anything I can do from my end to stop this from occurring? (re @IrcsomeBot: <arraybolt3> From experience, the error you're seeing is that the computer is trying to boot Kubuntu and can't find GRUB.)
 Or should I stop leaving the system on sleep mode for a long time too cause seems like the hardware doesn't support that
[14:53] <genii> Some Macs have 32bit UEFI but 64bit OS
[14:54] <arraybolt3> @PJtunes: I guess not leaving it in sleep for a while would be a good starting point. Also if you have anything related to hibernation enabled, disable it.
 True (re @IrcsomeBot: <genii> Some Macs have 32bit UEFI but 64bit OS)
 Okay I'll do just that, thank you very much (re @IrcsomeBot: <arraybolt3> @PJtunes: I guess not leaving it in sleep for a while would be a good starting point. Also if you have anything related to hibernation enabled, disable it.)
[15:50] <yossarianuk> heads up - 23.04 - the zoom-client snap is broken
[15:51] <yossarianuk> with the 'stable' snap ->  Testing for explicit PulseAudio choice...  ...and PulseAudio has been explicitly chosen, so using it
[15:51] <yossarianuk> And app doesn't start
[15:51] <yossarianuk> you cannot use edge either
[15:51] <yossarianuk> error while loading shared libraries: libfontconfig.so.1: cannot open shared object file: No such file or directory
[15:52] <yossarianuk> however .. the zoom deb package works fine
[15:56] <vboxuser> ls
 Hi every one! any cases of Intel Iris XE and grafic freeze in normal boot? (recovery boot works fast)
[20:31] <Elliria> This is from Kubuntu 20.04, but may be useful: https://www.reddit.com/r/linuxquestions/comments/nlh3xq/kubuntu_2004_strange_freeze/
[21:00] <floown> Hello. I wanted to upgrade to Kubuntu 23.04 from 22.04 but the new upgrade is not available when I do a: # do-release-upgrade -m desktop
[21:01] <Elliria> I think that's because 22.04 is an LTS and 23.04 isn't.
[21:01] <floown> The command result is: = Welcome to Ubuntu 22.10 'Kinetic Kudu' =
[21:01] <Elliria> You can only go from the same kind to the same kind.
[21:03] <floown> really? So I must upgrade to Kinetic first, and in a second time to 23.04?
[21:04] <arraybolt3> Elliria: Almost - you can only go from one release to the next subsequent release, except for you can jump from LTS to LTS without going through all the ones in between.
[21:05] <arraybolt3> floown: So yes, you have to upgrade to Kinetic first, then Lunar. Note that Kinetic and Lunar are both interim releases that get much less support time than the LTS releases, so if you don't want to be upgrading often, you should probably stay on Jammy.
[21:06] <Elliria> Interesting. Thanks, arraybolt3.
[21:07] <floown> Oh, ok. But for the backport (for Plasma) it will continue on Jammy, even if Lunar is launched?
[21:12] <floown> I have that line deb https://ppa.launchpadcontent.net/kubuntu-ppa/backports-extra/ubuntu/ jammy main
[21:21] <arraybolt3> floown: Jammy *should* continue to get backported KDE versions, if they can be made to work with Jammy at least.
[21:26] <floown> Ok
[22:11] <fsflp23> guiverc: Thanks for the info!  It pointed me in the right direction to research a bit more,  I don't know much about the themes but learning.
[22:12] <fsflp23> Don't know if this will work but I may try to remove the snap version and try downloading from the mozilla web site and see how that works.
[22:14] <fsflp23> I downloaded the new Mullvad browser based on firefox and it installed easily and uses the titlebar colors selected in system settings so at least I can use this browser if the download from mozilla does not work.
[22:27]  * keithzg[m] uploaded an image: (16KiB) < https://libera.ems.host/_matrix/media/v3/download/kde.org/8ca3aee477c052e4d9edd9a3f82da4b1f5cc3a60/1682116035881.png >
[22:27] <keithzg[m]> Well that's not terribly informative
[23:13] <mmikowski> keithzg[m]: Upgrade from what-to-what?
[23:14] <mmikowski> 22.04 to 23.04? 22.10 to 23.04? Something else?
[23:33] <keithzg[m]> 22.10 to 23.04
[23:33] <keithzg[m]> Oh well, the GUI updater has literally never worked for me on any of my main PCs, just tried it on a whim heh


[03:55] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (xenial-proposed) [3.168.6]
[03:58] -queuebot:#ubuntu-release- Unapproved: accepted postfix [source] (xenial-proposed) [3.1.0-3ubuntu0.3]
[03:59] -queuebot:#ubuntu-release- Unapproved: accepted powerline [source] (xenial-proposed) [2.3-1ubuntu0]
[08:25] -queuebot:#ubuntu-release- Unapproved: accepted fwupdate [source] (xenial-proposed) [0.5-2ubuntu7]
[08:26] -queuebot:#ubuntu-release- Unapproved: accepted fwupdate-signed [source] (xenial-proposed) [1.11.3]
[08:27] -queuebot:#ubuntu-release- Unapproved: fwupdate (xenial-proposed/main) [0.5-2ubuntu6 => 0.5-2ubuntu7] (core)
[08:27] -queuebot:#ubuntu-release- Unapproved: fwupdate (xenial-proposed/main) [0.5-2ubuntu6 => 0.5-2ubuntu7] (core)
[09:50] <Laney> distro-info-data claims zesty is still supported :(
[09:51] <Laney> ah someone reported it https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1743936
[09:53] <tsimonq2> .ir
[09:53] <tsimonq2> (mistype)
[10:27] <tseliot> wgrant: hi, would you mind bumping the armhf build here, please? https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/340.106-0ubuntu1
[10:28] <cjwatson> I'll do it, one moment
[10:31] <cjwatson> tseliot: done
[10:31] <tseliot> cjwatson: thanks!
[10:35] <infinity> Laney: Thankfully, that bug solves itself in a week!
[10:52] <Laney> infinity: Heh.
[10:57] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (artful-proposed) [1:17.10.9]
[11:18] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (artful-proposed) [17.1-6-g8b145067-0ubuntu1~17.10.1]
[11:48] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (xenial-proposed) [17.1-6-g8b145067-0ubuntu1~16.04.1]
[12:01] -queuebot:#ubuntu-release- Unapproved: accepted designate-dashboard [source] (artful-proposed) [5.0.1-0ubuntu1]
[12:27] -queuebot:#ubuntu-release- Unapproved: accepted fwupdate [amd64] (xenial-proposed) [0.5-2ubuntu7]
[12:27] -queuebot:#ubuntu-release- Unapproved: accepted fwupdate [i386] (xenial-proposed) [0.5-2ubuntu7]
[12:46] -queuebot:#ubuntu-release- Unapproved: clamav (xenial-proposed/main) [0.99.2+dfsg-0ubuntu<IP_ADDRESS> => 0.99.2+dfsg-0ubuntu<IP_ADDRESS>] (ubuntu-server)
[12:54] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (xenial-proposed) [2:9.1.2-0ubuntu4]
[13:04] -queuebot:#ubuntu-release- Unapproved: rejected grub2-signed [source] (xenial-proposed) [1.66.16]
[13:04] -queuebot:#ubuntu-release- Unapproved: rejected grub2 [source] (xenial-proposed) [2.02~beta2-36ubuntu3.16]
[13:21] <slangasek> nacc: yakkety> yes, IS raised that same question and I've acked its removal also
[13:26] -queuebot:#ubuntu-release- Unapproved: rejected gnome-software [source] (xenial-proposed) [3.20.5-0ubuntu<IP_ADDRESS>]
[14:18] -queuebot:#ubuntu-release- Unapproved: linux-firmware (xenial-proposed/main) [1.157.15 => 1.157.16] (core, kernel)
[14:48] -queuebot:#ubuntu-release- Unapproved: rejected bluez [source] (xenial-proposed) [5.37-0ubuntu5.2]
[14:49] -queuebot:#ubuntu-release- Unapproved: bluez (xenial-proposed/main) [5.37-0ubuntu5.1 => 5.37-0ubuntu5.2] (ubuntu-desktop)
[15:36] -queuebot:#ubuntu-release- Unapproved: accepted keystone [source] (xenial-proposed) [2:9.3.0-0ubuntu3.2]
[15:49] -queuebot:#ubuntu-release- Unapproved: accepted bluez [source] (xenial-proposed) [5.37-0ubuntu5.2]
[16:04] <nacc> slangasek: cool, thanks
[17:11] -queuebot:#ubuntu-release- New binary: json-c [amd64] (bionic-proposed/main) [0.12.1-1.3] (core)
[17:14] -queuebot:#ubuntu-release- New binary: json-c [i386] (bionic-proposed/main) [0.12.1-1.3] (core)
[17:16] -queuebot:#ubuntu-release- New binary: btchip-python [amd64] (bionic-proposed/universe) [0.1.24-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: krb5 [i386] (bionic-proposed/main) [1.16-1] (core)
[17:17] -queuebot:#ubuntu-release- New binary: argon2 [amd64] (bionic-proposed/universe) [0~20161029-1.1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: argon2 [i386] (bionic-proposed/universe) [0~20161029-1.1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: kpmcore [i386] (bionic-proposed/universe) [3.3.0-1] (kubuntu)
[17:25] -queuebot:#ubuntu-release- New binary: ignition-msgs [i386] (bionic-proposed/universe) [1.0.0+dfsg1-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: ignition-msgs [amd64] (bionic-proposed/universe) [1.0.0+dfsg1-1] (no packageset)
[17:30] -queuebot:#ubuntu-release- New binary: libgaminggear [amd64] (bionic-proposed/universe) [0.15.1-4] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: limesuite [amd64] (bionic-proposed/universe) [17.12.0+dfsg-1] (no packageset)
[17:39] -queuebot:#ubuntu-release- New binary: kpmcore [amd64] (bionic-proposed/universe) [3.3.0-1] (kubuntu)
[17:41] -queuebot:#ubuntu-release- New binary: mygpoclient [amd64] (bionic-proposed/universe) [1.8-1] (no packageset)
[17:45] -queuebot:#ubuntu-release- New binary: rapmap [amd64] (bionic-proposed/universe) [0.5.0+dfsg-3] (no packageset)
[17:46] -queuebot:#ubuntu-release- New binary: krb5 [amd64] (bionic-proposed/main) [1.16-1] (core)
[17:46] -queuebot:#ubuntu-release- New binary: limesuite [i386] (bionic-proposed/universe) [17.12.0+dfsg-1] (no packageset)
[17:50] -queuebot:#ubuntu-release- New binary: svxlink [amd64] (bionic-proposed/universe) [17.12.1-1] (no packageset)
[17:51] -queuebot:#ubuntu-release- New binary: svxlink [i386] (bionic-proposed/universe) [17.12.1-1] (no packageset)
[17:51] -queuebot:#ubuntu-release- New binary: tinyxml2 [amd64] (bionic-proposed/universe) [6.0.0+dfsg-1] (no packageset)
[17:52] -queuebot:#ubuntu-release- New binary: slurm-llnl [amd64] (bionic-proposed/universe) [17.11.2-1] (no packageset)
[17:52] -queuebot:#ubuntu-release- New binary: ttfautohint [i386] (bionic-proposed/universe) [1.8.1-1] (no packageset)
[17:53] -queuebot:#ubuntu-release- New binary: tinyxml2 [i386] (bionic-proposed/universe) [6.0.0+dfsg-1] (no packageset)
[17:56] -queuebot:#ubuntu-release- New binary: golang-github-juju-httpprof [amd64] (bionic-proposed/universe) [0.0~git20141217.14bf14c-1] (no packageset)
[17:56] -queuebot:#ubuntu-release- New binary: golang-github-juju-mutex [amd64] (bionic-proposed/universe) [0.0~git20171110.1fe2a4b-1] (no packageset)
[17:56] -queuebot:#ubuntu-release- New binary: golang-github-lunixbochs-vtclean [amd64] (bionic-proposed/universe) [0.0~git20170504.d14193d-1] (no packageset)
[17:57] -queuebot:#ubuntu-release- New binary: golang-github-tv42-zbase32 [amd64] (bionic-proposed/universe) [0.0~git20160707.5015726-1] (no packageset)
[17:57] -queuebot:#ubuntu-release- New binary: ttfautohint [amd64] (bionic-proposed/universe) [1.8.1-1] (no packageset)
[17:58] -queuebot:#ubuntu-release- New binary: golang-gopkg-errgo.v1 [amd64] (bionic-proposed/universe) [0.0~git20161222.442357a-1] (no packageset)
[17:58] -queuebot:#ubuntu-release- New binary: votca-tools [i386] (bionic-proposed/universe) [1.4.1-2] (no packageset)
[17:59] -queuebot:#ubuntu-release- New binary: golang-github-juju-retry [amd64] (bionic-proposed/universe) [0.0~git20160928.1998d01-1] (no packageset)
[17:59] -queuebot:#ubuntu-release- New binary: ioport [i386] (bionic-proposed/universe) [1.2-1] (no packageset)
[18:00] -queuebot:#ubuntu-release- New binary: ioport [amd64] (bionic-proposed/universe) [1.2-1] (no packageset)
[18:00] -queuebot:#ubuntu-release- New binary: votca-tools [amd64] (bionic-proposed/universe) [1.4.1-2] (no packageset)
[18:00] -queuebot:#ubuntu-release- New binary: spinner-el [amd64] (bionic-proposed/universe) [1.7.3-1] (no packageset)
[18:02] -queuebot:#ubuntu-release- New binary: ldc [i386] (bionic-proposed/universe) [1:1.6.0-1] (no packageset)
[18:02] -queuebot:#ubuntu-release- New binary: queue-el [amd64] (bionic-proposed/universe) [0.2-1] (no packageset)
[18:03] -queuebot:#ubuntu-release- New binary: salt-pepper [amd64] (bionic-proposed/universe) [0.5.2-1] (no packageset)
[18:04] -queuebot:#ubuntu-release- New binary: gnuastro [amd64] (bionic-proposed/universe) [0.5-1] (no packageset)
[18:08] -queuebot:#ubuntu-release- New binary: gnuastro [i386] (bionic-proposed/universe) [0.5-1] (no packageset)
[18:12] -queuebot:#ubuntu-release- New binary: ldc [amd64] (bionic-proposed/universe) [1:1.6.0-1] (no packageset)
[18:22] -queuebot:#ubuntu-release- New binary: slurm-llnl [i386] (bionic-proposed/universe) [17.11.2-1] (no packageset)
[22:03] -queuebot:#ubuntu-release- Unapproved: curtin (artful-proposed/main) [17.1-6-g8b145067-0ubuntu1~17.10.1 => 17.1-11-ga4c9636b-0ubuntu1~17.10.1] (ubuntu-desktop, ubuntu-server)
[22:07] -queuebot:#ubuntu-release- Unapproved: curtin (xenial-proposed/main) [17.1-6-g8b145067-0ubuntu1~16.04.1 => 17.1-11-ga4c9636b-0ubuntu1~16.04.1] (ubuntu-server)
[22:32] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (artful-proposed) [17.1-11-ga4c9636b-0ubuntu1~17.10.1]
[22:34] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (xenial-proposed) [17.1-11-ga4c9636b-0ubuntu1~16.04.1]
[22:49] -queuebot:#ubuntu-release- Unapproved: accepted gcc-5 [source] (artful-proposed) [5.5.0-1ubuntu2]
[22:51] -queuebot:#ubuntu-release- Unapproved: accepted gcc-5 [source] (xenial-proposed) [5.4.0-6ubuntu1~16.04.6]
[23:07] -queuebot:#ubuntu-release- Unapproved: accepted clamav [source] (xenial-proposed) [0.99.2+dfsg-0ubuntu<IP_ADDRESS>]
[23:38] -queuebot:#ubuntu-release- Unapproved: php-sabre-vobject-3 (xenial-proposed/universe) [3.5.0-1ubuntu1 => 3.5.0-1ubuntu1.1] (no packageset)
[23:49] <tsimonq2> slangasek: So I just got asked why Artful's base-files etc. haven't been updated to say 17.10.1. Am I safe to respond with "because it's not an LTS" or is it just something that wasn't done but probably could be done?
[23:54] <xnox> tsimonq2, huh, no point releases for artful. It is not a point release....
[23:54] <xnox> tsimonq2, the .disk-info/* on the iso should be updated with the new date-time serial timestamp
[23:57] <krytarik> Given that the whole -updates was pulled into it too, it could indeed be called a point release though.