[00:59] <JontheEchidna> inane error du jour: http://tinyurl.com/7u62bak v.v
[01:00] <JontheEchidna> turns out, function pointers are always nonzero :P
[01:06] <Jacky> always :P
[01:25] <JontheEchidna> I'll blame tab completion :P
[02:57] <ScottK> yofel_: Should be in main.
[03:07] <ScottK> yofel_: Being promoted.
[03:35]  * genii-around sips
[09:25] <CIA-42> [lp:~kubuntu-packagers/kubuntu-packaging/kde-workspace] Philip Muškovac * 640 * debian/ (changelog control) Switch boost build-dep to 1.49
[09:46] <apol> can anybody help me with this log? https://launchpadlibrarian.net/105030999/buildlog_ubuntu-precise-amd64.qapt_1.3.50-0~940~precise1_FAILEDTOBUILD.txt.gz
[10:17] <CIA-42> [lp:~kubuntu-packagers/kubuntu-packaging/kdepim-runtime] Philip Muškovac * 108 * debian/ (changelog control) Switch boost build-dep to 1.49
[10:19] <yofel_> apol: in libqapt1.install change usr/lib/libqapt.so.1.3.0 to 1.3.65
[10:20] <apol> hm
[10:20] <apol> thanks
[10:29] <ulysses> apol: a question: translations are imported to Muon Discover?
[10:31] <apol> ulysses: imported?
[10:32] <ulysses> apol: I installed Muon Discover from the PPA, and it is in English :( But I translated it to Hungarian
[10:33] <apol> ulysses: well, upload the .po files to the hungarian svn repository
[10:34] <apol> ulysses: in future versions the kde-l10n-hu package should provide it, I guess
[10:34] <ulysses> uploaded
[10:36] <apachelogger> technically speaking, since muon is extragear I suppose the translations would be in the muon tar ;)
[10:47] <apachelogger> afiestas: http://paste.kde.org/477938/ when unpluggin bluetooth adapter while scanning
[10:47] <afiestas> apachelogger: report a bug plz
[10:49] <apachelogger> no idea where, your application fails to give me a bug report button :P
[10:50] <afiestas> I don't see debug symbols installed 
[10:50] <afiestas> not one bd .cpp file in that bt
[10:50] <apachelogger> my application fails to find them :D
[10:50] <apachelogger> there is BlueDevil::Adapter::unregisterAgent though :P
[10:51] <afiestas> not useful
[10:51] <afiestas> what version are you using?
[10:51] <apachelogger> your application also fails to tell me that :P
[10:51] <apachelogger> you need a  khelpmenu somewhere, srsly
[10:51] <afiestas> dude
[10:51] <apachelogger> !info bluedevil precise
[10:51] <afiestas> check out the package you have installed
[10:51] <apachelogger> afiestas: what is this? 1990? :P
[10:52] <apachelogger> checking installed packages
[10:52] <afiestas> patches are welcomed
[10:52]  * apachelogger mumbles and scuttles off to *manually* search for dbg symbols
[10:52] <afiestas> you  should update yoru version
[10:52] <afiestas> to a supported one
[10:52] <afiestas> 1.2.3 
[10:53] <afiestas> fixed a few fixed in there, one related to unregisterAgent
[10:53] <afiestas> BUG: 298633 // Crash in kded daemon (ObexFtp module)
[10:53] <apachelogger> u telling me we have an unsupported version in a long term support release :O
[10:53] <afiestas> nd another one in libbluedevil 1.9.1 
[10:53] <afiestas> well not my fault
[10:53] <afiestas> I do maintain the 1.2 branch
[10:54] <afiestas> but kubuntu has not upgrade to 1.2.3 
[10:54] <apachelogger> I blame ScottK
[10:54] <apachelogger> blue* is imported from debian
[10:54]  * afiestas start packing, still in sfo
[10:55] <BluesKaj> Hey all
[10:56] <apachelogger> uhm
[10:56] <apachelogger> http://packages.debian.org/changelogs/pool/main/b/bluedevil/bluedevil_1.2.3-1/changelog
[10:56] <apachelogger> afiestas: so now I need to revise, not ScottK is to blame but Debian
[10:57] <apachelogger> ftp://ftp.kde.org/pub/kde/stable/bluedevil/1.2.3/src/
[10:57] <apachelogger> afiestas: and now not Debian is to blame but you :P
[10:57] <apachelogger> \o/
[10:57] <afiestas> ?
[10:57] <apachelogger> you releasing after us :P
[10:57]  * apachelogger runs a diff
[11:01] <apachelogger> afiestas: http://paste.kde.org/477956/
[11:01] <apachelogger> aren't you using releaseme? cause I don't think you need that with releaseme
[11:02] <apachelogger> the find_package stuff anyway
[11:16] <apachelogger> afiestas: debian decided to change the packaging ecessivley, so we probably need to manual update the package and sru it -.-
[11:50] <apachelogger> bulldog98_: i18n( "Install Mysqldump") that is terrible realy
[11:55] <apachelogger> bulldog98_: also I think mysqldump should be package separately
[11:55] <apachelogger> it appears to only link against low level libraries
[12:29] <Quintasan> Sup
[12:34] <BluesKaj> Din
[13:08] <Quintasan> Darkwing: ping
[13:15] <jovin> JonTheEchidna: muon 1.4 alpha looks awesome great job
[13:22] <jtechidna> jovin: thank apol too :)
[13:23] <jtechidna> but thanks :)
[13:26] <koolhead17> hellos all
[13:29] <jovin> jtechidna: ah of course both of you, i didnt know :)
[13:31] <apol> jtechidna, jovin \o/ :)
[13:34] <rbelem_> yofel, heya
[13:34] <jtechidna> lol: http://imgur.com/rJ6z0
[13:36]  * koolhead17 is still in hangover
[13:37] <ulysses> jtechidna: will Muon 1.3 alpha available on Oneiric?
[13:37] <ulysses> 1.4*
[13:38] <jtechidna> ulysses: I think the cyberspace ppa has daily snapshots for oneiric, but I don't plan to support anything past the current release + the development release for the QApt Experimental PPA
[13:38] <jtechidna> https://launchpad.net/~cyberspace/+archive/cyber-stuff?field.series_filter=oneiric
[13:39] <jtechidna> Package: /var/cache/apt/archives/libmuonprivate1_1.3.65-0ubuntu1~precise1_amd64.deb
[13:39] <jtechidna> Error: trying to overwrite '/usr/share/kde4/apps/muon-installer/categories.xml', which is also in package muon-installer 1.3.1-0ubuntu2
[13:39] <jtechidna> oops
[13:39] <jtechidna> dammit, I'll have to wait until I get home to fix that :(
[13:39] <Quintasan> jtechidna and apol: Yeah, good job on Muon, makes me use terminal a little bit less :P
[13:40] <jtechidna> :P
[13:40] <Quintasan> Now just somebody has to fix KMail once and for all
[13:40] <Quintasan> SHUT UP ALREADY WITH CANNOT APPEND FLAGS
[13:40] <apol> Quintasan: #kontact :D
[13:40]  * Quintasan purges kmail back to hell
[13:40] <ulysses> jtechidna: that doesn't contains my translation yet :( your packages in the QApt Experimental does
[13:41] <jtechidna> unfortunately I don't have the time necessary for maintaining packages for 3 releases :(
[13:42] <ulysses> I understand
[13:42] <Quintasan> What's the name for Q release?
[13:43] <jtechidna> Quantal Quetzal or something
[13:43] <Quintasan> Urgh
[13:43] <jtechidna> this thing: http://images.nationalgeographic.com/wpf/media-live/photos/000/006/cache/quetzal_675_600x450.jpg
[13:43] <Quintasan> They really want me to break my tongue
[13:43] <jtechidna> lol
[13:44] <koolhead17> haha
[13:45] <jtechidna> Muon 1.4's codename is Energetic Elemental, after the creatures from this Dr. Who episode: http://tardis.wikia.com/wiki/Love_%26_Monsters :D
[13:45] <jtechidna> in keeping w/ the Doctor Who codename tradition ;-)
[13:45] <Quintasan> If QQ is supposed to be quantal, how do we do it?
[13:45] <Quintasan> Release and don't release at the same time?
[13:45] <jtechidna> lol
[13:46] <jtechidna> we could start another rumor about a rolling release :P
[13:46] <Quintasan> NO
[13:46] <jtechidna> haha
[13:46] <Quintasan> EVERYTHING BUT NOT ROLLING RELEASE
[13:46] <Quintasan> I'm getting out of here if we switch to rolling
[13:46] <apol> what's wrong with rolling?
[13:46] <apol> (just asking)
[13:47] <Quintasan> What's wrong with stable and current devel release separation?
[13:48] <Quintasan> jtechidna: Maybe we announce that we switch to emerge?
[13:48] <Quintasan> :P
[13:48] <apol> doesn't benefit from projects that release-soon-release often
[13:49] <Quintasan> apol: no qa on rolling
[13:49] <Quintasan> who can guarantee that release-soon, release-often is better?
[13:49] <Quintasan> I prefer to have some testing done instead of PACKAGE ALL THE VERSIONS
[13:50] <apol> well that works for the OS if you want
[13:50] <apol> but there's little advantage in packaging only the last version of, let's say, digikam before the last release xD
[13:51] <Quintasan> jtechidna: Who is going to make some todos from uds discussion?
[13:51]  * Quintasan pokes apachelogger
[13:52] <Quintasan> or Darkwing
[13:52] <Quintasan> Muahahahaha
[13:52]  * Quintasan digs trough his basement looking for Might Stick of TODO Creation
[13:53] <Quintasan> s/Might/Mighty
[13:57] <ximion> JontheEchidna: ping
[13:58] <jtechidna> ximion: pong
[13:58] <jtechidna> (JontheEchidna is my laptop which is at home right nwo)
[14:01] <ximion> jtechidna: ah, makes sense! :) I wanted to ask you a few questions about QApt/Muon and the relation to PackageKit...
[14:02] <ximion> first of all, I'm doing a GSoC on AppStream, the underlying distro-agnostic technology for the Ubuntu Software-Center, which is also used on other distributions.
[14:03] <ximion> I'm driving the implementation at Debian and a (possible) update of some background stuff on Ubuntu too, but apt and the repository format will first need some changes for that. (will probably be finished with the end of this year)
[14:03] <ximion> the GSoC project is for OpenSUSE, btw.
[14:03]  * jtechidna nods
[14:04] <ximion> now, Muon has a very nice software-center-like feature, which uses the same AppStream infrastructure available on other distros too (only few changes necessary, which Ubuntu will do too, later)
[14:05] <ximion> it also ships an own Apt transaction daemon, the qapt-worker.
[14:05] <ximion> it would be awesome to make at least the MSC cross-distro using PackageKit.
[14:06] <ximion> right now, PK has some API missing, we're currently planning the changes so e.g. fetching package lists will be faster in future.
[14:06] <ximion> so, would you allow porting parts of Muon to PK, where it makes sense, so other distributions can use the software too?
[14:07] <ximion> (please remember that this is a long-term goal, won't happen now since I first have to fix the USC fork to use PK)
[14:07] <ximion> jtechidna: ^
[14:07] <apol> ximion: where are AppStream servers?
[14:07] <apol> as in, for reviews and all
[14:08] <ximion> apol: distributions provide the necessary data by themselve
[14:08] <jtechidna> So let me start off by saying that I would like to see Muon integrate in with AppStream to some degree
[14:08] <jtechidna> in terms of the flowchart here: http://gitorious.org/appstream/resources/blobs/raw/master/architecture.png
[14:08] <ximion> for the review stuff, a cross-distro solution is planned, but nobody has taken the task yet
[14:08] <jtechidna> I could see Muon/QApt implementing the "client" section
[14:08] <jtechidna> adding support for additional reviews/ratings backends shouldn't be too hard given the current setup
[14:09] <jtechidna> and getting the app data from an external server as opposed to the current app-install-data package shouldn't be too hard
[14:09] <ximion> just for information: http://distributions.freedesktop.org/wiki/AppStream/Implementation (how AppStream works)
[14:09] <jtechidna> But I'm not too convinced that swapping out QApt for PK is in the best technical interest of the project.
[14:09] <ximion> http://wiki.debian.org/AppStreamDebianProposal (what is planned to make it work easily on any Debian repository)
[14:10] <apol> ximion: what's supposed to be in app-data.xml?
[14:10] <jtechidna> apol: it's analagous to the flat files that we use from app-install-data
[14:10] <apol> jtechidna: I thought so
[14:10]  * apol thinks that AppStream is reinventing the wheel
[14:11] <ximion> apol: see http://gitorious.org/appstream/resources/blobs/master/appdata.xml (but at Debian, we will use a different format than XML, where ftpmasters are happier with - what matters in the end is the Xapian database)
[14:12] <ximion> apol: AppStream is essentially a cross-distro version of what Ubuntu has today, with some extras. Ubuntu people were at the meeting, so AppStream is heavily influenced by them, of course ^^
[14:12] <jtechidna> With some work, I could see the qaptworker providing at least a limited PK-like API
[14:12] <jtechidna> sort of like aptdaemon is currently doing
[14:12] <ximion> jtechidna: please, please don't do that! It's already causeing much pain for me with PK :)
[14:12] <apol> ximion: I think that from the muon PoV we could start collaborating by being compatible with AppStream reviewing services
[14:12] <ximion> jtechidna: What are your concerns about PK?
[14:13] <jtechidna> ximion: well, for one thing, it will never be too terribly fast due to everything going through DBus
[14:13] <apol> ximion: the concern is that what we have works great
[14:13] <apol> +1
[14:13] <apol> :P
[14:13] <ximion> apol: In fact, it should already be ^^
[14:14] <apol> ximion: if you give me a reference server, I probably can adapt Muon myself to target it in my work time
[14:14] <ximion> jtechidna: You could for example replace the QApt-worker with PK without loosing any functionality, but sharing more code with PK. The PK daemon would take modify-tasks over DBus and do exacly the same as the current QApt-daemon does
[14:14] <jtechidna> ah, hmm. hadn't thought about that
[14:15] <ximion> regarding the other speed-limits, you're right, that's why future PK versions will be able to access backends without DBus, but that's not yet implemented
[14:15] <jtechidna> ximion: does the aptcc backend currently support specifying package versions?
[14:15] <jtechidna> e.g. for downgrading
[14:16] <apol> ximion: what do we win by having half libqapt relying on apt for some features and pk on other?
[14:17] <jtechidna> Muon would still have to rely on APT and wouldn't be cross platform
[14:17] <ximion> apol: Removing code-duplication by using PK, avoiding running another package-management daemon in background (I got bug reports from users running three (!) at the same time), implementation of PackageKit API for free.
[14:17] <jtechidna> *cross distro
[14:19] <jtechidna> btw, the qaptworker doesn't run all the time
[14:19] <jtechidna> it times out after 30 seconds of inactivity
[14:19] <ximion> jtechidna: yes, but we'd have the benefits mentioned above, and it would be easier to make it cross-distro. Muon itself can't be cross-distro and shouldn't be, e.g. because it can target specific Apt features (like pinning) then. - But the MSC could be cros-distro, as it does not rely on advanced functionality, like Muon does.
[14:20] <ximion> jtechidna: so does PK, so does Aptd - the user I'm talking about used Muon, a PK-relying application (PK is used be many apps now, at least on Debian) and the USC at the same time :P
[14:20] <jtechidna> currently MSC does use libqapt functions for getting information about the underlying packages. (Version, file size, etc)
[14:21] <jtechidna> so it's not that simple to just not use libqapt for that
[14:22] <ximion> jtechidna: We'd need the new, planned PK functions for that to replace libqapt there.
[14:22] <ximion> this is @work, I just want to check the general possibility of doing this :P
[14:23] <ximion> because right now, having aptd, PK, and Qaptd around is not optimal...
[14:23] <ximion> and even PackageKit has two backends for Apt
[14:24] <ximion> (where aptcc is the better (and faster) one right now)
[14:24] <jtechidna> well, to be fair nobody uses the python apt one :P
[14:24] <jtechidna> that one is broken as heck
[14:25] <ximion> it was even removed, because it was abandoned - all Ubuntu developers did aptd then.
[14:25] <jtechidna> I think we could definitely commit to using the OCS Reviews and Ratings API as an alternate (perhaps even default?) backend, as well as the metadata sourcing system.
[14:25] <ximion> but suddenly, they were back, made a huge set of commits and then vanished again (for months now)
[14:25] <jtechidna> But sharing worker implementation will require more discussion
[14:26] <ximion> jtechidna: I think PK can cover 98% of current qapt worker already, for the other stuff, we can discuss :)
[14:27] <ximion> PK will now get a sqlite cache, to make accessing the package-information faster and to benachmark backends, then we'll go for "PK2", when Richard has some more time again.#
[14:29] <ximion> for other parts of Muon, you don't need much changes. AppStream is nearly the same as current Ubuntu implementation is, and mvo will make it more AppStream-like during the next releases.
[14:29] <jtechidna> I should note that Muon currently does not have a strong Xapian backend for retreiving pkg information
[14:29] <jtechidna> it only uses Xapian for package search
[14:30] <ximion> jtechidna: How does it fetch the application data then?
[14:30] <jtechidna> ximion: via libapt-pkg
[14:31] <ximion> ah, okay :)
[14:31] <jtechidna> https://projects.kde.org/projects/extragear/sysadmin/libqapt/repository/revisions/master/entry/src/package.cpp
[14:32] <jtechidna> basically libapt-pkg mmap's a large (15 or 30 MB, depending on whether you're 32 or 64 bit) file in to memory that contains the info for all the packages
[14:32] <jtechidna> and uses pointers and iterators to access information 
[14:32] <ximion> hmm... I'll suggest another AppStream meeting (maybe not in person but in IRC) to discuss the current state - there are many things which are unclear and the goal "ship something with the end of December" hasn't been reached too :P
[14:32] <jtechidna> very fast, once you've actually mmap'ed the file :P
[14:33] <ximion> hehe ^^
[14:33] <apol> ximion: i'd be intrested in attending such meeting
[14:33] <jtechidna> that takes around 1 or 2 seconds at application startup ^.^
[14:33] <ximion> I like QApts code very much, btw. - given the horrow Apt's API is, it lokks very clean and is super-easy to read :)
[14:33] <jtechidna> ;-)
[14:33] <jtechidna> I'm very proud of it
[14:34] <apol> +1
[14:34] <apol> kudos for jtechidna :)
[14:34] <jtechidna> though there are definitely things I'd like to change <.<
[14:34] <jtechidna> like this abomination: https://projects.kde.org/projects/extragear/sysadmin/libqapt/repository/revisions/master/entry/src/package.cpp#L1088
[14:34] <jtechidna> lol
[14:34] <apol> :P
[14:34] <ximion> Apt has the worst API I've ever seen, so this QApt is indeed a great thing to have.
[14:35] <jtechidna> I wrote that after I discovered QHash, and went "Use QHash for EVERYTHING!"
[14:36] <jtechidna> http://www.quickmeme.com/meme/3pa44v/
[14:36] <ximion> ^^
[14:36] <apol> :)
[14:37] <ximion> apol: I can tell you when we discuss the matter :)
[14:37] <ximion> would be cool to get the team back together and some new people too - especially from QApt/Muon
[14:38] <ximion> and as soon as PK-with-less-DBus is ready, implementaing Software-Centers with PK should be a trivial thing.
[14:39] <ximion> for my GSoC on SC, I use a not very nice workaround.
[14:39]  * apol doesn't really like such "when it's ready it will be awesome"
[14:39] <apol> because it doesn't always happen
[14:40] <apol> let's focus on what we have working at the present at any moment and keep iterating forward
[14:42] <ximion> apol: that's the plan
[14:42] <ximion> and since I want a working SC with the end of my project, I will now implement an ugly solution to be able to switch to the better one when it's ready
[14:44] <jtechidna> So on a slightly-related note, I was thinking that the Qt4 -> Qt5 transition might be the perfect excuse to break ABI/ABI and do a QApt2.
[14:44] <jtechidna> If you've looked in the code, you can probably see that I've written some notes about API that I'd like to change for a QApt2.
[14:44] <jtechidna> But I think that it would be beneficial to get an API review with a few more heads than my own
[14:47] <jtechidna> A 'grep -iR QApt2 src/' should show all of my notes :)
[14:49] <jtechidna> oh, and this isn't mentioned in the source code, but the QApt Worker API needs a bit of rework.
[14:50] <jtechidna> all of the functions that start processes where the worker and frontend communicate should return dbus objects which can be monitored for dbus signals. (Kind of like aptdaemon does now)
[14:50] <jtechidna> currently all signals are outputted on the main qaptworker dbus bus
[14:50] <jtechidna> which means that all open applications that can communicate with the qaptworker will recieve them. :(
[14:51] <jtechidna> that's probably the biggest design problem with the library at the moment, which has to be worked around with considerable effort in the frontends
[14:52] <jtechidna> I should set up a wiki page or something for an API review
[14:55] <apol> jtechidna: yep, Qt4->Qt5 will break ABI anyway, so yes it makes sense
[15:00] <jtechidna> We'll definitely want to not go too wild with changing API. While Muon is the biggest consumer of the LibQApt API, there are some other things using it.
[15:01] <jtechidna> IIRC there's some small Ubuntu derivative using it to develop a Qt package manager
[15:02] <jtechidna> and some other users include the GRUB2 KCM and the Kubuntu debug installer plugin for Dr. Konqi
[15:07] <apol> :)
[15:09] <jtechidna> but the good thing is that I don't think we'll have to change too much
[15:14] <jtechidna> oh btw, I was also able to find out how the Ubuntu Software Center populates its "For Purchase" origin: http://software-center.ubuntu.com/api/2.0/applications/en/ubuntu/precise/i386/
[15:15] <jtechidna> since they're ever so good at making their API publicly visible :P
[15:16] <jtechidna> While I feel there's definitely less impetus to implement support for their AppStore API now that we aren't an official Canonical Ubuntu flavor, I think that having support there would still be nice.
[15:17] <jtechidna> I don't know if Blue Systems would take an interest in implementing the API, but it's quite similar to the reviews API and it uses the Ubuntu SSO which we can now do in Muon, so I'd be willing to give a shot at implementing it
[15:28] <ronnoc> jtechidna: Congrats on the new Muon Suite release! When updating 12.04, I get this error, first by standard upgrade (within Muon) and also in terminal with -f flag. Ideas? http://paste.kde.org/478226/
[15:28] <jtechidna> ronnoc: unfortunately a result of me not testing the packages
[15:29] <jtechidna> run sudo dpkg -i --force-overwrite /var/cache/apt/archives/libmuonprivate1_1.3.65-0ubuntu1~precise1_amd64.deb
[15:29] <jtechidna> you'll also need to do /var/cache/apt/archives/muon-installer_1.3.65-0ubuntu1~precise1_amd64.deb if my memory serves
[15:30] <jtechidna> anways, I'm off to lunch, and afterwards I do have some $WORK stuff to do so I'll get off of IRC (well, idle, but yeah)
[15:31] <ronnoc> jtechidna: ok thanks :)
[15:31] <yofel> jtechidna: btw. could you integrate adding the dbgsym sources to the kubuntu debug installer? Or would that be too invasive? (maybe add, install, remove again?)
[15:32] <jtechidna> yofel: it'd require some code for adding the dbgsym repo, running an update, searching for the package, removing the repo afterwards
[15:32] <jtechidna> so it's doable
[15:32] <jtechidna> it just hasn't been don eyhet
[15:32] <jtechidna> *done yet
[15:33] <yofel> ok, was just curious if it's doable or total nonsense
[15:33] <jtechidna> it's not exactly trivial, but it's not insane either
[15:46] <CIA-42> [lp:~kubuntu-packagers/kubuntu-packaging/kdemultimedia] Philip Muškovac * 153 * debian/ (changelog libkcddb4.symbols) * Update symbol files for gcc 4.7
[16:46] <CIA-42> [lp:~kubuntu-packagers/kubuntu-packaging/kdepim] Philip Muškovac * 203 * debian/ (changelog control) * Switch boost depends to 1.49
[17:08] <CIA-42> [lp:~kubuntu-packagers/kubuntu-packaging/smokekde] Philip Muškovac * 23 * debian/changelog releasing version 4:4.8.3-0ubuntu1
[17:14] <eagles0513875> hey yofel :) 
[17:14] <yofel> o/
[17:14] <Peace-> razor is in the repos ?
[17:14] <Peace-> i guess no
[17:15] <eagles0513875> btw yofel my bug Darkwing is going to help me fix it :) maybe ill learn a few things :) 
[17:16] <yofel> Peace-: it is
[17:16] <Peace-> yofel: razor-qt sorry
[17:16] <Peace-> :D
[17:16] <Peace-> i mean http://nowardev.wordpress.com/2011/12/16/light-qt-destkop-ex-antico-razor-qt/
[17:18] <Peace-> yofel: btw on unity there is a shortcut to open unity menu  with super key
[17:18] <Peace-> on kubuntu shoudl be the same 
[17:19] <Peace-> i managed to get it but it seems with some problme 
[17:20] <yofel> well, problem is that you can't use Meta by itself as a shortcut, it's a modifier
[17:20] <yofel> and I haven't managed to set a single key shortcut for kickoff so far
[17:21] <Peace-> yofel:  i did it
[17:22] <Peace-> yofel: http://nowardev.wordpress.com/2012/05/06/kde-laucher-set-superkey-lke-shortcut/
[17:22] <Peace-> but i have a problem anyway
[17:49] <CIA-42> [lp:~kubuntu-packagers/kubuntu-packaging/kdeadmin] Philip Muškovac * 150 * debian/changelog releasing version 4:4.8.3-0ubuntu1
[18:17] <CIA-42> [lp:~kubuntu-packagers/kubuntu-packaging/kdeartwork] Philip Muškovac * 139 * debian/changelog releasing version 4:4.8.3-0ubuntu1
[18:48] <nixternal> ^^ why isn't a hook used that when you commit, or better yet, tag, add 'release:precise' to change debian/changelog automagically instead of manually doing it each time?
[18:50] <yofel> I've a script that does that :P
[18:50] <nixternal> locally?
[18:51] <yofel> yeah (that's a local hook anyway, launchpad has no CIA support)
[18:52] <nixternal> you can't add a hook to the bzr server that takes care of it server side? with your script, after it triggers the release:precise, you sill have to do another commit right?
[18:53] <yofel> well, as I need to testbuild before uploading, I need to edit the changelog anyway to create the source package. If it builds fine I let my script commit, tag and upload
[18:54] <yofel> and there's a bug about CIA support, that's about as cooperative the launchpad folks will get
[18:55] <nixternal> ahh, that sucks, though i could care less about cia
[18:55] <yofel> shadeslayer: you were looking for fun build failures, enjoy: http://paste.kde.org/478406
[19:39]  * highvoltage adds #kubuntu-devel to autojoin to keep up to date with tablet stuff :)
[19:46] <shadeslayer> yofel: I don't see the error, needs more backlog :P
[19:47] <shadeslayer> unless that's the only error message you get
[19:47] <shadeslayer> then it's just plain weird
[19:47] <yofel> shadeslayer: that *is* the error, but here the full log http://paste.ubuntu.com/987758/
[19:49] <shadeslayer> ...
[19:50] <shadeslayer> firefox just froze up when I tried to use Find on that page
[19:50] <CIA-42> [lp:~kubuntu-packagers/kubuntu-packaging/kdeplasma-addons] Philip Muškovac * 202 * debian/ (changelog control) * Switch boost build-dep to 1.49
[20:33] <CIA-42> [lp:~kubuntu-packagers/kubuntu-packaging/kdesdk] Philip Muškovac * 166 * debian/ (changelog control) * Switch boost build-dep to 1.49
[20:34]  * JontheEchidna is now home
[20:53] <JontheEchidna> blog post without screenshots on April 26th vs. blog post with screenshots today: http://i.imgur.com/1v5T0.png
[20:53] <JontheEchidna> :P
[20:54] <JontheEchidna> people love teh screenies
[20:56] <debfx> next time you'll have to create some gif images for even more hits
[21:00] <yofel> all is fine as long as you don't use flash :D