[00:38] <Darkwing> jjesse: ping
[00:54] <yottabit> anyone here live in the southeast US?
[01:39] <jjesse> Darkwing,  pong
[01:40] <Darkwing> jjesse: Rats, you caught me on my way to dinner.
[01:40] <jjesse> no worries i'll be here most of the night ;)
[01:40] <Darkwing> jjesse: I want to sit down and talk about the docs.
[01:40] <jjesse> figured :)
[01:41] <Darkwing> :D
[01:41] <jjesse> i'll be here to 10:30 EST or so 
[01:41] <jjesse> if you want to eat dinner :)
[01:42] <Darkwing> Yeah, wife is yelling.. BBL
[08:31] <fabo> Riddell: https://launchpad.net/~fboudra/+archive/qt/+sourcepub/2170022/+listing-archive-extra
[08:49] <agateau> bambee: hi, thanks a lot for the phonon gst fix!
[08:49] <bambee> yw ;)
[08:52] <bambee> agateau: however a qgraphicsview does not help, because xoverlays (like gl or xv) does not work with a qgraphicsview (I don't understand why..), so the actual renderer is software :(
[08:53] <agateau> bambee: ok :/
[08:53] <apachelogger> cuz xv is crap(tm)
[08:53] <agateau> bambee: that's not too bad, gwenview is not intended to be the default video player of choice anyway
[08:55] <bambee> I know, but all scaling and colorspaces tasks are done on the cpu, I don't like that!
[08:56] <apachelogger> nah, the worst thing is that software rendering always leads to quality loss WRT resolution *and* color
[08:57] <apachelogger> which in turn has bad impact on the overall impression of polish in the kde workspace :S
[08:57] <bambee> :s
[09:41] <fregl> fabo: Riddell: hi, I did a rebase of the a11y repo last week but didn't clean it up yet. I have a few conflicts to sort out. I can finish it and push if you want.
[09:43] <Riddell> fregl: or just give us a patch :)
[09:43] <fregl> Riddell: I'd rather have the proper repo with a patch collection. then getting the diff for all changes is still easy
[09:44] <fregl> rebasing still seems nicer to me than just maintaining a diff
[09:44] <Riddell> yes you're right, it is nicer
[09:44] <Riddell> for people who know how to use git :)
[09:44] <Riddell> but I'm sure fabo does
[09:45] <fabo> I'll take whatever makes my life easier :)
[09:46] <fregl> well, producing the patch from git is easy - and this made it convenient to go from Qt 4.8 to 4.7 back in the days - so it seems a good idea
[09:47] <fabo> fregl: 21:52 < fabo> the diff between v4.8.0 and 4.8-a11y branch is ~210Mb
[09:47] <fregl> fabo: yes, give me a bit and it will be a couple lines...
[09:49] <fabo> indeed it isn't only a11y changes but it requires some work to reduce the patch to ~130kb
[09:49] <fabo> fregl: thanks! poke when you finished
[09:49] <fregl> sure
[09:49] <fregl> seems as good as anything on a monday morning :p
[10:00] <fabo> Riddell: what's the story about kubuntu active? 0% of 7 :)
[10:00] <fabo> anything I could look at?
[10:02] <Riddell> fabo: work out how to package plasma active would be the place to start
[10:02] <Riddell> it might need patches to kdelibs or elsewhere
[10:03] <Riddell> rbelem may know more but probably you just need to ask in #plasma
[10:07] <fabo> Riddell: ok
[10:25] <afiestas> agateau: ping
[10:37] <fregl> fabo: I pushed a new version to http://qt.gitorious.org/+qt-developers/qt/accessibility branch name: 4.8-a11y-rebased-onto-828771056e96cd47d3eaf93db1b3d28c8624b332
[10:38] <fregl> fabo: let me know if you run into issues
[10:38] <fabo> ok
[11:27] <agateau> afiestas: pong
[11:28] <afiestas> agateau: this holidays we bought a new camera to my parents and I decided to try the download feature (to make it easier for them) and I think I have a good idea to improve the experience
[11:28] <afiestas> do you know about media-device-info project ?
[11:28] <agateau> afiestas: no
[11:29] <afiestas> basically it is a set of UDEV rules that indicate where the pictures/videos/mp3 are within the device folder structure
[11:29] <agateau> ohoh cool!
[11:29] <afiestas> in the case of my parents camera is something within DCIM/1000SDHC/something/
[11:29]  * agateau wants
[11:29] <afiestas> you got it then :p
[11:30] <agateau> but then some camera change dirs from time to time :/
[11:30] <agateau> how does it cope with that?
[11:30] <afiestas> mmm don't think so
[11:30] <agateau> can it return multiple dirs
[11:30] <agateau> ?
[11:30] <afiestas> the project iself is thought for media players I think
[11:30] <afiestas> meda-players-info is the project, but then gphoto should add the specific UDEV rules for cameras
[11:31] <afiestas> iirc
[11:31] <agateau> do you have an url to get started on that?
[11:31] <afiestas> I always forget how exactly this work :$ iirc mpi is for everything BUT camera-only devices and then you have gphoto 
[11:31] <afiestas> yes, 1 sec
[11:32] <afiestas> agateau: http://www.freedesktop.org/wiki/Software/media-player-info
[11:33] <afiestas> agateau: iirc libsolid should give you the .fdi name and then you can read it
[11:33] <afiestas> I'm planning to work on this during this week to be sure that 4.8 is ready
[11:34] <agateau> afiestas: you mean work on libsolid to provide that info?
[11:35] <afiestas> agateau: yes, I have to check what we can provide I'm not sure where the line is (we can't couple libsolid with linux or any system) and since kdelibs is in freeze we can't provide new interfaces
[11:35]  * jussi loves seeing this kind of collaboration :D
[11:35] <agateau> afiestas: I see
[11:36] <afiestas> the idea is, libsolid tells to gwenview: "Hey! this is a gphoto device !" then you se libgphoto to do the rest
[11:36] <afiestas> "Hey! this is mpi device!" then you read the .fdi files (.desktop like files provided in the mpi project)
[11:37] <agateau> afiestas: I have a bunch of mpi files in /usr/share/media-player-info here, but they do not seem to contain any DCIM folder
[11:37] <agateau> :/
[11:38] <afiestas> :/ they are only for phones and media players aparently
[11:38] <afiestas> gphoto should give you the info for cameras 
[11:38] <afiestas> anyway, having gwenview supporting better all the devices in m-p-i would be awesome :p
[11:38] <agateau> afiestas: agreed
[11:38] <afiestas> and having some kind of scan would be awesome too, to be sure that nothing is ignored
[11:40] <agateau> afiestas: I always photo libgphoto was about PTP devices, not mass-storage ones
[11:41] <afiestas> agateau: then this is something we may want to add m-p-i, the developer is quite friendly
[11:41] <afiestas> and he is a college of yours, from ubuntu iirc
[11:42] <agateau> afiestas: now I am confused. Didn't you start the conversation by telling me there was a way to get the camera picture dirs?
[11:42] <afiestas> agateau: I thought m-p-i did that but apparently it is only for media players 
[11:42] <afiestas> :/
[11:43] <agateau> afiestas: ah ok
[11:43] <agateau> afiestas: my other idea was to keep the latest photo dir for each device in the config
[11:43] <agateau> afiestas: so that next time you plug the same device, it goes automatically in the photo dir
[11:44] <afiestas> wouldn't be better to abstract gwenview from the "dir concept" ? is it really needed? 
[11:44] <agateau> afiestas: not as magical, but better than today situation I would say
[11:44] <agateau> afiestas: gwenview is a file-based picture viewer (at least for now)
[11:44] <afiestas> only for the download I mean
[11:44] <agateau> afiestas: ah yes
[11:45] <afiestas> I'm imaging somethign like: (workflow for my parents)
[11:45] <agateau> afiestas: I considered recursively going trough the device,
[11:45] <agateau> afiestas: problem is when you plug an external hard drive :/
[11:45] <afiestas> I plug the camera into the laptop, the notifier ask me if I want to download the pics to gwenview
[11:46] <afiestas> I click on it, and gwenview starts to scan my device, after it it offers me a list og pics and videos, I select them and click on import 
[11:46] <afiestas> btw, if the device notifier says "Download" the interface should say download too
[11:46] <afiestas> right now interface says import (this confused me, not my parents xD)
[11:48] <agateau> afiestas: agreed
[11:50] <afiestas> and about the m-p-i project, maybe you can talk with the developer and offer hiim to add Camera's info
[11:50] <afiestas> at the end, they are mass storage just like mp3, phones etc
[11:50] <afiestas> and capable to reproduce mp3 and the like formats
[11:51] <agateau> indeed
[11:52] <agateau> so you say he is a colleague of mine?
[11:52] <agateau> oh it's pitty
[11:52] <agateau> he is currently sitting 6 meters on my left :)
[11:53] <agateau> talking to him should be doable :)
[11:56] <afiestas> xD
[12:04] <agateau> lunch time!
[14:22] <bambee> 1)° open qt designer, 2)° create a mainwindow, 3)° Try to add any widget to this windows --> does it work for you ? I cannot add anything to the window :\
[14:22] <bambee> wtf
[14:22] <bambee> (on precise)
[14:24] <bambee> and now it works again... xD
[14:24]  * bambee needs a coffee...
[14:25] <Riddell> :)
[14:26] <mikecb_> keeping you on your toes
[14:58] <mikecb_> anyone working on a ubuntu one qt frontend?
[14:59] <ScottK> I think the unity-qt people might be.
[15:00] <mikecb_> interesting
[15:02] <Riddell> mikecb_: the default frontend will by pyqt soon I believe
[15:03] <mikecb_> is that 12.04 or +2?
[15:07] <Riddell> dunno you'd need to ask them
[15:07] <mikecb_> kk
[15:07] <Riddell> and report back :)  they didn't know last time I asked
[15:20] <fabo> Riddell: a11y patch commited and up-to-date. just need to build it, update symbols, and we're good to go with Qt 4.8
[15:20] <fabo> fregl: thanks, ^^^
[15:20] <Riddell> awooga, saves me forward porting this patch needed by libreoffice 
[15:24] <fregl> fabo: great :)
[15:25] <Riddell> rdieter: thanks for the strigi tars
[15:31] <rdieter> Riddell: np
[15:32] <ScottK> Riddell: barry's going to work on packaging PyKDE4 for Python3.
[15:33] <ScottK> It turns out that /usr/lib/kde4/kpythonpluginfactory.so won't be a problem since for Ptyhon3 it'd be kpythonpluginfactory.cpython-32mu.so
[15:41] <Riddell> ScottK: nice
[15:54] <fabo> Riddell: which tarball are you talking about?
[15:55] <fabo> last tag is 0.7.7, it has been uploaded to debian some time ago.
[15:56] <fabo> afaik, you just need to sync
[16:00] <Riddell> fabo: rdieter just posted that he could not find any tars so made some
[16:03] <fabo> ah yeah, I created them myself using their release script
[16:09] <PaulW2U> #freenode
[16:19] <ewoerner> hey :-)
[16:19] <ewoerner> who should i convince to package a newer version of plasma-widget-networkmanagement?
[16:19] <ewoerner> "Plasma Shell Crashed after Resuming from Suspend to RAM" is creating lots of upstream duplicates from precise users
[16:23] <debfx> fabo: ^ is your networkmanagement package ready?
[16:24] <Riddell> I'm just about to look at that actually
[16:29] <fabo> debfx: what do you mean by ready? I provided the last nm09 release and there's at least 1 known issue
[16:30] <Riddell> fabo: what's the issue?
[16:30] <fabo> Riddell: visual regression on the buttons
[16:31] <Riddell> let me try.  the buttons are pretty screwed up in the version in oneiric anyway
[16:31] <fabo> http://www.dodaj.rs/f/21/RR/3irNejQ2/snapshot2.png
[16:32] <fabo> the same nm doesn't have this issue with KDE 4.7.4
[16:32] <Riddell> that's what I have with KDE 4.7.97 and nm 0.9~svngit.nm09.20111023.ff842e-0ubuntu1~oneiric1~ppa1
[16:33] <schnelle_> Riddell, fabo: I opened bugreport about this: https://bugs.kde.org/show_bug.cgi?id=290964
[16:34] <schnelle_> the worst is that lamirque is not aware of this because he is still using 4.7.4 (where this problem doesn't exist)
[16:34] <schnelle_> "when I upgrade to 4.8 I will try to fix this. I do not even use that version of Plasma NM regularly anymore :-/
[16:34] <schnelle_> I just use the master branch version."
[16:34] <schnelle_> this told me lamarque 2 days ago
[16:36] <debfx> yeah our current nm widget has the same bug so that's not a blocker for the new version
[16:36] <fabo> agree
[16:36] <Riddell> version from fabo's PPA works and has no extra issues with my 3G modem
[16:36] <Riddell> I'll check over the packaging and upload
[16:36] <fabo> :)
[16:42] <Riddell> ewoerner: look out for updates arriving in an hour or two
[16:43] <jussi>  Sari is just taking a quick shower, then we will be off soon to the hospital :) :D :D
[16:43] <ewoerner> great, thanks
[16:43]  * jussi runs
[16:44] <Riddell> jussi: good luck!
[17:00] <Riddell> fabo: hmm networkmanagement  compiled fine but failed to upload
[17:00] <fabo> Riddell: just seen
[17:01] <fabo> interesting, because --compare-versions is fine
[17:02] <fabo> and no warning on upgrade
[17:02] <ScottK> Riddell: missing epoch.
[17:04] <Riddell> ScottK: network-manager-kde has -v'1:0.9~rc3-0ubuntu1'
[17:05] <Riddell> and plasma-widget-networkmanagement shouldn't need it
[17:05] <fabo> 0.9*.0*
[17:06] <fabo> I missed debian/rules as I didn't touched it
[17:06] <fabo> 0.9.0~rc3 > 0.9~svngit
[17:07] <Riddell> fabo: so sed 's/^[[:digit:].]\+/1:0.9.0/' ?
[17:07] <Riddell> in debian/rules?
[17:10] <Riddell> dpkg says yes, yes loading
[17:14] <fabo> yes
[17:19] <Riddell> I need to go out in a bit, if there is a tech board (keep an eye on https://wiki.ubuntu.com/TechnicalBoardAgenda and #ubuntu-meeting) in 3.5 hours please text message me
[17:19] <Riddell> jriddell.org/contact.html
[17:44] <Quintasan_> yofel, Call to lnusertemp failed( temporary directories full?). Check your installation. Ring any bells? Got this after upgrade. 
[17:45] <Quintasan_> bleh
[17:45] <Quintasan_> nvm
[19:06] <ScottK> yofel_: Would you be up for updated KDE l10n for oneiric-proposed?  I'm going to prepare the actual packages for upload based on the PPA and I'd like to get the translation updates in too.  If so, please close Bug #913928  in changelog.
[19:21] <Darkwing> charlie-tca: pign
[19:21] <Darkwing> *ping
[19:22] <charlie-tca> yes?
[19:22]  * yottabit wonders..
[19:22] <Darkwing> charlie-tca: care for a PM?
[19:22] <charlie-tca> sure
[19:23] <yottabit> is it legal to sell kubuntu and offer support, etc. without being canonical...
[19:23] <ScottK> yottabit: As long as you comply with the trademark policy, yes.
[19:23] <yottabit> nice
[19:23] <yottabit> i'm thinking about doing that after google summer of code to have some money
[19:24] <ScottK> (which is somewhere on Canonical's web site (or maybe ubuntu.com).
[19:25] <yottabit> http://www.canonical.com/partners/reseller
[19:27] <ScottK> http://www.ubuntu.com/aboutus/trademarkpolicy
[19:27] <ScottK> It's free software so you don't have to be an official reseller.
[19:53] <Riddell> ScottK: kubuntu lts seems to have been added to the tech board agenda, with your name
[19:53] <ScottK> I added it since they were discussing all the others.
[19:54] <ScottK> IIRC Kubuntu LTS is a precursor to Edubuntu LTS, so it kind of has to get discussed.
[19:54] <ScottK> I also assumed based on your comment you wanted it discussed.
[19:54] <Riddell> well you'd think so but I was naievely following the tech board's instructions and assuming they would add it
[19:54] <Riddell> yes I do
[19:55] <Riddell> I guess the main things to be questioned are will upstream care about KDE after KDE Frameworks 5 is out
[19:56] <Riddell> and KDE will do the same for 4.8 as they do for every other release
[19:56] <Riddell> which is better than gnome do as far as I can see
[19:56] <Riddell> will Qt care about Qt 4 after Qt 5 is out
[19:56] <Riddell> which is much the same
[19:56] <Riddell> and will QtWebkit be a security risk
[19:57] <Riddell> which is arguable but it's the same general upstream policy as firefox
[19:57] <ScottK> Unless they want to kick it out of Main, it kind of already is, LTS for Kubuntu or not.
[19:57] <Riddell> right it's in ubuntu desktop anyway so it's not really a question
[19:57] <Riddell> I think things can be in main but not 5 year LTS
[19:57] <ScottK> Makes sense.
[20:57] <ScottK> Riddell: Looks like TB is happening.
[20:58] <Riddell> or at least pitti joined the channel :)
[20:58] <ScottK> mdz is rounding people up in #u-devel.
[20:59] <Darkwing> I'll be lurking
[21:20] <Riddell> I wonder how this applies to us "What kind of SRU throughput do you have at the moment?"
[21:20] <Riddell> besides "loads when ScottK does the point releases"
[21:20] <ScottK> That's not insignificant.
[21:20] <ScottK> It also reduces the drive for indiviual SRUs.
[21:20] <ScottK> There have been some though.
[21:21] <Riddell> I'm working on one just now for qt infact
[21:22] <yofel_> it also helps with CVE patches on code that might have changed between .1 and .4/5, as one would need to port that first for the SRU
[21:22] <yofel> ScottK: I'll do l10n in a bit
[21:22] <ScottK> yofel: Thanks.
[21:26] <charlie-tca> You are welcome for the heads up on what to expect now :)
[21:30] <charlie-tca> Xubuntu got approval, Kubuntu should be a simple one.
[21:30] <Riddell> charlie-tca: ah but we're asking for 5 years not 3, and there's a lot more packages different in our seeds :)
[21:31] <charlie-tca> Yeah, but you are pretty much equal to Ubuntu, too.
[21:31]  * yofel is mostly worried about kees and qtwebkit...
[21:31] <charlie-tca> Kubuntu has always had LTS designation, too
[21:31] <Riddell> no we missed one for the kde 4 transition
[21:32] <charlie-tca> Xubuntu never had any officially, we just supported the release for the full time
[21:32] <Riddell> yofel: jdstrand is the guy to be scared about I expect :)
[21:33] <yofel> ~.~
[21:37] <Riddell> ScottK: do you want to introduce or shall I?
[21:37] <ScottK> Riddell: Go for it.
[21:38] <ScottK> I started based on mdz changing /topic.
[21:47]  * fabo don't expect API/ABI changes for QtWebKit 2.x anyway
[21:52] <Darkwing> Ubuntu sure made it simpler by adopting Qt anyway 
[21:52] <Riddell> see you in 2017 :)
[21:52] <Darkwing> lol
[21:53] <yofel> party time \o/
[21:53] <ScottK> micahg: It's in Main ...
[21:53] <fabo> the only problem is if microsoft buys Nokia :)
[21:53] <Darkwing> not that it'll matter with the world ending in december
[21:53] <Darkwing> :P
[21:53]  * ScottK runs to the airport ...
[21:53] <ScottK> Have fun everyone.
[21:53] <fabo> bye ScottK 
[21:55] <Riddell> fabo: they're only interested in the high end nokia bits, the super secret nokia low end stuff is where qt is at
[21:56] <micahg> ScottK: indeed, but it still needs someone to support it
[21:56] <Riddell> anyone wanting to do new calligra beta or is that my task for tomorrow?
[21:56] <Darkwing> Riddell: building or testing?
[21:57] <Riddell> Darkwing: packaging then testing, probably twice
[21:57] <Riddell> of course I can set up an ec2 to help you :)
[21:58] <CIA-48> [lp:~kubuntu-packagers/kubuntu-packaging/kde-l10n-common-oneiric-release] Philip Muškovac * 115 * debian/changelog 4.7.4 oneiric-proposed
[21:58] <fabo> Riddell: do you really think if that happens, they'll keep qt/qtwebkit for meltemi :) I doubt it
[21:58] <CIA-48> [lp:~kubuntu-packagers/kubuntu-packaging/kde-l10n-common-oneiric-release] Philip Muškovac * 116 * debian/changelog refresh date
[21:59] <debfx> micahg: how do you plan to support webkitgtk? qtwebkit upstream said it's impossible to backport webkit fixes after a few months
[21:59] <Riddell> fabo: they'll keep it for the super secret OS they're working on.  meltemi is a mystery to everyone
[22:00] <micahg> debfx: I plan on getting people to help me maintain a stable branch, it's work, but possible (a lot of work, but seems there's no way around it)
[22:01] <CIA-48> [lp:~kubuntu-packagers/kubuntu-packaging/kde-l10n-common-oneiric-release] Philip Muškovac * 117 * debian/config fix branch link
[22:01] <micahg> I was wondering if the directory structure is similar enough that if you were on the same base revision of webkit as webkitgtk if you'd be able to use the patches from there
[22:02] <fabo> we can expect also a slow down in changes on webkit1 as a lot of teams are focusing on webkit2
[22:02] <micahg> right
[22:03] <micahg> that's the main impetus to create a stable branch as opposed to migrating to newer versions as webkitgtk for the most part has been API stable
[22:06] <Riddell> upstream say they'd be happy to see a 4.8 updates branch for qtwebkit but indeed it would take work
[22:12] <debfx> micahg: maybe that will be possible in the future if there is some coordination between qtwebkit and webkitgtk
[22:13] <debfx> but not for qtwebkit 2.2 as they pretty much stopped following trunk around august
[22:14] <micahg> indeed, I'd much prefer if there were a libwebkit that both wrapped around
[22:20] <Riddell> I think that would take alot more coordination by webkit teams than they are willing to do