[01:25] <shadeslayer> sgclark: kauth is broken
[01:26] <sgclark> ok?
[01:27] <sgclark> I am currently beating my head on networkmanager-qt. I will get back to you as soon as I find my way out of this madness. Thank you.
[01:29] <shadeslayer> sgclark: yeah, the cmake file is now installed in both -dev and -bin-dev
[01:29] <shadeslayer> jfyi
[01:30] <sgclark> shadeslayer: well. Which one does it need to be in? cause I cant seem to get it right
[01:33] <shadeslayer> sgclark: debian says : debian/libkf5auth-dev.install:usr/lib/*/cmake/KF5Auth/KF5AuthMacros.cmake
[01:34] <sgclark> shadeslayer: that is bizarre. ok thanks.
[01:35] <shadeslayer> oh?
[01:35] <sgclark> bizarre in how kubuntu had it other way around, and it looked like a maxy commit. /shrug
[01:35] <shadeslayer> usr/lib/*/cmake/KF5Auth/* < is too wide anyway
[01:36] <shadeslayer> s/wide/greedy/
[01:37] <shadeslayer> sgclark: http://paste.ubuntu.com/13634466/ < the patch I have in my email
[01:38] <shadeslayer> anyway, will leave you to it
[01:39] <sgclark> shadeslayer: thank you
[01:39] <sgclark> helping, not abandoning me lol
[09:04] <sick_rimmit> Morning..
[09:04] <sick_rimmit> Sorry about having to postpone Podcast yesterday
[09:05] <valorie> are you rescheduling, sick_rimmit?
[10:22] <sick_rimmit> Hi valorie
[10:22] <sick_rimmit> Yes, I have rescheduled for this evening, both events
[10:22] <sick_rimmit> Kubuntu Core Team
[10:23] <sick_rimmit> and Kubuntu Podcast
[11:14] <shadeslayer> sgclark: heh xD
[11:14] <shadeslayer> sgclark: you're most welcome
[11:14] <clivejo> mmmmm marshmallow
[12:13] <BluesKaj> Hiyas all
[13:28] <sgclark> shadeslayer: you about?
[14:28] <Mirv> we've potential kwin kwin_testScreenEdges problem with Qt 5.5.1 and marble failure parsing Tour.kml. could anyone look if you believe those two problems can be ignored or not regarding release pocket migration? the tour.kml parsing has failed also with Qt 5.4.2, but not passing at all with Qt 5.5.1 (other 25 .kml file parsings in TestGeoDataWriter are fine)
[14:28] <Mirv> logs<EMAIL_ADDRESS>+<EMAIL_ADDRESS>[14:31] <Mirv> sorry, correction, marble is a real failure too
[15:27] <Mirv> kwin is probably this https://github.com/KDE/kwin/commit/eda4f6103707bc425dec884c3fe4dac1077b21a7 that could be cherry-picked - but it's no-xrandr only so not a big deal
[15:28] <mgraesslin> Mirv: no-xrandr means in this case a Xvfb setup
[15:30] <mgraesslin> Mirv: so if the test fails for you in CI tests, that's the change you want
[15:31] <Mirv> mgraesslin: it does, so I'm now more worried about the marble issue where "4.2" in https://github.com/KDE/marble/blob/master/tests/data/Tour.kml becomes 4.2000000000000002
[15:31] <Mirv> kwin issue is probably exactly that
[15:31] <mgraesslin> concerning marble I have no idea - I only do kwin ;-)
[15:32] <Mirv> yes I know, thanks for the kwin fix :)
[15:32] <mgraesslin> was painful
[15:34] <shadeslayer> sgclark: ssup
[15:34] <shadeslayer> I'm sorry, I missed the ping
[15:37] <sgclark> shadeslayer: ahh no worries. was seeking help with failed tests in karchive because it cannot find the test data. But if your busy I can continue fighting with google for the answer.
[15:38] <shadeslayer> I saw that too on DCI
[15:38] <shadeslayer> or was it ark
[15:38] <shadeslayer> ark I think
[15:39] <sgclark> files exist in source.. I can only think maybe it is being searched for in a different directory off path? hard to say without a workspace to look in.
[15:39] <shadeslayer> got a error?
[15:40] <sgclark> shadeslayer: https://launchpadlibrarian.net/228266063/buildlog_ubuntu-xenial-amd64.karchive_5.16.0%2Bgit20151203.0514%2B16.04-0_BUILDING.txt.gz
[15:41] <shadeslayer> sgclark: why not just dpkg-buildpackage locally?
[15:41] <sgclark> I looked at karchive code.. seems right, but I am not a c++ programmer.. :(
[15:41] <shadeslayer> or in a container
[15:41] <sgclark> that was my next step atually. have some RL to attend to for a bit though. thanks.
[15:41] <shadeslayer> make[2]: Entering directory '/«BUILDDIR»/karchive-5.16.0+git20151203.0514+16.04/obj-x86_64-linux-gnu'
[15:41] <shadeslayer> gives you a hint
[15:42] <sgclark> ahh so it is a path issue
[15:42] <sgclark> so source patched or is this something I fix in packaging?
[15:42] <yofel> well, going by that the path would be correct..
[15:42] <shadeslayer> ^^
[15:43] <sgclark> pft what?
[15:43] <shadeslayer> sgclark: http://dci.pangea.pub/job/unstable_unstable_frameworks_karchive_bin_amd64/6/console
[15:43] <shadeslayer> seems to build just fine on DCI
[15:43] <shadeslayer> tests pass
[15:43] <sgclark> congratulations?
[15:44] <sgclark> it does not for kci
[15:44] <sgclark> the test cannot find the test data
[15:44] <shadeslayer> right, so try out a build locally
[15:44] <shadeslayer> see if it works
[15:44] <shadeslayer> if it does, then poke someone in #launchpad I guess, and/or add debugging info to the debian/rules
[15:44] <sgclark> ok
[15:45] <BluesKaj> Is plasma 5.5 in a ppa yet ?
[15:45] <Mirv> regarding marble, upstream has this https://github.com/KDE/marble/commit/05df36b674db4b150835ceecc53021d61b51f27e.patch - but I'm not sure if it's a workaround or something acceptable
[15:45] <shadeslayer> would recommend adding debugging info like overriding auto_test and echo'ing the path to stdout
[15:45] <sgclark> BluesKaj: no. and I have no ETA
[15:46] <sgclark> shadeslayer: thank you for the hints. Will try them.
[15:46] <shadeslayer> cool
[15:46] <BluesKaj> ok thanks sgclark ...was curious about the hype I just read :-)
[15:51] <Mirv> ok I will include the upstream fixes for both shortly
[16:07] <BluesKaj> Hype: http://www.tuxmachines.org/node/82554
[16:10] <BluesKaj> still takes 2mins to get to the login page from grub on Xenial here
[16:11] <sgclark> heh takes me 10
[16:12] <BluesKaj> you must be joking
[16:15] <sgclark> lol nope. Could be my 10 chroots on bootup though haha. And my laptop is getting quite old and I put it through hell with packaging.
[16:18]  * BluesKaj nods
[16:22] <lordievader> sgclark: Perhaps 'systemd-analyze blame' can tell you who is responsible for the delay.
[16:22] <lordievader> systemd-analyze is a rather nice utility :)
[16:26] <clivejo> sgclark:  cant find a file ../../autotests/kcompressiondevicetest.cpp
[16:26] <sgclark> lordievader: neat thanks
[16:27] <sgclark> clivejo: yes that is karchive failure. Do you have ideas? Of just telling me?
[16:28] <yofel> systemd-analyze is nice. Now we just need to enable user-session journals and it might even help with our login delay debugging
[16:31] <lordievader> Does (K)Ubuntu use the systemd pm-suspend/hibernate already?
[16:35] <yofel> IIRC yes. Although there was some confusing fallback code and a story with required pm-suspend hooks so it might not. Can't quite remember (I looked at that like 2 years ago when the new upower came out)
[16:36] <lordievader> Hmm, since it was rather easy to implement a user hook into the systemd suspend thing.
[16:36] <lordievader> More automation is lovely :D
[16:52] <clivejo> stupid internet
[16:55] <clivejo> sgclark: karchive seems to be building fine in wily with the same packaging, could it be an issue with QT in xenial?
[16:57] <yofel> the failing builtlog said Qt5.4, so unlikely
[16:57] <yofel> *buildlog
[16:57] <sgclark> yeah I dont think so. unfortunately I am in a meeting and will not get back to it for an hour or so.
[16:57] <yofel> meh, now I'm curious. Let me throw that thing in pbuilder
[16:58] <clivejo> yofel: just done it
[16:58] <clivejo> builds ok :/
[16:58] <sgclark> yofel: ty
[16:59] <yofel> clivejo: with or without CI repo?
[17:00] <clivejo> where does qtbase get built?
[17:00] <yofel> come again?
[17:00] <clivejo> qtbase5-dev
[17:01] <yofel> if you mean what source it's from, apt-cache showsrc tells you that
[17:50] <clivejo> yofel: Is qtbase-opensource-src (5.5.1+dfsg-1ubuntu1~wily1~test1) available for xenial?
[18:41] <yofel> clivejo: in proposed yes. (rmadison tells you that)
[18:42] <clivejo> but its also in the CI, could this be why karchive is building on wily but failing on xenial?
[18:43] <ovidiu-florin> Meeting is about to start, humans and bots ready? :D
[18:43] <ovidiu-florin> https://plus.google.com/u/0/events/c1gaj5gljd5e9m3qb5q05qr6b80?authkey=CJCt_dqO7udV
[18:43] <yofel> possibly
[18:44]  * yofel will join around 8
[18:44] <clivejo> yofel: Im currently building it on my xenial install, will install it and try
[18:54] <clivejo> how do I listen in?
[18:56] <yofel> you join the hangout
[18:57] <clivejo> I dont see a hangout
[18:57] <clivejo> just an animated gif
[18:57] <clivejo> of people having a party
[18:57] <ovidiu-florin> Has someone started the hangout?
[18:57] <ovidiu-florin> can someone link me please?
[18:58] <clivejo> 18:47 Lets get ready to RUMBLE
[18:58] <clivejo> yofel: is that you in the red shirt?
[18:58] <yofel> no, I'm not in
[19:01] <ovidiu-florin> shall I start it?
[19:02] <ovidiu-florin> Ok, I'll start it, since there is no answer
[19:02] <ovidiu-florin> join here: https://plus.google.com/hangouts/_/2mf6364wp26pqticvqqgfrfzzma?authuser=0&hl=en
[19:05] <ovidiu-florin> Am I in the wrong place, or is actually no one there?
[19:05] <yofel> I got interrupted and am on the phone right now. I'll join in a bit
[19:05] <clivejo> I cant get on - ERR_SSL_PROTOCOL_ERROR
[19:09] <BluesKaj> clivejo, probly needs the googletalk plugin
[19:10] <BluesKaj> clivejo, http://www.google.com/tools/dlpage/hangout/download.html?hl=en
[19:10] <clivejo> that was in chrome
[19:10] <clivejo> in firefox it says Im the only one here
[19:10] <yofel> still needs a plugin
[19:10] <BluesKaj> works in firefox here'
[19:11] <ovidiu-florin> ignore my previous link
[19:11] <sick_rimmit> https://plus.google.com/u/0/b/112102796730023795852/events/c1gaj5gljd5e9m3qb5q05qr6b80
[19:11] <sick_rimmit> This is the events.
[19:11] <BluesKaj> I have no camera on this pc, so i just made a quick visit
[19:14] <BluesKaj> no one needs to see my old mug, so I use a pic of me and my beautiful daughter to distract
[19:20] <yofel> Ok, let me try again, but even quassel says ~3s lag, so my network seems to have issues today :(
[19:22] <yofel> ok, progress. I can somewhat understand what people say, but the quality is horrible :/
[19:25] <yofel> and I got kicked out again, dangit
[19:25] <mhall119> yofel: so the options are:
[19:26] <mhall119> A) Spin up a VPS or cloud instance, install Jenkins on it and run the CI stuff on there and request reimbursement from the community donations fund
[19:27] <mhall119> B) Canonical's internal CI team has a "Jenkins as a service" setup that we might be able to give you access to, which lets you spin up vanilla Jenkins instances on demand, but you don't get shell access on them, only the Jenkins interface
[19:28] <mhall119> if (A) I'd also recommend talking to the Juju guys about using charms to deploy it, so you can scale up as needed or move to other providers
[19:31] <yofel> mhall119: I would really love B), but as sitter did say something about shell access, we would first have to see if we could get rid of that requirement.
[19:31] <yofel> sitter: on that point, how do I actually reach clemens? I haven't seen him around on IRC whenever I'm online... can I have his mail address?
[19:37] <mhall119> yofel: brent clements?
[19:39] <yofel> mhall119: No, Clemens Tönnies from blue systems
[19:40] <mhall119> ah, ok
[19:57] <sgclark> yofel: fairly certain we would need B. Am I right that we would not be able to use our tooling on A mhall119?
[19:58] <sgclark> yofel: mhall119totally backwards
[19:58] <sgclark> flip my question we have tooling, we would need A I think
[19:58] <sgclark> aka we need more than a point and click jenkins install
[19:59] <sgclark> I am looking at the juju bits for my kde jenkins
[20:08] <Rick_Timmis> http://youtu.be/eZH6b6hJi2o
[20:08] <ovidiu-florin> Kubuntu Podcast Link ^
[20:09] <clivejo> thanks
[20:43] <valorie> phooey, missed it altogether
[20:43] <valorie> there was no link on telegram
[20:44] <clivejo> join in valorie
[20:44] <clivejo> its interesting!
[20:44] <clivejo> bugs have always confused me
[20:46] <valorie> oh, still going on?
[20:47] <valorie> no, it says I'm the first one here
[20:54] <clivejo> LOL
[20:54] <valorie> actually, apport has been crashing for awhile
[20:54] <valorie> and I've reported a bug about it
[20:54] <clivejo> Rick crashed the bug reporter tool!
[20:54] <valorie> sometimes `ubuntu-bug whatever` works though, in the cli
[20:56] <clivejo> valorie: some of these bugs are years old, are they still relevent?
[20:57] <valorie> well, we need a working apport
[20:57] <valorie> it's hard enough to report bugs, we don't want it even harder
[21:03] <mhall119> sgclark: it would depend on what your tooling is
[21:03] <sgclark> mhall119: a pile of ruby scripts and they are run in docker containers.
[21:04] <mhall119> ah, then B may not be an option for you
[21:04] <sgclark> I am fairly certain B will not work for us. I could be wrong..
[21:04] <sgclark> and I would hate to lose all of the great work put into our existing CI.
[21:15]  * sgclark out for a bit
[21:34] <valorie> two questions: what about the core-devel meeting?
[21:35] <valorie> two: when you guys were discussing the spinning up the VMs, do you recall that wikitolearn has such a functionality?
[21:35] <valorie> available online, even when you don't have a linux computer to use
[21:35] <valorie> also, feedback about referring to gender: just use names
[21:36] <valorie> please don't assume "people" are "guys"
[21:36]  * valorie is upgrading the xenial box
[21:37] <valorie> ovidiu-florin: ^^^ Rick_Timmis
[21:38] <valorie> great podcast; sorry I wasn't able to join
[21:38] <valorie> but I did listen live for about half
[21:39] <Rick_Timmis> Guys in US probably means Men, but in UK Guys means the group aka Folks
[21:40] <ovidiu-florin> the core-devel meeting happened
[21:40] <ovidiu-florin> kind of
[21:40] <clivejo> LOL
[21:40] <Rick_Timmis> We did hold Kubuntu Core Team meeting, and I scheduled a new one for Jan 6, pre show
[21:40] <Rick_Timmis> On G+
[21:40] <Rick_Timmis> I check invite for valorie
[21:40] <ovidiu-florin> valorie: VMs, do you reffer to the Kubuntu devel VM I talked about?
[21:41] <clivejo> poor yofel was having network issues
[21:41] <Rick_Timmis> valorie: Yes, I checked I have sent you invite for Core Team on G+
[21:42] <Rick_Timmis> valorie: It all got a bit disorganised, as we had to postpone, and then aaron didn't arrive tonight..
[22:07] <valorie> ok
[22:08] <valorie> Rick_Timmis: the reason I ask not to use "guys" is because it isn't inclusive
[22:08] <valorie> just like "mankind" sort of leaves half of us out
[22:09] <valorie> it isn't offensive to me, or bugging me, but best practice: be inclusive
[22:09] <valorie> ovidiu-florin: yes, the devel VM
[22:09] <valorie> the wikitolearn folks have those all set up on their server
[22:10] <valorie> Rick_Timmis: I was too late, and I didn't look at G+ on my phone, unfortunately
[22:10] <valorie> I was looking at Telegram, and got no link there
[22:10] <valorie> anyway, haven't gotten to the part in the podcast where you talk about GCi tasks
[22:10] <valorie> was that covered?
[22:11] <valorie> contest opens on the 7ty
[22:11] <valorie> 7th
[22:12] <valorie> KDE has under 50 tasks, when we should have 100 more
[22:16] <sgclark> the "guys" arguement is the most annoying thing ever. I always called everyone "guys" even my girlfriends. Until I got repremanded at at job of course.  Surely there are more improtant things to worry about.
[22:17] <valorie> I'm not worried about it
[22:18] <valorie> I want us to be inclusive
[22:18] <valorie> I've always used it too, and I'm trying to change that a bit
[22:19] <mhall119> sgclark: I think the gender-neutrality of "guys" is a regional thing
[22:19] <mhall119> personally I favor the always-gender-neutral southern y'all :)
[22:19] <sgclark> lol
[22:19] <valorie> me too
[22:19] <valorie> :-)
[22:20] <valorie> although when I use it, people expect me to have a drawl
[22:20] <sgclark> you humans over there
[22:20] <mhall119> valorie: if you use it, the drawl will come
[22:21] <valorie> I got a bit of one when I spent some time in Colorado as a teen
[22:21] <valorie> I didn't even notice that there was an accent, but people remarked on it when I returned home
[22:25] <keithzg> "guys" is definitely gender-neutral here in Western Canada. Although our accent is pretty much just Broadcast North American English for anyone under about 45 and/or not living in a small town, heh.
[22:28] <valorie> I'm not advocating political correctness: I just want us to be as inclusive as possible
[22:32] <clivejo> so bug https://bugs.launchpad.net/debian/+bug/1157723 is it not out of date?
[22:32] <keithzg> There's always "their" and "they" and such for the sake of gender-agnostic plural.
[22:32] <sgclark> kfilebox?
[22:32] <clivejo> hardly a new bug after 2.5 years?
[22:32] <sgclark> not sure I have heard of that lol
[22:33] <clivejo> !info kfilebox
[22:33] <sgclark> lol
[22:33] <clivejo> neither has wily!
[22:33] <clivejo> seems to be KDE4
[22:33] <sgclark> anyway, I have never felt "unincluded" in our community. If anything I am "too" included hahah
[22:34] <clivejo> Kfilebox is a KDE dropbox frontend. Previously known as kdropbox.
[22:34] <clivejo> dont dropbox have their own client?
[22:35] <keithzg> http://kdropbox.deuteros.es/ shows last post in January 2011, and http://sourceforge.net/p/kdropbox/svn/HEAD/tree/ similarly shows no activity since then.
[22:35] <clivejo> I think that bug should be closed :/
[22:35] <sgclark> yes, if there is no kf5 port than it is useless
[22:36] <sgclark> looks unmaintained
[22:36] <keithzg> It does look like there's some new-ish maintenance, but not actually KF5 porting? https://github.com/gtgt/kfilebox/
[22:36] <valorie> right, I feel and felt welcome too, but I'm a white Murrican woman
[22:36] <keithzg> (Got that from the link from AUR, apparently some folks are still packaging it for Arch at least: https://aur.archlinux.org/packages/kfilebox/
[22:36] <valorie> who grew up with mostly boys
[22:37] <sgclark> oh hmm, well maybe if someone is interested, perhaps upstream could be poked to port it.
[22:38] <Mamarok> Rick_Timmis: about your comment in that bug report for Amarok: you will have to fix and maintain that yourself, I have no devs for that. also comparing v 2.5 with 2.8 (which is already outdated btw, try 2.8-git) is really a very long stretch, thousands of lines of code i between...
[22:41] <keithzg> sgclark: that github page does claim there's a Debian maintainer, but unless I'm doing something wrong it sure doesn't seem to be in any official Debian repos: https://packages.debian.org/search?suite=all&searchon=names&keywords=kfilebox
[22:42] <sgclark> very weird. search seems right.
[22:43] <clivejo> !cutepaste
[22:43] <clivejo> !info cutepaste
[22:46] <clivejo> that could be handy
[22:46] <clivejo> wonder does it work with the new KDE paste inferface
[22:49] <valorie> I miss the pastebin widget
[22:49] <valorie> still
[22:49] <clivejo> how do I close this bug - https://bugs.launchpad.net/debian/+bug/1255895
[22:49] <valorie> supposedly you can do it from clipboard now, but I don't see how
[22:50] <clivejo> its been packaged and latest version is in the archive
[22:50] <valorie> maybe link to the package in the archive?
[22:50] <valorie> somebody forgot to close it
[22:50] <clivejo> it tis linked
[22:53] <valorie> bugsquad, where are ya?
[22:53] <clivejo> its a debian bug?
[22:53] <clivejo> have debian a group on LP?
[22:53] <valorie> I'm trying to google to get my Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01) to use 5g on our new router
[22:54] <valorie> not having much luck
[22:54] <valorie> clivejo: weird
[22:55] <valorie> jr set it to fixed-released though
[22:55] <valorie> which is basically closed
[22:56] <clivejo> !info kdev-qmljs
[22:58] <clivejo> !info kdevelop
[22:59] <clivejo> lastest is 4.7.2
[22:59] <sgclark> I have 4.7.2 in staging-misc
[22:59] <sgclark> but I was trying to package the py3 and failed miserably and then got distracted
[22:59] <clivejo> ready for the archive?
[22:59] <sgclark> well
[22:59] <sgclark> if we delete the py3 yes.
[23:00] <clivejo> there is a beta release of KDevelop 5.0.0
[23:00] <clivejo> interesting
[23:01] <yofel> clivejo: yes, there is a debian component on LP for bug links and code imports. And as you can see, debian bug 725403 is still open, so that bugs is fine as it is
[23:02] <clivejo> yofel: how come it still appears under Kubuntu Bugs?
[23:02] <yofel> what filter are you using?
[23:02] <clivejo> does it not get removed from the group its fixed under?
[23:03] <yofel> no, that's what the "Fix Released" status is for, which hides a bug in the default filters
[23:04] <yofel> we only care about bugs under ubuntu/ and kubuntu-ppa/
[23:04] <clivejo> dont have a filter applied
[23:04] <clivejo> https://bugs.launchpad.net/~kubuntu-bugs/
[23:04] <yofel> please don't touch the bug tasks for any other LP projects without the consent of the project maintainer
[23:06] <yofel> clivejo: https://bugs.launchpad.net/ubuntu?field.subscriber=kubuntu-bugs is what you want
[23:10] <yofel> actually, let me put that link on qa
[23:17] <yofel> for some reason that bug list feels too short though....
[23:21] <yofel> clivejo: meh, wrong filter: https://bugs.launchpad.net/ubuntu?field.structural_subscriber=kubuntu-bugs
[23:21] <yofel> 5k bugs sounds about right
[23:21] <sgclark> lol https://bugs.launchpad.net/ubuntu/+source/kdewebdev-kde3/+bug/27025
[23:21] <sgclark> kde3...
[23:21] <sgclark> surely we dont support that anymore
[23:21] <sgclark> quanta is dead upstream to bot
[23:22] <sgclark> err boot
[23:22] <DalekSec> sgclark: Congrats on CC, btw.
[23:22] <sgclark> thanks DalekSec :)
[23:22] <yofel> uh, that's something for EOL alright..
[23:23] <valorie> the quanta guy briefly spoke of reviving the project, then disappeared again 5 minutes later
[23:23] <valorie> I guess the current recommendation is just to use kdevelop instead
[23:23] <sgclark> was a nice tool back in the day
[23:23] <yofel> lp 16575 is the oldest still open bug that we're monitoring ^^
[23:23] <valorie> yes, when I was thinking of learning webdev, I installed it
[23:23] <valorie> but sort of never went further
[23:24] <sgclark> I have used it for web dev!
[23:24] <sgclark> but not for some time now.
[23:24] <sgclark> of course I do not use kde3 either lol
[23:25] <sgclark> woow 2005
[23:25] <sgclark> 10 years and still open? that cant be good
[23:25] <yofel> you *could* ask the trinity folks if they care :P
[23:25] <yofel> well, martin marked an 11 years or so kwin bug report as fixed recently :P
[23:25] <sgclark> lol true
[23:25] <yofel> but yeah, for us that's useless
[23:26] <clivejo> do many people still use prior Kubuntu to 14.04?
[23:26] <sgclark> Munich is on older version
[23:26] <valorie> I began with kub. very long ago
[23:26] <sgclark> but heavily patched
[23:26] <valorie> perhaps 2003?
[23:26] <yofel> great, even the debian and kde bug reports of that are still open...
[23:27] <valorie> whenever Mandrake decided to change to mandriva or whatever
[23:27] <yofel> Munich certainly, right. There's also other people that just don't bother to upgrade
[23:27] <sgclark> I started with RedHat 1999, quickly moved to Suse, used that for 10 years... and then distro hopped till ya'll found me.
[23:28] <sgclark> there I avoided "guys" yaya me.
[23:28] <valorie> lol
[23:28] <sgclark> lol
[23:28] <yofel> but bugs for packages that don't exist any supported release anymore are as dead as they can be
[23:28] <valorie> yes
[23:28] <yofel> !botsnack
[23:28] <yofel> XD
[23:28] <valorie> we can't support stuff forevar
[23:28] <clivejo> can those bugs not be closed?
[23:29] <sgclark> what do we put? wont fix?
[23:29] <yofel> I would say won't fix / Invalid with a slightly modified stock EOL response
[23:30] <clivejo> Not supported, obsolete, dead as a dodo?
[23:30] <sgclark> ok
[23:30] <yofel> saying that the package is not part of a supported release anymore (instead of saying that the release went EOL)
[23:30] <yofel> although, that would be true as well
[23:30] <sgclark> I have copy pasted the release EOL message to the couple I did close.
[23:31] <clivejo> yofel: BTW you can blame Rick_Timmis for all this interest in bugs
[23:31] <yofel> I guess Expired would also be a valid status, but you need a script for that
[23:31] <yofel> clivejo: I kind of guessed that already :P
[23:31] <sgclark> Oh, do not see expired on my list of options
[23:31] <sgclark> perhaps not elite enough
[23:31] <yofel> right, it's a LP-internal status that bugs get if they were "incomplete" for more than... 90? days
[23:32] <sgclark> bug triage is an area we are weak in, so yay Rick_Timmis
[23:32] <yofel> you can set it through the API though
[23:32] <sgclark> ah
[23:32] <clivejo> I cant work out how LP bugs work
[23:32] <clivejo> its a dark kind of magic
[23:32] <yofel> wait, I did write something for that...
[23:33] <yofel> http://bazaar.launchpad.net/~yofel/+junk/lp-scripts/view/head:/lp-set-expired.py
[23:33] <yofel> (C) 2010-2011 Philip Muskovac, time files..
[23:33] <yofel> *flies
[23:33] <sgclark> I suppose I outta get back to my current set of bugs called debain merges, ugh.
[23:34] <sgclark> I cannot spell debian correctly today to save my life.
[23:34] <clivejo> Installation of 9.10 - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/482166
[23:34] <clivejo> confirmed and high importance
[23:34] <clivejo> :/
[23:35] <clivejo> mustnt have been that important
[23:35] <sgclark> mm not us anyway
[23:35] <valorie> well, stuff gets fixed and the devel doesn't know about /forgets about the bug report
[23:35] <valorie> life happens
[23:35] <sgclark> true that.
[23:36] <yofel> that's not quite what "Importance" says here.. more like "amount of affected people"
[23:36] <yofel> https://wiki.ubuntu.com/Bugs/Importance
[23:36] <clivejo> Im joking yofel
[23:37] <yofel> heh. Well, it's an ubiquity bug report
[23:37] <clivejo> a lot of them are
[23:37] <clivejo> using that link you posted
[23:40] <yofel> hm, the filter is too wide now it seems :/
[23:40] <yofel> it *should* only list ubiquity reports tagged kubuntu, but doesn't seem to do that
[23:42] <yofel> anyway, off to bed
[23:42] <yofel> gn
[23:43] <valorie> sweet dreams, yofel
[23:44] <valorie> it would be great if some folks could step up and mentor kids triaging bugs or packaging
[23:44] <valorie> soon
[23:44] <valorie> or make videos
[23:44] <valorie> etc.
[23:46] <sgclark> Wish I could, If I step up for anymore I only have sleep to give up time wise. Though I guess sleep is over rated.
[23:47] <valorie> no, your health is more important than anything else
[23:47] <valorie> if we have to drop out of the contest because people can't do it, then that's what we have to do
[23:47] <valorie> since it seems that my father is forgetting/has forgotten how to swallow
[23:48] <valorie> I'm unsure what my time will look like in the near future
[23:48] <sgclark> :(
[23:48] <valorie> and my health comes before FOSS
[23:48] <valorie> no matter how much I love y'all
[23:48] <sgclark> my aunt is not doing so well. just put her in hospice
[23:48] <valorie> I'll find out more tonight
[23:48] <valorie> and that may be the next step for him
[23:49] <valorie> fortunately, they do hospice at that facility, so he won't have to be moved
[23:49] <sgclark> nice
[23:49] <sgclark> my aunt is in Vegas with no family.. :( my mom had to go back to work
[23:49] <sgclark> in Phoenix
[23:50] <sgclark> I may be taking a road trip soon
[23:51] <sgclark> then there is holidays..
[23:51] <valorie> getting old ain't for the faint of heart
[23:51]  * sgclark runs of screaming
[23:51] <valorie> lol
[23:51] <valorie> my husband says he'll put up lights when I finish the shopping
[23:51]  * valorie runs off screaming too
[23:51] <sgclark> lol
[23:52] <sgclark> speaking of husbands, I need to make mine coffee and lunch. bbl