[00:01] <sarnold> Basketball: at https://chrx.org/chrx-install the function do_install() looks like it supports two install methods already -- compressed tarballs, and docker images; does elementaryos publish either of these?
[00:10] <Basketball> sarnold, nope
[02:51] <sladen> ~>
[10:06] <Harris> I know this is #ubuntu-dev but I have a question about elementary os
[10:07] <Harris> there is a script chrx (chrx.org) that currently supports ubuntu and I want to add support for elementary os
[10:07] <Harris> elementary os is built from seeds of ubuntu whatever that means
[10:07] <Harris> there is a script chrx (chrx.org) that currently supports ubuntu and I want to add support for elementary os
[10:17] <rbasak> I doubt anyone here will know. Try an elementary os support channel.
[10:21] <brendand> rbasak, Harris - but in theory it's Ubuntu based so whatever jiggery pokery chrx does to the ubuntu iso, should apply equally to elementary??
[10:22] <brendand> if you're looking for a step by step, there probably isn't one
[10:23] <brendand> Harris, the best route might be to file an issue against chrx on github
[10:23] <brendand> oh would you look at that
[13:59] <Blu2> Is Ubuntu Core still a thing for Desktop?
[14:03] <seb128> wgrant, hey, could you trigger a new zesty full langpack export this w.e so we can upload updated base langpacks on monday?
[14:09] <wgrant> seb128: There was a full export on Wed, but I'll kick off a fresh one.
[14:21] <seb128> wgrant, right, but the zesty schedule said translators could do their work until the 6th so Gunnar wanted an export after that if possible, thanks
[14:21] <wgrant> seb128: Yep, it'll be done. I've fixed the issue that was causing full exports to be unreliable.
[14:23] <seb128> wgrant, great, thanks!
[15:10] <Laney> @pilot in
[15:10] <Laney> queue's looking good
[15:54] <nacc> is sandbox-upgrader still used ?
[16:04] <nacc> xnox: infinity: --^ you had the last two uploads (trusty and raring) ... I'm guessing not, but would like to confirm before I request it's removal (so we can move vm-builder)
[16:58] <infinity> nacc: Yeah, our uploads were just small dependency fixes, I'm not sure either of us cares at all about the package.
[16:59] <infinity> nacc: mvo's the author, you might ask him about his carefactor.
[16:59] <nacc> infinity: ack, will do
[17:17] <Laney> @pilot out
[17:24] <jbicha> Laney: I don't see any reason to rush LP: #1670248 into zesty, how are we marking bugs we're deferring?
[17:25] <nacc> you can target it to aa-series?
[17:30] <jbicha> ok, there we go, thanks
[17:31] <nacc> np
[20:55] <elopio> barry: ping. We used this to retry the autopkgtests, but it seems to be gone: https://git.launchpad.net/~ubuntu-release/+git/autopkgtest-cloud/tree/tools/retry-github-test
[20:56] <elopio> do you have a new location?
[20:57] <cjwatson> elopio: https://git.launchpad.net/autopkgtest-cloud/tree/tools/retry-github-test
[20:58] <barry> cjwatson: beat me by that --> <-- much
[20:58] <barry> https://code.launchpad.net/~ubuntu-release/autopkgtest-cloud/+git/autopkgtest-cloud
[20:58] <elopio> thanks cjwatson, barry.
[21:35] <|234c7> howdy p33ps


[00:45] <head_victim> AlanBell: that theme looks good and appears to have fixed a number of bugs I had with the old "new" theme. If you can fix bug 624108 in the theme as well I would be over the moon.
[00:45] <ubot4> Launchpad bug 624108 in ubuntu-website "Last-used breadcrumb links are missing (affects: 2) (heat: 5)" [Medium,Confirmed] https://launchpad.net/bugs/624108
[14:07] <AlanBell> head_victim: I can't fix bugs in this new theme yet, newz2000 needs to do some rearranging to publish the code on Launchpad
[14:08] <AlanBell> daker: the grey line over the menu in firefox is not intentional
[14:08]  * AlanBell thinks the design team use more webkit than gecko
[14:12] <AlanBell> looks like #wikinav needs a height attribute
[14:13] <AlanBell> and I have no idea what the objective of "#wikinav hr" is, but turning it off seems to be better
[14:33] <newz2000> head_victim: sounds good, I will keep it on the todo list. It won't be done in the first iteration though
[15:11] <stas> cjohnston: ping
[19:44] <AlanBell> newz2000: updated image: http://libertus.co.uk:8083/moin_static193/light/images/orangeheader-tile.png
[19:44] <AlanBell> that one is 1px narrower and tiles correctly
[19:45] <AlanBell> avoiding a vertical bar every 49px where the diagonals don't join up right
[19:47] <newz2000> AlanBell: I'll check it, got to finish one other thing first
[20:15] <head_victim> newz2000: not a problem, it's the one thing holding me back from using the newer themes though so thought I'd throw in my 2cents as a general user comment for you
[23:56] <mhall119> newz2000: ping


[00:04] <tormod> bryce, I updated the pastebin report: http://ubuntu.pastebin.com/d2e3f7b0a
[03:08] <corp186> I debugged an X crash, patched it up, and got the fix pushed upstream into the xserver git repo
[03:08] <corp186> It fixes bug 361489
[03:09] <corp186> I left a comment about this in the bug
[03:09] <corp186> is there anything else I can do to help get this fix released for ubuntu?
[03:37] <hyperair> corp186: create a debdiff?
[04:00] <corp186> hyperair: done
[04:00] <corp186> anything else I can do?
[04:23] <Sarvatt> hey guys, is there any plan regarding xorg 7.5 component syncs from debian for lucid? I noticed a few protos like render and xf86dri were synced, just curious if more will automatically or if it'll be done manually later because of all the breakage that will come and I'm not sure if I should start throwing things on edgers
[04:39] <hyperair> corp186: well you can subscribe the relevant parties i suppose
[04:40] <hyperair> Sarvatt: lp #361489
[04:40] <hyperair> corp186 was working on that
[08:42] <Sarvatt> phew 2 libs left then i can work on xserver master, think i'll leave that and all the video and input drivers until tomorrow unless anyone wants to help out in lucid on edgers
[09:04] <Sarvatt> i'm just guessing we're going to have xorg 7.5/xserver 1.8 in lucid, figure i'd follow xserver master then switch to 1.8 branch later. anyone know if thats about right? i've been out of the loop for a few months and havent seen any schedules, dunno if it'd be better to do 1.7 for now
[10:44] <mvo> bryce: thanks for your update on the nvidia issues - when I tested without nvidia.ko the system would come up normally, just without glx and with a big warning in the log. is this different for some nvidia driver versions/models? i.e. does it sometimes fails complettely?
[11:41] <Duke`> latest xserver-xorg-video-intel is broken for me (x86_64): pix and fonts are defect.  I saw your halloween pictures while I was trying to find your x package status page :)
[19:45] <Sarvatt> i wish :(
[19:46] <bryce> ahh thanks :-)
[19:46] <Sarvatt> cant afford the $600 for rooms right now
[19:46] <bryce> yeah we're taking veterans day and thurs/fri to head to the beach for a little vacation
[19:46] <bryce> well, maybe we can work out sponsorship for you next time
[19:47] <bryce> actually for X this UDS may be rather dull... we've got few X people coming
[19:47] <Sarvatt> life forced me out of the loop for a few months there, just getting back into the swing of things now that lucid is all set up and I got excited again :D
[19:47] <Sarvatt> yeah i saw that there wasnt much in the way of X stuff on the blueprints
[19:48] <bryce> yeah we missed you.  Baby took me out of the loop as well
[19:49] <bryce> I feel bad, there's a couple severe bugs due to the new gdm and upstart that I could have caught sooner if I'd not been on leave
[19:50] <Sarvatt> i still have to wrap my head around all this new upstart stuff, imagine it is throwing dkms for a loop?
[19:50] <JanC> bryce: sometimes there are more important things in life  ;)
[19:51] <bryce> Sarvatt, pretty much
[19:51] <bryce> JanC, yeah tell that to all the users sending in bug reports ;-)
[19:53] <Sarvatt> karmic was an amazing release, i gave 6 people who dont know much about computers install cds and they have no problems with it unlike jaunty :D the only friend that had problems with it was from doing an upgrade when he had some PPA nvidia blob drivers (like most people do..)
[19:53] <bryce> yeah
[19:54] <bryce> https://wiki.ubuntu.com/X/Bugs/Nvidia
[19:54] <Sarvatt> i had alot of problems with karmic during the dev cycle though that werent really that big a deal but all of them are gone in the release, first time i actually left things alone and used stock stuff there :D
[19:55] <bryce> the whole nvidia thing has been really irritating me.  It seems rather than focus on the huge improvements that have been made on the open source side, esp. intel, it seems everyone is fixated on -nvidia problems, which hardly has ever been without upgrade hassles
[19:56] <bryce> anyway, my guess is just that there have been the usual assortment of -nvidia problems, just that the experience has been poor due to the new gdm lacking failsafe x
[19:57] <Sarvatt> would it be possible to ship precompiled nvidia.ko's with the package? im guessing dkms is gonna need to be running via upstart and putting things on hold instead of building the updates in parallel to booting somehow?
[20:01] <bryce> precompiled only works if we know absolutely what kernel will be running (which we won't)
[20:01] <bryce> we used to do things that way with lrm, and it was quite a hassle
[20:01] <bryce> yeah the real solution is to not do stuff quite so parallel
[20:02] <bryce> also, it may be possible to make it build multiple kernels during install time rather than post-boot time
[20:03] <Sarvatt> yeah i know it can do that from using the drivers straight from nvidia
[20:13] <Sarvatt> kernel packages dont run a postinst trigger to build any dkms modules for the new kernel in it? dunno why i thought they did
[20:14] <Sarvatt> guess that would make dkms a mandatory install though
[20:15] <Sarvatt> since its optional is it a big deal if it delays booting a few seconds always if its installed?
[20:17] <Sarvatt> oh yeah the ko is huge, precompiled for the release kernels would suck :D
[20:33] <Sarvatt> anyone know what arguments this i915 module powersave parameter takes in 2.6.32? is it just 1 for on 0 for off?
[20:37] <tormod> hi guys!
[20:41] <Sarvatt> heyo :D
[20:45] <Sarvatt> 0.16.2-1 (in Ubuntu) to 0.16.2-1~xorgedgers (243 bytes)
[20:45] <Sarvatt> @tormod
[20:47] <bryce> Sarvatt, what was discussed was adding a way to queue up dkms requests during install, so after all base packages are done installing, it does a cycle of dkms builds prior to the reboot
[20:52] <Sarvatt> like add a test for dkms to see if it exists and run it in the gdm shutdown script if so maybe?
[20:56] <bryce> well I got the impression it'd be part of the upgrader, rather than gdm
[20:56] <bryce> but yeah something like that
[20:56] <bryce> ok I'm getting evil eyed by my wife for not being more helpful packing for the beach... gotta go
[20:57] <Sarvatt> have fun man!
[20:58] <RAOF> Yay! Beach!
[21:03] <Sarvatt> hopefully the weather isnt as crappy there as it is here, we've got another 2 days of rain coming :D
[21:04] <tormod> beach? it's skiing season
[21:09] <Sarvatt> maybe they're going somewhere on the way to UDS, its like 80 degrees in texas right now :D
[22:15] <tormod> booting the lucid kernel now, want to check KMS also
[22:16] <Sarvatt> hey you pulled a sarvatt!
[22:17] <Sarvatt> i wish i had my hd2400 pro in the HTPC still, too much of a pain in the butt putting it in to try it out when at best it'll just work like normal but slow.. lol
[23:58] <maco> what's that command to generate a skeleton xorg.conf?


[01:27] <rschroll> aquarius: Any pending changes from you on the icon branch?
[01:27] <rschroll> If not, I'll address those points I had and push it
[01:28] <rschroll> (I have icon downloader code waiting to go it)
[01:28] <aquarius> rschroll, no, get stuck in. I have some half-finished code which actually fetches all the icons and does the "decide which icon" stuff inside manifestParser.js, but it can certainly wait
[01:29] <aquarius> I haven't committed it because I honestly can't decide whether I should decide on an icon with full knowledge and then give you a URL, or give you a list of URLs in order and then you fetch the first one.
[01:30] <rschroll> sounds good
[01:30] <rschroll> I have a C++ plugin to do the icon fetching, waiting in the wings
[01:30] <rschroll> Right now, it gets a list of urls and goes through them until it finds a good one.
[01:31] <aquarius> yeah. The issue is this: if I fetch all the icons to decide, then we have to fetch the "best" icon twice (once in my code, once from C++). Which seems wasteful. But if I *don't* fetch them all, then I don't have enough information to make a decision about which to use.
[01:32] <rschroll> We can worry about that later, I think
[01:33] <aquarius> certainly
[01:33] <aquarius> the current code (that is, all the code which is currently pushed) picks an icon
[01:33] <aquarius> we currently fail if the site points at an icon which doesn't currently exist, but that's OK for now
[01:34] <rschroll> I altered that a bit in my branch.  Now it returns a sorted list.  We can go through the list until we find one that downloads.
[01:34] <aquarius> ah, ok
[01:34] <rschroll> At least I hope we can.  I need a broken site to test it on
[01:35] <aquarius> try, I think, brucelawson.com
[01:35] <rschroll> Do you want to review the branch before I merge it into master, or should I hit the big red button as soon as I'm ready?
[01:36] <aquarius> (I need to make the URL textbox properly handle "www.example.com" and treat it as "http://www.example.com", etc)
[01:36] <aquarius> nah, if you're happy with it, run with it
[01:37] <rschroll> brucelawon: invalid hostname.  It's broken, but not in the right way....
[01:39] <aquarius> bah. I can't remember which URL I used -- it indicated an icon on a different domain, which didn't exist
[01:41] <aquarius> might be worth setting up half a dozen test websites somewhere
[01:41] <rschroll> I can just insert some bad urls in the javascript code and check that the compiled code handles them properly...
[01:41] <aquarius> ha! that's probably easier.
[01:41] <aquarius> have a test suite would be better still, but that's lots of work
[01:41] <aquarius> don't tell the QA people.
[01:43] <rschroll> my lips are sealed
[06:51] <dholbach> good morning
[09:01] <sturmflut2> 30 hours to go for UbuContest!
[09:02] <sturmflut2> And we need much more nominations, so go crazy! :)
[09:05] <sturmflut2> http://ubucon.de/2015/contest/nominate-individual
[10:12] <zsombi> t1mp: why would you need to get the z-value always max?
[10:13] <zsombi> daker: ping
[10:14] <t1mp> zsombi: to put the header on top of other stuff
[10:15] <t1mp> zsombi: but in the end I just went with the default z-value
[10:15] <zsombi> t1mp: you mean overlay the Page content, or whatever it is the content?
[10:15] <t1mp> zsombi: yes
[10:15] <zsombi> t1mp: why don't you leave that to the user?
[10:15] <t1mp> zsombi: but I can more easiliy do that later in the page with header
[10:15] <t1mp> zsombi: right, that's what I'm doing now in the Header
[10:15] <t1mp> zsombi: see https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/cppHeader/+merge/271347
[10:15] <zsombi> t1mp: the Page can then set the z-order if wants, then any other case would need to be custom, right?
[10:15] <t1mp> zsombi: it is ready
[10:16] <t1mp> zsombi: right
[10:16] <zsombi> t1mp: ahh, finally :D
[10:16] <zsombi> t1mp: especially that if you use it in a ListView.header, then you don't have to care about that
[10:16] <zsombi> cool
[10:17] <t1mp> zsombi: this is only the 'empty' header
[10:17] <t1mp> quite a lot of code for such a small API :s
[10:17] <t1mp> but it works :)
[10:17] <zsombi> t1mp: why do you rename ListItems.Header?
[10:17] <t1mp> zsombi: see the Description of the change
[10:17] <t1mp> zsombi: I couldn't get qdoc to work properly if there is a Header.qml *anywhere* :s
[10:18] <t1mp> zsombi: all the \qmlproperty Header::flickable and such go to the ListItem.Header
[10:18] <zsombi> t1mp: fuuuuck!!! wdoc...
[10:18] <zsombi> qdoc
[10:18] <zsombi> t1mp: but you still export it as Header in qmldir right?
[10:19] <t1mp> zsombi: yes
[10:19] <zsombi> ok
[10:19] <t1mp> zsombi: but the ListItems.Header docs are gone :(
[10:19] <zsombi> t1mp: that's because of \deprecated
[10:19] <t1mp> qdoc appears to care about filenames first
[10:19] <t1mp> zsombi: right. Without that I would still have the problem.
[10:20] <t1mp> zsombi: so it seems different "namespaces" for our module is a bad idea for qdoc
[10:20] <zsombi> t1mp: crap
[10:21] <t1mp> zsombi: I chose to do it like this because the ListItems module will be deprecated anyway
[10:21] <zsombi> t1mp: right
[10:21] <t1mp> zsombi: there is just one more thing I started to have doubts about,
[10:22] <t1mp> zsombi: how to deal with styling
[10:22] <zsombi> t1mp: ....
[10:22] <t1mp> zsombi: I could make the header a StyledItem and give it a background (+divider)
[10:22] <zsombi> t1mp: told ya...
[10:22] <t1mp> but that can also come in a subcomponent for the the contents of the Header
[10:22] <t1mp> hmm
[10:22] <zsombi> t1mp: ... it can... but why a subcomponent?
[10:22] <t1mp> zsombi: will making it a StyledItem mess up the implicitWidth?
[10:23] <zsombi> t1mp: why not to derive from Header?
[10:23] <t1mp> zsombi: with subcomponent I meant to derive from Header
[10:23] <zsombi> t1mp: StyledItem takes the implicitWidth if set in the style only
[10:23] <t1mp> zsombi: ah, good :)
[10:24] <zsombi> t1mp: if you set one in teh component, that will override the style one
[10:24] <zsombi> t1mp: check loadStyleItem() or postStyleLoaded()
[10:24] <t1mp> zsombi: I was actually thinking of possible next-gen theming, and whether I should deal with the styling by, for example, adding a background property to the Header
[10:25] <zsombi> t1mp: even if we go with next gen theming, the base type will be something we can control focus and others, so you shoudl deal with it
[10:26] <t1mp> right. So I'll make it a StyledItem
[10:31] <t1mp> zsombi: good, that didn't break any of the unit tests :)
[10:31] <zsombi> t1mp: push it
[10:32] <t1mp> zsombi: I will add a style for the background, and move the implicitHeight to the style as well
[10:32] <zsombi> t1mp: ping me when you are ready...
[10:32] <t1mp> zsombi: okay
[10:35] <daker> zsombi: pong
[10:35] <zsombi> daker: hei, I think me and faenil needs your help :)
[10:36] <zsombi> daker: we have an issue finding out the correct layout for RTL ListItem progression
[10:36] <daker> zsombi sure
[10:36] <daker> zsombi: show me something
[10:36] <zsombi> daker: liek where would you expect to have the progression, on the lright side or on teh left, pointing to the left direction?
[10:37] <zsombi> daker: uhh, that'd be hard... do you have the UITK gallery in hand?
[10:37] <daker> zsombi: screenshot that part
[10:38] <zsombi> daker: in the UITK gallery, in the menu you will see items with chevron
[10:38] <daker> zsombi: i don't have the latest version, using 14.04
[10:38] <zsombi> daker: https://www.dropbox.com/s/yw52ay91pqd2gg8/Screenshot%202015-09-17%2013.38.42.png?dl=0
[10:39] <zsombi> daker: see the chevrons on the first column
[10:39] <zsombi> daker: how woudl you expect to see this layout in RTL?
[10:40] <daker> zsombi: ok so in theory, the first column should be at right
[10:40] <zsombi> daker: ok, how about the header layout? and the list items?
[10:42] <zsombi> daker: do you expect to have the header actions in teh same place as in LTR?
[10:42] <zsombi> daker: also the chevron...
[10:42] <daker> zsombi: wait a sec
[10:42] <zsombi> daker: however if you said the left column shoudl be on the right, then I think intuitive woudl be to have teh chevrons pointing to the left, isn't it?
[10:42] <zsombi> daker: ah, ok, sorry :)
[10:49] <daker> zsombi: i would expect something like this https://imgur.com/OW6iV2D
[10:49] <t1mp> zsombi: I need to create a UCHeaderPrivate in order to set the styleName from cpp?
[10:49] <zsombi> faenil: ^ see daker's screenshot?
[10:50] <zsombi> t1mp: why? no, you shouldn't
[10:51] <zsombi> t1mp: if you don't want to use Q_D() then you can simply go for UCStyledItemBasePrivate::get(this)->setStyleName()
[10:51] <zsombi> t1mp: also, for you, daker's image^^
[10:51] <faenil> zsombi: yep
[10:51] <zsombi> t1mp: for teh header layout
[10:51] <davmor2> popey: what is happening with reminders?
[10:51] <zsombi> daker: thanks, buddy, a lot!!!
[10:52] <faenil> daker: thanks, may I ping you in the future for more difficult examples? :)
[10:52] <t1mp> zsombi: ah, okay :)
[10:52] <daker> zsombi: yw :)
[10:52] <daker> faenil: sure anytime
[10:52] <faenil> great, cheers
[10:52] <zsombi> t1mp: also, if you want to use Q_D() then you need to use Q_DECLARE_PRIVATE_D() macro
[10:53] <zsombi> t1mp: and use QScopedPointer<UCStyledItemBasePrivate> d_ptr
[10:53] <t1mp> zsombi: do I need to set themeVersion?
[10:53] <zsombi> t1mp: uhm... yeah.. you should
[10:53] <daker> faenil: as i said in tablet mode this column at the right, should be at the left
[10:54] <zsombi> t1mp: perhaps we should have a proper solution for that as well... right now this is embedded in the ListItem...
[10:54] <daker> faenil: in other word everthing should be read from Right to Left
[10:54] <faenil> daker: sorry I'm confused now :) you siad the column in tablet should be on the right, is that correct?
[10:54] <faenil> said*
[10:55] <zsombi> t1mp: I was thinking to have a solution for that as well, so we don't necessarily have to derive 13, 14, etc classes
[10:55] <zsombi> faenil: what did confuse you?
[10:55] <zsombi> faenil: the layout I had had two columns
[10:55] <faenil> "as i said in tablet mode this column at the right, should be at the left  "
[10:55] <zsombi> faenil: the one on teh left should be on teh right and th other on teh right shoudl be on teh left.
[10:55] <faenil> yes, he said the first column should have been on the right, now he said on the left :)
[10:56] <faenil> zsombi: yeah, that's what I thought
[10:56] <popey> davmor2: kalikiana was looking at the sdk issue, but do you have logs for the apparmor issue?
[10:56] <zsombi> ehm.. whatever :)
[10:56] <ogra_> just trun the tablet around
[10:56] <faenil> ogra_: deal
[10:56] <daker> faenil: ah sorry, you are correct
[10:56] <davmor2> popey: there was a pastebin that I threw up let me dig it out
[10:57] <faenil> daker: ok I see what you mean now, I misinterpreted your last message, neverming ;)
[10:57] <faenil> nevemind*
[10:57] <popey> davmor2: ta
[10:57] <faenil> but we got it :)
[10:57] <daker> faenil: if you have a layout with colomuns, the order need to be reversed in RTL
[10:57] <daker> faenil: 1|2 in LTR => 2|1 in RTL
[10:58] <t1mp> zsombi: alternatively I could set the style in PageHeader.qml that will inherit from the cpp Header
[10:58] <faenil> daker: sure, sure :)
[10:58] <zsombi> t1mp: do you want to make the PageHeader in cpp or QML?
[10:59] <t1mp> zsombi: qml seems the best solution. It will be a Header with two ActionBars and some title.
[10:59] <t1mp> or a Header with a SlotsLayout, depending on how flexible that will be ;)
[10:59] <zsombi> t1mp: right, then do it there
[11:00] <davmor2> popey: line 15 on I think http://paste.ubuntu.com/12419623/
[11:00] <t1mp> zsombi: in that case, https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/cppHeader/+merge/271347 is ready!
[11:02] <t1mp> zsombi: our generated docs don't show inheritance
[11:02] <popey> davmor2: I'm getting issues on rc-proposed with reminders too now.
[11:02] <zsombi> t1mp: that's bad, qdoc crap
[11:02] <popey> davmor2: "add new account" doesn't work
[11:03] <zsombi> t1mp: I wonder how Qt does... what tags do they use
[11:03] <t1mp> zsombi: right. They have inheritance in the docs
[11:03] <daker> faenil: https://2.bp.blogspot.com/-txMrX6kMxtY/UR6AW28Jx9I/AAAAAAAAB9E/DhVAtPhkPSI/s1600/settings-rtl.png
[11:03] <daker> faenil: https://4.bp.blogspot.com/-EzUf6UQhhus/UR6ATD23lZI/AAAAAAAAB88/_APE31dL4zw/s1600/setings-ltr.png
[11:03] <davmor2> popey: that's the one, but if you create the account in system settings, and then add that app it's called com.reminders_reminders rather than notes right?
[11:03] <t1mp> zsombi: the docs for Header don't show that it is a StyledItem. But I guess that's a separate issue.
[11:04] <faenil> daker: yup :)
[11:04] <popey> davmor2: yes, only user facing parts were renamed
[11:04] <zsombi> t1mp: use \inherits, dear
[11:04] <davmor2> popey: but in ota6 it's called notes
[11:04] <popey> "it"?
[11:04] <zsombi> t1mp: see QQuickFlickable docs
[11:04] <t1mp> right
[11:05] <daker> faenil: if an icon is pointing to a direction, like the chevrons they should point to the correct direction
[11:05] <faenil> daker: yeah, that's what I expected
[11:05] <popey> davmor2: the user facing parts were called notes, but not the plugin. this is expected
[11:06] <t1mp> zsombi: we should do that also for AbstractButton to show that it is an ActionItem
[11:07] <zsombi> t1mp: sure
[11:07] <davmor2> popey: http://people.canonical.com/~davmor2/notes.png
[11:07] <davmor2> popey: that is ota6
[11:07] <popey> right, what's wrong?
[11:08] <popey> [M#mZRequestAccess failed: QDBusError("com.ubuntu.OnlineAccountsUi.InvalidApplication", "Invalid client application")
[11:08] <popey> this is an issue
[11:08] <davmor2> popey: in the installed version it is called com.reminders_reminders not notes so I wondered if that was triggering some of the apparmor issues
[11:08] <popey> no
[11:08] <popey> the user facing bits are called notes
[11:08] <popey> underneath it's reminders
[11:08] <popey> that should be fine, been like that for ages
[11:09] <popey> ^^ the QDBusError is more of a concern!
[11:09] <davmor2> popey: right okay
[11:09] <popey> why is it suddenly unable to launch online accounts
[11:09] <davmor2> popey: no idea
[11:10] <popey> yeah, i'll file a bug
[11:10] <popey> ah, you did https://bugs.launchpad.net/reminders-app/+bug/1496084
[11:11] <davmor2> popey: oh can you change it to confirmed
[11:11] <popey> done
[11:12] <davmor2> mzanetti: can you do a wipe of you device at all?  It seems that myself and popey who have done a wipe can see both issue but you can't, not sure if it is your main phone though or something :)
[11:13] <popey> i haven't wiped
[11:13] <popey> just using my retail device which has had no debs or any nonsense
[11:19] <davmor2> popey: I thought your rc-proposed device was wiped
[11:24] <popey> no
[15:28] <mzanetti> popey, I'd be ready in the hangout already (a bit too early, I know but I've just finished a task)
[15:28] <popey> okay
[15:58] <popey> mzanetti: [M#8        'ubuntu-sdk-15.10-dev1' is not a supported framework
[15:58] <popey> we _are_ using that framework, surely that's the issue then?
[15:59] <popey> (that was from building mardy's branch)
[15:59] <popey> ah, trunk uses 15.04, so the mardy branch will certainly fail.
[16:02] <mzanetti> popey, it should be there by now
[16:03] <popey> mzanetti: not on ota-6
[16:03] <mzanetti> right...
[16:03] <mzanetti> popey, probably this branch was the reason why mardy started the conversation in the first place
[16:03] <popey> yeah
[16:03]  * popey is updating chroots for another build of r490
[16:03]  * popey gets coffee
[16:27] <popey> mzanetti: it works! (cc davmor2 )
[16:27] <mzanetti> popey, which one?
[16:28] <mzanetti> ah, with the updated build chroots
[16:28] <popey> the one built with an updated chroot!
[16:28] <mzanetti> still weird
[16:28] <popey> yes
[16:29]  * davmor2 just blames the store and JamesTait in particular it's easier
[16:30]  * popey flips it back to "Ready for QA"
[16:31] <davmor2> popey: does that fix both issues then?  Or is the other one an sdk issue?
[16:32] <popey> the black box is sdl
[16:32] <popey> *sdk
[16:32] <davmor2> popey: no the reminder setter
[16:32] <davmor2> popey: black box was weather app ;)
[16:33] <popey> oh, yes.
[16:33] <popey> sorry, confused
[16:33] <davmor2> or ride on time
[16:33] <popey> yes, it fixes both
[16:33] <popey> on my ota-6 retail krillin
[16:33] <davmor2> \o/
[16:33] <popey> ya
[16:33]  * popey updates build scripts to update chroots before builds
[16:35] <davmor2> popey: man not even a batted eyelid at throwing ride on time in there, I'm disappointed popey ;)
[16:35] <popey> I am immune to that song
[16:36] <popey> it washes over me
[16:38] <popey> davmor2: to be clear, date thing still busted on rc-proposed, which kalikiana was looking at, but works fine on ota-6
[16:38] <popey> wonder if this is a vivid overlay issue.
[16:38] <davmor2> popey: of all the things that you said.....that you said....are running through my head.......running through my head....../me now pictures popey tapping his foot and cussing me for finding tatu
[16:38] <popey> davmor2: lemme do more testing, I'll undo my citrain switch
[16:39] <davmor2> hahaha
[16:39] <popey> :)
[16:40] <davmor2> popey: what's your opinion of titanium? It's a song that grows on you :)
[16:45] <popey> meh
[16:52] <popey> mzanetti: 163 packages to install in each chroot, I suspect that will fix it ;)
[17:29] <popey> mzanetti: built with fully updated chroot including the ppa, and the date problem is still there, so I am sure it's an SDK issue, because it only happens on rc-proposed, not retail bq
[17:34] <mzanetti> popey, yes. I talked to zsombor about it. seems they are aware of it
[17:34] <popey> ok
[17:34] <popey> sweet
[17:34] <mzanetti> some binding loop decided to go mad
[17:35] <popey> so davmor2 so, what do you want me to do? the date picker is busted, but it seems it's not us?
[17:40] <rschroll> Qt Creator question: Where are the build and run settings stored?  They've become corrupted for my project
[17:40] <rschroll> I've deleted my .user file and the whole build directory, but the settings persist
[17:49] <rschroll> I've removed the relevant kit from that project and re-added it.  Still broken
[17:50] <DanChapman> rschroll: wild guess but are they stored under ~/config/QtProject/*
[17:50] <DanChapman> *.config
[17:51] <rschroll> That was my guess to, but grepping for the project name in that directory gave nothing useful
[17:52] <rschroll> I guess I could nuke the whole directory and see if that helps
[17:52] <DanChapman> zbenjamin: ^^
[17:55] <DanChapman> rschroll hmmm yeah. Well i see there are some kit related directories .config/QtProject/qtcreator/ubuntu-sdk/ubuntu-sdk-15.04-armhf/ no idea whether they are related or what they are for :-)
[17:56] <rschroll> DanChapman: No luck with nuking that directory.  Settings must be elsewhere
[17:57] <DanChapman> meh :-(
[17:57] <rschroll> I dont' have a ubuntu-sdk subfolder.  Hrm....
[17:57] <rschroll> I'm on 14.04, if that makes a difference
[17:58] <rschroll> Well, I do, but it's under ~/.config itself.
[17:59] <rschroll> Nothing project related that I can see, though
[17:59] <davmor2> popey: let me have a play with it and I'll get back to you
[18:00] <popey> thanks davmor2
[18:01] <popey> davmor2: [M#uR53cad72310673c52cefedb551bde3055  com.ubuntu.reminders_0.5.490_multi.click
[18:01] <popey> thats the one that should work :)
[18:01] <davmor2> popey: thanks
[18:10] <Inglebard> Hi, anybody having issue with ubuntu-emulator (segmentation fault) ?
[18:18] <davmor2> popey: is the link the same I assume so just a different check sum right?
[18:18] <popey> yes
[18:18] <davmor2> cool ta
[18:18] <popey> re-download and check
[18:18] <popey> np
[20:02] <mardy> mzanetti, popey: yes, indeed the 15.10-dev1 framework is the reason why that branch is not working at all :-/
[20:03] <popey> :( mardy
[20:04] <mardy> popey: well, my understanding from that e-mail thread is that no one really objects to the creation of a new framework, so things will eventually be solved
[20:49] <zbenjamin> rschroll: per project settings are only stored in the .user file
[20:50] <zbenjamin> rschroll: the other settings are stored in ~/.config/QtProject/qtcreator
[21:24] <kivi> !ping
[21:45] <rschroll> zbenjamin, DanChapman: The problem was the Qt Creator couldn't parse my manifest file because of CMake variables I had in there.  (Why isn't it looking at the manifest file after configuration?)
[21:46] <rschroll> Thanks for the helpful attempts, anyway!


[00:00] <shadeslayer> hurray, wine finished, off to bed I am then
[00:00] <sgclark> night night
[00:01] <valorie> sweet dreams, shadeslayer
[00:02] <valorie> happy new year, ScottK
[00:02] <valorie> ooo, and scarlett
[00:02] <ScottK> Thanks.
[00:02] <valorie> nice to see you again
[00:02] <sgclark> Same to you valorie
[00:03] <valorie> I noticed that you are giving our docs the once-over
[00:03] <sgclark> yeah between flu and holidays I am back logged, but working on Kubuntu userbase now, and going to learn packaging
[00:03] <valorie> which is awesome; thanks so much
[00:03] <Quintasan> sgclark: Any questions bout pbuilder?
[00:03] <valorie> i've forgotten a lot of what I knew on userbase
[00:03] <Quintasan> Note that we are working on trusty so you need only trusty pbuilders for now
[00:06] <valorie> Quintasan: yofel: http://community.kde.org/Promo/Events/FOSDEM/2014
[00:07] <valorie> if you didn't see it already
[00:15] <sgclark> Quintasan: still working on it, fresh install so adding missing repo, updates etc
[00:15] <Quintasan> mmkay
[00:15] <Quintasan> I won't be sticking for too long though since uni
[00:16] <sgclark> at least I assume pbuilder is in kubuntu-dev-tools, command not found atm
[00:16] <valorie> happy new year, Quintasan
[00:16] <Quintasan> sgclark: no, pbuilder is in it's own package
[00:16] <SonikkuAmerica> Quintasan: I talked to you last about Kubuntu Active; is it dead in the water?
[00:17] <sgclark> no worries, I will be around alot more now
[00:17] <SonikkuAmerica> valorie: I haven't finished up the KubuntuLinks page yet; however, I've added the Social Section.
[00:17] <Quintasan> sgclark: generally you want to install ubuntu-dev-tools and kubuntu-dev-tools
[00:17] <sgclark> ok, thanks!
[00:17] <valorie> cool, SonikkuAmerica
[00:17] <MangaKaDenza> so uh...
[00:17] <Quintasan> SonikkuAmerica: Don't really want to get into details now since I have to to go bed if I'm to get up at a reasonable hour. In short: no.
[00:18] <SonikkuAmerica> Quintasan: That's OK, tell me about it later :)
[00:18] <MangaKaDenza> to whom do I report a broken file for the 13.10 iso repository?
[00:18] <MangaKaDenza> or... wait what?
[00:18] <Quintasan> Long version, wait for me to get back here tomorrow or email me at quintasan at kubuntu.org so I can reply in details or something
[00:18] <MangaKaDenza> Huh, thats odd...
[00:18] <Quintasan> MangaKaDenza: How is it broken?
[00:19] <MangaKaDenza> last I tried, I couldn't get the .torrent file for 13.10 64 bit...
[00:19] <MangaKaDenza> but now I can...
[00:19] <valorie> looking good, SonikkuAmerica
[00:19] <MangaKaDenza> like... just a few hours ago I couldn't...
[00:19] <MangaKaDenza> anyways... sorry for wasting your time :P it seems to work now
[00:19] <Quintasan> well, it's...magic?
[00:19] <Quintasan> it took you like 30 seconds so it's not a huge waste of time
[00:20] <MangaKaDenza> file in question, just in case: http://cdimage.ubuntu.com/kubuntu/releases/13.10/release/kubuntu-13.10-desktop-amd64.iso.torrent
[00:20] <SonikkuAmerica> valorie: I hope the Facebook link is right, but the only Kubuntu community page I could find is in French, and it's all screenshots of KDE being contorted every which way.
[00:20] <Quintasan> (actually it's only you who wasted 30 seconds :P)
[00:20] <MangaKaDenza> well see you guys around
[00:20] <SonikkuAmerica> valorie: (Which of course is a good thing)
[00:20] <Quintasan> night
[00:21] <valorie> yeah, I don't know about that fb page
[00:21] <valorie> maybe ask on the kubuntu-devel list
[00:22] <valorie> the thing about having a facebook page is that someone has to maintain it
[00:22] <SonikkuAmerica> Mhm
[09:17] <apachelogger> shadeslayer: do we have a timeline for touchpad-kcm inclusion?
[10:46] <shadeslayer> apachelogger: is everything good to go from the source side? ( haven't read your last conversation )
[10:47]  * shadeslayer is going to patch kde-workspace now
[10:47] <apachelogger> shadeslayer: I never blocked on the source :P
[10:47] <apachelogger> none of the issues was in any way a showstopper
[10:52] <apachelogger> python3-aptdaemon.pkcompat   pulled in by ubuntu-drivers-common
[10:52] <apachelogger> shadeslayer: didn't you do something about that?
[10:52] <apachelogger> or did we decide not to do anything for .10?
[10:52] <shadeslayer> I need to write 2 things for the KCM, the installation stuff and the second one being generic interface name support using udev
[10:53] <shadeslayer> I am thinking of working on install support today, generic names for interfaces isn't a priority and requires me learning udev api pieces
[10:54] <apachelogger> bug 704597
[10:54] <apachelogger> shadeslayer: how does that affect the dependency on polkit?
[10:54] <apachelogger> eh
[10:54] <apachelogger> packagekit
[10:55] <shadeslayer> aha
[10:55] <shadeslayer> apachelogger: I don't think that package is required
[10:55] <apachelogger> it's recommended
[10:55] <apachelogger> and we kinda get ubuntu-drivers-common forced on us by the platform seed
[10:56] <shadeslayer> it's required for the pkkit interface
[10:56] <shadeslayer> not for the stuff we need tbh
[10:56] <apachelogger> yeah
[10:56] <apachelogger> I figured that, hence why I want it gone :P
[10:56] <apachelogger> why I wanted it gone for .10 already
[10:56] <apachelogger> pulls in all sorts of rubbish
[10:56] <shadeslayer> I thought we can twiddle around and make recommends disappear
[10:57] <shadeslayer> with the fancy braces
[10:57] <shadeslayer> hm no, that was to make foo a Depends or Recommends
[10:57] <shadeslayer> but I distinctly remember twiddling so that packages don't pull in Recommends
[10:58] <apachelogger> never seen that
[10:59] <apachelogger> point is
[10:59] <apachelogger> it shouldn't be a recommend to begin with
[10:59] <apachelogger> or should be fullfilled by some kde bit
[10:59] <apachelogger> just not having it on the seed still means the packaging is wrong
[11:01] <shadeslayer> yofel: did you not push kde-workspace 4.11.5 packaging to bzr?
[11:06] <yofel> shadeslayer: I did not package it for trusty
[11:06] <yofel> if you do you'll need to refresh a patch, but I think that's all
[11:08] <shadeslayer> Ack, will have a look later if I get the time
[11:19] <shadeslayer> apachelogger: what were your thoughts on the "IDE in your face" wrt the kde developer meta package?
[11:19] <shadeslayer> IIRC I argued that it was merely a suggests
[11:20] <Riddell> yofel: how about kde-workspace?
[11:21] <Riddell> sgclark: did you get anyone to look at packaging
[11:21] <Riddell> ?
[11:21] <Riddell> Quintasan: yeah come to fosdem
[11:27] <shadeslayer> apparently Riddell is giving a talk there
[11:28] <Riddell> you can cheer me on
[11:28] <shadeslayer> yeah ... that's what I plan to do .... ;)
[11:32] <shadeslayer> hm, no mitya57
[11:45] <shadeslayer> and I don't think moc-boost148-53.patch is required
[12:09] <yofel> Riddell: uh, same question as shadeslayer or..?
[12:12] <shadeslayer> I hate live build
[12:13] <shadeslayer> the only way to get live build to reliably work is to assume the docs are wrong
[12:13] <shadeslayer> and to look at the code
[12:21] <sgclark> good morning
[12:22] <Riddell> morning sgclark
[12:22] <Riddell> what timezone are you in?
[12:22] <sgclark> Pacific in the US
[12:22] <Riddell> yofel: oh yeah, I didn't read his question properly :)
[12:22] <Riddell> sgclark: way over there!
[12:23] <Riddell> sgclark: I'm happy to show you packaging any time we have a couple of hours spare that cross over
[12:23] <sgclark> hehe yeah, I am an early bird though.
[12:23] <sgclark> I am around all day, so whenever you have time :)
[12:24] <Riddell> sgclark: I'll set up an ec2 server, do you have a launchpad account with your ssh key?
[12:24] <sgclark> yep! I got that all updated last night
[12:34] <shadeslayer> hmm
[12:34] <shadeslayer> Riddell: does muon updater work for you
[12:35] <Riddell> let me try
[12:37] <Riddell> shadeslayer: runs fine and downloading updates now
[12:37] <Riddell> in trusty
[12:37] <Riddell> what's not working?
[12:37] <shadeslayer> ack, so some weird auth issue with my system
[12:37] <shadeslayer> need to reinstall everything anyway, partitions are totally full
[12:39] <BluesKaj> 'Morning all
[12:40] <Riddell> sgclark: where your lp account?
[12:41] <sgclark> Riddell: not sure I understand the question, my username is scarlett-7
[12:42] <shadeslayer> sgclark: https://launchpad.net/~scarlett-7
[12:42] <shadeslayer> is that you?
[12:42] <sgclark> that is me :)
[12:43] <shadeslayer> yeah, that's your LP page then :)
[12:51] <shadeslayer> apachelogger: http://bazaar.launchpad.net/~neon/neon/neon5-image/revision/4
[13:12] <Riddell> sgclark: want to get started?
[13:12] <Riddell> ssh ubuntu<EMAIL_ADDRESS>if so
[13:12] <Riddell> and run   byobu
[13:12] <sgclark> Riddell: ok
[13:13] <Riddell> type something if you get in
[13:14] <sgclark> Riddell: denied public key
[13:15] <Riddell> bother, scarlett@scarlett-dev is in the authorized_keys
[13:15] <Riddell> sgclark: try again
[13:16] <sgclark> fail :(
[13:16] <sgclark> let me double check my key
[13:16] <Riddell> sgclark: bother, are you sure you have that ssh key on your system?
[13:22] <sgclark> Riddell: copied again and it was exactly the same. Could it be my configuration?
[13:23] <Riddell> hmm, dunno
[13:24] <Riddell> sgclark: are you in byobu now?
[13:24] <Riddell> type something if so
[13:24] <jussi> is there supposed to be a double ubuntu@ in that address ?
[13:25] <Riddell> jussi: la la la
[13:25] <Riddell> sgclark: gosh you have a narrow terminal
[13:25] <Riddell> sgclark: yay!!
[13:25] <jussi> Riddell: Im sending you stickers tomorrow :) (I has envelopes and everything :D) you should have them very soon.
[13:25] <sgclark> Riddell:lol
[13:26] <Riddell> sgclark: so this is an ec2 cloud computer from amazon's cloud platform AWS
[13:26] <Riddell> sgclark: we're both in that gnu screen session (which has byobu a profile for gnu screen) and can both interact
[13:27] <Riddell> sgclark: would you like me to take you through a package?
[13:27] <sgclark> Riddell: neato
[13:27] <Riddell> you in control me telling you want to do
[13:27] <sgclark> Riddell: yes please
[13:27] <Riddell> sgclark: let's take a look at one I did yesterday, threadweaver
[13:27] <Riddell> sgclark: make a new directory and apt-get update then apt-get source threadweaver
[13:28] <Riddell> I added kubuntu-ppa/experimental to sources.list so it should find it
[13:29] <Riddell> sgclark: you have sudo
[13:29] <Riddell> hmm bother
[13:29] <Riddell> I know, hang on
[13:30] <Riddell> oh maybe I didn't add it
[13:31] <Riddell> sgclark: ok try again
[13:31] <Riddell> grr
[13:31] <Riddell> no source by default
[13:31] <Riddell> sgclark: ok try again
[13:31] <Riddell> yay!
[13:32] <Riddell> sgclark: so here you can see the sources for the package
[13:32] <Riddell> the .orig.tar is what we get from upstream
[13:32] <sgclark> ok
[13:32] <Riddell> the debian.tar.gz contains the debian/ directory with the various instructions for packaging it
[13:32] <sgclark> ok
[13:32] <Riddell> and the .dsc is just a description meta file with md5sums etc for checking uploading and downloading
[13:33] <Riddell> you ran apt-get source with sudo so those files were root, no need for that, I just ran it again as the user
[13:33] <Riddell> sgclark: take a look in the extracted threadwaver directory
[13:33] <sgclark> gotcha
[13:34] <shadeslayer> Riddell: where are the notes for kf5
[13:34] <Riddell> shadeslayer: http://notes.kde.org/p/kubuntu-ninjas-frameworks
[13:34] <shadeslayer> cheers
[13:34] <Riddell> sgclark: ever compiled sources before?
[13:35] <sgclark> Riddell: everyday, main computer is Gentoo hehe
[13:35] <Riddell> elite!
[13:35] <sgclark> Riddell: lol
[13:35] <Riddell> sgclark: so take a look in the debian/ directory, that's where our magic happens
[13:36] <Riddell> changelog has the packaging changelog
[13:37] <Riddell> compat is a version number, most of the work is done by debhelper scripts and that has new versions occationally, compat tells it what version to run as
[13:37]  * allee lurks to learn last stuff about library pkging ...  :-)
[13:37] <Riddell> allee: want to join in?
[13:37] <allee> yes
[13:37] <Riddell> give me an ssh key if so
[13:37] <Riddell> public ssh key
[13:38]  * Riddell thinks allee knows all this already
[13:38] <Riddell> sgclark: control lists the packages that will be made
[13:38] <allee> Riddell: key -> launchpad.net/~allee    Never used api tracing
[13:39] <Riddell> allee: ssh<EMAIL_ADDRESS>[13:39] <Riddell> byobu
[13:39] <Riddell> sgclark: .install files list the files which get made and what .deb packages they go into
[13:40] <Riddell> sgclark: rules is the Makefile which actually compiles then installs everything
[13:40] <sgclark> ahh
[13:40] <Riddell> sgclark: that is mostly a simple target to run everything through  dh  but for more complex stuff you need to know what's going on in there
[13:40] <Riddell> sgclark: and source just has a version of source packaging we're using
[13:40] <Riddell> sgclark: do take a look in each file
[13:41] <sgclark> ok
[13:41]  * Riddell gets a drink
[13:45] <sgclark> Riddell: done
[13:46] <Riddell> sgclark: lets compile this baby
[13:46] <Riddell> sgclark: cd ..; debuild
[13:46] <Riddell> dpkg-checkbuilddeps: Unmet build dependencies: cmake extra-cmake-modules qtbase5-dev
[13:46] <Riddell> sgclark: apt-get install  them
[13:48] <Riddell> sgclark: it's compiling!
[13:48] <sgclark> Riddell :)
[13:49] <Riddell> sgclark: running it with  debuild -nc -j2
[13:49] <Riddell> -nc is no clear and just means it resumes compiling rather than starting again
[13:49] <Riddell> -j2 is build in parallel cos I note this ec2 has 2 processors
[13:49] <Riddell> sgclark: it compiled!
[13:49] <sgclark> gotcha
[13:49] <Riddell> sgclark: take a look in the directory above
[13:50] <Riddell> yay we have our .deb files!
[13:50] <Riddell> you can use lesspipe to see what's in them
[13:50] <sgclark> oh cool
[13:50] <sgclark> lesspipe?
[13:50] <Riddell> lesspipe just runs files through a useful command, in this case dpkg --info
[13:51] <sgclark> oh cool, learned something new
[13:51] <Riddell> looking good
[13:51] <Riddell> sgclark: you can also run them through lintian which is a tool to look for common errors
[13:53] <sgclark> no errors :)
[13:53] <Riddell> yay
[13:53] <Riddell> sgclark: so voila, that's a package
[13:53] <Riddell> sgclark: if you have another hour spare we can have a go at making a new package
[13:53] <sgclark> Riddell: i do
[13:54] <sgclark> Riddell: give me a sec to make more coffee
[13:54] <allee> Riddell: where there file that store the info about methods + version of 1st appearance?
[13:54] <Riddell> allee: you're right I don't seem to have added a .symbols file
[13:55] <Riddell> strange I thought I did but maybe that was another package
[13:55] <allee> there was something in the rules file ...
[13:56] <Riddell> sgclark: allee .symboles files list every symbol in a library to make sure upstream hasn't sneakily removed any and made it binary incompatible
[13:56] <Riddell> doing with with c++ is surprisingly faffy and difficult
[13:56] <Riddell> those clever people at debian have a nice setup for it which we use and is documented at http://pkg-kde.alioth.debian.org/symbolfiles.html
[13:56] <sgclark> ok
[13:56] <Riddell> let me add one to threadweaver
[13:58] <Riddell> so a couple of faffy commands needed
[13:58] <Riddell> debian/libkf5threadweaver5.symbols
[13:59] <Riddell> nope
[13:59] <Riddell> pkgkde-symbolshelper create -o debian/libkf5threadweaver5.symbols -v 4.95.0 symbols.amd64
[13:59] <Riddell> pkgkde-gensymbols -plibkf5threadweaver5 -v4.95.0 -Osymbols.amd64 -edebian/libkf5threadweaver5/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
[13:59] <Riddell> but the other way around
[13:59] <Riddell> then we end up with debian/libkf5threadweaver5.symbols which is checked when a new version comes out
[14:00] <Riddell> also any packages which depend on this library will know which version is the minimum it needs
[14:00] <Riddell> so I'll upload this change to the PPA on launchpad
[14:00] <shadeslayer> Riddell: thoughts about not doing separate dbg packages
[14:00] <Riddell> dch -i  add to the debian changelog
[14:01] <shadeslayer> but then if we want to backport frameworks to PPA's that won't work .. hmmm
[14:01] <Riddell> debuild -S  builds the source only files
[14:02] <Riddell> shadeslayer: what's changed to allow us to do that?
[14:03] <shadeslayer> dbgsym?
[14:03] <shadeslayer> but won't work out well for PPA's is the problem
[14:03] <Riddell> shadeslayer: right but debian will still want dbg packages
[14:04] <Riddell> and I hope this packaging will be useful to them
[14:04] <Riddell> sgclark: dput then uploads it to the launchpad PPA where it will compile and hopefully all will work
[14:04] <shadeslayer> ack
[14:04] <shadeslayer> Riddell: you're missing "include /usr/share/pkg-kde-tools/qt-kde-team/2/debian-qt-kde.mk" in threadweaver
[14:05] <Riddell> shadeslayer: hmm I was just using dh9 rather than dhmk
[14:07] <Riddell> which I suppose might not be how debian wants to do it
[14:07] <Riddell> well I'll e-mail them in a bit and get feedback
[14:07] <Riddell> sgclark: shall we do karchive?
[14:07] <sgclark> ok
[14:08] <Riddell> sgclark: make a new directory
[14:08] <Riddell> and wget  http://download.kde.org/unstable/frameworks/4.95.0/karchive-4.95.0.tar.xz
[14:08] <shadeslayer> dunno why but I can't get dbg package extraction to work :/
[14:08] <Riddell> sgclark: no apt-get possible, it's not packaged yet :)
[14:09] <Riddell> sgclark: copy and paste is your friend :)
[14:09] <sgclark> irc on diff computer
[14:09] <Riddell> doh
[14:10] <Riddell> sgclark: now the tar needs renamed so the - is a _
[14:10] <Riddell> and the end is .orig.tar.xz
[14:11] <Riddell> sgclark: extract it
[14:11] <Riddell> shadeslayer: what are you trying?
[14:11] <Riddell> sgclark: tab completion is your friend :)
[14:12] <sgclark> not working
[14:12] <Riddell> err
[14:12] <shadeslayer> ah nvm
[14:12] <Riddell> why not?
[14:12] <shadeslayer> made it work somehow
[14:13] <Riddell> sgclark: now it's probably easiest just to copy over the debian/ directory from threadweaver into the karchive sources
[14:13] <Riddell> you could also use dh_make which is a command to give you a template
[14:14] <sgclark> ok
[14:15] <Riddell> sgclark: now using your favourite editor edit debian/changelog and update the bits for this package
[14:16] <Riddell> hmm, vi eh?  oh well nobody is perfect :)
[14:16] <Riddell> sgclark: just remove the top block and change my name/address to yours
[14:18] <sgclark> version? no idea
[14:18] <Riddell> sgclark: that's the right version
[14:18] <Riddell> quite a few bits in that version number just to confuse you
[14:19] <Riddell> 4.95.0-0ubuntu1~ubuntu14.04~ppa1
[14:19] <apachelogger> hm
[14:19] <Riddell> 4.95.0 is upstream kde version
[14:19] <sgclark> ok
[14:19] <Riddell> 0 is debian version (0 because it's not in debian)
[14:19] <Riddell> ubuntu1 is ubuntu version
[14:19] <sgclark> gotcha
[14:19] <sgclark> time?
[14:19] <Riddell> ~ubuntu14.04 is a backport version because it's not in the archive
[14:19] <Riddell> and ~ppa1 is more backport because it's in a PPA
[14:19] <Riddell> sgclark: just leave the time
[14:19] <sgclark> ok
[14:19] <apachelogger> Riddell, ScottK, yofel: anyone knows what the 34m/33m stuff is in pykde4? http://paste.ubuntu.com/6715011/ pykde4 in trusty is essentially twice as big as the one in saucy
[14:20] <apachelogger> https://docs.google.com/spreadsheet/pub?key=0AiHh-WCutt3jdEotb2RFaWh1dl9YbFdhdGUwQkgyNWc&output=html
[14:20] <Riddell> sgclark: control is next to edit
[14:21] <Riddell> sgclark: good start
[14:21] <Riddell> sgclark: Homepage next to change
[14:21] <Riddell> check on projects.kde.org for the right url
[14:24] <Riddell> sgclark: now we need to tell it what .deb packages we want it to make
[14:24] <Riddell> sgclark: since I've not compiled this I'm not sure what it'll end up with but it's very likely just the same as threadweaver but with a different name
[14:24] <Riddell> so lets change libkf5threadweaver to libkf5archive
[14:25] <Riddell> apachelogger: some magic for python 3.3 and 3.4?  who does the changelog blame?
[14:25] <Riddell> sgclark: please ask any questions as we're going along of course
[14:26] <Riddell> sgclark: libkf5archive should be libkf5archive5
[14:26] <Riddell> that final 5 is the soname version which gets bumped if there is some binary incompatible change in a new version
[14:27] <Riddell> sgclark: ah but not in the -dev package
[14:27] <Riddell> no so name needed there
[14:27] <Riddell> you just want to compile against whatever the latest version is
[14:30] <sgclark> is that right?
[14:30] <Riddell> sgclark: looking good
[14:30] <Riddell> all done in that file I think
[14:31] <sgclark> why is dev different? and how do I figure that out?
[14:31] <Riddell> sgclark: different how?
[14:31] <sgclark> 5 at the end
[14:32] <Riddell> sgclark: applications typically don't care what version of the library they build against, they just want the latest version, so we don't usually put a version number in there
[14:32] <Riddell> sometimes we do such as with qt4 vs qt5 applications will care what version they build with so we do for that case
[14:33] <Riddell> but .deb binary packages do care they have the right version of the library so we need to version them
[14:33] <sgclark> oh ok
[14:33] <Riddell> else the library version might get upgraded and not the application then it'll crash
[14:33] <Riddell> for the gory details you can read the debian policy on shared libraries which has exact specifications for packaging
[14:33] <Riddell> but that's not much use when getting started, too much detail
[14:34] <sgclark> ok
[14:34] <apachelogger> Riddell:   * debian/rules: Fix support for multiple Python 3 versions.
[14:34] <apachelogger>  -- William Grant<EMAIL_ADDRESS>Mon, 30 Dec 2013 13:38:41 +1100
[14:34] <apachelogger> suppose that's the cause
[14:34] <Riddell> sgclark: in rules you'll need to update the dbg package name I think
[14:35] <Riddell> apachelogger: we've found our culprit, he'll likely know what it'll take to reduce it again
[14:35] <apachelogger> Riddell: also, http://packages.ubuntu.com/saucy/language-pack-kde-en these packages are pulled onto the ISO and bring kdevelop l10n with it for no good reason
[14:35] <Riddell> sgclark: right I'm bored of this, let's try and compile and see what happens!
[14:35] <sgclark> lol ok
[14:35] <Riddell> apachelogger: I don't know another way of doing that,you either have translations installed or people will install packages and not get them translated
[14:36] <Riddell> sgclark: boom!
[14:36] <apachelogger> Riddell:
[14:36] <apachelogger> recommends
[14:36] <sgclark> need to install zlib?
[14:36] <Riddell> apachelogger: downgrade it to a recommends if you want but it'll still be installed on the images by default
[14:37] <Riddell> sgclark: yep it needs libraries for zip bzip and zx I think
[14:37] <apachelogger> nono
[14:37] <apachelogger> I mean kdevelop should recommend kdevelop-l10n
[14:37] <Riddell> sgclark: let me look up the old kde4libs to see what it uses
[14:37] <Riddell> sgclark: zlib1g-dev
[14:37] <apachelogger> the language pack shouldn't
[14:37] <Riddell> sgclark: libbz2-dev
[14:37] <apachelogger> because kdevelop isn't part of our default delivery
[14:37] <Riddell> sgclark: liblzma-dev
[14:37] <Riddell> sgclark: add those to the build-depends in debian/control and install them and rebuild
[14:38] <apachelogger> Riddell: generally speaking the issue is with muon though... it ought to manually craft language packs into the depency tree of a package
[14:38] <apachelogger> i.e. an interactive version of the langauge kcm logic
[14:38] <Riddell> apachelogger: yes that would be nice, although then you'd have people using other ways to install stuff and not getting translations
[14:38] <apachelogger> JT also agreed with that notion, but things we talked about rarely got to see the light of day ^^
[14:39] <Riddell> sgclark: remember commas
[14:39] <apachelogger> Riddell: you have that regardless
[14:40] <apachelogger> right now the people are thos that are using packages that are not recommends of the languagepack and do not have a proper package relationship
[14:40] <Riddell> sgclark: yay it's compiling!
[14:40] <apachelogger> with muon supporting it the group people are those that are using packages that are not recommends of a languagepack and do not have a proper package relationship and were not installed via muon
[14:40] <Riddell> sgclark: just looked at the cmake configure output there, looks like it's all happy
[14:40] <apachelogger> so actually it would reduce the amount of people affected ;)
[14:41] <apachelogger> anyway, IMO if you use a non-user-centric tool then don't expect it to do everything for you
[14:41] <Riddell> sgclark: success! (of some description)
[14:42] <sgclark> dbg error?
[14:42] <apachelogger> Riddell: german l10n removed from seed, this at least should fix the oversize
[14:42] <Riddell> "debug package libkf5karchive5-dbg is not listed in the control file"  hmm, what's up with that?
[14:43] <sgclark> it is there
[14:43] <shadeslayer> hurray for source without attribution
[14:43] <apachelogger> incorrect formatting can make it so that it is technically not there (the dbg package)
[14:44] <Riddell> sgclark: I think we don't use a version number in the dbg package
[14:44] <Riddell> although suddenly I realise there's mixed practice on that
[14:44] <Riddell> sgclark: ah you misspelt it in debian/rules, an extra k
[14:44] <apachelogger> for dbg packages? Oo
[14:45] <Riddell> or are we missing that k everywhere?
[14:45] <Riddell> apachelogger: to version or not to version dbg?
[14:45] <apachelogger> version
[14:45] <Riddell> libKF5Archive.so  only 1 K
[14:45] <apachelogger> otherwise you can't debug libfoo1 and libfoo2 on the same system
[14:46] <Riddell> apachelogger: the majority are against you http://paste.ubuntu.com/6715111/
[14:46] <apachelogger> (also technically speaking again ... you can debug libfoo1 and libfoo2 because debug symbols are named with uuids so there is no actual file conflict, but you have to update/downgrade the dbg packge as needed ;))
[14:46] <apachelogger> Riddell: the majority is wrong
[14:47] <sgclark> I may be lost now. So do I need to change stuff to archive rather than karchive?
[14:47] <apachelogger> Riddell: it's like some libraries have stuff in /usr/share and that is packaged in libfoo1 ...
[14:47] <Riddell> sgclark: yes should all be kf5archive
[14:47] <apachelogger> defeats the purpose of calling it libfoo1 in the first place
[14:47] <Riddell> sgclark: next you need the .install files moved and changed for kf5archive
[14:49] <apachelogger> Riddell: btw random thought on the kf5 packaging ... please do that in bzr and please bzr branch it from kdelibs
[14:49] <apachelogger> kppp packaging has no history because it was manually copied :S
[14:49] <Riddell> apachelogger: good idea
[14:50] <sgclark> Riddell: correct?
[14:51] <Riddell> sgclark: yeah I think so
[14:51] <Riddell> we can check once you've done the -dev one
[14:52] <Riddell> groovy
[14:52] <Riddell> sgclark: run (probably from the directory above) dh_install --list-missing
[14:52] <Riddell> that'll check if the .install files are listing the right stuff
[14:53] <Riddell> dh_install: usr/mkspecs/modules/qt_KArchive.pri exists in debian/tmp but is not installed to anywhere
[14:53] <Riddell> what the heck is that?
[14:54] <Riddell> "### qmake support - TODO, make a ecm macro for this"
[14:54] <Riddell> says the cmake file
[14:54] <Riddell> weird
[14:54] <Riddell> sgclark: well I guess you'd better add that to the -dev.install file
[14:54] <sgclark> sorry, add what?
[14:54] <Riddell> usr/mkspecs/modules/qt_KArchive.pri
[14:56] <sgclark> ok
[14:57] <Riddell> sgclark: now lets add the symbols file
[14:59] <Riddell> sgclark: I did that, it's too faffy to explain but that details are on http://pkg-kde.alioth.debian.org/symbolfiles.html
[14:59] <sgclark> yeah, will read that after we are done
[15:00] <Riddell> sgclark: next debian/copyright needs updated
[15:00] <Riddell> sgclark: licencecheck tells me it's all LGPL 2
[15:00] <Riddell> which is the same as threadweavers
[15:00] <Riddell> so it should just be updating some names
[15:00] <Riddell> sgclark: are you able to copy/paste them or shall I?
[15:01] <sgclark> go ahead
[15:02] <tester56> hi, could somebody try the following: go to systemsettings,/workspace appearance/Window Decorations and click: configure decoration. Now  change for example the button size, click ok and the results apply instantly without clicking the apply button ...
[15:02] <tester56> at least on my setup it behaves that way ... seems like a bug to me ...
[15:04] <Riddell> sgclark: right, do a debuild -j2  to build it again and this time it should be a work of perfection
[15:05] <tester56> i would like to file a bug against the kcm module, the probleme is, i do not know which module this belongs to... but first of all I would be happy if someone could confirm or refute ...
[15:05]  * Riddell highfives apachelogger and shadeslayer for doing worthy tasks today
[15:05] <Riddell> sgclark: oh we renamed that package so it didn't clear those files, just rm -r debian/libkf5archive5-dbg
[15:06] <shadeslayer> I wish someone would do these shitty copyright files for me
[15:06] <shadeslayer> it's the thing I hate most about packaging
[15:06]  * shadeslayer high fives Riddell
[15:06]  * Riddell makes a cup of tea
[15:06] <sgclark> woot compiling
[15:07] <sgclark> yeah, seems I need to sit down and learn sed. I have avoided it forever lol
[15:09] <sgclark> was a error in copyright, run debuild again?
[15:12] <Riddell> ah yes
[15:12] <Riddell> W: karchive source: syntax-error-in-dep5-copyright line 12: Cannot parse line "2004-2013 Mirko Boehm"
[15:12] <shadeslayer> apachelogger: how do I know what's what in that csv
[15:12] <Riddell> sgclark: you fixed that?
[15:12] <sgclark> Riddell: yes
[15:12] <sgclark> was left from threadweaver
[15:12] <Riddell> sgclark: ok build again and see if it is fixed
[15:14]  * Riddell spams kubuntu-devel with moderated postings
[15:14] <Riddell> W: libkf5archive-dev: non-standard-dir-in-usr usr/mkspecs/
[15:14] <Riddell> sgclark: that needs a bit more investigation
[15:15] <Riddell> seems /usr/share/qt5/mkspecs/ is the place for those files to go on debian/ubuntu
[15:15] <tester56> so nobody knows the name of the kcm module "workspace appearance"?  :-(
[15:15] <Riddell> # Packagers who use -DCMAKE_INSTALL_PREFIX=/usr will certainly want to set ECM_MKSPECS_INSTALL_DIR to something like share/qt5/mkspecs/modules
[15:16] <Riddell> tester56: i think we're all busy, you can try in #kde-devel ?
[15:16] <shadeslayer> ah it's at the bottom
[15:16] <shadeslayer> how weird
[15:16] <shadeslayer> Riddell: I don't suppose you have a LGPL-2 stub lying around for debian/copyright?
[15:16] <tester56> Riddell, sure, sry for interrupting!
[15:18] <apachelogger> for a minut enow my inbox keeps notifiying me of review requets
[15:18] <apachelogger> this looks dodgy
[15:18] <shadeslayer> likewise
[15:18] <apachelogger> someone tries to kill my mail :@
[15:18] <sgclark> wow 46 email in kubuntu-devel haha
[15:18] <apachelogger> now it stopped, muhahaha
[15:18] <shadeslayer> ^^
[15:19] <Riddell> shadeslayer: look in threadweaver
[15:19] <shadeslayer> Riddell: LGPL-2+
[15:19] <Riddell> shadeslayer: backspace is your friend :)
[15:19] <Riddell> shadeslayer: copy/paste from whatever the source files say
[15:20] <Riddell> sgclark: yep this needs some more investigation to fix properly
[15:20] <sgclark> ok
[15:20] <Riddell> sgclark: but I think we're otherwise all good
[15:20] <apachelogger> oh the notifications stopped
[15:20] <apachelogger> my inbox is full with launchpad reviews and someone decided to send me patches
[15:21] <apachelogger> by mail
[15:21] <Riddell> sgclark: install the .debs to check they really install
[15:21] <apachelogger> :S
[15:21] <Riddell> sgclark: dpkg --install *deb
[15:21] <apachelogger> shadeslayer: csv? what csv?
[15:21] <shadeslayer> https://docs.google.com/spreadsheet/pub?key=0AiHh-WCutt3jdEotb2RFaWh1dl9YbFdhdGUwQkgyNWc&output=html
[15:22] <apachelogger> desktop + desktop-common
[15:22] <apachelogger> ah
[15:22] <apachelogger> wait
[15:22] <Riddell> sgclark: yay, now let's upload it    debuild -S   to build the source
[15:22] <apachelogger> shadeslayer: your question fails to parse
[15:22] <apachelogger> shadeslayer: the size diff you mean?
[15:22] <shadeslayer> apachelogger: nvm, I found out what the columns meant
[15:22] <apachelogger> red -x size increase by x... green x size decrease by x
[15:22] <shadeslayer> the description is at the bottom
[15:22] <shadeslayer> instead of the top
[15:22] <apachelogger> shadeslayer: ah yeah, sorting was very nice xD
[15:23] <shadeslayer> the world is upside down
[15:23] <apachelogger> google docs is weird
[15:23] <apachelogger> also .... it has a hard time computing the diff for the some 1600 entries in the table
[15:23] <sgclark> I don't have  a key on this server
[15:23] <Riddell> sgclark: yeah I need to sign it
[15:23] <apachelogger> I should claim that google docs are not very suitable for anything but writing the odd letter now and then
[15:23] <Riddell> as a member of kubuntu-ppa
[15:24] <sgclark> k
[15:24] <shadeslayer> kcodecs up
[15:24] <apachelogger> Sput: https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1262187 does that compute for you?
[15:24] <Riddell> sgclark: press return to upload!
[15:24] <shadeslayer> needs more license stubs that I was too annoyed to add
[15:24] <apachelogger> shadeslayer: http://bazaar.launchpad.net/~neon/neon/neon5-image/revision/4 needs ppa-purge
[15:25] <Riddell> sgclark: ahem, press again
[15:25] <shadeslayer> but whai
[15:25] <sgclark> woot
[15:25] <Riddell> sgclark: well done, you're now an elite kubuntu ninja!
[15:25] <sgclark> coolness
[15:25] <Riddell> sgclark: if you have an idenity.kde.org account you can update the package status on https://notes.kde.org/p/kubuntu-ninjas-frameworks
[15:25] <apachelogger> shadeslayer: because of transitions a la 'kdelibs is now karchive,kdesu,kded,kconfig,kspaceship;kdalek'
[15:25] <sgclark> there a package I can try on my own computer?
[15:25] <sgclark> I do
[15:26] <shadeslayer> apachelogger: not required
[15:26] <apachelogger> pourqui?
[15:26] <shadeslayer> apachelogger: I purged the schroot cache and stuff
[15:26] <apachelogger> nah
[15:26] <shadeslayer> so it doesn't give issues now
[15:27] <apachelogger> see, I wrote a la there because I did not mean kdelibs specifically :P
[15:27] <Riddell> sgclark: you can scp the .deb files to your computer and install them but they were built for trusty so they probably won't install if you're using saucy, you'd also need to have the qt5 PPA setup
[15:27] <sgclark> in file, what do I put?
[15:27] <Riddell> sgclark: you can watch the package compile at https://launchpad.net/~kubuntu-ppa/+archive/experimental/+packages
[15:27] <Riddell> sgclark: how do you mean "in file"?
[15:27] <sgclark> ninjas frameworks
[15:28] <Riddell> sgclark: change wip (work in progress) to "in PPA"
[15:28] <apachelogger> shadeslayer: since neon does not have package relationships that would remove split rubbish the ISO builder needs to make sure it does not run into issues like the kdelibs transition
[15:28] <apachelogger> hence why it should completely wipe all of project-neon5 and then install session again
[15:29] <sgclark> never used this befre, does it save itself?
[15:29] <Riddell> sgclark: yes it does
[15:29] <Riddell> it's etherpad
[15:30] <sgclark> oh, I meant another package to package
[15:30] <shadeslayer> apachelogger: checking if I can do that
[15:31] <Riddell> yay we made omgubuntu! http://www.omgubuntu.co.uk/2014/01/kde-frameworks-5-tech-preview-released
[15:32] <Riddell> sgclark: so if you're up for doing more find another tier 1 module to package from http://community.kde.org/Frameworks/Epics/Splitting_kdelibs
[15:32] <shadeslayer> Riddell: are we also tracking kf5 packaging in bzr?
[15:33] <mikecb> The first comment want's screenshots of the frameworks.
[15:33] <Riddell> shadeslayer: not yet but we ought to start doing that
[15:33] <shadeslayer> yeah
[15:33] <Riddell> mikecb: here's a lovely one http://agateau.com/tmp/kf5/tier3-kio.png :)
[15:34] <Riddell> ooh this is a goodie http://agateau.com/tmp/kf5/tier3-kdeclarative.png
[15:34] <mikecb> Riddell: such diagram, many arrow, boxes, wow
[15:35] <Riddell> mikecb: this has a screenshot of plasma 2 using frameworks 5 http://kshadeslayer.wordpress.com/2013/12/03/introducing-project-neon-5-isos/
[15:35] <Riddell> not much to show alas
[15:35] <shadeslayer> apachelogger: okay can't be done, live build does a install pass post restoring the chroot
[15:35] <mikecb> nice!
[15:36] <shadeslayer> so it'll fail there if files are moved
[15:36] <shadeslayer> unless we pass options to overwrite files
[15:37] <sgclark> ok, need to eat some breakfast and stuff, will try to package something something on my setup in a bit, thanks for all the help
[15:39] <apachelogger> shadeslayer: I am confused, how would that diff of yours work then?
[15:39] <apachelogger> because there are bound to be file conflicts
[15:40] <shadeslayer> apachelogger: yeah, we /could/ pass an option to overwrite files
[15:42] <shadeslayer> apachelogger: FWIW if I drop pm-utils I can save another 0.5 MB of space :D
[15:42] <shadeslayer> on the ISO
[15:43] <Riddell> yay!
[15:47] <apachelogger> shadeslayer: poor powermanagement :(
[15:47]  * apachelogger out for dinner
[15:50] <shadeslayer> dinner? 0.o
[15:51] <shadeslayer> it's only 5
[15:52] <Riddell> high tea
[15:53] <sgclark> hehe 8am here
[15:53] <Sput> apachelogger: sounds like settings are not stored properly. does it work for you?
[16:13] <Riddell> sgclark: are you done with the ec2?
[16:24] <sgclark> Riddell: yes sorry
[17:27] <shadeslayer> who wants to write copyright files!
[17:31]  * yofel drops a needle and vanishes
[17:33] <shadeslayer> kimageformats has like 3-4 files that have a standard copyright header
[17:33] <shadeslayer> everything else has "This code is distributed under the conditions of foo blah blah"
[17:35] <Riddell> shadeslayer: your copyright file for kcodecs has a couple of issues
[17:36] <shadeslayer> Riddell: I know, I hate those files
[17:36] <Riddell> shadeslayer: it says src/probers/ is MIT but doesn't list what MIT is
[17:36] <shadeslayer> MIT/X11?
[17:36] <Riddell> it says src/probers/nsSJISProber.h is MPL but it's also LGPL
[17:36] <Riddell> shadeslayer: want me to tidy it up?
[17:37] <shadeslayer> nsSJISProber.h can be relicensed under MPL/GPL 2/LGPL 2.1
[17:37] <shadeslayer> though the primary one seems to be MPL
[17:37] <shadeslayer> feel free to tidy it up more
[17:37] <shadeslayer> if you want you can also do kimageformats
[17:38] <Riddell> gosh is that the time, I don't think I can do kimageformats today :)
[17:38] <shadeslayer> :D
[17:38] <Riddell> shadeslayer: based on sune's say so I've decided to use dhmk for debian/rules files
[17:38] <shadeslayer> fooey, ok
[17:41]  * Riddell updates kcodecs
[17:41] <Riddell> Source: git://anongit.kde.org/kcodecs   hmm I was using the projects.kde.org URL for that in debian/copyright
[17:43] <shadeslayer> well, that *is* where one would get the source for kcodecs
[17:43] <Riddell> spose so
[17:44] <Riddell> W: libkf5codecs: package-name-doesnt-match-sonames libKF5Codecs5
[17:44] <Riddell> W: libkf5codecs: description-synopsis-starts-with-article
[17:44] <Riddell> tsk
[17:45] <Riddell> I has also started versioning the -dbg packages so libkf5codecs5-dbg based on discussions in debian channel
[17:46] <Riddell> I had also put Multi-Arch: same but I don't really know what that's good for
[17:48] <shadeslayer> do we *want* to have names with weird casing?
[17:48] <Riddell> how do you mean?
[17:51] <shadeslayer> libKF5Codec{-dbg,-dev}
[17:52] <Riddell> .deb package names need to be lower case
[17:55]  * Riddell out
[17:57] <Riddell> shadeslayer: but do remember to version them libkf5codec5-dbg (not the -dev)
[18:01] <shadeslayer> Riddell: ack
[18:01] <shadeslayer> Riddell: did you fix kcodec?
[18:01] <Riddell> shadeslayer: yep
[18:01] <shadeslayer> awesome
[18:01] <shadeslayer> I'm going to upload kimageformats
[18:01] <shadeslayer> without a copyright file
[18:02] <shadeslayer> fortunately, they're only plugins, so no naming or symbol files
[18:03] <shadeslayer> *weird lib naming
[20:20] <Peace-> Riddell:
[20:20] <Peace-> r y there?
[20:33] <Peace-> guys i have a problem with kubuntu and palava.tv
[20:33] <Peace-> it seems it's a problem with phonon
[20:33] <Peace-> apachelogger: ^
[20:48] <shadeslayer> sgclark: hey, saw your email
[20:48] <shadeslayer> sgclark: I'd use licensecheck to find the right copyright
[20:48] <sgclark> shadeslayer: I managed to get the command :) where do I find the licence though
[20:48] <shadeslayer> or copyright-helper
[20:48] <shadeslayer> sgclark: as in the full text?
[20:48] <sgclark> that a program?
[20:49] <shadeslayer> sgclark: yes, it's a perl script to ease copyright checking
[20:49] <shadeslayer> just google for copyright-helper and you'll find it
[20:49] <sgclark> I was able to grep the copyright info from source, fine
[20:49] <shadeslayer> alternatively : git clone git://anonscm.debian.org/users/modax/copyright-helper.git
[20:49] <sgclark> thank you
[20:49] <shadeslayer> usage : ./copyright-helper.pl -f  /path/to/source
[20:50] <shadeslayer> sgclark: full licenses in /usr/share/common-licenses
[20:51] <shadeslayer> mmmm ... I've had too much chocolate
[20:54] <sgclark> oh wow great program, thanks so much
[20:57] <sgclark> shadeslayer: what if most files are LGPL-2.1+ but 2 files are LGPL-2
[20:58] <shadeslayer> sgclark: you can specify regex's
[20:58] <shadeslayer> so for LGPL-2.1+ you can do  : Files: *
[20:58] <shadeslayer> then for the 2 files that are LGPL-2 : Files: src/foo1.cpp\nsrc/foo2.cpp
[20:58] <shadeslayer> or Files: src/foo1.*
[20:59] <sgclark> and it seems 5 files not explicitly specified
[21:04] <sgclark> I do not have any licenses with + in common-licenses, is there a difference?
[21:07] <shadeslayer> sometimes the license header is not in the standard format
[21:07] <shadeslayer> so you have to read the license which should specify what license it is
[21:09] <sgclark> ugh, afraid I am completely lost here, what am I supposed to put in copyright file in debian? I am using one we did earlier and this copyright is much shorter than that /usr/share one
[21:10] <sgclark> I was doing so well until copyright :(
[21:20] <ScottK> apachelogger: If there's more than one supported Python version, that's excepted.
[21:21] <ScottK> expected.
[21:36] <apachelogger> ScottK: is that going away before final or what?
[21:36] <ScottK> Not sure (I've lost the bubble).  Ask barry or doko.
[21:48] <Peace-> apachelogger:
[22:09] <shadeslayer> sgclark: sorry for leaving you in the dark, had to cook dinner
[22:09] <shadeslayer> sgclark: basically one puts the copyright stub
[22:10] <shadeslayer> that's usually found in the code
[22:10] <shadeslayer> as for the cmake issue, you're missing the Qt 5.2 ppa
[22:10] <shadeslayer> https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta2
[22:13] <sgclark> shadeslayer: thanks!
[22:13] <shadeslayer> :)
[23:27] <ahoneybun> hey valorie
[23:27] <valorie> hi ahoneybun
[23:27] <ahoneybun> how are you?
[23:28] <valorie> I'm good
[23:28] <valorie> how are you?
[23:29] <ahoneybun> good too
[23:29] <ahoneybun> really happy about sgclark's work
[23:29] <sgclark> look ok?
[23:29] <ahoneybun> yea
[23:29] <valorie> beware, Riddell is trying to steal her from us
[23:29] <sgclark> lol
[23:30] <ahoneybun> lol
[23:30] <valorie> can't trust those ninjas.....
[23:30] <valorie> really, it's lovely to have lots of people doing lots of things
[23:31] <valorie> cross-knowledge makes us all smarter
[23:31] <sgclark> I am going to remove the construction tags, hopefully some translators will do their magic
[23:31] <valorie> once we do that on a few pages, I'll write to the translation teams asking for their help
[23:32] <valorie> ovidiu-florin: did you get the help you needed to start translating on Userbase/kubuntu?
[23:32] <sgclark> I finished them all today :) can refine as we go, but tags are right etc now
[23:32] <valorie> awesome
[23:32] <ahoneybun> valorie: did you see the installation and software pages?
[23:33] <valorie> well, we need the text to be pretty much set, or it's unfair to ask them to start work
[23:33] <valorie> not in the last couple of days
[23:33] <ahoneybun> she combined the subpages
[23:33] <ahoneybun> looks good
[23:34] <valorie> main page top: This page contains changes which are not marked for translation.
[23:34] <sgclark> valorie: it is pretty much set, won't change much till new release
[23:35] <valorie> same heading on http://userbase.kde.org/Kubuntu/Installation
[23:35] <sgclark> yeah odd, googling that now
[23:36] <valorie> we need a new image instead of this: http://userbase.kde.org/File:Kubuntu-13.04-installer_2%3D2.png
[23:36] <valorie> and here: http://userbase.kde.org/File:Kubuntu-13.04-DualBoot.png
[23:36] <valorie> and here: http://userbase.kde.org/File:Kubuntu-13.04-installer_4%3D2.png
[23:37] <sgclark> no idea where those from. What do you want images from? 13.10?
[23:37] <valorie> and the last two as well
[23:37] <valorie> we're working on Trusty, so they all need to be 14.04
[23:37] <santa_> yofel: hi, when building kde 4.12, did you have any problem building kalzium?
[23:37] <valorie> those are probably placeholders
[23:37] <sgclark> oh cool, I am installing that on my laptop tonight, will get screenies
[23:37] <valorie> presumably the new slides are available
[23:38] <valorie> no need for that; we can get the originals
[23:38] <sgclark> or slides, where would one get these slides you speak of?
[23:38] <valorie> right, ahoneybun?
[23:38] <yofel> santa_: not that I remember...
[23:39] <valorie> sec
[23:39] <ahoneybun> huh
[23:39] <ahoneybun> sorry got to read
[23:40] <ahoneybun> the installer slides?
[23:42] <sgclark> there is suppose to be a way to "mark page for translation" I do not see it anywhere, perhaps I do not have permissions
[23:42] <santa_> yofel: ok, I guess it's debian specific, I will have to dig deeper into it. thanks
[23:46] <valorie> sgclark: not a whole lotta traffic on the #kde-www chan, but that or the list are the place to ask
[23:46] <sgclark> yeah, will try list if I don't figure it out, never get response in irc
[23:50] <sgclark> ok, only translators can mark page for translation. I only know english lol, anyone have a translator account?
[23:52] <sgclark> if not I can ask yuri to do it
[23:56] <valorie> ovidiu-florin was trying; maybe needs to get a translator account?
[23:56] <sgclark> yeah someone needs to
[23:56] <sgclark> I have no skills to justify one hehe
[23:58] <valorie> me either
[23:59] <valorie> on http://userbase.kde.org/Kubuntu/Software we need to check the canonical list of what will be included on the ISO


[06:20] <mup> Bug #1589140 opened: No WOL option in latest MAAS version for 16.04 also the Manual settings crashes <MAAS:Confirmed> <https://launchpad.net/bugs/1589140>
[06:36] <reikermann> Hi, my MAAS hardware test stress-ng-cpu-long is getting a timed out error after 11:59:26 , but the test definition is a 12h test why is the timeout so short?
[07:53] <mup> Bug #1710092 opened: Hardware Tests have a short timeout  <MAAS:New> <https://launchpad.net/bugs/1710092>
[07:53] <mup> Bug #1710096 opened: [2.2] for non-local network ranges, allow_proxy should be false by default <MAAS:New> <https://launchpad.net/bugs/1710096>
[10:57] <D4RKS1D3> bryan_att, you have the curtin documentation
[10:58] <D4RKS1D3> let me share with you the link
[10:58] <D4RKS1D3> bryan_att, https://media.readthedocs.org/pdf/curtin/latest/curtin.pdf
[13:23] <mup> Bug #1710177 opened: curtin in-target commands do not work for ubuntu core <MAAS:New> <https://launchpad.net/bugs/1710177>
[14:16] <bryan_att> D4RKS1D3: many thanks, just what I was looking for. I'm trying to find out how to circumvent the cloud-init/NIC race condition that resulted in the DEVTIMEOUT option being added, so I can avoid the 5-min hang due to the primary NIC not being ready in time.
[14:17] <bryan_att> e.g. per https://bugzilla.redhat.com/show_bug.cgi?id=1194623 and<EMAIL_ADDRESS>- I think that is what I am encountering.
[15:22] <bryan_att> anyone familiar with how to format the kernel options that MAAS allows: can you tell me if the format at http://cloudinit.readthedocs.io/en/latest/topics/network-config.html for disabling network configuration (network-config={config: disabled}) is correct for use in MAAS?
[15:23] <bryan_att> I am trying to see if disabling the cloud-init network config can help me avoid the NIC ready race condition that causes a 5-min delay in server bootup
[15:32] <mup> Bug #1710241 opened: Cannot deploy customized ubuntu cloud image <MAAS:New> <https://launchpad.net/bugs/1710241>
[15:44] <mup> Bug #1710241 changed: Cannot deploy customized ubuntu cloud image <MAAS:New> <https://launchpad.net/bugs/1710241>
[15:48] <mup> Bug #1710241 opened: Cannot deploy customized ubuntu cloud image <MAAS:New> <https://launchpad.net/bugs/1710241>
[16:56] <maticue> hi everyone! one question, if I add a new Bare Metal to my network and I boot it at first time with PXE, MAAS will discover it. My question is, at that stage is it possible to execute directly the commissioning stage automatically?
[17:00] <maticue> I'm trying to identify automatically IPMI
[17:00] <maticue> for each bare metal
[19:42] <mup> Bug #1710278 opened: [2.3a1] named stuck on reload, DNS broken <MAAS:New> <https://launchpad.net/bugs/1710278>
[20:06] <blizzow> I have three machines that maas has enlisted.  I changed the hostnames/entered their IPMI information and selected all of them to be commissioned.  They all show the RAM and CPU core after being commissioned, but there are no disks detected. What do I have to do to get the disks detected and do a deployment?


[17:19] <nagyz> hi guys
[17:20] <nagyz> I've just upgraded to rc2 and somehow PXE boot stopped working.. I see in the logs that the machine gets a DHCP address but nothing further happens (either in the logs on or at the machine's pxe bootloader)
[17:20] <nagyz> where could I debug this further? I guess it could be stuck doing the tftp transfer...
[17:28] <nagyz> after the upgrade this seems completely broken for me now :(
[18:56] <nagyz> a bit of a dead channel, eh?