[00:04] -queuebot:#ubuntu-release- Unapproved: openldap (jammy-proposed/main) [2.5.16+dfsg-0ubuntu<IP_ADDRESS> => 2.5.17+dfsg-0ubuntu<IP_ADDRESS>] (i386-whitelist, ubuntu-server)
[00:47] <mfo> sudip, hey o/ it's normal to have -proposed enabled, as seen in launchpad build logs when the package is built in the -proposed pocket.   In this particular case, the issue is unrelated to the pockets (I posted some comments and addressed yours about this in the bug as well :)
[00:49] <sudip> mfo: but the builds for -proposed do not have -proposed enabled
[00:51] <mfo> sudip, hmm, if you look at the build log for weex in focal-proposed, there are several search matches for focal-proposed, including sources and packages installed.
[00:53] <mfo> it's normal config of the build chroot (it's the last sources entry in the line with `RUN: .../in-target override-sources-list`)
[17:14] -queuebot:#ubuntu-release- New binary: reprozip [amd64] (noble-proposed/none) [1.3-2] (no packageset)
[20:43] -queuebot:#ubuntu-release- Unapproved: cmake (jammy-proposed/main) [3.22.1-1ubuntu<IP_ADDRESS> => 3.22.1-1ubuntu<IP_ADDRESS>] (core, i386-whitelist)


[00:30] <gord> can someone keep an eye on Like in -offtopic please, he's not a native english speaker i think and thus spouts gibberish. can't find a !ur factoid that doesn't alias to !u to point him in the right direction. would do it myself but its rather bedtime
[07:16] <dholbach> good morning
[07:16] <bazhang> hi
[08:51] <ardchoille> Suspicious activity in #ubuntu, check the recent flood of enters and parts with the<EMAIL_ADDRESS>[08:52] <ardchoille> might keep an eye on anyone with the pool-96-244-79-253.bltmmd.fios.verizon.net host
[08:52] <ikonia> ok
[08:53] <ardchoille> They've learned to circumvent the floodbots by multiple nicks joining from the same host and then spamming and jumping to another nick.
[08:53] <ardchoille> Thanks ikonia
[12:29] <bazhang> * [dhanesh] (~dhanesh@<IP_ADDRESS>): dhanesh ban removed?
[12:30] <dhanesh> hi everybody
[12:30] <dhanesh> i came
[12:30] <dhanesh> iam free
[12:30] <bazhang> dhanesh, how are you in #ubuntu now
[12:30] <dhanesh> yes thank you
[12:30] <dhanesh> are you angry with me
[12:31] <bazhang> dhanesh, you are not unbanned from #ubuntu
[12:31] <dhanesh> why
[12:31] <bazhang> dhanesh, you were instructed to come here in 24 hours to discuss, not to change IP and re-enter
[12:32] <dhanesh> no i have reinstalled ubuntu because of srash reported
[12:32] <dhanesh>  no i have reinstalled ubuntu because of crash report.
[12:33] <bazhang> dhanesh, that has no relation to your being banned in #ubuntu
[12:33] <dhanesh> i didnt change my ip
[12:34] <bazhang> dhanesh, please exit #ubuntu until you have discussed the ban
[12:34] <dhanesh> what i want to discuss
[12:35] <bazhang> dhanesh, the reason for your being banned
[12:35] <dhanesh> i didnt change my ip
[12:36] <bazhang> dhanesh, please exit #ubuntu now
[12:36] <dhanesh> i dont know how to change my ip
[12:56] <bazhang> dhanesh was copying at least two nicks (or close enough)
[14:00] <knome> ehm
[14:00] <Pici> uh
[14:00] <Pici> jussi01: ? ^
[14:01] <Pici> nvm
[15:25] <elky> ...
[15:26] <jussi01> that issue is fixed in trunk, should be applied soonish
[16:25] <bazhang> * [haiku123] (~bbs@122-124-132-125.dynamic.hinet.net): noname dsl558 from earlier
[16:25] <ikonia> ?
[16:26] <bazhang> trolling multiple Ubuntu channels, then logged out and back in via the new nick, switched to other channels. still around
[16:26] <ikonia> mega
[21:03] <Myrtti> !ko
[21:08] <Myrtti> my troll-dar says there's something brewing about in #ubuntu
[21:08] <knome> hey Myrtti
[21:09] <Myrtti> ohai knome
[21:12] <jpds> Myrtti: That'd be me.
[21:12] <Myrtti> co2_ is out of the game now, who's next, I wonder
[21:13] <Myrtti> waltercool is a good candidate
[21:15] <knome> :)
[21:15] <Myrtti> happy hunting to active ops in -offtopic
[21:46] <Tm_T> hello
[22:07] <maco> jpds: ban evading?
[22:08] <maco> jpds: you didnt set a ban the first time, just removed
[22:08] <jpds> maco: I did.
[22:08] <maco> er i dont see a +b anywhere
[22:08] <jpds> Oh, haha.
[22:08] <jpds> 22:06:43 [!] #ubuntu<EMAIL_ADDRESS>Channel ban list is full
[22:08] <maco> nor do i see one this time
[22:08] <jpds> !ops | hi.
[22:09] <jrib> not my fault!
[22:09] <maco> haha
[22:10] <Tm_T> @login
[22:14] <jpds> lolforward.
[22:14] <maco> jpds: why so many bbbb after the - ?
[22:14] <jpds> maco: Multiple removals.
[22:15] <Amaranth> Feel free to remove any I may have
[22:15] <Amaranth> I always insist I don't have any though
[22:22] <Tm_T> I hope I don't do anything silly this time :-P
[22:23] <topyli> i admire your optimism! :)
[22:24] <Tm_T> topyli: I can empty whole banlist, and I don't need to even try!
[22:24]  * Tm_T hides
[22:24] <topyli> :)
[22:25] <Tm_T> oh well, one ban stays, needs comments ->
[23:16] <Tm_T> see what dr3mro said


[02:51] -queuebot:#ubuntu-release- Unapproved: fwupdate (bionic-proposed/main) [10-2 => 10-2] (core)
[02:52] -queuebot:#ubuntu-release- Unapproved: fwupdate (bionic-proposed/main) [10-2 => 10-2] (core)
[03:10] -queuebot:#ubuntu-release- Unapproved: fwupdate (xenial-proposed/main) [0.5-2ubuntu7 => 0.5-2ubuntu7] (core)
[03:10] -queuebot:#ubuntu-release- Unapproved: fwupdate (xenial-proposed/main) [0.5-2ubuntu7 => 0.5-2ubuntu7] (core)
[03:11] -queuebot:#ubuntu-release- New binary: liburcu [armhf] (bionic-proposed/main) [0.10.0-3] (ubuntu-desktop, ubuntu-server)
[03:14] -queuebot:#ubuntu-release- New binary: liburcu [arm64] (bionic-proposed/main) [0.10.0-3] (ubuntu-desktop, ubuntu-server)
[03:18] -queuebot:#ubuntu-release- New binary: json-c [armhf] (bionic-proposed/main) [0.12.1-1.3] (core)
[03:19] -queuebot:#ubuntu-release- New binary: json-c [arm64] (bionic-proposed/main) [0.12.1-1.3] (core)
[03:31] -queuebot:#ubuntu-release- New binary: krb5 [arm64] (bionic-proposed/main) [1.16-1] (core)
[03:33] -queuebot:#ubuntu-release- New binary: krb5 [armhf] (bionic-proposed/main) [1.16-1] (core)
[04:32] -queuebot:#ubuntu-release- New binary: libqmi [arm64] (xenial-proposed/main) [1.16.2-1ubuntu<IP_ADDRESS>] (kubuntu, ubuntu-desktop)
[04:35] -queuebot:#ubuntu-release- New binary: libqmi [armhf] (xenial-proposed/main) [1.16.2-1ubuntu<IP_ADDRESS>] (kubuntu, ubuntu-desktop)
[05:10] -queuebot:#ubuntu-release- New binary: qt5ct [amd64] (bionic-proposed/none) [0.34-1] (no packageset)
[05:12] -queuebot:#ubuntu-release- New binary: qt5ct [i386] (bionic-proposed/none) [0.34-1] (no packageset)
[10:24] -queuebot:#ubuntu-release- Unapproved: openvswitch (artful-proposed/main) [2.8.1-0ubuntu<IP_ADDRESS> => 2.8.1-0ubuntu<IP_ADDRESS>] (ubuntu-server)
[11:09] -queuebot:#ubuntu-release- New binary: stex [amd64] (bionic-proposed/universe) [1.2.1+git20171204.g5e4f0ca-1] (no packageset)
[18:06] <tsimonq2> flocculant: You could have copied the ISO to another filename and used zsync to grab the delta :P
[18:10] <flocculant> teaching granny to suck eggs then :p
[19:09] -queuebot:#ubuntu-release- New binary: argon2 [arm64] (bionic-proposed/universe) [0~20161029-1.1] (no packageset)
[19:09] -queuebot:#ubuntu-release- New binary: argon2 [armhf] (bionic-proposed/universe) [0~20161029-1.1] (no packageset)
[19:19] -queuebot:#ubuntu-release- New binary: kpmcore [arm64] (bionic-proposed/universe) [3.3.0-1] (kubuntu)
[19:22] -queuebot:#ubuntu-release- New binary: ignition-msgs [armhf] (bionic-proposed/universe) [1.0.0+dfsg1-1] (no packageset)
[19:24] -queuebot:#ubuntu-release- New binary: ignition-msgs [arm64] (bionic-proposed/universe) [1.0.0+dfsg1-1] (no packageset)
[19:24] -queuebot:#ubuntu-release- New binary: kpmcore [armhf] (bionic-proposed/universe) [3.3.0-1] (kubuntu)
[19:31] -queuebot:#ubuntu-release- New binary: tinyxml2 [arm64] (bionic-proposed/universe) [6.0.0+dfsg-1] (no packageset)
[19:34] -queuebot:#ubuntu-release- New binary: tinyxml2 [armhf] (bionic-proposed/universe) [6.0.0+dfsg-1] (no packageset)
[19:39] -queuebot:#ubuntu-release- New binary: ttfautohint [armhf] (bionic-proposed/universe) [1.8.1-1] (no packageset)
[19:40] -queuebot:#ubuntu-release- New binary: ttfautohint [arm64] (bionic-proposed/universe) [1.8.1-1] (no packageset)
[19:45] -queuebot:#ubuntu-release- New binary: svxlink [armhf] (bionic-proposed/universe) [17.12.1-1] (no packageset)
[19:45] -queuebot:#ubuntu-release- New binary: votca-tools [armhf] (bionic-proposed/universe) [1.4.1-2] (no packageset)
[19:45] -queuebot:#ubuntu-release- New binary: votca-tools [arm64] (bionic-proposed/universe) [1.4.1-2] (no packageset)
[19:46] -queuebot:#ubuntu-release- New binary: limesuite [arm64] (bionic-proposed/universe) [17.12.0+dfsg-1] (no packageset)
[19:47] -queuebot:#ubuntu-release- New binary: limesuite [armhf] (bionic-proposed/universe) [17.12.0+dfsg-1] (no packageset)
[19:50] -queuebot:#ubuntu-release- New binary: svxlink [arm64] (bionic-proposed/universe) [17.12.1-1] (no packageset)
[20:03] -queuebot:#ubuntu-release- New binary: ldc [armhf] (bionic-proposed/universe) [1:1.6.0-1] (no packageset)
[20:10] -queuebot:#ubuntu-release- New binary: slurm-llnl [arm64] (bionic-proposed/universe) [17.11.2-1] (no packageset)
[20:19] -queuebot:#ubuntu-release- New binary: slurm-llnl [armhf] (bionic-proposed/universe) [17.11.2-1] (no packageset)
[20:34] -queuebot:#ubuntu-release- New binary: x264 [armhf] (bionic-proposed/universe) [2:0.152.2854+gite9a5903-2] (kubuntu)
[20:35] -queuebot:#ubuntu-release- New binary: kmscube [arm64] (bionic-proposed/universe) [0.0.0~git20170508-1] (no packageset)
[20:35] -queuebot:#ubuntu-release- New binary: kmscube [armhf] (bionic-proposed/universe) [0.0.0~git20170508-1] (no packageset)
[20:36] -queuebot:#ubuntu-release- New binary: x264 [arm64] (bionic-proposed/universe) [2:0.152.2854+gite9a5903-2] (kubuntu)
[20:38] -queuebot:#ubuntu-release- New binary: tl-cpputils [arm64] (bionic-proposed/universe) [1.0-1] (no packageset)
[20:40] -queuebot:#ubuntu-release- New binary: tl-cpputils [armhf] (bionic-proposed/universe) [1.0-1] (no packageset)
[20:41] -queuebot:#ubuntu-release- New binary: ignition-math4 [arm64] (bionic-proposed/universe) [4.0.0+dfsg1-1] (no packageset)
[20:41] -queuebot:#ubuntu-release- New binary: ignition-math4 [armhf] (bionic-proposed/universe) [4.0.0+dfsg1-1] (no packageset)
[21:05] -queuebot:#ubuntu-release- New binary: lamarc [arm64] (bionic-proposed/universe) [<IP_ADDRESS>+dfsg-1] (no packageset)
[21:09] -queuebot:#ubuntu-release- New binary: lamarc [armhf] (bionic-proposed/universe) [<IP_ADDRESS>+dfsg-1] (no packageset)
[21:13] -queuebot:#ubuntu-release- New binary: qt5ct [arm64] (bionic-proposed/universe) [0.34-1] (no packageset)
[21:13] -queuebot:#ubuntu-release- New binary: qt5ct [armhf] (bionic-proposed/universe) [0.34-1] (no packageset)
[22:50] -queuebot:#ubuntu-release- New binary: ddrutility [arm64] (bionic-proposed/universe) [2.8-1] (no packageset)
[22:51] -queuebot:#ubuntu-release- New binary: ddrutility [armhf] (bionic-proposed/universe) [2.8-1] (no packageset)
[22:58] -queuebot:#ubuntu-release- New binary: gnuastro [arm64] (bionic-proposed/universe) [0.5-1] (no packageset)
[23:09] -queuebot:#ubuntu-release- New binary: gnuastro [armhf] (bionic-proposed/universe) [0.5-1] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: krb5 [i386] (bionic-proposed/main) [1.16-2] (core)
[23:16] -queuebot:#ubuntu-release- New binary: libgaminggear [amd64] (bionic-proposed/universe) [0.15.1-5] (no packageset)
[23:16] -queuebot:#ubuntu-release- New binary: mali-midgard-driver [armhf] (bionic-proposed/multiverse) [0.1-2] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: krb5 [amd64] (bionic-proposed/main) [1.16-2] (core)
[23:21] -queuebot:#ubuntu-release- New binary: krb5 [arm64] (bionic-proposed/main) [1.16-2] (core)
[23:24] -queuebot:#ubuntu-release- New binary: speech-tools [amd64] (bionic-proposed/universe) [1:2.5.0-2] (kubuntu)
[23:25] -queuebot:#ubuntu-release- New binary: speech-tools [i386] (bionic-proposed/universe) [1:2.5.0-2] (kubuntu)
[23:28] -queuebot:#ubuntu-release- New binary: krb5 [armhf] (bionic-proposed/main) [1.16-2] (core)
[23:51] -queuebot:#ubuntu-release- New binary: speech-tools [armhf] (bionic-proposed/universe) [1:2.5.0-2] (kubuntu)
[23:52] -queuebot:#ubuntu-release- New binary: speech-tools [arm64] (bionic-proposed/universe) [1:2.5.0-2] (kubuntu)


[00:57] <wallyworld> axw: looking at 1.25 PR. interesting that in 2.x, we have leaseClientId as an attribute on State and hence set that as part of State.start() instead of during lease worker startup as your 1.25 change does
[00:58] <axw> wallyworld: yeah probably should do it in 1.25 too, since it should be a terminal error. just made things a little simpler this way
[00:59] <wallyworld> axw: yeah, it may be what's proposed is good enough. i guess if we can't get the clientId stuff will still break, but in a different way
[01:02] <wallyworld> anastasiamac: hml: axw: forgot to remind - if there's anything you want to add to release notes for beta3, now is the time
[01:03] <hml> wallyworld: nothing coming to mind
[01:03] <wallyworld> yeah, mostly bug fixes this time
[01:03] <wallyworld> i added a few key things
[01:04] <anastasiamac> wallyworld: m all good but will confirm with the rest of the squad later on in the day
[01:04] <wallyworld> ty, may be too late then :-)
[01:06] <axw> nah I don't think so
[01:06] <anastasiamac> really? 4pm our time?..
[01:06] <axw> only thing was the mutex fix, and that's out :~(
[01:06] <anastasiamac> wallyworld: most bug fixes anyway :)
[01:07] <wallyworld> indeed
[01:07] <wallyworld> anastasiamac: yeah veebers is on fire, i expect it wil be done by 4pm our time as that will be well into his evening and he will already be on the beer :-)
[01:08] <anastasiamac> wallyworld: :D
[01:11] <veebers> wallyworld: hah more like cleaning up spit-up and baby wees off my hands, but hopefully there will be a beer there sometime ^_^
[01:11] <wallyworld> the joys of parenthood
[01:11] <wallyworld> you'll be doing the same thing to yuorself when you hit 80
[01:11] <veebers> hah ^_^
[01:12] <veebers> s/when/if/ /me dies of parenthood related stress
[01:32] <axw> wallyworld: https://github.com/juju/mutex/pull/5
[01:33] <axw> currently running the network-health test with the old code to repro locally, then will run with this to make sure it's the problem
[01:33] <axw> it's definitely *a* problem though
[01:34] <wallyworld> axw: looking. good we have CI
[01:34] <axw> indeed
[01:39] <wallyworld> axw: lgtm, just a comment typo
[01:40] <axw> wallyworld: heh thanks
[01:58] <axw> wallyworld: do you have rights to merge https://github.com/juju/mutex/pull/5 ?
[01:58] <wallyworld> yup, i think so
[02:00] <wallyworld> axw: added you with perms to merge
[02:00] <wallyworld> try it?
[02:00] <axw> wallyworld: thanks
[03:24] <hml> wallyworld: changes we discussed have been made, pr updated
[03:47] <thumper> axw: what was happening with the mutex?
[03:47] <thumper> axw: was it inheriting the lock, and only one closed it, so it was still "held" or something?
[03:48] <axw> thumper: subprocess inherited the file descriptor, so flock was held by subprocess even though juju closed its FD
[03:48] <thumper> but that sub process would have finished as well, releasing it, right?
[03:48] <axw> thumper: yeah, unless it spawned off something like "timeout"
[03:55] <thumper> axw: is that what the tests were doing?
[03:55] <thumper> so that explains why some hooks were fine and others not yes?
[03:57] <axw> thumper: the network-health test starts a server from one of the hooks, and never stops it AFAICT
[03:57] <axw> thumper: yeah, depends on the hook implementation for sure
[03:58] <thumper> ah..
[03:58] <thumper> ok, I like to know why things fail :)
[05:10] <wallyworld> axw: the state we attach to the apiRoot object - the one facades get via ctx.GetState() - i can't see where that gets closed. do you know?
[05:12] <axw> wallyworld: looking, have to remind myself
[05:12] <wallyworld> i also can't see where we Stop() resources
[05:13] <axw> wallyworld: it's the same State that's attached to the Server
[05:13] <wallyworld> and we stop that one? let me look
[05:13] <axw> wallyworld: which is closed by the agent
[05:13] <wallyworld> ok, ta
[05:14] <wallyworld> axw: trying to decide whether to add a "controller" Resource
[05:14] <wallyworld> rather that yet another attribute on server
[05:14] <wallyworld> as resources i think is the preferred way to add stuff to the facade context
[05:15] <axw> wallyworld: I'd prefer it was part of the Server
[05:15] <wallyworld> there's a snaky comment from willian next to ctx.State() that it should be a resource
[05:15] <wallyworld> any reason for preferring to add to Server?
[05:16] <axw> wallyworld: I don't know what that would buy us
[05:16] <axw> wallyworld: because State and StatePool are there. and because it's not a per-connectio nresource
[05:16] <wallyworld> keeps facade Context interface stable
[05:16] <axw> it's owned by the Server, not by the connection
[05:17] <axw> and eventually it shouldn't even be owned by the Server, but passed in and owned by a manifold
[05:18] <wallyworld> hmmm, ok, let me think on it
[05:18] <axw> wallyworld: perhaps we should start a new branch for this work? I have some things I'd like to land too, but have been holding off until after 2.3
[05:19] <wallyworld> a feature branch? yeah maybe
[05:19] <axw> wallyworld: though possibly my work will make fixing https://bugs.launchpad.net/juju/+bug/1642618 easier anyway
[05:19] <mup> Bug #1642618: enable-ha using existing machines breaks agents <enable-ha> <juju:In Progress by axwalk> <https://launchpad.net/bugs/1642618>
[05:19] <wallyworld> i think we can do a few things on develop
[05:20] <wallyworld> a lot of this stuff is shifting furnature around
[05:21] <axw> wallyworld: sometimes the furniture is accidentally load bearing though :)
[05:22] <wallyworld> that is true
[05:23] <wallyworld> i'll do this work and see how it looks
[05:23] <wallyworld> can propose against a fb if it looks too messy
[05:56] <wallyworld> axw: sorry, another question. do you know why we pass in a State to startStateWorkers() but then provide a separate openState() method to the apiserverWorkerStarter? we barely use the result from openState(). but noentheless, why not just use the one we already have, especially when that one we alrready have comes from the manifold
[05:57] <wallyworld> openState() as it turns out provides a State used to get ControllerConfig(), which we could just pass in from the original st, and create an audit log sink, which we also could get from a manifold.
[05:57] <axw> wallyworld: I thought there was a comment, but can't find it now. it's because the apiserver kills the state workers
[05:58] <axw> wallyworld: so if hte apiserver restarts, it needs a new State
[05:58] <axw> sas the old's watchers, lease manager, etc. will have been stopped
[05:58] <axw> *as
[05:58] <axw> wallyworld: this is one of the things I have fixes for in the pipeline
[05:58] <axw> wallyworld: if it makes it easier for you to do what you want to do, I can look to land my work sooner rather than later
[05:59] <wallyworld> yeah, that would be good. i want to thread through a controller
[05:59] <wallyworld> but need a state
[05:59] <axw> wallyworld: I have a branch that will move the apiserver to a manifold, too, but needs a bit more work
[05:59] <axw> wallyworld: probably better to get that in, then you can use the controller manifold?
[05:59] <wallyworld> would be good to get that stuff landed
[05:59] <wallyworld> yes
[05:59] <wallyworld> maybe a fb then?
[06:00] <wallyworld> it's all very messy atm
[06:00] <wallyworld> would be good to get this cleaned up
[06:00] <axw> wallyworld: I think that'd be prudent. then fold it into develop as soon as we branch
[06:00] <wallyworld> yup
[06:00] <axw> wallyworld: first step is to land https://github.com/juju/juju/pull/8038 in a feature branch then
[06:01] <wallyworld> ok, and it's been approved
[06:01] <axw> wallyworld: want to review for me? it has rog's +1, would be good to get a second opinion tho, as it's core
[06:01] <wallyworld> ok
[06:01] <wallyworld> i'll create the fb
[06:01] <wallyworld> as well
[06:05] <wallyworld> axw: https://github.com/juju/juju/tree/state-controller-refactor
[06:05] <wallyworld> looking at PR now
[06:05] <axw> wallyworld: thanks
[06:06] <axw> wallyworld: note there's two commits, might be easier to review them independently
[06:06] <axw> one after the other, rather
[06:06] <wallyworld> ok
[06:07] <wallyworld> axw: i had a look earlier - we disucssed a bit already this week, i'll re-review
[06:07] <axw> wallyworld: we did? I don't remember htat at all :o
[06:07]  * axw is losing the plot
[06:08] <wallyworld> i was asking about exposing context to api leayer, and clarifying operation on apiserver sid eetc
[06:08]  * wallyworld has already lost the plot
[06:08] <axw> sounds vaguely familiar :p
[06:19] <wallyworld> axw: +1 to go into fb. i'd like to ensure we get some good CI runs (which we will) and do some more extensive manual testing with all the other changes we will be landing soon
[06:20] <axw> wallyworld: ok. I think I broke something in the API package with a change I made about an hour ago, will fix that and land
[06:20] <wallyworld> sgtm
[06:20] <wallyworld> axw: and then you had a followup bit of work to go on top of this?
[06:21] <wallyworld> i'll look to pick up my stuff next week perhaps
[06:21] <axw> wallyworld: yes, to move apiserver to the dependency engine
[06:21] <wallyworld> great, ok
[06:21] <axw> then there'll be more followups on top of that I'm sure
[06:21] <wallyworld> yep
[06:22] <axw> wallyworld: e.g. once we move to using a single StatePool, the introspection code can be cleaned up a bit
[06:22] <axw> it's really awkward atm, the apiserver starter needs to create a new StatePool, then set that on the agent so the introspection worker can reference it
[08:45] <wpk> wpk@minnie:~/dev/src/gopkg.in/juju/names.v2$ grep -r IsValidRelation *
[08:45] <wpk> wpk@minnie:~/dev/src/gopkg.in/juju/names.v2$ grep -r IsValidRelation relation_test.go
[08:45] <wpk> 			c.Assert(names.IsValidRelation(key), gc.Equals, isValid)
[08:45] <wpk> magic
[08:45] <wpk> 			c.Assert(names.IsValidRelation(peerKey), gc.Equals, isValid)


[08:39] <bittin> morning
[18:08] <cbreak> anyone here using firefox in snap?
[18:08] <cbreak> I have font rendering issues with japanese, like on https://ja.wikipedia.org/wiki/%E6%97%A5%E6%9C%AC%E3%81%AB%E3%81%8A%E3%81%91%E3%82%8B%E6%BC%A2%E5%AD%97
[18:08] <cbreak> not entirely sure why, but it seems to only affect firefox
[18:09] <murmel> cbreak: what specifically is your issue, as it renders fine here 22.04 firefox snap
[18:09] <murmel> (with fonts noto)
[18:10] <cbreak> all I see here is the unicode fallback font boxes
[18:10] <cbreak> https://postimg.cc/nXh7459V
[18:10] <murmel> cbreak: does your font support japanese (which is configured in the settings?)
[18:11] <cbreak> no
[18:11] <cbreak> japanese works fine outside firefox
[18:11] <cbreak> for example, kitty term, dolphin show it just fine
[18:11] <cbreak> and the window title from plasma also shows it
[18:11] <cbreak> outside firefox, noto is available
[18:12] <murmel> cbreak: yeah, probably because it uses a different font Oo
[18:12] <cbreak> but inside it, I can not chose it
[18:12] <murmel> i installed fonts-noto, and it's available in the snap
[18:14] <cbreak> this is how it looks for me in normal 20.04 firefox: https://postimg.cc/JDZkYfWf
[18:16] <cbreak> With 22.10 snap firefox, I don't have most of my fonts listed: https://postimg.cc/18b0WcqN
[18:17] <cbreak> I suspect something prevents firefox from seeing / finding noto here
[18:20] <cbreak> the problem persists, even if I delete ~/snap/firefox completely
[18:27] <cbreak> murmel: so it's probably some bug in either snap or firefox, on 22.10 :(
[18:27] <cbreak> since the same thing seems to work for you in 22.04
[18:28] <cbreak> I've only noticed this problem today, but no idea how long it existed.
[18:30] <cbreak> is there a way to execute commands inside the context of a snap?
[18:39] <cbreak> interesting!
[18:39] <cbreak> https://gist.github.com/cbreak-black/df3b78277f9dfa4b454c29d78873ee97
[18:39] <cbreak> so there are actually only few fonts visible
[18:43] <cbreak> ls -la /usr/share/fonts inside the snap shell gives me an empty directory
[18:48] <cbreak> maybe I should pull a windows, and reboot... :/
[18:53] <cbreak> unsurprisingly, rebooting didn't help :(


[15:31] <ev> ugh, my accessibility fixes in ubiquity-dm seem to be broken, at least on this nfs booted netbook
[15:31] <ev> weird though, I tested that thoroughly
[17:22] <charlie-tca> Is it known that the alternate images are failing to install - No kernel modules were found ?
[17:22] <charlie-tca> I can't find anything in the logs about this
[17:32] <ev> charlie-tca: https://launchpad.net/bugs/723148
[17:32] <ubot2> Launchpad bug 723148 in debian-installer "Natty server ISO images fail to install" [High,New]
[17:33] <charlie-tca> thanks, saves me filing a duplicate then
[20:25] <highvoltage> is this also the right channel for casper related stuff?
[20:25] <highvoltage> if so, https://bugs.launchpad.net/ubuntu/+source/casper/+bug/723357
[20:26] <ubot2> Launchpad bug 723357 in casper "Edubuntu Live DVD does not use ship-seeded packages properly" [Undecided,New]
[21:56] <TheMuso> ev: Tested only-ubiquity mode with orca, and all works well, thanks. Got a weird crash on one machine, but haven't investigated further, will do so in a day or so once I am done cramming stuff prior to feature freeze. :)
[22:13] <stgraber> superm1: http://www.stgraber.org/2011/02/22/edubuntus-installer-ready-for-11-04/ thought you might be interested
[23:26] <superm1> stgraber, looks nice.  i do question if you really do need to present in the UI that extra "Name" column though.  Does it really add value?


[00:06] <jtaylor> hm I seem to have applied the patches wrongly
[00:07] <jtaylor> the upstream patches do work error less, but the py3 output is less useful
[00:16] <jtaylor> yup, just be being dumb again, the upstream patches work for me
[00:16] <jtaylor> slangasek: ^
[00:17] <jtaylor> < goes to bed, bye
[00:32] <barry> StevenK: fix committed sounds right-ish at least, since python's roundup doesn't really have a fix released status, and nothing's really fix released until the next python (patch) version, which isn't tracked in round up.
[00:33] <StevenK> barry: Do you want to add that to the bug and change the status as you see fit, then?
[00:34] <barry> StevenK: i just added a comment. let's see if lifeless responds before setting status
[00:35] <StevenK> barry: Thanks
[00:47] <lifeless> barry: url ?
[00:59] <infinity> @pilot out
[03:10] <slangasek> cjohnston, mhall119: do you have any idea why there are duplicate sessions for a blueprint, and can you tell me how to get rid of one of them? http://summit.ubuntu.com/uds-1311/meeting/22028/core-1311-dmraid2mdadm/ http://summit.ubuntu.com/uds-1311/meeting/22017/transitioning-to-use-mdadm-by-default-for-some-of-the-fakeraid-devices/
[04:24] <pitti> Good morning
[05:05] <rbasak> infinity: I'm not sure how to test libapache2-mod-svn without also relying on svnadmin and svn to work :)
[05:06] <infinity> rbasak: Heh.  Well, I like it anyway.  It's the complete opposite of unit testing, but the build-time tests do a fair job of that.  Your test is a great one-shot "yeahp, pretty much the whole package still works when installed".
[05:06] <rbasak> A happy coincidence :)
[05:06]  * infinity curses firebird, which appears to hate him on arm64.
[05:07]  * rbasak appreciates the praise. Thank you!
[05:08] <pitti> infinity: would you mind adding a "bad test" override for debtags? someone added an XS-Testsuite: without actually having tests; I removed the jobs from jenkins, but britney still thinks it's "failed"
[05:08] <infinity> pitti: Sure, if it's removed and won't have a sad next time.
[05:08] <pitti> infinity: no, the override can go again once it propagated
[05:09] <pitti> infinity: I would just have updated the autopkgtest status file, if I could remember to which host britney moved to :)
[05:09] <infinity> pitti: Done.
[05:09] <pitti> infinity: cheers
[05:09] <infinity> pitti: And nakefruit.
[05:09] <infinity> snakefruit, too.
[05:10] <infinity> The first barrier of entry is deciphering my typos.
[05:10] <pitti> ah, thanks
[05:12]  * infinity decides he cares a lot less about porting firebird2.5 to arm64 than he did an hour ago and finds something less stupid to do.
[09:23] <tseliot> pitti: https://jenkins.qa.ubuntu.com/job/trusty-adt-ubuntu-drivers-common/10/ :)
[09:23] <pitti> tseliot: indeed, thanks for fixing!
[09:24] <tseliot> :)
[09:25] <tseliot> pitti: oh, BTW, where do you suggest that I file a bug report on the python gtk (gir) bindings?
[09:26] <pitti> tseliot: that'd be gtk+3.0
[09:26] <tseliot> pitti: yes, the 3.0 ones
[09:27] <tseliot> pitti: or do you mean that I should file the report against the source of gtk+3.0?
[09:27] <pitti> tseliot: right, as that builds the Gtk GIR bindings
[09:27] <tseliot> pitti: ok, thanks
[10:33] <seb128> cjwatson, hey, how do you determine if config.guess/sub have support for arm64?
[10:40] <pitti> seb128: check if config.guess contains "aarch64"
[10:40] <pitti> "aarch64:Linux:" more specifically
[10:41] <seb128> pitti, danke
[10:42] <seb128> cjwatson, I'm syncing libisoburn (it's on your merge list, the only diff was running dh-autoreconf to have an updated config.guess/sub for arm64, the new version is Debian has those recent enough)
[10:42] <xnox> slangasek: hm, i filed a blueprint _and_ did the propose a session "simple form" on summit.u.c. So the earlier "manual" one needs killing, i.e. kill http://summit.ubuntu.com/uds-1311/meeting/22017/transitioning-to-use-mdadm-by-default-for-some-of-the-fakeraid-devices/
[10:42] <xnox> cjohnston: ^
[10:43] <seb128> cjwatson, doh, ignore that, we already have the new version in trusty-proposed it seems (I didn't have proposed enabled)
[10:43] <seb128> cjwatson, well, I updated libisofs which unblocked the depwait at least :p
[10:44] <seb128> pitti, thanks CurrentDesktop btw ;-) oh, and hey ;-)
[10:53] <cjwatson> seb128: grep aarch64 config.{guess,sub}
[10:53] <cjwatson> oh, pitti got there
[10:53] <seb128> cjwatson, thanks ... yes ;-)
[10:53] <cjwatson> seb128: right, I was assuming you'd get to libisofs :)
[10:53] <cjwatson> I went through the same sync decision last week
[10:53] <pitti> seb128: ça va :)
[10:53] <seb128> cjwatson, ;-)
[10:53] <pitti> seb128: rmadison FTW!
[10:54] <seb128> cjwatson, did you have a good trip back btw?
[10:54] <seb128> pitti, indeed
[10:54] <pitti> since the archive stuff moved to a new server, rmadison is actually usable again
[10:54] <cjwatson> meh, as good as you can get for that duration :)
[10:54] <cjwatson> slept a bit and the plane didn't crash
[10:55] <cjwatson> I've been vaguely meaning to have merges.u.c look at both trusty and trusty-proposed so that we don't have this duplicate-work window
[11:34] <xnox> ev: can you make me an admin of https://launchpad.net/~timezonemap-team ?
[11:35]  * Laney sniggers
[11:44] <ev> xnox: done
[11:47] <xnox> Laney: I think you are now the highest contributor to timezonemap. And as the one who touch it last, you are now the maintainer ;-)
[11:47] <Laney> Someone must have witten all the existing code :-)
[11:47] <Laney> anyway, review iz good
[11:48] <xnox> Laney: well ev copycatted some of it, then passed the maintainance baton to me, and now it's you =) it's a desktop component anyway ;-)
[11:48] <Laney> but ta
[11:48] <sladen> xnox: ev: talking of which, did the original 2.7MB 'tz_map.svgz' get included?
[11:49] <Laney> haha, it's both desktop & installer
[11:49] <xnox> sladen: i have it in an email somewhere. Let me check.
[11:49] <Laney> destroy the silo
[11:50] <sladen> xnox: ev: it was PD derived from a CIA map (confirmed by kwwii), and sabdfl okay'ed shipping it (based on the CIA's PD statement)
[11:50] <sladen> xnox: if so, you can probably finally close off bug #651064
[11:51] <xnox> sladen: pushed.
[11:51] <Laney> phwoar
[11:51] <Laney> that calls for a release
[11:53] <Laney> xnox: do you need to make it use that somehow?
[11:53] <xnox> sladen: well I committed the original .svg into timezonempa, but I don't know how to render the timezone pixmap.
[11:53] <Laney> also, didn't put it in src/data?
[11:54] <Laney> which already has some countryInfo1.svg thing
[11:54] <xnox> Laney: oh.
[11:55] <Laney> yeah I guess there is something more to be done here
[11:55] <xnox> sladen: if you can update the rendered.pngs that would help the original svg and rendered.pngs are in src/data in lp:timezonemap
[11:56] <xnox> sladen: similarly russia has moved one timezone to the right across the board, so I general refresh of timezones rendered pngs would be nice.
[12:01] <brainwash> is this behavior intended? bug 1248137
[12:02] <brainwash> I read about this issue some time ago in this channel, some processes still remain alive after session logout
[12:02] <brainwash> upstart?
[12:04] <pitti> we didn't enable logind's option to kill all remaining processes after logout, mostly for safety
[12:04] <pitti> (as it would make it impossible to leave stuff running in the background deliberately)
[12:04] <pitti> brainwash: check "ps aux | grep <username>" after logout for leftovers?
[12:05] <brainwash> pitti: it's not my report, but I'll try to confirm it
[12:06] <brainwash> pitti: did you already take a look at the new dbus-monitor logs which got added to the logind suspend/resume report?
[12:06] <pitti> not yet, no
[12:08] <brainwash> this issue is causing way too trouble, we need to fix it asap :)
[12:08] <brainwash> because most users are forced to reboot their system, if they are not aware of any workaround
[12:12] <pitti> yeah, I know; I need to grab desrt, but I didn't reach him yesterday
[12:18] <seb128> pitti, he might not be back before a few days, he was taking some swap days for thanksgiving and travelling
[12:24] <pitti> seb128: ah, thanks for letting me know
[12:25] <seb128> pitti, yw
[12:39] <mati75> hello, I'm looking for sponsor this package: https://launchpad.net/~mati75/+archive/lubuntu/+sourcepub/3642755/+listing-archive-extra
[13:01] <tseliot> pitti: shall I also file bug 1248152 upstream?
[13:16] <pitti> tseliot: sorry, back from lunch
[13:19] <pitti> tseliot: followed up to the bug
[13:21] <tseliot> pitti: ah, thanks. Is the .new() method documented somewhere?
[13:22] <tseliot> pitti: as in when to use it
[13:23] <tseliot> pitti: as opposed to simply calling ClassName()
[13:23] <pitti> tseliot: it's rather that *not* using the _new() method isn't documented well
[13:25] <pitti> https://wiki.gnome.org/PyGObject/IntrospectionPorting#Constructors
[13:26] <pitti> tseliot: so, ^ usually you have the choice between a class' constructor (often there are several ones, like gtk_button_new_with_label), or a GObject constructor which you pass initial properties
[13:26] <pitti> and usually a class constructor should do nothing else than setting the properties from its arguments, but some classes violate that (like GtkFileChooserWidget)
[13:26] <pitti> in that case you have to use the real constructor
[13:27] <tseliot> pitti: so there's no way to know for sure until you try?
[13:28] <pitti> tseliot: calling the class constructor should always work
[13:28] <pitti> tseliot: calling the GObject constructor should work in most cases these days, but it seems you found a case where it doesn't
[13:28] <pitti> that part is worth a bugzilla report as it will also break e. g. loading from a GtkBuilder file
[13:29] <tseliot> pitti: are you going to file it yourself or shall I? (you definitely have more context to do it)
[13:29] <pitti> tseliot: so Gtk.FileChooserWidget(self, Gtk.FileChooserAction.SELECT_FOLDER) does not make any sense at all (both the self, and the positional flag argument), I'm currently checking why it doesn't raise an exception
[13:30] <pitti> tseliot: I can file it if you want
[13:30] <tseliot> pitti: yes please
[13:36] <pitti> tseliot: filed upstream bug for pygobject and linked to the LP bug
[13:36] <tseliot> pitti: great, thanks!
[13:58] <mhall119> slangasek: was one of them entered manually into summit
[13:58] <mhall119> ?
[13:59] <mhall119> slangasek: or was an old BP removed from Launchpad?
[14:00]  * mhall119 blames xnox either way
[14:03] <xnox> mhall119: yes, i manually entered into summit.
[14:04] <xnox> mhall119: do you have powers to delete the manual one?
[14:04] <mhall119> yes I do
[14:04] <mhall119> xnox: slangasek: done
[14:04] <xnox> mhall119: delete this one - http://summit.ubuntu.com/uds-1311/meeting/22017/transitioning-to-use-mdadm-by-default-for-some-of-the-fakeraid-devices/
[14:05] <xnox> mhall119: \o/ thanks.
[14:42] <pitti> cjwatson: OOI, why is dell-recovery on http://people.canonical.com/~ubuntu-archive/transitions/html/hal.html ?
[14:42] <pitti> cjwatson: it has Depends: udisks | devicekit-disks | hal (of course all of these are obsolete, but it shouldn't really pull in hal)
[14:43] <pitti> i. e. is that just a bug with alternative dependencies, or shouldn't hal be in the transition tracker in the first place?
[14:46] <cjwatson> pitti: *shrug* the config has .depends ~ /hal/
[14:46] <cjwatson> sorry, rather: .depends ~ /(^| )hal([ ,]|$)/
[14:46] <xnox> pitti: well the stanza for bad is ".depends ~ /(^| )hal([ ,]|$)/ " which is don't specify alternate "hal" dep.
[14:47] <xnox> snap.
[14:47] <cjwatson> pitti: you could just ignore it :)
[14:47] <cjwatson> I see dff still Recommends: hal
[14:56] <brainwash> the pulseaudio user process keeps the logind session alive after session logout, is this a known issue? I recall reading about this some time ago in this channel
[14:56] <brainwash> bug 1248137
[15:21] <tseliot> stgraber: why did you reject nvidia-prime for precise-proposed?
[15:23] <stgraber> tseliot: what? The only nvidia-prime related stuff I did today was release two SRUs into -updates, didn't do any rejecting
[15:24] <tseliot> stgraber: Rejected: nvidia-prime 0.4.2~hybrid0.0.1 in precise (source has no binaries to be copied)
[15:24] <stgraber> oh, that's LP, not me :)
[15:24] <stgraber> let me try and see what happened there
[15:25] <stgraber> tseliot: doh, I know what's going on, let me try to sort it out
[15:25] <tseliot> stgraber: thanks
[15:27] <stgraber> tseliot: basically it's one of those packages that got introduced post-release, so the binaries end up in New every time. Apparently nobody processed that one for some reason, so the testers grabbed the binaries straight from the librarian and the copy failed since the binaries weren't actually in -proposed
[15:27] <stgraber> tseliot: I just accepted the binaries into -proposed now and will retry a copy once that's published
[15:28] <tseliot> stgraber: oh, I see. Thanks for your help
[16:04] <tseliot> stgraber: also can you have a look at bug 1246735 when you have the time, please?
[16:06] <davmor2> tseliot: oooooohhh
[16:23] <tseliot> davmor2: yep :)
[16:29] <slangasek> mhall119: ta
[16:39] <barry> mitya57: hi :)
[16:50] <mitya57> hi barry!
[16:51] <mitya57> Actually I may leave soon, so if you have something long, please send mails instead…
[16:51] <barry> mitya57: thanks for helping out with coverage :)  i'd like to see how ben responds before we do the merge.  otoh, i suppose we can merge now and resync later based on his responses
[16:51] <barry> mitya57: naw, we can use email.  just wanted to say hey
[16:51] <mitya57> Yes, and if we don't merge now we can include the fix for debug packages when it's ready
[16:51] <barry> mitya57: yep
[16:53] <seb128> slangasek, what do you mean by "The GNOME stack should be handling the suspend suppression"?
[16:53] <slangasek> seb128: it's GNOME components that are responsible both for the reboot signal and the suspend trigger
[16:54] <slangasek> upstart has nothing to do with this
[16:54] <seb128> slangasek, do you call logind "GNOME components"?
[16:54] <slangasek> seb128: ah, is this not handled on the gnome-settings-daemon side?
[16:55] <slangasek> do we signal logind directly to request a reboot?
[16:55] <seb128> slangasek, that bug happens if you close your lid during shutdown, at a time where there is no session open
[16:55] <seb128> slangasek, e.g if you close the lid on the plymonth shutdown screen
[16:56] <seb128> slangasek, I'm not sure how a GNOME component could be still holding an inhibitor at this time
[16:56] <slangasek> seb128: ah, ok; I understood it as "close lid during shutdown while the session is still open but shutdown has been requested"
[16:56] <slangasek> if it's after the session has exited, then yeah, that's obviously a logind bug, so feel free to reassign
[16:56] <seb128> slangasek, no, and I can confirm that bug, I've the plymonth logo displayed for 5-10s here, if I close the lid during that time it goes to suspend
[16:56] <seb128> slangasek, doing that, thanks
[17:32] <rbasak> What are we supposed to do for the Maintainer field for Ubuntu-only packages in universe for new packages? I've seen it be "Ubuntu Developers" and also an individual person. Are we supposed to use one or the other?
[17:50] <xnox> rbasak: as long as it has "ubuntu.com" somewhere in the string it's fine. =)
[17:51] <xnox> rbasak: if it's the typical one the devel-discus mailing list, it's fine. If you put your email in there, you'll get upload notifications for it even if somebody else does the upload.
[17:53] <rbasak> xnox: thanks. I'm reviewing/sponsoring for someone else (@ubuntu.com), so just wanted to check that non devel-discuss was acceptable.
[17:53] <xnox> rbasak: yeah, anything is ok.
[17:55] <Laney> It doesn't mean they are the maintainer though
[18:07] <mati75> I have question where I can find sponsor for Ubuntu patched package?
[18:10] <TheLordOfTime> is someone here with permissions to approve a bug nomination for Saucy able to do so on https://bugs.launchpad.net/ubuntu/+source/nautilus-dropbox/+bug/1242413?
[18:10] <TheLordOfTime> it was requested in -bugs to get it nominated and set accordingly for an SRU, with a claim that this is already fixed in Trusty
[18:22] <ivanka> hi seb128 - you around?
[18:24] <seb128> ivanka-train, hey, yes
[18:25] <ivanka-train> seb128, How are you?
[18:25] <seb128> ivanka-train, I'm good thanks! How are you?
[18:25]  * ivanka-train has a question, of course
[18:26] <seb128> ivanka-train, I was expecting so ;-)
[18:26] <seb128> ivanka-train, let me guess, you upgraded to 13.10 and have an issue?
[18:27] <ivanka-train> seb128, I am very well
[18:27] <ivanka-train> seb128, you are so clever! :-)
[18:27] <seb128> ;-)
[18:27] <ivanka-train> seb128, my battery life has disappeared
[18:27]  * xnox is intrigued
[18:27] <seb128> ivanka-train, you mean the battery indicator?
[18:28] <ivanka-train> ivanka-train, no, i mean that I have gone from having a couple of hours of battery life to 19 minutes
[18:29] <ivanka-train> I mean seb128 ^
[18:29]  * ivanka-train has started talking to herself now
[18:29] <seb128> ivanka-train, is the estimation wrong or is your battery drained out like that?
[18:29] <seb128> ivanka-train, what's your CPU usage in top/gnome-system-monitor?
[18:31] <ivanka-train> seb128, it seems to get drained out
[18:31] <seb128> ivanka-train, check the cpu usage, just in case something max it out
[18:31] <ivanka-train> seb128, it looks like 10%
[18:31] <seb128> ivanka-train, if not, I would tend to say your battery is having hardware issues
[18:31] <seb128> ivanka-train, how old is the battery?
[18:32] <ivanka-train> seb128, it is a couple of years old but it seems a weird coincidence that it dies all of a sudden, no?
[18:32] <seb128> ivanka-train, you can click on the indicator -> battery line -> battery in the sidepane
[18:33] <ivanka-train> seb128, hmm - it looks like the capacity is down to 8%...how annoying!
[18:33] <ivanka-train> actually it is about to die now and I am on the train
[18:33] <ivanka-train> seb128, I am going to drop off rudely
[18:33] <seb128> ivanka-train, looks like an hardware issue, battery to get buggy like that
[18:34] <ivanka-train> seb128, thanks for your help - I will check out a new battery and report back
[18:34] <seb128> ivanka-train, the Ubuntu upgrade is probably a coincidence timing
[18:34] <seb128> ivanka-train, good luck
[18:34] <seb128> ivanka-train, have a nice evening!
[18:34] <jtaylor> is it worth filing bugs for crashes when /tmp is not writable?
[18:34] <ivanka-train> seb128, thank you!
[18:34] <jtaylor> a collegue somehow made it read only and lots of unity related stuff just crashed
[18:34] <jtaylor> e.g. unity-scope-loader, firefox due to the menu integration (probably) etc.
[18:35] <seb128> jtaylor, not really worth it, code could handle a buggy system better (same as no space on disk) but in reality that's still a buggy system
[18:35] <jtaylor> but I guess non writeable /tmp is unusual
[18:35] <seb128> jtaylor, e.g you can file those but I expect they are not going to be ranked high on priority lists
[18:37] <jtaylor>  /tmp is cleared on boot in ubuntu, shouldn't it also restore permissions on boot?
[18:37] <xnox> ivanka-train: you can try this drain the battery until it will not turn on, leave it off and fully charge for e.g. 3 hours. Perform that 3 times. It should recover and make battery capacity increase.
[18:37] <jtaylor> it was owned by some random user with 700
[18:37] <seb128> xnox, you missed her it seems
[18:37] <xnox> =(
[18:38] <seb128> xnox, how much do you expect those charge cycles to change things?
[18:39] <seb128> jtaylor, /etc/init/mounted-tmp.conf
[18:43] <jtaylor> so thats no it should not reown the folder?
[18:44] <seb128> jtaylor, I'm not sure what it's supposed to do, the upstart job reacts on tmp being "mounted" it seems ...
[18:45] <seb128> jtaylor, I guess you need somebody from foundations to reply to that question, e.g maybe xnox knows ;-)
[18:45] <jtaylor> so far I see the script will overlay a working tmp if its full, but not if the permissinos are wrong
[19:09] <Serus> Hi
[19:12] <Serus> Can I import a keyboard map from my raspberry pi? my current maps are a tiny little bit different from what I want
[19:14] <sladen> Serus: what operating system are you running on the Raspberry Pi?
[19:14] <Serus> raspbian
[19:14] <sladen> Serus: if it is something Linuxy (very likely) then somewhere it will be using kernel and X keymaps, which is the same as Ubuntu (based on Debian) uses under the hood
[19:15] <Serus> raspbian is also based on debian
[19:15] <sladen> Serus: Raspbian is based on Debian too.  What is the keymaps you are wanting to import called?
[19:15] <Serus> Dutch - US international
[19:16] <Serus> the English (US) - US international behaves different
[19:16] <Serus> for example I now do this when I try to type "I'm"
[19:16] <Serus> I´m
[19:16] <Serus> Iḿ*
[19:17] <Serus> Which is pretty annoying, since I switch between windows and ubuntu. And it's even more annoying when programming.
[19:18] <sladen> Serus: in Ubuntu, open "system settings"; type 'keyboard', click 'Keyboard layout', click [+] (bottom left), type 'Dutch', select "Dutch US international" from the list (if it is there)
[19:19] <Serus> It's not there.
[19:19] <Serus> Running ubuntu 12.04
[19:19] <Serus> Should I do a dist upgrade
[19:19] <sladen> Serus: no, hold on
[19:20] <Serus> Ok
[19:22] <sladen> Serus: apologies, need to re-aquint myself with where keyboard layouts are kept
[19:22] <Serus> /usr/share/
[19:23] <Serus> /usr/share/X11/xkbd
[19:23] <Serus> /usr/share/X11/xkbd/symbols *
[19:25] <sladen> Serus: yes, thankyou.  They are from the 'xkb-data' package
[19:26] <Serus> That one is installed
[19:27] <sladen> Serus: dpkg -l xkb-data   on Raspbian, what version is shown?
[19:27] <sladen> Serus: on ubuntu 12.04 LTS, you probably have 2.5-1ubuntu1.3?
[19:28] <Serus> I need to setup my ssh server on the raspberry pi with a few new keys for ubuntu
[19:28] <Serus> yes, thats the version I have on ubuntu
[19:29] <Serus> If you give me a moment, I reboot into windows and see what version I have on the pi
[19:29] <Serus> brb
[19:36] <Serus> Ok I'm in windows now
[19:36] <Serus> Only now my sound is gone O.o
[19:39] <sladen> Serus: btw, you can copy your existing ssh private keys from the windows partition to ~/.ssh/
[19:39] <sladen> Serus: in Ubuntu
[19:39] <Serus> they are putty keys
[19:39] <Serus> will they work?
[19:43] <sladen> Serus: use puttygen to convert them to the standard format
[19:44] <Serus> Export OpenSSH key right?
[19:45] <sladen> Serus: if you're already back in Ubuntu;   sudo apt-get install putty   then run 'puttygen foo.ppk -O private-openssh -o foo_private
[19:45] <Serus> I'm still in windows
[19:46] <sladen> Serus: http://84kids.com/how-to-convert-your-putty-key-to-openssh-format/  this suggests that under MS Windows  puttygen is GUI, and that there is a Tools->Export OpenSSH key menu
[19:47] <Serus> Yeah I did that
[19:48] <Serus> Ok, I'll go back to ubuntu
[19:48] <Serus> brb
[19:52] <Serus> Ok I'm back
[19:56] <sladen> Serus: any how; either manually copy+add your desired keyboard layout; or find a newer .deb containing the Dutch US int layout
[19:56] <Serus> ok
[19:56] <sladen> Serus: did you find out what version you had on the Pi?
[19:57] <Serus> Yeah, I'll check it
[19:57] <Serus> because I saw it on windows, but now I'll copy+paste it
[20:05] <Serus> Ok I'm finally in
[20:05] <Serus> ii  xkb-data       2.5.1-3      all          X Keyboard Extension (XKB) config
[20:06] <Serus> that's the output on the raspberry pi
[20:20] <sladen> Serus: is (on Rasbian), "Dutch US International" (exactly that string) available in the GUI
[20:20] <sladen> Serus: I've installed a new xkb-data on an Ubuntu 12.04 LTS machine, and not (yet) made it come up
[20:21] <Serus> not (yet) made it come up?
[20:21] <sladen> Serus: I have not yet made "Dutch US International" appear as an available option in the keyboard configuration
[20:22] <Serus> well Iḿ used to selecting a language and then selecting a layout for that language.
[20:22] <Serus> Which makes the layout behave slightly different.
[20:22] <sladen> Serus: in the console?  Or the GUI?
[20:23] <Serus> I used raspi-config from the console. But for some reason that won't work from ssh on ubuntu
[20:23] <hallyn_> tjaalton: around?
[20:24] <Serus> let me try via remote desktop
[20:24] <sladen> Serus: do you mean "raspi-config" won't work over SSH;  or you make a selection but it doesn't make a difference over SSH?
[20:24] <Serus> it won't work over ssh
[20:24] <sladen> Serus: do you mean "raspi-config" won't work over SSH;  or you make a selection but it doesn't make a difference over SSH?
[20:26] <Serus> I don't get to see the screen where I can select a keyboard layout
[20:26] <sladen> Serus: if it is the first; what error does it show.  If it is the second, it is probably because the keyboard configuration is the one of the MS Windows/Ubuntu
[20:27] <sladen> Serus: do you get the command prompt back?
[20:27] <Serus> yes
[20:28] <Serus> I get the message that it's loading keymaps
[20:28] <Serus> and then it stopts
[20:28] <sladen> Serus: are you running 'sudo raspi-config'  or just  'raspi-config'
[20:28] <Serus> stops*
[20:28] <Serus> sudo raspi-config
[20:29] <tjaalton> hallyn_: sorry, forgot to check the fbtfs..
[20:29] <tjaalton> ftbfs
[20:29] <Serus> It also happens over RDP
[20:29] <Serus> guess I'll reboot it
[20:30] <hallyn_> tjaalton: near as I can tell it should just need libxext-dev in build-deps
[20:30] <hallyn_> why it gets pulled in automatically on x86 i'm not sure
[20:31] <Serus> Also it could've been loading the windows keymap
[20:38] <tjaalton> hallyn_: ok, i'll investigate a bit and fix it, thanks for testing
[20:46] <hallyn_> tjaalton: thanks.
[22:18] <utlemming> is there a definitive place to look up info on cgroups? i.e. all the things that it can do?
[22:19] <infinity> utlemming: Ask Lennart, obviously.  According to him, no one else understands them.
[22:19] <infinity> (But, more seriously, stgraber and hallyn might be able to point you at some decent writeups/docs/whatever)
[22:19] <infinity> stgraber: ^
[22:20] <stgraber> ;)
[22:20] <stgraber> utlemming: most documentation is in the kernel tree, there's typically a .txt file per controller listing all the keys and valid values
[22:20] <stgraber> utlemming: https://www.kernel.org/doc/Documentation/cgroups/
[22:51] <hallyn_> infinity: so fwiw the patchset applies cleanly on top of trusty's package.  I'm first going to build and test that with no aarch64 target actually enabled - though our testsuites don't do much if any lniux-user testing (hm).  then i'll enable the aarch64 arch and see how that goes
[22:51] <hallyn_> (over next few days)
[22:56] <infinity> hallyn_: Awesome, thanks.
[22:56] <infinity> hallyn_: Bonus points if you push those changes to Debian too, so they don't have to do it all over again.
[22:56] <infinity> hallyn_: (And so we agree on pathnames and such)
[22:57] <hallyn_> infinity: yeah i'll talk to mjt after testing
[22:57] <hallyn_> (now, off to dinner.)


[01:00] <akutz> falcojr: This is confirmed as a bug in v21.3 per this comment https://github.com/kubernetes-sigs/image-builder/issues/712#issuecomment-938257637
[01:00] <akutz> (includes a way to repro with a unit test)
[01:18] <akutz> falcojr: I've also identified a patch for the issue, and I'll submit a PR in the morning. The patch is at https://github.com/kubernetes-sigs/image-builder/issues/712#issuecomment-938262835.
[08:13] <otubo> blackboxsw, rhansen hey guys I didn't see any messages about cloud-init summit this year. You guys thinking about having one?
[14:28] <akutz> I filed https://github.com/canonical/cloud-init/pull/1058 to address https://bugs.launchpad.net/cloud-init/+bug/1946493
[15:14] <H__> how to try cloud-init 21.3 on Ubuntu 20.04.3 in AWS ? (I see only 20.04.2 there)
[15:38] <manuvakery1_> holmanb: yes i am using the same Openstack version.  the Local boot stage is where I am getting the error because the known_mac dict contains only {'00:00:00:00:00:00': 'lo'}
[17:36] <holmanb> manuvakery1_: net.get_interfaces() filters out various interface types (vlan/bond/bridge/blacklisted driver/etc) does anything there stand out to you as a possibility?
[17:37] <holmanb> If not the best way forward might be to just file a bug (including cloud-init collect-logs output and as much system detail as you can manage)
[17:38] <blackboxsw> otubo: I think we were going to delaying until Mar 2022, but wanted to float that idea by the mailinglist to get concensus on timing.
[17:39] <manuvakery1_> holmanb: I will bebug more and update
[17:39] <blackboxsw> *consensus
[18:39] <akutz> falcojr: Thanks for the quick merge1
[18:39] <akutz> Er, merge! :)
[18:48] <minimal> akutz: I've been using v2 file with set-name for many months now but not with per-interface nameservers, rather using global nameservers so guess its by luck I didn't spot this previously
[18:50] <akutz> Heh. Well, Cluster API Provider for vSphere (CAPV) uses "set-name" to "normalize" interface names. It just so happened this person *also* added the DNS entry feature. When I was running CAPV I basically modeled its guest network config on Cloud-Init's v2 model :) https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/66795d613fe06b4ff7e8f4fe3beb63c4d53c9d4d/api/v1alpha4/types.go#L186-L279
[18:51] <akutz> Here's a Golang Template for transforming the above data into a valid Cloud-Init v2 network config :) https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/66795d613fe06b4ff7e8f4fe3beb63c4d53c9d4d/pkg/util/constants.go#L19-L89
[18:52] <akutz> minimal: But I never caught this either, because I was also always using global nameservers, so what can ya do? I'm just glad I had the epiphany about the set-name. That seemed suspicious to me since there was a KeyError.
[18:53] <minimal> I guess if you define per-interface nameservers for more than 1 interface that its supposed to use resolvconf to handle this?
[18:56] <akutz> I mean, I've no clue. Looking at netplan I think they expect one interface is the default route and you set them there? https://netplan.io/reference/#common-properties-for-all-device-types
[19:01] <Nico1> Hey just wanted some guidance on this error
[19:02] <Nico1> this morning after reboot clud-init gave: azure.py[ERROR]: Could not crawl Azure metadata: 'Dat
[19:02] <Nico1> aSourceAzure' object has no attribute 'failed_desired_api_version'
[19:03] <Nico1> after that it reconfigured everything as it it were firstboot
[20:01] <blackboxsw> Nico1: can you run `cloud-init --version`
[20:03] <Nico1> sure /usr/bin/cloud-init 21.3-1-g6803368d-0ubuntu1~18.04.3
[20:08] <blackboxsw> thanks Nico1:  Can you please file a bug at  https://bugs.launchpad.net/cloud-init/+filebug  and attach the tar.gz from `cloud-init collect-logs to help triage here? Ok so you are ubuntu bionic Azure. That attribute was added in 21.1-19 which was released in March I think.
[20:08] <blackboxsw> I'm guessing you can from a version earlier that 21.1-19 straight to 21.3.1, but your /var/log/cloud-init.log will tell us better
[21:14] <Nico1> will do thanks, on the other hand I validated that package was updated on october, but from v21.2


[05:41] <RikMills> https://launchpadlibrarian.net/468188742/buildlog_ubuntu_focal_amd64_kubuntu_BUILDING.txt.gz
[05:41] <RikMills> I: Extracting libcrypt1...
[05:41] <RikMills> E: Tried to extract package, but file already exists. Exit...
[05:43] <RikMills> ditto for ubuntu-mate and xubuntu livefs recently
[05:55] <RikMills> in release libcrypt1 Breaks libc6 (<< 2.31), but glibc in release is still 2.30!
[05:56] <RikMills> that is screwed up :/
[06:54] -queuebot:#ubuntu-release- New sync: kipi-plugins (focal-proposed/primary) [4:19.12.3-1]
[07:29] <OldManWinter> Indeed, and it's throwing dose3 on my personal repo all out of whack. :P
[07:48] <juliank> RikMills: that sounds right?
[07:49] <RikMills> nope
[07:49] <juliank> RikMills: libc6 2.30 contains libcrypt1, libc6 2.31 does not
[07:49] <juliank> Hence Breaks / Replaces (<< 2.31)
[07:49] <vorlon> it doesn't sound right that there should be a package in the release pocket which Depends: libc6 and Breaks: libc6 (<< 2.31) when the release pocket has libc6 2.30
[07:50] <vorlon> p-m shouldn't have allowed this into the release pocket
[07:50] <RikMills> juliank: the breaks is right. it being in the release pocket is not
[07:50] <juliank> ah yes
[07:54] <vorlon> I could demote it back to -proposed, but I don't see how it got into the release pocket in the first place so I expect it would just sneak back
[07:59] <RikMills> trying: base-files libxcrypt
[07:59] <RikMills> accepted: base-files libxcrypt
[07:59] <RikMills> :?
[08:00] <juliank> this is very confusing!
[08:00] <juliank> base-files should not be in release pocket either?
[08:01] <RikMills> it doesn't install
[08:01] <juliank> yeah
[08:01] <juliank> does britney not understand breaks correctly?
[08:02] <juliank> did someone hint it badly
[08:02] <juliank> it sure sounds dangerous
[08:02] <RikMills> in a vm I have base-files, login and passwd held back
[08:03] <juliank> on m y laptop I have base-files, libcrypt1 held back
[08:03] <juliank> login and passwd it is going to upgrade
[08:04] <vorlon> found no evidence of a hint
[08:06] <juliank> ack
[08:06] <juliank> so a bug in britney solver then
[08:07] <juliank> vorlon: revert base-files and libcrypt1, demoting the versions to proposed, and add a block hint?
[08:07] <vorlon> yeah probably
[08:07] <vorlon> let's see
[08:08] <RikMills> looks like dok was doing something weird with publishing base-files and build essential?
[08:09] <vorlon> why are there packages in the release pocket that depend on libcrypt1 :P
[08:09] <RikMills> I have emails about the going into focal, not focal-proposed
[08:09] <RikMills> *them going
[08:09] <RikMills> as if they have been repubished there
[08:11] <vorlon> I don't see any manual publications to the release pocket in the lp history
[08:16] <vorlon> libxcrypt, base-files, shadow, libuser, apache2 rolled back
[08:18] <vorlon> and p-m disabled for the moment to make sure it doesn't start up again mid-publication
[08:20] <RikMills> :)
[08:22] <RikMills> btw, I think we should be good to get rid of Qt4 now. It has been removed from unstable
[08:25] <vorlon> publication appears to be done, turning p-m back on
[08:26] <vorlon> and I'm off to bed
[08:26] <RikMills> night, and thanks!
[15:11] -queuebot:#ubuntu-release- New: accepted linux-signed-azure-5.3 [amd64] (bionic-proposed) [5.3.0-1015.16~18.04.1]
[15:11] -queuebot:#ubuntu-release- New: accepted linux-signed-oem-osp1 [amd64] (bionic-proposed) [5.0.0-1042.47]
[15:11] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (bionic-proposed) [5.0.0-1033.34]
[15:43] -queuebot:#ubuntu-release- New binary: llvm-toolchain-10 [s390x] (focal-proposed/universe) [1:10.0.0~+rc3-1] (no packageset)
[16:48] <doko> is this libcrypt1 breaks/replaces libc6 (<< 2.31) the reason that the package doesn't migrate?
[16:49] <doko> can't retry autopkg tests, all requests are timing out
[17:00] <RikMills> doko: 'the package' = libxcrypt? vorlon put a block hint on that this morning
[17:01] <doko> yep, I know, but I don't understand why the breaks/replaces would affect that.
[17:01] <doko> I mean, why is it blocked without the hint?
[17:03] <RikMills> it wasn't blocked and did migrate, that was what broke things. it was demoted back to -proposed along with a few other things that should never have migrated
[17:06] <doko> RikMills: could you retry an autopkg test to see if it times out for you?
[17:06] <RikMills> any test?
[17:07] <doko> yep. http://autopkgtest.ubuntu.com/running isn't updated either. so there might be more than the timing out retries
[17:08]  * RikMills waits
[17:10] <RikMills> not timing out so far, but retry page is not loading either
[17:10] <RikMills> something is not well
[17:13] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-10 [s390x] (focal-proposed) [1:10.0.0~+rc3-1]
[17:13] -queuebot:#ubuntu-release- New: accepted ubuntustudio-look [amd64] (focal-proposed) [0.68]
[17:44] <doko> still showing the 4413/2004 pending builds for arm64/armhf
[20:00] -queuebot:#ubuntu-release- New binary: qgis [ppc64el] (focal-proposed/universe) [3.10.3+dfsg-1~exp2] (no packageset)
[20:38] -queuebot:#ubuntu-release- New binary: qgis [amd64] (focal-proposed/universe) [3.10.3+dfsg-1~exp2] (no packageset)
[22:21] -queuebot:#ubuntu-release- New binary: qgis [armhf] (focal-proposed/universe) [3.10.3+dfsg-1~exp2] (no packageset)
[22:23] -queuebot:#ubuntu-release- New binary: qgis [s390x] (focal-proposed/universe) [3.10.3+dfsg-1~exp2] (no packageset)
[22:36] -queuebot:#ubuntu-release- New binary: python-tinyalign [amd64] (focal-proposed/universe) [0.2-1ubuntu1] (no packageset)
[22:37] -queuebot:#ubuntu-release- New binary: python-tinyalign [ppc64el] (focal-proposed/universe) [0.2-1ubuntu1] (no packageset)
[22:38] -queuebot:#ubuntu-release- New binary: python-tinyalign [arm64] (focal-proposed/universe) [0.2-1ubuntu1] (no packageset)
[22:38] -queuebot:#ubuntu-release- New binary: python-tinyalign [s390x] (focal-proposed/universe) [0.2-1ubuntu1] (no packageset)
[22:38] -queuebot:#ubuntu-release- New binary: python-tinyalign [armhf] (focal-proposed/universe) [0.2-1ubuntu1] (no packageset)
[23:15] -queuebot:#ubuntu-release- Unapproved: snapd-glib (eoan-proposed/main) [1.49-0ubuntu<IP_ADDRESS> => 1.56-0ubuntu<IP_ADDRESS>] (desktop-core)
[23:21] -queuebot:#ubuntu-release- Unapproved: snapd-glib (eoan-proposed/main) [1.49-0ubuntu<IP_ADDRESS> => 1.56-0ubuntu<IP_ADDRESS>] (desktop-core)


[02:25] <sethly> hey all
[02:26] <Cheri703> hi
[02:29] <Unit193> U-H is now over... (started later)
[02:29] <Unit193> Hello sethly!
[02:29] <sethly> hi :)
[02:35] <Unit193> Shell hosting with Ubuntu!: http://www.nvita.org/free-shells.aspx
[02:49] <dmcglone> Hiya Pals
[02:49]  * Unit193 runs
[02:50] <dmcglone> later gator.. ;-)
[02:50] <Unit193> Hello dmcglone
[02:50] <Cheri703> hey dmcglone
[02:51] <dmcglone> How's that data coming along Cheri703?
[02:51] <dmcglone> Unit193: figure out your problem yet?
[02:51] <Cheri703> slow, have a ton of stuff going on! it's on my list!
[02:52] <dmcglone> I know the feeling :-/
[02:53] <dmcglone> I asked a couple clients for testimonials today
[02:53] <Unit193> dmcglone: I have many problems ;)
[02:53] <Cheri703> :)
[02:54] <dmcglone> I feel ya Unit193 I take crazy pills for mine ;-)
[02:54] <Unit193> dmcglone: It's really crapped, I'm going to be lucky if I can even get data off the HDD
[02:55] <dmcglone> can you use command line to backup
[02:55] <Cheri703> Unit193: can you plug the hdd in to another computer?
[02:55] <Unit193> dmcglone: Things took a turn for the worse...
[02:55] <Unit193> Cheri703: LiveCD hung on mount
[02:55] <Cheri703> I have an adapter that makes it a usb drive
[02:56] <Unit193> So do I... Lubuntu didn't see it (never used the device on that computer)
[02:57] <Cheri703> try it on another?
[02:58] <dmcglone> Unit193: why are you using Lubuntu or Xubuntu?
[02:58] <Unit193> dmcglone: Why are you using Ubuntu?
[02:59] <dmcglone> LOL I'm just asking if there is a perticular reason
[02:59] <Unit193> The lubuntu box can only mostly handle Lubuntu
[02:59] <dmcglone> is there a big difference between the 2?
[03:00] <Unit193> L and X? heck yeah! Ubuntu and Xubuntu have more in common...
[03:01] <dmcglone> I just thought that they were Ubuntu with different apps installed by default
[03:01] <Unit193> Xubuntu uses XFCE by default (not Gnome) Lubuntu uses LXDE
[03:01] <Cheri703> same as how kubuntu uses kde instead of gnome
[03:02]  * Unit193 is waiting 'til 11.04 to reinstall *ubuntu on main
[03:02] <Unit193> I don't know if I'm going with X or K, I like both
[03:04] <dmcglone> this begs the question, whatever happened to lindows?
[03:04] <Unit193> What?
[03:05] <dmcglone> last I heard they had to change their name, but don't remember what they changed it to
[03:05] <dmcglone> that was like 8 or so years ago
[03:06] <dmcglone> Ah it's Linspire
[03:06] <Unit193> Cheri703: Can you plug the IDE to SATA in after boot?
[03:06] <Cheri703> uhm, no
[03:06] <Cheri703> not that I'm aware of
[03:06] <Unit193> Sorry, IDE/SATA to USB
[03:06] <Cheri703> why would you need to do it after boot?
[03:07] <Cheri703> yeah, you can plug the usb in after boot
[03:07] <dmcglone> USB is "hot swappable"
[03:08] <Unit193> Yeah, was just making sure Ubuntu would detect it...
[03:08] <dmcglone> It should
[03:12] <Unit193> sudo fdisk -l |pastebinit > http://paste.ubuntu.com/591057/
[03:22] <dmcglone> Ok all, I'm out.
[03:22] <dmcglone> I'll catch you all later
[03:22] <Unit193> dmcglone: Have a nice night
[03:23] <dmcglone> U too Unit193
[03:36] <canthus13> Unit193: Reinstalled your box yet?
[03:37] <Unit193> canthus13: No, I need data off the HDD first, and I can't seem to read it (I'm starting to think bad HD)
[03:38] <canthus13> Unit193: double-bag it in freezer bags after it cools down. then freeze it overnight and try to grab as much off the drive as you can.
[03:38] <Unit193> canthus13: That was my next plan
[03:38] <Unit193> Thanks for the idea anyway
[03:38] <canthus13> :)
[03:51] <Unit193> I hope to get all of /home and maybe some of /etc
[03:56] <Unit193> canthus13: If you had to guess, how long do you think a freezer would give you?
[04:58] <canthus13> Unit193: Eleventy-seven minutes.
[04:58] <canthus13> Seriously, though, It all depends on the drive.
[07:58] <BiosElement> Ya know, mediawiki is a mess but it brings me comfort at times
[07:58] <BiosElement> When designing my own wiki system, I ran into a pretty big design bug where example.com/pagename?rev=3 would not actually be the third revision for the 'page' but the third revision of all pages on the site.
[07:59] <BiosElement> Here I was trying to think of a fancy solution, and I came up with a couple. Then I wonder what wikipedia does about it since I'm sure they're smarter then me
[07:59] <BiosElement> Answer: Nothing at all, their revision id's are a mess.
[15:39] <Derath-Srvr> :P
[16:29] <canthus13> Ooo... http://www.ugo.com/the-goods/smell-even-more-like-bacon-with-bacon-cologne
[16:42]  * Derath-Srvr smirks
[16:43] <Derath-Srvr> That would drive me insane... would be hungry all day
[16:53] <canthus13> :D
[19:53] <thafreak> Afternoon ohio
[19:53] <thafreak> Finally got around to trying out crunchbang on my netbook...
[19:53] <thafreak> I'm liking it
[19:54] <thafreak> course, I was running fluxbox on lucid on it prior...so it's obviously not too minimalistic for me :)
[19:58] <Unit193> thafreak: Sounds great! You're using the Openbox version?
[20:10] <thafreak> yep
[20:11] <thafreak> it's nice...
[20:11] <Unit193> Switching to debian now? ;)
[20:12] <thafreak> eh, I've typically always had something debian somewhere...
[20:12] <thafreak> but yeah, I kind of like how some projects are shifting to rolling releases using debian...
[20:12] <thafreak> mint debian edition is nice too
[20:13] <Unit193> I have tried some of the Mints, haven't tried that one yet...
[20:15] <thafreak> hmmm...I was almost impressed
[20:15] <thafreak> I inserted an encrypted SD card...and it prompted me for the password to mount it
[20:15] <thafreak> it didn't work...but it's close
[20:16] <Unit193> With the *ubuntus, I have to install the getdeb + launchpad repos
[20:23] <Derath-Srvr> Hey freak, Unit
[20:24] <Unit193> Hello Derath-Srvr! how was/is work?
[20:24] <thafreak> hey Derath-Srvr
[20:24] <Derath-Srvr> Getting there...
[20:24] <Derath-Srvr> Been wondering if it's possible to corrupt a VBox snapshot by loading it too many times
[20:25] <Derath-Srvr> And ya know, I wish there was a "Keep Above/Keep Below" option in Aero... getting tired of not having that
[20:26] <Derath-Srvr> has anyone ACTUALLY heard from spwelton in the last couple months?
[20:28]  * Unit193 only talks to people on here
[20:30] <Derath-Srvr> Only wonder to see if he's still doing Ubuntu Hours... I emailed him and still haven't heard bac
[20:33] <Unit193> Last seen  : Jan 13 02:11:29 2011 (12 weeks, 1 day, 17:21:11 ago)
[20:33] <Unit193> ^^ last freenode login with his user
[20:33]  * Derath-Srvr smirks
[20:34] <Unit193> You're not any type of ReLoCo lead?
[20:34] <Derath-Srvr> For Dayton...
[20:35] <Derath-Srvr> But can't say that I've actually run one... also seems like there are only about 2-3 users in the LoCo that are in my region
[20:35] <BiosElement> Amazing
[20:35] <Unit193> Doesn't say on: http://ohio.ubuntu-us.org/reloco
[20:35] <Derath-Srvr> There's a lot more in my LUG
[20:35] <Derath-Srvr> Yeah I checked that, and I've been removed from Dayton...
[20:35] <BiosElement> Gnome really needs to throw out some loose cannon 'volunteers' who think they're helping. :|
[20:36] <Derath-Srvr> Oh well, no loss there
[20:36] <Derath-Srvr> lol
[20:36] <Unit193> Derath-Srvr: AFAIK leads just show up and make sure everyone is nice
[20:37]  * Derath-Srvr shrugs
[20:38] <Unit193> The Ubuntu Hour I go to isn't even on there...
[20:42] <Derath-Srvr> Hmm... wonder when we'll start the planning for OLF this year, and is it going to be on me again
[20:43] <thafreak> How does the name "Logix Labs" sound?
[20:43] <Derath-Srvr> For?
[20:43] <thafreak> a company
[20:43] <Derath-Srvr> Purpose of company?
[20:44] <thafreak> cool stuff
[20:44] <Derath-Srvr> lol
[20:44] <thafreak> development of solutions
[20:44] <thafreak> to problems
[20:44] <Derath-Srvr> Sales? (Product selling?) Services? etc...
[20:44] <thafreak> sales?
[20:44] <thafreak> that's some one else's problem
[20:44] <Derath-Srvr> So services then...
[20:44] <Derath-Srvr> hmmm
[20:45] <Derath-Srvr> Not bad...
[20:45] <thafreak> services...that's also some one elses problem :)
[20:45] <Derath-Srvr> Development == services
[20:45] <Derath-Srvr> I was trying to figure if the name of the company fit what you wanted the company to do
[20:46] <BiosElement> Out of curiosity, would anyone care for a convore group? It might be a tad more useful for planning events then a mailing list.
[20:46]  * Derath-Srvr shrugs
[20:47] <thafreak> nah, development is not necessarily a service
[20:47] <thafreak> this is more of an incubator...
[20:47] <thafreak> for awesomeness
[20:47] <Derath-Srvr> O.o
[20:47] <Derath-Srvr> Changing the business model on the fly? lol
[20:47] <thafreak> not programmers for higher
[20:48] <thafreak> nah, just developing ideas...
[20:48] <Derath-Srvr> Okay, if incubator, it's good... if you're "providing" development work for people, then it's good, but not best...
[20:48] <thafreak> some one else can figure out how to make money with them...
[20:48] <Cheri703>  sort of like eureka mansion is/was?
[20:48] <thafreak> YES
[20:48] <thafreak> eureka
[20:48] <thafreak> like the bell labs of old
[20:49]  * Cheri703 toured eureka mansion YEARS ago with a gifted kid group
[20:49] <Cheri703> was SWEET
[20:50] <thafreak> wait...this is a place?
[20:50] <Cheri703> it's now "eureka ranch"
[20:50] <Cheri703> http://www.eurekaranch.com/
[20:51] <Cheri703> it was so freaking cool
[20:51] <Cheri703> this was at least 12 years ago
[20:51] <thafreak> soo....what do they do
[20:51] <Cheri703> it's in newtown ohio
[20:52] <Cheri703> it's an "idea" place
[20:52] <Cheri703> at least when I was there, they had rooms full of things to jog imagination and help you look at things differently
[20:52] <Cheri703> look at the site :)
[20:52] <Cheri703> yeah, so it was pre-1997 when I was there
[20:53] <thafreak> too much going on the site...couldn't focus...
[20:53] <Derath-Srvr> And Hi Cheri
[20:54] <Cheri703> hi Derath-Srvr
[20:54] <Derath-Srvr> gilbert, could you get in contact with me when you can? I have a question for you
[20:55] <Derath-Srvr> hope he's got a screen session going or something lol
[20:55] <Cheri703> ah, yes, gilbert I also have a question for you :)
[21:01] <Cheri703> or BiosElement if you're around
[21:02] <Unit193> http://www.unit193.org
[21:08] <BiosElement> Just ask heh
[21:09] <Cheri703> can someone update the ReLoCo page? mansfield's has been happening since december and we're not listed :(
[21:09] <BiosElement> canthus13: Don't you have ReLoCo access?
[21:10] <Unit193> Doesn't Jacob run the site?
[21:10] <Cheri703> I mean on the main website
[21:10] <BiosElement> Not sure
[21:10]  * BiosElement is going to eat, nag me if it's not done when I get back
[21:19] <Unit193> Are they still having U-H in Akron?
[21:31] <thafreak> Dunno, I haven't been to one in akron for a while
[21:33] <canthus13> BiosElement: I have no idea.
[21:34] <canthus13> BiosElement: I have access to the google calendar, but I don't think I can update the page.
[21:40] <Cheri703> http://consumerist.com/2011/04/the-magical-chinese-hard-drive.html
[21:57] <Derath-Srvr> heading home... laters
[21:57] <Unit193> Have a nice one Derath-Srvr!
[21:58] <thafreak> http://blog.adamnash.com/2010/11/29/why-t-shirts-matter/
[22:01] <Cheri703> Oh, so...I figure I'll toss this up in here, with the MAJOR disclaimer that I COMPLETELY understand if you look and say "HA, NO" and apologies in advance if you think it's crappy of me to do so: http://cheri703.chipin.com/uds-stuff
[22:24] <canthus13> Cheri703: I think I posted that drive last night... pretty funny stuff.  I've gotten one of those looped thumb drives before.  I was lucky.. Mine was a 4gb masquerading as a 16gb.
[22:24]  * canthus13 fixed it with the HP flash drive tool.
[22:48] <Cheri703> \o/ I win!
[22:49] <canthus13> eh?
[22:49]  * Cheri703 used the word "Blargh" as the dual factor authorization word for new online banking thing :)
[22:49] <canthus13> HAHA!
[22:49] <Cheri703> had to be at least 6 characters
[22:49] <Cheri703> that was the first thing that came to mind
[22:51] <canthus13> That's awesome. :)
[22:51] <Cheri703> so now every time I log on, it will have an image of the word Blargh :)
[22:51] <Cheri703> and I will chuckle
[22:51]  * Cheri703 is far too amused by this
[22:52] <canthus13> Simple pleasures... :)
[22:58] <Unit193> After the drive is in the freezer for a long time, do you just pull it out and plug it in?
[23:14] <canthus13> Yup.
[23:45] <Unit193> Hello rokkett77
[23:51] <rokkett77> heloo all
[23:51] <rokkett77> hello that is