[00:01] <superm1> me
[00:15] <Daviey> superm1: you are of no use to me :)
[00:15] <supermario> me 3
[00:15] <Daviey> heh
[00:37] <BullCreek> There seems to be a problem with the lucid beta1 alternate cd where partman can't handle partitions > 2TB anymore.  I'm using the alternate cd in lieu of the mythbuntu beta1 cd due of course to the fact that your desktop build doesn't include support for mdadm.  I started a thread for it in the forum and filed a bug on launchpad (probably should have been against partman instead of the kernel as I don't think it is a kernel problem after lookin
[00:37] <BullCreek> http://ubuntuforums.org/showthread.php?t=1436325
[00:37] <BullCreek> I know quite a few mythbuntu folks use mdadm so was thinking it should probably be addressed before lucid goes gold if possible.
[00:37] <Zinn> [ubuntuforums.org] problem with large partition and 10.04BETA - Ubuntu Forums
[00:41] <BullCreek> FWIW, it would be great if you could somehow hack your live cd to include mdadm - maybe not a full blown ui for configuring it like the alternate cd has, but at least to where it could recognize pre-existing arrays and include the option of installing on them - particularly since grub2 can now boot from a raid5 or raid6 md device.
[00:42] <BullCreek> If one of you guys is savvy in the the machinations of how the partman stuff works and could give me some pointers I might even have some cycles to work on it.
[00:44] <superm1> BullCreek, i think the intention is to eventually be able to support mdadm in the live installer
[00:44] <superm1> BullCreek, you should test with the most recent alternate daily image though to see if it's been fixed since beta
[00:44] <superm1> if it isn't, then please file a bug
[00:45] <Daviey> superm1: yeah, it's been a wish list for 3 years IIRC :)
[00:45] <BullCreek> i tried yesterdays daily build and it had problems and todays wasn't out yet when I checked this morning.
[00:45] <superm1> it had other problems?
[00:46] <BullCreek> yes, the cdrom device was not found and the six sata drives on my motherboard were also not found
[00:46] <BullCreek> I will try todays if it is out there now
[00:49] <BullCreek> looks like the 3/28 builds must have not worked for some reason as there are no isos in the folder like for the 3/27 builds - maybe they don't do them on Sunday or something
[00:50] <BullCreek> http://cdimage.ubuntu.com/daily/20100328/ is the right place to be looking right?
[00:50] <Zinn> [cdimage.ubuntu.com] Ubuntu 10.04 LTS (Lucid Lynx) Daily Build
[00:51] <superm1> they do them every day
[00:51] <superm1> but it looks like they failed for today
[00:51] <superm1> oh i heard about the bug you had from yesterdays
[00:51] <superm1> there is something wrong with the updated kernel
[00:52] <superm1> BullCreek, have you tried just apt-get installing mdadm before running ubiquity?
[00:52] <superm1> for live disks that is
[00:52] <superm1> i thought the partition handler didn't freak out entirely if you made the arrays outside of it and wanted to use them
[00:53] <superm1> in which case we could always just include it in our pool for people like you until it's got proper support to make the arrays
[01:15] <BullCreek> i tried apt-getting mdadm back in the day on the livecd and it wouldn't pick up the array but that was way back in hardy days or even before if I recall - so it might be worth a shot to try it again (thanks for the suggestion).  I agree that that would be a sufficient fix in that it is really easier to configure/build/manage the array on the command line than using the gui anyway.
[01:22] <superm1> i remember at the last UDS that was an item of discussion and someone raised that it might do that today
[01:44] <BullCreek> I apt-getted mdadm - did an "mdadm --assemble /dev/md0" and appear to be off the races - ubiquity correctly puts a gpt partition on the array, and had no complaints about its size.  Hopefully it will work - should know soon.  Thanks for the help!
[01:45] <BullCreek> When they have a working daily build of the alternate cd again I will try it and if it is still broken I will file a bug against partman unless you have a better suggestion. I will also outline this fix in the bug.
[02:06] <superm1> BullCreek, sounds great thanks.
[02:50] <dewman> so i got a new card today (well used) a pctv hdpci. I am still having the same issues as before when scanning channels. i dont get all the channels and some of the channels have music on them rather then tv. could that indicate that the channels are encrypted?
[02:55] <dewman> since this card has two tuners in it, i need to configure both tuners dont i?
[03:16] <matmatmat> my channel scan (which is m3u parsing) doesnt do anything
[03:16] <matmatmat> earlier it gave me an error in the console at least when the file formatted improperly
[03:17] <matmatmat> now that ive found the right format, it just sits at 0% and says tuning
[03:44] <ball> I think I just found a way to justify the cost of a Mythbuntu box.
[03:45] <styelz> tivo?
[03:46] <ball> styelz: No, but we're supposed to pay the cable TV company something like US$ 16/month for an abyssmal DVR
[03:47] <ball> ...perhaps it's more than that, I forget.  If I build a Mythbuntu DVR that works, eventually it will pay for itself.
[03:47] <ball> ...hopefully.
[03:47] <ball> ...and will be less sucky.
[03:58] <dewman> and your wife/gf/parter will be happy
[03:58] <dewman> or husband
[03:58] <ball> dewman: She's really not happy with this DVR.
[03:59] <dewman> lol...mine isnt happy with me right now. upgraded to cable and it hasnt worked for a month....lol
[04:00] <dewman> my fault on the not working.... I only configured the digital side of the capture card and not the analog side....
[04:00] <dewman> couldnt figure out why i was only getting 20 channels instead of 90
[04:01] <ball> I raided savings to get Cable television installed.
[04:02] <ball> :-/
[04:02] <dewman> well i am going to raid the savings to get raid... =P
[04:02] <ball> RAID-1?
[04:04] <dewman> not sure yet...I have a dl580 sitting idle....so i need to figure out what I am going to do with that, it already has a fiber card in it....
[04:04] <ball> FDDI?
[04:04] <ball> ...or Ethernet?
[04:06] <dewman> for a san...
[04:09]  * ball blinks
[04:09] <ball> Fibrechannel?
[04:11] <dewman> yep.. thats it...
[04:12] <ball> Just because you have FC, doesn't mean you have to use it.
[04:13] <ball> If it makes sense in your application, that's fair enough.
[04:14] <dewman> it was a good buy on the box....of course, the power bill will probably kill me..
[04:15] <ball> Does MythTV benefit greatly from a quad core processor, especially if I buy a dual-tuner card?
[04:29] <mrand> ball: as long as they aren't frame grabbers, tuners don't chew up cpu.
[04:32] <mrand> video decoding can chew up some cpu if you don't have video decoding offload (like Nvidia VDPAU).  For standard def, VDPAU isn't really needed, but if you're buying a video card anyway, might as well buy one that can do it, even if you don't move to HD until later.
[05:27] <ball> mrand: any particular nVidia chip to look for?
[05:27] <rhpot1991> ball: depends on your price point and needs
[05:28] <mrand> http://www.mythtv.org/wiki/NVidia_Cards
[05:28] <Zinn> [www.mythtv.org] NVidia Cards - MythTV
[05:28] <rhpot1991> there are some nice 9500/9600 silent cards
[05:28] <mrand> that list looks old
[05:28] <rhpot1991> and then there are things like the ion boxes that also work very well
[05:28] <rhpot1991> !frontend
[05:28] <Zinn> Ion Boxes make a great frontend.  http://www.baablogic.net/drupal/node/2
[05:28] <mrand> http://www.mythtv.org/wiki/VDPAU
[05:28] <rhpot1991> mrand: very :)
[05:28] <Zinn> [www.mythtv.org] VDPAU - MythTV
[05:28] <mrand> That list looks new
[05:29] <rhpot1991> GT220 is prob a good card to get now, not sure if anyone ever came out with a silent cell version
[05:29]  * rhpot1991 is all about the silent
[05:31] <mrand> I have decent hearing, but I swear I really have to load my machine down with all sorts of flash sites playing on a background website in order to be able to hear my combined FE+BE with 2x750 GB drives that sit 5' to the right of my TV.  Hell, even when I'm sitting right in front of it, I barely hear it.
[05:31] <Zinn> mrand: Please watch your language.
[05:33] <ball> rhpot1991: I think even the GeForce 210 has a fan now.
[05:33] <ball> ...sadly.
[05:35] <rhpot1991> I spent more money than I should have on a 1tb silcent cell 9600
[05:35] <rhpot1991> was the only card I could get to fit in my case though, so it was a good investment
[05:39] <ball> I'm going to have to build a whole new machine.
[05:42] <mrand> ball: it can be cheap or expensive - all depends on what you want to do.  I went kinda middle of the road, but overall I'm not a fan of overspending on computer stuff because tech prices come down so quickly.
[05:48] <rhpot1991> ball: do you already have anything mythtv in place?
[05:48] <ball> mrand: I'm not in a position to overspend.  What's the bare minimum?
[05:48] <ball> rhpot1991: No.
[05:49] <rhpot1991> I'd say you want to build a nice dual or quad core machine, with a nice big hard drive
[05:49] <rhpot1991> look for a nice board with VDPAU capable video, or get a separate card for this
[05:49] <ball> 4 Gbytes RAM sufficient?
[05:49] <mrand> quad is overkill.  I have a cheap dual-core E2200 (2.2 GHz) that keeps up with everything I throw at it.
[05:50] <mrand> 2 GB is enough RAM.
[05:50] <rhpot1991> ya I'm on a dual core 5000+
[05:50] <rhpot1991> pleanty fine
[05:51] <rhpot1991> and 2gb of ram on one, 4gb on another (it was on sale)
[05:51] <rhpot1991> might want to break 2gb if you do onboard video, since you will want to devote 512-1024 of that to video
[05:54] <ball> Hmm... okay
[05:57] <mrand> I guess it depends on what else you plan on running on the system.  If it is *only* Myth BE+FE, then I think that 2 GB is enough, even with video memory.  If you're like me and run a zillion other apps on that same machine (including this irc session, along with NX that I'm connected to it with), then going above 2 GB could help slightly.
[06:02] <ball> Is VDPAU a binary thing, or open source?
[06:02] <mrand> VDPAU is binary.  But until Intel manages to get their stuff straight, or AMD finally spits out something usable, it's the best thing going.
[06:06] <rhpot1991> supposidly ATI has the same now, but its not in debian or ubuntu, and doesn't work with mythtv yet
[06:11] <ball> Hmm...
[06:40] <ball> Presumably VDPAU contains things that are missing from Xvideo
[19:10] <zyberzero> Hi! Today I've got an ION based HTPC  (Intel Atom + Nvidia 9400M). It works fine, but here's the catch: I've got a Full-HD-projector (thru HDMI), a regular monitor (VGA) but I also want to have my old thick TV as well - which uses S-video. What's the most simple way to connect the old TV? I can live with only one output/time, but I want to have the offloading of h264 files.
[19:12] <rhpot1991> zyberzero: that might be tough getting it hooked up to the old tv, IIRC there was a thread on the mailing list with people trying to do the same you might want to check that
[19:13] <zyberzero> rhpot1991: okay, thanks. Can you remember any keywords for me to search for?
[19:17] <mrand> zyberzero: if all else fails, there are VGA -> composite "scan converters."  I get some color banding on mine, but it's functional.
[19:17] <mrand> I bought mine on ebay for $20 as I recall.
[19:17] <rhpot1991> zyberzero: not really, I just searched quick here and couldn't find it
[19:18] <mrand> Some may have less banding - maybe I should have spent more.
[19:18] <rhpot1991> mrand: just put it towards a fancy new tv instead :)
[19:18] <zyberzero> mrand: yes, I used to have one of those in early -00, I may have that somewhere in my "good-to-keep"-boxes.
[19:18] <zyberzero> rhpot1991: okay, thanks for your help! :)
[19:20] <zyberzero> Btw, have anybody heard that myth hangs up the whole computer while watching recorded tv?
[19:21] <mrand> rhpot1991: heh.  Course, the TV I want probably doesn't come with VGA input, so I'll still need to buy a video card with HDMI (or else swap motherboards with my wife - she has an Intel G35 with buildin HDMI).  All this means that I should have just bought a video card to begin with rather than the stupid scan converter.
[19:21] <mrand> zyberzero: it is borderline impossible for it to hang the whole computer... have you tried ssh'ing in from another machine?
[19:21] <mrand> Or telnet.
[19:22] <zyberzero> It hangs. I can't SSH, the display on the front stops at the time when it hangs etc.
[19:22] <rhpot1991> zyberzero: when does this happen, watching video, in the menu?
[19:22] <zyberzero> watching video
[19:22] <zyberzero> never ever
[19:22] <rhpot1991> you running VDPAU?
[19:22] <mrand> can't ssh?  Wow.
[19:23] <zyberzero> Yes, VDPAU is activated
[19:23] <mrand> zyberzero: you running auto-builds?
[19:23] <zyberzero> mrand: I'm running the packages from ubuntu.
[19:23] <rhpot1991> upgrading to audobuilds may help
[19:24] <rhpot1991> you should use QT painter to avoid a potential memory leak issue
[19:24] <rhpot1991> and there are some tweaks to xorg that may help you as well
[19:24] <zyberzero> Ok! I think I've actually changed it to OpenGL as I thought it would be smoother.
[19:25] <rhpot1991> http://mythbuntu.pastebin.com/Fmu8cy4j
[19:25] <rhpot1991> there is my xorg.conf
[19:25] <rhpot1991> points of interest, you want UseEvents off  (I commented mine out, feel free to delete)
[19:26] <rhpot1991> Enabling tripple buffer and disabing composite may help with tearing but shouldn't really affect your crashing issue
[19:26] <rhpot1991> I'd venture you would be best served upgrading to the latest nvidia drivers from our autobuilds
[19:27] <zyberzero> Okay, I'll try that!
[19:27] <zyberzero> Thanks one more time for your help!
[19:27] <rhpot1991> you will have to dist-upgrade when installing, it will remove the old nvidia and put the new ones in
[19:28] <rhpot1991> no problem, good luck
[21:15] <camelreef> good evening from Scotland
[21:15] <camelreef> just a question
[21:16] <camelreef> is there any know transiant issue with the packages in Lucid at this time ?
[21:16] <camelreef> I've just lost all my tuners, inputs and other storage groups info on a reboot
[21:16] <camelreef> the DB appears fine, but the BE or mythtv-setup appear lost
[21:17] <camelreef> mythtv-setup shows close to nothing
[21:17] <camelreef> I'm a bit stressed
[21:18] <camelreef> the last DB backup I have is from Saturday, from .22, before the upgrade
[21:18] <camelreef> I could backup the current DB and restore the pre-.23 and see what it does
[21:19] <camelreef> but if the pb is non-DB related, I might as well save the time
[21:19] <mrand> camelreef: there are no known problems.  Do you have any idea what happened?  Did you update software?
[21:20] <mrand> Have you checked over any logs?
[21:21] <rhpot1991> camelreef: try to repair the db?
[21:21] <rhpot1991> I've seen issues where a crash happened and data seemed lost but after db repairs all was good
[21:22] <camelreef> well, I had done normal lucid upgrades
[21:22] <camelreef> I do not remember if there was any BE packages in that
[21:23] <camelreef> I rebooted the system at noon
[21:24] <camelreef> I shut it down this evening
[21:24] <camelreef> added a disk
[21:24] <camelreef> turned it back on
[21:24] <camelreef> did not check anything
[21:24] <camelreef> formatted the disk
[21:24] <camelreef> mounted it
[21:25] <camelreef> then did a massive and long cp from one disk to another.
[21:25] <camelreef> that created big I/O wait
[21:25] <camelreef> as expected
[21:26] <camelreef> I went into mythtv-setup as I wanted to add some directories to storage groups
[21:26] <camelreef> and I notices the loss of the storage groups
[21:26] <camelreef> and saw the loss of cards, inputs, etc...
[21:26] <camelreef> the weird thing is that when I look at the DB, all the info is there
[21:27] <rhpot1991> did it ever work after upgrading to lucid?
[21:27] <camelreef> capturecards, cardinput, channel, etc...
[21:27] <camelreef> mysqlcheck said all was OK
[21:28] <camelreef> and yes, it worked flowlessly from Saturday evening (lucid+.23 upgrade) to this evening
[21:30] <superm1> camelreef, what's your build number and are you on autobuilds?
[21:30] <superm1> i'm wondering if that new patch for the group magic didn't work right on autobuilds last night
[21:31] <camelreef> I'm on pure lucid
[21:31] <superm1> okay that can't be it then, nvm
[21:31] <camelreef> + medibuntu, but that should make no difference
[21:31] <mrand> so you're saying the contents of the database appear to be there and correct. Is the backend running?  does it show anything interesting in its log about missing tuners, etc?  What happens when you fire up a frontend?
[21:32] <camelreef> ok, one answer at a time :o)
[21:32] <camelreef> if I fire up a front end I cannot watch Live TV
[21:32] <camelreef> I can watch a recordin
[21:32] <camelreef> but that's the only storage group lest in mythtv-setup
[21:33] <camelreef> let me check the rest of the functionality
[21:33] <camelreef> mythvideo  shows content
[21:34] <camelreef> and it can play files
[21:34] <camelreef> said files are in one storage group normally
[21:34] <camelreef> that storage group is not seen in mythtv-setup anymore
[21:35] <camelreef> but all the onfo is still in the storagegroup table
[21:35] <mrand> backend log complain that you don't have any tuners defined now?
[21:35] <camelreef> backen is obviously running
[21:36] <camelreef> let me look at the logs
[21:37] <camelreef> backend logs show no complains during the lunch time reboot so far
[21:39] <camelreef> hmmm, a backen start when nothing should have happened i mid afternoon
[21:40] <camelreef> wow!
[21:40] <camelreef> tons of SQL errors!
[21:41] <camelreef> let me look further
[21:41] <camelreef> trying to correlate timing sith syslog events
[21:42] <camelreef> those errors happened during shutdown
[21:43] <camelreef> correlating with sudo logs
[21:44] <mrand> so the database maybe got corrupted and didn't get shut down, or had problems shutting down, perhaps?
[21:44] <camelreef> let me see
[21:45] <camelreef> poweroff issued at 18:10:14
[21:45] <camelreef> first SQL error message at 18:10:16.067
[21:47] <camelreef> nothing in syslog about MySQL shuting down after the issue of poweroff
[21:47] <camelreef> no real info in syslog at all
[21:48] <camelreef> 18:10:27.907 backen restarts
[21:49] <camelreef> 18:10:27.929 Unable to connect to database!
[21:49] <camelreef> tries multiple times to connect until machine is off
[21:49] <mrand> Is that maybe somewhat expected?   I would have hoped that the backend would down first before sql, but maybe sql was shut down first and backend was still trying to talk?
[21:50] <camelreef> so we have the sutdown scenario/timing
[21:51] <mrand> camelreef: I certainly don't know for certain... just asking if that is maybe a possibility.
[21:51] <camelreef> I just have binary logs for mysql
[21:51] <camelreef> mrand, it looks like ot
[21:52] <camelreef> it
[21:52] <camelreef> so, let's look at the SQL error message befor complete sutdown
[21:53] <camelreef> 2010-03-29 18:10:16.067 Error preparing query: SELECT chanid, useonairguide FROM channel, dtv_multiplex WHERE serviceid        = :SERVICEID   AND       networkid        = :NETWORKID   AND       transportid      = :TRANSPORTID AND       channel.mplexid  = dtv_multiplex.mplexid AND channel.sourceid = :SOURCEID
[21:53] <camelreef> 2010-03-29 18:10:16.068 Driver error was [2/2006]:
[21:53] <camelreef> QMYSQL3: Unable to prepare statement
[21:53] <camelreef> Database error was:
[21:53] <camelreef> MySQL server has gone away
[21:53] <camelreef> 2010-03-29 18:10:20.803 DB Error (Looking up chanID):
[21:53] <camelreef> Query was:
[21:53] <camelreef> SELECT chanid, useonairguide FROM channel, dtv_multiplex WHERE serviceid        = :SERVICEID   AND       networkid        = :NETWORKID   AND       transportid      = :TRANSPORTID AND       channel.mplexid  = dtv_multiplex.mplexid AND channel.sourceid = :SOURCEID
[21:53] <camelreef> Bindings were:
[21:53] <camelreef> :NETWORKID=9018, :SERVICEID=16288, :SOURCEID=1, :TRANSPORTID=12291
[21:53] <camelreef> Driver error was [2/2006]:
[21:53] <camelreef> QMYSQL: Unable to execute query
[21:53] <mrand> !pastebin
[21:53] <Zinn> when pasting more than 5 lines of data please use http://mythbuntu.pastebin.com so you don't flood the channel.  Then please post the link in the channel.
[21:53] <camelreef> Database error was:
[21:53] <camelreef> MySQL server has gone away
[21:53] <camelreef> mrand is right
[21:53] <camelreef> MySQL gone before backend
[21:54] <camelreef> oops,, sorry
[21:55] <camelreef> all SQL are just queries for data, not modifications
[21:56] <camelreef> ok, let's look at the startup
[21:56] <camelreef> 18:33:36 syslog resumes
[21:57] <camelreef> 18:34:00.932 backend restarts
[21:57] <camelreef> let's look at syslog in-between
[21:58] <camelreef> 18:33:53 mysql starts
[21:59] <camelreef> 18:33:57 favia /etc/mysql/debian-start[1851]: Triggering myisam-recover for all MyISAM tables
[22:03] <camelreef> last entry is usual for mysql starts
[22:03] <camelreef> nothing else in syslog
[22:03] <camelreef> backend logs now
[22:04] <camelreef> 18:34:04.101 Connected to database 'mythconverg' at host: localhost
[22:05] <rhpot1991> camelreef: might be easier if you pastebin the entire logs, or run mythbuntu-log-generator
[22:05] <camelreef> 18:34:04.546 Current MythTV Schema Version (DBSchemaVer): 1254
[22:05] <camelreef> I will post all
[22:05] <camelreef> but I want to do my digging too
[22:06] <camelreef> first sign that something is wrong: 18:34:05.588 DiSEqCDevTree, Warning: No device tree for cardid 24
[22:06] <camelreef> and then stuff about DTD mux and chans
[22:08] <camelreef> oh well
[22:08] <camelreef> so something got killed during poweroff
[22:09] <camelreef> running log-generator
[22:09] <camelreef> what package is it in?
[22:10] <camelreef> not in a package, apparently
[22:18] <camelreef> ok, posted the logs on my web site
[22:19] <camelreef> http://www.youplala.net/~will/htpc/20100329/
[22:19] <Zinn> [www.youplala.net] Index of /~will/htpc/20100329
[22:19] <camelreef> remeber, poweroff issued at 18:10
[22:20] <camelreef> rhpot1991, logs are posted
[22:26] <mrand> what you described certainly seems to be reflected in the logs.
[22:26] <camelreef> the only thng we can get from the logs is indeed the MySQL shutdown before the backend
[22:27] <camelreef> or died somehow
[22:27] <camelreef> there isn't anything else to get from that
[22:27] <camelreef> frontend logs show absolutely nothing
[22:27] <camelreef> messages same thing
[22:29] <camelreef> sooooo......
[22:29] <mrand> Yeah, I wouldn't expect it to.  The likelihood  of mysql dying on its own right then seem pretty small to me... more likely that the shutdown terminated the process.  Safest thing to do for now (until this can be sorted out) is to shut down mythbackend first, then shutdown the rest of the machine.   I'd try repairing your database, and if that doesn't work, restore.
[22:29] <camelreef> the database never showed any error on mysqlcheck
[22:29] <camelreef> that is also weird
[22:30] <camelreef> sooo.....
[22:30] <camelreef> I will take a dump of the current broken (?) db
[22:30] <camelreef> restore my .22 DB
[22:30] <camelreef> start the backend
[22:31] <camelreef> start mythtv-setup and go through the DB upgrade phase
[22:31] <mrand> yes, or mythtv-setup.  I think either one will upgrade the database.
[22:31] <camelreef> yes, probably mythtv-setup first
[22:31] <mrand> don't need to start backend before firing off mythtv-setup... it'll just shut it down.
[22:31] <camelreef> then the backend
[22:31] <camelreef> then the frontend
[22:31] <mrand> yep
[22:32] <camelreef> then hunt orphan recordings from the last 2 days
[22:32] <camelreef> np, kids cartoons
[22:32] <mrand> everything is a learning experience ;-)
[22:32] <camelreef> here we go
[22:32] <camelreef> stop backend
[22:33] <camelreef> backing up current broken DB using phpmyadmin
[22:35] <camelreef> dropping all tables
[22:36] <camelreef> importing 0.22 DB
[22:45] <camelreef> ok, restored
[22:45] <camelreef> going to mythtv-setup
[22:45] <camelreef> and all the rest
[22:58] <camelreef> ok, all is back
[22:58] <camelreef> indedd a broken DB
[22:58] <camelreef> indeed
[22:59] <camelreef> probably from MySQL going away before mythbackend
[23:00] <camelreef> want a bug about it?
[23:01] <mrand> Very interesting.  Yes, please attach those two log files to a bug if you could.
[23:01] <camelreef> with pleasure
[23:02] <camelreef> against mythtv-backen, I presume ?
[23:03] <mrand> camelreef: either backend or mythbuntu.  The ticket can be moved around.
[23:05] <camelreef> ok
[23:05] <camelreef> I'll use ubuntu-bugs
[23:05] <camelreef> then atatche the 2 logs
[23:06] <mrand> Awesome.
[23:27] <camelreef> https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/551277
[23:27] <Zinn> [bugs.launchpad.net] Bug #551277 in mythtv (Ubuntu): “mythtv-backen stopped after mysql on shutdown causing database corruption”
[23:27] <camelreef> how's that ?
[23:28] <camelreef> with typo and all...
[23:28] <camelreef> corrected the typo
[23:28] <camelreef> https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/551277
[23:28] <Zinn> [bugs.launchpad.net] Bug #551277 in mythtv (Ubuntu): “mythtv-backend stopped after mysql on shutdown causing database corruption”
[23:32] <mrand> camelreef: that will certainly provide the developers with a reminder to check it out.
[23:33] <mrand> greatly appreciated.
[23:34] <camelreef> np
[23:34] <camelreef> thanks for the attention
[23:37] <superm1> camelreef, oh man that's messy.  i dunno how we can fix such things....
[23:37] <camelreef> really ?
[23:37] <superm1> well all the processes get sent the TERM signal at the same time I thought
[23:37] <camelreef> ouch
[23:37] <superm1> i'm not sure you can really control which one goes down in what order
[23:37] <camelreef> maybe it was one in a million
[23:38] <camelreef> I had shut down the machine a few times since the upgrade
[23:38] <superm1> although there are things like pre-stop scripts i think for upstart jobs
[23:38] <camelreef> or maybe I was hit by a solar flare or whatnot
[23:39] <camelreef> but the logs are there
[23:39] <camelreef> and I think that the one thing vsible is that mysql went down before mysql
[23:39] <camelreef> not much else is visible
[23:40] <camelreef> the real problem could be hidden
[23:40] <superm1> is mysql an upstart job these days?
[23:40] <superm1> i forget it if it got converted
[23:40] <superm1> although maybe i converted it
[23:40] <superm1> yeah i did - that's right
[23:41] <superm1> so maybe there is a way to set dependencies on the way down
[23:41] <camelreef> that would be excellent
[23:42] <camelreef> could you do that on the way up to?
[23:42] <camelreef> I may remember an occasion when the backen was waiting for mysql
[23:42] <camelreef> I may be wrong, though
[23:47] <camelreef> anyway, good luck with that
[23:47] <camelreef> off to bed for me
[23:47] <camelreef> ttyl
[23:55] <superm1> cya


[08:59] <xnox> I regret to inform you that upstart has been removed from Ubuntu Artful release due in 17.10, a follow up announcement about project EOL will follow shortly.


[00:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_analitza build #159: STILL FAILING in 11 min: http://kci.pangea.pub/job/yakkety_unstable_analitza/159/
[00:14] <DarinMiller_> So far, I am including Clive, Rik, Phil, Scarlette, Valorie, Simon, Aaron and Santa so far in the membership doodle.  Any recommended additions or deletions?
[00:14] <valorie> send it to Kubuntu-devel list, DarinMiller_
[00:14] <valorie> including those people is fine, but we have open meetings
[00:15] <clivejo> is it open so people can add themself
[00:15] <clivejo> I prefer to go by crazy_banana_boat these days
[00:15] <DarinMiller_> oh, that's much easier than the method I was attempting.... (scraping addresses off people's lp sites...)
[00:16]  * DarinMiller_ noting clive's appellation change....
[00:17] -kubuntu-ci:#kubuntu-devel- Project merger_ksudoku build #225: FAILURE in 15 min: http://kci.pangea.pub/job/merger_ksudoku/225/
[00:17] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #813: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/mgmt_merger/813/
[00:17] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #797: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/mgmt_progenitor/797/
[00:18] <valorie> just like an old-fashioned wedding, everyone who wants to can speak up when the minister asks, Has anyone a reason this couple should not be wed? Speak now or forever hold your peace
[00:18] <valorie> :-)
[00:18] <clivejo> and if any should speak up, valorie will beat them up with her rucksack
[00:18] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:19] -kubuntu-ci:#kubuntu-devel- Project merger_ksudoku build #226: FIXED in 37 sec: http://kci.pangea.pub/job/merger_ksudoku/226/
[00:19] <valorie> rofl
[00:19] <DarinMiller_> lol
[00:19] <clivejo> that thing is a beast!
[00:19] <clivejo> you could carry an entire football teams laptops in it
[00:20] <valorie> just the little travel lappy
[00:20] <valorie> heavier this trip with extra batteries
[00:20] <valorie> :(
[00:20] <valorie> hopefully I will not need them much
[00:20] <clivejo> but there is room for lots more
[00:20] <valorie> oh, also all the power adaptors for Indian powerpoints
[00:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmail build #117: STILL FAILING in 5 min 9 sec: http://kci.pangea.pub/job/xenial_unstable_kmail/117/
[00:23] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmail build #109: STILL FAILING in 5 min 24 sec: http://kci.pangea.pub/job/yakkety_unstable_kmail/109/
[00:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kube build #1: FAILURE in 6 min 33 sec: http://kci.pangea.pub/job/xenial_unstable_kube/1/
[00:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kube build #1: FAILURE in 7 min 1 sec: http://kci.pangea.pub/job/yakkety_unstable_kube/1/
[00:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kube build #1: FAILURE in 8 min 52 sec: http://kci.pangea.pub/job/zesty_unstable_kube/1/
[00:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #348: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/348/
[00:29] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #155: STILL FAILING in 12 min: http://kci.pangea.pub/job/zesty_unstable_kmail/155/
[00:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_analitza build #160: STILL FAILING in 12 min: http://kci.pangea.pub/job/yakkety_unstable_analitza/160/
[00:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-sdk build #126: STILL FAILING in 13 min: http://kci.pangea.pub/job/zesty_unstable_plasma-sdk/126/
[00:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #403: STILL FAILING in 15 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/403/
[00:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #251: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/251/
[00:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kaddressbook build #98: FAILURE in 14 min: http://kci.pangea.pub/job/xenial_unstable_kaddressbook/98/
[00:39] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-dev-utils build #86: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/zesty_unstable_kde-dev-utils/86/
[00:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdb build #43: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kdb/43/
[00:39] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalarm build #75: FIXED in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kalarm/75/
[00:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kproperty build #29: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kproperty/29/
[00:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadiconsole build #59: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_akonadiconsole/59/
[00:55] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #308: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/xenial_unstable_cantor/308/
[00:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pim-data-exporter build #65: FIXED in 37 min: http://kci.pangea.pub/job/yakkety_unstable_pim-data-exporter/65/
[00:55] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_gwenview build #171: FIXED in 37 min: http://kci.pangea.pub/job/yakkety_unstable_gwenview/171/
[00:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-dev-utils build #135: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/xenial_unstable_kde-dev-utils/135/
[00:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #104: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/104/
[01:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #200: FAILURE in 10 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/200/
[01:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kaddressbook build #111: FAILURE in 12 min: http://kci.pangea.pub/job/zesty_unstable_kaddressbook/111/
[01:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #109: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/zesty_unstable_kopete/109/
[01:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-dev-utils build #148: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/yakkety_unstable_kde-dev-utils/148/
[01:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_k3b build #50: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/yakkety_unstable_k3b/50/
[01:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #169: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/169/
[01:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kexi build #59: STILL UNSTABLE in 53 min: http://kci.pangea.pub/job/xenial_unstable_kexi/59/
[01:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_minuet build #123: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/yakkety_unstable_minuet/123/
[01:13] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdb build #63: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_kdb/63/
[01:13] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kproperty build #72: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_kproperty/72/
[01:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_akonadiconsole build #76: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/zesty_unstable_akonadiconsole/76/
[01:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_k3b build #42: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_k3b/42/
[01:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #130: FAILURE in 21 min: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/130/
[01:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kaddressbook build #67: FAILURE in 6 min 58 sec: http://kci.pangea.pub/job/yakkety_unstable_kaddressbook/67/
[01:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadiconsole build #57: FAILURE in 4 min 27 sec: http://kci.pangea.pub/job/yakkety_unstable_akonadiconsole/57/
[01:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-pa build #357: UNSTABLE in 25 min: http://kci.pangea.pub/job/xenial_unstable_plasma-pa/357/
[01:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kube build #2: STILL FAILING in 4 min 34 sec: http://kci.pangea.pub/job/xenial_unstable_kube/2/
[01:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_grantlee-editor build #72: FAILURE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_grantlee-editor/72/
[01:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_sink build #9: STILL FAILING in 6 min 44 sec: http://kci.pangea.pub/job/zesty_unstable_sink/9/
[01:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_sink build #12: STILL FAILING in 4 min 32 sec: http://kci.pangea.pub/job/yakkety_unstable_sink/12/
[01:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kube build #2: STILL FAILING in 5 min 18 sec: http://kci.pangea.pub/job/yakkety_unstable_kube/2/
[01:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kube build #2: STILL FAILING in 5 min 24 sec: http://kci.pangea.pub/job/zesty_unstable_kube/2/
[01:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #123: FAILURE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/123/
[01:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sink build #12: STILL FAILING in 6 min 25 sec: http://kci.pangea.pub/job/xenial_unstable_sink/12/
[01:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kaddressbook build #99: STILL FAILING in 7 min 49 sec: http://kci.pangea.pub/job/xenial_unstable_kaddressbook/99/
[01:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-sdk build #127: STILL FAILING in 8 min 46 sec: http://kci.pangea.pub/job/zesty_unstable_plasma-sdk/127/
[01:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #349: STILL FAILING in 9 min 6 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/349/
[01:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_korganizer build #84: FAILURE in 9 min 39 sec: http://kci.pangea.pub/job/yakkety_unstable_korganizer/84/
[01:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #228: STILL FAILING in 9 min 48 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/228/
[01:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #404: STILL FAILING in 10 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/404/
[01:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #252: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/252/
[01:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #151: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/xenial_unstable_okular/151/
[01:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pim-sieve-editor build #69: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_pim-sieve-editor/69/
[01:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_korganizer build #76: FAILURE in 13 min: http://kci.pangea.pub/job/xenial_unstable_korganizer/76/
[01:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #122: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/122/
[01:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #81: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/81/
[01:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmail build #110: STILL FAILING in 8 min 43 sec: http://kci.pangea.pub/job/yakkety_unstable_kmail/110/
[01:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kaddressbook build #112: STILL FAILING in 14 min: http://kci.pangea.pub/job/zesty_unstable_kaddressbook/112/
[01:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmail build #118: STILL FAILING in 10 min: http://kci.pangea.pub/job/xenial_unstable_kmail/118/
[01:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kaddressbook build #68: STILL FAILING in 4 min 40 sec: http://kci.pangea.pub/job/yakkety_unstable_kaddressbook/68/
[01:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #156: STILL FAILING in 9 min 16 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/156/
[01:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_korganizer build #90: FAILURE in 16 min: http://kci.pangea.pub/job/zesty_unstable_korganizer/90/
[01:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_sink build #10: STILL FAILING in 3 min 42 sec: http://kci.pangea.pub/job/zesty_unstable_sink/10/
[01:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sink build #13: STILL FAILING in 4 min 43 sec: http://kci.pangea.pub/job/xenial_unstable_sink/13/
[01:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #201: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/201/
[01:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_grantlee-editor build #73: STILL FAILING in 5 min 51 sec: http://kci.pangea.pub/job/yakkety_unstable_grantlee-editor/73/
[01:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_sink build #13: STILL FAILING in 5 min 42 sec: http://kci.pangea.pub/job/yakkety_unstable_sink/13/
[02:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_korganizer build #85: STILL FAILING in 7 min 40 sec: http://kci.pangea.pub/job/yakkety_unstable_korganizer/85/
[02:00] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #131: STILL FAILING in 11 min: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/131/
[02:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_korganizer build #77: STILL FAILING in 4 min 35 sec: http://kci.pangea.pub/job/xenial_unstable_korganizer/77/
[02:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #229: STILL FAILING in 7 min 39 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/229/
[02:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmail build #119: STILL FAILING in 4 min 39 sec: http://kci.pangea.pub/job/xenial_unstable_kmail/119/
[02:03] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #157: STILL FAILING in 4 min 46 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/157/
[02:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #222: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/222/
[02:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #66: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_kdb/66/
[02:03] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kexi build #55: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/zesty_unstable_kexi/55/
[02:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #260: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/260/
[02:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #65: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/xenial_unstable_kproperty/65/
[02:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #193: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/193/
[02:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #294: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/294/
[02:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #126: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/zesty_unstable_kstars/126/
[02:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #79: STILL UNSTABLE in 1 hr 24 min: http://kci.pangea.pub/job/yakkety_unstable_krita/79/
[02:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdb build #44: STILL FAILING in 26 min: http://kci.pangea.pub/job/yakkety_unstable_kdb/44/
[02:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #198: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/198/
[02:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_minuet build #112: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_minuet/112/
[02:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kproperty build #30: STILL FAILING in 26 min: http://kci.pangea.pub/job/yakkety_unstable_kproperty/30/
[02:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #217: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/217/
[02:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #124: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/124/
[02:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalgebra build #166: FIXED in 27 min: http://kci.pangea.pub/job/yakkety_unstable_kalgebra/166/
[02:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_korganizer build #91: STILL FAILING in 5 min 44 sec: http://kci.pangea.pub/job/zesty_unstable_korganizer/91/
[02:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_incidenceeditor build #130: FAILURE in 4 min 38 sec: http://kci.pangea.pub/job/xenial_unstable_incidenceeditor/130/
[02:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_incidenceeditor build #69: FAILURE in 5 min 51 sec: http://kci.pangea.pub/job/zesty_unstable_incidenceeditor/69/
[02:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #393: STILL UNSTABLE in 47 min: http://kci.pangea.pub/job/xenial_unstable_kstars/393/
[02:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #109: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/109/
[02:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadiconsole build #58: NOW UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_akonadiconsole/58/
[02:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #60: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/xenial_unstable_trojita/60/
[02:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_incidenceeditor build #131: STILL FAILING in 3 min 32 sec: http://kci.pangea.pub/job/xenial_unstable_incidenceeditor/131/
[02:16] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_trojita build #59: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/zesty_unstable_trojita/59/
[02:16] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #104: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/zesty_unstable_cantor/104/
[02:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #170: STILL FAILING in 38 min: http://kci.pangea.pub/job/yakkety_unstable_marble/170/
[02:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #126: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/xenial_unstable_marble/126/
[02:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_trojita build #46: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/yakkety_unstable_trojita/46/
[02:24] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_incidenceeditor build #70: STILL FAILING in 7 min 37 sec: http://kci.pangea.pub/job/zesty_unstable_incidenceeditor/70/
[02:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_spectacle build #105: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/zesty_unstable_spectacle/105/
[02:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #220: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_okular/220/
[02:26] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libgravatar build #87: FIXED in 10 min: http://kci.pangea.pub/job/yakkety_unstable_libgravatar/87/
[02:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdiagram build #66: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kdiagram/66/
[02:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-apps-libs build #45: FIXED in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-apps-libs/45/
[02:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #94: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/94/
[02:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #105: STILL UNSTABLE in 1 hr 20 min: http://kci.pangea.pub/job/zesty_unstable_krita/105/
[02:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_calligra build #82: STILL UNSTABLE in 1 hr 17 min: http://kci.pangea.pub/job/zesty_unstable_calligra/82/
[02:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #171: STILL FAILING in 31 min: http://kci.pangea.pub/job/yakkety_unstable_marble/171/
[02:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktexteditor build #194: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_ktexteditor/194/
[02:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkdepim build #78: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_libkdepim/78/
[03:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #282: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_ktexteditor/282/
[03:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #93: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/zesty_unstable_kdiagram/93/
[03:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kunitconversion build #402: STILL FAILING in 4 min 4 sec: http://kci.pangea.pub/job/xenial_unstable_kunitconversion/402/
[03:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kunitconversion build #107: STILL FAILING in 5 min 39 sec: http://kci.pangea.pub/job/zesty_unstable_kunitconversion/107/
[03:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kunitconversion build #403: STILL FAILING in 4 min 34 sec: http://kci.pangea.pub/job/xenial_unstable_kunitconversion/403/
[03:16] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kunitconversion build #108: STILL FAILING in 4 min 37 sec: http://kci.pangea.pub/job/zesty_unstable_kunitconversion/108/
[03:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #128: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_marble/128/
[03:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #80: STILL UNSTABLE in 1 hr 51 min: http://kci.pangea.pub/job/xenial_unstable_krita/80/
[03:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkdepim build #79: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_libkdepim/79/
[03:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okular build #132: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/zesty_unstable_okular/132/
[03:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcmutils build #313: FIXED in 17 min: http://kci.pangea.pub/job/xenial_unstable_kcmutils/313/
[03:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kexi build #75: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kexi/75/
[03:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktexteditor build #104: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/zesty_unstable_ktexteditor/104/
[03:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #99: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_kitemmodels/99/
[03:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_eventviews build #73: FIXED in 13 min: http://kci.pangea.pub/job/yakkety_unstable_eventviews/73/
[03:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemmodels build #376: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kitemmodels/376/
[03:44] <DarinMiller_> by chance are any packagers online?
[03:44] <tsimonq2> !ask
[03:45] <DarinMiller_> Hey Simon!
[03:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_incidenceeditor build #59: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_incidenceeditor/59/
[03:48] <DarinMiller_> I am fighting MP basics 101:  the mp web page is saying I my target repo is invalid.  I modified some ka scripts for santa and am attempting to complete the mp.
[03:49] <DarinMiller_> uploaded here: https://code.launchpad.net/~darinmiller/+git/ka
[03:49] <DarinMiller_> target repo is: ka (yes?)
[03:49] <tsimonq2> YEP
[03:49] <DarinMiller_> Target reference path is: master (yes?)
[03:50] <tsimonq2> eek caps lock
[03:50] <tsimonq2> sorry
[03:50] <tsimonq2> yep
[03:51] <DarinMiller_> so why is the mp website saying "invalid value" and blocking my  mp?
[03:51] <tsimonq2> screenshot?
[03:52] <DarinMiller_> http://imgur.com/a/y97HY
[03:53] <tsimonq2> O___o
[03:53] <tsimonq2> DarinMiller_: Ask in #launchpad
[03:53] <DarinMiller_> ok
[04:01]  * DarinMiller_ feeling rather embarassassed.  Took me half the day today  to realize that my lp account name change yesterday was preventing my git clone/push attempts.
[04:03] <DarinMiller_> I forgot to update my .gitconfig and .ssh/config files.  I was so accustomed to seeing my old username, i was totally disregarding the invalid username warnings.
[04:03] <DarinMiller_> duh...
[04:05] <sintre> lol my epic dumb bug report trumps that 100 fold  , then again it was mostly ignore thank god lol
[04:05] <sintre> good to run into you darin and simom btw
[04:05] <DarinMiller_> hey sintre
[04:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_calligra build #82: STILL UNSTABLE in 59 min: http://kci.pangea.pub/job/yakkety_unstable_calligra/82/
[04:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kunitconversion build #198: STILL FAILING in 4 min 3 sec: http://kci.pangea.pub/job/yakkety_unstable_kunitconversion/198/
[04:23] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kunitconversion build #199: STILL FAILING in 4 min 9 sec: http://kci.pangea.pub/job/yakkety_unstable_kunitconversion/199/
[04:24] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[04:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcmutils build #202: FIXED in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kcmutils/202/
[04:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #328: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/328/
[04:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kjobwidgets build #110: STILL UNSTABLE in 6 min 50 sec: http://kci.pangea.pub/job/zesty_unstable_kjobwidgets/110/
[04:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #329: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/329/
[05:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #94: STILL UNSTABLE in 1 hr 0 min: http://kci.pangea.pub/job/xenial_unstable_calligra/94/
[05:03] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcompletion build #79: STILL UNSTABLE in 9 min 55 sec: http://kci.pangea.pub/job/zesty_unstable_kcompletion/79/
[05:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemviews build #109: STILL UNSTABLE in 9 min 53 sec: http://kci.pangea.pub/job/zesty_unstable_kitemviews/109/
[05:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kconfigwidgets build #73: STILL UNSTABLE in 9 min 53 sec: http://kci.pangea.pub/job/zesty_unstable_kconfigwidgets/73/
[05:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kjobwidgets build #386: STILL UNSTABLE in 8 min 52 sec: http://kci.pangea.pub/job/xenial_unstable_kjobwidgets/386/
[05:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kguiaddons build #95: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kguiaddons/95/
[05:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kconfig build #83: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kconfig/83/
[05:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kauth build #58: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kauth/58/
[05:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwidgetsaddons build #119: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/zesty_unstable_kwidgetsaddons/119/
[05:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcodecs build #90: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kcodecs/90/
[05:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdbusaddons build #116: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/zesty_unstable_kdbusaddons/116/
[05:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #404: FIXED in 15 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/404/
[05:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktextwidgets build #360: FIXED in 15 min: http://kci.pangea.pub/job/xenial_unstable_ktextwidgets/360/
[05:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #205: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/205/
[05:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kjobwidgets build #259: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kjobwidgets/259/
[05:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ki18n build #95: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_ki18n/95/
[05:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcompletion build #184: STILL UNSTABLE in 6 min 57 sec: http://kci.pangea.pub/job/yakkety_unstable_kcompletion/184/
[05:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcoreaddons build #90: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kcoreaddons/90/
[05:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kguiaddons build #386: STILL UNSTABLE in 7 min 4 sec: http://kci.pangea.pub/job/xenial_unstable_kguiaddons/386/
[05:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdbusaddons build #277: STILL UNSTABLE in 7 min 46 sec: http://kci.pangea.pub/job/yakkety_unstable_kdbusaddons/277/
[05:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kconfig build #192: STILL FAILING in 7 min 47 sec: http://kci.pangea.pub/job/yakkety_unstable_kconfig/192/
[05:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdbusaddons build #413: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kdbusaddons/413/
[05:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kauth build #335: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kauth/335/
[05:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ki18n build #408: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_ki18n/408/
[05:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcompletion build #402: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kcompletion/402/
[05:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemviews build #380: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kitemviews/380/
[05:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcodecs build #389: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kcodecs/389/
[05:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemviews build #237: STILL UNSTABLE in 9 min 0 sec: http://kci.pangea.pub/job/yakkety_unstable_kitemviews/237/
[05:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ki18n build #272: STILL UNSTABLE in 9 min 2 sec: http://kci.pangea.pub/job/yakkety_unstable_ki18n/272/
[05:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #222: STILL UNSTABLE in 9 min 1 sec: http://kci.pangea.pub/job/yakkety_unstable_kauth/222/
[05:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcodecs build #274: STILL UNSTABLE in 9 min 1 sec: http://kci.pangea.pub/job/yakkety_unstable_kcodecs/274/
[05:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kguiaddons build #202: STILL UNSTABLE in 9 min 0 sec: http://kci.pangea.pub/job/yakkety_unstable_kguiaddons/202/
[05:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwidgetsaddons build #278: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kwidgetsaddons/278/
[06:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfig build #423: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/xenial_unstable_kconfig/423/
[06:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwidgetsaddons build #392: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/xenial_unstable_kwidgetsaddons/392/
[06:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcoreaddons build #212: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kcoreaddons/212/
[06:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #380: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/380/
[06:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kconfig build #193: STILL FAILING in 7 min 40 sec: http://kci.pangea.pub/job/yakkety_unstable_kconfig/193/
[06:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfigwidgets build #372: NOW UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kconfigwidgets/372/
[07:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kservice build #250: FAILURE in 2 min 48 sec: http://kci.pangea.pub/job/yakkety_unstable_kservice/250/
[07:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kconfigwidgets build #240: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kconfigwidgets/240/
[07:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kservice build #251: FIXED in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kservice/251/
[08:18] <tsdgeos> clivejo: you guys compiled okular without mobipocket support?
[08:20] <tsdgeos> even worse, you guys included all of the backends in okular-extra-backends?
[08:20] <tsdgeos> so installing okular gives you nothing?
[08:50] <acheronuk> tsdgeos: hmmm. I can see that there has perhaps been a misunderstanding during packaging about what some of the installed files actually are and hence where they should go
[10:29] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #152: FIXED in 18 min: http://kci.pangea.pub/job/xenial_unstable_okular/152/
[10:29] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:29] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okular build #133: FIXED in 18 min: http://kci.pangea.pub/job/zesty_unstable_okular/133/
[10:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #221: FIXED in 26 min: http://kci.pangea.pub/job/yakkety_unstable_okular/221/
[11:35] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kaddressbook build #100: FIXED in 9 min 44 sec: http://kci.pangea.pub/job/xenial_unstable_kaddressbook/100/
[11:42] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:42] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kaddressbook build #69: FIXED in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kaddressbook/69/
[11:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kaddressbook build #113: FIXED in 16 min: http://kci.pangea.pub/job/zesty_unstable_kaddressbook/113/
[11:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kube build #3: STILL FAILING in 2 min 34 sec: http://kci.pangea.pub/job/xenial_unstable_kube/3/
[11:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kube build #3: STILL FAILING in 4 min 38 sec: http://kci.pangea.pub/job/yakkety_unstable_kube/3/
[11:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kube build #3: STILL FAILING in 4 min 40 sec: http://kci.pangea.pub/job/zesty_unstable_kube/3/
[11:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalzium build #180: NOW UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kalzium/180/
[11:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalzium build #132: NOW UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kalzium/132/
[11:57] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalzium build #80: NOW UNSTABLE in 15 min: http://kci.pangea.pub/job/zesty_unstable_kalzium/80/
[11:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kube build #4: STILL FAILING in 3 min 32 sec: http://kci.pangea.pub/job/xenial_unstable_kube/4/
[11:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_incidenceeditor build #71: FIXED in 14 min: http://kci.pangea.pub/job/zesty_unstable_incidenceeditor/71/
[12:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kube build #4: STILL FAILING in 3 min 36 sec: http://kci.pangea.pub/job/yakkety_unstable_kube/4/
[12:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kube build #4: STILL FAILING in 4 min 39 sec: http://kci.pangea.pub/job/zesty_unstable_kube/4/
[12:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kube build #5: STILL FAILING in 4 min 34 sec: http://kci.pangea.pub/job/xenial_unstable_kube/5/
[12:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kube build #5: STILL FAILING in 4 min 38 sec: http://kci.pangea.pub/job/yakkety_unstable_kube/5/
[12:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #160: NOW UNSTABLE in 25 min: http://kci.pangea.pub/job/xenial_unstable_messagelib/160/
[12:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #214: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/214/
[12:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kube build #5: STILL FAILING in 6 min 39 sec: http://kci.pangea.pub/job/zesty_unstable_kube/5/
[12:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kube build #6: STILL FAILING in 5 min 3 sec: http://kci.pangea.pub/job/xenial_unstable_kube/6/
[12:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kube build #6: STILL FAILING in 4 min 1 sec: http://kci.pangea.pub/job/yakkety_unstable_kube/6/
[12:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_messagelib build #152: NOW UNSTABLE in 32 min: http://kci.pangea.pub/job/zesty_unstable_messagelib/152/
[12:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kube build #7: STILL FAILING in 3 min 58 sec: http://kci.pangea.pub/job/xenial_unstable_kube/7/
[12:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kube build #7: STILL FAILING in 3 min 58 sec: http://kci.pangea.pub/job/yakkety_unstable_kube/7/
[12:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kube build #6: STILL FAILING in 5 min 44 sec: http://kci.pangea.pub/job/zesty_unstable_kube/6/
[12:22] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #158: STILL FAILING in 6 min 58 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/158/
[12:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kube build #7: STILL FAILING in 4 min 9 sec: http://kci.pangea.pub/job/zesty_unstable_kube/7/
[12:24] <BluesKaj> Hiyas all
[12:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kube build #8: STILL FAILING in 3 min 58 sec: http://kci.pangea.pub/job/xenial_unstable_kube/8/
[12:27] <clivejo> hi BluesKaj
[12:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kube build #8: STILL FAILING in 4 min 2 sec: http://kci.pangea.pub/job/yakkety_unstable_kube/8/
[12:28] <BluesKaj> hi clivejo
[12:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #159: STILL FAILING in 3 min 46 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/159/
[12:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kube build #8: STILL FAILING in 8 min 3 sec: http://kci.pangea.pub/job/zesty_unstable_kube/8/
[12:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_korganizer build #92: NOW UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_korganizer/92/
[12:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #215: STILL FAILING in 36 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/215/
 hello world
 do we currently have a way of making firefox use the KDE file picker to upload files? instead of the GNOME one?
 of the KDE directory picker to download files.
 AFAIK firefox itself needs to be patched. I think chakra and maybe some opensuse people do or did that.
[13:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #160: STILL FAILING in 6 min 15 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/160/
[13:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkdepim build #80: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_libkdepim/80/
[13:11]  * clivejo throws stuff at kmail
[13:14] <yofel> yes, firefox needs a fairly large patchset + a plugin for that. Talk to shadeslayer if you want to know more
[13:14] <shadeslayer> what up
[13:14] <yofel> kmozillaplugin ^
[13:14] <shadeslayer> I haz automation for that
[13:15] <yofel> or however that was called
[13:15] <yofel> send it to ovidiuflorin
[13:17] <acheronuk> ovidiuflorin: patches from here I think? http://www.rosenauer.org/hg/mozilla/file/default
[13:18] <acheronuk> shadeslayer: aha. missed your reply
[13:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #161: STILL FAILING in 5 min 55 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/161/
[13:18] <shadeslayer> ovidiuflorin: https://github.com/blue-systems/pangea-tooling/blob/master/ci-tooling/lib/kdeify.rb
[13:18] <shadeslayer> automation
[13:20] <acheronuk> shadeslayer: I'm more concerned that Firefox 52 is about break the breeze GTK them scrollbars in a fugly way!
[13:20] <shadeslayer> oh?
[13:21] <shadeslayer> maybe try the other css theems
[13:21] <acheronuk> https://bugs.kde.org/show_bug.cgi?id=377008
[13:21] <shadeslayer> have you tried with the gtk theme
[13:21] <shadeslayer> acheronuk: what gtk version do you have?
[13:21] <acheronuk> shadeslayer: I use arc, so don't get the breakage
[13:22] <shadeslayer> ah ok
[13:22] <shadeslayer> because I saw breakage with synaptic because the build system was shit
[13:22] <shadeslayer> I fixed it so it would pick up the right GTK CSS them from breeze now
[13:22] <shadeslayer> https://github.com/KDE/breeze-gtk/blob/master/Breeze-gtk/gtk-3.20/gtk.css
[13:22] <acheronuk> shadeslayer: but if I switch breeze GTK3 it breaks
[13:22] <shadeslayer> you need that
[13:22] <shadeslayer> not the 3.18 one
[13:23] <acheronuk> shadeslayer: pretty sure our breeze builds with the 3.20 one
[13:25] <shadeslayer> acheronuk: point me to the packaging
[13:26] <acheronuk> shadeslayer: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/breeze-gtk/tree/debian/rules?h=kubuntu_zesty_archive
[13:26] <shadeslayer> aha
[13:26] <shadeslayer> yes that sounds about right
[13:27] <acheronuk> shadeslayer: arch and chakra also get the same breakage on firefox beta 52 with GTK >= 3.20
[13:27] <shadeslayer> ok
[13:27] <shadeslayer> acheronuk: does firefox spit out warnings on the console
[13:27] <shadeslayer> because sometimes that's helpful
[13:28] <acheronuk> shadeslayer: mozilla are also looking at it, as it seems to be just them that get a breakage
[13:29] <acheronuk> Neon will be fine, as they are still on GTK 3.18
[13:29] <shadeslayer> ok
[13:30] <acheronuk> just a lot of people may start getting it when mozilla release 52 in a few days time and that gets pushed to users. so be forewarned ;)
 thank you
[13:34] <shadeslayer> ovidiuflorin: basically working folder should have 2 subfolder, one called suse and one called packaging
[13:34] <shadeslayer> then you clone our tooling and do a require_relative '/path/to/kdeify.rb'
[13:36] <shadeslayer> and then KDEify.firefox!
[13:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkdepim build #81: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_libkdepim/81/
[13:37] <acheronuk> cool. I tried to build with those patches long ago, but gave up.
[13:38] <acheronuk> though the normal Firefox does not bother me really
[13:39] <mamarley> My opinion is that the GTK file selector sucks, but I so seldom use it in a browser that it probably isn't worth the effort.
[14:21] <santa_> good morning everyone
[14:21] <santa_> so, apparently today is the 16.12.3 apps tagging
[14:21] <santa_> and the release would be this thursday
[14:22] <santa_> https://community.kde.org/Schedules/Applications/16.12_Release_Schedule
[14:23] <santa_> regarding the autopkgtests the last remaining thing would be akonadi autopkgtests (which are failing right now)
[14:23] <santa_> I have seen a few interesting commits in akonadi's kde git which would be included in .3
[14:24] <santa_> so a possible way to proceed would be: staging .3 tonight, re.schedule the autopkgtests and then go this thursday with the FFE
[14:25] <santa_> clivejo, acheronuk: opinions? do you want a mini dev meeting tonight to discusss this?
[14:30] <acheronuk> santa_: if tarballs are available later, then sounds ok
[14:31] <santa_> I expect them to be available today at some point
[14:48] <santa_> tsdgeos: indeed, the okular-extra-backends package seems to provide more backends/files than what it should be providing, I will get this sorted out for .3
[14:51] <acheronuk> santa_: should be sorted, I hope
[14:51] <santa_> tsdgeos: if you can confirm the neon packaging is ok (and I think it is) you can see the installed files here: https://packaging.neon.kde.org/applications/okular.git/tree/debian I could proceed with a neon "merge" so we will gte this right for zesty
[14:51] <santa_> s/gte/get/
[14:51]  * kfunk can open files over fish:/ again \o/
[14:51] <tsdgeos> santa_: i see lots of kde4 in there
[14:53] <santa_> tsdgeos: oops, let me give you the right link: https://packaging.neon.kde.org/applications/okular.git/tree/debian?h=Neon/release
[14:54] <acheronuk> santa_: already done in our git
[14:54] <tsdgeos> santa_: i've no idea why even someone decided there's first class and second class plugins, so can't confirm if it's right
[14:54] <tsdgeos> i.e. why someone decided to create an okular-extra-plugins is not something i can answer
[14:56] <santa_> tsdgeos: that splitting comes from debian, from a very long time ago. I can't tell you why it was done in the first place, if you think they should be all in the okular package I guess we could give that a try
[14:58] <santa_> acheronuk: ack, thanks
[14:58] <tsdgeos> okular ships all plugins in one package, don't ask me if i think all of them should be together, ask yourselves what you win by them being separate
[15:03] <santa_> tsdgeos: ok, I guess I will discuss this with neon's people to see if there's actually any benefit from that (I have my doubts about it). ftr acheronuk have just corrected the bigger issue so what we have right now in the packaging git is this https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/okular/tree/debian?h=kubuntu_zesty_archive
[15:05] <acheronuk> I also just uploaded a 16.12.1-0ubuntu3 to hopefully sort that version while we stage the .3
[15:05] <acheronuk> and will sync the changelog in git shortly
[15:05] <santa_> thank you
[15:06] <acheronuk> just checked that -extra package and the initial commit for that in 2009 in debian says "initial ubuntu import" in 2009
[15:07] <acheronuk> so maybe originated here with JR/haruld/kubuntu anyway?
[15:08] <acheronuk> s/2009/2011
[15:08] <clivejo> worth chatting JR and Haruld about
[15:08]  * sitter throws a keyboard
[15:08] <yofel> if it's from back then, then it might've been one of those "put stuff extra so it doesn't waste CD space" things
[15:08] <yofel> we did a lot of that back then
[15:09] <sitter> yofel: more likely main vs. universe
[15:09]  * acheronuk throws a mouse... **squeak**
[15:09] <santa_> https://thoughtsfromtheshore.files.wordpress.com/2015/02/jim-carrey.jpg?w=300&h=200
[15:09]  * clivejo pets sitter
[15:09] <clivejo> there there
[15:09] <yofel> sitter: for an okular plugin o.O?
[15:09] <clivejo> copyright issues?
[15:10] <santa_> I don't think so (re: copyright issues)
[15:10] <yofel> maaaaaaybe
[15:10] <sitter> yofel: sure, MIRs were so annoying it often was easier to just split
[15:10] <yofel> someone check the old bzr repo
[15:10] <yofel> sitter: yes, but building the plugin would've already required the MIR, wouldn't it?
[15:11] <sitter> dunno, there also was weird nonesense going on with source vs. bin at some point
[15:11] <yofel> hm, true
[15:16] <sitter> predates bzr even. http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/kdegraphics/revision/1#debian/control
[15:17] <sitter> excitingly enough the changelog does not document when or why it was added
[15:17] <sitter> #ChangelogsAreUseless
[15:17] <sitter> yofel: probably debian put it there becuase "why not"
[15:19] <yofel> now I wonder if that was a thing back in 3.5 o.O
[15:26] <sitter> not sure okular was a thing in 3.5, might still have been kpdf
[15:26] <sitter> https://kpdf.kde.org/
[15:27] <sitter> I enjoy how it still has a website
[15:28] <sitter> so, probably someone between 4.0 beta and 4.0.1 decided that okular should have split backends. why they decided this shall be forever unknown. I like to think it was for purity reasons because kpdf was pdf only so okular clearly should only do pdf, who needs anything else anyway /s
[15:36] <tsdgeos> sitter: if i had to guess someone at canonical didn't want to pull stuff to main, but that's not a problem anymore
[15:36] <tsdgeos> s/canonical/ubuntu/whoever decides those
[15:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeconnect-kde build #189: FAILURE in 24 min: http://kci.pangea.pub/job/xenial_unstable_kdeconnect-kde/189/
[15:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeconnect-kde build #187: FAILURE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kdeconnect-kde/187/
[15:55] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[15:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #162: FIXED in 18 min: http://kci.pangea.pub/job/zesty_unstable_kmail/162/
[15:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeconnect-kde build #96: UNSTABLE in 23 min: http://kci.pangea.pub/job/zesty_unstable_kdeconnect-kde/96/
[15:56]  * santa_ tests kmail with his zillions of mails
[15:56] <santa_> sitter: so ... undo the splitting?
[15:56] <clivejo> sitter: can you make the changed happen in debian too?
[15:56] <clivejo> so they dont filter back down again
[16:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeconnect-kde build #190: NOW UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_kdeconnect-kde/190/
[16:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeconnect-kde build #188: NOW UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kdeconnect-kde/188/
[16:23] <clivejo> yippeeee
[16:24] <clivejo> kmail is working again
[16:24] <clivejo> felt as if I had a leg cut off this past few days!
[16:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #132: STILL FAILING in 4 min 47 sec: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/132/
[16:50] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #133: STILL FAILING in 4 min 42 sec: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/133/
[17:02] <clivejo> tsimonq2: did you do any work on providing a search facility for KCI Unstable PPA?
[17:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #202: STILL FAILING in 4 min 39 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/202/
[17:05] <acheronuk> clivejo: https://bugs.launchpad.net/ubuntu/+source/calligra-l10n/+bug/1670426
[17:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #125: STILL FAILING in 6 min 20 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/125/
 @clivejo, Uh no?
[17:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #203: STILL FAILING in 5 min 40 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/203/
[17:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #126: STILL FAILING in 4 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/126/
[17:25] <yofel> search facility for what kind of data?
[17:27] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #134: FIXED in 26 min: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/134/
[17:57] <ahoneybun> heyo all
[17:58] <wxl> o/
 Packages and files
[17:58] <ahoneybun> what crap day
 Ahoneybun: +1
[18:18] <ahoneybun> valorie: wxl tsimonq2 going to LFNW?
[18:18] <wxl> that's the plan, ahoneybun. you coming?
[18:18] <ahoneybun> thinking of appling
[18:18] <wxl> yes please
[18:18] <wxl> it was fun hanging out with you last time :)
[18:18] <ahoneybun> if we can split a room again
[18:18] <wxl> sure
[18:18] <ahoneybun> it was indeed
[18:19] <ahoneybun> I'll ask for the days off tomorrow at work
[18:19] <wxl> i'm going to come in friday night and leave sunday night so i'm not going to take off work
[18:19] <wxl> i imagine you'll be there earlier, so you're welcome to sign up for the room
[18:20] <wxl> hampton's got special rates https://www.linuxfestnorthwest.org/2017/travel
[18:20] <ahoneybun> I would be coming in on friday and leave on monday
[18:20] <ahoneybun> let me see if I can get funding
[18:20] <ahoneybun> first
[18:21] <wxl> well ok i'll go ahead and reserve it on my card
[18:21] <wxl> otherwise we lose the room
[18:21] <wxl> unless you want to
[18:21]  * wxl bats eyelashes
[18:21] <ahoneybun> well for sure you will go
[18:21] <ahoneybun> not 100% for me
[18:21] <wxl> i'm 100% unless i don't get funding
[18:21] <ahoneybun> xD
[18:21] <wxl> and even if that's the case, i'll just cancel the room
[18:22] <wxl> it's not like they're going to charge me
[18:23] <ahoneybun> well we have a booth there?
[18:25] <ahoneybun> Request sent
[18:25] <wxl> yep
[18:25] <ahoneybun> LFNW can have Code Sprints
[18:25] <ahoneybun> https://www.linuxfestnorthwest.org/2017/community-collaboration-rooms
[18:27] <wxl> that would be nice to do
[18:27] <ahoneybun> atm only you and I are looking to go
[18:27] <wxl> well valorie and tsimonq2 are as well
[18:27] <ahoneybun> alright
[18:28] <ahoneybun> maybe we could call it a sprint
[18:30] <wxl> maybe we could coerce Darin to go
[18:31] <ahoneybun> Darin is in the USA right?
[18:33] <wxl> yeah
[18:33] <wxl> he's in my time zone too if i remember correctly
[18:34] <wxl> ok so i guess i'll call up the freaking hotel and make the reservation from friday-monday with 2 queens
[18:34] <ahoneybun> freaking?
[18:35] <wxl> fooking?
[18:36] <ahoneybun> who is Jaber Gabriel and Paulo Dias
[18:36] <wxl> shoot
[18:36] <wxl> they're out of double queens
[18:37] <wxl> so king with sofabed it is :(
[18:37] <ahoneybun> I call sofabed lol
[18:37] <wxl> good with me!
[18:37] <ahoneybun> xD
[18:37] <wxl> cuz i love a king
[18:37] <ahoneybun> lol
[18:38] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[18:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_keditbookmarks build #55: FIXED in 20 min: http://kci.pangea.pub/job/yakkety_unstable_keditbookmarks/55/
[18:39] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[18:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdialog build #54: FIXED in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kdialog/54/
[18:39] <wxl> i made a request for 2 beds
[18:40] <ahoneybun> nice
[18:46] <wxl> you sent the request for the room? should be $291.72
[18:47] <wxl> we get free full breakfast buffet yay
[18:52] <genii> Probably grilled cheese and coffee
[18:52]  * genii ducks
[18:53] <wxl> ahoneybun: you disappear?
 @genii, or http://i.imgur.com/OYRp44X.png
[19:02] <ahoneybun> oh sorry
[19:02] <ahoneybun> wxl: I sent the request for my flight
[19:03] <wxl> oh ok
[19:03] <ahoneybun> didn't do the room
[19:03] <wxl> i guess that's just as well
[19:03] <ahoneybun> genii: that sounds good to me lol
[19:03] <wxl> yeah i like grilled cheese
[19:04] <ahoneybun> theres an awesome place for that down here wxl
[19:04] <wxl> there is in cleveland too called "melt"
[19:04] <ahoneybun> if there is an event that you can come for down here we'll go
[19:04] <wxl> what happened to um
[19:04] <wxl> uhh
[19:04] <wxl> fossetcon?
[19:04] <ahoneybun> well the guy running it took some time for moving
[19:04] <ahoneybun> he moved from tampa to orlando
[19:05] <ahoneybun> not sure his plans this year
[19:05] <wxl> i REALLY like that guy
[19:05] <wxl> met him at oscon before they stopped doing that in portland :'(
[19:05] <ahoneybun> Bryan?
[19:06] <wxl> yes!
[19:06] <wxl> he had a great talk about radio stuff
[19:06] <ahoneybun> he's a very cool guy
[19:06] <wxl> it was just awesome
[19:06] <wxl> one of the most memorable people i've ever met at an event
[19:06] <wxl> except for you of course XD
 @ahoneybun, Yep, I applied and if I get the funds I'll be there
 genii: Can you give us coffee to give out at the booth? XD
[19:19] <wxl> ok mine is sent
[20:00] <ahoneybun> memorable wxl?
 wxl: We should provide free coffee and/or tea at the booth XD
 See and I'll be there all hyper on caffeine XD
[20:04] <wxl> tsimonq2: you get the funding for it and i'll brew the tea :)
[20:05] <wxl> i could bring my çaydanlık
[20:10] <clivejo> wxl: dont be rude
[20:11] <wxl> clivejo: that's your imagination that's rude :)
[20:11] <clivejo> not I!
[21:05] <genii> @acheronuk: Mmm Fruit Loops!
[21:32] <valorie> the Hampton breakfasts are actually good
[21:33] <wxl> they're not bad at the very least
[21:33] <valorie> you can even make yourself a fresh waffle
[21:33] <wxl> yup
[21:33] <wxl> and they have jam to put on it :)
[21:33] <valorie> my laptop froze again
[21:33] <valorie> :(
[21:33] <wxl> boo
 (Photo, 720x1280) https://irc-attachments.kde.org/zfwTw0cf/file_2167.jpg
[21:34] <valorie> at least it lasted a day and half
[21:34] <wxl> did you apply for the conference pack, valorie ?
 Thanks for the great timing Netflix
[21:34] <valorie> no, you said you would?
[21:34] <valorie> you actually have a working oregon group
[21:34] <wxl> ok
[21:34] <wxl> email me your address?
[21:34] <valorie> wa is basically defunct
[21:34] <wxl> we need to fix that
 Now I'll have some more time for Kubuntu it seems
[21:35] <wxl> especially since wa (you) always do events every year
 wxl: What kind of tea am I buying and how much?
[21:35] <wxl> tsimonq2: get some good black tea and a lot :)
[21:35] <valorie> done
[21:35] <wxl> tsimonq2: this is actually really darn good https://www.jteainternational.com/tea/j-tea-tea-boxes/eugene-breakfast
[21:36] <valorie> I'll be bringing back tea from Assam!
[21:36] <valorie> \o/
[21:36] <wxl> nice
[21:36] <wxl> tsimonq2: https://www.jteainternational.com/tea/yunnan-gold-tips is good too
[21:37] <wxl> i'd say lapsang souchong but that's a bit of an acquired taste
 wxl: I don't think I'll be able to get tea by the TSA now that I think about it :/
 Why not?
[21:37] <wxl> tsimonq2: this is good too http://www.townshendstea.com/black-tea/golden-needles/
 Your American and not traveling to America from somewhere else
 Maybe I can have them ship it to the event?
[21:38] <wxl> exactly
[21:38] <wxl> you could potentially
[21:38] <wxl> ship it to the hotel
 Can the hotel keep packages for you until you get there?
 Or do you have to time it right?
 Yep
[21:40] <wxl> yep
 Jose does that all the time
 Ah ok
[21:40] <valorie> or just ship to me
[21:41] <valorie> by friday
[21:41] <valorie> I mean, by Thursday
 wxl: You should go ping popey and ask for him to support my funding request ;)
 It's in their hands whether I go or not
 Nah
 That doesn't help I don't think
[21:42] <valorie> I'm not sure buy tea and shipping it is worthwhile, given that we have good tea in Washington
[21:42] <valorie> even in Bellingham
 valorie: Maybe you and wxl can work out something and I can foot some if not all of the bill? :)
 We also need styrofoam cups and some coffee :P
 Plus I don't think popey is on the UCC anymore
 @ahoneybun, The Community Council doesn't handle that. The Canonical Community Team does.
 Not even going point out how weird it would be for an adult male to pay for the ticket of a minor lol
 Overlap in some people, for example mhall119
 mhall is everywhere
 @ahoneybun, My mom's bf would be going with me, he has lots of travel miles so he'd pretty much be flying for free
 Oh that's good
 So no stranger danger :P
 XD
 wxl, valorie: I wonder if we can like special make some Ubuntu styrofoam cups XD
 I'm sure Rafael would do it :P
[21:46] <valorie> STYROFOAM????
[21:46] <valorie> paper cups maybe
 Why not? Like hot cups
[21:47] <valorie> styrofoam is of the devil
[21:47] <valorie> but this is the wrong channel for this
 :P
 Yeah I think so
[22:27] <valorie> on the upside, the upgrades yesterday were to the new gcc
[22:27] <valorie> and everything seems hunky dory so far
[22:37] <clivejo> any crashes?
 *BOOM*
 There's a crash :P
[22:41] <clivejo> har har
 You coming to LFNW Clivey?
[22:45] <clivejo> no, too far away
 No, you're in Australia, right? Max isn't a kangaroo?
[22:46] <clivejo> He might think he is at times
[22:46] <clivejo> but no, hes not
 Lol
[23:11] <valorie> clivejo: plasma crashed last night, for no discernable reason, but came right back
[23:11] <clivejo> weird
[23:12] <valorie> but the freeze happened maybe 8 hours after that, so.... no clue
[23:12] <valorie> why crash at 5:30am?
[23:12] <clivejo> no clue
[23:12] <clivejo> I dont have any crashes
[23:12] <clivejo> bar experimental stuff
[23:12] <clivejo> like kmail
[23:12] <valorie> only things running: konversation, faclient which is folding@home, and ktorrent
[23:13] <valorie> this is how i've been leaving it overnight for yonks
 Apps 16.12.3 tarballs aren't there yet :|
[23:14] <clivejo> nope
[23:14] <clivejo> and tsdgeos just told me to read something and I have no idea what it was
 Read what?
[23:15] <clivejo> I dunno what it was!
[23:15] <clivejo> just listings of garbage :/
[23:15] <clivejo> then
 clivejo: All deadlines are due 23:59 UTC
 11:10 PM
 Monday, March 6, 2017
 Coordinated Universal Time (UTC)
[23:16] <clivejo> so I guess we have to wait a while
[23:16] <clivejo> I think acheronuk is chomping at the bit to stage them!
 Ah, yes, well the tarballs would appear today at some point. The hour is not something fixed.
 Anyway even if they are there at some point later, no prob
[23:20] <clivejo> would been nice to get them staged
 Yeah, will do as soon as they are there
 Murphys law says akonadi tests are going to fail anyway XD
[23:22] <clivejo> are Debian and Ubuntu the only distro's to care about autotests?
 Maybe
 And anyway 90% of the problems are the way we execute them
[23:24] <clivejo> wfLoadSkin( 'Vector' );
[23:25] <clivejo> oh how so?
 One of these days I would like to ask in neon of they do, I have the impression they do given some commits I have seen in their git bu keep in mind that they are on xenial while we are on zesty
 @clivejo, See the "common tricks" in phab, for instance
 Keep in mind that kde autotests are not like unit testing a function which calculates a square root. They tend to need sometimes an x server, sometimes a window manager, sometimes certain environment variables...
 Sometimes the tests themselves are broken and they pass by coincidence in kde's ci... (see the kstars case with float/double comparisons for instance
 )
 I mean, welcome to the world of packaging. The world of corner cases :)
 @Santa, You going to be up late to do them if they appear? I can quite happily do it in the morning as well if they are late.
 Yeah I will be on guard for a few hours
 This way I could also schedule the tests in the night
 Whatever you feel like doing then. :)