[00:45] <al12gamer> I got Ubuntu running on my cr-48 :)
[00:45] <Cheri703> yay
[00:46] <al12gamer> anyone else here get one?
[00:46] <al12gamer> However I used the easy scripted method.......http://chromeos-cr48.blogspot.com/2010/12/easy-way-to-install-ubuntu-on-your-cr.html
[00:47] <al12gamer> I hate that we're forced to use Windows Vista in our highschool. I'm on my vista machine right now. I'd rather be on my Ubuntu 10.10 cr-48 or my Fedora 14 desktop
[00:47] <al12gamer> Why can't schools just go open source? Our Java teacher agrees with me and asks them every year to switch to Linux. We'd save $1000 the first year, if not more.
[00:50] <al12gamer> Anyway, feel free to check out my blog http://technation.tumblr.com sometime, perhaps that'd be an easy way to communicate. I'll be on here later or another day in the future
[01:17] <Cheri703> hmm...ok
[03:40] <lostConnection> if I downloaded a .tar.gz file do I just have to type something like "sudo install" to install it? Sorry still getting used to terminal commands
[03:41] <Cheri703> uhm....I can never remember
[03:42] <canthus13> lostConnection: You usually have to extract it into a folder first.
[03:42] <canthus13> then you read the README.
[03:42] <canthus13> then follow the directions in the README.
[03:43] <lostConnection> hahaha lol it doesn't have a README is some software that my professor has created in his research
[03:46] <canthus13> I'd ask him, then.  Is there a makefile?
[03:46] <canthus13> ...or a .bin or .run?
[03:49] <lostConnection> oh wow I guess there was already an executable in the compressed folder.
[03:49] <lostConnection> I don't know exactly what I'm looking at but I'm getting somewhere now.
[03:51] <canthus13> extract the file, chmod +x <filename>, then ./<filename from the folder it's in.
[03:51] <canthus13> that should execute it.
[03:54] <lostConnection> hmm.. well I guess I never really knew exactly what this is supposed to do. When I ran it with ./ it just left me with a blankscreen so I can only assume that it is running.
[03:57] <lostConnection> I guess it is some kind of mark up language. Really all of this is over my head at this point. I'm just trying to toy around with it. It's called src2srcml he has it distributed online.
[04:31] <canthus13> lostConnection: http://www.sdml.info/projects/srcml/beta/src2srcml.html
[04:32] <canthus13> lostConnection: that's the manpage.
[04:37] <lostConnection> well damn I didn't even find this in the little bit of scanning I did on his site. This is definitely better than all of the stuff that I found on the site.
[04:37] <canthus13> Heh.
[16:57] <thafreak> whoa....who was asking about srcml???
[16:57] <thafreak> I'm pretty sure that was developed here at kent...
[16:57] <thafreak> interesting
[17:00] <thafreak> Hey ReLoco leads...
[17:01] <thafreak> I've got a few older machines...and I'd like to get them into the hands of some kids who want to tinker, but have no spare hardware
[17:01] <thafreak> Do any of you know of such up and coming linux users in your loco?
[17:11] <canthus13> thafreak: Only my kids, and I'm up to my ears in spare hardware.
[17:11] <canthus13> I'll keep an eye out, though.
[17:12] <thafreak> well, yeah I knew you were in the same boat as me, or very similar... :)
[17:12] <canthus13> Heh.
[17:13] <thafreak> I'm probably going to get my basement down to two embedded boards, two vm servers, and that might be it (besides switches)
[17:13] <canthus13> I've only got 3 machines running in my basement, and one is my kid's sauerbraten server.
[17:13] <thafreak> decided to not have a dedicated storage system, but throw disks in the new vm host, and have a virtual file server...not like performance is uber crucial in my basement :_
[17:13] <thafreak> :)
[17:14] <canthus13> Heh. I've got my file server, my web/mail/shell server, and that sauerbraten server (which I also use to burn CDs because the burner on my laptop has decided it doesn't like to burn.)
[17:15] <thafreak> nice...
[17:15] <thafreak> I still have other machines, but those are elsewhere in the house, and turned off most of the time (hopefully)
[17:15] <canthus13> I'm thinking about upping the memory and tossing a qaud-core into it and making it do dual duty as a freenx server as well.
[17:16] <thafreak> quad core, make it a vm host man
[17:16] <canthus13> Oh. Heh. My oldest has a laptop, my youngest has a desktop, my wife has a laptop.
[17:16] <canthus13> If I find a need for a VM host.
[17:16] <thafreak> My old one is only a dual core athlon, with 4gb of ram, and it does virtual desktops plus everything else fine
[17:17] <thafreak> well, nxserver from nomahchine did eat a lot of CPU...and memory...
[17:17] <canthus13> right now my laptop is serving up FreeNX so I can use it from work... I'd like to shift that duty over to another machine.
[17:17] <thafreak> never used freenx much...
[17:17] <canthus13> Really? Mine uses practically nothing.
[17:18] <canthus13> Even with two users logged in, the only CPU hog is plugin-container.
[17:18] <thafreak> I even separated it out at one point, had a machine run just the nx server from no machine, and ran the desktop on a separate vm
[17:18] <thafreak> interesting, so you use freenx from ppa, or compiled from source?
[18:44] <canthus13> thafreak: Umm... ppa.
[18:49] <canthus13> ...I think.
[18:49] <canthus13> thafreak: I used this guide.
[18:49] <canthus13> https://help.ubuntu.com/community/FreeNX
[20:30] <Unit193> 3 instances of VLC, 2 sound cards and 2 sets of earbuds...
[21:04] <canthus13> Unit193: how many ears do you have?
[22:42]  * Cheri703 just reassembled client's zune and is praying it works
[22:43] <Cheri703> hey canthus13
[22:44] <Unit193> canthus13: 2 people
[22:44] <Cheri703> ?
[22:44] <canthus13> 2 people?
[22:44] <canthus13> Cheri703: Hey.. freaking server dropped offline. :(
[22:44] <Cheri703> no good
[22:44] <canthus13> Yeah...
[22:44] <Cheri703> at least you know where it is ;)
[22:44] <Unit193> canthus13: not 4 ears....
[22:45] <canthus13> Oh. Ok.
[22:45] <canthus13> Cheri703: True.
[22:45] <canthus13> I'm hoping a cable came loose... I was doing some rearranging down there yesterday.
[22:47] <Cheri703> I just put my client's zune back together...had to solder on new battery, hoping I didn't kill anything -_- it's charging now
[22:48] <canthus13> cool...
[22:49]  * Cheri703 is always nervous when soldering on boards...I think I bumped the chip with the soldering iron...not extensively, just....frightened
[23:40] <Cheri703> it is working!
[23:40] <Cheri703> hooray
[23:40] <Cheri703> it didn't at first, but now it is :)


[00:58] <robert_ancell> tdaitx, hey, are you working on bug 1503450 at the moment? I didn't see your branch
[01:17] <tdaitx> robert_ancell, yeah, I made a mistake fetched ubuntu/mir/, thus the merge had a lot of differenced and conflicts, I'm redoing it for lp:mir now
[01:17] <robert_ancell> tdaitx, ok, I'll delete my branch - I added some comments on the bug.
[01:19] <tdaitx> robert_ancell, nice! just saw your comments, thanks for the help =)
[01:19] <robert_ancell> tdaitx, np, thanks for finding the issue :)
[01:20] <tdaitx> robert_ancell, I had a feeling that Requires.private might be better, but I'm not that familiar with pkgconfig
[01:20] <robert_ancell> Requires.private is super confusing
[01:26] <tdaitx> robert_ancell, I saw your commit now, go ahead with it... I'm acquiring experience and evidence to apply for ubuntu dev, but your commit is way better, so go ahead =)
[01:27] <robert_ancell> tdaitx, ok
[01:27] <tdaitx> robert_ancell, btw, your commit still uses Requires instead of Requires.private
[01:28] <robert_ancell> tdaitx, ah, I forgot the last commit!
[01:28] <tdaitx> =)
[04:23] <ScottK> slangasek: If the python3.4 regression made it to updates, shouldn't another SRU be uploaded that reverts the regression?  Simply removing it from updates doesn't get the regression off the systems where it was installed.
[04:24] <slangasek> ScottK: yes, but as the SRU was a new upstream version I've not been eager to initiate the 3.4.3.really.a.ball.of.lint dance.  I will do so if there's no progress in a day or so
[04:24] <ScottK> OK.
[04:25] <ScottK> I'm a bit surprised Ubuntu is doing full version updates of Python.  I'm not particularly surprised it didn't end well.
[04:51] <sitter> pitti: http://autopkgtest.ubuntu.com/packages/k/kdevelop/wily/armhf/ probably needs a retry? Temporary failure resolving 'ftpmaster.internal'
[05:16] <pitti> bdmurray: I'll look in the bug and reply there, but it seems cjwatson already responded with the reason
[05:17] <pitti> sitter: yes, retrying
[05:17] <pitti> Good morning
[07:14] <dholbach> good morning
[07:16] <seb128> hey dholbach
[07:16] <dholbach> salut seb128
[07:18] <dholbach> seb128, dpm: https://translations.launchpad.net/ubuntu/ says translation focus is vivid - is that right?
[07:19] <seb128> dholbach, I guess that should be changed to wily
[07:19] <dpm> dholbach, seb128, done, well spotted
[07:19] <seb128> thanks
[07:19] <dholbach> thanks
[07:24] <rbasak> Any thoughts on an eventual SRU for bug 525674? Appropriate? Patch too invasive?
[07:24] <rbasak> infinity: ^
[07:26] <pitti> rbasak: oh my, please
[07:26] <pitti> rbasak: it doesn't seem very invasive to me, it merely runs the apt-check bits in the background, no?
[07:26] <pitti> i. e. ( existing code ) &
[07:27] <pitti> (and yes, agreed that it is really annoying)
[07:32] <cpaelzer> the only other than the ( existing code ) & is the try to fix concurrent updates
[07:32] <cpaelzer> this became more obvious with the async version, but was broken before as well for multi logins
[07:33] <pitti> cpaelzer: ah, by redirecting into $tmpfile first, and atomically moving to $stamp
[07:33] <cpaelzer> pitti: that was the idea
[07:34] <cpaelzer> pitti: and a cleanup added on rbasak first review to avoid stale files in /tmp
[07:34] <pitti> for stable SRUs this seems fine; for wily and upstream, coud this perhaps move into /etc/cron.daily/apt or a similar daily cronjob?
[07:34] <pitti> running this check on every login seems like a waste
[07:35] <cpaelzer> pitti: I wanted to keep the update policy as close to the original as possible - anyone can later on move the check somewhere else
[07:35] <cpaelzer> but for the given update I'd keep it small
[07:35] <cpaelzer> it is a first step to move the updating somewhere else, but for now just tries to fix the immediate issue
[07:36] <pitti> ack
[07:37] <rbasak> pitti: yeah it just moves things to the background, but though I like the approach and I can't find anything wrong with it, it feels like it's ripe for odd bugs to crop up to me. IOW I wouldn't be surprised if something came up.
[07:38] <rbasak> I guess a cronjob is reasonable, given that it's always going to be out of date on first login.
[07:38] <pitti> the obvious change in behaviour is that the first time that you log in it won't show up, but that seems fine
[07:38] <pitti> it's almost certainly right after a fresh install
[07:38] <pitti> right
[07:39] <pitti> the cronjob avoids concurrency and blocking login at the same time, so structurally it seems even easier to me
[07:39] <rbasak> What's almost certainly right? cpaelzer's patch?
[07:39] <pitti> but this is running as user, so it doesn't take an apt lock, does it?
[07:39] <rbasak> It does run as root.
[07:40] <pitti> rbasak: I mean the first login is almost certainly after a fresh install, i. e. it doesn't matter if it doesn't do the check there
[07:40] <rbasak> Ah
[07:40] <pitti> I meant "right after" -> immediately after, not "it is right"
[07:40] <rbasak> I meant first login after a while, ie. when it's slow.
[07:40] <cpaelzer> still it takes no apt lock
[07:40] <pitti> yay language ambiguities :)
[07:40] <cpaelzer> the call to apt-check runs fine as user, so no apt lock involved
[07:41] <rbasak> On a default system, what runs apt-get update to keep that up to date?
[07:41] <cpaelzer> rbasak: yeah this would be the right place to update the file ...
[07:41] <pitti> rbasak: supposedly /etc/cron.daily/apt ?
[07:41] <rbasak> ie. is installing unattended-upgrades or similar required to keep this updated, or are we running regular apt-get updates already?
[07:42] <pitti> ah, is that being called through PAM? otherwise, how can it run as root when you log in as user?
[07:42] <pitti> rbasak: we've done for many years
[07:42] <rbasak> Yeah update-motd is a PAM module
[07:47] <cpaelzer> actually in /etc/cron.daily/apt is even already a function that updates a marker update_stamp in case anytihng interesting had changed
[07:47] <cpaelzer> it updates various timestamps after autoclean, unattended-upgrade, dist-upgrade, ...
[07:48] <cpaelzer> pitti: rbasak: that would be just the spot to update the info for the motd
[07:48] <cpaelzer> so again not very invasive ...
[07:48] <cpaelzer> it would also avoid having to create a new daily cron and so on
[07:49] <rbasak> Crossing an abstraction boundary here.
[07:49] <cpaelzer> rbasak: between packages?
[07:49] <rbasak> Which is OK, but maybe quite a bit of this functionality needs to move into the package supplying /etc/cron.daily/apt
[07:49] <rbasak> cpaelzer: right
[07:49] <rbasak> Or maybe all of the logic even
[07:50] <cpaelzer> rbasak: but you are right and it would be an issue - the apt-check command is part of update-notifier and not apt (despite its name)
[07:50] <rbasak> Ah
[07:50] <rbasak> And we can't really have apt depend on update-notifier
[07:50] <cpaelzer> so it would force everybody (apt is always there) to have update-notifier :-/ not what I want
[07:51] <rbasak> OK so the logic has to stay in update-notifier
[07:51] <cpaelzer> yes
[07:51] <rbasak> What's the cleanest way to cross the boundary?
[07:51] <rbasak> update_stamp
[07:51] <rbasak> mvo: ^^ any opinion?
[07:52] <cpaelzer> rbasak: the cleanest is probably to use as few dependencies as possible and just do a bi-daily update or so
[07:52] <rbasak> Maybe have an update-notifier cron.daily job check update_stamp as left by apt's cron job, and if it is newer than the cached motd then update it?
[07:52] <cpaelzer> no hooks or relying on knowing another packages file names
[07:52] <rbasak> cpaelzer: that sounds reasonable
[07:53] <rbasak> I think we prefer to use cron.daily where possible, so everything runs at once
[07:53] <cpaelzer> rbasak: to bad there is no ordering in there
[07:53] <cpaelzer> rbasak: running AFTER each cron.daily/apt would be great
[07:54] <cpaelzer> wait a second
[07:54] <cpaelzer> there is a /etc/cron.daily/update-notifier-common - WTF
[07:56] <pitti> oh, I'm in the news! http://lwn.net/Articles/657345/
[07:56] <mvo> rbasak: sorry, wasn't following - if apt-check needs to move e.g. into apt itself we can consider that. I need double check if its a good fit
[07:56] <mvo> pitti: woah!
[07:57] <rbasak> mvo: I'm not sure apt-check itself needs to move, but we want to change the logic around when the update-motd stuff happens
[07:57] <rbasak> mvo: so it doesn't block login. So from cron maybe, but not sure where the best fit is.
[07:57] <rbasak> Preferably after apt-get update runs
[07:57] <rbasak> brb
[07:58] <didrocks> pitti: with a great smile, as usual :)
[07:58] <pitti> and one of my favourite T-shirts :)
[07:58] <didrocks> pitti: classic Monkey Island ;)
[07:59] <cpaelzer> rbasak: if we want to be "just after" updates we would need to move apt-check to the package "apt"
[08:00] <cpaelzer> rbasak: but if we want to keep it simle we can just hook into the already existing /etc/cron.daily/update-notifier-common
[08:00] <mvo> rbasak, cpaelzer: we could add apt-check --human-readable as a hook into APT::Update::Post-Invoke-Success
[08:00] <cpaelzer> rbasak: still for now keeping the fix as simple as it is might be ok - on the other hand nothing stays longer than a good workaround :-/
[08:00] <mvo> and make it write the data to a file that is just cat on login
[08:01] <mvo> this way its always up-to-date and can still be part of u-m-common
[08:01] <mvo> the downside is a lightly slowe apt-get update, but then the cache is hot so it should be fine
[08:01] <mvo> (unless I miss something)
[08:02] <cpaelzer> mvo: ah so one could hook just after an update with APT::Update::Post-Invoke-Success without a reverse dependency
[08:02] <cpaelzer> yet I see a small fix getting more and mre complex :-)
[08:03] <cpaelzer> pitti: seems to be monkey island day - just got this refferred this morning https://chinstrap.canonical.com/~smb/askme-2.png
[08:04] <pitti> cpaelzer: you fight like a cow!
[08:04] <smb> I am shuddering :-P
[08:05] <pitti> oh the times -- I can't be grateful enough to the makers of ScummVM
[08:06] <mvo> cpaelzer: yeah, exactly. this might actually reduce complexity but yeah, its different from what was done before
[08:06] <cpaelzer> mvo: well /etc/apt/apt.conf.d/ seems rather clear - just looked into that
[08:06] <cpaelzer> mvo: do you know how the new numbers are made up there - just pick one for ordering?
[08:06] <pitti> cpaelzer: as I said, I think this fix is still good for stables; it's just not very elegant
[08:06] <pitti> (for the future, I mean)
[08:07] <pitti> not elegant> the whole current architecture I mean, not the fix in particular
[08:07] <cpaelzer> pitti: I can read your shirt's text - so I'm obliged to like to over-engineer
[08:08] <cpaelzer> and I like the APT::Update::Post-Invoke-Success approach mvo suggested
[08:08] <mvo> cpaelzer: yeah, just one for ordering
[08:09] <kruger> hi, i've rebuild a ubuntu dvd with a new kernel version (taken from ubuntu source) but i'm unable to boot in uefi mode -i've got (initramfs) error-, but i'm able only to boot in bios mode. Whats' wrong?
[08:09] <cpaelzer> rbasak: maybe the fix as is for SRU (if we want it as SRU) and the more complex but eventually cleaner one for wily&upstream ...
[08:18] <cpaelzer> mvo: regarding slower apt-get update - we can still keep it asynchronous, so it shouldn't add a reasonable delay
[08:28]  * mvo nods
[08:52] <rbasak> cpaelzer, mvo: I like the APT::Update::Post-Invoke-Success idea. You're suggesting the update-notifier packaging dropping something into /etc/apt/apt.conf.d/ that sets it, right? And the script will just cache the result for the update-motd script later?
[08:52] <rbasak> So cpaelzer's patch for the SRUs, and this for Wily/Wily+1?
[08:52] <pitti> that sounds wonderful
[08:53] <cpaelzer> rbasak: yes
[08:53] <rbasak> +1
[08:53] <cpaelzer> rbasak: ok, that sounds like an agreement - I'll come up with some code for that
[08:53] <pitti> then it would run exactly once, exactly when needed, and there's no collision from multiple logins, or delays of those
[08:53] <rbasak> It's really elegant. The cache should be hot (and we could background it if needed as cpaelzer says), and then the cached output will always be current.
[08:53] <rbasak> Right.
[08:54] <rbasak> If backgrounding then need to be careful about collisions.
[08:54] <rbasak> I find the "watershed" program really handy for this. IMHO it should be somewhere more common.
[08:56] <rbasak> mvo: would multiple things that set APT::Update::Post-Invoke-Success in apt.conf.d add to the list or override?
[08:56] <rbasak> Ah, nm. I think the manpage is telling me that it will append.
[08:56] <cpaelzer> rbasak: there are already 4 in my current system
[09:06] <pitti> rbasak: flock from util-linux? it's okay to just fail if it's already running
[09:07] <pitti> watershed seems like a very rare corner case -- ISTM that either you only ever want one run (potentially triggered several times), or serialize all triggered runs
[09:07] <pitti> watershed runs the program once or twice, which I find a bit odd?
[09:08] <pitti> ah, this is to "mop up" the extra requests with just one extra run, I see
[09:08] <pitti> nevermind
[09:09] <pitti> but in this case flock is better
[09:11] <rbasak> pitti: say I run apt-get update twice, and we async the apt-check. If apt-check hasn't finished by the time my apt-get update finishes, I want to run it again to get it up to date.
[09:12] <rbasak> pitti: so I think watershed is the correct logic here ideally. But it's not worth pulling in a dependency just for that.
[09:12] <pitti> running apt-check twice in a row sounds like a waste, isn't it?
[09:13] <rbasak> Not if the first one started too early to produce up-to-date results
[09:14] <rbasak> As another example I use watershed + rsync to trigger an rsync when a new file arrives.
[09:14] <rbasak> Cheap and nasty 1-way realtime replication
[09:59] <cjwatson> infinity: Thanks, fixing and taking that as an approve vote.
[10:03] <infinity> cjwatson: I didn't look at it with context.  Is that limited to dirty suites, or will it magically create InRelease files for all old suites on first run?
[10:04] <cjwatson> infinity: All of them.
[10:04] <cjwatson> Which I think is what we want?
[10:04] <cjwatson> It does end up changing ordinarily immutable stable suites, but only to the tune of creating that file
[10:05] <infinity> cjwatson: yeah, that's fine.  Lemme just quickly look at context.
[10:06] <infinity> cjwatson: Okay, gpg_opts is responsible for key-picking, shiny.  Have you tested that the double-signing trick works for InRelease as well as detached sigs?
[10:06] <infinity> (Don't see why it wouldn't, but would be nice to make sure apt won't barf, since it'll suddenly favour InRelease as soon as it leaps into existence)
[10:07] <cjwatson> Not specifically, but let me try.
[10:08] <xnox> arges: your core-dev membership is expiring in 9h
[10:08] <infinity> Which reminds me, I need to cargo-cult that bit for ubuntu-cdimage and re-sign some history.
[10:10] <xnox> soren and james_w expired =( oh well.
[10:12] <Laney> I usually check the mail to see if expired people were active
[10:14] <cjwatson> infinity: OK, after signing wily's Release file with both my old and new personal keys: http://paste.ubuntu.com/12703167/
[10:14] <cjwatson> which looks fine to me
[10:15] <cjwatson> Let me just try with trusty and precise to make certain
[10:16] <cjwatson> I think precise has InRelease support disabled
[10:16] <apw> pitti, are you able to get a ps listing out of one of the lxc hangers, as the logs are not complete (according to stgraber)
[10:18] <infinity> cjwatson: Huh.  Does apt warn about a single missing key on the detached sigs too?
[10:18] <cjwatson> trusty behaves the same way except that I have to use a short key ID to apt-key del
[10:18] <cjwatson> infinity: Pretty sure I remember it doing that
[10:18] <infinity> cjwatson: That seems kinda crap, as retiring one from the keyring entirely would make double-signed suites throw warnings.
[10:18] <infinity> cjwatson: But if it behaves the same for both, that's not a problem for today.
[10:18] <cjwatson> Yep, it sure does.
[10:19] <cjwatson> (schroot -c trusty-amd64 -u root, apt-key del 437D05B5, apt-get update)
[10:19] <infinity> cjwatson: Speaking of.  Can we drop the old sig (and key) for 16.04?  Pretty sure we can.
[10:19] <cjwatson> I assume we'd stop double-signing if we were doing that.
[10:19] <cjwatson> infinity: Should be able to.
[10:19] <cjwatson> infinity: Let's do it when we open?
[10:20] <infinity> And yeah, we should stop double-signing and drop the key together, given the warning being otherwise very scary. :P
[10:20] <infinity> cjwatson: Is there any argument for rotating a new key in, rather than just dropping the old one?
[10:20] <cjwatson> Possibly, but we'd need to generate one.
[10:20] <infinity> Well, yes.
[10:21] <infinity> But I think Bluefin has nearly enough shards to do that.
[10:21] <cjwatson> I think we would have three at the release sprint, if we warn a couple of sysadmins.
[10:23] <cjwatson> Right, and precise ignores InRelease, as I remembered.
[10:23] <cjwatson> So this looks fine.
[10:23] <infinity> cjwatson: Excellent.  +1 from me, then.
[10:24] <cjwatson> Let's blow stuff up while I have plenty of day left. :-)
[10:25]  * infinity is going to go grab a bit of food, since sleep has completely eluded him.
[10:25] <infinity> cjwatson: I'll be back in time to see the world burn.
[10:25] <hyperair> why do you think there'll be any world left to burn?
[10:26] <cjwatson> Deployed.
[10:29] <infinity> Ahh, a quick proposed-only run too.
[10:29] <infinity> Handy.
[10:29]  * infinity watches.
[10:32] <cjwatson> Haha it's resigning dapper
[10:32] <cjwatson> pepo FTW
[10:32] <cjwatson> (not that it matters, it won't be mirrored)
[10:32] <infinity> Yeah. ;)
[10:33] <infinity> cjwatson: Throwing stuff at a PPA to see how apt loves the new ftpmaster.
[10:33] <cjwatson> It'll be fiiiine.
[10:34] <infinity> cjwatson: https://launchpad.net/~adconrad/+archive/ubuntu/staging/+packages
[10:34] <cjwatson> Looking good so far.
[10:35] <infinity> That really shrinks the apt-get update output.
[10:35] <infinity> cjwatson: I don't see precise ignoring it at all...
[10:36] <infinity> cjwatson: It totally favoured InRelease.
[10:36] <infinity> (But also seems to have worked)
[10:36] <cjwatson> Definitely ignored it here, but OK.
[10:36] <infinity> https://launchpadlibrarian.net/220504260/buildlog_ubuntu-precise-amd64.hello_2.7-2_BUILDING.txt.gz
[10:36] <cjwatson> Oh
[10:36] <cjwatson> Baseline precise
[10:36] <cjwatson> It was disabled in precise-security
[10:37] <infinity> Ahh, cute.
[10:37] <infinity> Not that I care, as we implicitly trusty ftpmaster.internal.
[10:37] <infinity> But a bit entertaining that we're using, I assume, an insecure codepath.
[10:39] <cjwatson> Yeah, I think it's not particularly worse than before, AIUI it's not like the natty thing where any signed material anywhere can be used to construct a compromise.
[10:39] <cjwatson> Now I wonder how many layers of caching are between me and archive.u.c
[10:40] <infinity> cjwatson: Looks happy across the board.
[10:41] <cjwatson> Great.  An update here hasn't spotted it yet, but I guess syncproxy will take a while to catch up.
[10:41] <cjwatson> Thanks for the test.
[10:41] <infinity> syncproxy runs in < 2m, IIRC, but frontends are a little more slack.
[10:42] <pitti> apw: yes, I can start the test and then lxc-attach to it to do anything you (or stgraber) likes
[10:43] <apw> pitti, i think there are two existing ones jammed right now (well were last i looked)
[10:43] <apw> pitti, but i think the ones which are working are the lxc ones, it is the proper instance ones which are jamming
[10:44] <pitti> apw: lxc-in-cloud-instance (i386, amd64) work fine; lxc-in-lxc (armhf, ppc64el) hang indeed
[10:44] <cjwatson> infinity: There was a lot of mirroring infrastructure to fix up.  Hopefully I got it all.
[10:44] <pitti> apw: running the test locally fails fast, so I guess it's trying to download something and fails on the proxy or something such
[10:45] <infinity> cjwatson: Oh.  Balls.  You did fix all the 2-stage scripts to exclude InRelease, I hope?
[10:45] <cjwatson> infinity: Yes
[10:45] <cjwatson> Or at least I certainly tried
[10:45] <cjwatson> infinity: See the enormous pile of private MPs attached to the bug for misc deployment stuff
[10:45] <infinity> cjwatson: Including ports, which doesn't use the one from the charm because reasons.  Or was that us.ports?
[10:46] <cjwatson> infinity: Yes, I got ports
[10:46] <cjwatson> And us.ports
[10:47] <cjwatson> us.ports is the weird one, I think.
[10:47] <infinity> cjwatson: So, they worked around the juju issue that wasn't allowing them to actually deploy to mirror frontends before? :P
[10:47] <cjwatson> infinity: https://rt.admin.canonical.com/Ticket/Display.html?id=84674
[10:47] <infinity> cjwatson: Yeah, ports itself is a syncproxy (so, magicmirror), us.ports uses a fork of the 2-stage mirror script instead of the generic one, for some reason or other.
[10:47] <cjwatson> I think they may have done it by hand again.
[10:48] <cjwatson> Get:1 http://archive.ubuntu.com wily InRelease [218 kB]
[10:48] <cjwatson> aha
[10:48] <cjwatson> http://archive.ubuntu.com/ubuntu/dists/wily/ shows differing timestamps though, why
[10:49] <cjwatson> I guess rsync doesn't update them if the file contents haven't changed
[10:49] <infinity> magicmirror resets some timestamps.
[10:49] <infinity> Because lamont.
[10:49] <cjwatson> Oh, I removed that but maybe it hasn't been deployed
[10:50] <cjwatson> https://code.launchpad.net/~cjwatson/canonical-magic-mirror/remove-timestamp-hacking/+merge/272718
[10:50] <infinity> ...
[10:50] <infinity> How is InRelease *older* than Release?
[10:51] <cjwatson> Because magic-mirror knows to touch Release/Release.gpg but not InRelease
[10:51] <infinity> Oh, right.  So, it is the lamont bit.
[10:51] <infinity> Gross.
[10:51] <infinity> We fixed that on the publisher side ages ago, right?
[10:51] <cjwatson> Except I thought I'd got a magic-mirror change deployed to touch InRelease, actually
[10:51] <cjwatson> So that's a bit weird
[10:52] <cjwatson> infinity: I did the last bit of the fix quite recently.
[10:52] <apw> your removal is unmerged
[10:53] <infinity> It is, but it should be touching InRelease, looking at the current code.
[10:53] <infinity> So a bit WTF.
[10:54] <infinity> Oh, but that was recent too.  So maybe never actually deployed.
[10:54] <cjwatson> apw: Right, I know the removal is unmerged but indeed the previous allegedly-deployed version touched InRelease
[10:54] <cjwatson> Chasing that up
[10:56] <pete-woods> pitti: is there anything I can do to help expedite the dbusmock stuff? write the release notes, perhaps? I've checked the tests with pep8, pyflakes, etc already
[10:57] <sil2100> pitti: ping! Hey, we didn't seem to get langpack-o-matic translations yesterday uploaded to the overlay
[10:57] <sil2100> pitti: did anything happen to those?
[11:03] <infinity> cjwatson: So, I'm kinda hoping this is coincidence, but we also seem to have blown up the frontends. :P
[11:03] <cjwatson> ?
[11:04] <infinity> apt-get update is now downloading at a snail's pace.  Or not at all.  Undecided.
[11:04] <infinity> I thought it was a local thing, but another user just complained.
[11:04] <cjwatson> Maybe they're remirroring lots or something?
[11:05] <infinity> Or deleting half the archive.
[11:07] <infinity> cjwatson: Can you reproduce, or am I and said user just going insane?
[11:07] <cjwatson> I can
[11:08] <cjwatson> Though I wouldn't normally put much stock in a network problem visible from behind my ADSL
[11:08] <cjwatson> (Or what could easily be a network problem)
[11:08] <infinity> Okay, load must be through the roof.  telnet just took 10s to get apache to say hi on one of them.
[11:08] <infinity> This seems like a bad sign.
[11:09] <cjwatson> See #is-outage
[11:27] <doko> pitti, please override node-srs's autopkg test again (triggered by gdal)
[11:34] <doko> infinity, or you ^^^
[11:55] <pitti> sil2100: I rebuilt the -base packages manually to fix the desktop translations, so the cronjob didn't run again
[11:55] <pitti> sil2100: I can run it manually if needed
[11:56] <sil2100> pitti: yes, please :)
[11:56] <pitti> sil2100: running
[11:56] <sil2100> We're in freeze so we want to build out image candidate
[11:56] <sil2100> Thanks!
[11:56] <rvr> pitti: Cool, thanks!
[11:57] <didrocks> slangasek: doko: shouldn't we rather upload a revert for bug #1500768 matching the previous content of -security as the faulty SRU has been released for quite a while (and so most of people upgraded to it) and there is no assignee anymore working on it?
[11:57] <pitti> doko: done
[11:58] <sil2100> barry: ^
[12:10] <doko> didrocks, I'm looking at it, and I think we should not yet
[12:11] <didrocks> doko: can you assign yourself to this bug please? The regression is already around for a couple of weeks
[12:11] <doko> didrocks, nobody told me until recently
[12:12] <didrocks> doko: last week was my first ping for you about it
[12:12] <doko> "couple of weeks" != last week
[12:13] <didrocks> doko: the issue started when python3.4 hit -updates, so a couple of weeks
[12:13] <didrocks> doko: then, time for me to debug it (didn't want to blame python before checking it's not my side), I did debug it when I could
[12:13] <didrocks> and found the exact interaction issue last Tuesday (so a week ago)
[12:14] <didrocks> but people DO experience it for a couple of weeks
[12:14] <didrocks> which is what matters here IMHO
[13:08] <infinity> jibel, pitti, Laney, apw: Can you guys reply to that release sprint email, so clan knows what's up?
[13:08] <infinity> jibel: You especially, since I wasn't sure if you wanted to come, or send a minion, or both.
[13:08] <seb128> when/where is it?
[13:09] <infinity> seb128: London, release week.  Unless you meant where's the mail, in which case, it was sent to the people mentioned. :P
[13:09] <seb128> no, just curious
[13:09] <seb128> desktop team is in London next week
[13:09] <seb128> but that's one week before
[13:09] <seb128> so maybe Laney wins the right to have another week in the office ;-)
[13:13] <pitti> infinity: not quite sure yet; I've been/will be travel quite a lot these days, and at the weekend before we have a big family event in Dresden
[13:14] <Laney> replied, ta for the reminder
[13:14] <infinity> pitti: Sure.  If you think it's not going to work for you, cyphermox might be a better choice.
[13:14] <infinity> pitti: But he's also a more expensive choice, so I need to make that call soon. ;)
[13:14] <cyphermox> oi
[13:27] <lamont> infinity: the lamont bit was just updating it to be faster at merging all of hte stay of execution files
[13:27] <lamont> stay of execution predates me\
[13:28] <infinity> lamont: I think the lamont thing I was blaming you for was the timestamp mangling in magicmirror.  Which was totally you.
[13:28] <infinity> lamont: But that was hours ago, and I blame you for a lot of things, so maybe I'm mistaken. :P
[13:28] <lamont> infinity: I have no memory of that action.
[13:28] <infinity> lamont: There's a bug log that has memory on your behalf. ;)
[13:29] <lamont> I'll believe that
[13:29] <infinity> lamont: https://bugs.launchpad.net/launchpad/+bug/1033581
[13:35] <xnox> barry: 3.5 not default?
[13:36] <xnox> =(
[13:37] <barry> xnox: it will be for xnoxian xenomorph
[13:37] <xnox> barry: but i need it now =) to reproduce openstack bugs which modify ordereddicts whilst interating it ;-)
[13:37] <xnox> fine, i can fille with it.
[13:37] <xnox> =)
[13:38] <barry> :)  it is supported for wily, so just `python3.5`
[13:43] <cpaelzer> mvo: pitti: rbasak: you were such a great help this morning - FYI on the bug https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674 is the fix as discussed. Any review is welcome
[13:45] <morphis> bdmurray: seb128 told me you're the one who can add me to the bugsquad team :)
[13:51] <rbasak> cpaelzer: thanks! Based on your comment this sounds good. I'll review the patch.
[13:53] <pitti> cpaelzer: replied
[13:56] <cpaelzer> piiti: thanks will, read it and agree to you - I'll come with a modified version the next days
[13:57] <pitti> cpaelzer: it's pretty much bikeshedding at this point; I don't like that indirection/new script particularly much, but it's not at all wrong
[13:57] <pitti> so if you prefer having it, keep it :)
[14:00] <cpaelzer> pitti: I have removed one indirection on my own, just missed the other opportunity
[14:01] <cpaelzer> pitti: and all that is training in packaging and versioning to me :-)
[14:18] <pete-woods> pitti: thanks very much for the work on dbusmock! :)
[14:21]  * pete-woods watch rmadison python-dbusmock now ;)
[14:22] <pitti> pete-woods: I didn't upload it yet (sorry, being over-pinged)
[14:23] <pete-woods> I understand
[14:23] <pitti> pete-woods: if it's urgent, you can always cherry-pick and directly upload to the overlay, no?
[14:23] <pete-woods> I can see you're really busy just from this channel
[14:23] <pete-woods> I have no power, so can't upload to the overlay
[14:23] <pete-woods> kinda wish I could operate dbusmock via the citrain
[14:23] <pete-woods> but I guess that makes having it in debian harder?
[14:25] <sil2100> barry: hey hey! I'm slowly tackling some python-* FTBFS from the wily test rebuild if you don't mind :)
[14:25] <sil2100> barry: https://bugs.launchpad.net/ubuntu/+source/python-pysaml2/+bug/1503698 is on my plate once I'm finished with some touch tasks
[14:26] <barry> sil2100: excellent!  ping me if you need review/sponsorship
[14:27] <pitti> pete-woods: I uploaded a cherry-pick to the overlay, that's the fastest way
[14:28] <pete-woods> pitti: awesome, this is very much appreciated!
[14:31] <pete-woods> pitti: it'd be super awesome to be able to pass template parameters in through the main command line when you do python -m dbusmock -t mytemplate ????
[14:31] <pete-woods> but my python-fu isn't so great
[14:31] <pete-woods> I'd be happy to work on the feature
[14:31] <pete-woods> if you had a suggestion of how to encapsulate the parameters
[14:32] <pete-woods> maybe as json?
[14:32] <pitti> pete-woods: there's no proper data types with plain strings, so only strings would work properly; JSON is also not typed
[14:33] <pete-woods> it's not?
[14:33] <pitti> pete-woods: ah, it can tell apart ints and strings indeed
[14:33] <pete-woods> I thought it had all the types of javascript
[14:33] <pete-woods> bool, string, array, number, etc
[14:33] <pete-woods> and also dict
[14:34] <pete-woods> it might not be perfect
[14:34] <pitti> pete-woods: so I guess it's one of json (ugly to type), gvariant-ish like "gdbus", or just live with strings and int only
[14:34] <pitti> most properties are simple, after all
[14:35] <pitti> pete-woods: but in the end it seems easier to change them after instantiation via some d-bus calls?
[14:37] <pete-woods> pitti: that involves standing up separate comms channels, right? e.g. to remove some of the default setup
[14:37] <pete-woods> I saw this as a way of supporting the existing parameters mechanism that is already supported by most of the modules
[14:37] <pete-woods> sorry, templates
[14:38] <pete-woods> without the need to modify all of the templates, to add the capability to remove the default setup
[14:38] <pete-woods> e.g. in the case of ofono, it adds a modem by default
[14:38] <pete-woods> which you don't always want
[14:40] <pete-woods> but it already has a parameter to avoid it adding the default modem
[14:41] <tdaitx> rbasak, any updates on the squid3 merge?
[14:57] <popey> cyphermox: got another one of these plymouth bugs from a friend who bought a brand new thinkpad x1. first update (14.04) broke it :S https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1503716
[14:59] <pete-woods> something as simple as this? https://github.com/pete-woods/python-dbusmock/commit/b511c1d98c09e054816544b7aa52be0dec4b615c
[15:00] <cyphermox> popey: ok
[15:00] <cyphermox> I think I have a fix for your bug from yesterday, I'm going to try it here now and upload
[15:01] <cyphermox> this new one will probably take more time, plymouth doesn't change much, and lots of issues are really graphical display driver problems
[15:02] <davmor2> popey: do you know if it is optimus
[15:02] <popey> no, pure Intel I believe
[15:11] <pitti> pete-woods: seems okay to me (just needs a test case)
[15:13] <pete-woods> pitti: cool (and also to work ;) )
[15:14] <pitti> pete-woods: and please also a test case for ill-formatted params; I guess it should make clear somewhere that it needs to be a dictionary, etc.
[15:14] <pete-woods> pitti: yeah, will add tests as thorough as I can manage
[15:14] <pete-woods> might need some pointers where my python is lacking
[15:15] <davmor2> pete-woods: well for a start you are not hissing enough
[15:15] <pete-woods> :D
[15:16] <pitti> pete-woods: https://pbs.twimg.com/media/B329uElIAAEarI2.png
[15:17] <pete-woods> pitti: that png was too quickly to hand :p
[15:17] <pitti> pete-woods: sssssSSS sSSSssSSSS ssssssSS SS sssS
[15:17] <pitti> pete-woods: err, I meant "I had a bookmark for it" :)
[15:21] <pete-woods> ha!
[15:25] <davmor2> pete-woods, pitti: you'll appreciate this http://search.cpan.org/~iamcal/Acme-Python-0.01/Python.pm
[15:26] <pete-woods> davmor2: I'm amazed how so many people have the time to create these things!
[15:26] <pitti> yeah, as if brainfuck wasn't enough :)
[15:28] <kruger> the kernel provided in the dvd (vmliz.efi) is compiled with some
[15:28] <kruger> the kernel provided in the dvd (vmliz.efi) is compiled with some
[15:29] <kruger> specific parameters?
[15:30] <ogra_> kruger, try in #ubuntu-kernel
[15:31] <kruger> ogra_: thank you
[15:46] <bdmurray> morphis: Did you mean the bug control team?
[15:56] <morphis> bdmurray: basically I wanted to assign a bug to some one else
[16:00] <bdmurray> morphis: Are you an upstream developer or bug triager for an upstream project? If so which one.
[16:15] <pete-woods> pitti: how about something like this? https://github.com/pete-woods/python-dbusmock/commit/ba9e044f84f095dcb2d6f0ddb451c5ccc196b5e8
[16:21] <pete-woods> created a PR at any rate: https://github.com/martinpitt/python-dbusmock/pull/15/files
[16:24] <kruger> i'm unable to recreate a vmlinuz.efi for boot in the uefi mode (in bios mode boot fine) any hints?
[16:34] <bdmurray> xnox: Do you have any plans to finish bug 1433013?
[16:37] <kruger> i try to explaim better: i've recompiled the vmlinuz.efi, but i'm unable to boot the dvd in the uefi mode, i'm kicked in busybox shell (initramfs). In bios mode boot fine. Any hints?
[16:39] <xnox> bdmurray: not immediately
[16:54] <morphis> bdmurray: depends on how you define that, I am going to maintain bluez and doing development on ofono
[18:28] <kruger> someone can help me about the issue with vmlinuz.efi?
[21:04] <doko> Laney, slangasek: is there any policy when/how to remove finished/almost finished transition trackers to done?
[21:08] <slangasek> doko: none that I know of; for gcc5 I generally moved them out when I knew they were 100% done in -proposed


[12:33] <sylwek-ibmr50e> yo
[12:33] <sylwek-ibmr50e> you guys like kendrick lamar?
[14:32] <wxl[m]> sylwek-ibmr50e: see -offtopic. Also we are all not guys.
[14:39] <diogenes_> guys is interchangeable term
[14:50] <wxl> diogenes_: no, it's not.
[14:54] <diogenes_> wxl, there are different use cases, if it's singular then it refers to a male, if plural it can be used as a form of addressing a mixed gender group
[14:56] <wxl> diogenes_: it's ambiguous, just as refering to humankind as mankind.
[14:57] <diogenes_> i can see no huge problem there
[14:57] <wxl> diogenes_: and what gender do you identify with?
[14:57] <diogenes_> :) not sure already
[14:58] <wxl> well good, then. i'm sure you would appreciate to be inclusive. "folks" or "people" is inclusive. "guys" is not, necessarily.
[14:59] <wxl> the etymology of the word refers to Guy Fawkes who was most certainly male.
[15:01] <diogenes_> wxl, as long as there is no such a rule or "Code of Conduct", the only thing that matters is to be polite and the meanings of the words have suffered considerable changes throughout of the history, nothing stays the same as it was originally.
[15:02] <wxl> @diogenes_: https://www.ubuntu.com/community/code-of-conduct "We will challenge prejudice that could jeopardise the participation of any person in the project." also the "Be considerate" clause. can you be guaranteed that every person will feel exactly the same as you do? if not, don't.
[15:07] <diogenes_> yeah  that's where the separation of people begins, it has the reverse effect, not the intended one because all is interpretable and can be used with wicked intention.
[15:08] <wxl> diogenes_: people unambiguously refers to everyone, so no.
[15:11] <diogenes_> wxl, then to avoid confusion (because people come from different backgrounds) the ops should specify those things in the topic of the channel (e.g. use "people" as a general form of addressing)
[15:12] <wxl> diogenes_: as i pointed out, there are clauses in the CoC that apply and that is most certainly mentioned when you join any ubuntu cannel.
[15:12] <diogenes_> on other ubuntu channels there is no problem with that
[15:13] <wxl> i urge you to ask them all about it. or better yet, ask the community council. i'm sure you will find it applies.
[15:14] <diogenes_> oh, then i suppose that's counter productive
[23:50] <Wafficus> hey guys, where do I change my EDITOR variable in Lubuntu to be Vim?
[23:51] <Wafficus> cause I prefer Vim over nano tbh
[23:51] <wxl> export EDITOR=vim
[23:52] <wxl> put that in bashrc
[23:52] <Wafficus> is this a file within my bin or root?
[23:52] <Wafficus> ah gotcha, will do
[23:52] <Wafficus> thanks
[23:52] <wxl> $HOME/.bashrc
[23:52] <wxl> you actually might want to export VISUAL=vim as well
[23:53] <wxl> you can also `sudo update-alternatives --config editor`
[23:53] <wxl> `select-editor` is a thing too
[23:54] <wxl> Wafficus: head over to #lubuntu-devel. i got something i want to chat with you about


[00:07] <OvenWerks> Eickmeyer[kde]1: playing with firewire today, I think I have finished the headphone stuff.
[00:07] <Eickmeyer[m]> Nice. :)
[00:08] <OvenWerks> but the internal external speaker thing, I don't know.
[00:08] <OvenWerks> I don't have one to play with.
[00:09] <OvenWerks> I am going to have to move my fw card or my M66
[00:09] <OvenWerks> they are both on the same irq :P
[00:10] <OvenWerks> I may move the AudioPCI to irq 16 as it only does MIDI so it can share.
[00:12] <OvenWerks> but if I try to start a zita-ajbridge for the D66 while the audiofire is jackmaster the firewire kernel modules lock up.
[00:12] <OvenWerks> I think jack crashes and doesn't release the device
[15:31] <OvenWerks> interesting, this page seems to indicate that USB audio is best at 48000, 96000, and maybe a few 192000... https://wiki.linuxaudio.org/wiki/list_of_jack_frame_period_settings_ideal_for_usb_interface
[16:54] <Eickmeyer[m]> Yeah, because it has to do with the 1ms multiplier. Makes sense.
[16:54] <Eickmeyer[m]> I could
[16:55] <Eickmeyer[m]> 've sworn that site had 44100 at one point.
[18:47] <OvenWerks> It still does... one or two of them are 44k1
[18:52] <OvenWerks> However, for setting up zita-ajbridge where SRC is happening anyway, USB devices could all be set to 48k even if jack is running at 44k1
[19:42] <OvenWerks> Huh, Ordered parts on tuesday for my mixer (mackie cr1604) because the PS has >5v ripple... got here today... even with a border crossing.
[19:43] <OvenWerks> I am replacing all the caps in the ps plus two resitors that are quite dark.
[19:45] <OvenWerks> Eickmeyer[kde]1: in other news, moved my D66 card to a new slot (no shared irq) and redid rtirq. I can now add my D66 and an extra device without crashing the audiofire :)
[19:45] <Eickmeyer[m]> Oh cool!
[19:46] <OvenWerks> moved my AudioPCI to irq16 which it shares with my PATA to SATA bridge. It will only be used for MIDI anyway.
[19:47]  * OvenWerks doesn't know what to do with 16 i/o...
[19:47] <OvenWerks> I only have 8 Mic pre.
[19:48] <OvenWerks> (the cr1604 only has 6 plus I have another stereo one.
[19:49] <OvenWerks> The D66 is actually higher priority than the audiofire.
[19:55] <Eickmeyer[m]> Yeah, that's a lot of channels. You could almost turn your computer into a mixer with the right midi controller.


[00:00] <sirriffsalot> How do I put in precise values in the frequency knobs with calf equalizer 12-band?
[00:55] <Boris> Hi all
[00:57] <Boris> any upgrade gurus around? I need help.
[01:03] <Boris> I'm trying to upgrade from 12.10 and after downloading ~1600 packages the upgrade fails with a "Failed to fetch : gb...........phasex.0.14......size mismatch" .  I have tried 'sudo apt-get clean all' 'sudo apt-get update" but this doesn't fix the problem.
[01:06] <Boris> I don't even have phasex installed
[01:06] <Boris> I guess I'm talking to an empty room
[03:55] <nixnine> anyone know what dependency libz is?
[03:56] <holstein> !info libz
[03:56] <holstein> nixnine: what are you doing?
[03:57] <nixnine> trying to install a program -- pdfedit -- but it says libz not found
[03:57] <holstein> nixnine: from where?
[03:57] <holstein> !info pdfedit
[03:58] <nixnine> download from sourceforge and trying to configure the file to make install
[03:58] <holstein> nixnine: http://askubuntu.com/questions/36601/what-to-use-to-annotate-pdf-highlight-underline offers pdf annotation options
[04:00] <nixnine> I need to edit the pdf.  I used the program on mint 12 but now i am using studio and would like to use the program again
[04:00] <holstein> nixnine: get the .deb from the mint repos
[04:00] <holstein> nixnine: or, use another option
[04:01] <nixnine> no idea on libz?
[04:01] <holstein> nixnine: i'll download it from sourceforge and see
[04:01] <holstein> nixnine: the maintainer is really responsible for making usre you can use the software
[04:01] <nixnine> okay.  using studio 12:10
[04:07] <holstein> nixnine: 32? 64bit?
[04:07] <nixnine> 32
[04:09] <holstein> nixnine: its not in the repos?
[04:09] <nixnine> sourceforge is the only place I found it
[04:09] <holstein> nixnine: open the terminal
[04:10] <nixnine> opened
[04:10] <holstein> apt-cache search pdfedit
[04:10] <holstein> do you see it?
[04:11] <holstein> nixnine: ?? do you see it listed?
[04:11] <Unit193> !info libreoffice-pdfimport
[04:11] <nixnine> nothing happens when I do that
[04:11] <holstein> nixnine: you can try this..
[04:11] <holstein> cd ~/Downloads
[04:11] <holstein> wget http://archive.ubuntu.com/ubuntu/pool/universe/p/pdfedit/pdfedit_0.4.5-2_i386.deb
[04:12] <holstein> then, sudo apt-get install gdebi
[04:13] <holstein> gksudo gdebi-gtk ...then navigate to the downloaded .deb
[04:13] <holstein> then, you can email the address in the readme if that doesnt work, and ask the maintainer what you are supposed to so with the software they make
[04:14] <holstein> or, load up a 12.04 live CD and sudo apt-get install pdfedit and work with it
[04:14] <holstein> or, try one of the other pdf editing options that *is* supported
[04:15] <holstein> nixnine: you can also ask in #ubuntu or #xubuntu since this is not an ubuntustudio specific issue
[04:15] <nixnine> do you know of another pdf editor?
[04:16] <holstein> http://www.ubuntugeek.com/list-of-pdf-editing-tools-for-ubuntu.html
[04:17] <holstein> !info flpsed
[04:19] <nixnine> thanks
[17:11] <celesteh> i'm trying to write/find a script which can tell if my fast track ultra is plugged in.  I know that what I want is aplay -l | grep -i ultra, but I can't seem to figure out how to put together an if statement for the bash script
[17:20] <zequence> celesteh: You want a script to do something only if it finds the fast track?
[17:20] <zequence> celesteh: Would you mind sharing what you have done so far? You could paste here http://paste.ubuntu.com
[17:23] <zequence> I would probably do "grep -o"
[17:23] <zequence> ULTRA_EXISTS = $(aplay -l | grep ultra)
[17:24] <zequence> if [ $ULTRA_EXISTS == "ultra" ]; then..
[17:24] <zequence> I forgot to add the -o option to that
[17:31] <celesteh> thanks zequence, that's got me sorted!
[19:04] <Arkhana> Can anyone help me with configuring GRUB 2?
[19:22] <zequence> Arkhana: What is it that you are configuring in Grub2 more exactly?
[19:23] <Arkhana> I want to dual-boot Ubuntu Studio and Syllable. The problem is: Syllable is not Linux or even BSD
[19:23] <Arkhana> So I don't know where to edit GRUB
[19:25] <Arkhana> Correction: how to edit grub
[19:26] <zequence> Arkhana: http://web.syllable.org/documentation/FAQ.html#2_4
[19:26] <zequence> Seems you need a module
[19:27] <Arkhana> Ok, and where to edit the menu?
[19:30] <Arkhana> So I can enter the lines so that Syllable can boot. Then it will be no problem to copy the module
[19:31] <zequence> Arkhana: I'm not sure you need to edit the menu. May be enough to add the module, and then do: sudo update-grub
[19:32] <zequence> Arkhana: If you want to edit the grub menu manually, you need to edit a file in /etc/grub.d/*
[19:32] <zequence> then do: sudo update-grub
[19:33] <zequence> check out /etc/grub.d/40_custom
[19:34] <Arkhana> Yes, I've already looked at that file, but I didn't really understand were to enter the lines
[19:35] <Arkhana> Btw my pc is turned off. I'm doing this on my smartphone now
[19:35] <Arkhana> I've looked at grub.d
[19:37] <zequence> Arkhana: https://help.ubuntu.com/community/Grub2/CustomMenus
[19:37] <zequence> But, you won't be able to boot syllable without the module anyway
[19:37] <zequence> So, you'll need the module first
[19:37] <zequence> Also, you might not need to edit grub manually at all, if you have the module
[19:37] <zequence> I would try the module first
[19:38] <zequence> Then, do: sudo update-grubv
[19:38] <zequence> Then, do: sudo update-grub*
[19:38] <zequence> It may be that syllable will automatically be added to the menu
[19:42] <Arkhana> Seems kinda hard to config...
[19:43] <zequence> Arkhana: Why not try the module first, and then maybe you wont' need to do any configs
[19:43] <Arkhana> Where are the commands menuentry until intrid for?
[19:45] <Arkhana> Only the module won't work. Syllable didn't install along Ubuntu, there was only a chainloder command
[19:46] <Arkhana> In the GRUB installed by Syllable
[19:46] <zequence> Arkhana: It might be easier just to install Syllable last, as I believe the GRUB it has will also see Ubuntu
[19:48] <Arkhana> I did install Syllable at last. But in the menu.lst of Syllable's GRUB were only chainloaders
[19:49] <Arkhana> And yes, those chainloaders did not work
[19:49] <Arkhana> I already tested them out
[20:01] <Arkhana> Sorry, did you say something while I was away?
[20:03] <zequence> nope
[20:03] <zequence> I've never installed syllable, and don't have any experience with it
[20:04] <zequence> neither have I ever had a reason to edit grub2 menus manually
[20:11] <kuranevi> hi
[20:11] <kuranevi> i am new on ustudio
[20:11] <kuranevi> i have any questions
[20:13] <zequence> kuranevi: Just ask away
[20:13] <kuranevi> what is the standart desktop environment on ustudio?
[20:13] <Arkhana> Lxfe
[20:14] <zequence> kuranevi: XFCE. It's mostly imported from Xubuntu
[20:14] <Arkhana> Zequence is righr
[20:14] <kuranevi> OK
[20:14] <kuranevi> my system is correct;)
[20:14] <kuranevi> another question:
[20:15] <zequence> Arkhana: I better be, since I'm the project lead :)
[20:17] <Arkhana> Zequencer :D
[20:17] <kuranevi> my monitr support 1280 x 1024 resolution but i can use only 1024 x 768
[20:17] <kuranevi> what is wrong?
[20:18] <zequence> kuranevi: Did you try arandr?
[20:19] <kuranevi> no. i dont know this!
[20:19] <Unit193> Do you have the open or closed drivers?
[20:20] <kuranevi> no
[20:20] <zequence> kuranevi: menu -> settings -> ARandR
[20:20] <kuranevi> this is my first run
[20:21] <zequence> kuranevi: You either have free drivers, or you have closed (proprietary), but I'm guessing you have free
[20:21] <kuranevi> vga-0
[20:22] <kuranevi> he says 1024x768 too
[20:22] <Unit193> For some cards/drivers, I've needed to generate an xorg.conf file, and on one computer I have to force it to a higher resolution.
[20:23] <kuranevi> how?
[20:24] <zequence> kuranevi: did you try arandr yet?
[20:24] <zequence> oh, sorry
[20:24] <kuranevi> yes.. zequence
[20:24] <zequence> kuranevi: So, only one resolution there?
[20:24] <kuranevi> only tree, the another res. is lower
[20:25] <kuranevi> excuse me: only 4 resolution but the another tree is lower
[20:25] <Unit193> You could try the proprietary driver, if there is one for your device.
[20:26] <zequence> kuranevi: what kind of graphic card do you have?
[20:27] <kuranevi> radeon hd 4650
[20:31] <zequence> kuranevi: I would take this up at ubuntu channels or forums, as it's something that affects all ubuntu flavors
[20:32] <zequence> kuranevi: Are you sure 1280x1024 is the native resolution for your screen?
[20:35] <kuranevi> yes: http://downloadcenter.samsung.com/content/EM/200512/20051227074515625/EN/6_sub.htm
[20:38] <zequence> kuranevi: might be you need to do as Unit193 said, create a custom xorg.conf. I can't advice you on that, but it it's a file that is not used anymore, unless you want to make settings manually. You put it in /etc/X11/xorg.conf
[20:41] <kuranevi> hmm
[20:41] <Arkhana> I have some problems with ALSA and JACK
[20:41] <kuranevi> can i do anything under add. drivers?
[20:43] <Arkhana> Kuranevi: You could build a second-hand video card in your PC. For about ten euros you don't have to config anything
[20:44] <zequence> Arkhana: It's not sure that it's the fault of the driver
[20:44] <Arkhana> Ok
[20:44] <kuranevi> yes, i can. which graphic card can i use
[20:44] <zequence> Maybe none of the drivers are making sense of the screen
[20:46] <zequence> kuranevi: Something like this http://askubuntu.com/questions/74808/how-do-i-force-a-resolution-of-1024x768
[20:47] <zequence> Modes     "1024x768" "800x600"
[20:48] <zequence> not sure what you should do with the HoriSync and VertRefresh
[20:48] <zequence> You could try leaving them out
[20:48] <zequence> kuranevi: When you do this kind of stuff, it's good if you know a little bit about using the terminal
[20:49] <kuranevi> i have this information on add. drivers: http://www.cnx-software.com/wp-content/uploads/2011/12/Ubuntu-Additional-Drivers-ATI_Radeon_drivers_Catalyst.png
[20:49] <zequence> kuranevi: There's a package for it in Ubuntu repos
[20:49] <zequence> kuranevi: fglrx
[20:49] <zequence> kuranevi: Again, it might not be a problem with the driver
[20:49] <zequence> kuranevi: Also, it's not certain that the new AMD drivers work
[20:50] <zequence> kuranevi: But, if you want to try: https://help.ubuntu.com/community/BinaryDriverHowto/ATI
[20:51] <zequence> there's been a problem with recent AMD proprietary drivers. not very good support
[20:51] <zequence> the free drivers are good, except some people have problems with overheating
[20:52] <zequence> also, the proprietary AMD drivers drop support for newer cards very quickly
[20:52] <zequence> And, you can't easily build the older drivers on newer Ubuntu releases
[20:52] <zequence> So, in the end, the free drivers are the easiest
[20:52] <zequence> sorry, drop support for older card, is what I mean :)
[20:53] <Arkhana> Sounds like building a driver is not for noobs
[20:54] <kuranevi> you meaning, i have a risk activate the licenced driver under addional drivers;?
[20:54] <kuranevi> better is to work with xorg.conf?
[20:55] <Arkhana> I don't know. I always recommend to do back-ups when you're doing things like this
[20:55] <zequence> kuranevi: Just read the page to learn about the different choices you have with drivers
[20:55] <kuranevi> ok
[20:55] <kuranevi> thank you all
[20:55] <zequence> kuranevi: I would at least try the xorg.conf solution
[20:56] <Arkhana> Kuranevi: do you understand it a little?
[20:56] <zequence> kuranevi: Just remember, if you do it badly, your desktop could disappear, and all you can do is use a terminal, so it's good if you know what to do when that happens
[20:56] <kuranevi> yes Arkhana
[20:56] <kuranevi> i know zequence
[20:57] <kuranevi> ...
[20:58] <Arkhana> Ok, if you understand all the files and such you are kinda safe not to break something
[20:58] <Arkhana> All the files you need for this
[20:59] <kuranevi> understand sir:)
[21:00] <Arkhana> I learn computing by breaking things and building it up again
[21:00] <Arkhana> But that's not always nice, believe me :D
[21:01] <Arkhana> Good night everybody
[21:01] <Arkhana> I'm going to sleep
[21:02] <kuranevi> Arkhana: we walk on the same way but you are far away;)
[21:02] <Arkhana> What do you mean?
[21:02] <kuranevi> learning computing by breaking
[21:03] <kuranevi> and building it up again;)
[21:04] <Arkhana> Yep. Sometimes you have a nice thing for office purpose, and after 10 minutes you have to start over new again
[21:05] <Arkhana> Where are you from, btw
[21:05] <kuranevi> good night all
[21:05] <kuranevi> i?
[21:05] <Arkhana> Yes
[21:06] <kuranevi> from Istanbul
[21:06] <kuranevi> and you?
[21:06] <Arkhana> I'm from the Netherlands
[21:06] <Arkhana> Tomorrow it's Queens Day
[21:07] <Arkhana> Maybe you have heared about it?
[21:07] <kuranevi> A little bit
[21:07] <kuranevi> we have not a king and queen;)
[21:07] <Arkhana> A sheik?
[21:07] <kuranevi> are you Dutch?
[21:07] <Arkhana> Yup
[21:08] <kuranevi> not a Sheik
[21:08] <kuranevi> we have a democratic republic
[21:08] <Arkhana> We too. We have a queen, but she has no power at all
[21:08] <kuranevi> i dont love the Sheiks
[21:09] <Arkhana> No? Why not?
[21:09] <zequence> I think the Turkish language is probably quite similar to Finnish. Not many people know this
[21:09] <zequence> It is not related to Arabic
[21:09] <zequence> As many think
[21:09] <Arkhana> No. I didn't know that too
[21:09] <zequence> Even if many words are borrowed from the Arabic language
[21:10] <zequence> The grammar is very similar to Hungarian and Finnish
[21:10] <kuranevi> zequence: you are right
[21:10] <Arkhana> But the capital letter i in Turkey is very handy
[21:10] <kuranevi> Arkhana: i dont love the monarchy and Theocracy
[21:10] <Arkhana> I love communism
[21:11] <Arkhana> But there will never be good communis,
[21:11] <Arkhana> Communism
[21:11] <kuranevi> do you know anything from ibni Haldun?
[21:11] <Arkhana> No, not at all
[21:11] <Arkhana> Is he Atatürk?
[21:12] <Arkhana> Who is Ibni Haldun?
[21:13] <kuranevi> no he is a socialogist: http://en.wikipedia.org/wiki/Ibn_Khaldun
[21:14] <kuranevi> but you can find not good informations on wiki
[21:15] <kuranevi> read this: http://en.wikipedia.org/wiki/Muqaddimah#.27Asabiyyah
[21:15] <Arkhana> Well, i see a lot of informatiom
[21:15] <Arkhana> I will check that out tommorow. I'm going to sleep now
[21:16] <Arkhana> Good night
[21:16] <kuranevi> i ask you tomorrow;)
[21:16] <kuranevi> good Queens day for any, and on 1 mai for us all:)
[21:17] <kuranevi> good night
[21:17] <Arkhana> I will leave my phone turned on the whole night, so the link is still on my phone tommorow
[21:17] <Arkhana> Bb
[21:17] <Arkhana> But what is on 1 mai?
[21:18] <kuranevi> International Workers' Day
[21:18] <Arkhana> O yes, that's true.
[21:18] <kuranevi> a spirit day in communism:P
[21:18] <Arkhana> Good night
[21:19] <kuranevi> zequence: where are you from?
[21:20] <zequence> kuranevi: I'm Finnish, but I live in Sweden
[21:21] <zequence> I've read about a bit about the Turkish language. It looks very similar to Finnish in deed, even if probably not a single word is the same, but the grammar is very similar
[21:22] <zequence> The way you can use one word to say something that in other languages require 5 words
[21:22] <kuranevi> yes, you are right
[21:22] <kuranevi> eskimo people and the american indians too
[21:22] <zequence> Yes
[21:22] <zequence> Sioux :)
[21:23] <zequence> Probably all of the languages of the nomad people on the northern hemisphere
[21:23] <kuranevi> tottally correct
[21:24] <kuranevi> what do you know about the runic alphabet?
[21:25] <zequence> not much
[21:25] <zequence> used by the old norse people
[21:25] <kuranevi> what do you know about he Etrusk?
[21:25] <zequence> Finnish didn't have a written language until quite late. Officially, probably not until the 1800
[21:26] <zequence> Very little
[21:27] <kuranevi> and Basque people?
[21:27] <zequence> Not much
[21:27] <zequence> I know there has been some ideas about those belonging to the same group of languages
[21:28] <kuranevi> yes
[21:28] <Arkhana> Dutch with Somalian
[21:28] <kuranevi> this communitys have no connection from the Indo-european
[21:28] <zequence> In Europe, the study of languages has been heavily influenced by nationalism, so probably a lot of the information today is wrong
[21:29] <Arkhana> The Dutch grammar is quite easy nowadays
[21:29] <kuranevi> Dutch=Deutch/German/allemania etc.
[21:29] <Arkhana> Very few people use right grammar
[21:30] <Arkhana> in Holland
[21:30] <kuranevi> is same  in all countrys
[21:30] <Arkhana> But in Holland a lot more
[21:31] <kuranevi> Arkhana kannst du deutsch sprechen?
[21:31] <Arkhana> The gender types of words are used wrong very often
[21:31] <Arkhana> Ja naturlich
[21:31] <Arkhana> Das habe ich gelernt auf der Schule
[21:31] <kuranevi> ich auch
[21:31] <zequence> Finnish grammar is easy in one way. You can put the words almost in any order you want, and it will always be correct. But, knowing how to bend them, is a different story :). 16 forms of casus
[21:32] <Arkhana> Here it's not
[21:32] <kuranevi> "i love linux" on turkish: "linux'u sev+i+yor+um"
[21:33] <Arkhana> At our language lessons at school we learn to give all the kinds of words a own kname
[21:33] <Arkhana> Name
[21:33] <kuranevi> sev(mek) mean love
[21:33] <Arkhana> I love linux : Ik houd van Linux
[21:33] <Unit193> !xorgconf
[21:34] <Arkhana> Houd van: love
[21:34] <kuranevi> Houd man is not german?
[21:34] <Arkhana> Houd (van)
[21:34] <Arkhana> It's Dutch
[21:34] <zequence> in Finnish: "linuxta rakastan", all though, Finns rarely say they love something ;)
[21:35] <Arkhana> German: liebe
[21:35] <Arkhana> Ik haat smurfen: I hate smurfs :D
[21:35] <Arkhana> When do they say they love someti
[21:35] <Arkhana> Something?
[21:37] <zequence> It's not a word easily used
[21:37] <kuranevi> Love and Liebe is a little similar but Houd is very different
[21:37] <Arkhana> Houd : keep
[21:37] <Arkhana> Houd van : love
[21:38] <Arkhana> Houd jij van Linux : Do you love Linux?
[21:38] <Arkhana> Jij: you
[21:38] <zequence> In Finnish, you only need two words for that: rakastatko linuxta?
[21:38] <kuranevi> you on turkish: siz/sen :)
[21:38] <zequence> rakastatkokin linuxta = do you also love linux?
[21:38] <Arkhana> Lazy typing in Finnish :D
[21:39] <zequence> Arkhana: Less word, more complicated words
[21:39] <Arkhana> I see
[21:39] <kuranevi> Do you love Linux on turkish: Linux'u seviyormusun?
[21:39] <Arkhana> All kinda long words
[21:40] <Arkhana> The most complicated word I know is methylfenidaathydrochloride
[21:41] <kuranevi> MPH
[21:42] <Arkhana> My daily medicine
[21:42] <Arkhana> To decrease autism
[21:42] <zequence> Probably the longest one word in Finnish epäjärjestelmällistyttämättömyydellänsäkään
[21:42] <zequence> It's not a combination of words, but a grammatical form of one word
[21:42] <zequence> http://www.finlandforum.org/viewtopic.php?f=9&t=9172
[21:43] <Arkhana> WOW GEEZ
[21:43] <kuranevi> hey friendst , i want to go sleep
[21:43] <kuranevi> nivce to meet you
[21:43] <Arkhana> Yep
[21:43] <kuranevi> yhave you twitter account?
[21:43] <Arkhana> Yes
[21:43] <zequence> If your read further down, you'll see how the word is constructed
[21:43] <Arkhana> Speedfreaked1
[21:43] <zequence> "I wonder if it's not with his act of not having made something be seen as unsystematicality"
[21:43] <kuranevi> follow me please: kksafak
[21:44] <Arkhana> Ok
[21:44] <kuranevi> and zequence?
[21:45] <zequence> I don't twitter
[21:45] <zequence> But, I'm usually always around here
[21:46] <kuranevi> ok
[21:46] <Arkhana> I don't know how to add people on Symbian
[21:46] <Arkhana> So please follow me: speedfreaked
[21:46] <kuranevi> i cant find your nickname on twitter
[21:47] <Arkhana> Without the 1
[21:47] <Arkhana> So just speedfreaked
[21:47] <kuranevi> no, icant find
[21:47] <Arkhana> Weird
[21:47] <kuranevi> Dennis?
[21:47] <Arkhana> Yes
[21:48] <kuranevi> my name is Kenan
[21:48] <Arkhana> Ok
[21:48] <kuranevi> you can fşnd my name in Binle:P
[21:49] <kuranevi> find
[21:49] <kuranevi> Bible
[21:49] <Arkhana> I don't know where to search people in Symbian
[21:51] <Arkhana> Could you place a tweet with #something_very_random ?
[21:51] <Arkhana> I can find you that way
[21:52] <Arkhana> And then tell me what's after the hashtag
[21:53] <Arkhana> Or do you have fb
[21:53] <kuranevi> i dont use fb
[21:54] <Arkhana> Ok could you place a tweet?
[21:54] <kuranevi> ok
[21:55] <Arkhana> What's in it?
[21:57] <kuranevi> and
[21:57] <kuranevi> i have say how are you
[21:57] <Arkhana> Hey a mail
[21:57] <Arkhana> Thnx
[21:57] <Arkhana> Now I can finally sleep :D
[21:58] <kuranevi> me too:P
[23:41] <IntuitiveLeap> hello everyone
[23:42] <IntuitiveLeap> if any of the ubuntustudio folks are on, i have recently gotten this following nasty message from some of the regular updates.
[23:43] <IntuitiveLeap> Do you want to continue [Y/n]? y
[23:43] <IntuitiveLeap> Setting up initramfs-tools (0.103ubuntu0.7) ...
[23:43] <IntuitiveLeap> update-initramfs: deferring update (trigger activated)
[23:43] <IntuitiveLeap> Processing triggers for initramfs-tools ...
[23:43] <IntuitiveLeap> update-initramfs: Generating /boot/initrd.img-3.8.0-19-lowlatency
[23:43] <IntuitiveLeap> gzip: stdout: No space left on device
[23:43] <IntuitiveLeap> E: mkinitramfs failure cpio 141 gzip 1
[23:43] <IntuitiveLeap> update-initramfs: failed for /boot/initrd.img-3.8.0-19-lowlatency with 1.
[23:43] <IntuitiveLeap> dpkg: error processing initramfs-tools (--configure):
[23:43] <IntuitiveLeap>  subprocess installed post-installation script returned error exit status 1
[23:43] <IntuitiveLeap> No apport report written because MaxReports is reached already
[23:43] <IntuitiveLeap>                                                               Errors were encountered while processing:
[23:43] <IntuitiveLeap>  initramfs-tools
[23:43] <IntuitiveLeap> E: Sub-process /usr/bin/dpkg returned an error code (1)
[23:44] <Unit193> gzip: stdout: No space left on device  You seem to be out of room, try removing something, adding room to the partition, or uninstalling some things as well.  Bit first, what's the output of df -h ?
[23:44] <Unit193> !pastebin
[23:44] <IntuitiveLeap> i have a terabyte of space O.o
[23:45] <Unit193> Ah, nice.  What's the output of  df -h  though?
[23:46] <IntuitiveLeap> any speciasl folder u after?
[23:46] <IntuitiveLeap> special
[23:46] <Unit193> That's drives, not dirs.  (it is df, not du.)
[23:46] <IntuitiveLeap> so u after boot
[23:46] <IntuitiveLeap> ah yes i am at 98 %
[23:47] <Unit193> There ye go, that's your problem. :)
[23:47] <IntuitiveLeap> can gparted increase the boot drive while it's running?
[23:47] <Unit193> I'm pretty sure it cannot.
[23:48] <IntuitiveLeap> well ty for the diagnosis
[23:48] <IntuitiveLeap> i will mull this over
[23:48] <IntuitiveLeap> lol
[23:48] <Unit193> Sure.  LiveCD and gparted should be on it.
[23:53] <IntuitiveLeap> ty again, ill give that a try. does it seem strange that the boot drive would be full, i have only had this os on here for a few months?
[23:53] <IntuitiveLeap> ubuntustudio 13.04
[23:58] <Unit193> Depends on what you have, if you remove old kernels, etc.
[23:58] <Unit193> dpkg -l | grep -e linux-image -e linux-header
[23:58] <IntuitiveLeap> i know the updates have installed a lot of updated kernels, that must be it
[23:59] <Unit193> You normally only want to keep the current one, and one you know works.
[23:59] <IntuitiveLeap> what is the standard procedure to remove them?


[03:12] <bigjools> wgrant: more font changes in LP lately?
[03:13] <wgrant> bigjools: Yes, we reverted from Ubuntu Mono to monospace, because Ubuntu Mono is difficult to size correctly.
[03:13] <bigjools> ok
[03:13] <bigjools> wondered if it was my browser screwing me over
[03:13] <wgrant> Not this time, at least :)
[03:13] <bigjools> on MPs the font size for commit message and description is now larger than the rest of the page
[03:14] <wgrant> It's meant to be exactly the same size.
[03:14] <bigjools> no big deal but a bit jarring
[03:14] <wgrant> But it probably looks larger because the characters are wider, because monospace.
[03:14] <bigjools> well it ain't :)


[12:43] <jbailey> 3) Install in ppc buildd chroot so that we can do a source upload that relies on and replaces them.
[12:43] <jbailey> 2) Ah, okay.  doko thought you could do it.
[02:15] <zul> hey
[05:25] <fabbione> morning
[05:25] <lamont> morning fabbione
[05:26] <fabbione> hey lamont
[05:31] <fabbione> lamont: i think we will need to move the kernel-team shared archive somewhere other than your home dir...
[05:32] <lamont> fabbione: eventually to be sure
[05:32] <lamont> although ~lamont will remain alive past june 1
[05:32] <fabbione> if that's the case, it can stay where it is :)
[05:38] <fabbione> do we have a date to switch the default c++ compiler?
[05:38] <lamont> dunno
[05:38] <fabbione> ok
[05:38] <fabbione> just because i will be off most of this week in one way or another
[06:25] <lamont> fabbione: how stable is 2.6.12 these days?  would I be stupid to run it on my desktop?
[06:26] <fabbione> lamont: i have been using it on my laptop without any problem
[06:26] <fabbione> i know there are a few bugs here and there
[06:26] <lamont> kewlness
[06:27] <fabbione> like pcmcia sometimes oops on some cards removal
[06:27] <fabbione> and ipw2200 oops with iwscan
[06:28] <crimsun> stable here, too, for ~2 days
[06:28] <crimsun> eek, I need to look at those alsa requests and tweak the .config
[06:30] <fabbione> lamont: ehehe i think that generally there is a pcmcia bug
[06:30] <fabbione> i can see some weird things in pcmcia hotplug
[06:30] <fabbione> but nothing too fancy
[06:30] <fabbione> crimsun: that would be leet :)
[06:32] <fabbione> lamont: yeah.. that would be safer :)
[06:35] <fabbione>   * Added support for via6410 motherboard.
[06:35] <fabbione>     - drivers-ide-pci-via82cxx_enable-via6410.dpatch
[06:35] <fabbione> ?
[06:35] <fabbione> is this one?
[06:35] <z3k3_pheonix> negative, that one failed.
[06:35] <lamont> fabbione:  -1.1?
[06:35] <z3k3_pheonix> I gave zul a copy of the new one, he was sick, so not sure if he fixed it up yet on his baz
[06:35] <fabbione> z3k3: can you put the patch somewhere?
[06:35] <lamont> or was that my doing?
[06:36] <fabbione> lamont: 1.1 as in ABI.debver
[06:36] <z3k3_pheonix> fabbione: yep, give me a min.
[06:36] <fabbione> z3k3: thanks
[06:36] <lamont> doh
[06:41] <z3k3_pheonix> fabbione: http://www.fazekas.net/drivers-ide-pci-generic_enable_via6410.dpatch
[06:42] <z3k3_pheonix> seems to work fine :)
[06:42] <lamont> `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead.
[06:42] <lamont> hrm..
[06:43] <z3k3_pheonix> ?
[06:43] <lamont> much better.  hate it when I screw things up
[06:44] <z3k3_pheonix> anyhow.
[06:44] <z3k3_pheonix> peaceut
[06:44] <z3k3_pheonix> err.. peaceout too.
[06:51] <fabbione> argh
[06:51] <fabbione> Resolving www.fazekas.net... failed: Host not found.
[06:52] <fabbione> lamont: can you resolv that domain?
[06:53] <lamont> www.fazekas.net has address <IP_ADDRESS>
[06:54] <fabbione> hmm nope..
[06:54] <fabbione> doesn't work from here
[06:54] <fabbione> lamont: can you grab the patch please?
[06:56] <fabbione> nevermind
[06:56] <fabbione> i forgot about my shells around the world :)
[07:01] <fabbione> hmm z3k3 patch doesn't make much sense to me....
[07:08] <fabbione> impressive... other than the usual 293829372 typos in the changelog, zul did a really nice work :)
[07:27] <lamont> fabbione: you hip deep in a bunch of commits?
[07:27] <lamont> like after the build at least gets through patching on my test machine...
[07:27] <fabbione> lamont: i only merged from zul, but i need to clean up and test build
[07:28] <fabbione> lamont: i usually do a full merge and commit
[07:28] <fabbione> and clean afterwards
[07:28] <fabbione> right now i am parsing the mails from bugzilla
[08:14] <ivoks> lol the are no kernel bugs, only broken hardware
[10:06] <lamont> fabbione: my latest committed... test build running now to make sure it's not ftbfs, but should be OK.  changes are all hppa specific, so not a big deal.
[10:06] <lamont> well, --patch-21 commited now
[10:07] <fabbione> lamont: no problem.. thanks
[11:01] <lamont> fabbione: grumble... questions on i386 in config.
[11:01] <lamont> Rt2500 chipset support (RT2500) [N/m/y/?]  (NEW)
[11:01] <fabbione> lamont: uh???
[11:01] <lamont> what's your pleasure?
[11:01] <fabbione> m
[11:01] <fabbione> i still need to try to build the merge
[11:01] <lamont>     Acer Hot Keys Support (INPUT_ACERHK) [N/m/y/?]  (NEW) m?
[11:01] <fabbione> i had to boil down a lot
[11:01] <fabbione> yes m
[11:01] <lamont> several of them, m for all
[11:02] <fabbione> yes.. all m
[11:02] <lamont> I'll walk through the configs and do another checkin
[11:06] <lamont> --patch-22
[11:20] <lamont> fabbione: --patch-22 is building much better than --patch-21... :)
[11:20] <mjg59> acerhk? Eww.
[11:20] <fabbione> hey mjg59
[11:20] <lamont> mjg59: at least it's not ==y :-)
[11:28] <lamont> builds running on i386, hppa.  /me sleeps
[02:35] <Z3K3_work> quick question: if I am accessing my devel box through ssh and want to do a kernel compile, how would I damonize the dpkg-buildpackage so that it doesn't crap out when I kill the ssh session?
[02:35] <Z3K3_work> if that makes sense.
[02:35] <Z3K3_work> :)
[02:35] <Mithrandir> use screen
[02:36] <Z3K3_work> so #screen dpkg-build.....
[02:38] <Z3K3_work> thx
[02:46] <Z3K3_work> wb
[03:03] <zul> heylo
[03:04] <lamont> fabbione: built on hppa, i386 just about done.
[03:04] <lamont> (is building documentation cruft)
[04:52] <gabriel> hi
[04:53] <gabriel> i upgraded from warty and my doesnt boot with the latest kernel
[04:53] <zul> #ubuntu
[04:53] <gabriel> can i get some support
[04:53] <gabriel> ?
[04:53] <lamont> gabriel: we should take that to #ubuntu
[04:53] <gabriel> yes i try
[04:53] <zul> #ubuntu is for support #ubuntu-kernel is to discuss how you should fix it
[04:56] <gabriel> ok, only one thing more could you give one advise, where can I start to read
[04:57] <gabriel> I now the problem is hotplug
[05:06] <zul> to universe?
[05:06] <lamont> that's where it'd be most likely to wind up at this point, yes.
[05:07] <lamont> wouldn't want to change the meta packages though
[05:07] <zul> meh...head is starting to hurt again i should have come into work
[05:35] <zul> oooh...new inotify
[05:47] <Z3K3_work> hey zul.. feelin better?
[06:00] <lamont> zul: we should get that in, since it tends to force new abi each time...
[06:15] <fabbione> re
[06:16] <fabbione> i think next monday is a good target for 12rc3
[06:16] <fabbione> there are a few bits that must be cleaned first
[06:16] <fabbione> hey zul
[06:16] <fabbione> z3k3: still around?
[06:20] <fabbione> lamont: i386 build is go here
[06:21] <fabbione> zul: are you still alice?
[06:21] <fabbione> alive?
[06:30] <fabbione> zul: wake up punk!
[06:31] <Z3K3_work> i keep getting
[06:31] <Z3K3_work> Missing /usr/src/linux-source-2.6.12-<IP_ADDRESS>/debian/abi/<IP_ADDRESS>-1.1/abiname file.
[06:31] <Z3K3_work> in the /abi folder is 2.6.10-34
[06:31] <fabbione> z3k3: i did answer to that already....
[06:31] <Z3K3_work> do i just rename this to 2.6.11-91-1.1?
[06:31] <fabbione> the patch you gave to me this morning
[06:32] <fabbione> is it incremental or a replament for the one zul did?
[06:32] <Z3K3_work> replacement
[06:32] <Z3K3_work> you did answer somewhat.  but do i rename it to get it working?
[06:32] <Z3K3_work> sorry.
[06:32] <fabbione> there is no point in making it working.
[06:32] <fabbione> so just skip that bit
[06:32] <fabbione> it is not of any use with a major upstream release
[06:33] <fabbione> as i already wrote
[06:33] <fabbione> hey jb
[06:33] <Z3K3_work> i cant skip, it borks there everything i dpkg-buildpackage
[06:33] <fabbione> z3k3: it works here perfectly
[06:33] <fabbione> you must have changed something in the attempt to shut up a warning
[06:34] <Z3K3_work> strange.  i did a dpkg-source -x linux-source-2.6.12_<IP_ADDRESS>-1.dsc
[06:34] <jbailey> g'm all
[06:34] <Z3K3_work> rm'd the debian
[06:34] <Z3K3_work> then did baz get
[06:34] <fabbione> jbailey: lvm2 sparc.. i am 100% sure it is a l-k-h problem. it builded on debian without any problem and it fails here
[06:34] <Z3K3_work> pretty vanilla
[06:35] <fabbione> Z3K3_work: well you must have changed something in one way or another that the build system didn't like
[06:35] <Z3K3_work> ok.  thanks for the heads up.  i'm still a bit new to this.
[06:36] <fabbione> zul: i am merging this last patch from you now.
[06:36] <fabbione> zul: from today we are going to "stabilize" the tree for release.
[06:36] <zul> ok...
[06:36] <fabbione> i need to pull in a new GFS version and start cleaning/porting
[06:37] <fabbione> zul: anyway... it was really a neat job..
[06:37] <fabbione> thanks :)
[06:37] <fabbione> except for the changelog...
[06:37] <zul> just having lunch
[06:37] <fabbione> but i will clean it up :)
[06:37] <zul> yeah i suck with the changelog
[06:37] <fabbione> ahah
[06:37] <fabbione> i am the changelog bitch :)
[06:38] <zul> no you are just a bitch :)
[06:38] <fabbione> feeling better today?
[06:38] <fabbione> i like T-Bone emails on kernel-team...
[06:39] <zul> a little im at work...but if i dont work i dont get paid which sucks
[06:39] <fabbione> specially because of the high contribution level of the contents
[06:39] <fabbione> zul: well you suck anyway :)
[06:39] <zul> i know..
[06:39] <zul> i just dont have a witty retort
[06:39] <fabbione> anyway...
[06:39] <fabbione> family time
[06:40] <fabbione> i still feel all foggy and slow from the jetlag
[06:40] <fabbione> and my wife and I need to discuss a few things
[06:40] <fabbione> like next state in which we are going to live
[06:40] <zul> btw the new inotify is in my baz as of lunch time my time
[06:40] <fabbione> already merged
[06:40] <zul> cool
[06:40] <zul> i can go back to halicunating
[06:40] <fabbione> actually.. i was typing the passphrase :)
[06:41] <fabbione> * committed<EMAIL_ADDRESS>[06:41] <fabbione> there...
[06:41] <jbailey> fabbione: Right.  Weren't you going to provide me a list of failures that weren't also gcc-4 failures in general? =)
[06:41] <jbailey> fabbione: got a build log I can see?
[06:41] <fabbione> jbailey: the build log is in the same plase as usual
[06:42] <fabbione> actually it FTBFS on other arches too
[06:42] <fabbione> but the error seems to be very related to l-k-h
[06:43] <fabbione> jbailey: but look at it only if you have time
[06:43] <fabbione> i really need to go now
[06:43] <fabbione> bbl or tomorrow
[06:43] <jbailey> If it's for other arch's I can look nowish =)
[06:43] <jbailey> Good night, Fabio!
[06:43] <fabbione> cya
[06:44] <zul> toodles fabbione
[06:50] <zul> hey dilinger
[06:55] <dilinger_> hello
[06:57] <Z3K3_work> ls -alh
[06:57] <Z3K3_work> oops sorry
[07:02] <jbailey> lvm2 failure on ia64 and i386 is libdevmapper fuckage, tracing.
[07:07] <dilinger_> meh.  lvm2 is perfect!
[07:24] <zul> now for hostap
[07:57] <Z3K3_work> stupid disconnect.
[07:57] <Z3K3_work> where does dpkg dump the kernel build log?
[08:02] <zul> huh?
[08:07] <zul> yay..
[08:07] <zul>  CC [M]   drivers/net/wireless/hostap_crypt_wep.o
[08:07] <zul>   CC [M]   drivers/net/wireless/hostap_crypt_tkip.o
[08:07] <zul>   CC [M]   drivers/net/wireless/hostap_crypt_ccmp.o
[08:07] <zul>   CC [M]   drivers/net/wireless/hostap_cs.o
[08:07] <zul>   CC [M]   drivers/net/wireless/hostap_plx.o
[08:07] <zul>   CC [M]   drivers/net/wireless/hostap_pci.o
[08:53] <Z3K3_work> :)
[08:54] <Z3K3_work> Sorry, before I was asking where dpkg-buildpackage has a log file.  so when my kernel compile borks I can go look through it and see how come it borked?
[08:55] <Z3K3_work> lol
[08:57] <zul> dpkg-buildpackage -rfakeroot -uc -us -b 2>&1 | tee LOG or something like that
[09:33] <jbailey> zul: debuild, good.
[09:35] <zul> jbailey: ill try it tonight


[23:02]  * toddy waves
[23:04] <jose> hi
[23:04] <nhaines> _o/
[23:05] <linaporras> 👋
[23:08] <toddy> who is the chair today?
[23:08] <madhens> o/
[23:09] <toddy> hi madhens :)
[23:09] <madhens> (clarifies I am waving, and not being chair) :D
[23:09] <toddy> :D
[23:09] <linaporras> teward or Eickmeyer
[23:09] <linaporras> jajajaj madhens
[23:10] <nhaines> :D
[23:10] <linaporras> do not know if they are here, otherwise I can do that.... if u agree... but please take into account that I do not have discourse access today jeje
[23:12] <jose> feel free to go ahead but I would wait for someone else before calling it quorum
[23:12] <jose> imagine I'm not here
[23:13] <toddy> wxl: are you here?
[23:15] <jose> considering it's been 15mins I would say we don't have quorum, and cancel this meeting
[23:15] <nhaines> I'd vote yes on that, but we don't have quorum...
[23:16] <linaporras> So... do we schedule this meeting for the next week, or just go until the firs meeting of april?
[23:17] <madhens> If there is anything I can do to reach out to members to help ensure quorum for the next meeting, let me know. I could start doing reminder e-mails.
[23:18] <linaporras> This is the first meeting that we do not have quorum... I think that we can work in create the agenda with more time as a reminder...
[23:19] <nhaines> Yup, no need to worry just yet.
[23:19] <toddy> madhens: thanks. I don't need reminders. I am here :D
[23:19] <wxl> oh heck now i'm here :(
[23:19] <nhaines> Hi wxl!
[23:19] <wxl> heyo :)
[23:19] <toddy> Hi wxl :)
[23:19] <madhens> toddy: Check one off the list!
[23:20] <toddy> :)
[23:20] <wxl> sooooo do we have enough of us now?
[23:20] <toddy> yes we are 4 of the cc
[23:21] <linaporras> Yes.. so jose are u still with us
[23:21] <linaporras> ?
[23:21] <toddy> than we would be 5.
[23:21] <linaporras> oh that's right
[23:21] <linaporras> so we can start...
[23:21] <toddy> yes
[23:22] <linaporras>  #startmeeting Community Council meeting, 20210317.
[23:22] <meetingology> Meeting started at 23:22:23 UTC.  The chair is linaporras.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[23:22] <meetingology> Available commands: action, commands, idea, info, link, nick
[23:22] <toddy> thanks linaporras :)
[23:23] <linaporras> #chair toddy wxl  nhaines jose
[23:23] <meetingology> Current chairs: jose, linaporras, nhaines, toddy, wxl
[23:23] <Eickmeyer> Oh, I'm here!
[23:23] <toddy> Hi Eickmeyer :)
[23:23] <linaporras> chair Eickmeyer
[23:23] <Eickmeyer> It's off by an hour because the US is now in DST.
[23:23] <Eickmeyer> Meaning I went from UTC -8 to UTC -7 on Monday.
[23:23] <Eickmeyer> er, Sunday.
[23:23] <linaporras> ahh ok, is that ok for u?
[23:24] <Eickmeyer> It's fine, I'm just off-guard. hehe
[23:24] <toddy> we have the time difference on next Sunday
[23:24] <linaporras> so we do not have an specific agenda for today, but we can recap on our previous meeting, and see if anyone of u have new topics
[23:25] <nhaines> Eickmeyer: I stressed out about the time change and this meeting a lot on Monday.  :)
[23:25] <madhens> I do have updates on some of the matters Jose brought to us, whenever you're finished with new business or another appropriate time
[23:26] <linaporras> #topic ESM and Standard Support vs. End of LIfe
[23:26] <linaporras> we will be back on this on April, however the ubuntu member's wiki update is in progress...
[23:26] <teward> *punts jose into the void*
[23:27] <toddy> Hi teward :)
[23:27] <teward> blame my FT job for not being here earlier
[23:27] <teward> sorry.
[23:27] <linaporras> I correct myself, the wiki is updated... but when we go back to the topic, maybe we need to support clarifications on that
[23:27] <linaporras> https://wiki.ubuntu.com/Membership
[23:27] <teward> linaporras: I remember Canonical saying it's a "Medium Effort" issue - and we don't have an eta on the ESM / Standard Support vs. EOL
[23:27] <linaporras> #chair Eickmeyer  teward
[23:27] <meetingology> Current chairs: Eickmeyer, jose, linaporras, nhaines, teward, toddy, wxl
[23:27] <Eickmeyer> teward: It's Ok, we essentially just got started.
[23:28] <teward> linaporras: when you say 'the wiki is updated' to what extent?
[23:28] <teward> oh i see
[23:28] <linaporras> I quote the item from the wiki:
[23:28] <linaporras> "Ubuntu Advantage for up to 50 systems for access to ESM and Kernel Livepatching (Announcement post)"
[23:29] <teward> linaporras: I would suggest that we **strongly** tell the DMB to say "Limited Ubuntu Advantage coverage"
[23:29] <teward> or word it to 'ESM Repositories and Kernel Livepatching only' to be more precise
[23:29] <Eickmeyer> ^ Agreed
[23:29] <Eickmeyer> ^ Yep
[23:29] <linaporras> OH I guess I did not put u on CC, I will put u on CC and advice on that (i'll do that after this meeting)
[23:29] <teward> leave **no room for interpretation** in that.
[23:29] <madhens> teward: Rhys' last update is that he's still waiting on guidance, which I think is due early April, for the official guidance.
[23:29] <linaporras> (cc in the email)
[23:30] <teward> madhens: not oging to bash you guys up at Canonical or otherwise
[23:30] <teward> but I've had numerous (and I mean NUMEROUS) discussions with the tech and infrastructure marketing teams at Canonical
[23:30] <madhens> Oh, no worries! We need to know when squeaky wheels need grease.
[23:30] <teward> and the details of "limited UA-I" vs. "UA-I Essential full coverage"
[23:30] <linaporras> ok, we have to go back to this topic on the next month for sure
[23:30] <teward> madhens: so RE: Ubuntu Advantage, I know the limits of what is "covered" by the limited Ubuntu Advantage ;)
[23:31] <teward> (i have additional benefits thanks to Mark like Landscape as a Service access, but that's beyond the UA-I et of stuff)
[23:31] <teward> *sips caffeine*
[23:31] <linaporras> oks
[23:31] <linaporras> #topic IRC council update
[23:31] <teward> but yeah as for the definitions for ESM, End of SUpport, Etc. **Those** are needed to issue governance in other sections not just Membership and UA-I stuff
[23:31] <teward> linaporras: i have info on that
[23:31] <linaporras> +1
[23:31] <teward> IRC Council is all up for reelection.  Three are not going to be rerunning.
[23:31] <teward> no details on the other two
[23:32] <teward> i'm keeping a pulse on it
[23:32] <teward> the tentative schedule is on the original post lemme grab that link
[23:32] <Eickmeyer> teward: The other two are stepping-down early with the others.
[23:32] <Eickmeyer> Essentially, all 5 positions are up.
[23:32] <teward> Eickmeyer: ah, okay, that was not what dax told me :P
[23:32] <Eickmeyer> teward: That's what the email said.
[23:32] <teward> but yes, with all five positions up, they're going to need 5 nominees.
[23:32] <teward> https://lists.ubuntu.com/archives/ubuntu-irc/2021-March/001912.html
[23:32] <teward> Essentially, I'm keeping a pulse on it
[23:33] <teward> if there's not enough nominations by the 5th IRCC said they'd just keep it open until they get enough nominations.
[23:33] <teward> or... unless we stop it and do something more 'drastic'
[23:33] <teward> I'm considering adding my name, the IRCC isn't a heavy-workload thing like Lubuntu Council or others are
[23:33] <teward> but i'm sitting to see if *any* nominations come in first
[23:33] <teward> s/sitting/sitting on my hands/
[23:33] <teward> as i'm on<EMAIL_ADDRESS>i'll see any nominations as they're filed
[23:34] <teward> (been subbed to that list since Eons)
[23:34] <linaporras> so this topic so far is updated and we will back with this in case they do not reach enough nominations
[23:34] <teward> yep, i'll bring it up if there's not enough nominations.  OR if they have to keep extending it
[23:34] <teward> worst case they get *zero* nominations (or 1 if I put my name in)
[23:35] <linaporras> ok
[23:35] <linaporras> #topic LCRC next steps
[23:35] <teward> but we'll cross that bridge when we get there for IRCC
[23:35] <toddy> ok
[23:36] <linaporras> Regarding the LCRC there is one person that have no answer my e-mail, however... I will try my best to schedule the meeting for the coming weekend or monday... which seems to suit for most of the members...  If everything is ok, I hope to announce the event no later than friday...  I will be in touch with u with updates on this
[23:37] <toddy> I will try to be present at the meeting.
[23:37] <nhaines> Me too, if I'm available.
[23:37] <linaporras> that's great!
[23:38] <linaporras> I do not have any more news on that, and that was the last topic.
[23:38] <toddy> I think we don't need all of the cc but it would be nice if three or four could be there
[23:39] <linaporras> totally agree!
[23:39] <linaporras> I guess is other topic
[23:39] <toddy> Than new business. We got the topic of the shop on the Mailing list
[23:39] <teward> toddy: I don't think we can do anything on that.
[23:39] <linaporras> the ubuntu products and web shop...
[23:39] <madhens> I have an update from Popey on the shop
[23:39] <teward> #topic Ubuntu Products / Web Shop (ML item)
[23:39] <linaporras> jajaja yes toddy
[23:39] <teward> madhens: go ahead
[23:39] <linaporras> #topic  Ubuntu products and web shop
[23:40] <teward> linaporras: i already was 3 steps ahead sorry :)
[23:40] <teward> ERR:CAFFEINATED
[23:40] <madhens> Basically, the conversations and plans around it are still delayed because of COVID.
[23:40] <linaporras> Sorry teward  I sent it befor read it :s
[23:40] <toddy> :D
[23:40] <madhens> Shipping is a major issue, and there is still a bunch of merchandise in BlueFin, which is still locked down.
[23:42] <madhens> So it it's been on hold, and we do plan to do it, but it hasn't moved forward for a bit. I will find out who I need to talk to directly and see if I can get any more detailed of an update for the next meeting.
[23:42] <linaporras> oh! and is there  any news regarding when the lock down will end...?
[23:42] <teward> madhens: and all: I believe we might want to make a note in the thread that "Because there's COVID, we have no ETA for this at a time."
[23:42] <teward> s/there's/of/
[23:42] <linaporras> I mean the lock down of BlueFIn
[23:42] <teward> that this is still on the radar, but because of COVID and the lockdown on BlueFin and other things going on we don't have an ETA at this time of it returning.
[23:42] <madhens> I will definitely add that note, that progress is also contingent on ending/mitigating a pandemic. :(
[23:42] <teward> linaporras: i meant in general so they don't think we're blowing them off
[23:42] <teward> madhens: indeed.
[23:43] <toddy> madhens: thanks for the update
[23:43] <madhens> Of course!
[23:44] <linaporras> oh ok... hope vaccines help to unlock us all  soon!!!!!!!!
[23:44] <teward> second dose of the Pfizer vaccine for me in 2 weeks
[23:44] <teward> (April 2)
[23:44] <toddy> linaporras: I hope so
[23:44] <linaporras> oh teward  I wish I have that luck here... :s
[23:45] <linaporras> Glad for u
[23:45] <linaporras> So... i think that we have finished that topic.
[23:45] <toddy> ok
[23:45] <linaporras> is there any other topic that u want to discuss?
[23:45] <teward> other than the fact IRC irritates me sometimes, not really :P
[23:45] <nhaines> I don't have anything else at this time.
[23:45] <linaporras> jajajajajaj
[23:45] <madhens> I have updates on Inclusive Naming
[23:45] <toddy> nope
[23:45] <linaporras> oh that's cool
[23:46] <linaporras> #topic  Inclusive Naming
[23:46] <toddy> madhens: Oh which kind of updates :)
[23:46] <Eickmeyer> I'm still waiting to get my first dose, but Idaho is super slow and even though I'm high risk I can't get mine yet.
[23:46] <linaporras> go ahed madhens
[23:46] <toddy> Eickmeyer: Germany is also slow :/
[23:46] <linaporras> *ahead
[23:48] <madhens> So there is a very organized group at Canonical working on this, getting buy in from teams, and not only identifying artifacts to change, but working on guidelines for the future. I am on the group, and we just had our kickoff meeting today. While it seems like initial focus is on canonical-produced documents, i am stressing the next stage should be working with the volunteer community for volunteer-produced
[23:48] <madhens> documentation.
[23:48] <nhaines> Oh, that's great.  :)
[23:48] <toddy> cool
[23:48] <Eickmeyer> Just booked my first dose. Next week opened-up so I jumped on that.
[23:48] <madhens> I had to do the kickoff meeting in a car with a horrible phone, because coming back from first vaccine (!), but things are very much organized and in motion!
[23:49] <linaporras> That's really good news....
[23:49] <toddy> madhens: that are very good news
[23:49] <toddy> I like the idea with inclusive naming :)
[23:49] <madhens> Also, slightly related, but Women's Resource Group did a workshop attended by 70 people, including VPs, and I made sure to mention we should have actions and future events that involve the entire community - employees and volunteers.
[23:50] <teward> nice!
[23:51] <nhaines> These are good developments.
[23:51] <linaporras> I think that some kind of awareness for the community regarding Inclusive naming could be useful... I do not know... maybe a wiki page, videos... or both...  the reason why I think that is useful is that with some colleagues here in my country they are not too much aware and still they are not sensitive with this topic...
[23:51] <linaporras> awesome madhens
[23:51] <madhens> And those are our major updates! Lubuntu legal and community funding are still progressing. Community funding quite well, Lubuntu more slowly.
[23:52] <madhens> Thanks all!
[23:52] <linaporras> Do u think that for next meeting the funding could be a topic... or ...?
[23:52] <teward> madhens: regarding "Community Funding" we need to have an internal discussion on what people can request from the community funding pools.
[23:52] <linaporras> wait more jeje
[23:53] <linaporras> I agree, and what, how much, how frequently...
[23:53] <teward> because there's **extreme** discrepancy between what's been published on what you can request, and what the 'practice' is so things need up to date
[23:53] <teward> among the other things, also, yes.
[23:53] <linaporras> I totally agree...
[23:53] <toddy> teward: yes that is true
[23:53] <teward> except the amount of concerns I have is a little beyond what can be discussed on iRC
[23:54] <madhens> Let me chat with Rhys and Claire Nerman on my end, you all have a talk, and we can start resolving discrepancies
[23:54] <teward> so if we can arrange a call between me and someone (you guys?) at Canonical to discuss in depth that'd be wonderful.
[23:54] <teward> madhens: ok.
[23:54] <teward> i'll bring my list of discrepancies to our ML internally.
[23:54] <linaporras> So... we can discuss or elaborate some ideas in a gdoc before... and after bring it here for vote...
[23:54] <teward> then we can send you the full list.
[23:54] <madhens> tedward: send me an e-mail at<EMAIL_ADDRESS>and we'll get that talk in as soon as we can.
[23:54] <linaporras> cool! teward
[23:54] <nhaines> madhens: That is a nice, fancy email address.  :)
[23:55] <madhens> Me and my fancy schmancy hyphenated name :)
[23:55] <teward> madhens: wil do
[23:56] <nhaines> teward: I'll look forward to participating, because I've benefitted nicely from the community funding pool (current outstanding request not... withstanding), and I've tried to urge others to request resources when they have great ideas.
[23:56] <linaporras> ok, so teward you will be in charge to sent the e-mail... and we all participated on the discussion, is that ok?
[23:56] <teward> yep.
[23:56] <teward> i still need to get some clarification on my Two Rejected REquests In The Past, but that's a different issue
[23:56] <linaporras> Cool, any other new business?
[23:57] <teward> (the remaining things that WOULD get community funding requests are being handled via Lubuntu because it's for Their Benefit.)
[23:57] <teward> (but that's not a CC concern)
[23:58] <nhaines> That's all for me.
[23:58] <jose> nothingh ere
[23:58] <teward> nothing here.
[23:58] <madhens> That's all I had.
[23:58] <toddy> nope no new business here
[23:58] <linaporras> ok
[23:58] <linaporras> so anyone wants to chair next meeting?
[23:59] <teward> *sips coffee* i'm probably due to, sl me.
[23:59] <teward> so*
[23:59] <linaporras> jajaja ok teward  so you will be the next chair
[23:59] <linaporras> ☕
[23:59] <toddy> ☕☕☕☕☕