[00:01] <wallyworld_> sinzui: the first comment on that bug - i don't think juju needs to change since it already generates metadata for just one stream at a time, leaving the other stream metadata untouched
[00:25] <sinzui> wallyworld_, does implementing option 3 risk releasing beta1 tomorrow?
[00:25] <wallyworld_> sinzui: i'll have a fix asap
[00:25] <sinzui> wallyworld_, As much as I don't want to write  hack, I can do it in a 3 hours
[00:25] <wallyworld_> sinzui: the hack will be the backup plan?
[00:26] <wallyworld_> but i will have juju changed today
[00:26] <wallyworld_> promise :-)
[00:26] <sinzui> wallyworld_, it allows my to release, then worry that juju will want to do something different next week
[00:26] <sinzui> wallyworld_, I like your promises, but I don't want you to rush, stress, loose sleep
[00:27] <wallyworld_> i'll be fine, we're almost there
[00:27] <wallyworld_> i'll have it done b the time you SOD
[00:27] <sinzui> okay, thank you, but if you discover  blocker, remember we have a backup plan
[00:27] <wallyworld_> yep, good to know :-)
[00:27] <wallyworld_> just finishing 1 other bug, will get straight on to it soon
[00:37] <tvansteenburgh> is there something i can do to prevent this (see agent-state-info on machine 3)? http://pastebin.ubuntu.com/8859275/
[00:59] <wallyworld_> tvansteenburgh: that will be fixed in 1.21 beta1
[01:00] <tvansteenburgh> wallyworld_: \o/ thanks
[01:00] <wallyworld_> we expect to release the beta by early next week
[01:00] <tvansteenburgh> that's great news, i was about to ask :)
[01:00] <wallyworld_> :-)
[01:00] <wallyworld_> there's also a lot of other network fixes for maas
[01:01] <wallyworld_> well juju/maas
[01:23] <axw> tvansteenburgh: you can delete the default VPC in your region if you don't need it; you can't undo that (without AWS support's help)
[01:23] <axw> that should stop the error from occurring
[01:42] <wallyworld_> axw: when you have a moment :-) http://reviews.vapour.ws/r/369/
[01:50] <wallyworld_> thanks :-)
[02:00] <tvansteenburgh> axw: thanks for the tip, although i probably can't/shouldn't do that since these environments are owned by sinzui and co.
[02:11] <axw> right, probably not then ;)
[02:38] <wallyworld_> axw: i'm off to lunch, so no hurry, but review appreciated http://reviews.vapour.ws/r/370/
[02:42] <axw> wallyworld_: sure, enjoy
[03:51] <ericsnow> axw: when you have a minute could you take a look at http://reviews.vapour.ws/r/342/?  It's a little guy.
[03:55] <axw> ericsnow: sure
[03:55] <ericsnow> axw: thanks
[04:10] <axw> ericsnow: done
[04:14] <ericsnow> axw: with that backups is now completely switched over to gridfs :)
[04:14] <axw> ericsnow: awesome :)
[04:31] <wallyworld_> ericsnow: you backporting to 1.21?
[04:31] <ericsnow> wallyworld_: planning on it
[04:32] <wallyworld_> ericsnow: awesome. curtis will be doing a beta build tomorrow
[04:32] <ericsnow> wallyworld_: I guess I'm planning on doing it tonight! :)
[04:32] <wallyworld_> \o/
[04:32] <wallyworld_> ericsnow: or we can
[04:33] <wallyworld_> once it lands, we'll backport
[04:33] <ericsnow> wallyworld_: well, there's more than one patch that needs backporting
[04:33] <wallyworld_> ericsnow: in that case, don't worry, it can wait
[04:33] <ericsnow> wallyworld_: k
[04:33] <wallyworld_> it will be a bit of risk
[04:34] <wallyworld_> ericsnow: just in case, can you email be the rev numbers that would need merging
[04:34] <ericsnow> wallyworld_: will do (shouldn't be more than a handful
[04:34] <wallyworld_> ok, ta
[06:05] <ericsnow> wallyworld_: I've emailed you those rev numbers (3 of them)
[06:06] <wallyworld_> thanks ericsnow :-)
[06:06] <ericsnow> wallyworld_: plus the one I'm commiting right now (to master)
[06:06] <wallyworld_> righto
[06:06] <ericsnow> wallyworld_: you think I should hold off on backporting them?
[06:07] <wallyworld_> ericsnow: well, it's really late for you isn't it
[06:07] <ericsnow> wallyworld_: sort of :)
[06:07] <wallyworld_> so, we'll backport if needed, you go get some sleep
[06:07] <ericsnow> wallyworld_: k
[06:08] <wallyworld_> have a good weekend
[06:08] <ericsnow> wallyworld_: also, are we okay to land http://reviews.vapour.ws/r/371/? (add .reviewboardrc to the 1.20 branch)
[06:08] <wallyworld_> can't see why not
[06:08] <ericsnow> wallyworld_: k
[06:10] <ericsnow> wallyworld_: FYI, we've yet to land the restore side of backups (and we're cutting it close)
[06:11] <wallyworld_> ericsnow: i was hoping to be divorced from storage, but if it's not all there, we can wait
[06:12] <ericsnow> wallyworld_: I meant the replacement for the juju restore CLI plugin (not storage)
[06:13] <wallyworld_> ah, right, yeah that one will have to wait
[06:13] <ericsnow> wallyworld_: wait for what?
[06:13] <wallyworld_> 1.22
[06:14] <wallyworld_> ideally we'll have a week to fully test 1.21 beta before release, which is next friday
[06:14] <ericsnow> wallyworld_: so does that mean we should yank the new backups (at least the CLI for it)?
[06:15] <ericsnow> wallyworld_: they kind of go together
[06:15] <wallyworld_> yeah, i'm not across the state of play with that stuff
[06:15] <ericsnow> wallyworld_: okay, I'll follow up with Nate tomorrow
[06:15] <wallyworld_> ta, but i imagine we'd want to revert the cli
[06:16] <wallyworld_> keep curtis in the loop also
[06:16] <wallyworld_> as he will be pulling th trigger on the release
[06:19] <ericsnow> wallyworld_: got it
[06:19] <wallyworld_> ty
[06:20] <ericsnow> wallyworld_: have a good weekend :)
[07:46] <rogpeppe> does anyone know if the "format" field in metadata.yaml still has any relevance to anything?
[07:46] <rogpeppe> fwereade: ^
[07:47] <davecheney> rogpeppe: beware format 0 charms
[07:47] <rogpeppe> davecheney: there are none
[07:47] <rogpeppe> davecheney: AFAICS - i downloaded all the charms in the charm store
[07:48] <rogpeppe> davecheney: hi, BTW!
[07:48] <rogpeppe> davecheney: do you know the difference between format 1 and format 2 ?
[07:49] <rogpeppe> davecheney: the only charms that i can find that explicitly mention format specify 2, which is different from our default. but we don't seem to have any logic (in the charm package anyway) that cares one way or another
[07:50] <fwereade> rogpeppe, davecheney: the format stuff was a long long time ago, and I thought all references to it had been purged
[07:51] <rogpeppe> fwereade: there are still remnants in the charm package
[07:51] <fwereade> rogpeppe, davecheney: I can't remember exactly what it did -- some subtle change in hook tool behaviour
[07:51] <fwereade> rogpeppe, I think it's safe to ignore them
[07:51] <fwereade> rogpeppe, the code that would have been triggering on them does not exist
[07:51] <rogpeppe> fwereade: i'm just writing a GetYAML method so we can marshal metadata as yaml (finally!) and i'm just making sure that I can always omit the format field.
[07:52]  * fwereade cheers heartily at rogpeppe
[07:52] <fwereade> rogpeppe, that sgtm
[07:52] <rogpeppe> fwereade: cool
[07:53] <rogpeppe> fwereade: this means that soon you'll be able to programmatically generate charms in tests and produce their yaml metadata, which i think you might find quite useful :)
[07:54] <fwereade> rogpeppe, that is why I'm cheering :)
[07:54] <rogpeppe> fwereade: :)
[08:00] <davecheney> rogpeppe: i think we had this discussion in august 2012
[08:01] <davecheney> and determined at the time we'd expunged them all
[08:01]  * rogpeppe forgets most things
[08:01] <davecheney> from memory, i think the charm format affected the default output format of charm hooks ?
[08:01] <davecheney> and let me just say, "good riddence"
[08:01] <fwereade> davecheney, that sounds pretty likely
[08:02] <fwereade> davecheney, yeah :)
[08:02] <mattyw> morning folks
[08:52] <rogpeppe> anyone fancy a little review? https://github.com/juju/charm/pull/75
[08:55] <TheMue> morning
[09:07] <alexisb> morning TheMue
[09:08] <TheMue> alexisb: hey, still in Europe?
[09:09] <alexisb> I dont normally get to say that to you
[09:09] <alexisb> yes I am in paris
[09:09] <TheMue> alexisb: or is you inner clock not yet adjusted back to home? ;)
[09:10] <TheMue> alexisb: ah, ok, I thought you were already on your flight back
[09:51] <rogpeppe> fwereade:  https://github.com/juju/charm/pull/75
[10:23] <mattyw> fwereade, are you around?
[10:24] <rogpeppe> fwereade: i'm not sure what you mean by making the marshaling explicit
[10:25] <rogpeppe> fwereade: do you mean the field names?
[10:26] <fwereade> rogpeppe, yeah
[10:26] <rogpeppe> fwereade: why is that better? we rely on the default lower casing everywhere else?
[10:26] <rogpeppe> s/\?$//
[10:27] <rogpeppe> fwereade: and the tests ensure that it's working correctly
[10:27] <fwereade> rogpeppe, (1) we try not to everywhere else
[10:27] <fwereade> rogpeppe, (2) it's hard to make those tests good
[10:27] <fwereade> rogpeppe, unless we do explicit checks of what gets written out, which have their own problems
[10:28] <rogpeppe> fwereade: the tests test round-tripping, which seems like a good-enough test to me
[10:28] <fwereade> rogpeppe, roundtrip tests don't detect marshalling *changes* though
[10:28] <rogpeppe> fwereade: yeah, i think they will
[10:28] <rogpeppe> fwereade: we read in with the standard ReadMeta, and check that when marshaled, and read back, we get the same thing
[10:29] <rogpeppe> fwereade: so if the marshaling semantics change (e.g. to not lower case the name) the test will fail
[10:31] <rogpeppe> fwereade: for example, if i change the "Categories" tag so that the name is "Categories", the test fails
[10:31] <fwereade> rogpeppe, doesn't that depend on a chain of inference across multiple tests and implementations? I'd rather just have it 100% obvious how something's going to marshal
[10:32] <fwereade> rogpeppe, assuming readmeta works and the readmeta test works and this test uses readmeta...
[10:32] <fwereade> rogpeppe, vs "that's how it marshals, done"
[10:32]  * fwereade has to go again anyway
[10:33] <rogpeppe> fwereade: ok, i'll add explicit names, no big deal
[10:34] <rogpeppe> fwereade: though everything would break if yaml didn't lower-case as it marshaled (i actually don't like that behaviour, as it's doesn't fit with encoding/json, but i think it's reasonable to rely on)
[10:35] <rogpeppe> fwereade: and the same testing issue applies whether i make the names explicit or not.
[10:36] <fwereade> rogpeppe, thanks -- fwiw I've caught at least one proposed fieldname change that would have broken stuff subtly, I'd rather just make that mistake harder across the board
[10:37] <fwereade> rogpeppe, granted, but it's that fieldname changes don't *always* trigger hey-changing-marshalling in people's brains
[10:37] <fwereade> rogpeppe, this means that marshalling changes must be made explicitly, and will be seen to be explicit in review
[10:37] <rogpeppe> fwereade: at some point, i plan to implement a backward-compatibility checker that can ensure this kind of stuff automatically
[10:37] <fwereade> rogpeppe, that sounds awesome
[10:38] <fwereade> rogpeppe, in the meantime, be so kind as to indulge my paranoia ;)
[10:38] <rogpeppe> fwereade: will do
[10:38] <rogpeppe> fwereade: the idea is that you run all the tests, check what gets marshaled/unmarshaled, and that gives you your list of stuff that needs to be maintained correctly.
[11:06] <anastasiamac> jam, wallyworld_, axw: could u plz cast ur eyes over http://reviews.vapour.ws/r/357/ when u get a chance. this should cater for recomendations based on hardware and user preference
[11:31] <menn0> this needs a review. it's a fix for one of the bugs that needs to be sorted for 1.21 beta1. Turns out it's a long-standing issue. http://reviews.vapour.ws/r/377/
[12:12] <rogpeppe> here's a tiny PR in the charm package, if anyone wants to take a look: https://github.com/juju/charm/pull/76
[12:18] <TheMue> rogpeppe: will do
[12:18] <rogpeppe> TheMue: ta!
[12:21] <TheMue> rogpeppe: lgtm
[12:21] <rogpeppe> TheMue: ta!
[12:21] <TheMue> yw
[13:06] <wallyworld_> anyone know where fwreade is?
[13:06] <alexisb> wallyworld_, I am looking at him
[13:06] <wallyworld_> alexisb: ah, in that case i really need to talk to him
[13:06] <wallyworld_> fwereade: !!
[13:07] <wallyworld_> a couple of things, could you please look at http://reviews.vapour.ws/r/377/
[13:07] <wallyworld_> we need to land this for 1.21
[13:07] <fwereade> wallyworld_, ok, looking
[13:08] <wallyworld_> it looks ok, but i have a coupleof concerns, bt may be ok
[13:10] <fwereade> wallyworld_, I think that LGTM, but what are the concerns?
[13:10] <wallyworld_> fwereade: what happens if someone changes the number of sub ords after a relation is added
[13:10] <wallyworld_> then it could become invalid
[13:11] <fwereade> wallyworld_, don't understand the question
[13:11] <fwereade> wallyworld_, a service can't change its subordinacy
[13:11] <wallyworld_> fwereade: i had a couple brief other questions, quick chat?
[13:11] <wallyworld_> or you may be busy
[13:12] <fwereade> wallyworld_, in a sprint room, private irc if you don't want to pollute here?
[13:12] <fwereade> wallyworld_, happy to talk ofc
[13:12] <fwereade> wallyworld_, just not convenient to do so out loud
[13:12] <fwereade> wallyworld_, also my connection is rather spotty
[13:54] <lazyPower> perrito666: thanks for the follow up, dimitern and ericsnow got me sorted. I should have sent un-ping ;)
[14:00] <perrito666> np
[14:00] <perrito666> you can thank fwereade that told me you where looking for me, he told it to me after 3 beers, but the information persisted nevertheless
[14:04] <wallyworld_> perrito666: is nate around?
[14:20] <perrito666> wallyworld_: there he is
[14:20] <dimitern> anyone can review a trivial patch to fix bug 1307677? http://reviews.vapour.ws/r/380/diff/
[14:20] <mup> Bug #1307677: juju tries to use lxcbr0 when local provider is configured with kvm containers <cloud-installer> <config> <kvm> <local-provider> <juju-core:In Progress by dimitern> <https://launchpad.net/bugs/1307677>
[14:20] <wallyworld_> perrito666: tis ok, i was just going to ask for a branch to be backported, but i've just done it
[14:23] <dimitern> cmars, TheMue, as OCR, can you have a look? ^^
[14:23] <perrito666> wallyworld_: uh, I should postpone answering to you more often
[14:25] <wallyworld_> indeed :-)
[14:25] <lazyPower> fwereade: tap me next sprint and i'll get ya a beer
[14:26] <lazyPower> perrito666: same to you *hattip*
[14:26] <dimitern> thanks wallyworld_ !
[14:27] <wallyworld_> dimitern: np, sorry about brief comments, beena long day
[14:27] <wallyworld_> is this for 1.21 also?
[14:27] <dimitern> wallyworld_, yeah
[14:27] <TheMue> dimitern: *click*
[14:28] <wallyworld_> great, really happy to see these network issues get fixed
[14:29] <wallyworld_> natefinch: hey
[14:30] <wallyworld_> or perrito666
[14:32] <natefinch> yo
[14:33] <wallyworld_> hey nate
[14:33] <wallyworld_> for 1.21
[14:33] <TheMue> dimitern: you've got a review
[14:33] <dimitern> TheMue, thanks!
[14:33] <wallyworld_> i landed menno's fix for bug 1382751
[14:33] <TheMue> dimitern: yw
[14:33] <mup> Bug #1382751: non subordinate container scoped relations broken  <regression> <relations> <subordinate> <juju-core:Fix Committed by menno.smits> <juju-core 1.20:In Progress by menno.smits> <juju-core 1.21:In Progress by menno.smits> <https://launchpad.net/bugs/1382751>
[14:33] <wallyworld_> pr 1075
[14:33] <wallyworld_> i backported to 1.21
[14:33] <wallyworld_> and tried to land in pr 1077
[14:34] <wallyworld_> but
[14:34] <wallyworld_> there was test failure, due to a missing file http://juju-ci.vapour.ws:8080/job/github-merge-juju/1229/console
[14:34] <wallyworld_> i'm totally buggered, after 12:30am here
[14:34] <wallyworld_> could you possibly take a look and fix the issue and land?
[14:34] <wallyworld_> it should be small and easy hopefully given it's anded in master already
[14:35] <natefinch> wallyworld_: sure
[14:35] <wallyworld_> tyvm
[14:35] <wallyworld_> the goal is to get 1.21 beta blessed today
[14:40] <natefinch> wallyworld_: seems likely something changed between 1.21's charm.v4 revision and master's charm.v4 revision
[14:41] <wallyworld_> ah could be, charm.v4 has changed, yes
[14:47] <wallyworld_> natefinch: maybe also poke wayne about bug 1361316
[14:47] <mup> Bug #1361316: juju status panic if state conn is shutdown || closing. <cts-cloud-review> <panic> <status> <ui> <juju-core:Triaged by wwitzel3> <https://launchpad.net/bugs/1361316>
[14:47] <wallyworld_> should be a one line fix
[14:47] <natefinch> wallyworld_: yep, I'll ping him.  he was going to start looking at it yesterday, I'll make sure he's just doing the easy fix and not the hard fix :)
[14:48] <natefinch> wwitzel3: ^
[14:48] <wallyworld_> yeah, juju status is messed up
[14:48] <wallyworld_> even with err != nil, you are expected to still print partial status
[14:48] <wallyworld_> anyone know that state of bug 1381619
[14:48] <mup> Bug #1381619: Failed to destroy-environment when node is in commissioning or new state <cloud-installer> <oil> <juju-core:Triaged by mfoord> <MAAS:Incomplete> <https://launchpad.net/bugs/1381619>
[14:49] <wallyworld_> comments on the bug made me think that the fix was well understood
[14:49] <dimitern> wallyworld_, voidspace started on that yesterday IIRC
[14:49] <natefinch> rogpeppe: You just changed something in charm.v4 about testing and charm repos... we're trying to backport a change from master to 1.21 and it's getting this error: ... Panic: open /home/ubuntu/juju-core_1.21-beta1/src/gopkg.in/juju/charm.v4/testing/repo/quantal/logging-principal/metadata.yaml: no such file or directory (PC=0x4144D6)
[14:49] <wallyworld_> hopefully will be done today as it's marked critical for 1.21 :-)
[14:50] <wallyworld_> anyways, gotta sleep, good luck with final bug fixes
[14:50] <rogpeppe> natefinch: looks like you've got the wrong dependencies
[14:51] <perrito666> yay windows is fun
[14:51] <rogpeppe> natefinch: or... do you need the new changes in the charm package?
[14:51] <natefinch> rogpeppe: well, so 1.21 uses charm.v4 from before your latest change...
[14:51] <natefinch> rogpeppe: that or we make the ported fix work with charm.v4 from before your change
[14:51] <rogpeppe> natefinch: if that's the case, then how could my change in charm.v4 affect it?
[14:51] <wwitzel3> natefinch: ok, I can add the status check and put up a review
[14:52] <rogpeppe> natefinch: i think you'll have to do that
[14:52] <natefinch> rogpeppe: the fix was made to master after your change
[14:52] <rogpeppe> natefinch: that's part of the backport
[14:52] <natefinch> rogpeppe: right, so my question is - what's different?
[14:52] <natefinch> wwitzel3: cool
[14:53] <rogpeppe> natefinch: we moved the testing charms repo from charm.v4 to juju-core
[14:53] <rogpeppe> natefinch: but...
[14:53] <rogpeppe> natefinch: that error message looks like you haven't updated the charm.v4 package
[14:54] <natefinch> rogpeppe: right, I'm just concerned that if we update the charm.v4 revision that 1.21 uses, that it'll break a whole lot more stuff
[14:54] <rogpeppe> natefinch: because charm.v4/testing/repo/quantal *should* exist in the old charm.v4 package
[14:54] <rogpeppe> natefinch: yes, it will. don't do that.
[14:54] <natefinch> oh hmm
[14:54] <natefinch> ok, good, so that's what I assumed
[14:55] <rogpeppe> natefinch: it's possible that the logging-principal test charm was added recently
[14:55] <natefinch> https://github.com/juju/juju/pull/1077/files
[14:55] <natefinch> it was added in this PR
[14:55] <rogpeppe> natefinch: what version of charm.v4 is being used?
[14:55] <natefinch> rogpeppe: f97c8d630e45651f7b39ce352dd7329082f134c4
[14:56] <rogpeppe> natefinch: right, that's your problem
[15:00] <natefinch> well, so, I'm not sure how to fix this.  If updating the charm.v4 revision will break a bunch of stuff... but this test won't work in 1.21 because charm.v4 at that revision expects the testcharm to be under its own testing/repo directory
[15:00] <rogpeppe> natefinch: i see the issue
[15:01] <natefinch> It seems like the only fix is to update 1.21's dependencies to use charm.v4 with your change
[15:01] <rogpeppe> natefinch: and this is also a reason that the changes we've made in charm.v4 are good - it will prevent things like this from happening again
[15:01] <natefinch> yes definitely
[15:01] <rogpeppe> natefinch: yes
[15:01] <natefinch> and then fix whatever else falls out of that
[15:02] <rogpeppe> natefinch: those changes were sweeping but pretty much automatics
[15:02] <rogpeppe> s/cs$/c/
[15:02] <natefinch> k
[15:02] <rogpeppe> natefinch: and the compiler will tell you if you've gotten it wrong
[15:02] <rogpeppe> backporting is such fun
[15:03] <natefinch> what's doubly aggravating is that this is just  for the test.  The actual production code is fine.
[15:03] <natefinch> (in theory)
[15:03] <natefinch> well, I'm glad we made the fix so it won't happen again... too bad we hit it one last time though
[15:08] <ericsnow> natefinch: standup?
[15:33] <ericsnow> sinzui: FYI, the restore side of backups has not landed for 1.21, which renders the rest of the new backups code kind of pointless for 1.21
[15:34] <ericsnow> sinzui: I'm planning on getting a change into 1.21 that simply removes the new backups CLI but leaves the rest of the backups code intact (to lessen the risk of removing so much)
[15:34] <ericsnow> sinzui: that patch should be up in a little bit
[15:35] <wwitzel3> natefinch: http://reviews.vapour.ws/r/382/ fix for lp:1361316
[15:38] <sinzui> ericsnow, thank you
[15:40] <wwitzel3> also wallyworld_ if you're still around - http://reviews.vapour.ws/r/382/
[15:41] <sinzui> natefinch, can you organise an effort to backport the fix for bug 1382751 to beta1 (1.21 branch)? It may be in progress already
[15:41] <mup> Bug #1382751: non subordinate container scoped relations broken  <regression> <relations> <subordinate> <juju-core:Fix Committed by menno.smits> <juju-core 1.20:In Progress by menno.smits> <juju-core 1.21:In Progress by menno.smits> <https://launchpad.net/bugs/1382751>
[15:42] <natefinch> sinzui: yeah, it's in progress by me ;)
[15:42] <natefinch> sinzui: just updated the bug to reflect that
[15:43] <sinzui> you rock natefinch
[15:43] <natefinch> someday I'll tell the story of changing the keys on my keyboard so the bottom row spelled out "NATEROCKS" :)
[15:43] <natefinch> ok, well, actually, that's the whole story
[15:46] <sinzui> :)
[15:47] <wwitzel3> thanks for the review TheMue
[15:48] <TheMue> wwitzel3: yw
[15:49] <wwitzel3> I just got an email from Amazon trying to get me to pay $99 to stick a device in my home that will listen to everyting in my house and send all that data to them ...
[15:49] <wwitzel3> I feel like they should pay me for that
[15:49] <voidspace> hah
[15:49] <voidspace> wwitzel3: what's the device called?
[15:49] <voidspace> I've not heard of that
[15:49] <wwitzel3> Amazon Echo ..
[15:49] <voidspace> wwitzel3: the NSA probably did that for you for free
[15:50] <wwitzel3> if it was April .. I would of thought it was a joke
[15:50] <voidspace> http://www.amazon.com/oc/echo
[15:50] <voidspace> interesting
[15:51] <natefinch> I saw a thing about that yesterday.  It seems interesting, but don't we all have something like that in our pockets already?  I guess not with a halfway decent speaker
[15:51] <wwitzel3> see, the NSA did it wrong, all they needed to do was has a nice landing page and charge people for PRISM and it would of been a hit
[15:51] <natefinch> haha
[15:52] <natefinch> honestly, the main problem with this thing is that it's audio-only.  You now how many times I'm going to listen to it read out a wikipedia page?
[15:52] <voidspace> :-)
[15:53] <wwitzel3> natefinch: though it is probably more effective than when your friends read a wikipedia page off their phone, they always leave out the citation needed part :D
[15:53] <voidspace> axw: ping
[15:54] <natefinch> haha
[15:54] <voidspace> axw: although I really doubt you're around
[15:55] <wwitzel3> voidspace: it is like 5am saturday morning, who isn't up (still) then? ;)
[15:55] <wwitzel3> voidspace: since you are OCR today, mind looking at http://reviews.vapour.ws/r/382/
[15:56] <voidspace> ah, am I?
[15:56] <wwitzel3> voidspace:  you and fwereade I believe
[15:56] <ericsnow> sinzui, natefinch: 1.21 backups CLI removal patch: http://reviews.vapour.ws/r/383/
[15:56] <voidspace> wwitzel3: you're looking at the wrong friday I think...
[15:56] <wwitzel3> voidspace: probably
[15:56] <wwitzel3> voidspace: will you look anyway *eyebat*
[15:57] <voidspace> heh
[15:57] <ericsnow> wwitzel3: cmars and TheMue are OCR
[15:57] <voidspace> wwitzel3: seeing as I'm very unlikely to get this high priority bug completed anyway *sigh*
[15:57] <voidspace> wwitzel3: I think I know where in the code to fix it at any rate
[15:57] <natefinch> wwitzel3: you got a ship it from TheMue
[15:57] <wwitzel3> voidspace: which are you working on?
[15:57] <voidspace> wwitzel3: there's even a comment from axw predicting that there would be a problem with the code...
[15:57] <wwitzel3> natefinch: don't we still need two?
[15:57] <TheMue> yeah
[15:58] <voidspace> wwitzel3: bug #1381619
[15:58] <mup> Bug #1381619: Failed to destroy-environment when node is in commissioning or new state <cloud-installer> <oil> <juju-core:Triaged by mfoord> <MAAS:Incomplete> <https://launchpad.net/bugs/1381619>
[15:58] <natefinch> wwitzel3: no?
[15:58] <wwitzel3> oh, I was still under the impression we needed two LGTM/Ship It on reviews, ok :)
[15:59] <voidspace> wwitzel3: have you seen how RB renders that diff?
[15:59] <voidspace> ericsnow: ^^
[15:59] <natefinch> wwitzel3:  I don't think we've needed 2 LGTMs since before we hired you :)
[15:59] <voidspace> anyway LGTM *sigh*
[15:59] <voidspace> wwitzel3: couldn't you just remove registering the command, whilst leaving the rest of the code in there?
[16:00] <natefinch> ericsnow: yeah, that's what I was thinking ^
[16:00] <wwitzel3> voidspace: huh?
[16:00] <natefinch> wwitzel3: I think he keeps typing you instead of ericsnow
[16:00] <voidspace> wwitzel3: basically, only do the change in cmd/juju/main.go
[16:00] <perrito666> natefinch: when I entered whoever induced me, which I believe was mgz said that 1 for trivial changes 2 for anything importan
[16:00] <perrito666> t
[16:00] <voidspace> oh
[16:00] <wwitzel3> voidspace: what?
[16:01] <voidspace> is it ericsnow who asked for the review
[16:01] <voidspace> wwitzel3: no, you asked for a review on 383
[16:01] <wwitzel3> oops
[16:01] <wwitzel3> wrong thing
[16:01] <voidspace> wwitzel3: which removed backups
[16:01] <natefinch> haha
[16:01] <natefinch> 383 is eric's code
[16:01] <voidspace> ah, ok
[16:01] <wwitzel3> voidspace: http://reviews.vapour.ws/r/382/ sorry .. but I apparently don't need your review anyway :P
[16:01] <voidspace> ericsnow: for 383... couldn't you just remove registering the command and leave everything else in place?
[16:02] <voidspace> wwitzel3: hah ok :-)
[16:02] <ericsnow> voidspace: too easy <wink>
[16:02] <voidspace> ericsnow: :-)
[16:02] <voidspace> ericsnow: if the code is good, and it's tested, why not leave it in place
[16:03] <ericsnow> voidspace: good point; it hadn't crossed my mind
[16:07] <mattyw> fwereade, you got 30 seconds?
[16:07] <fwereade> mattyw, yeah, more or less :)
[16:10] <ericsnow> voidspace: yeah, that makes for a much simpler change :)
[16:11] <natefinch> ericsnow: +1
[16:11] <ericsnow> natefinch: could you give me a ship-it?
[16:12] <natefinch> ericsnow: done
[16:12] <ericsnow> natefinch: thanks
[16:12] <natefinch> ericsnow: just make sure all the tests still pass
[16:12] <ericsnow> natefinch: they do
[16:12] <natefinch> cool
[16:18] <voidspace> gah, virsh can't use a storage pool on another physical drive due to strange permissions problems
[16:18] <voidspace> but you can create a filesystem in a file and then mount that as if it's on the partition it wants it on
[16:18] <voidspace> and it will use that happily
[16:19] <voidspace> that took me nearly half a day to work out
[16:19] <voidspace> but now I have two maas nodes
[16:19] <voidspace> not using hard drive space on my boot disk
[16:19] <voidspace> so now I can bootstrap *and* deploy a service - to try and reproduce the bug I'm meant to be working on
[16:20] <wwitzel3> voidspace: progress :)
[16:20] <voidspace> wwitzel3: yeah, slow and painful - but definite
[16:21] <voidspace> although juju bootstrap hasn't started the node
[16:21] <voidspace> "competent-bait" is resolutely off
[16:21] <voidspace> but the power reporting works, so maas could boot the node if it wanted to
[16:22] <voidspace> status is "Deploying" but power is off
[16:22] <voidspace> INFO 0 minutes ago Node powered on
[16:22] <voidspace> no it didn't...
[16:23] <voidspace> and if I switch it on it shuts down again
[16:24] <natefinch> voidspace: it's like one of those boxes that you turn on and a hand comes out and turns itself off.
[16:25] <voidspace> natefinch: unfortunately so...
[16:25] <voidspace> "useless box"
[16:25] <voidspace> very qppropriate
[16:42] <voidspace> nope, maas changes the node state to Deploying, they start and then shutdown almost immediately
[16:43] <voidspace> the only record in the logs (libvirtd, maas and qemu) is that libvirtd kills the qemu process (shuts down the node)
[16:44] <voidspace> commisioning works fine
[16:52] <voidspace> and now it's working (after another manual kvm image start)
[16:52] <voidspace> for no fathomable reason
[16:54] <voidspace> looks like pxe booting isn't working, but manual starting is now working (didn't before)
[16:54] <voidspace> that's good enough
[17:51] <voidspace> heh, so I can't quite reproduce the bug
[17:51] <voidspace> but if I manually release a maas node and then call destroy-environment, juju hangs
[17:51] <voidspace> I don't know for how long...
[17:52] <voidspace> ah...
[17:52] <voidspace> that was releasing the bootstrap node
[17:52] <voidspace> *state server node
[17:52] <voidspace> not what I intended
[17:53] <voidspace> no it wasn't
[17:54] <voidspace> I released the right node
[19:08] <natefinch> whoever is responsible for files in Juju that are over 2000 lines long should be flogged.  (really, anything over ~500 is too much)
[19:09]  * natefinch goes to fix a test failure at line 2440 in apiserver/client/client_test.go
[19:12]  * TheMue likes the good old Smalltalk. no files and methods seldom with more than 20 lines
[19:12] <natefinch> That's one of the things I like about Go - you can subdivide into as many files as you want. They're all effectively just cat'ed together by the compiler
[19:13] <natefinch> (per package)
[19:13] <TheMue> natefinch: yes, no need to put everything in one file
[19:14] <TheMue> natefinch: but otherwise, one file per unit of code and a rule of few lines leads to small units (classes, packages, modules, etc)
[19:14] <natefinch> yep
[19:15] <natefinch> big files aren't the end of the world, honestly, it's just a little annoying having to page through them in diffs and in the editor.  Big functions are the really killer... we have some 200 line functions in Juju that I've seen.  Biggest function I've seen in my career was a 1000 line behemoth, but that was a long time ago
[19:16] <TheMue> ouch, that really hurts
[19:19] <voidspace> happy weekend everyone
[19:19] <voidspace> g'night all
[19:19] <natefinch> see ya voidspace
[21:00] <natefinch> sinzui: btw, backporting https://launchpad.net/bugs/1382751 is turning out to be a big mess.  It requires porting another change, and that then requires a third change....
[21:01] <mup> Bug #1382751: non subordinate container scoped relations broken  <regression> <relations> <subordinate> <juju-core:Fix Committed by menno.smits> <juju-core 1.20:In Progress by menno.smits> <juju-core 1.21:In Progress by natefinch> <https://launchpad.net/bugs/1382751>
[21:03] <sinzui> natefinch, :(
[21:04] <sinzui> natefinch, is the chain for pain for 1.21 or both 1.21 and 1.20?
[21:05] <natefinch> sinzui: I would imagine it's possibly even more difficult for 1.20, though I haven't even looked at 1.20 yet
[21:06] <sinzui> natefinch, okay. I really appreciate you working on this. I am not sure we will release 1.20.12...well I need to work out how since 1.21 has permanently changes streams
[21:21] <natefinch> sinzui: I think I have most of what needs doing done... just running the tests now, which is always its own adventure
[21:22] <sinzui> fab
[21:40] <natefinch> sinzui: so, I have  PR for the prerequisite code that needs to go in before I can backport the fix
[21:40] <natefinch> sinzui: but it seems unwise to simply dump all this into 1.21 on Friday afternoon.  What do you think?
[21:42] <sinzui> natefinch, if I see a pass tomorrow morning, I am happy to release. A failure may mean the antipodians have a regression to fix
[21:43] <natefinch> sinzui: what i hear is "merge it and we'll see what happens" ... is that correct? :)
[21:44] <sinzui> natefinch, yes, let's be hopeful
[21:44] <natefinch> sinzui: does the merge bot work on the 1.21 branch?
[21:44] <sinzui> natefinch, if it turns out bad, we are still are ahead of delaying until our monday
[21:44] <natefinch> sinzui: yep
[21:44] <sinzui> natefinch, yep, just works
[21:44] <natefinch> ok
[21:47] <cmars> natefinch, is reviewboard spewing lots of errors for you when you try to view this diff? http://reviews.vapour.ws/r/384/diff/#
[21:47] <natefinch> typ
[21:47] <natefinch> yup
[21:47] <cmars> ericsnow, any ideas? ^^
[21:48]  * ericsnow looks
[21:48] <cmars> natefinch, ok, just wanted to confirm. i'll review in my dev env
[21:51] <natefinch> sinzui: I'll hafve to finish up the second PR with the fix in the morning, I'm out of time today. It's just merging PR 1075 into 1.21 ... I've just run out of time trying to wrestle with git and github to get it to do that
[21:51] <sinzui> natefinch, okay, Thank you for your time
[21:53] <ericsnow> cmars: looks like a classic merge conflict (as the error messages imply)
[21:53] <ericsnow> cmars: why?  I'm not immediately sure
[21:56] <ericsnow> cmars: I'm guessing something didn't line up right when Nate initially made his pull request, which caused RB trouble and it hasn't been able to get back on its feet to try again
[21:56] <cmars> ericsnow, could be the target branch is 1.21 instead of master? it doesn't look like it has a conflict
[21:57] <ericsnow> cmars: 1.21 is definitely the trigger, but the cause of the problem is unclear
[21:57] <ericsnow> cmars: FYI, other 1.21 PRs have generated proper review requests without incident
[21:58] <ericsnow> cmars: I wonder if Nate used rbt to post the diff


[16:34] <jdstrand> hi!
[16:34]  * sbeattie waves
[16:34] <jdstrand> #startmeeting
[16:34] <meetingology> Meeting started Mon Aug 19 16:34:32 2013 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:34] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:34] <jdstrand> The meeting agenda can be found at:
[16:34] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:34] <jdstrand> [TOPIC] Weekly stand-up report
[16:34] <jdstrand> I'll go first
[16:34] <jdstrand> I'm on community this week
[16:35] <jdstrand> I have some bug triage to finish up
[16:35] <jdstrand> I have pending updates I'm working on
[16:35] <jdstrand> I've also been bootstrapping appstore review scripts
[16:35] <jdstrand> I also hope to test/sponsor tyhick's pending apparmor/dbus upload
[16:35] <jdstrand> mdeslaur: you're up
[16:36] <mdeslaur> I'm in the happy place this week
[16:36] <mdeslaur> I start my holiday on wednesday, until the 3rd
[16:36] <mdeslaur> so I'll basically be upgrading my laptop to saucy today, and that's pretty much it
[16:36] <mdeslaur> and will possibly do some triage/research
[16:36] <mdeslaur> that's it for me, sbeattie
[16:37] <sbeattie> mdeslaur: enjoy your holiday
[16:37] <sbeattie> I'm on apparmor this week
[16:37] <sbeattie> I'm focused on writing additional testcases for the regression tests, in particular IPC.
[16:38] <sbeattie> ... which is pretty much it for me.
[16:38] <sbeattie> tyhicks: you're up
[16:40] <sbeattie> oh wait, tyhicks is off today.
[16:40] <sbeattie> sarnold: I think you're up.
[16:41] <sarnold> I'm on triage this week, working on an embargoed update, and doing MIR audits
[16:42] <sarnold> I'm also playing with different published kernels to try to find one that does kvm / qemu / libvirt without any problems. some kernels run VMs fine but I'm having trouble creating VMs, which is a big necssary for the update I'm working on..
[16:43] <jdstrand> erf
[16:43] <sarnold> yeah. I kinda wish I had a precise machine around for this kind of stuff. :)
[16:44] <sarnold> oh well :) chrisccoulson, you're up :)
[16:44] <jdstrand> I don't see why a kernel would fail on creating a vm vs running it
[16:44] <chrisccoulson> hi :)
[16:44] <jdstrand> (well, unless running it causes problems, like 3.10 with vmvga)
[16:44] <sarnold> jdstrand: no, me neither, it might also be libvirt's fault.. :)
[16:44] <chrisccoulson> this week, i'm mostly working on a messaging API for oxide (to allow content scripts to pass messages to the application), so that i can finally start adding some proper tests
[16:45] <chrisccoulson> last week was quite a productive week :)
[16:46] <chrisccoulson> there's also a firefox 23.0.1 (which is already released actually). it's not a security driven update and from looking at the bug list, i'm not convinced it's worth spending time on to update
[16:47] <chrisccoulson> i think that's me done
[16:48] <jdstrand> [TOPIC] Highlighted packages
[16:48] <jdstrand> he Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so.
[16:48] <jdstrand> See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.
[16:49] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/open-vm-tools.html
[16:49] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/hawtjni.html
[16:49] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/mplayer.html
[16:49] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/elinks.html
[16:49] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/gollem.html
[16:49] <jdstrand> [TOPIC] Miscellaneous and Questions
[16:49] <jdstrand> Does anyone have any other questions or items to discuss?
[16:51] <jdstrand> mdeslaur, sbeattie, sarnold, chrisccoulson: thanks!
[16:51] <jdstrand> #endmeeting
[16:51] <meetingology> Meeting ended Mon Aug 19 16:51:24 2013 UTC.
[16:51] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-08-19-16.34.moin.txt
[16:51] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-08-19-16.34.html
[16:51] <sarnold> thanks jdstrand :)
[16:51] <sbeattie> jdstrand: thanks!
[16:51] <mdeslaur> thanks jdstrand!
[19:59] <kees> \o
[19:59]  * pitti waves hello
[19:59] <kees> heya
[20:00] <pitti> cjwatson is on holidays
[20:00] <pitti> soren sent apols
[20:00] <pitti> hm, no mdz either
[20:00] <pitti> stgraber: est-ce que tu es ici ?
[20:03]  * stgraber waves
[20:03] <stgraber> pitti: oui
[20:06]  * pitti currently reads the openvswitch SRU request
[20:06] <pitti> that seems to be the only agenda item today?
[20:07] <stgraber> yeah, there's also kees who gave an updated list of MRE but I think I'd want more time to look at those or have the number of bugs and number of uploads that caused regressions before I can decide whether to turn some of those into full MREs
[20:08] <pitti> yeah, me too; the preliminary report doesn't yet have the information about how well these went
[20:09] <stgraber> for openvswitch, I think I'm happy with a provisional MRE for now, in line with what openstack has already
[20:09] <kees> stgraber: I've almost got the error report counts...
[20:10] <kees> although since they're all zero, I don't trust it.
[20:11] <stgraber> openvswitch has been SRUed multiple times in the past but never to get a full upstream version (that I can see), so a provisional MRE seems appropriate
[20:11] <stgraber> if all goes well and the next few uploads based on an upstream point release look good, I'd be happy to turn it into a full MRE
[20:11] <pitti> the upstream test suite looks quite fine, but the autopkgtest is timing out
[20:12] <pitti> but in general I agree
[20:12] <stgraber> well, autopkgtest isn't terribly useful for an LTS anyway
[20:12] <pitti> well, for the next one it will be :)
[20:12] <stgraber> (I was meaning to point that out as a reply to the original e-mail but didn't get to it)
[20:12] <stgraber> only if someone looks at the results
[20:13] <stgraber> publishing from -proposed to -updates is manual for stable releases so autopkgtest won't prevent the package from reaching the users
[20:13] <pitti> well, I assume we'll keep the britney gatewaying for SRUs?
[20:13] <stgraber> not that I know of. britney is meant to gateway the dev release, not stable releases
[20:14] <pitti> ah, ok; so I guess that should become part of the SRU report
[20:14] <stgraber> yep, that'd be good
[20:15] <stgraber> we certainly could run britney on stable and have it consider everything as "blocked" so that it needs an hint to get copied over to -updates (that way we'd still benefit from the rest of the checks) but I don't think we have any plan to actually do this, so I wouldn't count on it
[20:16] <pitti> stgraber: I think it's enough if http://people.canonical.com/~ubuntu-archive/pending-sru.html points out test regressions
[20:16] <pitti> no need to make the copying tools more complicated
[20:16] <stgraber> yep, I can certainly agree with that :)
[20:17] <pitti> kees: any reservations against an openvswitch provisional MRE?
[20:17] <kees> pitti: seems fine to me.
[20:17] <kees> so, in doing the error review of the existing pMREs, it seems there are no servers reporting crashes. :)
[20:18] <stgraber> kees: that'd make sense, whoopsie doesn't report anything on those IIRC :)
[20:18] <kees> right :(
[20:18] <pitti> yeah, we don't exactly make it easy to do that
[20:18] <pitti> it's much easier in saucy now, but I doubt that many server admins would want to enable that
[20:18] <kees> because the whole glance, horizon, etc stack shows 0 errors, and libreoffice .... not so much
[20:18] <kees>     libreoffice, quantal updates: 1
[20:18] <kees>         2012-11-19 1:3.6.2~rc2-0ubuntu4
[20:18] <kees>             error report count: 40
[20:19] <kees> I'll have to report both error count and bugs-in-specific-version.
[20:23] <kees> anyway, I'll continue working on the report.
[20:23] <pitti> kees: thanks
[20:23] <pitti> so it seems we are done?
[20:23] <kees> yeah
[20:24]  * pitti responds to MRE request mail
[20:25] <kees> thanks!
[20:27] <stgraber> thanks pitti
[20:29] <pitti> done, and ttps://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions updated
[20:29] <pitti> good night


[00:35] <lsd|2> Polish King in Munchien https://www.youtube.com/watch?v=fIxlfNDwzBM
[01:04] <MockingMoniker> So, I have a PPA I added and I get an unmet dependency when trying to install a pakcage from it... I found out that in order to fix it I need to refer to the exact package name with version info, and not let apt figure it out... how do I figure out the exact package name?
[01:04] <MockingMoniker> I know that apt-cache search finds a description (but I don't see anything else).
[01:15] <Bashing-om> MockingMoniker: ' dpkg -l <package_name> ' might be one way forward.
[01:21] <MockingMoniker> Is it possible to make sure apt/dpkg ignore all packages of a pattern for one repository and add only those of a perferred repo? I have a PPA with packages that I want to install but there are some packages with the same name on my system.
[01:22] <Bashing-om> !pin | MockingMoniker
[01:22] <arraybolt3> Maybe look into apt pinning?
[01:22] <MockingMoniker> basically if I install kodi-* then all the Ubuntu repos are entirely eignored but all the onse for the Kodi team's PPA are only pulled.
[01:22] <MockingMoniker> OK, looking into it.
[01:22] <arraybolt3> Bashing-om: Heh, I missed by one second.
[01:23] <ax562> good evening.  Is there nvidia drivers support for ubuntu 22.04 lts with wayland/low-latency-kernel?
[01:23] <Bashing-om> MockingMoniker: Versoning control - apt will always look at the latest verson numbers.
[01:23] <ax562> or just Wayland?
[01:24] <Bashing-om> ax562: So far as I know - nvidia/Wayland support is spotty at best.
[01:25] <Bashing-om> ax562: If you recall - Nvidia required that we pull Wayland support from their proprietary driver :(
[01:26] <ax562> ah ok, I was getting conflicting info from my search.  What would be the way to go if one would try to take the plunge on trying to get it working? site or tutorial?
[01:27] <ax562> Bashing-om been on the Deb/Bullseye trains for a minute so I have not kept my ear too open on Ubuntu news.  I had not heard about Nvidia pulling Wayland support from drivers.
[01:28] <ravage> ax562: install linux-image-lowlatency and install the nvidia driver via "additional drivers" in gnome or use "ubuntu-drivers" on the terminal
[01:29] <ax562> ravage thanks, I will try and report back.  I'm already using the low latency linux kernel.  I'll report findings shortly.
[01:42] <ax562> ravage the little gear on the login screen is not visible to change the option from gnome-X to gnome(wayland) after nvidia-driver install.
[01:42] <ax562> I did modify the gnome cofig file to "WAYLAND=true".
[01:44] <ax562> as Bashing-om mentioned, I do not think it's possible :(
[01:45] <MockingMoniker> So, I'm trying to tell Ubuntu to not use a repo for a package glob (kodi*) and I added a file to /etc/apt/preferences.d with line 1: Package: kodi*; line 21: Pin: release n=jammy; Line 3: Pin_priority: -1; but apt policy kodi shows the default priority.
[01:47] <ravage> ax562: WAYLAND=true sounds wrong: https://linuxconfig.org/how-to-enable-disable-wayland-on-ubuntu-20-04-desktop
[01:49] <ax562> ravage that is the exact site I used.  Please excuse the syntax err, I'm using 2 different machines
[01:49] <ravage> MockingMoniker: dont clutter your system with PPAs. they offer a flatpak. just use that for kodi
[01:51] <ravage> ax562: thats the only place i know of that would disable that. but maybe there is another. but im almost certain you would not be very happy with wayland+nvidia
[01:51] <ravage> i tried switching a few times. never got everything working that i need
[01:52] <MockingMoniker> Still, how do I prevent my system from installing packages from the Ubuntu repos with pattern kodi*?
[02:13] <lenswipe> Hey folks, I have a Dell laptop with an ipu6 camera and have followed the directions here: https://wiki.ubuntu.com/Dell to get the camera up and working
[02:13] <lenswipe> however, after a reboot that seems to no longer be the case
[02:13] <lenswipe> the camera _is_working (sort of) in that cheese can detect two ipu6 cameras. But they are no longer available to zoom or OBS etc.
[02:14] <arraybolt3> How do you have Zoom and OBS installed?
[02:14] <lenswipe> from the snap store I think
[02:15] <lenswipe> wait, no
[02:15] <arraybolt3> Hmm, do they have permission to access the camera? Check the Snap permissions.
[02:15] <lenswipe> arraybolt3, i'll look into it but again..this _was_ working
[02:15] <lenswipe> i was screwing around with v4l2loopback before it broke so that may be why
[02:15] <lenswipe> but I wasn't aware that changes to that persisted through reboots and...I wouldn't think that would break it, surely?
[02:16] <arraybolt3> v4l2loopback uses a kernel driver as part of its magic, so... yeah, that may persist through reboots.
[02:16] <MockingMoniker> ravage: that does give me a lot more peace of mind. Now I know I'm keeping my packages sorted.
[02:16] <lenswipe> so, zoom was installed using the .deb from their website - OBS meanwhile did indeed come from the snap store
[02:16] <ax562> couldn't get Wayland working.  Decided to just stay on X.  Thanks for all the help ravage Bashing-om
[02:17] <lenswipe> arraybolt3, right, i wonder if I've broken something with that - v4l-ctl --list-devices does show 4 devices -  /dev/video2, /dev/media0 which are apparently both "ipu6" and two v4l2lo0 and v4l2lo1 devices as /dev/video0 and /dev/video1 respectively
[02:18] <arraybolt3> I see this in that Wiki page you linked: "Ubuntu 22.04 includes gstreamer1.0-pipewire plugin to replace v4l2 gstreamer plugin." I wonder if having v4l2 stuff installed along with is making things get confused?
[02:18] <lenswipe> arraybolt3, i don't know
[02:18] <lenswipe> i didn't install v4l2 afaik
[02:18] <arraybolt3> But you did install v4l2loopback.
[02:18] <lenswipe> I did?
[02:19] <arraybolt3> 20:15:24         lenswipe | i was screwing around with v4l2loopback before it broke so that may be why
[02:19] <lenswipe> right
[02:19] <lenswipe> i don't remember installing that though
[02:19] <lenswipe> maybe OBS brings it in?
[02:19] <arraybolt3> Doubtful, unless the OBS Snap is unconfined.
[02:19] <lenswipe> hmm
[02:19] <lenswipe> it's possible I installed it, i dont remember
[02:19] <arraybolt3> (If an unconfined Snap can install a kernel module, that would be a total defeat of the Snap security model.)
[02:19] <lenswipe> either way - what's the best way to fix this?
[02:20] <lenswipe> just uninstall v4l2?
[02:20] <lenswipe> and/or v4l2loopback
[02:20] <arraybolt3> I don't know. What does "sudo apt remove v4l2loopback" say it's going to uninstall?
[02:20] <lenswipe> E: Unable to locate package v4l2loopback
[02:20] <arraybolt3> Er... ok one moment.
[02:21] <arraybolt3> sudo apt remove v4l2loopback-dkms
[02:21] <arraybolt3> (I don't really know how to fix this, this is just me taking shots in the dark based on the info I have, so I'm sorry in advance if this doesn't work.)
[02:21] <lenswipe> ah!
[02:21] <lenswipe> Package 'v4l2loopback-dkms' is not installed, so not removed
[02:22] <arraybolt3> Hmm. That's odd.
[02:22] <lenswipe> indeed
[02:22] <lenswipe> I mean, this _was_ working even with v4l2loopback installed (or not, as the case may be)
[02:23] <arraybolt3> Did you happen to change anything related to Secure Boot?
[02:23] <lenswipe> uhhh, not afaik - I mean - I'm using secure boot but otherwise no
[02:24] <wr> what would i use to install a deb file on ubuntu 22.10?
[02:24] <arraybolt3> OK that *might* be a clue, one moment...
[02:24] <lenswipe> arraybolt3, my recollection of events was that i had a working clean ubuntu install, so I copied over my entire home dir from my old machine...after which my webcam no longer worked
[02:24] <lenswipe> which makes absolutely no sense
[02:24] <arraybolt3> wr: "sudo apt install ./filename.deb" from within the folder containing the .deb file
[02:25] <arraybolt3> lenswipe: What does "ls /var/lib/shim-signed/mok" show? I only need to know if there are files in there or not, do **NOT** share the contents of the files in there.
[02:25] <lenswipe> arraybolt3, yeah of course lol
[02:25] <lenswipe> yeah, there's files in there - MOK.der  MOK.priv
[02:26] <arraybolt3> Hmm. Well then it's not likely to be Secure Boot's fault...
[02:26] <arraybolt3> Is there anything related to Zoom or OBS in the hidden files within your home folder?
[02:26] <lenswipe> indeed
[02:26] <lenswipe> uh...i guess there _could_ be..
[02:26] <lenswipe> but..
[02:27] <lenswipe> Zoom sees no camera at all
[02:27] <lenswipe> OBS also sees no camera
[02:27] <arraybolt3> Also try making a new user account and see if anything can see the camera from there.
[02:27] <lenswipe> Cheese sees two cameras both called ipu6. But I'm not setting a lot of store by that because cheese is broken in the latest release afaik
[02:27] <lenswipe> yeah, was thinking of doing that
[02:27] <lenswipe> will try it and get back to you
[02:27] <arraybolt3> If it works in a clean user account, then it is the fault of something you copied over.
[02:27] <lenswipe> yeah
[02:27] <lenswipe> but like - that'd be pretty nuts
[02:27] <arraybolt3> (Or at least it's very likely to be.)
[02:28] <lenswipe> home dir stuff shouldn't break hardware like that
[02:28] <arraybolt3> lenswipe: I wouldn't be surprised if something was cached that caused the problem.
[02:28] <lenswipe> webcamtests.com can't even see it
[02:31] <arraybolt3> lenswipe: Also is Webcamoid able to see it?
[02:31] <arraybolt3> That's the camera software I have.
[02:32] <lenswipe> arraybolt3, okay, just swithced to a new user account - doesn't work there either
[02:32] <arraybolt3> :(
[02:32] <lenswipe> lets' try webcamoid
[02:32] <lenswipe> I'm not hopeful
[02:34] <lenswipe> yeah, webcamoid is a bust too
[02:34] <lenswipe> it's trying to use /dev/video0 and failing
[02:36] <MockingMoniker> I installed Kodi from flatpak and it won't respond to keyboard or mouse.
[02:36] <arraybolt3> lenswipe: And you already did the "Workaround to make Cheese useable by disable v4l2 in pipewire" thing?
[02:37] <lenswipe> arraybolt3, I think so, but honestly I don't care about cheese all that much
[02:37] <arraybolt3> Just check and make sure that line is still commented out, if things are trying to use v4l2 devices still that might be the problem.
[02:37] <lenswipe> oh this is interesting
[02:38] <lenswipe> cheese is no longer finding _any_ device
[02:38] <lenswipe> even ipu6
[02:40] <lenswipe> arraybolt3, looks like that was uncommentd
[02:40] <lenswipe> what do i restart for that to take effect?
[02:40] <lenswipe> pipewire?
[02:40] <arraybolt3> I'd reboot entirely.
[02:40] <lenswipe> k
[02:40] <lenswipe> brb
[02:41] <arraybolt3> !root | Guest8617
[02:41] <arraybolt3> Er.. ok that was the wrong factoid...
[02:41] <arraybolt3> What is the factoid for "don't use IRC on the root account?"
[02:42] <arraybolt3> !rootirc | Guest8617
[02:43] <lenswipe> arraybolt3, okay so now cheese still doesn't work, but zoom can see v4l2lo0 and v4l2l1
[02:44] <Guest8617> hello
[02:44]  * arraybolt3 throws up my hands
[02:44] <lenswipe> arraybolt3, it looks like v4l2l0 is the output of the OBS virtual camera
[02:44] <arraybolt3> lenswipe: You have the Frankencamera. Good luck, I have no clue what to do at this point.
[02:45] <lenswipe> arraybolt3, quite.
[02:45] <arraybolt3> (If someone else has any ideas, please insert them, I'm stumped.)
[02:45] <lenswipe> well thanks anyway
[02:45] <lenswipe> arraybolt3, current options on the table are "send this ****ing dell laptop back and get a thinkpad"
[02:46] <lenswipe> I've been at this for like a week now
[02:46] <lenswipe> I don't care about facial recogntion login, fingerprint scanenrs or all sorts of other bullshit dell built into this thing - i just want a decent laptop to get work done
[02:49] <MockingMoniker> Flatpak Kodi expects an X server, it seems, so without an X server, the mouse and keyboard won't work.
[02:55] <ravage> MockingMoniker: then check out the kodi kiosk snap. it comed with its own wayland server for headless/iot systems
[02:55] <ravage> https://snapcraft.io/mir-kiosk-kodi
[02:56] <ravage> check description for more information
[02:59] <lenswipe> okay, i figured out what i did yesterday
[02:59] <lenswipe> arraybolt3, I followed this: https://www.scs.stanford.edu/%7Edm/blog/hide-webcam.html
[02:59] <lenswipe> I've gone through and undone those changes, now I'm going to reboot
[02:59] <lenswipe> brb
[03:02] <lenswipe> okay
[03:02] <lenswipe> so
[03:02] <lenswipe> I now have "Dummy video device" listed in zoom...
[03:02] <lenswipe> cheese isn't much better
[03:20] <lenswipe> arraybolt3, any ideas?
[04:30] <weeb11> I used ubuntu many years ago does it still crash like it used to? I haven't used linux in a very very long time
[04:31] <arraybolt3> It's rock solid for me over here.
[04:31] <weeb11> now I use ghost spectre's custom mod of windows 11 and startall back for taskbar
[04:31] <weeb11> nice to hear
[04:31] <arraybolt3> I use various flavors of Ubuntu on all of my computers, and I have quite a few computers.
[04:31] <weeb11> how's the gpu support these days
[04:31] <arraybolt3> Quite good in my experience.
[04:32] <weeb11> does it sometimes still break or nah
[04:32] <arraybolt3> I'm using an NVIDIA 1050 Ti in one of my desktops, works perfectly.
[04:32] <arraybolt3> I've seen some people break it in the past, but it doesn't seem to just randomly break for me.
[04:32] <weeb11> hmm improved : D
[04:33] <weeb11> want's your favorite flavor?
[04:33] <arraybolt3> Depends on the power of the computer I'm using and the use case I have in mind.
[04:33] <arraybolt3> Right now I'm using Kubuntu on my primary laptop, and Lubuntu on my primary desktop.
[04:34] <weeb11> full or kde?
[04:34] <arraybolt3> I like Xubuntu too though, and have used Ubuntu Studio in the past and have it installed on one of my best friend's laptop.
[04:34] <arraybolt3> weeb11: Kubuntu uses KDE if that's what you mean.
[04:34] <weeb11> ahh
[04:34] <weeb11> any fun with arch?
[04:35] <arraybolt3> ...define fun. :P
[04:35] <arraybolt3> Let's just say Arch was a painful nightmare the first time. I still have an Arch installation in a VM, but it's definitely not something I'd want to use on my primary system.
[04:35] <weeb11> true
[04:35] <weeb11> alot of custom mod on that os
[04:35] <weeb11> nice displays
[04:36] <arraybolt3> Quite customizable but you pay for that power hand over fist. At any rate, this is a fun discussion, but it would probably fit better in #ubuntu-discuss. I'd be happy to move there with you if you'd like.
[04:36] <weeb11> : D
[04:36] <weeb11> it's ok, it's 11 I'm just winding down for the night
[04:36] <weeb11> see you later it was fun /
[04:37] <arraybolt3> Thanks!
[04:37] <weeb11> : D
[04:37] <Umeaboy> Hi! Does anyone here have trouble receiving Launchpad emails to download a po file? I made a bugreport about it and it still happens.
[04:37] <arraybolt3> Umeaboy: What are you trying to do? I don't know what a po file is.
[04:38] <Umeaboy> arraybolt3: A po file contains translations for each program.
[04:38] <arraybolt3> Oh, right.
[04:38] <arraybolt3> (It sounded a bit familiar but now I remember.)
[04:38] <Umeaboy> Launchpad is the platform to either translate directly in the web ui or it offers to download the file.
[04:38] <Umeaboy> This hasn't been a problem before.
[04:39] <Umeaboy> https://bugs.launchpad.net/launchpad/+bug/1996436
[04:39] -ubottu:#ubuntu- Launchpad bug 1996436 in Launchpad itself "launchpad does not send any email with link to po file" [Undecided, New]
[04:39] <Umeaboy> I have mentioned it in #launchpad, but no help there.
[04:39] <arraybolt3> Hmm. You might ask in #launchpad. I use Launchpad a lot, but haven't used the translation feature before.
[04:40] <Umeaboy> Can  you try to reproduce the issue just to see if you get an email??
[04:40] <arraybolt3> Sure.
[04:41] <Umeaboy> It should arrive within 5-10 minutes.
[04:42] <arraybolt3> Umeaboy: OK, I requested the translations for the Spanish version of GNOME Software (I think), we'll see what happens.
[04:42] <Umeaboy> I haven't broken any of the guidelines so I'm fairly sure that my email is not banned/blocked.
[04:43] <arraybolt3> Did you check your spam by any chance
[04:43] <Umeaboy> Yes.
[04:43] <Umeaboy> Empty.
[04:44] <arraybolt3> I'm still waiting for any email to come through, for what it's worth.
[04:45] <Umeaboy> I use Tutanota to read my emails if that's relevant.
[04:45] <arraybolt3> I'm on GMail so that means we'll have two mail platforms checked.
[04:46] <Umeaboy> Yeah.
[04:48] <arraybolt3> Still nothing for me.
[04:51] <Umeaboy> This makes it valid for you to click "This affects me to"
[04:51] <arraybolt3> True. I'm waiting just a bit longer.
[04:51] <arraybolt3> But yeah it looks like this is indeed a bug. And I know for a fact I'm not banned or anything.
[04:52] <jeffrey_f> is it possible to move an active process to my GPU?
[04:56] <Umeaboy> jeffrey_f: I would say YES, but I don't know how to do that. I found some info on how to shift from GPU to CPU: https://unix.stackexchange.com/questions/591393/how-to-shift-process-from-gpu-to-cpu-usage
[04:56] <arraybolt3> Umeaboy: Yeah, I still haven't gotten an email. I'm going to say yes this is a bug and throw some support behind it.
[04:57] <jeffrey_f> @Umeaboy, I found that too.  I guess I need a bigger shovel to dig more.  Thanks
[04:59] <Umeaboy> jeffrey_f: If I were you I'd try to find support from the GPU maker here on IRC somehow.
[04:59] <Umeaboy> I don't know if it's a kernel question or something else.
[05:00] <jeffrey_f> @Umeaboy, That should be rather easy to do.  NVidia is generally active in forums and such.  Again, Thanks
[05:00] <Umeaboy> jeffrey_f: https://netsplit.de/channels/?chat=nvidia
[05:01] <Umeaboy> I don't know how up-to-date that list is though.
[05:02] <jeffrey_f> Thanks @Umeaboy
[05:04] <Umeaboy> Anytime, jeffrey_f. We're all family here even though it's not by blood. :)
[05:04] <jeffrey_f> @Umeaboy, Truth!
[05:37] <misterx8> anyone knows any good tweaks for linux performance?
[05:38] <toddc> run headless
[05:38] <misterx8> whats headless
[05:39] <toddc> no gui/screen
[05:39] <toddc> command line only
[05:40] <toddc> xubuntu is faster too
[05:40] <misterx8> lol thats besides the point
[05:40] <arraybolt3> Lubuntu is also a possible option, it's also light, like Xubuntu.
[05:40] <misterx8> nah i mean regardless of distro anything to make it run faster i already have a setup but asking around to see what more i can add
[05:41] <arraybolt3> Maybe disable the swapfile and enable RAM compression?
[05:41] <NickH> If you want a fast GUI then consider using a light weight wayland compositor
[05:41] <toddc> misterx8: I am headless only
[05:41] <misterx8> better ill send my config and you guys check it out to see what ive missed any potential setting...
[05:41] <misterx8> https://github.com/thanasxda/basic-linux-setup/blob/master/init.sh
[05:42] <misterx8> nickh ur right. im on it already. i cant wait till kde gets vulkan compositor
[05:43] <arraybolt3> misterx8: YOU DID mitigations=off???!!!??!?!??? I know that's sometimes seen as a performance enhancer, but that is a shockingly horribly terrifyingly no good very bad idea.
[05:43] <misterx8> run windows t hen lol
[05:43] <arraybolt3> Unless you don't care if the first malicious site you open is able to read everything in your system's RAM, that is.
[05:44] <misterx8> nah i dont. this setup is personal. besides the point. i get half hackbench latency with just this script. without considering mitigations
[05:44] <misterx8> check it out and tell me what i can add. i want to finish this once n for all add anything possible
[05:44] <arraybolt3> Eh, well then OK.
[05:45] <misterx8> thats why i added switches like those variables for people to edit it easily cause i run stuff my way
[05:45] <arraybolt3> Hmm, I see zram already in there.
[05:46] <misterx8> just for low spec
[05:46] <misterx8> zswap for 2gb and zram + zswap for 1 gb
[05:46] <misterx8> im not exactly a professional so i hope you mind my scripting skills lol
[05:47] <misterx8> dont mind i mean
[05:51] <arraybolt3> misterx8: Heh, I like the system-level adblocking.
[05:51] <misterx8> thanks bro
[05:52] <misterx8> its just an attempt to automate all. it was a bad script at first but my rig broke and it was easy improving performance last 2 weeks cause its barely noticable on a good system so im working at it daily lately to finish it once and for all
[05:53] <misterx8> theres so much you can do with linux and trying to see wahts worth putting in so asking around
[07:16] <kattupoochi> does https://github.com/FreeRDP/FreeRDP/ is a client tool, or they provide RDP/vps in open source (free of cost)
[07:28] <alkisg> kattupoochi: it's a tool. They're not offering free servers.
[07:30] <kattupoochi> thank u alkisg:
[09:33] <kristian_> Helloo.. I have a multi os setup (ubuntu & windows) and I'd like to do a fresh install of ubuntu. I remember last time I updated ubuntu I messed up my multi os setup because it forgot that windows existed. What's the best way to tackle this?
[09:34] <oerheks> sudo fdisk -l # shows partitions, note them down so you will not make a mistake, also the installer gives an option to update/replace an existing ubuntu install,have fun!
[09:35] <alocer> Hello all! There is a script name oem-config-remaster in ubiquity package. i was wondering if its okay to use it? is anyone using it? any alternatives? Thanks.
[09:35] <kristian_> oerheks: thanks - replace is what I want. That should work then too?
[09:36] <oerheks> kristian_, sure, it is tested and proven to be working correctly
[09:36] <EriC^^> kristian_: no, there used to be a bug that replace
[09:36] <EriC^^> would overwrite the whole disk with only ubuntu, at least back in 14.04 it happened with me
[09:36] <kristian_> EriC^^: hmm that scare me a bit :D
[09:37] <oerheks> err... ages ago ?
[09:37] <oerheks> did you file a bugreport, EriC^^ ?
[09:38] <EriC^^> oerheks: i didnt even use ubuntu then or linux
[09:38] <oerheks> alocer, ' Remaster a CD with additional oem-config functionality' ,... never used it myself
[09:38] <EriC^^> kristian_: you could remove the ubuntu partitions using gparted, then when you run the installer it should show the usual 'install alongside windows' and choose that
[09:39] <alocer> oerheks, Yes, I am thinking about wether i should investigate modifying it or not, its goes back to 2011.
[09:40] <EriC^^> oerheks: seems it was put by someone anyways #1265192
[09:40] <EriC^^> !bug 1265192
[09:40] -ubottu:#ubuntu- Bug 1265192 in ubiquity (Ubuntu Trusty) "Install/reinstall wipes out all/other partitions" [Critical, Fix Released] https://launchpad.net/bugs/1265192
[09:45] <rebab> Is there a software that I can grab Google links for a specific word in a unique way?
[10:00] <mar77i> good ugt morning! hey, I was interested, is there some plan for the future of python- and python3- packages in ubuntu?
[10:00] <mar77i> like, is python3-* going to be renamed to the other once 2.x is dropped?
[10:11] <rebab> I figured out, don't answer my question.
[10:18] <oerheks> python2.7 has already been dropped, mar77i .. not installed standard anymore
[10:18] <oerheks> !python
[10:23] <Unit193> ...Huh, I thought it was sorta dropped from the archive, but seems not.  Now that I looked at that, I do remember it lingering...
[10:25] <oerheks> it is installable, but we do recommend updating scripts/apps to 3.x
[10:55] <mar77i> oerheks: that... I knew already. thanks for attempting, anyway :)
[11:25] <Vuurdraak> -hi everybody, i am about to remove a Geforce GPU and install a Radeon RX 6600, I just read in a forum post that it won't automaticly work properly with the 5.4 kernel, and somebody said it was fixed by using a 5.13 kernel, I am wondering it's not possible to get a Radeon GPU working by installing drivers like with the Geforce card, the kernel must support the AMD GPU ?
[11:26] <oerheks> Vuurdraak, what ubuntu version?
[11:26] <Vuurdraak> 18.04 LTS
[11:26] <oerheks> for focal, install hwe to get 5.15 ..
[11:26] <Vuurdraak> - only a kernel switch can avoid tany problems ?
[11:26] <Vuurdraak> any*
[11:27] <oerheks> oh, Radeon RX 6600, that came out after 2018 ?
[11:27] <oerheks> i would upgrade, to at least 22.04 LTS
[11:28] <Vuurdraak> - i got 22.04 as a second OS, but I also want to get it working on 18.04 as I got a lot of legacy stuff still running there
[11:29] <oerheks> you would try to install hwe on 18.04, that is supported ( for one year)
[11:29] <Vuurdraak> - seems official launch date was 2021 13 oktober
[11:29] <oerheks> !hwe
[11:29] <Vuurdraak> - oke  thanks, i guess I will install the HWE kernel later
[11:31] <Vuurdraak> - oww it's even just one bash line :)
[11:32] <Vuurdraak> - oww this is already the HWE kernel line
[11:32] <oerheks> :-(
[11:33] <oerheks> setup a VM with KVM in 22.04, to run that old software?
[11:33] <Vuurdraak> it's because of what i red here in a forum post "This was my issue. I was using kernel 5.4.0-91 and my new Radeon RX 6600 would boot to a black screen. I could get a terminal, but no desktop environment. After switching to kernel 5.13.0-22-generic, I'm flying. Thanks!"
[11:34] <Vuurdraak> - and I am now on 5.4
[11:34] <Vuurdraak> in 18.04
[11:35] <Vuurdraak> - i guess i have to be carefull, with just replacing the hardware, if I want to get stuff out of 18.04
[11:36] <Vuurdraak> - which kernel is Ubuntu 20.04 on ?
[11:37] <Vuurdraak> i mean I good do a upgrade of 18.04 to 20.4 if that fixes some stufff
[11:38] <Vuurdraak> 5.15 apperently
[11:40] <oerheks> indeed
[12:13] <mazzle> hi there. I'm trying to set up clonezilla server using the DRBL server packages and I keep failing when it tries to find my nameservers in resolv.conf. I can't directly edit that file due to ubuntu. Is there some way to trcik third party apps into reading it without messing up the resolver setup?
[12:22] <Chrissy> Hi!  In the past (ie. before 22.04.1) I was able to plug my Arduino (MKR1310) via USB and I could reach it via /dev/ttyUSB0.  This does not work anymore and I don't even see any reaction in any log, when I plug it in...
[12:23] <Chrissy> (The device still works fine under windows 10 (with the same cable on the exact same machine))
[12:25] <oerheks> Chrissy, it is caused by the brltty daemon .. https://askubuntu.com/questions/1408192/can-not-connect-arduino-ide-with-arduino-board-on-ubuntu-22-04
[12:25] <oerheks> with fix
[12:25] <oerheks> stop, disable, mask that service
[12:25] <ogra> unless you are blind and rely on it ...
[12:27] <Chrissy> Still no change. I'll reboot my machine
[12:31] <Chrissy> Still no luck. brltty removed. Machine rebooted. tail -f /var/log/kern.log shows nothing when I put that Arduino in...
[12:52] <ogra> did you disable anything in your BIOS ? there is really no reason why the kernel would not show/see the plug even if there is no physical problem
[12:53] <ogra> *event
[12:55] <oerheks> maybe an usb2/usb3 issue? usb3 = blue
[12:57] <ogra> yeah, that would be such a BIOS setting ... (legacy USB support on USB3)
[12:58] <lotuspsychje> or bad usb cable?
[13:04] <gebbione> is it possible to get cifs-utils 6.14 in bionic (ubuntu 18)? at the moment i get cifs-utils/bionic-updates,bionic-security,now 2:6.8-1ubuntu1.2 amd64
[13:05] <Chrissy> The strange thing is : It works on the same device with the same cable just when I boot Windows.  (And it worked before the update to 22.04)
[13:06] <oerheks> gebbione, no, upgrade to 22.04 ?
[13:37] <BluesKaj> Hi all
[14:11] <ELFrederich> Does gnome itself run as a snap package?  When I do "sudo snap list" I see gnome listed there.
[14:38] <oerheks> ELFrederich, one part is..
[14:46] <ELFrederich> oerheks, ?
[14:47] <ELFrederich> I'm just wondering if theses are leftover from when I had some snap packages installed.
[14:47] <ELFrederich> https://bpa.st/OSQA
[15:10] <robertparkerx> I used curl -sL https://deb.nodesource.com/setup_13.x | sudo bash - to install node 13 but it installed node 10
[15:10] <robertparkerx> how do I remove this?
[15:41] <co0n> Hi, I am having trouble using my Dockerfile with Ubuntu Jammy. While installing Python packages using pip, and using the `--prefix` attribute to install somewhere else, jammy produces a `./local` subdirectory where focal does not, see: https://paste.debian.net/1260680/ Also, packages are installed into dist-packages with jammy, they were installed to site-packages with focal.
[15:41] <robertparkerx> I have node 10 installed from apt get install nodejs npm but I need version 13 of node
[15:41] <robertparkerx> how do I install it
[15:42] <co0n> robertparkerx, nodejs provides upstream repositories you can use
[15:42] <ogra> robertparkerx, see "snap info node" ... pick the channel for the 13 stable version
[15:42] <ogra> (see "snap help install" for how to give a channel to the install command, node works with cannicl to provide all their versions as snaps)
[15:43] <robertparkerx> ogra how do I do that?
[15:43] <ogra> *canonical
[15:43] <co0n> robertparkerx, the official install instructions are here: https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions
[15:44] <ogra> robertparkerx, moszt likely like: "snap install --channel=13/stable node" ...
[15:45] <ogra> ah, needs also --classic ... so: ""snap install --channel=13/stable node --classic"
[15:45] <ogra> (BTW: any reason why you ned such an old version ? )
[15:45] <robertparkerx> ogra I installed it but node --version still says 10
[15:46] <ogra> robertparkerx, remove the version you installed through the curl hackery
[15:46] <robertparkerx> ogra how do I do that?
[15:47] <ogra> (and *never ever* do such a thing again ... piping random curl scripts from the wenb into sud bash can easily turn your machine into a botnet client)
[15:47] <ogra> robertparkerx, read the script you downloaded and reverse each single step it did
[15:47] <ogra> i.e. go backwards through that script
[15:48] <robertparkerx> I did curl -sL https://deb.nodesource.com/setup_13.x | sudo bash -
[15:49] <ogra> right
[15:49] <robertparkerx> how do I remove that?
[15:49] <co0n> robertparkerx, `snap run node --version` already works with the correct version, doesn't it?
[15:49] <ogra> so look at that script
[15:49] <co0n> omg, I read this script years ago to be able to reverse-engineer their repo entries :P Now I remember
[15:49] <robertparkerx> ogra I don't understand
[15:50] <co0n> robertparkerx, there is a shell script at the url you provided, it did set-up nodejs and the relevant repos for you.
[15:50] <ogra> robertparkerx, well, you gave some randowm script you downloaded with curl to the "sudo bach" command to execturte it as root on your machne
[15:50] <ogra> yu need to read that script, understand what it did and do each of the steps backwards
[15:52] <ogra> robertparkerx, and the next ime you see durl and "sudo bash" in any install instructions, better run away screaming ... or write an angry email to the people that provide such super-dangerous instructiona
[15:52] <ogra> *curl
[15:52] <robertparkerx> ogra can you please help
[15:52] <robertparkerx> I don't know what I'm doing
[15:53] <ogra> just open https://deb.nodesource.com/setup_13.x in your browser to read the script
[15:53] <robertparkerx> I don't know what to look for
[15:53] <co0n> ogra, I think he really can't read shell scripts
[15:54] <ogra> hmm
[15:54]  * ogra looks
[15:54] <co0n> robertparkerx, do you know what you executed?
[15:54] <ogra> ARGH !
[15:54] <robertparkerx> No
[15:54] <ogra> this is horrid !
[15:55] <co0n> robertparkerx, what does the command `sudo dpkg -s nodejs` say?
[15:55] <co0n> robertparkerx, we are looking for the installed version
[15:56] <robertparkerx> https://i.imgur.com/r8YNTFl.png
[15:56] <co0n> robertparkerx, that's the same version as reported by `node --version`, right?
[15:56] <robertparkerx> yes
[15:57] <ogra> sudo apt purge nodejs
[15:57] <ogra> start with that command
[15:57] <co0n> ogra, wait
[15:57] <co0n> Let's remove the source first
[15:57] <ogra> i'D have done that next, but yeah, feel free to take the lead here
[15:57] <co0n> robertparkerx, do you see a file named something with node in /etc/apt/sources.list.d
[15:58] <co0n> robertparkerx, `ls /etc/apt/sources.list.d`
[15:58] <ogra> it seems to hack the sources.list file directly instead of adding a sources.list.d snippet ... oh what a mess 😕
[15:58] <co0n> fml
[15:58] <robertparkerx> co0n https://i.imgur.com/cnksBRg.png
[15:59] <co0n> robertparkerx, please run `grep node /etc/apt/sources.list`
[15:59] <robertparkerx> co0n nothing
[16:00] <co0n> robertparkerx, can you inspect that file and see what node might have added in there?
[16:00] <co0n> robertparkerx, or feel free to share it, I don't know what secrets you have hidden there...
[16:00] <ogra> looking at the script there shoudl be a line with "nodesource" in it somewhere
[16:01] <robertparkerx> ls /etc/apt/sources-list shows /etc/apt/sources.list
[16:01] <co0n> robertparkerx, yeah, you want to open that file
[16:02] <co0n> robertparkerx, use `cat <file>` to just see it.
[16:03] <robertparkerx> co0n https://kopy.io/bKzgV
[16:05] <co0n> robertparkerx, what does `apt-cache policy nodejs` say?
[16:05] <robertparkerx> co0n https://i.imgur.com/Exb1S7X.png
[16:06] <co0n> robertparkerx, you did not successfully execute the script ogra was afraid about, it seems
[16:06] <ogra> yea
[16:06] <ogra> looks like you got nodejs from some archive mirror instead and the script did not run at all
[16:07] <ogra> (which is actually good)
[16:07] <robertparkerx> How do I install the proper node version?
[16:07] <co0n> robertparkerx, still, `apt remove --purge nodejs`, please, to remove the pacakage installed via APT. Afterwards, we'll try to get your snap to work like it should.
[16:07] <ogra> so just remove the package with "sudo apt purge nodejs"
[16:08] <robertparkerx> co0n done that
[16:08] <ogra> what does "node --version" say now ?
[16:08] <robertparkerx> no such file or directory
[16:08] <co0n> robertparkerx, what does `snap run node --version` say
[16:09] <ogra> hmm, interesting
[16:09] <robertparkerx> co0n it has the version
[16:09]  * ogra wonders why it is not in PATH ... it shoudl be)
[16:09] <co0n> Maybe it detected another install and was graceful?
[16:09] <ogra> nah, snaps are greedy 🙂
[16:10]  * alkisg sees ogra talking about nodejs and wonders if he woke up in another universe...
[16:10] <ogra> on all official Ubuntu installs since 16.04 /snap/bin is in PATH
[16:10] <co0n> robertparkerx, what does `echo $PATH` return for you?
[16:11] <ogra> if it is not you can indeed add it to /etc/environment, but something is not correct with that install (though it looks ike some cloud image, perhaps the cloud provider mangled it or so)
[16:11] <robertparkerx> ./usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
[16:11] <ogra> alkisg, i have done a lot of nodejs stuff in my life 🙂 nothing to brag about in public though 🙂
[16:12] <co0n> robertparkerx, can you `ls /snip/bin` for us, or check if `node` is in there?
[16:12] <co0n> robertparkerx, /snap/bin
[16:12] <alkisg> :D
[16:12] <robertparkerx> node is in there co0n
[16:12] <ogra> i wonder if anyhing could cache the old location ?
[16:13] <ogra> robertparkerx, try logging out and back in and see if it is then found
[16:13] <co0n> robertparkerx, soo, `/snap/bin/node --version` gives you the version, but `node --version` does not?
[16:13] <robertparkerx> now it's found
[16:13] <robertparkerx> it logged back in
[16:13] <robertparkerx> node --version returns correct version
[16:13] <ogra> perfect
[16:14]  * ogra blames systemd-logind or some such thing
[16:14] <co0n> robertparkerx, try to remember to not just download and execute some script because installation instructions tell you. If you don't understand what the script is about, don't run it.
[16:16] <Guest34> hello, after reporting a bug in launchpad against "linux (ubuntu)" i now want to make state more precisly that it concerns "linux (Ubuntu Kinetic)". Is there a way to to link kinetic? "Also affects distribution/package" and "Also affects project" only offer some generic "Ubuntu" and no way to choose kinetic.
[16:18] <co0n> Guest34, this bug is filed against Linux Kinetic, does that help: https://bugs.launchpad.net/ubuntu/kinetic/+source/linux/+bug/1965882
[16:18] -ubottu:#ubuntu- Launchpad bug 1965882 in linux (Ubuntu Kinetic) "[nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker)" [High, Incomplete]
[16:19] <Guest34> to be more precise 1994126 there is no way to link it to some release.
[16:20] <ogra> bug 1994126
[16:20] -ubottu:#ubuntu- Bug 1994126 in linux (Ubuntu) "NULL pointer dereference in power_supply_get_property" [Undecided, Confirmed] https://launchpad.net/bugs/1994126
[16:21] <ogra> Guest34, i added a kinetic task, bt it is up to the kernel team to approve that as confirmed etc
[16:22] <ogra> better try asking in #ubuntu-kernel about kernel bugs ...
[16:23] <Guest34> thanks ogra, was there a way to do it for my own or is it just some special privilege you have unlocked within launchpad?
[16:23] <co0n> Might someone look at the rather weird pip install log I posted at ~ 15:40 UTC, 45 minutes ago.
[16:24] <co0n> I'm rather confused about the different layout generated by pip install --prefix in focal and jammy.
[16:24] <jhutchins> co0n: What problem are you trying to solve?
[16:25] <ogra> Guest34, i'm in the ubuntu-bugs team, that gives a few extra options (there is a "target to series" option, not sure if you can see that)
[16:25] <co0n> jhutchins, jammy generates an additional ./local directory and puts installed files in dist-packages
[16:25] <jhutchins> co0n: This is a python package you're trying to install?
[16:25] <co0n> jhutchins, focal installs directly into --prefix and puts installed files in site-packages
[16:26] <co0n> jhutchins, this is an excerpt from a dockerfile where package up some dependencies and some self-built modules.
[16:26] <Guest34> nope only "also affects project" and "Also affects distribution/package". thx anyways
[16:26] <co0n> jhutchins, But it falls apart with jammy or Python 3.10, it seems
[16:26] <co0n> jhutchins, works fine with focal and debian bullseye
[16:27] <jhutchins> co0n: If you don't get much python response here, there's always #python, although they'll just probably point back at #ubuntu's packaging.
[16:27] <ash_worksi> am I the only person who has programs randomly bleeding behind the dock?
[16:28] <ash_worksi> on 22.04
[16:28] <jhutchins> ash_worksi: Yes.
[16:28] <ash_worksi> it just happened with telegram :\
[16:28] <co0n> jhutchins, dist-packages is a Debianism, I'm afraid to annoy upstream ;)
[16:28] <ash_worksi> jhutchins: what do you think it takes to solve this problem? reinstall 22?
[16:29] <Guest34> ash_worksi nope :p  https://www.imgpaste.net/image/KL2xEa
[16:29] <jhutchins> ash_worksi: Sorry, I don't even have any intelligent questions to ask about it.
[16:31] <jhutchins> ash_worksi: Did you have this problem with the previous release?  We presume you're running the standard gnome desktop.  What is your graphics hardware configuration?
[16:31] <ogra> ash_worksi, start with "ubuntu-bug gnome-shell" and file it to launchpad ... the desktop team will probably know if others see it and if tere is a fix/workaround
[16:44] <ash_worksi> jhutchins: re: previous release, no, I was on 20.04
[16:44] <ash_worksi> ogra: will do
[19:00] <myrti> I recently upgraded to 22.04 and ever since then I have internet connection issues. The connection drops every ~20min for 5s and reestablishes itself. It just happened and this is the line I found in dmesg: deauthenticating from dc:39:6f:e0:45:97 by local choice (Reason: 2=PREV_AUTH_NOT_VALID). Does anyone know what could be causing this?
[19:05] <ForeverNoob[m]> @jhutchins: Now it definitely seems up again! \o/
[19:05] <Guest45> launchpad.net is instable https://twitter.com/launchpadstatus
[20:52] <eb_> Has anyone switched from Pop!_OS to Ubuntu, or vice versa? Wondering how they compare on a daily basis. I know they're very similar
[20:53] <oerheks> this is ubuntu support, pop os uses some repos we provide, that is all.
[20:53] <arraybolt3> eb_: Booted it a couple of times for testing. Hated it, stuck with Ubuntu. :P
[20:53] <eb_> oh wow!
[20:54] <arraybolt3> But oerheks is right, Pop!_OS is significantly different from Ubuntu. It is to Ubuntu what we are to Debian.
[20:54] <arraybolt3> At least kinda, from what I know.
[20:54] <eb_> Got it. I really enjoy both. Just having trouble deciding on which to go with, I guess
[20:55] <arraybolt3> I'm sure there's advantages to both sides. I will warn you, however, Pop recently disabled phased updates in apt, a safety feature that was recently added to Ubuntu. This gets rid of a confusing message when doing an apt upgrade, but it also essentially makes it so that if we make a fumble in Ubuntu, it may immediately break a swath of Pop!_OS machines.
[20:56] <eb_> Thank you for the heads up!
[20:56] <oerheks> i like snaps.
[20:58] <arraybolt3> oerheks: +1
[21:07] <alkisg> Pop!_OS mentions ubuntu in /etc/apt/sources.list; Ubuntu doesn't mention debian there. That's a major difference, recompiling all the packages from scratch and hosting them...
[21:13] <dillon> is anyone here?
[21:14] <MonoL> In the sound settings there's a balance slider, but what exactly does it do?
[21:14] <dillon> can anyone tell me how to remove a ppa?  I think I broke updates
[21:16] <ravage> dillon: https://itsfoss.com/ppa-purge/
[21:19] <dillon> tried it twice and got error: :sudo ppa-purge ppa: nilarimogard/webupd8
[21:19] <dillon> Updating packages lists
[21:19] <dillon> E: The repository 'https://ppa.launchpadcontent.net/nilarimogard/webupd8/ubuntu kinetic Release' does not have a Release file.
[21:19] <dillon> Warning:  apt-get update failed for some reason
[21:19] <dillon> :
[21:20] <ravage> but then you did not actually install anything from that PPA yet? or did you do an upgrade of Ubuntu before?
[22:57] <runelind> I am running ubuntu 20.04 and whenever I run apt upgrade, snapd gets stuck at upgrading at 45% - I'm not using snap currently, but I can't remove it using snap for the same reason.
[22:58] <runelind> dpkg-reconfigure -a causes the same hang.
[23:11] <Sven_vB> is there a way to watch Twitch on a Ubuntu focal netbook that is too weak for a browser? until recently, streamlink with VLC worked nicely, but no longer, due to a bug in focal's ancient version of python3-urllib3.
[23:12] <Sven_vB> sorry I mean a way with just deb packages, maybe PPAs. i.e. not pip nor AppImage.
[23:33] <Sven_vB> back again :)
[23:34] <Sven_vB> seems the official logs haven't caught up yet. did someone comment on my question while I was offline?


That's one of the things driving me crazy about LXQt. Settings for appearance are in million different kind of places. Totally crazy thing. KDE from other side, got countless number of settings in general. There is no end of setting things up in Plasma 😊 I gave up and applied back the default light theme to everything I could in LXQt and using it that way now. (re @Ac1d: Hello, I have installed the dracula theme on /usr/share/themes


[06:34] <dholbach> good morning
[17:08] <coolbhavi> cwayne, hey
[17:09] <cwayne> coolbhavi: hiya
[17:10] <coolbhavi> cwayne, could you give the link to your app on the portal? ll mark it as published if it has not been done yet
[17:10] <cwayne> coolbhavi: sure, here ya go: https://myapps.developer.ubuntu.com/dev/apps/807/
[17:12] <coolbhavi> cwayne, thanks! ll fill  in required details and mark it as published
[17:12] <cwayne> coolbhavi: thanks again for all your help!  you guys will be seeing more of me soon :P (or rather, more lenses submitted by me)
[17:12] <coolbhavi> cwayne, my pleasure! sure :-) you guys are rockstars!
[17:14] <coolbhavi> dpm, is there a problem with rendering of myapps portal recently?
[17:18] <coolbhavi> cwayne, published :-)
[17:19] <cwayne> coolbhavi: thanks!  to make up for it, submitted another lens just now too :P
[17:20] <coolbhavi> cwayne, haha link pls
[17:21] <cwayne> coolbhavi: https://myapps.developer.ubuntu.com/dev/apps/1690/
[17:23] <coolbhavi> cwayne, just had a quick look
[17:24] <cwayne> coolbhavi: just realized i'll probably need to make some changes, someone else did them for the other lens, would have to take a look at what they are, unless the quickly template was fixed
[17:25] <coolbhavi> you need to install the app in /opt/extras.ubuntu.com and change namespace of the service file to add extras prefix
[17:25] <coolbhavi> you can take a look at unity-lens-vm
[17:25] <cwayne> that sounds pretty familiar, let me take a look
[17:26]  * cwayne will have to do that for unity-lens-pypi as well
[17:26] <dpm> coolbhavi, sorry, I don't know if there is anything going on with myapps atm
[17:27] <coolbhavi> dpm, oh ok again sorry for pinging you off work :)
[17:27] <dpm> coolbhavi, you can ping me any time if I'm around :)
[17:27] <coolbhavi> :)
[17:30] <coolbhavi> cwayne, if you dont mind ll leave a comment on the portal marking it in progress
[17:30] <cwayne> coolbhavi: sounds good to me, i'm taking a look now
[17:30] <cwayne> replicating what happend with unity-lens-vm :)
[17:30] <coolbhavi> :)
[17:34]  * coolbhavi opens up a bug report against myapps
[17:36] <coolbhavi> dpm, if I am not wrong bug in myapps should be reported here right? https://launchpad.net/developer-portal
[17:42] <cwayne> coolbhavi: made some fixes, testing if it builds now :)
[17:42] <coolbhavi> cwayne, great!
[17:44] <dpm> coolbhavi, yes, that's the place to report bugs
[17:45] <coolbhavi> dpm, thanks!
[18:07] <cwayne> coolbhavi: fixed, pushed to lp:~cwayne18/ubuntu-app-reviews/unity-lens-github
[18:07] <coolbhavi> cwayne, ll have a look :)
[18:08] <cwayne> coolbhavi: thanks!  built and installed, seemed to work
[18:08] <coolbhavi> :)
[19:02] <coolbhavi> cwayne, excellent looks great!
[19:02] <coolbhavi> mailing the list now
[19:03] <cwayne> coolbhavi: hey, thanks!
[19:03] <cwayne> ill try and fix up the pypi lens tonight, but i think this one is higher priority for me, more people seem to want it :P
[19:08] <coolbhavi> cwayne, mailed now marking you in CC
[19:08] <cwayne> coolbhavi: thanks!
[19:09] <coolbhavi> cwayne, awesome work!
[19:09] <cwayne> coolbhavi: thanks! couldn't have done it without quickly + singlet, so much credit should go to mhall119 :P
[19:10] <coolbhavi> yes mhall119 is mr lens :)
[19:21] <coolbhavi> cwayne, good night!
[19:24] <cwayne> coolbhavi: you too!
[19:27] <coolbhavi> cwayne, have a wonderful day ahead!


[00:49] <alteregoa> good morning
[00:55] <alteregoa> us 15.04 working with ubuntu mate?
[06:06] <ses1984> i'm trying to install 15.04, and when i boot with "install ubuntu" or "try before installing" i get dropped at a log in screen
[06:10] <ses1984> i'm trying to install 15.04 and when i choose install ubuntu or try before installing, i get dropped at a login screen,
[06:10] <ses1984> and if i try to log in with username ubuntu password blank, then it keeps going black, then going back to a new login screen, and going black...and repeating forever
[06:11] <ses1984> once it gets into this state i can't press ctrl-alt-fx to enter another console
[06:11] <ses1984> as far as i can tell i just have to hard reboot
[06:12] <ses1984> not sure what to try next. i didn't bother to check if there were known issues with my hardware
[06:12] <ses1984> my hardware is new-ish
[06:12] <ses1984> x99 chipset and nvidia 750ti graphics
[06:13] <ses1984> if i get dumped at the login screen for the first time and do not try to log in, i can switch consoles to a text console, install irssi and here i am
[09:27] <lordievader> Good morning.
[12:50] <BluesKaj> Hiyas all
[12:51] <penguin42> hey BK
[12:52] <BluesKaj> hi penguin42
[19:21] <Volkodav> vivi
[19:29] <TheNumb> Volkodav: d
[23:27] <joao_> i everyone
[23:28] <joao_> I need a little help to understand
[23:28] <joao_> whats happening
[23:28] <joao_> So i installed teamspeak 3 and is working well
[23:28] <joao_> but in the past, when press right click, an option to open runscript sh on terminal was showed
[23:29] <joao_> Im running ubuntu 15.04
[23:29] <joao_> Sorry for my bad english
[23:29] <joao_> :s
[23:32] <joao_> Its anybody here?


[00:20] <meth> is there something like tig for bzr ?
[00:24] <treaves> If there is not, no one here would know, as no one here would know - or care - what 'big' is.
[00:24] <treaves> ^big^tig
[00:25] <poolie> http://jonas.nitro.dk/tig/
[00:25] <poolie> a curses gui
[00:25] <poolie> no, i'd recommend using the actual gui
[00:25] <poolie> qbzr/bzr explorer
[00:25] <poolie> looks useful
[00:25] <spiv> Or even the actual cli :)
[01:43] <thomi|work_> wgz: thanks!
[09:04] <mgz> morning all
[10:53] <mgz> argh, the command hooks again
[10:53] <mgz> these tests are all broken
[10:56] <mgz> ha, and fixing the test makes it fail spectacularly.
[11:59] <jelmer> mgz: :-S
[12:02] <mgz> what's the best help we have on using scenarios? I just poke around the code base looking for examples each time
[12:02] <mgz> and have no idea of the best way of doing things.
[12:02] <mgz> ...using scenarios here is probably a dodgy idea, but amusing.
[12:04] <jelmer> mgz: that's what I do too..
[12:13] <jelmer> mgz, vila: Could I persuade either of you to have a look at my lazy-regex-pickle branch?
[12:15] <mgz> ...that's actually what I was going to do before I got distracted
[12:18] <mgz> I wonder if 246 tests is too many... :)
[12:20] <jelmer> 246 tests for what ? :)
[12:21] <mgz> option help :D
[12:23] <jelmer> hmmok :)
[12:57] <CaMason> hi guys. Is there a viable way to squash commits (without a merge operation)?
[12:57] <CaMason> so for `A-B-C-D-E-F`, I'd like `A-----D----`
[12:57] <CaMason> I figure I can do the second part with 3 uncommits, followed by a commit. But I couldn't go any further back
[13:01] <CaMason> I suppose I could `bzr diff -r A..C > squashA.patch` & `bzr diff -r D..F squashB.patch`, uncommit back to A, then patch, commit, patch, commit
[13:01] <mgz> shelve works
[13:01] <mgz> avoids messing around with patches
[13:02] <CaMason> uncommit F-D, shelve, uncommit C-A, commit, unshelve, commit?
[13:03] <mgz> right.
[13:04] <CaMason> I could also re-order with shelving too
[13:04] <CaMason> great. That completley complements our Git workflow
[16:16] <mgz> jelmer: could you set aside some time this week to team up on reviewing MvG's lazy import branch?
[16:19] <jelmer> mgz: sure
[16:19] <jelmer> mgz: that reminds me, could we perhaps talk through some of the HPSS reviews?
[16:20] <mgz> sounds like a good thing to do at the same time.
[16:20] <jelmer> cool
[16:24] <mgz> I'm working from town tomorrow, so how about we say Friday, or do you think we can fit it all in the rest of today?
[16:25] <jelmer> friday works for me
[20:47] <beuno> o/
[20:47] <beuno> quick quesiton
[20:47] <beuno> how would I run a plugin's command from python?
[20:48] <beuno> I'm integration qbzr into an IDE written in python
[20:48] <beuno> and I want the context manu to bring up qbzr's commit dialog
[20:49] <mgz> do you want to yield execution to qbzr?
[20:49] <mgz> if not, use subprocess.call
[20:50] <mgz> otherwise, there are a couple of steps, but it's similar to calling a bzrlib command
[20:53] <beuno> I guess I could just subprocess it
[20:54] <mgz> you'll need to work with the qt main loop otherwise, which may or may not be an issue for you.
[20:54] <beuno> it's a QT app, but also, I ahve zero experience with QT  :)
[20:56] <mgz> ah, you're doing the qt creator integration?
[20:56] <mgz> or a different qt ide... you said written in python...
[20:58] <mgz> starting with subprocess isn't bad, but I recommend a post to the bazaar list with some details, as something more integrated may be preferable
[21:01] <beuno> different
[21:01] <beuno> ninja-idea
[21:02] <beuno> yeah, I'll get the basics with subprocess
[21:02] <beuno> and email the list
[22:00] <poolie> goofd morning, hi beuno
[22:02] <jelmer> hey poolie
[22:16] <poolie> hi there
[22:44] <lifeless> ♥ jelmer
[23:07] <jelmer> hi lifeless, what's with the question mark?
[23:12] <james_w> heh
[23:20] <poolie> haha
[23:21] <poolie> hi james
[23:24] <lifeless> jelmer: hah, surely your utf8 setup works ;)
[23:37] <jelmer> lifeless: hah, I see it now.. :)
[23:37] <jelmer> lifeless: glad you like it


[10:23] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3883 Pending binary packages (focal/slof). Successfully built (focal/libvirt, focal/qemu)
[10:43] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3883 Diff missing (focal/slof). Successfully built (focal/libvirt, focal/qemu)
[16:23] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3883 Diff missing (focal/slof). Pending binary packages (focal/libvirt). Successfully built (focal/qemu)
[16:43] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/3883 Diff missing (focal/slof). Successfully built (focal/libvirt, focal/qemu)