[13:54] <minimal> could someone review PR 626 please?
[14:55] <meena> minimal: well,uhm. yeah, not much i can do today
[14:58] <smoser> minimal: well i helpfully made a bikeshed whitespace comment :-(
[14:58] <smoser> the thing generally looks fine to me... in that your tests are present, but i didnt do a thoughtful review
[15:01]  * meena is all over the place… since… at least a few… months?
[15:05] <staples> Hi all, I am struggling with running cloud-init for custom-built AMI (Ubuntu 18.04 based) in AWS ec2 user data section. Essentially, it appears that cloud_final_modules (scripts_user and write_files) is not triggering.
[15:05] <staples> Content-Type: multipart/mixed; boundary="//"MIME-Version: 1.0--//Content-Type: text/cloud-config; charset="us-ascii"MIME-Version: 1.0Content-Transfer-Encoding: 7bitContent-Disposition: attachment; filename="cloud-config.txt"#cloud-configcloud_final_modules:- [scripts_user, always]- [write_files, always]apt_update: trueapt_upgrade: truepackages:  -
[15:05] <staples> openssh-serverwrite_files:
[15:06] <staples> this is my script. Can anyone help me here?
[15:07] <staples> I also tried with bash script with no luck. It seems to me that user data never executes on the machine.
[15:08] <paride> https://github.com/canonical/cloud-utils/pull/19 changelog update for cloud-utils 0.32 (from `git log | log2dch, as I think the previous entries were generated)
[15:08] <paride> Odd_Bloke, smoser ^^
[15:10] <staples> I suspect that it does not do it because it is custom AMI and because original /etc/cloud/cloud.cfg does not have these modules that I try to run with user data. Unfortunately, there is no option to rebake the image
[15:11] <minimal> paride: As you're here, any chance of a cloud-utils release soon? The last one was a long time ago and since then growpart has added LVM support which is something useful for cloud-init.
[15:11] <paride> minimal, that's exactly what that PR is for :)
[15:12] <minimal> paride: a cool, I'd mentioned it to Odd_Bloke last week so he'd said he'd ask about. Thanks!
[15:13] <paride> minimal, yep we decided to cut a new release after your ping about it
[15:14] <minimal> cool. I'm the cloud-utils (and cloud-init) maintainer for Alpine Linux so I'll be ready to package it up as soon as its out ;-)
[15:20] <AscII> I signed the CLA on LP when I added the Hetzner Cloud DS. Is this sufficient for https://github.com/canonical/cloud-init/pull/629 ?
[15:21] <AscII> Proof via https://code.launchpad.net/~lp-markusschade/cloud-init/+git/cloud-init/+ref/migrate-lp-to-github
[15:22] <AscII> I have seen that smoser has moved dmi functions out of util
[15:22] <AscII> So I guess depending on when it is merge I would have to rebase https://github.com/canonical/cloud-init/pull/630
[15:25] <meena> every damn time i update a bug on Launchpad and get an email about it, i'm like: OH! SOMEONE UPDATED MY BUG?!
[16:47] <paride> meena, I think you can disable that. https://launchpad.net/~minagalic/+edit should have a "Send me bug notifications for changes I make" setting
[18:21] <Hawk_X> Hello to all! I guess it is a recurrent question. I couldn't find an answer on the FAQ. What would be the best reference documentation on how to use "locally" user-data?
[18:22] <Hawk_X> I want to autoconfigure with cloud-init a KVM VM ran locally with the CDROM ISO mechanism and the documentation is not clear...
[18:22] <Hawk_X> On if it is the same as running the user-data file from the ISO or directly on a cloud instance.
[18:23] <Hawk_X> Of course this is a rookie question, hopefully it doesn't have a not too obvious answer...
[18:26] <Hawk_X> Thanks for any answer! :-)
[18:29] <rharper> Hawk_X: user-data should behave the same whether it comes from cdrom NoCloud datasource, or if the user-data comes from EC2's meta-data service;  I *think* that was what you were asking;
[18:35] <Odd_Bloke> rharper: I've updated https://github.com/canonical/cloud-init/pull/609/ with a fresh approach (and some tests), FYI.
[18:35] <rharper> ok
[18:36] <Odd_Bloke> blackboxsw: falcojr: ^ is the update I mentioned was coming in stand-up.
[18:39] <Hawk_X> You are right rharper Thanks!
[18:40] <Hawk_X> Now the next obvious question is, what is the best repository of examples for documentation on cloud init for ubuntu 20 instance?
[18:40] <Hawk_X> I know, it is obvious for many people but I really can't find how to set an static IP on user-data, from what I read it is part of meta-data but I can't get it to work with the ISO file.
[18:41] <Hawk_X> And also, from the website: https://cloudinit.readthedocs.io/en/latest/topics/examples.html it appears that the option to use pwauth over SSH is now gone.
[18:42] <Hawk_X> I have a user-data file that I ran on Ubuntu 16.04 that did work with ssh pw auth that is not working now on Ubuntu 20.04 Instance...
[18:43] <rharper> Hawk_X: you cannot supply network-config via user-data as network config must be applied before cloud-init fetches user-data;  some datasources, like NoCloud or ConfigDrive can accept network-config separately from user-data;  on clouds, network-config typically comes from the instance metadata service
[18:45] <Hawk_X> yes, so I can't supply network-config from the meta-data file over an ISO file.
[18:45] <rharper> Hawk_X: re: ssh pwauth, not clear what you mean; do you have a user-data file with the example config that's not working? I routinely launch with: #cloud-config\npassword: <some passwd>\nchpasswd: { expire: False}\nssh_pwauth: True;   and I can ssh in and enter a password (though typically I import an ssh public key
[18:45] <rharper> Hawk_X: in network-config, not meta-data
[18:45] <Hawk_X> And I can't supply network-config over the ISO or can I?
[18:45] <rharper> you can, depends on your Datasource
[18:46] <Hawk_X> I couldn't find any doc that tells me that is supported.
[18:46] <rharper> the NoCloud datasource, reads meta-data, user-data, network-config files;   the ConfigDrive datasource has a different directory structure, it reads a network-config file (which is in ifupdown format) and a network-data.json format (which is what openstack metadata service provides)
[18:46] <Hawk_X> I hope and not saying something stupid but it is a nocluod environment running on KVM in ubuntu 20.04
[18:47] <rharper> https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
[18:47] <rharper> Network configuration can also be provided to cloud-init in either Networking Config Version 1 or Networking Config Version 2 by providing that yaml formatted data in a file named network-config. If found, this file will override a network-interfaces file.
[18:48] <rharper> that could use some re-wording to make it more obvious
[18:48] <Hawk_X> Nice. rharper that last part is what I needed to read
[18:48] <Hawk_X> Yes, it isn't quite clear. Let me give it a go as I have the environment ready.
[18:49] <Hawk_X> REgarding the ssh_pwauth I will try the file you've wrote as I want to create a customer user.
[18:49] <Hawk_X> And user pwauth for it and for the love of me it doesn't works...
[18:49] <Hawk_X> This is what I am using:
[18:50] <rharper> https://paste.ubuntu.com/
[18:50] <rharper> Hawk_X: ^ if you want to share user-data;
[18:51] <Hawk_X> Thanks rharper
[18:51] <Hawk_X> https://paste.ubuntu.com/p/BXSn5WxJnD/
[18:53] <Hawk_X> I install the vm with virt-install and connect using SSH and the password is not accepted. The ssh key does.
[18:54] <Hawk_X> I looked at the /var/log/cloud-init.log file and I searched for "ssh_pwauth" and nothing match
[19:01] <rharper> I don't see anything wrong with that;  does the log show any other errors?
[19:01] <rharper> Hawk_X: look for: 2020-10-27 19:01:09,324 - ssh_util.py[DEBUG]: line 58: option PasswordAuthentication updated no -> yes
[19:01] <rharper>
[19:02] <rharper> now for your user login, look for cloudinit.config.cc_users_groups  in the log, should see what it's doing , like  Running hidden command to protect sensitive input/output logstring: ['useradd', 'rharper', '--shell', '/bin/bash', '-m']
[19:02] <Hawk_X> That I can look for. I am spinning up the instance
[19:08] <Hawk_X> Much appreciated!
[19:22] <Hawk_X> rharper, it says "yes"
[19:26] <rharper> cool, so ssh pwauth worked (it changes sshd config to allow password login over ssh)
[19:27] <rharper> so your remaining issue is your new user and the password;  I suggest importing an ssh key for the default user; and then login as the default user to help debug the secondary user
[19:37] <meena> paride: but then nobody will mail me :P
[19:57] <Hawk_X> Yes, but for some reason the network-config file config is not being accepted by cloudinit
[19:57] <Hawk_X> So the interface is brought up but not configured.
[19:57] <Hawk_X> I am looking at the logs now.
[20:10] <Hawk_X> Still looking...
[20:18] <rharper> Hawk_X: you can paste me your network-config file from the nocloud iso;  the cloud-init log file is usually pretty verbose about network config it applies and writes;
[20:46] <meena> smoser: i made the executive decision to resolve this comment: https://github.com/canonical/cloud-init/pull/625#discussion_r512296035
[21:00] <smoser> what does resolve mean in that scenario?
[21:01] <meena> smoser: i clicked the resolve conversation button, after explaining that Puppet Facter also calls jails `jail` and not `bsd-jail`
[21:02] <smoser> oh. i see.
[21:02] <meena> i could look at chef and salt and ansible for other clues
[21:02] <smoser> never mind.
[21:02] <smoser> thats fine.
[21:05] <Odd_Bloke> AnhVoMSFT: Would you be able to take a look at https://bugs.launchpad.net/cloud-init/+bug/1901011?  It relates to new Azure instance types that seem to be causing some issues with the Azure DS.
[21:46] <Hawk_X> Thanks to rharper for the assist.
[21:46] <Hawk_X> Unfortunately, the network-config is not being accepted by ubuntu. Here's the pastebin: https://paste.ubuntu.com/p/b6F2j8xhpH/
[21:46] <Hawk_X> I tried with the match and no match option for the MAC. Which it doesn't make sense to me as I do not know the MAC address to match it...
[21:47] <Hawk_X> Either way, it doesn't recognize the network config and the instance boots without IP :-(
[21:48] <Hawk_X> The cloud-init.log complains about some parameters but as I can't put an IP on the instance I can't paste the exact error here.
[21:49] <meena> eh?
[21:50] <meena> you have no (virtual) serial console access to the machine?
[21:51] <meena> Hawk_X: worst case, you could post a screenshot
[22:03] <rharper> Hawk_X: your nameservers is incorrect format, it's namesevers: addresses: [<IP_ADDRESS>]
[22:18] <Hawk_X> Thanks!
[22:18] <Hawk_X> I have virtual console access
[22:36] <Hawk_X> Apologies, I thought I would be receiving an answer soon. Much appreciated.
[22:36] <Hawk_X> Spinning a new instance now. BRB
[23:17] <Hawk_X> Ladies and Gentlemen unfortunately, the day caught up with me. I didn't have the time to spin the other instance. I will try to do it later tonight or tomorrow morning
[23:17] <Hawk_X> Thanks again for all your assistance!
[23:22] <johnsonshi> Odd_Bloke: I'm taking a look at https://bugs.launchpad.net/cloud-init/+bug/1901011 now
[23:24] <johnsonshi> Yes indeed, there are new instance types that don't have ephemeral resource disks. We're discussing internally about this issue.


[12:06] <apw> hanfm, that is most likley to be a bug in either cron or libpthread i would assume, it is reporting that that application core dumped
[12:14] <popey> are we including https://git.kernel.org/linus/9c4f61f01d269815bb7c37be3ede59c5587747c6 in 15.04? (ref https://btrfs.wiki.kernel.org/index.php/Gotchas)?
[16:19] <stgraber> ogasawara: hey, any chance we can reschedule the lxc/lxd sync to be earlier on Tuesday? hallyn will be around on Monday and Tuesday but has to leave around 3pm.
[16:19] <ogasawara> stgraber: sure, lemme shuffle things around
[16:19] <stgraber> ogasawara: thanks
[16:20] <hallyn> thanks
[23:46] <pepee> apw, are you here?
[23:50] <infinity> pepee: It's 1am for him, I'd guess "no".
[23:50] <pepee> oh, sorry
[23:51] <pepee> anyway.. I was wondering, will there be a fix for this bug in trusty, too?  https://bugs.launchpad.net/ubuntu/utopic/+source/linux/+bug/1313804
[23:51] <infinity> zequence: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1442400
[23:53] <infinity> pepee: You might want to comment on the bug and mention that it's a problem in the trusty kernel.
[23:54] <pepee> the bug report itself includes that info, infinity
[23:55] <pepee> the "feature" never worked in these laptops, with the radeon driver, afaiu
[23:55] <infinity> pepee: Ahh, indeed, I missed the 3.13 reference.
[23:56] <infinity> pepee: Added a trusty task, we'll see.
[23:57] <pepee> thanks
[23:59] <pepee> yeah, I didn't understand why it wasn't added


[16:08] <makumba> helllo
[16:08] <makumba> I can't install kernel.org
[16:09] <jeremy31> That isn't a supported topic here
[16:16] <makumba> where can I go
[16:17] <makumba> I want to make a pendrive with triple boot
[16:17] <makumba> ubuntu  red hat and kernel.org
[16:17] <jeremy31> This is the place for Ubuntu kernel issues, kernel.org is not an OS
[16:18] <makumba> kernel-linux 5 edition
[16:19] <makumba> from kernel.org
[16:19] <jeremy31> The linux kernel 5 is available in all supported Ubuntu versions
[16:21] <makumba> ok, what Iam doing is a grub loader with 3 Op system in a pendrive with 32gb
[16:21] <makumba> can you help me
[16:21] <sixwheeledbeast> kernel is the kernel not the os
[16:23] <makumba> so what is the page kernel.org
[16:25] <sixwheeledbeast> the kernel
[16:25] <makumba> ok
[16:26] <makumba> I also need a bot software can you help me
[16:26] <makumba> the only one thats shows up is eggdropp
[16:26] <sixwheeledbeast> linux/GNU is on top of the kernel. It's a off topic question but your probably looking for something like YUMI
[16:26] <makumba> Fedora?
[16:28] <makumba> is energymech goos
[16:28] <makumba> is energymech good boot
[16:29] <makumba> because my channel is on ryzon
[16:34] <makumba> ok bye
[16:34] <makumba> see ya


[00:07] <vychune> o/
[00:10] <netritious> howdy vychune
[00:12] <vychune> ready for this meet?
[00:12] <vychune> i'll only be here 30 mins i work tonight
[00:13] <netritious> yep i'm ready
[00:15] <netritious> it doesn't start until 7:30 however
[00:16] <vychune> of course
[00:16] <vychune> brb
[00:20] <Svpernova09> HAI netritious
[00:20] <Svpernova09> >.>
[00:20] <netritious> hey there Svpernova09!
[00:21] <netritious> what are you doing here? lol, you know what I mean.
[00:22] <netritious> ping alyawn binarymutant cyberanger Juzzy orias pace_t_zulu Svpernova09 vychune wrst
[00:23] <vychune> pong
[00:23] <netritious> meeting starts in seven minutes
[00:23] <Juzzy> heh
[00:23] <Juzzy> omg yes
[00:23] <Juzzy> whats today's agenda?
[00:23] <netritious> unofficially leadership elections
[00:25] <netritious> and/or some chat about the LoCo
[00:26] <cyberanger> netritious: let me check something
[00:26]  * orias looks for refreshments
[00:26]  * netritious hands orias a tall one
[00:27] <netritious> howdy cyberanger
[00:29] <netritious> pace_t_zulu: you around?
[00:30] <cyberanger> netritious: terms expire this meeting, so not late on that, just on time
[00:30] <netritious> I was pretty sure it was August, but thanks for double-checking cyberanger
[00:31] <netritious> let me switch machines
[00:31] <netritious> there we go
[00:32] <netritious> I'm ready when everyone else is ready. I'm more than happy to wait on stragglers though.
[00:36] <vychune> i may be in and out cooking
[00:36] <netritious> k
[00:37] <cyberanger> just a sml bot
[00:38] <netritious> sml cyberanger?
[00:38] <netritious> is that like effe emme elle?
[00:39] <cyberanger> small bit
[00:40] <netritious> let's get this party started ya'll
[00:40] <cyberanger> operating at 9600 baud, not fun
[00:40] <cyberanger> #startmeeting
[00:40] <meetingology> Meeting started Fri Aug  3 00:40:44 2012 UTC.  The chair is cyberanger. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[00:40] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[00:40] <netritious> ouch
[00:41] <cyberanger> netritious: high latency too (satellite phone)
[00:41] <netritious> eeek
[00:41] <cyberanger> #chair netritious
[00:41] <meetingology> Current chairs: cyberanger netritious
[00:41] <cyberanger> wrst: you here?
[00:41] <cyberanger> #chair wrst
[00:41] <meetingology> Current chairs: cyberanger netritious wrst
[00:42] <netritious> I would rather you chair cyberanger, but I'll try if needed.
[00:43] <cyberanger> netritious: take another look, it's three chairs
[00:43] <cyberanger> meetingology: has some new tricks the old bot didn't have
[00:43] <meetingology> cyberanger: Error: "has" is not a valid command.
[00:43] <cyberanger> and is still new enough to be dumb at moments ^
[00:44] <vychune> LOL
[00:44] <netritious> nice. where /is/ wrst?
[00:44] <cyberanger> netritious: wrst you & myself are all chairing it
[00:44] <vychune> im showing away in xchat
[00:44] <netritious> let's do roll call?
[00:44] <cyberanger> wrst: attending to family perhaps
[00:44] <netritious> most likely
[00:45] <vychune> whered Svpernova09 and orias go?
[00:45] <vychune> netritious: reping maybe?
[00:45] <orias> >.>
[00:46] <vychune> <.<
[00:46] <cyberanger> netritious: per the blog post...
[00:46] <cyberanger> # A minimum of six members should be present to hold elections.
[00:46] <cyberanger> # It is preferable that a minimum of two members from each region attend the elections.
[00:47] <cyberanger> however, having four is better than some prior meetings
[00:47] <netritious> Right, and elections doesn't have to happen, but the meeting should.
[00:47] <netritious> that's why all headers end in (unofficial)
[00:47] <netritious> on the blog post
[00:47] <cyberanger> netritious: if elections don't happen, what do you propose, one month extension
[00:47] <cyberanger> west tn does have enough for it's region though
[00:48] <cyberanger> lemme see something real quick (over 9600 baud, might not be THAT quick)
[00:48] <netritious> raise your hand if you're here for the meeting please?
[00:48] <netritious> o/
[00:48] <cyberanger> here
[00:49] <orias> o/
[00:49] <alyawn> lol... here :)
[00:50] <cyberanger> I happen to know Ubik is out of town today, so he might be more focused on his trip (we'll see)
[00:51] <cyberanger> Ubik: you here?
[00:51] <netritious> well there is four :) better than two, and who knows, someone might show up.
[00:52] <cyberanger> netritious: everyone besides Ubik & Svpernova09 have been idle for over an hour, Svpernova09 over a half and Ubik about a minute
[00:53] <cyberanger> so... your all west tn, do you want to do any elections on your seat
[00:53] <cyberanger> I'm neutral, east tn, but there's 3 of you here, so...?
[00:53] <netritious> we could or we could talk about LoCo biz
[00:53] <vychune> o/
[00:54] <netritious> yes vychune?
[00:54] <cyberanger> alyawn: remind me, your metro knoxville, yes
[00:54] <cyberanger> ?
[00:54] <alyawn> chattanooga
[00:54] <orias> we can, or just let it be if there's no changes
[00:54] <vychune> raising hand for presence late sorry
[00:54] <cyberanger> even better, my area ;-)
[00:54] <alyawn> heh
[00:54] <netritious> awesome, and then there was five.
[00:54] <alyawn> you're the one hogging my bandwidth then :)
[00:55] <cyberanger> not likely
[00:55] <cyberanger> netritious: so, no middle, two in east tn, 3 in west, loco biz, your call
[00:56] <netritious> I motion we postpone elections until we get the minimum (logical yet unofficial) attendees
[00:57] <netritious> *number of attendees
[00:57] <cyberanger> netritious: well, when was the last time we've had 6 people
[00:57] <cyberanger> w4ett's days? more recent?
[00:58] <netritious> when was the last time we had five? my point being, it's not important I don' think.
[00:58] <vychune> why not use a different method of voting, that enable absentee votes?
[00:58] <cyberanger> just asking to grasp if that's a high number, or not
[00:58] <netritious> ok, how about...
[00:59] <cyberanger> netritious: if it's not important, why postpone till we have it?
[00:59] <netritious> So is the motion not carried or...?
[00:59] <cyberanger> we can postpone it for this meeting at least, if there's a better issue to takle atm
[01:00] <alyawn> I'm usually available on here, provided I get a ping
[01:00] <cyberanger> but I can't really second it, if it'll keep getting tabled
[01:01] <cyberanger> if it's not having 6, I can table it saying "restructing voting rules" or something
[01:01] <netritious> I think the two w tn poc's are fine.
[01:01] <netritious> Does anyone have a nomination for w tn point of contact?
[01:01] <cyberanger> netritious: so, extend current terms one month, to focus on current issues this meeting, is that the motion?
[01:02] <netritious> currently it is Svpernova09 and orias I believe.
[01:02] <cyberanger> netritious: that's correct
[01:02] <vychune> nova and orias are good with me
[01:02] <cyberanger> they're terms were automatically extended
[01:03] <netritious> yeah, me to. I thought that if we didn't vote they would serve another term?
[01:03] <cyberanger> (last election we were short on west tn, so after voting the rest, there was a vote to automatically renew, pending a step down letter or a challenge or something)
[01:03] <netritious> so yeah, no need to vote I guess? then not really postponing.
[01:04] <alyawn> sounds logical
[01:04] <netritious> I motion that we move along lol.
[01:04] <cyberanger> netritious: so are we extending for the default 6 mo term, or just a one month postpone of elections
[01:04] <cyberanger> seconded
[01:05] <cyberanger> (sounds like we're agreed current leadership works for at least a month, worry about next month then)
[01:05] <cyberanger> any opposed?
[01:06] <vychune> no
[01:06] <netritious> no
[01:07] <cyberanger> [agreed] extend leadership term
[01:07] <cyberanger> netritious: next item
[01:08] <cyberanger> ( meetingology, unlike mootbot, is silent, no ack)
[01:08] <netritious> #topic Increasing attendance to the monthly LoCo IRC meetings, or is it important?
[01:09] <netritious> meetingology: #topic Increasing attendance to the monthly LoCo IRC meetings, or is it important?
[01:09] <meetingology> netritious: Error: "#topic" is not a valid command.
[01:09]  * netritious is a chair n00b
[01:09] <cyberanger> [topic]Increasing attendance to the monthly LoCo IRC meetings, or is it important?
[01:09] <cyberanger> netritious: syntax change mootbot to meetingology
[01:10] <netritious> roger. thx cyberanger
[01:10] <cyberanger> on the one hand, I can't make meetings on thursday anymore (today is an exception that barely happened)
[01:10] <cyberanger> on the other, not sure it's right to talk about changing something to just the people that made it to the meeting
[01:11] <netritious> It does seem that receiving reminders does increase attendance, even if it's just a little.
[01:11] <cyberanger> that and elections has typically drawn more than avg too
[01:11] <alyawn> Any night other than Thursday would also be better for me
[01:11] <cyberanger> so I'd like to see that repeat for a normal one
[01:12] <netritious> cyberanger: I put it to the list, but no one replied with an issue for Thur. nights.
[01:12] <cyberanger> then there's an issue, as I replied
[01:12] <cyberanger> and saw others reply
[01:12] <netritious> I do know that Svpernova09 will be occupied on the first Thu of the month, you and alyawn to now.
[01:12] <netritious> hm, that's odd.
[01:13] <cyberanger> (granted, some that replied tripped mailman errors that only I saw, and they didn't repost I guess)
[01:14] <netritious> hm. seems odd.
[01:14] <netritious> regardless, you have a point. we shouldn't move a meeting night just b/c the ppl showed, well, showed.
[01:14] <alyawn> I only received the one email
[01:14] <vychune> sounds legit
[01:14] <cyberanger> I've had list issues since I enherited the list from w4ett
[01:15] <netritious> So weird that it was tested and eighteen replied?
[01:15] <cyberanger> netritious: becuase the errors weren't pass or fail
[01:15] <netritious> Back on topic though: How to increase attendance to these meetings?
[01:16] <netritious> One suggestion is to move the meeting night.
[01:16] <netritious> Any other suggestions?
[01:16] <cyberanger> some were members somehow getting the list, but getting flaged as non-members
[01:16] <cyberanger> others were mis-flagged as spam
[01:16] <alyawn> Incentives?
[01:16] <cyberanger> majority made it
[01:16] <netritious> Ah, yes, that would be good. A reason to come. :)
[01:17] <netritious> I would like to either use the meeting time to possibly start doing some tutorials, right here in IRC.
[01:17] <cyberanger> netritious: I think actually when 2 out of 5 say they have issues with thursday, and an additional member (that we know of) has that too, that's enough to make a motion of some kind on it
[01:18] <alyawn> tutorials such as?
[01:18] <vychune> apache?
[01:18] <cyberanger> not to change it outright, but at least find out what works for those who showed
[01:19] <netritious> alyawn: maybe make suggestions to the list?
[01:19] <alyawn> Well, maybe we should just defer meeting changes to list
[01:19] <cyberanger> alyawn: anything a member proposes (within reason, a howto on commiting a federal crime with ubuntu would be bad)
[01:19] <netritious> alyawn: good point.
[01:19] <alyawn> ok.. so the primary rule is Ubuntu specific for tutorials?
[01:19] <netritious> cyberanger: can you get some support on the mailing list issues you are having?
[01:20] <wrst> sorry i'm late!
[01:20] <netritious> doesn't mailman allow you to mark something not spam?
[01:20] <netritious> howdy wrst
[01:20] <wrst> hey netritious sorry been providing support and also getting ready to install ubuntu for my brother so hopefully that excuses me :)
[01:21] <netritious> you don't need an excuse wrst
[01:21] <cyberanger> netritious: not at a rate that helps, considering how much spam lists.ubuntu.com gets
[01:21]  * wrst checks out the informative scrollback
[01:22] <netritious> cyberanger: is the first Thur of every month the official meeting day for LoCo's?
[01:22] <cyberanger> I've had to disapprove 350 messages on avg for zero approvals, this month, about 500 disapproved, for 5-10 legit
[01:22] <cyberanger> netritious: each loco sets it
[01:22] <vychune> maybe post to the Ubuntu-TN G= some stuff?
[01:22] <netritious> Looks like we may need another list?
[01:22] <cyberanger> it's not a loco council thing, it's just what worked back in feb 2009
[01:22] <netritious> ah k, didn't know.
[01:23] <cyberanger> and the time was tweaked once for a few (namely jfenn2199 & myself)
[01:23] <netritious> But still, it concerns me that so many replied to the test, and you say so many replied that need to change the night of the meeting, but none of those came through?
[01:23] <cyberanger> netritious: the issues are getting support, just fighting time & the rate of spam in the mean time
[01:24] <netritious> cyberanger: are you the only one that can maintain the list?
[01:25] <netritious> If you need help managing it, I'd be glad to provide it.
[01:25] <cyberanger> the issue really boils down to members actually joining the list
[01:25] <wrst> yeah i could throw my hat in that ring also, i help with the support in an opensource project and the spam can be overwhelming for one person to maintain
[01:26] <netritious> alyawn: I would think the tutorials need to be Ubuntu centric yes.
[01:26] <cyberanger> the few others are too few and far between, I maintain it twice daily on avg
[01:26] <alyawn> netritious, thought so
[01:26] <wrst> i've gotta go now tend to sleep stuff, but cyberanger, good to see we have doubled attendance from the last meeting!!
[01:26] <cyberanger> I'll get wrst in on it too (middle tn leadership)
[01:27] <wrst> sleep stuff for the youn 'un
[01:27] <wrst> thanks cyberanger... i think
[01:27] <netritious> ok, sounds good.
[01:27] <cyberanger> wrst: don't worry, stay focused on lp, I got the list
[01:27] <cyberanger> we'll just back each other up as we've already done
[01:28] <cyberanger> as needed
[01:28] <wrst> ha ha ok cyberanger now that sounds like a plan
[01:28] <netritious> Eighteen members replied to the test. Only one  replied with a issue with Thur nights, and only one other in this meeting.
[01:28] <netritious> I don't think we need a motion for changing meeting nights, unless you make one cyberanger.
[01:28] <cyberanger> netritious: two, alyawn Svpernova09 & myself
[01:28] <netritious> Ah yes, true.
[01:29] <netritious> So three.
[01:29] <wrst> netritious: just curious would it work better for people during the daytime we seem to be having more irc activity then at present?
[01:29] <netritious> Three of eighteen that has signed up to the list and replied to the test.
[01:29] <cyberanger> I'm making a motion, tutorials as part of every other meeting, and making it a choice between the current day & time, and another day & time
[01:29] <cyberanger> and putting that on the list
[01:29] <netritious> Actually I just had a thought.
[01:30] <cyberanger> (with a clear way to absentee vote too) and approve one or another next meeting
[01:30] <netritious> There is no reaosn I can't start providing tutorials independently of these meetings.
[01:30] <cyberanger> that's the motion I propose (but I'm tabling the motion to hear you out)
[01:30] <netritious> Not at the same time as the meeting of course.
[01:31] <cyberanger> true, but I think it's spot on, we need to get back to meetups, tutorials, helping on irc, the forums
[01:31] <netritious> Sure, but I thought the current topic was how to increase attendance? Are we done with that?
[01:31] <cyberanger> if that's an incentive for some, why deny it
[01:32] <netritious> I think we ran everyone off. There was traciton now none, lol.
[01:32] <cyberanger> vychune: still here
[01:32] <cyberanger> orias: still here
[01:32] <cyberanger> alyawn: still here?
[01:32] <alyawn> I think tutorials in a group session could be good, but will need to be time limited
[01:32] <alyawn> and yes... still here
[01:32] <netritious> +1
[01:32] <wrst> alyawn: yep sometimes the meetings can be too long like make you want to shoot yourself long!
[01:32] <netritious> haha wrst
[01:33] <wrst> now i really have to go :)
[01:33] <wrst> not to shoot anyone!
[01:33] <alyawn> heh... good luck
[01:33] <cyberanger> yeah... still don't know how to truely resolve that one
[01:33] <orias> heh
[01:33] <netritious> cyberanger: I was mainly trying to brainstorm.
[01:34] <netritious> We have enough here to do that.
[01:34] <netritious> So sending meeting reminders help.
[01:35] <alyawn> yes... we need reminders of the reminders
[01:35] <netritious> Having incentive helps, like sharing information, maybe int he form of tutorials.
[01:35] <cyberanger> netritious: I follow, but I do think a motion should be made towards that meeting time, some might have been indifferent, and nobody proposed an alternative yet (despite some saying thursday was an issue)
[01:35] <vychune> o/
[01:35] <netritious> you made the motion and no one seconded.
[01:35] <netritious> vychune: are you seconding?
[01:36] <cyberanger> I actually tabled it, for discussion
[01:36] <vychune> no responding
[01:36] <netritious> Oh lol
[01:36] <cyberanger> since we don't have that second option,
[01:37] <cyberanger> alyawn: is a tuesday better?
[01:37] <alyawn> yes...
[01:37] <cyberanger> netritious: also, if it's not a vote, don't think we need a second, just an agreement
[01:38] <netritious> I disagree with changing the regularly scheduled meetings.
[01:38] <cyberanger> alyawn: say, fourth tuesday
[01:38] <cyberanger> netritious: I'm not changing it, just setting a second option, so we can get better input on the list & next meeting
[01:38] <alyawn> any tuesday is fine with me
[01:38] <netritious> Ah ok, makes complete sense.
[01:39] <cyberanger> I think if we had first thursday OR forth tuesday, it makes it a choice, people have to pick
[01:39] <netritious> I think that is adding more complexity than neccessary cyberanger.
[01:39] <netritious> We can't even get replies to the mailing list.
[01:40] <netritious> Not in a predictable fashion anyway.
[01:41] <cyberanger> netritious: I think people saying they can't make it, or it's hard to make it, and offering no alternatives isn't a resolution to the issue
[01:41] <netritious> So I guess a better question is, if the mailing list is not going to work to communicate to the LoCo members, for wahtever reason, what can be done to rectify the situation?
[01:41] <cyberanger> agreed on the list
[01:41] <cyberanger> netritious: the list worked, mostly
[01:42] <cyberanger> the three issues I saw was it became two threads, due to some replying to the daily archive, others to the actual thread
[01:42] <vychune> i think the biggest issue is the purpose
[01:42] <cyberanger> others replied from an address not registered to mailman (but cross checked with lp, were members)
[01:42] <netritious> vychune: +1
[01:43] <cyberanger> and the third was...maybe the third was resolved before this thread
[01:43] <vychune> we have to define the reason we do things
[01:43] <netritious> These meetings are not getting much accomplished. I feel like we are tlaking in circles here.
[01:43] <netritious> *talking
[01:43] <cyberanger> the purpose of a loco is defined
[01:43] <netritious> true
[01:43] <vychune> a loco
[01:44] <netritious> LoCo = Local Community
[01:44] <cyberanger> but not at a loco level, at the council level
[01:44] <vychune> but TN's loco may need more definition
[01:44] <netritious> We, the people here that registered on Launchpad, are Ubuntu LoCo Members
[01:44] <vychune> cyberanger: or that lol
[01:44] <vychune> right
[01:45] <cyberanger> ubuntu loco tennessee members, yes
[01:45] <cyberanger> members of the tennessee team
[01:46] <cyberanger> I think on the topic of meeting times, first thursday 8:30 ET 7:30 CT and 4th tues same time, should that go to the list, the adgenda on wp, so on
[01:46] <cyberanger> to be put to a decision on our next meeting on...
[01:47] <cyberanger> on the 6th of sept
[01:47] <vychune> cool
[01:47] <cyberanger> making that a motion
[01:47] <vychune> i think a topic sholud be made about getting more activites in here
[01:48] <netritious> but that put's meetings back to back
[01:48] <netritious> unless it;s a five week month of course
[01:48] <netritious> argh this keyboard layout
[01:48] <cyberanger> netritious: it puts two meetings in one month, but not back to back
[01:49] <cyberanger> if that was switched, we'd have a meeting on the 6th & 25th
[01:49] <cyberanger> for one month only
[01:49] <netritious> the 4th tuesday of the month and the first tues of the followign month is typically back to back
[01:49] <cyberanger> and we've don that before for elections once
[01:49] <netritious> *first thur
[01:50] <cyberanger> this month, this meeting, next month, on the 6th, a vote on which one to hold future meetings
[01:50] <cyberanger> opt. 1, keep the same, nothing is back to back
[01:51] <cyberanger> opt. 2, switch, sept 25th, next meeting after is oct. 23rd
[01:51] <cyberanger> so nothing is back to back (but sept would have two meetings due to the switch)
[01:51] <netritious> crap, gotta take this call guys. afk
[01:52] <cyberanger> vychune: agreed, but activities doesn't help some of us attend meetings (if it wasn't for the satphone I'm on, I'd be at work with no internet for this meeting, normally I'm on a work project or at church right now)
[01:54] <cyberanger> I think we need activities too
[01:54] <alyawn> How about a Ubuntu Use-of-the-Month just as a conversation topic
[01:55] <cyberanger> well, that may work
[01:56] <cyberanger> ah darn, I only had an hour and a half for the meeting, gotta get back to work
[01:56] <alyawn> one member gives a short Q&A for something they did or used ubuntu with/for
[01:56] <cyberanger> finish this project by morning
[01:56] <alyawn> good luck, cyberanger
[01:59] <vychune> o/
[01:59] <vychune> fedex time i gotta go
[01:59] <vychune> good talk guys
[01:59] <alyawn> cya <vychune>
[01:59] <vychune> o/
[02:19] <cyberanger> #endmeetimg
[02:19] <alyawn> heh... yeah
[02:19] <cyberanger> [endmeeting]
[02:19] <meetingology> Meeting ended Fri Aug  3 02:19:23 2012 UTC.
[02:19] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-us-tn/2012/ubuntu-us-tn.2012-08-03-00.40.moin.txt
[02:19] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-us-tn/2012/ubuntu-us-tn.2012-08-03-00.40.html
[02:22] <orias> nite!
[02:22] <Unit193> Good night.
[02:29] <Svpernova09> wheeeeeeeeeeeeeeeeeeeeeeeeeee
[02:29] <Svpernova09> p/
[02:29] <Svpernova09> o/
[04:01] <Svpernova09> o/
[04:13] <chris4585> wrst, ah, but still a post somewhere isn't exactly apart of the system / pacman
[04:13] <chris4585> but yeah if I looked hard enough I probably could have found it
[06:54] <chris4585> I love the history command
[07:03] <chris4585> oh man
[07:03] <chris4585> I think I just installed everything kde
[07:04]  * chris4585 bangs head on keyboard
[07:05] <chris4585> oh well :|
[10:26] <chris4585> I really wish my external hdd was just magically ext4 instead of fat32
[10:28] <binarymutant> that sucks
[10:29] <binarymutant> but any computer can read fat while ext is pretty specific
[10:32] <wrst> i keep my external on ext4, but its always connected to my server
[10:32] <chris4585> well yeah, only reason it isn't switch right now is it would be a hassle to move 200 something gigabytes just to reformat it
[10:33] <chris4585> I mean yeah, every computer can pretty much read fat but I don't ever take it anywhere lol
[10:41] <chris4585> so wrst, I accidentally installed "kde" last night lol
[10:41] <chris4585> when I just wanted kdebase
[10:41] <wrst> ha ha
[10:41] <wrst> how do you like it chris4585? :)
[10:41] <chris4585> dunno yet, I've been too busy doing internet stuff to play around with it lmao
[10:49] <wrst> i have to say its nice but i just can not get into using it
[11:20] <chris4585> yeah, same
[11:20] <chris4585> http://imgur.com/a/IRf3K#3
[11:20] <chris4585> "This is what I call productivity"
[11:21] <chris4585> http://imgur.com/a/IRf3K#0 ***
[11:58] <binarymutant> crap, ima have to redo my dual monitors :/
[12:00] <binarymutant> next meeting we should do a post-your-desktop-a-thon
[12:01] <wrst> binarymutant: thats a good idea!
[12:01] <binarymutant> I'm full of em
[12:01] <binarymutant> full of something :P
[12:01]  * wrst is glad that he didn't have to say that :)
[12:02] <binarymutant> lol
[12:06] <wrst> binarymutant: how is debian treating you?
[12:06] <binarymutant> it's okay, still trying to set everything up again
[12:07] <binarymutant> like dualmonitors
[12:07] <wrst> i just have a few shell extensions i have to get when i set a system up, i try to keep it basic so i don't have issues, i used to modify everything
[12:07] <chris4585> binarymutant, that sounds fun
[12:07] <chris4585> binarymutant, you purged arch? lol
[12:08] <binarymutant> yeah I really need to stop modifying the system and just run everything as a user. That way I won't have to do anything if I change distros
[12:08] <binarymutant> chris4585, yeah they made me mad
[12:08] <binarymutant> back on good ole debian
[12:08] <chris4585> lol? well whatever works
[12:10] <wrst> or doesn't work :)
[12:10] <binarymutant> brb gotta restart X
[12:11] <chris4585> the arch bigots have angered me before in #archlinux ? but that isn't a reason I would give up arch though
[12:15] <wrst> chris4585: you are a brave man
[12:16] <wrst> i don't speak in #archlinux
[12:16] <chris4585> yeah, well I guess I wont ever go back in there
[12:17] <chris4585> this guy just wanted to be a douche because his ego and elitism was showing, they were all fine until I said archbang
[12:18] <wrst> chris4585: i go to watch the show , its like watching the crocs feed feed on the poor animals trying to cross the river
[12:18] <wrst> they pick on the weak and the wounded
[12:18] <wrst> and i am generally both so i just try to blend in and watch :)
[12:18] <chris4585> apparently archbang is so different that mentioning a pacman related issue forced them to shove me out the door and look for help elsewhere
[12:19] <wrst> chris4585: they really don't care about the size of the community i think they prefer it to be small and elitist but they shouldn't have created such a good distro
[12:19] <chris4585> which was fine I got what I wanted, came back to let the guy know what the issue was and he said he already knew what the issue was
[12:19] <binarymutant> I almost installed archbang
[12:19] <chris4585> wrst, right?
[12:20] <chris4585> binarymutant, it was pretty much my easy way of installing arch, which really wasn't all that much easier because the installer is the exact same as arch's
[12:20] <chris4585> I just had gparted up with the installer
[12:20] <chris4585> :)
[12:21] <binarymutant> so do they have an installer still?
[12:21] <chris4585> I have no idea, I don't think they have updated their iso in a while
[12:21] <binarymutant> yeah the one I downloaded was from may I think
[12:22] <chris4585> yeah, that is the same one I installed
[12:22] <wrst> chris4585: i tried archbang and it seemd just like the AIF but it installed a desktop
[12:22] <binarymutant> yeah
[12:22] <binarymutant> openbox
[12:23] <chris4585> pretty much, then I just tweaked openbox to my liking.. which was weird because I started removing things after an install than installing
[12:23] <chris4585> I don't like tint
[12:23] <chris4585> tint2*
[12:24] <chris4585> basically imo archbang got me to the same place arch would have faster
[12:27] <binarymutant> seems like it should be the other way around
[12:29] <wrst> binarymutant:  thats not the arch way ;)
[12:31] <chris4585> it is a little bass ackwards but... I do the same thing on ubuntu and every other distro
[12:40] <chris4585> holy poop my old settings for kde are still here
[12:41] <chris4585> kwin is noticeably more slow without my nvidia card
[12:43] <wrst> kwin is a little bit of a hog, but it sure is pretty
[12:43] <chris4585> agreed, well I gotta get some sleep, later wrst and binarymutant
[12:44] <binarymutant> later
[13:04] <wrst> binarymutant: chris4585 must work the night shift :)
[14:18] <wrst> xTEMPLARx: wb
[14:30] <xTEMPLARx> wrst:  thank you sir!
[15:01] <wrst> we are just honored to be in your presence
[15:24]  * alyawn yawns......
[15:24] <alyawn> morning
[15:24] <alyawn> I may have fallen asleep during last nights meeting :)
[15:32] <alyawn> I just noticed that I have "nameserver <IP_ADDRESS>" in my resolve.conf
[15:33] <alyawn> I'm not running DNS, so that's a bit odd.
[15:33] <alyawn> I'm using dhcp for addressing.... hmm
[15:47] <xTEMPLARx> that's normal alyawn
[15:48] <alyawn> I guess
[15:48] <alyawn> just never noticed before...
[15:48] <alyawn> I also notice that dnsmasq is running
[15:48] <xTEMPLARx> its because the system is using dnsmasq for caching dns
[15:48] <xTEMPLARx> yup
[15:49] <xTEMPLARx> network manager sets it up that way
[15:49] <alyawn> just trying to figure out how/why my host name got put in  /etc/hosts as "<IP_ADDRESS> sleek"
[15:49] <alyawn> wonder what did that
[15:49] <xTEMPLARx> i discovered all of that when I was having problems with this box a  few weeks back
[15:49] <xTEMPLARx> that one I don't know :)
[15:50] <alyawn> I'd rather everything lookup my hostname with my router
[15:50] <alyawn> anyway... learn something new every day!
[15:56] <xTEMPLARx> oh it IS using your router
[15:56] <xTEMPLARx> if thats the way DHCP set you up
[15:56] <xTEMPLARx> its just caching stuff at your pc as well
[15:57] <xTEMPLARx> look up dnsmasq and see if you can configure it to always just do the lookup and not cache anything
[15:58] <xTEMPLARx> caching is fun, and breaks the ice at parties
[15:59] <wrst> xTEMPLARx: i always need something networking related to break the ice at parties, thanky ou
[16:00] <xTEMPLARx> also good to break the ice at NAUGHTY parties
[16:00] <xTEMPLARx> wink wink nudge nudge say no more
[16:00] <xTEMPLARx> a nod's as good as a wink to a blind bat
[16:01]  * xTEMPLARx is done with the monty python quotes
[16:13] <alyawn> I'm just jealous that I don't get invited to such parties
[16:14] <wrst> alyawn: don't worry xTEMPLARx doesn't either :)
[16:14]  * alyawn done with HHGTTG quotes :)
[19:07] <alyawn> any of you guys going to dragon*con
[19:09] <binarymutant> I wish
[19:26] <xTEMPLARx> i haven't gotten my pikachu costume back from the cleaners yet, so I'ma hafta pass
[19:40] <alyawn> heh
[19:40] <alyawn> I go for the D&D not the cosplay :)
[19:42] <xTEMPLARx> =]
[20:32] <binarymutant> back on dwm
[20:33] <binarymutant> back on debian and back on dwm, it's like 2009 all over again
[20:34] <cyberanger> alyawn: I'll be lucky to get to chattacon at this point, wish I could be at dragoncon
[20:51] <xTEMPLARx> have a good weekend you guys
[23:25] <binarymutant> sucks, I can't play UrT with the nouveau driver


[04:43] <hyperair> meh. mesa is so hard to cross-compile
[04:44] <hyperair> you have this stupid builtin_compiler thing that needs to be built using the --build compiler, and then chattr +i, make clean to get rid of all the native object files, and make again to finish cross compiling. pfft.
[04:45] <Sarvatt> hyperair: i'm hoping to have multiarch on natty and oneiric in edgers in the next week so it should be a bit easier
[10:45] <tseliot> tjaalton, RAOF, Sarvatt, bryceh: do you mind if I upload a new  mesa with versioned breaks on proprietary drivers?
[10:45] <tseliot> (otherwise my new drivers won't be installable)
[10:57] <tseliot> hmm... most of you must be on holiday...
[11:00] <tseliot> the git branch looks a little confusing
[11:00] <bryceh> tseliot, yes that's fine
[11:01] <bryceh> tseliot, in fact Sarvatt and I were planning on trying to figure out what needed done tomorrow
[11:01] <tseliot> bryceh: I guess the last commit was not uploaded even though there's no UNRELEASED word in the changelog
[11:01] <tseliot> commit a6aaf514c91a593d79e9ae8899798641d52d19de
[11:02] <tseliot> i.e. Fix !i386 !amd64 builds by only installing i915g there, ie: where it's actually built
[11:02] <bryceh> could be; I didn't talk with raof about it
[11:03] <tseliot> bryceh: I'm wondering if it's ok to upload that change if it's not already in
[11:03] <bryceh> I don't know; perhaps there was more raof needed to do?
[11:03] <bryceh> could he have uploaded it but it failed to build?
[11:04] <tseliot> had he uploaded the commit we should've seen at least something in the changelog in git
[11:05] <tseliot> bryceh: I guess they won't miss i915g on armel anyway ;)
[11:05] <bryceh> heh
[11:06] <tseliot> oh, wait there's something in the changelog
[11:07] <tseliot> bryceh: yes, the change is already in
[11:07] <tseliot> I'll clean up things in git too
[11:08] <bryceh> yep.  $ apt-cache policy libgl1-mesa-dri
[11:08] <bryceh> libgl1-mesa-dri:
[11:08] <bryceh>   Installed: 7.10.3-0ubuntu3
[11:08] <bryceh>   Candidate: 7.10.3-0ubuntu3
[11:08] <bryceh> tseliot, any changes needed for xorg-server?
[11:09] <tseliot> bryceh: no, I don't think so. All we need is to version the breaks in Mesa (I've tested things here for a few days)
[11:39] <tseliot> jcristau: I'm getting Permission denied (publickey) when trying to push my commits. Any ideas?
[11:40] <tseliot> my username is tseliot-guest
[11:40] <jcristau> check that you're using the right key?
[11:40] <tseliot> jcristau: I've certainly not changed my key for a while now
[11:43] <jcristau> when was the last working commit?
[11:43] <tseliot> jcristau: also, if I try to ssh into alioth.debian.org, it says that remote host identification has changed, so I'm wondering if anything changed there
[11:43] <tseliot> let me check
[11:43] <jcristau> yes, something changed there
[11:45] <jcristau> http://lists.debian.org/debian-devel-announce/2011/05/msg00007.html http://lists.debian.org/debian-devel-announce/2011/05/msg00008.html
[11:46] <tseliot> jcristau: it was b28a90c9a78f605d521a9ba1cda42f23ad487e10
[11:46] <jcristau> that's not a date
[11:46] <tseliot> jcristau: sorry, Thu Dec 2 13:34:35 2010 +0100
[11:48] <jcristau> yeah, so long before the move
[11:48] <jcristau> try ssh to vasks.debian.org, see what that tells you
[11:49] <tseliot> jcristau: still Permission denied (publickey)
[11:51] <jcristau> then make sure https://alioth.debian.org/account/editsshkeys.php has the key you're trying to use
[11:51] <jcristau> (and that it's not a dsa key)
[12:06] <tseliot> jcristau: I've tried that (with RSA) but I'm still getting the same error. Shall I wait a few minutes?
[12:06] <tjaalton> tseliot: fix the hostname in .git/config
[12:06] <tjaalton> to git.d.o
[12:08] <tseliot> tjaalton: I'm using<EMAIL_ADDRESS>[12:09] <tjaalton> ok.. maybe plain ssh then?
[12:10] <tjaalton> can't check my config
[12:12] <tseliot> I keep getting the following:
[12:12] <tseliot> Permission denied (publickey).
[12:12] <tseliot> fatal: The remote end hung up unexpectedly
[12:13] <tjaalton> ok, so it's probably not related to the alioth upgrade
[12:14] <tjaalton> at least the way i thought it was :)
[12:31] <tseliot> jcristau: I've tried creating a new ssh key and setting my ssh config file to use that but it doesn't seem to solve the problem
[12:31]  * tseliot is starting to think that debian.org hates him
[12:47] <jcristau> the cron to sync the keys from the db runs at the hour
[13:23] <ScottK> Sarvatt: No more crashes since I installed your PPA package.
[13:29] <tseliot> ok, I'll wait then
[13:29] <tseliot> jcristau, tjaalton: thanks for your help
[13:33] <jcristau> if stuff still doesn't work there's always<EMAIL_ADDRESS>or #alioth on oftc
[13:39] <tseliot> jcristau: it works now, thanks again
[13:40] <jcristau> ah cool.
[17:54] <bjsnider> Sarvatt, the 275 blob is still going to be a big problem because of the supported pciid script being broken right?


[06:44] <ColbyStoker[m]> Question for UbuntuStudio devs, I am installing software that requires actual root access, sudo not working, whats the default protocol for root login on an US installation?
[06:45] <arraybolt3[m]> Colby Stoker: What software are you trying to install? I know how to elevate to root, but it sounds like you might be about to do something in a way that could be done a lot easier.
[06:46] <ColbyStoker[m]> OSSEC
[06:46] <ColbyStoker[m]> I am passing an argument from wget to bash
[06:46] <arraybolt3[m]> (For the record, I'm only technically an Ubuntu Studio dev, I help test it and can do dev work on it, but the main devs are other people.)
[06:47] <ColbyStoker[m]> yeah, It's not too complicated, I am actually wondering for my own purposes.  Its nice to have root sometimes
[06:47] <arraybolt3[m]> Hmm. OK, I don't see that in the Ubuntu repos, so I guess you're on the right track then.
[06:47] <ColbyStoker[m]> I am just a junior dev, maybe not even that
[06:47] <arraybolt3[m]> To elevate to root in Ubuntu (including Ubuntu Studio), run sudo su - in a terminal. That will give you a root shell, be careful.
[06:48] <ColbyStoker[m]> perfecto, thank array, that was a lot quicker and easier than I expected
[06:48] <arraybolt3[m]> Sure thing!
[06:49] <ColbyStoker[m]> also, for the record, I like to break things, but I also like to fix them.  I will try not to break things though
[06:49] <arraybolt3[m]> 👍 You might know about this already, but you can use virtualization software like GNOME Boxes to play with stuff and break it without breaking your whole system.
[06:49] <arraybolt3[m]> (I also am notorious for breaking stuff 🤣)
[06:50] <ColbyStoker[m]> HAHA I have been running Linux since 1996.  When it was everyday something was broken.
[06:50] <ColbyStoker[m]> first install of Slackware 2.0 on a 486, via floppy
[06:50] <arraybolt3[m]> Oh wow. I've not even been alive that long.
[06:51] <ColbyStoker[m]> Fun times, back then
[06:51] <arraybolt3[m]> Oldest system I have around here is a Pentium III, I'm hoping to resurrect it.
[06:52] <ColbyStoker[m]> imagine downloading an installation of Linux over 18 hours with one floppy having a sector of bad data. Then having to start all over.
[06:52] <arraybolt3[m]> Ugh. Hated bad floppy sectors.
[06:53] <arraybolt3[m]> I one time downloaded the whole Studio ISO over a 70 kliobyte-per-second connection. Not fun.
[06:53] <ColbyStoker[m]> yeah, that's close to the speeds, about half to a third of that
[06:53] <ColbyStoker[m]> Thank God for modern technology
[06:54] <arraybolt3[m]> Yours was in the kilobits though, right? Mine was kilobytes. So more like 300 Kbps.
[06:54] <arraybolt3[m]> Anyway, I'm going far off-topic :P
[06:56] <ColbyStoker[m]> Good to know this place is around.  You contribute to UbuntuStudios codebase?
[06:58] <arraybolt3[m]> I have the ability to, I haven't actually done so yet since the project I was working on got stalled and is currently sitting on a different SSD. Most of my contributions are helping test it.
[06:59] <ColbyStoker[m]> Nice, is all the documentation on that listed inside the developer section on the website?
[06:59] <arraybolt3[m]> On elevating to root? Or on how to help contribute?
[07:01] <ColbyStoker[m]> oh contributing
[07:02] <arraybolt3[m]> Probably the best way to get started contributing is to just ask in the Ubuntu Studio Development chat (it's invite-only, Eickmeyer is the flavor lead and can probably let you in). They know where things need help and can help you get started.
[07:04] <ColbyStoker[m]> Good to know, see if they pick up the line
[07:06] <Eickmeyer[m]> I'm  actually in bed winding down for the evening.
[07:06] <arraybolt3[m]> Eickmeyer: I was gonna say, what on earth are you doing awake? :P
[07:06] <Eickmeyer[m]> "Awake" is relative.
[07:07] <arraybolt3[m]> lol well that's true.
[07:07] <ColbyStoker[m]> If you want an email or github I would consider contributing any way that is helpful
[07:07] <Eickmeyer[m]> It's more complicated than that as there's no single codebase.
[07:08] <ColbyStoker[m]> sure, how about an invite to the dev chat
[07:08] <Eickmeyer[m]> Yeah, hang on.
[07:08] <ColbyStoker[m]> perfect, I can read an follow along with the discussions
[07:11] <ColbyStoker[m]> Got it, thanks to you both
 "I have the ability to, I haven't..." <- I really need to find my SATA-to-USB cable so I can get that project back, it was coming along nicely. /me adds that to the list of Things To Do
[09:26] <gordonjcp> b0id[m]: hah, slackware
[09:26] <gordonjcp> b0id[m]: you might be nearly as old as me
[09:27] <gordonjcp> arraybolt3[m]: I know someone who is working on getting FreeBSD 1 working on a 386
 "b0id: you might be nearly as old..." <- Time flies eh


[12:50] <BluesKaj> howdy all
 @RikMills, Rik, the new system monitor is consuming 68% of your CPU.
 @DarinMiller, That was in a VM with not much given to it
 It's an issue with the new sys mon.  It does the same on my bare hw with both neon and 21.04.
 There is KDE bug saying it uses more CPU
 I 'think' the git master built against latest plasma master is better
 I was chalking it up to betaware... not quire ready for prime time.
 It is a pre-release
 They should have labeled it alpha really
[20:45] <santa_> good night everybody
[20:47] <santa_> RikMills: I guess you already got that mail, but they are a couple of things worth patching in knewstuff and plasma-framework
[20:48] <santa_> RikMills: I plan to add the patches in question soon, maybe tonight or tomorrow
[21:26] <RikMills> santa_: one of them is already applied
[21:26] <RikMills> plasma-framework
[22:19] <santa_> RikMills: ok, I will do the knewstuff one then
[22:21] <RikMills> ack
[23:41] <santa_> RikMills: knewstuff with the patch in the _staging branch. build and tested in the staging PPA
[23:41] <santa_> please note that the bug is not 100% reproducible afaics


[17:05] <tomreyn> fwiw i just tried to install xubuntu 21.10 on a virtualbox VM with the minimum system requirements listed at https://xubuntu.org/requirements/ - namely 512 MB RAM. Got an instant kernel panic.
[17:05] <tomreyn> initramfs unpacking failed: write error
[17:06] <Montresor> Yeah, need 700 some, don't remember specifically, since the initramfs is huge and requires more space, this is due to the microcodes.
[17:06] <tomreyn> if i find out what's the minimum value that will let me install without things failing too much, would you update the website?
[17:07] <Montresor> Not sure I can, but ensure the graphics don't take some of the ram too during tests.
[17:07] <tomreyn> they are separate, and VRAM isset to 20 MB
[17:08] <Montresor> IIRC 712 wasn't enough but 756 was fine.
[17:08] <tomreyn> but realistically they actually would decrease overall ram if those would be igpu systems
[17:08] <tomreyn> and most users are not aware
[17:09] <Montresor> But to list on the site, I'd just say 1G really.  I do test Xubuntu Core on Qemu with less, but...
[17:09] <tomreyn> yes 712 also panics
[17:11] <tomreyn> 800 MB gets me to the first installer screen (background image loads, nothing else), then a black screen.
[17:12] <Montresor> Yeah, Xubuntu Desktop has the slideshow which IIRC uses webkit, Core doesn't.  I guess that wouldn't help (though you didn't even get to that point, soo.)
[17:15] <tomreyn> so you're saying 800 MB minimum + VRAM for Xubuntu Core 21.10 amd64, and 1024 MB minimum + VRAM for Xbuntu 21.10 amd64, right?
[17:16] <Montresor> I'd just make it 1024 across.
[17:18] <tomreyn> okay, with 1024 MB i got the first proper installer screen
[17:33] <tomreyn> and the installation succeeded with default options (other than german keyboard layout), too. though during boot, it seems to be stuck on the logo screen.
[17:34] <tomreyn> oh that's actually during shutdown of the installer, not reboot, yet
[17:35] <tomreyn> https://i.imgur.com/lPgb5NP.png
[17:35] <tomreyn> it's stuck there, i've been waiting for 2 minutes.
[17:36] <tomreyn> but this could be due to virtualization
[17:45] <tomreyn> i sent an acpi signal, without notable effect, then pressed ctrl-c, and got repeating squashfs errors for reads on a single block. no visual response to ctrl-alt-del then, so i rebooted. desktop comes up fine and quickly. with just the terminal open, free -h reports: https://i.imgur.com/2sn9rbf.png
[17:45] <tomreyn> so whom should I annoy to update the website?
[18:22] <tomreyn> i retried with uefi, otherwise same settings + specs. this also works out, but the installer also fails to reboot properly.
[18:23] <tomreyn> identical error message after ctrl-c
[18:23] <tomreyn> https://i.imgur.com/iDU2xGw.png
[18:25] <tomreyn> 30 MB more available than with BIOS boot, swap also untouched.
[18:25] <tomreyn> so, as a general sattement, 1 GB RAM + VRAM it is, I'd say, too.


[00:06] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #776: SUCCESS in 6 min 57 sec: http://kci.pangea.pub/job/mgmt_merger/776/
[00:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kajongg build #122: STILL FAILING in 7 min 38 sec: http://kci.pangea.pub/job/yakkety_unstable_kajongg/122/
[00:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio-gdrive build #23: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_kio-gdrive/23/
[00:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kajongg build #74: STILL FAILING in 6 min 42 sec: http://kci.pangea.pub/job/zesty_unstable_kajongg/74/
[00:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kreport build #33: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kreport/33/
[00:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_klinkstatus build #17: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_klinkstatus/17/
[00:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #28: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_kproperty/28/
[00:31] <clivejo> wxl: LP 1635911 was assigned to you, last I heard you were testing it from a PPA, what needs to be done?
[00:32] <clivejo> I uploaded 1.6.2 to zesty
[00:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #124: STILL FAILING in 25 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/124/
[00:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdesdk-kioslaves build #56: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/zesty_unstable_kdesdk-kioslaves/56/
[00:37] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdev-python build #60: FIXED in 30 min: http://kci.pangea.pub/job/xenial_unstable_kdev-python/60/
[00:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_klinkstatus build #14: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_klinkstatus/14/
[00:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #30: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_kdb/30/
[00:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #58: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/58/
[00:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kajongg build #94: STILL FAILING in 12 min: http://kci.pangea.pub/job/xenial_unstable_kajongg/94/
[00:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #56: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/zesty_unstable_kdiagram/56/
[00:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #63: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/zesty_unstable_kopete/63/
[00:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_klinkstatus build #14: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/yakkety_unstable_klinkstatus/14/
[00:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kommander build #17: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/zesty_unstable_kommander/17/
[00:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdiagram build #31: STILL UNSTABLE in 48 min: http://kci.pangea.pub/job/yakkety_unstable_kdiagram/31/
[00:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kproperty build #33: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_kproperty/33/
[00:57] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kio-extras build #68: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_kio-extras/68/
[00:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #278: STILL FAILING in 49 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/278/
[00:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #78: STILL FAILING in 49 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/78/
[01:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_trojita build #37: STILL UNSTABLE in 41 min: http://kci.pangea.pub/job/zesty_unstable_trojita/37/
[01:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_peruse build #53: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/zesty_unstable_peruse/53/
[01:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdb build #27: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/zesty_unstable_kdb/27/
[01:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #70: STILL UNSTABLE in 41 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/70/
[01:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-sdk build #77: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/zesty_unstable_plasma-sdk/77/
[01:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kajongg build #123: STILL FAILING in 6 min 1 sec: http://kci.pangea.pub/job/yakkety_unstable_kajongg/123/
[01:30] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #84: STILL UNSTABLE in 43 min: http://kci.pangea.pub/job/zesty_unstable_marble/84/
[01:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #257: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/257/
[01:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konqueror build #63: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/xenial_unstable_konqueror/63/
[01:30] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #78: STILL UNSTABLE in 53 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/78/
[01:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #303: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/303/
[01:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kajongg build #75: STILL FAILING in 16 min: http://kci.pangea.pub/job/zesty_unstable_kajongg/75/
[01:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kajongg build #95: STILL FAILING in 16 min: http://kci.pangea.pub/job/xenial_unstable_kajongg/95/
[01:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #125: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/125/
[01:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #72: STILL UNSTABLE in 1 hr 6 min: http://kci.pangea.pub/job/zesty_unstable_kstars/72/
[01:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #207: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/207/
[01:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kreport build #34: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kreport/34/
[01:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #152: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/152/
[01:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #211: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/211/
[01:44] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio-gdrive build #24: FIXED in 25 min: http://kci.pangea.pub/job/xenial_unstable_kio-gdrive/24/
[01:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio-extras build #284: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_kio-extras/284/
[01:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #273: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/xenial_unstable_cantor/273/
[01:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #79: STILL FAILING in 38 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/79/
[01:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevelop build #60: FIXED in 38 min: http://kci.pangea.pub/job/zesty_unstable_kdevelop/60/
[01:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kreport build #28: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/zesty_unstable_kreport/28/
[01:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #341: STILL UNSTABLE in 50 min: http://kci.pangea.pub/job/xenial_unstable_kstars/341/
[01:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #181: STILL UNSTABLE in 50 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/181/
[02:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdev-python build #48: STILL FAILING in 4 min 11 sec: http://kci.pangea.pub/job/zesty_unstable_kdev-python/48/
[02:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kexi build #39: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kexi/39/
[02:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #279: STILL FAILING in 56 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/279/
[02:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #95: STILL UNSTABLE in 1 hr 4 min: http://kci.pangea.pub/job/xenial_unstable_marble/95/
[02:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #140: STILL FAILING in 26 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/140/
[02:24] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:24] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdev-python build #49: FIXED in 16 min: http://kci.pangea.pub/job/zesty_unstable_kdev-python/49/
[02:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kexi build #35: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/zesty_unstable_kexi/35/
[02:39] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-runtime build #78: STILL FAILING in 41 min: http://kci.pangea.pub/job/zesty_unstable_kdepim-runtime/78/
[02:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kreport build #31: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kreport/31/
[02:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #194: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/194/
[02:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #65: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/65/
[02:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #39: STILL UNSTABLE in 2 hr 9 min: http://kci.pangea.pub/job/yakkety_unstable_krita/39/
[02:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #133: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/133/
[03:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #41: STILL UNSTABLE in 2 hr 2 min: http://kci.pangea.pub/job/xenial_unstable_krita/41/
[03:09] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-runtime build #79: STILL FAILING in 24 min: http://kci.pangea.pub/job/zesty_unstable_kdepim-runtime/79/
[03:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kexi build #35: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_kexi/35/
[03:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #141: STILL FAILING in 41 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/141/
[03:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-workspace build #105: FAILURE in 39 min: http://kci.pangea.pub/job/zesty_unstable_plasma-workspace/105/
[03:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #66: STILL UNSTABLE in 2 hr 43 min: http://kci.pangea.pub/job/zesty_unstable_krita/66/
[03:21] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_calligra build #51: STILL UNSTABLE in 1 hr 13 min: http://kci.pangea.pub/job/zesty_unstable_calligra/51/
[03:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #120: FAILURE in 25 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/120/
[03:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #66: STILL FAILING in 27 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/66/
[03:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #134: STILL FAILING in 28 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/134/
[03:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #45: STILL UNSTABLE in 1 hr 14 min: http://kci.pangea.pub/job/xenial_unstable_calligra/45/
[03:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-workspace build #106: STILL FAILING in 19 min: http://kci.pangea.pub/job/zesty_unstable_plasma-workspace/106/
[03:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_calligra build #50: STILL UNSTABLE in 1 hr 12 min: http://kci.pangea.pub/job/yakkety_unstable_calligra/50/
[04:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #121: STILL FAILING in 28 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/121/
[04:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #78: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_kitemmodels/78/
[04:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #169: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/169/
[04:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kguiaddons build #164: STILL UNSTABLE in 9 min 12 sec: http://kci.pangea.pub/job/yakkety_unstable_kguiaddons/164/
[04:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdbusaddons build #239: STILL UNSTABLE in 9 min 3 sec: http://kci.pangea.pub/job/yakkety_unstable_kdbusaddons/239/
[04:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdbusaddons build #74: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/zesty_unstable_kdbusaddons/74/
[04:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kguiaddons build #73: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/zesty_unstable_kguiaddons/73/
[04:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwidgetsaddons build #75: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/zesty_unstable_kwidgetsaddons/75/
[04:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwidgetsaddons build #237: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kwidgetsaddons/237/
[05:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdbusaddons build #374: STILL UNSTABLE in 8 min 1 sec: http://kci.pangea.pub/job/xenial_unstable_kdbusaddons/374/
[05:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kguiaddons build #348: STILL UNSTABLE in 8 min 54 sec: http://kci.pangea.pub/job/xenial_unstable_kguiaddons/348/
[05:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwidgetsaddons build #365: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kwidgetsaddons/365/
[08:57] <lordievader> Good morning.
[09:34] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libksieve build #74: FIXED in 14 min: http://kci.pangea.pub/job/zesty_unstable_libksieve/74/
[09:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #122: FIXED in 29 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/122/
[09:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #142: STILL FAILING in 29 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/142/
[09:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-workspace build #107: FIXED in 29 min: http://kci.pangea.pub/job/zesty_unstable_plasma-workspace/107/
[09:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libksieve build #86: FIXED in 20 min: http://kci.pangea.pub/job/yakkety_unstable_libksieve/86/
[09:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-runtime build #80: STILL FAILING in 21 min: http://kci.pangea.pub/job/zesty_unstable_kdepim-runtime/80/
[09:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libksieve build #86: FIXED in 21 min: http://kci.pangea.pub/job/xenial_unstable_libksieve/86/
[09:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #92: STILL FAILING in 18 min: http://kci.pangea.pub/job/zesty_unstable_kmail/92/
[10:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmail build #65: STILL FAILING in 8 min 33 sec: http://kci.pangea.pub/job/yakkety_unstable_kmail/65/
[10:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmail build #70: STILL FAILING in 15 min: http://kci.pangea.pub/job/xenial_unstable_kmail/70/
[10:10] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #93: STILL FAILING in 12 min: http://kci.pangea.pub/job/zesty_unstable_kmail/93/
[10:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #143: STILL FAILING in 26 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/143/
[10:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmail build #66: STILL FAILING in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kmail/66/
[10:24] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-runtime build #81: STILL FAILING in 26 min: http://kci.pangea.pub/job/zesty_unstable_kdepim-runtime/81/
[10:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmail build #71: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_kmail/71/
[10:35] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #94: FIXED in 21 min: http://kci.pangea.pub/job/zesty_unstable_kmail/94/
[10:38] <BluesKaj> 'Morning folks
[10:42] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmail build #67: FIXED in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kmail/67/
[10:47] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmail build #72: FIXED in 21 min: http://kci.pangea.pub/job/xenial_unstable_kmail/72/
[13:19] <clivejo> looking for testers, digikam 5.4 - https://launchpad.net/~clivejo/+archive/ubuntu/digikam/
[13:20] <clivejo> you will need backports enabled
[13:29] <clivejo> !info digikam unstable
[13:33] <KurousagiMK2> clivejo: can not be installed on Zesty, digikam-private-libs : Depends: libmarblewidget-qt5-24 (>= 4:15.12.0) but it is not going to be installed
[13:34] <clivejo> have you marble installed?
[13:35] <clivejo> what happens if you apt install libmarblewidget-qt5-24 ?
[13:36] <clivejo> if you have enabled the staging-kdeapplications PPA you would get those kind of issues
[13:36] <acheronuk> KurousagiMK2: is that with KCI ppa enabled?
[13:36] <clivejo> or KCI
[13:36] <KurousagiMK2> kci yes. Kubuntu Staging KDE Applications have libmarblewidget-qt5-26
[13:37] <clivejo> thats why then
[13:37] <clivejo> that version is build against whats in the archive
[13:37] <clivejo> which is 15.12
[13:37] <clivejo> disable KCI and staging PPA's
[13:38] <clivejo> so it "cant see the newer versions"
[13:38] <acheronuk> also on zesty deps against libqt5core5a (>= 5.7.0) for me, so I guess that ppa built against proposed
[13:38] <clivejo> yes, was built against proposed :(
[13:39] <acheronuk> trying to get Qt 5.7.1 out of proposed today!
[13:39] <clivejo> any luck?
[13:39] <clivejo> whats holding it back now?
[13:39] <acheronuk> but it's slow going. even with a lot having been force-badtes
[13:40] <acheronuk> new PyQt5 needing QtWebEngine to publish I think
[13:41] <clivejo> oooo
[13:41] <clivejo> qtspeech-opensource-src
[13:41] <acheronuk> yeah, I know
[13:41] <clivejo> that could clear up a lot of our lintian moaning
[13:41] <acheronuk> added a note on trello that maybe we can add that as a build dep to some things now
[13:43] <clivejo> would you be up for organising a ninja meetup on BBB?
[13:44] <acheronuk> oooh. qtwebengine published for amd64 :)
[13:44] <acheronuk> clivejo: taht would be fine with me
[13:45]  * clivejo thinks we should maybe try to have a weekly get together
[13:45] <acheronuk> I've been pottering along with stuff and making progress, but some coordination and planning would be a good idea
[13:45] <acheronuk> agreed
[13:45] <acheronuk> especially now the clock is ticking towards stuff like feature freezes etc
[13:46] <clivejo> I think wxl might be feeling a bit isolated with being in a different time zone
[13:47] <clivejo> also think my bouncer is dropping stuff
[13:47] <acheronuk> yeah. that time diff is unfortunate. for Darrin as well
[13:54] <BluesKaj> clivejo, using konversation?
[13:55] <clivejo> BluesKaj: ??
[13:58] <BluesKaj> clivejo, not using a bouncer, but konversation connection is restricted to the irc.freenode.net server here, anything else has "unknown errors"
[14:00] <clivejo> ok
[14:00] <BluesKaj> isuppose that was off topic for your discussion , but it's a problem that needs addressing
[14:01] <BluesKaj> and it's aproblem for both YY and ZZ
[14:03] <clivejo> you would have to take that upstream - https://konversation.kde.org
[14:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio-extras build #285: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kio-extras/285/
[14:59] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kio-extras build #69: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/zesty_unstable_kio-extras/69/
[14:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio-extras build #140: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/yakkety_unstable_kio-extras/140/
[15:10] -kubuntu-ci:#kubuntu-devel- Project merger_konqueror build #68: FAILURE in 4 sec: http://kci.pangea.pub/job/merger_konqueror/68/
[15:12] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[15:12] -kubuntu-ci:#kubuntu-devel- Project merger_konqueror build #69: FIXED in 9.8 sec: http://kci.pangea.pub/job/merger_konqueror/69/
[15:22] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[15:22] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kio-extras build #70: FIXED in 14 min: http://kci.pangea.pub/job/zesty_unstable_kio-extras/70/
[15:28] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[15:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio-extras build #141: FIXED in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kio-extras/141/
[15:35] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[15:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio-extras build #286: FIXED in 27 min: http://kci.pangea.pub/job/xenial_unstable_kio-extras/286/
[15:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_konqueror build #48: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/yakkety_unstable_konqueror/48/
[15:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konqueror build #64: STILL UNSTABLE in 43 min: http://kci.pangea.pub/job/xenial_unstable_konqueror/64/
[15:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_konqueror build #67: STILL UNSTABLE in 43 min: http://kci.pangea.pub/job/zesty_unstable_konqueror/67/
[16:49] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[16:49] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[16:49] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_konqueror build #68: FIXED in 54 min: http://kci.pangea.pub/job/zesty_unstable_konqueror/68/
[16:49] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[16:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_konqueror build #49: FIXED in 1 hr 5 min: http://kci.pangea.pub/job/yakkety_unstable_konqueror/49/
[16:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konqueror build #65: FIXED in 54 min: http://kci.pangea.pub/job/xenial_unstable_konqueror/65/
[17:09] <mamarley> Plasma 5.9 beta has been released but soee is nowhere to be found!
[17:14] <BluesKaj> mamarley, staging?
[17:14] <mamarley> BluesKaj: No, not anywhere in Kubuntu.  Just soee normally announces these things, but he isn't here.
[17:17] <BluesKaj>  released to where then?
[17:18] <mamarley> The KDE developers put out a beta release.  It has not been packaged (and quite likely will not, until the stable comes out)
[17:18] <acheronuk> https://www.kde.org/announcements/plasma-5.8.95.php
[17:20] <clivejo> Its looking good :)
[17:20] <acheronuk> yes. basically what has been building in KCI up until today.
[17:21] <clivejo> how is Qt going?
[17:22] <clivejo> or coming
[17:23] <Mirv> Valid Candidate, was pending on pyqt5 successful builds and NEW acceptance, done 10 mins ago
[17:24] <acheronuk> clivejo: new PyQt5 has built and been approved by archive admins, so it watching the excuses and update_output pages for a but again
[17:24] <acheronuk> *for a bit
[17:24] <Mirv> next up staring of http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt which probably 5 people on Earth can decipher (basically looking at the most suitable "trying easy from autohinter" section and looking at the package list it lists per arch that has problem, which may or may not easily give out what could be next problem
[17:24] <clivejo> :)
[17:24] <Mirv> I'm out now anyway for today
[17:24] <clivejo> Mirv: thanks for all your work :)
[17:25] <clivejo> acheronuk: you too :)
[17:25] <Mirv> yeah thanks acheronuk!
[17:25]  * acheronuk thanks everyone!
[17:32] <wxl> clivejo: re: konversation, i've had one person test the ppa. admittedly, it was a success, but 2-3 would be nice. i did beg people on irc and send an email on the subject as well. nothing's been happening since.
[17:32] <clivejo> :(
[17:32] <Sho_> what's up with konversation?
[17:32] <wxl> Sho_: i got a bugfix release for yakkety i want to sru in a ppa. want to test?
[17:33] <Sho_> what's the fix?
[17:33] <Sho_> (upstream maintainer)
[17:33] <wxl> oh well it's YOUR fix then XD
[17:33] <Sho_> ah
[17:33] <clivejo> the version in yakkety is crashing, and there is a fix for it
[17:33] <Sho_> good thrn
[17:33] <Sho_> ;)
[17:33] <clivejo> but its needs to follow procedure etc
[17:34] <clivejo> Sho_: did you see BluesKaj complaint earlier?
[17:34] <Sho_> I've been hearing him talk about connection problems
[17:34] <clivejo> something about not being able to connect via chat.freenode
[17:34] <Sho_> but I can't reproduce them and we haven't gotten any reports upstream
[17:34] <clivejo> oh ok, might be a local issue then
[17:35] <Sho_> if it's an ssl connection it could be some weird cert-openssl-qt mess issue or something
[17:35]  * acheronuk looks for wxl's email
[17:36] <clivejo> Sho_: will there be a release of konversation any time soon?
[17:37] <Sho_> clivejo: we really do need to do at least a beta, there's a ton of work in git
[17:38] <clivejo> I see a few changes between released and master
[17:38] <clivejo> we are building master on KCI
[17:38] <clivejo> but would need a stable release to get it into zesty
[17:38] <Sho_> it's held back by me finding the time to review the work, update the changelogs, figure out if it's in releasable condition, and then rolling the actual beta
[17:39] <BluesKaj> Sho_, I tried some of the servers like card.freenode with plain nickserv and no SSL on ports 6667-7000 with the same resulting "unknown error'
[17:39] <Sho_> i work on kde fulltime but konvi is spare time stuff, so it tends to lose out :/
[17:39] <Sho_> BluesKaj: the "unknown error" message is coming out of Qt code, so something on the QtNetwork level is going wrong
[17:39] <Sho_> it's an error string supplied by QTcpSocket
[17:40] <Sho_> and of course, very useless
[17:40] <clivejo> no problem, I thought would been nice to get current work into zesty
[17:40] <Sho_> clivejo: what's the timeline for zesty?
[17:41] <BluesKaj> Sho_, anyway good old irc.freenode.net still connects
[17:42] <clivejo> Sho_: https://wiki.ubuntu.com/ZestyZapus/ReleaseSchedule
[17:43] <ejat> http://paste.ubuntu.com/23787858/
[17:43] <ejat> can i proceed?
[17:43] <Sho_> clivejo: i can probably do a beta before feb 16th, but final not sure
[17:44] <clivejo> make sure you give us a shout when you do
[17:45] <mamarley> Just out of curiosity, which Plasma version are you shooting for in Zesty?
[17:45] <ejat> mamarley: mean?
[17:46] <mamarley> ejat: I'm wondering what Plasma version they are wanting/expecting to have in Kubuntu 17.04.
[17:48] <ejat> mamarley: owh
[17:48] <ejat> so i should wait for it before do the upgrade ?
[17:49] <clivejo> mamarley: what ever version we can get in before FF
[17:49] <clivejo> there are a couple of road blockers at the moment
[17:49] <clivejo> but Qt is moving along nicely
[17:49] <acheronuk> ejat: that is expected to happen, so should be fine
[17:50] <ejat> from v5 to v6 right ?
[17:51] <acheronuk> ejat: yes
[17:52] <ejat> thanks
[17:52] <acheronuk> mamarley: 5.9.4 is released 2 days before final freeze, so I guess aim for that or maybe 5.9.3
[17:52] <mamarley> Sounds good, thanks! :)
[17:53] <acheronuk> assuming the few issues we have to get 5.9.x done resolve
[17:53] <clivejo> acheronuk: any update on gpgme?
[17:54] <soee> o/
[17:54] <clivejo> hi soee
[17:54] <acheronuk> clivejo: nope. got tied up with Qt today, and basically depends now on cjwatson or other LP people
[17:55] <acheronuk> clivejo: if that LP builder issue does not get resolved, I may push strongly for the imperfect solution of disabling the 2 small sections of the python tests that cause the LP builds to hang
[17:57] <clivejo> seems like a reasonable solution
[17:57] <acheronuk> clivejo: logic being that its a LP specific bug, and in fact this builds and passes it;s tests just fine anywhere else. in fact, there is nothing to say that these tests would not pass if they actually would not hang
[17:57] <acheronuk> as in a launchpad-sbuild chroot that mimicks then, it also passsed
[17:57] <clivejo> g2g for a bit, tea time
[17:58] <acheronuk> ok
[18:02] <wxl> BluesKaj: on the private ops channel, i did see some discussion about some freenode servers maybe not working? i didn't really pay attention, so can't tell you more but maybe ask on #freenode?
[18:04] <BluesKaj> wxi yes, thanks for the suggestion, I did consider it earlier , but got a bit side tracked by other things
[18:04] <wxl> uh ok maybe i didn't send the email ugh :(
[18:05] <wxl> oh there it is
[18:06] <wxl> what a dumb subject
[18:06] <wxl> https://lists.ubuntu.com/archives/kubuntu-devel/2016-December/011062.html
[18:06] <wxl> ^^ acheronuk
[18:08] <acheronuk> wxl: found it, tried you ppa package on Yakkety, and seems to works ok
[18:08] <acheronuk> only a brief test though. have commented on the bug
[18:13] <wxl> acheronukL well, i'll let clivejo decide if that's sufficient to move forward with an sru
[19:27] <marco-parillo> I restored the entry for Kubuntu in: https://community.kde.org/Plasma/Live_Images If anybody wants a longer notice, feel free to edit it directly, or try my bouncer nick (mparillo) in a couple of hours.
 we're havng a party in BBB Room 1
 if anybody wants to join us
[21:26] <valorie> mparillo: thanks!
[22:43] <tsdgeos> clivejo: https://www.kde.org/info/security/advisory-20170112-1.txt is it now more clear what it is about?
[23:01] <tsdgeos> valorie: did you get the security advisory email?
[23:02] <valorie> looking
[23:02] <valorie> was just outside raking!
[23:02] <valorie> gotta use the sun while I have it
[23:02] <valorie> yes
[23:03] <valorie> and now marked as Important
[23:37] <mparillo> Thank you Rik for quietly saving me from a cut and paste fail.


[03:32] <JonHanDin> Hello Desktopers, Just a quick question... I like my bash scripts (they just make life easier);  one i cant get my head around... I'm forever using Files to explore some sftp and samba share through the UI...  Many thanks
[03:32] <JonHanDin> apologies, i reaslise this is for #ubuntu
[05:24] <didrocks> good morning
[05:32] <duflu> Morning didrocks
[05:37] <didrocks> hey duflu
[07:06] <oSoMoN> good morning desktoppers
[07:11] <didrocks> salut oSoMoN
[07:17] <oSoMoN> salut didrocks
[07:25] <marcustomlinson> morning oSoMoN and didrocks
[07:26] <didrocks> hey marcustomlinson
[07:27] <oSoMoN> morning marcustomlinson
[07:27] <ricotz> good morning all :)
[07:27] <marcustomlinson> hey ricotz
[07:28] <ricotz> marcustomlinson, hi
[07:29] <oSoMoN> good morning ricotz
[07:30] <marcustomlinson> ricotz: will test libreoffice 6.2.5 in eoan soon, should push to archive later this morning
[07:32] <ricotz> marcustomlinson, thanks, I pick it up for the backports then
[07:56] <willcooke> morning all
[07:59] <Trevinho> morning!
[07:59] <didrocks> hey willcooke, Trevinho
[08:03] <Laney> hi there
[08:03] <didrocks> hey Laney
[08:05] <Laney> hey didrocks, happy friday :>
[08:05] <Laney> you good?
[08:05] <didrocks> I'm ok, you? :)
[08:05] <didrocks> and happy friday too
[08:05] <Laney> yeah not bad
[08:06] <Laney> went out for dosa last night
[08:06] <Laney> yum yum
[08:08] <didrocks> nice
[08:39] <marcustomlinson> morning willcooke Trevinho and Laney
[08:40] <Laney> hey marcustomlinson
[08:40] <Laney> what's the news
[08:41] <marcustomlinson> newly received or noteworthy information, especially about recent events.
[08:41] <willcooke> lol
[08:41] <marcustomlinson> :) all good Laney, yourself?
[08:42] <Laney> alexa tomlinson
[08:42] <Laney> tell me a rude joke
[08:43] <Laney> (all good in this hood)
[08:43] <marcustomlinson> Sandpaper Sally
[08:59] <marcustomlinson> jamesh knows not to ask me for rude jokes
[09:00] <jamesh> Surely moving to Ireland has tempered your jokes a bit though?
[09:00] <marcustomlinson> Ireland?????
[09:00] <jamesh> Scotland
[09:00] <jamesh> same thing
[09:01] <jamesh> somewhere up north
[09:01] <marcustomlinson> Yer bum's oot the windae
[09:01] <willcooke> XD
[09:01] <jamesh> they all sound the same
[09:01] <marcustomlinson> What time is it there in New Zealand anyway?
[09:03] <willcooke> ha
[09:03] <jamesh> NZ and Australian accents are completely different
[09:03] <jamesh> :-)
[09:05] <marcustomlinson> jamesh: https://youtu.be/f2gii2nenUg
[09:07] <jamesh> marcustomlinson: see? totally different.
[11:00] <Laney> didrocks: can you add me to the ubuntu team on github pls? (assuming you are an admin there)
[11:04] <didrocks> 2nd requests in a day, that's trendy it seems :)
[11:04] <didrocks> hum, toomanyLaneys on github
[11:05] <Laney> iainlane
[11:05] <Laney> not sure I'll use it actually
[11:05] <Laney> I was going to start a repo for 'useful scripts' with one I just wrote
[11:05] <Laney> but I should probably not be lazy and contribute it to ubuntu-dev-tools instead
[11:05] <Laney> /o\
[11:05] <didrocks> Laney: invited
[11:05] <Laney> merci
[11:05] <didrocks> de rien :)
[11:12] <Laney> https://github.com/ubuntu/ubuntu-scripts
[11:19] <Trevinho> the project should be /ubuntu/THE-scripts :P
[11:19] <Laney> ZE
[11:19] <Trevinho> better indeed
[11:20] <didrocks> fortunately, you can rename projects :)
[11:20] <Laney> bet Trevinho has some scripts lying around
[11:20] <Trevinho> mh, yeah... but recently I'm just writing all oneline in bash :P
[11:21] <Trevinho> so mostly lost in my bash_history
[11:21] <Laney> 😱
[11:21] <Laney> I did that make-sru-tasks thing in lp-shell about 5 times
[11:21] <Laney> figured the 6th makes it worth writing a script
[11:22] <Nafallo> Trevinho: Telehouse East?
[11:22] <Trevinho> haha
[11:22] <Trevinho> Nafallo: ehm?
[11:23] <Nafallo> it's a data center, called THE :-P
[11:27] <Laney> :>
[11:29] <Nafallo> https://goo.gl/maps/RFfgyPWqVuJk4NDJ8
[12:21] <Trevinho> ahhh :)
[12:56] <Laney> didrocks: any chance I can be an owner so that I can build a snap of this or is that reserved?
[12:57] <didrocks> Laney: do you need to be owner to build snaps?
[12:57] <Laney> via BSI, yeah
[12:57] <Laney> that's what Colin just told me in #launchpad anyway
[12:57] <didrocks> waow, surprising
[12:57] <didrocks> but sure, let me change this
[12:57] <Laney> thx
[12:58] <didrocks> Laney: done
[13:00] <Laney> nice one 👏
[17:02] <willcooke> happy weekend all, night