[06:56] <jussi> yay, just got telepathy to crash, and my kwallet wont open. great morning coming up I can see... :/
[07:00] <jussi> there you are shadeslayer https://bugs.kde.org/show_bug.cgi?id=315429 - some fun for your morning
[07:01] <kubotu> ::qt-bugs:: [1129856] package libqtcore4 4:4.8.3+dfsg-0ubuntu3.1 failed to install/upgrade: trying to overwrite ... @ https://bugs.launchpad.net/bugs/1129856 (by Tom Plank)
[07:47] <jussi> right, had to delete the wallet and start again. annoying...
[07:52] <jussi> you are all boring today
[07:52] <jussi> :D
[08:04] <smartboyhw> Hey apachelogger shadeslayer and Riddell
[08:06] <smartboyhw> Hello to yofel too
[08:08] <yofel__> hey
[08:08] <yofel__> and hi jussi, shadeslayer should be awake soonish I guess ^^
[08:12] <jussi> heya yofel__, yeah, was being impatient
[08:15] <yofel__> smartboyhw: is callgra up yet?
[08:15] <yofel__> *calligra
[08:16] <murthy> hello everyone
[08:16] <yofel__> hi murthy
[08:16] <murthy> yofel__: hi
[08:16] <murthy> its nice to see some posts from Riddell
[08:17] <murthy> yofel__: calligra being packaged?
[08:17] <smartboyhw> yofel, NO
[08:17] <smartboyhw> Not yet
[08:17] <murthy> smartboyhw: ok
[08:18]  * smartboyhw needs to update the install files... (still building to see which files are missing and which files aren't)
[08:20] <smartboyhw> murthy, yofel is plasmate up?
[08:20] <murthy> smartboyhw: dont know
[08:21] <murthy> smartboyhw: who is packaging?
[08:24] <murthy> yofel__: have you tried vivaldi?
[08:31] <murthy> is there some kind of cpu throttler app for linux?
[08:48] <smartboyhw> murthy, shadeslayer
[08:48] <smartboyhw> My copyright fix is merged so wondering about it
[08:49] <smartboyhw> Jesus using 4-core to build is dead fast
[08:49] <smartboyhw> It's 54% now!!!
[08:49] <murthy> smartboyhw: which one?
[08:50] <smartboyhw> murthy, first two sentences for plasmate, last two for calligra
[08:50] <murthy> nice
[08:52] <sheytan> apachelogger: it looks OK :*
[08:53] <jussi> hrm
[08:53] <jussi> has anyone tried qupzilla ?
[08:59] <murthy> libkdeui5 doesn't have debugging symbols?
[09:01] <murthy> Riddell: I can't find a package for installing debugging symbols for libkdeui5 .  The debug package installer  reports it couldn't find a package
[09:07] <agateau> murthy: I think dbg package is kdelibs5-dbg
[09:08] <murthy> agateau: ok
[09:10] <Riddell> hi smartboyhw, where did you get to with calligra?
[09:12] <smartboyhw> Riddell, trying to see the dh_install --list-missing and the not-installed ones:P
[09:15] <Riddell> smartboyhw: it's just the krita colour profiles isn't it?
[09:15] <Riddell> shadeslayer: "ok" on http://kubuntu-qa.dyndns.org/  ok is good :)
[09:16] <smartboyhw> Riddell, don'
[09:16] <smartboyhw> don't know
[09:16] <smartboyhw> Riddell, that kubuntu-qa site is extremely good. Thanks shadeslayer
[09:17] <smartboyhw> Riddell, as it turns out using -j4 is even better (on my machine so no need for ec2s in Raring (may need for precise though)
[09:18] <smartboyhw> Riddell, you know what is going on for the tablet annoucement?
[09:18] <Riddell> smartboyhw: what tablet announcement?
[09:18] <smartboyhw> Riddell, in ubuntu.com
[09:18] <smartboyhw> there's a tablet thing coming in 6:42 hours
[09:18] <Riddell> oh no idea, presumably they're launching a tablet
[09:19]  * smartboyhw is anxious at the --list-missing things.
[09:20] <Riddell> smartboyhw: why anxious?
[09:22] <smartboyhw> Riddell, to tell me what to fix:P
[09:22] <smartboyhw> Riddell, is there a way to submit packages into Debian using Ubuntu? (Another package that I am helping a *friend* on)
[09:23] <Riddell> smartboyhw: file a bug in debian
[09:23] <smartboyhw> Riddell, ok
[09:25] <Riddell> jussi: what's qupzilla?
[09:26] <jussi> Riddell: its a Qt web browser
[09:26] <jussi> http://www.qupzilla.com/
[09:27] <jussi> No idea how it compares with rekonq, but interested to see how it goes
[09:27] <murthy> https://bugs.launchpad.net/ubuntu/+bug/1129977
[09:32] <murthy> how can i search the availability of a specific version of a package in debian unstable ?
[09:33] <Riddell> murthy: packages.debian.org
[09:34] <Riddell> lots of kde things to be packaged on https://blueprints.launchpad.net/ubuntu/+spec/desktop-r-kubuntu-packaging
[09:34] <jussi> Riddell: could be interesting to get qupzilla in the repos also
[09:34] <smartboyhw> Riddell, gee
[09:35] <smartboyhw> Wait a minute: Does it said [kubuntu-dev] package calligra 2.6 with lcms 2.4 ?
[09:35] <Riddell> that's what it says
[09:35] <smartboyhw> Riddell, what's lcms?
[09:36] <oy> little Color Management System
[09:36] <Riddell> looks like it has lcms in its build-depends
[09:36] <murthy> Riddell: i am in the website, but  is there a way i can search for a package, for example libdlna
[09:36] <Riddell> murthy: well yes, search on packages.debian.org
[09:37] <Riddell> http://packages.debian.org/search?searchon=sourcenames&keywords=libdlna
[09:37] <Riddell> https://www.google.co.uk/search?q=site%3Abugs.debian.org+libdlna
[09:37] <murthy> Riddell: no results? what does that mean?
[09:38] <smartboyhw> Riddell, so I see the files in dh_install --list-missing, and I add it back to the .install files?
[09:38] <Riddell> murthy: its means that package is not in debian
[09:38] <Riddell> smartboyhw: yes
[09:39] <Riddell> smartboyhw: it's not a case of "add it back" since they're new files, they've never been in there
[09:39] <murthy> Riddell: ok
[09:39] <smartboyhw> Riddell, oh... not *back*:P
[09:44] <shadeslayer> hey
[09:44] <shadeslayer> jussi: that crash looks familiar
[09:44] <jussi> shadeslayer: yeah, shaddup
[09:44] <jussi> :D
[09:44] <shadeslayer> did you not upgrade to 0.5.2
[09:44] <murthy> Riddell: we need privileges to assign importance field in bug reports?
[09:44] <jussi> shadeslayer: Im on whatever kubuntu backports has...
[09:45] <shadeslayer> eh
[09:46] <jussi> shadeslayer: I got a new machine, everything is a clean install. added the auth deb you gave me only (and kubuntu backports ppa)
[09:46] <shadeslayer> aha
[09:46] <smartboyhw> Hey shadeslayer when will plasmate be in?
[09:46] <shadeslayer> did you install the 0.5.2 one or the 0.5.1 one?
[09:46] <shadeslayer> smartboyhw: it had licensing issues
[09:46] <smartboyhw> shadeslayer, oh.......
[09:46] <shadeslayer> Quintasan:  did some work on it I think
[09:47] <shadeslayer> not sure if Riddell uploaded it
[09:47] <jussi> shadeslayer: installed: http://people.ubuntu.com/~rohangarg/kde-telepathy-auth-handler_0.5.1-0ubuntu2~ppa1_amd64.deb
[09:47] <shadeslayer> spent my entire day learning about auto-upgrade-tester :P
[09:47] <shadeslayer> jussi: okay
[09:47] <shadeslayer> hmm
[09:47] <jussi> shadeslayer: its a dupe in anycase, from the previously fixed one
[09:48] <shadeslayer> yeah
[09:49] <murthy> yofel__: I have registered a bug report requesting for packaging libdlna and i have assigned it to myself. The sponsor request documentation is not clear, i need your help  for further steps. Where should i mention the launchpad bug id in the changelog?
[09:54]  * apachelogger looks at shadeslayer
[09:55]  * apachelogger also looks at sheytan
[09:55]  * shadeslayer drops dead
[09:55]  * apachelogger wonders whether shadeslayer has already rewritten plymouth in qml
[09:55] <smartboyhw> Riddell, if something is located in the folder ./obj-x86_64-linux-gnu I should put it in calligra-dev or?
[09:55]  * shadeslayer wonders if apachelogger has fixed the ATI drivers
[09:56] <apachelogger> yofel__: the point would not be to have a backend for plymouth but rewrite plymouth
[09:56] <apachelogger> shadeslayer: someting wrong with them?
[09:56] <shadeslayer> broken for me
[09:57] <apachelogger> *shrug*
[09:57] <shadeslayer> something about the V_BIOS signature being invalid ( I think that means that my card isn't supported )
[09:57] <apachelogger> yah
[09:57] <apachelogger> and here I thought the free magic support everything
[09:57] <apachelogger> fail
[09:58] <apachelogger> shadeslayer: piiiiiiiiiiiiiiing
[09:58] <shadeslayer> whut
[09:59] <apachelogger> shadeslayer: I have an akonadi-facebook build fail in my inbox again :(
[09:59] <apachelogger> sheytan: piiiiiiiiiiiiiiing
[10:00] <shadeslayer> apachelogger: yeah, I can't help that, it needs KDE 4.10 and all the Blue Shell repos are meant to be standalone
[10:00] <shadeslayer> might just disable it
[10:02] <apachelogger> ohm
[10:02]  * apachelogger is alwasy surpsrised when software need latest and greates kde :P
[10:02] <jussi> apachelogger: your opinion on qupzilla would be appreciated...
[10:03] <apachelogger> sounds like something that has nothing to do with prn
[10:03] <apachelogger> jussi: what sort of opinion are you looking for?
[10:03] <sheytan> apachelogger: what? what? :D
[10:04] <apachelogger> sheytan: we need more artwork
[10:04] <jussi> apachelogger: it has lots to do with prn, its a web browser :P
[10:05] <apachelogger> sheytan: so, there is this UI mode which we use on 16bit drivers/setups, probelm is on 16bit you cannot have an alpha channel, so transparency is not possible, meaning we need a different approach of progress indication
[10:06] <apachelogger> well, not completely different but for example something like ... instad of glowing we draw a border around it
[10:06] <sheytan> when i get home. am @ work now ;)
[10:06] <apachelogger> justan example though
[10:06] <apachelogger> k
[10:07] <apachelogger> jussi: same thing as aurora
[10:07] <apachelogger> same thing as rekonq
[10:07] <apachelogger> well, rekonq has KDE bits, so not exactly the same thing... same web tech though
[10:07] <jussi> apachelogger: POS? :D
[10:08] <apachelogger> there is none
[10:08] <apachelogger> it's a different UI on the same qtwebkit
[10:17] <shadeslayer> more or less, yes
[10:19]  * shadeslayer tries to figure out how to add PPA's before upgrade
[10:19] <sheytan> apachelogger: you ofcourse mean the plymouth?
[10:19] <apachelogger> sheytan: yes?
[10:20] <sheytan> ok
[10:20] <Riddell> smartboyhw: hmm?  ./obj-x86_64-linux-gnu is where the compile happens, everthing for install gets installed to debian/tmp/
[10:21] <sheytan> sorry, we've got guessts from Turkey at my job, they're going to have practice here so i'm a bit busy today
[10:21] <smartboyhw> Riddell, that's the problem. I'm close to getting the dh_install thing done, I just don't know where they should be put (which .install file)
[10:21] <Riddell> smartboyhw: goes a list of files?
[10:21] <Riddell> smartboyhw: got a list of files?
[10:21] <apachelogger> sheytan: sure, no worries
[10:22] <smartboyhw> Riddell, wait I'm getting it. Shouldn't be more than 3-4 now
[10:22] <apachelogger> sheytan: http://wstaw.org/m/2013/02/18/plasma-desktopRH2164.png -> http://wstaw.org/m/2013/02/18/plasma-desktopjw2164.png -> http://wstaw.org/m/2013/02/18/plasma-desktopLJ2164.png
[10:22] <smartboyhw> dh_install: usr/bin/visualimagecompare exists in debian/tmp but is not installed to anywhere
[10:22] <murthy> we need privileges to assign importance field in bug reports?
[10:22] <smartboyhw> dh_install: usr/bin/cstrunner exists in debian/tmp but is not installed to anywhere
[10:22] <smartboyhw> dh_install: usr/bin/cstester exists in debian/tmp but is not installed to anywhere
[10:22] <smartboyhw> dh_install: usr/share/kde4/apps/formulashape/fonts/cmex10.ttf exists in debian/tmp but is not installed to anywhere
[10:22] <smartboyhw> Riddell, ^
[10:22] <smartboyhw> Last one I'm fixing
[10:22] <smartboyhw> What I DON'T know is the first three
[10:22] <shadeslayer> apachelogger: I don't like the background for plymouth btw
[10:23] <Riddell> smartboyhw: those are all not-installed I think
[10:23] <shadeslayer> makes it look like you have an issue with your monitor
[10:23] <smartboyhw> Riddell, /me is checking
[10:23] <apachelogger> shadeslayer: you are telling the wrong person?
[10:24] <shadeslayer> sheytan: ^^
[10:25] <sheytan> comeon, it doesn't :D
[10:27] <apachelogger> and I thought sheytan's display was crappy and there comes shadeslayer and tells me he has an even crappier display
[10:27] <shadeslayer> hey, I have a beautiful display
[10:27] <apachelogger> boot artwork is anoyting
[10:27] <apachelogger> we should drop the background and make it solid black
[10:27] <shadeslayer> your plymouth background makes it look like it has an isue
[10:27] <shadeslayer> apachelogger: sounds good actually
[10:27] <apachelogger> try it
[10:28] <shadeslayer> give patch
[10:28] <apachelogger> sudo rm /lib/plymouth/themes/kubuntu-logo/images/tile.png && sudo update-initramfs -u
[10:28] <shadeslayer> won't it fail or sth if it can't find the tile?
[10:28] <apachelogger> that may also break the splash entire
[10:28] <apachelogger> muhahaha
[10:28] <shadeslayer> FU
[10:28] <apachelogger> can't tell
[10:28] <shadeslayer> -.-
[10:29] <shadeslayer> anyway, will try in another hour or so because doing something else
[10:29] <apachelogger> plymouth decides how to fall apart depending on the mood of mighty thor or something
[10:30] <apachelogger> though likely it wont break
[10:30] <apachelogger> it still creates the image and sprite etc. but the image has no data so for all intents and purposes the sprites will be 0x0 and the image is 0x0 and therefore you get no background
[10:30] <apachelogger> ^^
[10:32] <smartboyhw> Riddell, how about calligra-l10n?
[10:33] <Riddell> smartboyhw: it looks good
[10:33] <smartboyhw> Riddell, OK then.... calligra should be fine within half hour
[10:34] <smartboyhw> or so...
[10:36] <Riddell> or so :)  calligra always takes longer than you expect just cos its so huge
[10:36] <smartboyhw> Riddell, it takes within a hour for me using -j4 I just forgotten the EXACT time
[10:36] <smartboyhw> I clearly forgotten to use the CPUs when I build 2.6.0 and I now remembered for 2.6.1 which is good news
[10:37] <smartboyhw> s/CPUs/cores and threads/
[10:37] <kubotu> smartboyhw meant: "I clearly forgotten to use the cores and threads when I build 2.6.0 and I now remembered for 2.6.1 which is good news"
[10:42] <shadeslayer> hmm
[10:43] <smartboyhw> shadeslayer, hmm?
[10:43] <shadeslayer> we might have to add some code that introduces PreBootStrap functionality
[10:43] <shadeslayer> from reading the code it seems like there's no way to add a repo before the upgrade
[10:43] <shadeslayer> AddRepo adds the repo post upgrade
[10:43] <shadeslayer> which is useless
[10:44] <shadeslayer> so I used PostBootStrap to add the repo, but then it'll download KDE 4.9 -> upgrade to 4.10 -> upgrade to raring
[10:44] <shadeslayer> that'll take more time as compared to add repo > install 4.10 > upgrade to raring
[10:52] <shadeslayer> but then we get more robust upgrades because that also tests upgrading to 4.10 automagically
[11:17] <yofel__> murthy_: sorry, was busy
[11:18] <yofel__> you need to be a memeber of ~ubuntu-bugcontrol to change the bug importance
[11:18] <yofel__> no, I haven't tried vivaldi. Is it out finally?
[11:18] <yofel__> I don't know of a cpu throtteling app for KDE, I have a shell script for that
[11:23] <shadeslayer> bah stupid pythorn
[11:25] <shadeslayer> yofel__: any ideas how I can get the upgrade tester to automatically substitute variables I put into the cfg files?
[11:25] <shadeslayer> For eg : PostBootstrapScript=$(AutoUpgradeTesterSharedDir)/kubuntu_add_backports
[11:25] <shadeslayer> it picks that up literally and doesn't substitute the var
[11:30] <shadeslayer> alternatively, could just hardcode the path
[11:30] <yofel__> shadeslayer: the other variables i see used use %(), not $()
[11:31] <shadeslayer> hm
[11:31]  * shadeslayer tries
[11:31] <yofel__> hm
[11:31] <yofel__> or those are just placeholders for manual substitution
[11:32] <shadeslayer> the simulate backend fails
[11:32] <shadeslayer> InterpolationSyntaxError: bad interpolation variable reference '%(AutoUpgradeTesterSharedDir)/scripts/kubuntu_add_backports'
[11:32] <yofel__> o.O
[11:33] <shadeslayer> aha
[11:33] <shadeslayer> yofel__: works now
[11:33] <shadeslayer> I was missing the 's' after )
[11:34] <yofel__> o.O
[11:34] <yofel__> btw. your qa page has errors
[11:35] <smartboyhw> yofel__, that is a lot of o.0's'
[11:35] <shadeslayer> yeah, I know
[11:35] <shadeslayer> refresh!
[11:35] <Riddell> umm, where did the build log go? https://launchpad.net/~kubuntu-ppa/+archive/experimental/+build/4311804
[11:35] <shadeslayer> hahaha
[11:35] <yofel__> :)
[11:35] <shadeslayer> Riddell: lunchpad ate it
[11:35] <shadeslayer> for lunch
[11:35] <smartboyhw> shadeslayer, LOL
[11:35] <Riddell> grr
[11:36] <shadeslayer> just retry it, build logs disappear randomnly at times
[11:36] <smartboyhw> Grrr really....:P
[11:43] <shadeslayer> hm, someone on windows using freenode webchat is accessing the qa page :P
[11:44] <yofel__> shadeslayer: blame me :P
[11:45] <shadeslayer> hahaha
[11:45] <Riddell> your cover is found out!
[11:45] <yofel__> and here I even set the proper host mask to not be seen :(
[11:45] <shadeslayer> ^^
[11:46] <shadeslayer> yofel__: no access to quasselcore?
[11:46] <shadeslayer> can't even proxy? :P
[11:47] <yofel__> haven't yet found an open port other than 80 to proxy through. Really strict firewall here
[11:47] <shadeslayer> wow
[11:49] <Riddell> 443?
[11:52] <shadeslayer> wtf
[11:52] <shadeslayer> bash: /home/shadeslayer/auto-upgrade-testing/share/scripts/kubuntu_add_backports: No such file or directory
[11:53] <shadeslayer> this thing needs a beating
[11:58] <apachelogger> hm
[11:59] <apachelogger> when do we get wayland?
[11:59] <apachelogger> ^^
[12:01] <shadeslayer> I don't get it
[12:01] <shadeslayer> why is it trying to run using /home/shadeslayer
[12:01] <shadeslayer> http://paste.kde.org/675818/
[12:01] <shadeslayer> code snippet
[12:01] <shadeslayer> yofel__: ^
[12:02] <yofel__> .joi ? (line 8)
[12:03] <shadeslayer> nah, that's fine, I probably accidentally pressed backspace
[12:03] <shadeslayer> it does copy the script
[12:04] <shadeslayer> it's in /upgrade-tester
[12:04] <apachelogger> back to the space
[12:05] <shadeslayer> http://paste.kde.org/675824/
[12:05] <apachelogger> http://wayland.freedesktop.org/xserver.html
[12:05] <apachelogger> omnomnom
[12:06] <shadeslayer> aha
[12:06] <shadeslayer> yofel__: won't 'script' be the full path?
[12:07] <yofel__> what's set as PostBootstrapScript ?
[12:08] <shadeslayer> PostBootstrapScript = %(AutoUpgradeTesterSharedDir)s/scripts/kubuntu_add_backports
[12:08] <shadeslayer> AutoUpgradeTesterSharedDir is /home/shadeslayer/auto-upgrade-testing/share
[12:09] <yofel__> so you want it to run from /upgrade-tester/home/shadeslayer/auto-upgrade-testing/share ?
[12:09] <shadeslayer> no
[12:10] <shadeslayer> I want it to run /upgrade-tester/kubuntu_add_backports
[12:10] <shadeslayer> but I want it to take the script from /home/shadeslayer/auto-upgrade-testing/share/scripts
[12:11] <yofel__> script.split('/') and take the last value?
[12:11] <yofel__> or os.path probably has something for that
[12:11] <shadeslayer> right, so my suspicion was correct
[12:11] <shadeslayer> buggy software
[12:12] <shadeslayer> script_file = script.split('/')[-1]
[12:12] <shadeslayer> does that sound right?
[12:13] <shadeslayer> and what's this :                 print("running script: %s" % os.path.join("/tmp", script_file))
[12:14] <smartboyhw> Riddell, https://code.launchpad.net/~smartboyhw/ubuntu/raring/calligra/packaging-2.6.1/+merge/149257
[12:14] <apachelogger> http://wstaw.org/m/2013/02/19/w.png
[12:14] <smartboyhw> calligra 2.6.1 in it
[12:14] <shadeslayer> 0.o
[12:15] <shadeslayer> apachelogger: nice
[12:15] <shadeslayer> but
[12:15] <shadeslayer> that doesn't look like KDE
[12:15] <shadeslayer> it looks like you know what
[12:15]  * smartboyhw thought shadeslayer is talking about you-know-who (Lord Voldemort):P
[12:18] <apachelogger> shadeslayer: yeah, screw plasma it depends on X :P
[12:18] <shadeslayer> heh
[12:18] <yofel__> shadeslayer: yeah, should work
[12:19] <smartboyhw> Riddell, at least the amd64 build failure buildlog for qtwebkit-source is available:P
[12:19]  * yofel__ goes back to work
[12:20] <smartboyhw> See ya yofel__
[12:32]  * smartboyhw has never seen such silence in this channel.............
[12:47] <apachelogger> http://i.imgur.com/Pe2iCNa.png
[12:47] <apachelogger> xwindows in wayland
[12:47] <apachelogger> :D :D :D
[12:51] <apachelogger> and qt5 wayland qml http://i.imgur.com/3lbrXEy.png
[13:12] <BluesKaj> Hiyas all
[13:12] <smartboyhw> Heyas BluesKaj
[13:13] <BluesKaj> hi smartboyhw
[13:24] <smartboyhw> Riddell, that new build of qtwebkit-source failed too:P
[13:38] <shadeslayer> yofel__: so yeah, modifying it a bit makes it work
[13:38]  * smartboyhw is stilll waiting for Riddell for calligra:P
[13:39] <shadeslayer> oh hmm
[13:39] <shadeslayer> it asks for console setup
[13:39] <shadeslayer> now we have to do debconf seeding :|
[13:51] <shadeslayer> aha
[13:51] <shadeslayer> DEBIAN_FRONTEND='noninteractive'
[14:00] <yofel__> why debconf?
[14:02] <yofel__> smartboyhw: could you please file a merge request for the packaging branch and not the UDD one?
[14:15] <shadeslayer> yofel__: yeah, not needed, I just set the DEBIAN_FRONTEND to noninteractive
[14:22] <shadeslayer> Riddell: I've setup 2 upgrade paths : Kubuntu Quantal to Raring  and Kubuntu Quantal with Backports to Raring
[14:22] <shadeslayer> cronjob will run every Tuesday at 14.30
[14:22] <shadeslayer> so people can come back after lunch and find issues to fix :P
[14:24] <shadeslayer> so, another 7 minutes before it's run
[14:35] <shadeslayer> I simply don't get cron jobs it seems :|
[14:39] <smartboyhw> yofel, sorry
[14:41] <smartboyhw> yofel__, WTF it says my branch is not mergeable into calligra. Probably I need to create another branch then. Please wait.....
[14:51] <smartboyhw> Damn my wifi is suddenly slow
[14:52] <smartboyhw> More accurately, the pushing suddenly is extremely slow
[14:53] <shadeslayer> it's python
[14:53] <shadeslayer> what did you expect
[14:53] <smartboyhw> shadeslayer, you are asking me?
[14:53] <shadeslayer> I'm telling you
[14:54] <smartboyhw> shadeslayer, it normally is fast...........
[14:56]  * smartboyhw is seriously if that was because his father watching online videos in LAN desktop
[15:01] <apachelogger> shadeslayer: it's all very weird
[15:03] <shadeslayer> ?
[15:03] <apachelogger> the testing foo
[15:03] <apachelogger> it says nothing here
[15:05] <shadeslayer> because it's running?
[15:05] <smartboyhw> yofel, or yofel__ https://code.launchpad.net/~smartboyhw/kubuntu-packaging/calligra-2.6.1/+merge/149295
[15:08] <smartboyhw> Dang it has conflicts
[15:08] <smartboyhw> Wait er.....
[15:08]  * smartboyhw deletes the merge
[15:08] <shadeslayer> apachelogger: takes about an hour to upgrade
[15:09] <apachelogger> that page is silly
[15:09] <apachelogger> shadeslayer: btw
[15:09] <apachelogger> shadeslayer: thought about jujuing
[15:09] <apachelogger> ?
[15:09] <shadeslayer> mmm
[15:10] <shadeslayer> I put in too much work :P
[15:10] <shadeslayer> and I know nothing about juj
[15:10] <shadeslayer> *juj
[15:10] <shadeslayer> *juju
[15:21] <smartboyhw> yofel, yofel__ https://code.launchpad.net/~smartboyhw/kubuntu-packaging/calligra-2.6.1-new/+merge/149305 (the correct one)
[15:22] <smartboyhw> Phew that's the good one:P
[15:26] <apachelogger> shadeslayer: learn to type :P
[15:26] <shadeslayer> heh
[15:27] <apachelogger> Riddell: did you ever manage to write an owncloud charm?
[15:27] <murthy> yofel__: yofel__: I have registered a bug report requesting for packaging libdlna and i have assigned it to myself. The sponsor request documentation is not clear, i need your help  for further steps. Where should i mention the launchpad bug id in the changelog?
[15:28] <murthy> yofel__: give me the cpu throttling script
[15:29] <murthy> yofel__: yofel__: I have registered a bug report requesting for packaging libdlna and i have assigned it to myself. The sponsor request documentation is not clear, i need your help  for further steps. Do i have to mention the bug in in the changelog? if so where should i mention the bug id in the changelog?
[15:36] <yofel__> smartboyhw: yep, that's ok now, thanks! I'll review in ~2h if Riddell isn't faster
[15:36] <yofel__> murthy: you would usually have a changelog entry like "New upstream release (LP: #XXXXX)"
[15:37] <smartboyhw> yofel_ LOL
[15:37] <murthy> yofel__: ok
[15:37] <yofel__> murthy: once you have all the information in place you subscribe ubuntu-sponsors and unassign yourself
[15:38] <murthy> yofel__: subscribe? you mean the mailing list?
[15:38] <smartboyhw> murthy, the bug
[15:38] <yofel__> no, the ~ubuntu-sponsors team on launchpad
[15:38] <murthy> yofel__: oh
[15:38] <yofel__> to the bug
[15:39] <murthy> yofel__: i am having doubts the debdiff, the output format is little bit wierd
[15:39] <yofel__> really? It's mostly a standard unified diff
[15:41] <murthy> yofel__: http://paste.kde.org/676094/
[15:41] <murthy> yofel__: thats waht i am getting for "diff filea.dsc fileb.dsc"
[15:41] <yofel__> I said debdiff, not diff. There is an actual "debdiff" program
[15:42] <murthy> yofel__: checking
[15:43] <murthy> yofel__: http://paste.kde.org/676100/
[15:43] <murthy> yofel__: now ok?
[15:47] <yofel__> murthy: much better. Now put the bug number into the changelog as I described above and throw the ~ubuntu13.04~ppa1 part out of the version
[15:48] <murthy> yofel__: ok
[15:48] <yofel__> murthy: in changelog: "Excluded" -> "exclude", we use present tense
[15:48] <murthy> yofel__: ok
[15:49] <apachelogger> Excluded /usr/share/cdbs/1/rules/simple-patchsys.mk for using quilt for patches instead
[15:49] <apachelogger> why?
[15:49] <apachelogger> alas you cannot exclude anything form a makefile
[15:50] <apachelogger> also why
[15:50] <apachelogger> actually, primarily why
[15:51] <yofel> ok, found an excuse to get my notebook out
[15:51] <apachelogger> lol
[15:51] <murthy> apachelogger: the build system was updated to autobuild
[15:51] <yofel> automake?
[15:51] <yofel> *autotools?
[15:52] <apachelogger> no it wasn't
[15:52] <murthy> yofel__: ya automake
[15:52] <apachelogger> it used autotools in the version you diffed against
[15:52] <murthy> apachelogger: i didn't fully migrate
[15:53] <apachelogger> ?
[15:53] <murthy> apachelogger: i just changed the patch system
[15:53] <yofel> he asked why you did that
[15:54] <murthy> i will paste the log
[15:55] <yofel> murthy: cpu stuff: http://paste.kde.org/676118
[15:55] <murthy> yofel__: this script can be recommended to any kde devs ?
[15:56] <yofel> uh, it's "Works for me", but feel free to share it
[15:58] <Darkwing> Do we still have a plasma-mobile updated around here?
[15:58] <murthy> apachelogger: here is the debuild log http://paste.kde.org/676124/
[15:58] <Darkwing> Once Ubuntu on the phone drops on the 21st I want to try plasma on it and see how that goes.
[15:59] <murthy> Darkwing: is it a htc tablet >
[15:59] <yofel> Darkwing: we have plasma-mobile 3.0-0ubuntu1, which is active
[15:59] <apachelogger> murthy: how does that answer my question?
[15:59] <Darkwing> yofel: Awesome.
[16:00] <shadeslayer> brrr
[16:00] <yofel> Darkwing: as in: that's plasma-active, not sure how the phone UI looks currently
[16:00] <murthy> apachelogger: when i use quilt , debuild succeeds without errors
[16:00] <Darkwing> murthy: I'm watching the HTC event too but, on the 21st they are releasing Ubuntu on the phone for Galaxy Nexus and Nexus 4 images.
[16:00]  * apachelogger thinks his local juju is broken :(
[16:00] <shadeslayer> apachelogger: aw
[16:01] <apachelogger> murthy: you are not using quilt in the presented change
[16:01] <murthy> Darkwing: ya
[16:01] <Darkwing> yofel: Mobile and active are the same for a phone and tablet?
[16:01] <murthy> apachelogger: you mean the debdiff ?
[16:01] <apachelogger> yes
[16:01] <yofel> Darkwing: I guess?
[16:01] <apachelogger> you are simply not applying/deapplying the patch
[16:01] <apachelogger> patches even
[16:02] <shadeslayer> stupid, shutils can't even overwrite stuff
[16:02] <Darkwing> rbelem: pingie
[16:02] <murthy> apachelogger: wait let me check without using this simple-patchsys.mk
[16:02] <apachelogger> kubotu: order coffee
[16:02]  * kubotu slides coffee with milk down the bar to apachelogger.
[16:03] <apachelogger> juju charm testing is a pain in the behind very much
[16:03]  * apachelogger gives up
[16:03] <shadeslayer> lol
[16:03] <genii-around> apachelogger: I've been obsoleted :(
[16:03] <shadeslayer> hah
[16:04] <apachelogger> shadeslayer: unhandled ERROR [Errno 17] File exists: '/var/www/kubuntu-backports':
[16:04] <shadeslayer> apachelogger: sawn
[16:04] <shadeslayer> stupid shutils
[16:04] <shadeslayer> can't even overwrite dirs
[16:04] <apachelogger> you know
[16:04] <murthy> apachelogger: ya, you are right, i didn't check that. I will add the patches now
[16:04] <apachelogger> I think you'd be faster writing something specific for us :P
[16:04] <apachelogger> in a lanaguage you are comfortable with ^^
[16:04] <shadeslayer> eh? already fixed, I simply rm -rf /var/www/*
[16:05] <apachelogger> murthy: yeah, so ... why?
[16:05] <yofel> uhm....
[16:05] <yofel> shadeslayer: "fix"?
[16:05] <apachelogger> shadeslayer: fix...
[16:05] <shadeslayer> :P
[16:05] <apachelogger> shadeslayer: also the hours you poured into it already....
[16:05] <apachelogger> .......
[16:05] <murthy> apachelogger: why what?
[16:05] <shadeslayer> just one day?
[16:05] <apachelogger> murthy: why change from simplepatch to quilt?
[16:05] <apachelogger> shadeslayer: just
[16:06] <shadeslayer> isn't that better than taking alot more time writing something specific for us?
[16:06] <apachelogger> shadeslayer: I think writing sometign specific would have gone faster
[16:06] <murthy> apachelogger: ok, you saw the log, tell me what can be done
[16:07] <shadeslayer> I doubt it
[16:07] <murthy> apachelogger: is partial migration wrong?
[16:07] <apachelogger> nothing?
[16:07] <apachelogger> there is no error?
[16:08] <apachelogger> shadeslayer: what does it do? setup a chroot... install upgrade?
[16:09] <murthy> apachelogger: i see somthing like this in the log "Patch debian/patches/03_libav_initialise_context.patch is not applied.", what does that mean?
[16:09] <shadeslayer> starts ec2, installs stuff, adds ppa, upgrades, returns logs and figures out if there was an issue
[16:09] <apachelogger> murthy: it tried to unapply a patch that was not applied
[16:09] <apachelogger> shadeslayer: that some 200 sloc in bash...
[16:10] <shadeslayer> apachelogger: not exactly :P
[16:10] <apachelogger> yeah?
[16:10] <murthy> apachelogger: why was it not applied?
[16:10] <apachelogger> like the bigger part is starting ec2?
[16:10] <apachelogger> then ssh over script
[16:10] <shadeslayer> that's probably the easy part
[16:10] <shadeslayer> hm
[16:10] <apachelogger> remote script goes sudo apt-get install kubuntu-desktop^
[16:10] <apachelogger> then ou fiddle with the sources
[16:11] <apachelogger> then ou dist-upgrade or whatever it is you want to do
[16:11] <apachelogger> all the while you munch stdout into a logfile
[16:11] <shadeslayer> mmm
[16:11] <apachelogger> then all you need is || handlerror() behind each binary call and voila
[16:12] <shadeslayer> good point
[16:12] <shadeslayer> :P
[16:14] <apachelogger> murthy: because you did not run make -f debian/rules apply-patches?
[16:14] <apachelogger> dunno
[16:14] <apachelogger> doesn't really mmatter
[16:15] <murthy> apachelogger: debuild wont do that?
[16:15] <shadeslayer> apachelogger: want me to spend more time and money writing something for us?
[16:15] <apachelogger> debuild -S only invokes the unapply-patches and clean targets
[16:16] <apachelogger> shadeslayer: no, I'd want you to decide which road is more efficient before throwing a workday out the window :(
[16:16] <shadeslayer> hm
[16:17] <apachelogger> that time could have been spent triaging bugs or something
[16:17] <shadeslayer> ...
[16:17]  * apachelogger totally doesn't get how to do local jujus
[16:17] <apachelogger> all deployments end up in pending state doing nothing
[16:17] <apachelogger> oh well
[16:18]  * BluesKaj speculates about tedium
[16:19] <BluesKaj> I guess somebody has to do it , just glad it isn't me.
[16:19] <apachelogger> yofel: how does one detach a bzr checkout again?
[16:19] <apachelogger> ah, nvm
[16:19] <yofel> bzr unbind
[16:19] <apachelogger> found it
[16:19] <apachelogger> yofel: thx ^^
[16:20] <apachelogger> livecd theme changines ready
[16:21] <murthy> yofel__: I was not told about this " make -f debian/rules apply-patches", can you give me some idea?
[16:21] <apachelogger> only need to finish the plymouth refactor and get the 4bpp setting done
[16:21] <murthy> BluesKaj: hi
[16:21] <apachelogger> shadeslayer: also while we have time I suggest you raise concerns about the background on the mailing list
[16:22] <BluesKaj> hi murthy
[16:22] <murthy> its a tablet :)
[16:22] <yofel> murthy: what patch system is that from?
[16:22] <shadeslayer> idk, seems like only I have concerns about it
[16:22] <murthy> yofel__: cdbs, the package is libdlna 0.2.4
[16:23] <yofel> I don't know what exactly simple-patchsys does there, read the makefile?
[16:23] <apachelogger> shadeslayer: still better document them?
[16:23] <yofel> I never used it
[16:23] <yofel> murthy: simply from the name I guess it applies the patches
[16:24] <apachelogger> yofel: every patchery is done via the apply-patches/reverse-patches taget
[16:24] <apachelogger> *target
[16:24] <apachelogger> at least everything before dh7
[16:24] <yofel> ah, I only joined at around dh7
[16:25] <apachelogger> dunno if they kept it in dh>7
[16:25] <apachelogger> anywho
[16:25] <apachelogger> before quilt those targets where the way to go to reliably apply/unapply patches :)
[16:26] <murthy> apachelogger:  so i have to run this everytime for packages < dh7 ? " make -f debian/rules apply-patches"
[16:26] <yofel> ah
[16:26] <yofel> anyway, I'm going home, bbl
[16:26] <murthy> yofel__: later
[16:26] <apachelogger> as I said
[16:26] <apachelogger> it does not matter
[16:27] <apachelogger> if a patch is not applied, it needs not unapply it and that is what it says there
[16:27] <murthy> apachelogger: but didn't the patches have to be applied?
[16:28] <shadeslayer> apachelogger: are you trying out juju?
[16:28] <apachelogger> no
[16:28] <apachelogger> gave up
[16:29] <apachelogger> something is bogus on my system
[16:29] <shadeslayer> heh
[16:29] <apachelogger> creating a charm should be trivial
[16:29] <apachelogger> testing without a cloud... not so much
[16:29] <shadeslayer> hmm
[16:29] <apachelogger> i.e. it simply runs a script on hook situations
[16:29] <shadeslayer> roger
[16:29] <apachelogger> and in that script you can do any rubbish you want
[16:30] <apachelogger> so really just gloryfied deployment scripts with instance management glue around it
[16:30] <apachelogger> murthy: no
[16:30] <murthy> apachelogger: i am confused
[16:31] <shadeslayer> I see
[16:31] <murthy> apachelogger: I have to build the source without appying the patches?
[16:32] <apachelogger>        -S     Specifies a source-only build, no binary packages need to be made.  Passed to dpkg-genchanges.
[16:32] <shadeslayer> apachelogger: wfm http://paste.kde.org/676172/
[16:32] <apachelogger> actually
[16:33] <apachelogger> it's sad that youngsters don't know how building works
[16:33] <apachelogger> I am reasonable certain shadeslayer doesn't know either
[16:33] <shadeslayer> wat
[16:33] <shadeslayer> I do!
[16:33] <shadeslayer> thats hurtful
[16:33] <apachelogger> shadeslayer: try pushing a service into that machine
[16:33] <apachelogger> they end up pending for me
[16:33] <apachelogger> not doing anything
[16:34] <apachelogger> shadeslayer: dpkg-buildpackage -B what does it do? :P
[16:34] <BluesKaj> apachelogger, heh , I'm old , but I don't know how it works
[16:34] <shadeslayer> apachelogger: builds architechture dependent packages?
[16:34] <apachelogger> like
[16:34] <apachelogger> exactly
[16:34] <apachelogger> what does it do
[16:34] <apachelogger> because you can do that yourself too...
[16:35] <shadeslayer> errr .. okay I don't know that
[16:35] <apachelogger> debian/rules clean; debian/rules build; fakeroot debian/rules binary-arch (on i386 also binary-arch-indep)
[16:36] <shadeslayer> apachelogger: did you mean I should just call juju deploy wordpress ?
[16:36] <shadeslayer> oic
[16:36] <apachelogger> then debsign & dpkggenchanges
[16:36] <apachelogger> EOF
[16:36] <apachelogger> shadeslayer: juju deploy mysql for exammple
[16:36] <BluesKaj> ...BBL
[16:36] <shadeslayer> @_@
[16:37] <shadeslayer> 2013-02-19 22:06:54,042 ERROR Error processing 'cs:quantal/mysql': entry not found
[16:37] <apachelogger> eh, use precise
[16:38] <murthy> apachelogger: can you give me the commands list ?
[16:38] <murthy> apachelogger: i mean the build steps
[16:38] <apachelogger> murthy: debian/rules is technically (although not visually) comprised of a number of targets (call them build steps if you will), those targets depend on other targets and each target has a given set of instructions that will be exectued when the target is executed (kinda like a script). the dependencies of targets essentially dictates what gets executed when.
[16:38] <apachelogger> now the tools we use are just loasd and loads of automation stacked on top of those targets
[16:38] <murthy> apachelogger:  i am aware of that
[16:39] <apachelogger> such that debuild in fact uses dpkg-buildpackage which in fact then uses make to execute any of the targets
[16:39] <apachelogger> well, not any, but a specific target
[16:39] <apachelogger> int he case of -B as i mentioned earlier the targets are clean; build; binary-arch
[16:39] <apachelogger> in  the case of -S the target is *only* clean
[16:40] <apachelogger> point being that the source is not ever polluted by anything that is not supposed to be there
[16:41] <shadeslayer> lul
[16:41] <apachelogger> i.e. after the clean target the source should always be in pristine condition (as it would be if one just extracted the source via dpkg-source)
[16:41] <shadeslayer> apachelogger: http://paste.kde.org/676178/
[16:41] <shadeslayer> from juju debug-log
[16:42] <apachelogger> so, no, patches are not applied when building the source
[16:42] <apachelogger> in particular they are not ever applied explicitly
[16:42] <apachelogger> only a hand full of targets are expected to be there
[16:42] <apachelogger> and nothing patchy is part of those
[16:42] <murthy> apachelogger: in that case why do we do a quilt push before a debuild?
[16:43] <apachelogger> we don't
[16:43] <apachelogger> you perhaps do
[16:43] <apachelogger> I don't
[16:43] <apachelogger> because it makes no sense
[16:43] <apachelogger> the clean target will pop -a
[16:43] <apachelogger> the build target will push -a
[16:44] <apachelogger> so any manual popping or pushing is completely uninteresting for the toolchain
[16:45] <murthy> apachelogger: i can understand that the source have to remain clean. but does the buyild system for libdlna does  try to unapply a patch is not to be applied>?
[16:45] <murthy> apachelogger: i can understand that the source have to remain clean. but why does the buyild system for libdlna does try to unapply a patch is not to be applied>?
[16:49] <apachelogger> 1/rules/buildcore.mk:clean:: testdir testroot cleanbuilddir reverse-config testsanity
[16:49] <apachelogger> 1/rules/simple-patchsys.mk:cleanbuilddir:: reverse-patches
[16:50] <apachelogger> 	for patch in $$patches; do \
[16:50] <apachelogger> 	  if [ "$@" = "reverse-patches" ]; then \
[16:50] <apachelogger> 	    if [ ! -e $(cdbs_patch_stamp_file) ]; then \
[16:50] <apachelogger> 	      echo "Patch $$patch is not applied."; continue; \
[16:50] <apachelogger> that's why
[16:50] <apachelogger> because it is part of the clean target
[16:50] <apachelogger> and as I explained the clean target is always executed as part of -S
[16:51] <Riddell> apachelogger: there is an owncloud charm, I didn't write it, that was atul jar I think
[16:51] <apachelogger> ah, groovy
[16:52] <apachelogger> no need for me to find out why my instances are broken then ^^
[16:52] <apachelogger> shadeslayer: I think your juju is also broken :P
[16:52] <shadeslayer> heh
[16:52] <shadeslayer> dunno
[16:53] <apachelogger> well
[16:53] <apachelogger> python
[16:53] <apachelogger> ...
[16:53] <apachelogger> :P
[16:53] <shadeslayer> right
[16:53] <shadeslayer> :P
[16:54] <Riddell> yofel: did you look at smartboy's calligra or is it still to do?
[16:55] <murthy> apachelogger: why does debuild -S always executes target clean? if it wants to clean the source, what changed the source ?
[16:56] <apachelogger> dpkg-buildpackage -B
[16:56] <apachelogger> now your source is polluted
[16:56] <apachelogger> dpkg-buildpackage -S
[16:56] <apachelogger> now your source is clean again
[16:56] <murthy> apachelogger: so when running debuild -S  "dpkg-buildpackage -B" is executed?
[16:57] <apachelogger> no
[16:58] <murthy> apachelogger: so dpkg-buildpackage -B is invoked by?
[16:58] <apachelogger> you
[16:58] <apachelogger> if you build a binary the build target is executed, the build target will invoke the actual build system which usually throws crap all over the source
[16:58] <murthy> apachelogger: after "sudo pbuilder build " ?
[16:59] <apachelogger> if you then build the source you need a clean source again so the clean target is invoked to clean the source
[16:59] <apachelogger> murthy: no
[16:59] <apachelogger> after dpkg-buildpackage -B
[16:59] <apachelogger> please read up on what tool does what
[16:59] <apachelogger> dpkg-buildpackage != pbuilder
[16:59] <apachelogger> pbuilder != anything really
[17:00] <murthy> apachelogger: why do i want to build a binary?
[17:00] <apachelogger> right
[17:00] <apachelogger> afk
[17:00] <murthy> apachelogger: ha ha ha
[17:08] <murthy> apachelogger: http://askubuntu.com/questions/178788/how-to-obtain-rej-file-from-debuild
[17:10] <murthy> apachelogger: when running debuild , quilt tries to apply the patch and rejects which doesn't work, it then cleans the applied pathches. So the patches are applied first and then cleaned
[17:12] <apachelogger> ok
[17:12] <apachelogger> shadeslayer: we won't get debug logs for the qa?
[17:12] <apachelogger> or is that because its broken?
[17:12] <shadeslayer> the latter
[17:12] <apachelogger> k
[17:12] <shadeslayer> I have them on disk if you want
[17:13] <murthy> apachelogger: so was the patches for patches appllied and
[17:14] <murthy> apachelogger: so was the patches for patches applied and succeed before unpatching/cleaning? for libdlna?
[17:14] <apachelogger> shadeslayer: nah, just interested
[17:14] <murthy> apachelogger: so was the patches  applied and succeed before unpatching/cleaning? for libdlna?
[17:14] <shadeslayer> http://<IP_ADDRESS>/kubuntu-backports/
[17:14] <apachelogger> murthy: dunno, askubuntu.com
[17:15] <apachelogger> shadeslayer: it's forbidden, oh noes
[17:15] <murthy> apachelogger: are you fed up?
[17:15] <apachelogger> apt-term.log
[17:15] <shadeslayer> wot
[17:15] <shadeslayer> O_O
[17:15] <apachelogger> murthy: why no, but if you think that askubuntu knows better how debuild works than I do, then you should very much ask ubuntu
[17:16] <murthy> apachelogger: no i was just pointing out that for an example log
[17:16] <apachelogger> also you still did not switch to quilt and there still is no reason, so any further discussion of the topic is very pointless
[17:16] <shadeslayer> apachelogger: try again
[17:16] <apachelogger> werks
[17:16] <apachelogger> thx
[17:18] <murthy> apachelogger: can you have some more patience and clear my doubts?
[17:18] <apachelogger> shadeslayer: hm
[17:18] <apachelogger> shadeslayer: I don't see the upgrade
[17:18] <apachelogger> murthy: revisit what I wrote
[17:19] <apachelogger> shadeslayer: ah, nvm
[17:20] <apachelogger> still confused, silly apt logs
[17:22] <murthy> apachelogger: this will be my last question. debuild -S does not test patches by applying and removing ?
[17:22] <apachelogger> debuild does not handle patches
[17:23] <murthy> apachelogger: ok
[17:25] <yofel> Riddell: still todo unless you did it in the meantime
[17:25] <murthy> is there a classroom or some channel where i can clear my doubts?
[17:26] <yofel> #ubuntu-packaging generally
[17:27] <yofel> murthy: but as he already said, debuild -S only builds the source package
[17:27] <Riddell> yofel: I'm doing it
[17:27] <yofel> that has nothing to do with patches in general
[17:28] <murthy> yofel: so patches won't get rejected during debuild?
[17:29] <yofel> not unless you have a properly configured patch system
[17:29] <yofel> dpkg-source has quilt support built in, but quilt is only used for format 3.0 (quilt) packages
[17:30] <murthy> yofel: does that matter during a debuild, you said it just builds the source
[17:30] <murthy> yofel: i mean for this "not unless you have a properly configured patch system"
[17:30] <yofel> not really, the only relevant part here is that the clean target *should* force-unapply all patches
[17:31] <yofel> murthy: debuild/debhelper doesn't know how to handle patches
[17:31] <murthy> yofel: so the patch was applied?
[17:31] <yofel> it doesn't matter whether it was applied or not
[17:31] <yofel> it will try to unapply it to make sure it's not applied
[17:31] <murthy> yofel: thats not correct procedure right?
[17:31] <yofel> as it has no way to know whether it was applied
[17:31] <yofel> murthy: and what would be the correct one?
[17:32] <murthy> yofel: it should check if the patch was applied before unapplying
[17:32] <yofel> feel free to write the make rule for that
[17:32] <yofel> usually nobody bothers
[17:32] <murthy> yofel: "quilt applied" lists the applied patches
[17:33] <apachelogger> yofel: all patch systems conditionally de-apply
[17:33] <yofel> apachelogger: I was talking about debhelper...
[17:33] <murthy> apachelogger: conditionally?
[17:34] <apachelogger> yofel: they still do not fail on reverse patching
[17:34] <apachelogger> in particular assuming reverse patching is always part of clean it in fact must not fail as clean must not fail
[17:35] <murthy> this is like blindly working
[17:35] <yofel> *sigh* - is "quilt pop -a" being run or not?
[17:35] <apachelogger> (which is why in a hand crafted clean target you will see loads of prefix minuses making make ignore the return code of the subprocess
[17:35] <yofel> that's all I was talking about
[17:35] <apachelogger> yofel: lol
[17:36] <apachelogger> yofel: too much backlog I'll just shut up :P
[17:36] <yofel> ofc. the patch system itself will know whether to deapply patches
[17:36] <yofel> dh/dpkg does not
[17:36] <apachelogger> I fail to see your point
[17:36] <apachelogger> (also technically dpkg does in case of source3(quilt))
[17:37] <yofel> dunno, I forgot what point I was trying to make -.-
[17:37] <apachelogger> ^^
[17:37] <shadeslayer> heh
[17:37] <apachelogger> ah
 it doesn't matter whether it was applied or not
 it will try to unapply it to make sure it's not applied
[17:38] <apachelogger> ^ that is a check for a patch being applied or not
[17:38] <murthy> yofel: why is there a condition to clean an source when we are just packaging and we when we wont touch the source
[17:38] <apachelogger> actually that is the only reliable way (i.e. trying to actually patch -R)
[17:38] <yofel> apachelogger: ok, good point
[17:39] <apachelogger> e.g. that is what simplepatch does
[17:39] <yofel> murthy: um, patching is very much part of the packaging
[17:39] <apachelogger> simply try to reverse patch
[17:39] <yofel> murthy: oh, you mean why run the clean target?
[17:40] <yofel> murthy: to have a clean source package?
[17:40] <murthy> yofel: so if i had done "quilt push -a" debuild will revert the patches?
[17:40] <yofel> murthy: the clean target won't do much unless you did a build before
[17:41] <yofel> murthy: with format 3.0 (quilt), or with quilt support manually added, yes
[17:41] <murthy> yofel: in case of us, we dont build it, so why cleaning?
[17:41] <yofel> how does dpkg-source know that it's clean?
[17:42] <murthy> yofel: it doesn't have to , it has to be a requirement for the source to be clean
[17:43] <yofel> how do you build a source package from a package that has build files in it?
[17:43] <murthy> yofel: i wont do that
[17:43] <yofel> you not, but it's supported
[17:43] <yofel> that's why the clean target it always run at the beginning
[17:43] <yofel> s/it/is/
[17:43] <kubotu> yofel meant: "that's why the clean target is always run at the beginning"
[17:44] <yofel> it's not like dh_clean does much on an already clean source
[17:45] <yofel> murthy: the clean target being run is part of the auto-sequencing, you don't need to worry about that
[17:45] <yofel> it's just that de-applying patches belongs into the clean target
[17:47] <yofel> murthy: back to libdlna
[17:47] <yofel> murthy: what you did here is break the patch support
[17:47] <murthy> yofel: ok
[17:47] <murthy> yofel: ya
[17:47] <yofel> you disabled simple-patchsys.mk without replacing it with something else
[17:48] <murthy> yofel: I forgot to add the patches to the quilt
[17:48] <yofel> you forgot to do that, and forgot to add quilt support
[17:48] <murthy> yofel: but as apachelogger told, there is no need
[17:48] <yofel> yeah, because... what's broken currently?
[17:48] <murthy> yofel: nothing
[17:49] <yofel> ok, so just keep simple-patchsys
[17:49] <murthy> yofel: I thought the deapplying patches warning was an error
[17:49] <yofel> ah, no
[17:51] <murthy> yofel: so at what point the patches are tested and gets rejected and we need to remove/refresh it?
[17:51] <yofel> during build
[17:51] <yofel> or actually before the configure step
[17:52] <murthy> yofel: ok, i forgot that
[17:52] <Darkwing> Riddell: you about?
[17:52] <Quintasan> \o
[17:54] <Riddell> Darkwing: howdy partner
[17:54] <Darkwing> Riddell: Greetings. I reinstalled Ubuntu using a dualboot on my nexus7. What steps did you run to get active? Just apt-get install plasma-active?
[17:55] <Quintasan> Darkwing: raring?
[17:55] <Riddell> Darkwing: kubuntu-active
[17:56] <Darkwing> Riddell: Okay
[17:56] <Riddell> then there's faff to log into it I think
[17:56] <Riddell> in lightdm you need to click the wee menu in the top right for accessibility to get a keyboard
[17:56] <Riddell> and work out where to press to get a login option
[17:57] <Darkwing> Hmmz... I would love to somehow get this into an image... this way we wouldn't have to worry about ubuntu/unity
[17:57] <yofel> murthy: the complicated part here is that the quilt behaviour that you're used to is the one described under "Format 3.0 (quilt)" in the dpkg-source manpage. libdlna is a format 1.0 package
[17:58] <apachelogger> images are always a big headache to create
[17:58] <Riddell> Darkwing: yeah, needs ogra poked
[17:58] <Darkwing> apachelogger: Yeah I know
[17:58] <murthy> yofel: ya, i can imaging a system do something blindly
[17:58] <Darkwing> Riddell: But, if touch on Active isn't even working correctly...
[17:58] <murthy> yofel: ya, i can't imaging a system do something blindly
[17:59] <Darkwing> At least the dualboot works. :D
[17:59] <Riddell> Darkwing: you can also connect to a console if you plug in the usb cable in to your laptop
[17:59] <Darkwing> Riddell: that would be helpful
[17:59] <Riddell> livecd-rootfs needs changes to get images made, I'm not sure what else
[17:59] <apachelogger> Oo
[17:59] <apachelogger> Darkwing: touch aint working? Oo
[17:59] <Riddell> Darkwing: https://wiki.ubuntu.com/Nexus7/UsingTheDevice
[18:00] <Riddell> apachelogger: wasn't working in QML when I tried it
[18:01] <apachelogger> :/
[18:01] <apachelogger> probably Qt touch breakage then
[18:01] <murthy> yofel: i have done the changes to the changelog and the rules file, i have to test build with pbuilder
[18:01] <apachelogger> IIRC that is one big stinky patch to qt4
[18:03] <Riddell> since ubuntu just announced their tablet UI with touch probably it'll get fixed
[18:03] <Riddell> it uses Qt of course
[18:04] <shadeslayer> they did?
[18:04] <shadeslayer> oh
[18:04] <shadeslayer> hmm
[18:04] <shadeslayer> is that the Nexus 10 :O
[18:05] <shadeslayer> looks like it
[18:05] <Riddell> shadeslayer: no there's no actual hardware there
[18:05] <Riddell> and no code
[18:05] <Riddell> just pretty pictures
[18:05] <apachelogger> Riddell: qt5 I'd suspect :P
[18:05] <shadeslayer> oh
[18:05] <shadeslayer> okay :D
[18:06] <apachelogger> which reminds me
[18:06] <apachelogger> fabo: how's the qt5 packaging going?
[18:07] <Riddell> apachelogger: the stuff we've been uploading for the last week?
[18:07] <Darkwing> I'm going to run a HUGE test run on it.
[18:07] <apachelogger> oh
[18:07] <apachelogger> that explains things
[18:07] <Riddell> just qtcreator being fiddly still
[18:08] <apachelogger> neat
[18:08] <apachelogger> Riddell: anyone doing backports?
[18:09] <Riddell> apachelogger: not that I know of
[18:09] <apachelogger> k
[18:09] <Riddell> although older packages in here https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-proper/+packages
[18:10] <Riddell> actually this one is pretty up to date https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta-proper/+packages
[18:10] <shadeslayer> Riddell: care to upload https://launchpad.net/~rohangarg/+archive/nightly?field.series_filter=raring
[18:11] <shadeslayer> oh and I've just uploaded the meta package
[18:11] <Riddell> shadeslayer: you don't have upload permissions?
[18:11] <shadeslayer> not for all of it
[18:12] <shadeslayer> only for the seeded stuff
[18:12] <yofel> any reason why not?
[18:12] <shadeslayer> because it's in universe?
[18:12] <yofel> add it to the supported seed?
[18:12] <yofel> if we're taking care of it anyway
[18:12] <shadeslayer> hmm ... yeah
[18:12] <apachelogger> Riddell: was thinking ubuntu-backports
[18:13] <apachelogger> may be worthwhile to throw at precise if at all possible
[18:13] <yofel> shadeslayer: if you're bored, also fix the KDE SC list ^^
[18:13] <shadeslayer> lol
[18:13] <Riddell> Darkwing: test on what?
[18:13] <Riddell> apachelogger: always nicer
[18:14] <Darkwing> find out what is working and what is not on the N7
[18:14] <apachelogger> Riddell: put it on todo for close to raring
[18:14] <apachelogger> such that we have something reliable
[18:14] <apachelogger> don't really wanna push continous patches to backports
[18:14]  * Riddell out again
[18:15] <apachelogger> ScottK: did you actually see my mangonel backport request?
[18:22] <murthy> yofel: the patches are already applied upstream for libdlna, should remove the patch files or just disable it by commenting out in series file?
[18:23] <yofel> if you verified that they're all part of the new upstream source that you're packaging, drop them and say so in the changelog stating the reason
[18:25] <murthy> yofel: "drop them" means deleting the .patch file right?
[18:27] <yofel> right
[18:32] <murthy> yofel: do i have to specify the list of patches that removed in the changelog?
[18:34] <yofel> yes
[18:34] <murthy> yofel: you mean the list of .patch files?
[18:35] <yofel> yes, the patch names. It's not required, but it really helps finding out what happened to a patch
[18:35] <murthy> yofel: ok
[18:36] <murthy> yofel: http://paste.kde.org/676220/
[18:37] <yofel> better
[18:38] <murthy> yofel: i don't have to modify anything else, example the rules file?
[18:38] <yofel> nope, simple-patchsys is rather simple
[18:38] <murthy> yofel: ok
[18:55] <murthy> yofel: https://bugs.launchpad.net/ubuntu/+bug/1129977
[18:59] <yofel> murthy: assigned it to the proper package, please set the status to confirmed again and wait
[19:01] <murthy> yofel: done
[19:02] <murthy> yofel: so this will the steps for getting a sponsor for ubuntu packages?
[19:03] <yofel> that should be it, yes
[19:03] <shadeslayer> ah shit
[19:03] <shadeslayer> I accidentially purged python3
[19:04] <shadeslayer> stuff is going to get ugly
[19:04] <yofel> how did you do that...
[19:04] <shadeslayer> I was looking at what would be removed if I removed python3
[19:04] <shadeslayer> and I accidentally hit enter when it asked to remove all of these packages
[19:04] <murthy> yofel: so if i want to get a debian sponsor, i have to add denian <packagename> to affects field and the add the debian sponsor team?
[19:05] <yofel> murthy: no, they have their own procedure
[19:05] <murthy> shadeslayer: :D
[19:05] <murthy> yofel: ok
[19:06] <yofel> murthy: for debian see http://mentors.debian.net/ and http://wiki.debian.org/DebianMentorsFaq#How_do_I_get_a_sponsor_for_my_package.3F
[19:06] <murthy> shadeslayer: did you check the debian/copyright for ktp-desktop-applets?
[19:07] <shadeslayer> I don't see a merge request : https://code.launchpad.net/~telepathy-kde/telepathy-kde/ktp-desktop-applets-ubuntu
[19:08] <shadeslayer> seems like stuff is merged?
[19:08] <shadeslayer> http://bazaar.launchpad.net/~telepathy-kde/telepathy-kde/ktp-desktop-applets-ubuntu/view/head:/debian/copyright
[19:08] <yofel> wow, enjoy the red :D
[19:09] <murthy> shadeslayer: http://paste.kde.org/676256/
[19:09] <shadeslayer> is line 5 required?
[19:09] <murthy> shadeslayer: its optionl as said by Riddell and i want to keep it
[19:10] <murthy> shadeslayer: i will request a merge aftr you confirm that the copyright is good
[19:17] <shadeslayer> murthy: looks good
[19:17] <shadeslayer> qtwebkit built \o/
[19:17] <murthy> shadeslayer: nice
[19:18] <shadeslayer> atleast for amd64
[19:18] <murthy> shadeslayer: shall i request a merge?
[19:18] <shadeslayer> yes please
[19:18] <murthy> shadeslayer: thank you
[19:19]  * apachelogger falls off chair
[19:19] <apachelogger> I think my designer is hiding
[19:19] <apachelogger> shadeslayer: halp
[19:20] <shadeslayer> apachelogger: ?
[19:20] <apachelogger> what did you do to my shetan?
[19:20] <sheytan> apachelogger: no i'm not :D
[19:20] <apachelogger> y missing somewhere there
[19:20] <shadeslayer> voila :D
[19:20] <apachelogger> sheytan: we needs the graphics!
[19:20] <sheytan> i know
[19:20] <apachelogger> sheytan: so I was thinking, perhaps instead of a glow we simply make it solid white
[19:20] <apachelogger> i.e. instead of glowing up the parts get fatter
[19:21] <sheytan> what about fade in and out?
[19:21] <shadeslayer> apachelogger: btw #juju says the problem is something to do with the way python2 and python3 handle unicode and strings
[19:21] <sheytan> the whole
[19:21] <sheytan> oh
[19:21] <sheytan> we cannot
[19:21] <apachelogger> then there's nothing there :)
[19:21] <shadeslayer> python2 used to convert automagically, while python3 does not
[19:21] <apachelogger> shadeslayer: big surprise there :P
[19:21] <shadeslayer> so update-manager it is! :D
[19:22] <sheytan> apachelogger: for fade in/out you will still need alpha channel, right?
[19:22] <apachelogger> yes
[19:22] <apachelogger> well
[19:22] <apachelogger> 16bit has some 4 bits for alpha or so (depending on the actual driver)
[19:23] <apachelogger> so we get some opacity, not much though
[19:23] <apachelogger> that being said... this does not need to be super slick
[19:23] <sheytan> what about your rotating one for that?
[19:23] <apachelogger> most people will either get the proper logo theme or the utterly ugly text theme
[19:24] <apachelogger> sheytan: hm, yeah
[19:24] <apachelogger> could do
[19:24] <sheytan> see? :D
[19:24] <apachelogger> that's quite some additional code
[19:24] <apachelogger> brrrrr
[19:24] <apachelogger> oh well
[19:24] <apachelogger> yeah, I guess that solves that
[19:24] <apachelogger> sheytan: only need lightdm/ksplash solved then :P
[19:25] <sheytan> and with that, it still looks good enough
[19:25] <sheytan> well :D
[19:25] <sheytan> here starts the adventure ;)
[19:25] <sheytan> with ldm
[19:25] <apachelogger> also I think we should then keep the crap until 14.04 (lts)
[19:25] <apachelogger> i.e. so much time went into that it would be a shame to tear it down for the next release again ;)
[19:25] <sheytan> i would say, that the modification of Ivan's ksplash is good
[19:25] <sheytan> yeah
[19:26] <apachelogger> agreed on the splash
[19:26] <sheytan> saw it, right?
[19:26] <apachelogger> yeah
[19:26] <sheytan> it's simple and looks good btw
[19:26] <apachelogger> also I am not a fan of that icon blinky stuff
[19:26] <apachelogger> no one really knows what the icons mean anyway
[19:26] <sheytan> true ture
[19:26] <sheytan> true true*
[19:26] <apachelogger> sheytan: thing is, that's big divergence from upstream so that definitely needs to be proposed on the list
[19:27] <sheytan> i will
[19:27] <sheytan> so now ldm
[19:27] <sheytan> if somene will help me with some things i need to resolve with that
[19:27] <sheytan> mine modified version of agateau 's work will be ok i guess
[19:28] <apachelogger> what's the modifications?
[19:28] <sheytan> what i need, is to know, how one change the size and color of the user's name text
[19:28] <sheytan> i moved the sysbuttons to the middle
[19:28] <sheytan> used bigger icons
[19:28] <apachelogger> ah yes
[19:28] <sheytan> and the clock
[19:28] <apachelogger> the clock needs changing though
[19:29] <sheytan> but the clock is like 4 lines of code to remove
[19:29] <apachelogger> not sure though
[19:29] <murthy> shadeslayer: the merge target will be "ktp-desktop-applets" branch or "ktp-desktop-applets-ubuntu" branch?
[19:29] <apachelogger> sheytan: I actually suggest you poke agateau tomorrow
[19:29] <sheytan> he's from France, right?
[19:29] <apachelogger> because a) that likely should be carried upstream anyway b) I think he'll have input
[19:29] <apachelogger> yes, france
[19:30] <sheytan> good, same time as here
[19:30]  * sheytan wish to have it's mockup come 100% ture
[19:30] <sheytan> ture*
[19:31] <sheytan> fu ck :D
[19:32] <apachelogger> teur? :P
[19:32] <sheytan> true i was about to say
[19:33] <apachelogger> sheytan: font.pixelSize: 100
[19:33] <apachelogger> color: "blue"
[19:33] <apachelogger> on loginText (I think)
[19:33]  * sheytan takes a look
[19:33] <murthy> any video showing current state of the plymouth ?
[19:33] <apachelogger> don't think so
[19:34] <apachelogger> sheytan: btw, saw my livecd screenshots earlier?
[19:34] <sheytan> dont know which one you think about :D
[19:34]  * sheytan saw few of them
[19:35] <apachelogger> sheytan:  http://wstaw.org/m/2013/02/18/plasma-desktopRH2164.png -> http://wstaw.org/m/2013/02/18/plasma-desktopjw2164.png -> http://wstaw.org/m/2013/02/18/plasma-desktopLJ2164.png
[19:36] <shadeslayer> murthy: the latter
[19:36] <murthy> shadeslayer: ok
[19:36] <sheytan> apachelogger: there's no such file like loginText.qml
[19:36] <apachelogger> sheytan: nah, in main.qml the item loginText
[19:37] <murthy> shadeslayer: getting an error "This branch is not mergeable into lp:~telepathy-kde/telepathy-kde/ktp-desktop-applets-ubuntu."
[19:37] <shadeslayer> err ... fix it?
[19:38] <yofel> murthy: what did you branch from?
[19:38] <sheytan> apachelogger: ok, looking
[19:38] <sheytan> saw the shots already
[19:38]  * apachelogger branches shadeslayer from yofel
[19:38] <murthy> yofel: nothing
[19:38] <murthy> yofel: its a fresh package
[19:38] <yofel> murthy: uh, you can't merge that
[19:39] <murthy> yofel: what should i do?
[19:39]  * apachelogger cannot merge his shadeslayer branch with shadeslayer :(
[19:39] <apachelogger> actually that would be fun... a shadeslayer that knows how to write the pyth0rn
[19:39] <apachelogger> muahaha
[19:39] <apachelogger> ^^
[19:39] <yofel> murthy: branch from lp:~telepathy-kde/telepathy-kde/ktp-desktop-applets-ubuntu, apply your changes there, push, merge
[19:39] <shadeslayer> nooo
[19:39] <apachelogger> :(
[19:40] <sheytan> apachelogger: the boot is ok. you might use gray text if you want. To not let somebody say, it looks like you've got broken lcd ;D
[19:40] <shadeslayer> I don't like python
[19:40] <murthy> shadeslayer: problem?
[19:40] <shadeslayer> /o\
[19:40] <shadeslayer> murthy: not really :)
[19:40] <murthy> shadeslayer: so i can carry on what yofel said?
[19:41] <sheytan> apachelogger: ok, i remeber now. I was trying that with color and size. It breaks the theme.
[19:41] <yofel> hm...
[19:42] <yofel> I thought about having shadeslayer package pyqt/pykde for neon...
[19:42] <apachelogger> sheytan: in what way?
[19:42] <yofel> but I can't find a reason why I would want to torture him...
[19:42] <sheytan> apachelogger: don't ask me :D
[19:42] <apachelogger> lol?
[19:42] <shadeslayer> :(
[19:42] <apachelogger> u no have eyes?:P
[19:43] <shadeslayer> murthy: yes
[19:43] <yofel> shadeslayer: I think that will not get looked at before it's based on qt5. pure insanity :(
[19:43] <shadeslayer> yofel: I see
[19:43] <shadeslayer> well
[19:43]  * apachelogger almost got to like yofel
[19:43] <shadeslayer> yofel: I think that's fair enough
[19:43] <apachelogger> who doesn't get looked at?
[19:44] <shadeslayer> apachelogger
[19:44] <apachelogger> aww :'(
[19:44] <yofel> apachelogger support in neon
[19:44] <apachelogger> yeah
[19:44] <apachelogger> qt5 will be better
[19:44] <apachelogger> KMS apachelogger
[19:44] <shadeslayer> hmm ... I don't think we can fit apachelogger in the neon ppa
[19:44] <apachelogger> hooray
[19:44] <yofel> haha
[19:44] <apachelogger> awwwww
[19:44] <shadeslayer> to the lp admins for more space!
[19:44] <apachelogger> I could destroy lunchpad from the inside
[19:44]  * sheytan thinks Nuno is really smart
[19:45] <shadeslayer> apachelogger: or you could make it more awesome
[19:45] <sheytan> apachelogger: you won't :)
[19:45] <apachelogger> sheytan: how so?
[19:45] <apachelogger> shadeslayer: who?
[19:45] <shadeslayer> apachelogger: lunchpad
[19:45] <sheytan> apachelogger: i've got that magic stuff you couldn't share :)
[19:45] <apachelogger> shadeslayer: more awesome
[19:45] <apachelogger> LOL
[19:45] <apachelogger> ROFLMAO
[19:45] <yofel> I think we could spend one whole cycle on making launchad sane...
[19:45] <apachelogger> sheytan: goody
[19:46] <sheytan> yepii
[19:46] <shadeslayer> one? ahahahaha
[19:46] <apachelogger> sheytan: still sad that a designer needs to make UI IMHO
[19:46] <shadeslayer> I bet everyone goes insane in 3 weeks
[19:46] <yofel> shadeslayer: I was optimistically thinking that you would learn python by then
[19:46] <apachelogger> fortunately it's simply enough with QML (when done right)
[19:46] <apachelogger> but in plymouth....
[19:46] <apachelogger> ......
[19:46] <sheytan> :D
[19:46] <apachelogger> and yet that is also pretty close to javascript
[19:47] <sheytan> evil comes out id this ;d
[19:47] <shadeslayer> heh
[19:47] <apachelogger> just more crap
[19:47]  * sheytan remembers javascript from school. Could not even make a calc done :)
[19:47] <shadeslayer> C++ ftw
[19:47] <apachelogger> yofel: thinking shadeslayer will learn useful things is far out
[19:47] <apachelogger> like he still doesn't speak make
[19:48] <apachelogger> yet make is the possibly most used language ever
[19:49] <sheytan> apachelogger: so, i will talk to agateau tomorrow, use his tricks, make a demo, show you, if you like, disquss on mailing list
[19:50]  * sheytan wishes the ldm theme to look like this, and is about to make it true! http://img41.imageshack.us/img41/930/login22.png
[19:51] <sheytan> apachelogger: one important thing for me here is, to learn how one put external icons for sysbuttons
[19:51]  * apachelogger scratches ear
[19:51] <apachelogger> ohm
[19:52] <apachelogger> Image { source: "images/foo.png" }
[19:52] <apachelogger> although
[19:52] <apachelogger> I think with lightdm from git this can be done differently
[19:52] <sheytan> trust me. I've tried that
[19:52]  * sheytan thinks ldm-qml code is wired
[19:52] <apachelogger> yeah, that's why master does it differently I guess
[19:52] <murthy> yofel: http://bazaar.launchpad.net/~murthy/kubuntu-packaging/ktp-desktop-applets-ubuntu/files/head:/debian/
[19:53] <apachelogger> sheytan: for testing simply use source: "/home/you/foo.png" or whatever
[19:53] <apachelogger> absolute path anyway
[19:53] <apachelogger> ah
[19:53] <apachelogger> source: "file:///home/you/foo.png"
[19:53] <yofel> shadeslayer: ^
[19:53] <apachelogger> that will work best I think ^^
[19:53] <sheytan> this is stupid ;D
[19:53] <sheytan> i mean, it shouldn't be that way
[19:53] <apachelogger> yeah, lightdm does something weird to qt
[19:53] <apachelogger> don't ask me what
[19:54] <apachelogger> all david's fault :P
[19:54] <apachelogger> sheytan: also you used imageshack again
[19:54] <sheytan> once i put an foo.png for sysbutton, it displayed but it wasn't a button anymore ;)
[19:54] <apachelogger> ... image still loading....
[19:54] <apachelogger> ......
[19:54] <apachelogger> now done
[19:54] <murthy> yofel: i am still getting this error "This branch is not mergeable into lp:~telepathy-kde/telepathy-kde/ktp-desktop-applets-ubuntu."
[19:54] <apachelogger> good lord that's slow
[19:54] <sheytan> apachelogger: sorry, will try to improve myself :D
[19:54] <apachelogger> AH
[19:55] <apachelogger> sheytan: you'll need to use the toolbutton item
[19:55] <apachelogger> i.e. not make it an image
[19:55] <apachelogger> or well
[19:55]  * sheytan doesn't even know what the hell it is :)
[19:55] <apachelogger> if you want to make it an image you have to add a mousearea
[19:55] <sheytan> tell me more, please tell me more.  :D
[19:57] <apachelogger> sheytan: best ask agateau :P
[19:57] <sheytan> that's what i will do :D
[19:57] <apachelogger> the thing is
[19:58] <murthy> shadeslayer: I am still getting this error "This branch is not mergeable into lp:~telepathy-kde/telepathy-kde/ktp-desktop-applets-ubuntu."
[19:58] <yofel> shadeslayer: for that matter, why are those branches owned by ~telepathy-kde if they are the release branches?
[19:58] <apachelogger> sheytan: the qml item he's using is based on an iconloader ... i.e. it expects the icon to be the name of an icon in your regular icon paths
[19:59] <sheytan> apachelogger: yeah, know that already. I came out with that mind cause of iconloader.qml
[20:00] <apachelogger> sheytan: however when you are using custom artwork anyway you might as well not use an iconloader for that thing so that's really no issue in the long rung
[20:00] <apachelogger> anywho
[20:00] <sheytan> but there must be a way to add your own icons.
[20:00] <apachelogger> sheytan: one problem I had with your themes
[20:00] <apachelogger> if a user is not listed I cannot log in
[20:00] <apachelogger> that is a considerable inconvenience
[20:00] <apachelogger> i.e. I cannot simply enter a user name
[20:01] <sheytan> apachelogger: it's the way agateau made the theme
[20:01] <yofel> murthy: I don't get it, it works if I do it
[20:01] <yofel> murthy: what did you do?
[20:01] <apachelogger> you mmockup also does not accomodate that use case
[20:02] <apachelogger> ...
[20:02] <apachelogger> nunos would :P
[20:02] <apachelogger> I actually cannot remember in what context I noticed the problem
[20:02] <murthy> yofel: 1. bzr branch  lp:~telepathy-kde/telepathy-kde/ktp-desktop-applets-ubuntu
[20:02] <apachelogger> I mean it is barely a use case, if at all
[20:02] <sheytan> yeah, i was about to make the theme that way too
[20:02] <murthy> yofel: 2. modified it
[20:02] <apachelogger> but there was something about it that was at the point rather annoying
[20:03] <apachelogger> sheytan: well, just something you should talk about
[20:03] <murthy> yofel: 3. bzr commit -m "Initial commit"
[20:03] <sheytan> apachelogger: i never used to type my username while login
[20:03] <sheytan> maybe it was the reason i didn't add this
[20:03] <murthy> yofel: 4. bzr push lp:~murthy/kubuntu-packaging/ktp-desktop-applets-ubuntu
[20:03] <yofel> murthy: hm, maybe it's because of the wrong project
[20:04] <murthy> yofel: wrong project?
[20:04] <yofel> telepathy-kde, not kubuntu-packaging
[20:04] <murthy> yofel: ok i will try that
[20:04] <apachelogger> sheytan: yeah, I mean the theme is fine for single user systems, and for large systems with the loginbox theme
[20:05] <sheytan> apachelogger: what about an 'other' option
[20:06] <sheytan> that will add a possibility to type your username
[20:06] <sheytan> and pass ofc
[20:06] <apachelogger> other?
[20:06] <sheytan> yeah
[20:06] <sheytan> then you get a user list of: FOO, GUEST, OTHER
[20:07] <sheytan> choosing other will bring up a textbox to input your username
[20:07] <apachelogger> ah
[20:07] <apachelogger> that'd would solve it indeed
[20:08] <apachelogger> very nice solution too
[20:08] <sheytan> see? :D
[20:08] <murthy> yofel: i think that was the issue
[20:08]  * sheytan thinks the wine helps with visions or somthing
[20:08] <murthy> yofel: how can i revert a revision?
[20:08] <murthy> yofel: the last commit
[20:09] <yofel> bzr uncommit
[20:09] <murthy> yofel: ok
[20:09] <yofel> or revert the change and commit agian
[20:09]  * sheytan will have the ubuntu ~760mb so in 10 minutes. His new ISP is great!
[20:27] <sheytan> apachelogger: made some time ago. U might like it http://2.bp.blogspot.com/_vNKxmokgKjU/TS9_1KwqP1I/AAAAAAAAB0g/24XanAp01pI/s1600/amarok.png
[20:35] <Darkwing> What's the KDE version being shipping with 13.04?
[20:35] <kubotu> ::qt-bugs:: [1129856] package libqtcore4 4:4.8.3+dfsg-0ubuntu3.1 failed to install/upgrade: trying to overwrite ... @ https://bugs.launchpad.net/bugs/1129856 (by Tom Plank)
[20:37] <yofel> 4.10.0 right now
[21:32] <murthy> shadeslayer: i have requested a merge for ktp-desktop-applets
[21:32] <murthy> yofel: the merge request is done
[21:33] <yofel> ack
[21:33] <murthy> yofel: thanks for your patience
[21:34] <yofel> sure, now it's shadeslayer's part :)
[21:34] <murthy> yofel: ya
[21:36] <murthy> yofel: can i package the items marked as to do in here? https://blueprints.launchpad.net/ubuntu/+spec/desktop-r-kubuntu-packaging
[21:37] <yofel> yeah
[21:39] <yofel> murthy: only the stuff marked as for kubuntu-dev though, and replace that with your own launchpad id
[21:39] <murthy> yofel: in the webpage?
[21:40] <yofel> yeah, see work items
[21:40] <yofel>  [kubuntu-dev] package kcm_touchpad and compare against synaptiks for default: TODO
[21:40] <murthy> yofel: ya
[21:41] <yofel> hm, where's that from o.O?
[21:41] <murthy> yofel: " investigate packaging" what does that mean?
[21:41] <yofel> whether it's doable or makes sense
[21:42] <murthy> yofel: ok
[21:45] <murthy> yofel:  I am going to try akonadi-social, i have to get the source from git master?
[21:46] <yofel> does it have a release?
[21:46] <murthy> yofel: checking
[21:46] <sheytan> is someone working on the user management kcm? The current one SUCKS :)
[21:47] <yofel> afiestas wrote something new
[21:47] <yofel> the current one is broken anyway
[21:50] <yofel> sheytan: it's user-manager in https://code.launchpad.net/~kubuntu-ppa/+archive/experimental/+packages if you want to try it
[21:52] <murthy> yofel: where can i get the source for akonadi-social
[21:52] <sheytan> yofel: great. i'm trying it now. Thanks!
[21:53] <yofel> murthy: good question
[21:54] <murthy> yofel: is this the package that contains it "libakonadi-socialutils4" ?
[21:54] <yofel> hm, could be
[21:55] <yofel> I'm not sure who put that TODO up
[21:55] <murthy> yofel: why?
[21:55] <yofel> dunno, that person should know
[21:56] <murthy> yofel: i guess that should be shadeslayer ?
[21:56] <yofel> what makes you think so?
[21:56] <murthy> yofel: it might be part of integrating kde-telepathy with akonadi
[21:57] <yofel> hm
[21:57] <yofel> well, don't ask me
[21:57] <murthy> yofel: ok, may be Riddell knows?
[21:57] <yofel> maybe
[22:02] <murthy> yofel: kdepimlibs contains libakonadi-socialutils4
[22:03] <yofel> sorry, I'm too tired right now to look at this
[22:03] <murthy> yofel: ok
[22:33] <yofel> hm, calligra's broken in raring
[22:34] <yofel> dpkg: error processing /var/cache/apt/archives/calligra-libs_1%3a2.6.1-0ubuntu1_amd64.deb (--unpack):
[22:34] <yofel>  trying to overwrite '/usr/lib/librcps_plan.so.11.0.0', which is also in package calligraplan 1:2.6.1-0ubuntu1
[22:51] <yofel> fixed for now
[23:45] <ahoneybun> hello people