=== jackyalcine_ is now known as jalcine [05:06] Riddell: yes [05:07] I rage quit last night, got too annoyed :P [05:08] next UDS in Oakland, CA [05:35] I'm as excited about going there again as I was the first time. [05:40] I'm guessing that code for "Not alot" [05:40] *thats [05:43] Yes. [06:31] hello everyone [06:32] hi phoenix_firebrd [06:32] shadeslayer: good morning [06:32] good morning to you as well :) [06:38] who can test some precise stuff? [06:39] X fails on precise when using qemu :( [06:39] and bug 1093220 needs verification [06:39] bug 1093220 in transmission (Ubuntu Quantal) "[SRU] Fix transmission-qt to open magnet links from a browser" [Undecided,Fix committed] https://launchpad.net/bugs/1093220 [09:12] ScottK, bug 1066225 has a new comment for you [09:12] bug 1066225 in ubiquity (Ubuntu) "encrypt home folder needs to be checkbox not radio button" [Medium,Fix released] https://launchpad.net/bugs/1066225 [09:29] does it make sense to encrypt the home folder and have autologin enabled? [09:30] I mean, the entire point of having encrypted data is that if someone gains physical access to your machine your data is safe ( assuming they cannot crack the key ) [09:33] shadeslayer: in that case using kwallet is also vulnerable [09:33] not exactly, your kwallet password is not associated with your login password [09:34] * shadeslayer uses crazy levels of encryption [09:35] I have full disk encryption as well as /home encryption setup [09:36] shadeslayer: ya, thats right, but why kwallet manager doesnt seek password when kwallet was opened previously for other use [09:36] shadeslayer: I dont encrypt my disk , because i am afraid i may not be able to recover data in case of a filesystem error [09:37] yep, that's a huge issue [09:37] which is why, unencrypted backups [09:37] which travel with me :P [09:37] shadeslayer: thats a vulnerability :) [09:38] I know :) [09:38] the biggest risk is my ssh and gpg keys, which do not have a backup [09:38] primarily because I have no good way to back them up [09:38] shadeslayer: "donot ask password" for screen locker is not working? [09:38] whut [09:41] shadeslayer: is the new screen locker working for you? [09:41] sure [09:41] ctrl-alt-l locks the screen [09:41] that's about all I tested [09:41] shadeslayer: does it ask for the password everytime? [09:41] well [09:42] that's intended behaviour [09:42] shadeslayer: no [09:42] I specifically asked it to lock the screen, so it should ask my password [09:42] what else would it do [09:43] shadeslayer: "the option require password after" is disabled for me and it asks for the password after i immediately try to unlock [09:43] let me confirm it one more time [09:44] where is this option? 0..o [09:44] screensaver === yofel_ is now known as yofel [09:44] screen locker [09:45] oh, they renamed the menu [09:45] shadeslayer: inside display and monitor settings [09:45] shadeslayer: i am using 12.10 [09:45] yofel: hi [09:45] hey [09:46] yofel: today 4.10 sc tagging? [09:46] phoenix_firebrd: anyway, I did notice there was somthing funky about that menu [09:46] I have no idea where this kcm is [09:46] yofel: menu? [09:46] give me the kcm module name [09:46] shadeslayer: no idea, but it's in the display settings [09:46] shadeslayer: can the see the display and monitor settings? [09:47] phoenix_firebrd: well, that was the screensaver kcm before [09:47] this ? http://i.imgur.com/BHRRto0.png [09:47] right [09:47] disable the 2nd checkbox [09:47] I think it has no effect [09:47] shadeslayer: thats it [09:47] or at least it doesn't work reliably [09:47] funny thing [09:47] shadeslayer: the second options is the one i am talking about [09:47] click "Screen Saver" [09:47] but I know they fixed a bunch of locker issues recently [09:48] and the monitor turns blue [09:48] click "Simple locker" and it stays blue [09:48] true o.O [09:48] heheh [09:48] phoenix_firebrd: http://mail.kde.org/pipermail/kde-cvs-announce/2013/000105.html [09:48] iirc tagging freeze is in effect no? [09:48] so work starts tomorrow [09:49] I'll fire the cronjob up later for the stats [09:49] it is [09:49] shadeslayer: but who cares about it? [09:49] well [09:49] tsdegos got pissed when I merged to okular extractor [09:49] so I'm not going to piss him off again :P [09:49] I'll just file a bug [09:49] heh [09:50] ok [09:56] yofel: In case my project is using automake i wont be needing to add rules for clean, build and install in debian/rules right? [09:56] ok wait, I'll elaborate on that [09:57] you know how gnu make works? (roughly?) [09:57] yofel: cmake configures with the make files and make buuilds the project with that [09:57] what was the Product for the screenlocker again :| [09:57] :) [09:57] shadeslayer: kscreensaver I believe [09:58] thx [09:58] phoenix_firebrd: ok, so let's talk about make first [09:58] yofel: ok [09:58] phoenix_firebrd: make is originally meant for building source code. It's usefullness comes from being able to determine what files have changed and only rebuilding what needs to be built [09:59] ok [09:59] it does that by defining make "targets" that have dependencies and commands that are needed to build it [09:59] yofel: wait [09:59] targets is key waord? [10:00] targets is key word? [10:00] no [10:00] yofel: the output? [10:00] a target is something like: [10:00] targetname: dep [10:00] commandlist [10:00] yofel: give me an example [10:01] done, kde bug 314122 [10:01] KDE bug 314122 in locker "Monitor is not turned 'off'" [Normal,Confirmed] http://bugs.kde.org/show_bug.cgi?id=314122 [10:01] phoenix_firebrd: http://paste.kde.org/659828 [10:02] phoenix_firebrd: so to build the "build" target, the configure target has to be finished [10:02] yofel: ok [10:03] now, the reason I run "touch" there, is because usually the targets are the filenames of the source you want to build [10:03] so if a file changes, it's target and all targets that depend on it will run [10:03] that's how make works... roughly [10:03] yofel: doubt [10:03] hm? [10:05] yofel: if you say that this is the label that points to build "build:" then what does this do "DEB_MAKE_BUILD_TARGET:" ? [10:05] what's DEB_MAKE_BUILD_TARGET? [10:05] just going by make syntax, DEB_MAKE_BUILD_TARGET would be the name of the target [10:06] i.e. the name would literally be "DEB_MAKE_BUILD_TARGET" [10:06] yofel: can you pulll-lp tomboy-blogposter [10:07] oh, :=, that's a variable definition, but we'll come to that ^ example in a bit [10:07] now back to rules [10:07] yofel: ok' [10:08] hehehe [10:08] yofel: http://pike.psu.edu/dongwon/pro/grannies.pdf [10:08] shadeslayer: o.O (I'll read it later...) [10:09] shadeslayer: in US too? [10:09] phoenix_firebrd: it's a worldwide phenomenon [10:09] ha ha ha [10:09] phoenix_firebrd: so, as making deb packages is a slighly complex process, we have a program called debhelper with perl scripts called dh_* that does most of the work for us [10:09] ok [10:10] phoenix_firebrd: back in dh 6 and early 7 days, a rules file would look like this: http://paste.kde.org/659858 [10:10] * shadeslayer is scared to click that link [10:10] which is gnu make taken too perfection [10:10] oh heh [10:10] shadeslayer: it's a clean rules file, nothing scary ;) [10:10] btw you should show him a cdbs file [10:10] shadeslayer: that's next [10:10] :D [10:10] shadeslayer: as his example above uses that :P [10:11] I joined just as cdbs was dying [10:11] trolololol [10:11] phoenix_firebrd: so, as you can see it's not really the most easiest, not the most readable way of doing it [10:11] phoenix_firebrd: + you had to be very careful to not mistake the sequencing [10:11] phoenix_firebrd: to help with that people went and wrote supplementary build systems, like cdbs [10:12] came across that [10:12] phoenix_firebrd: if you look at your tomboy rules, you'll see that it has include /usr/share/cdbs/1/rules/... [10:12] so it uses cdbs [10:12] ScottK: your sync is bad : https://launchpad.net/ubuntu/+source/pyside/1.1.2-1 [10:12] wait, checking [10:12] makes pyside completely disappear for some reason [10:12] the advantage: the sequencing is done in the build system, and you just have to set some configuration variables like DEB_MAKE_BUILD_TARGET [10:13] phoenix_firebrd: which makes rules a lot simpler as you can see [10:14] ok [10:14] yofel: where to specify the type of build system/version i am using [10:15] by "include"-ing the buildsystem makefile you want to use [10:15] now, next [10:15] ok [10:16] since debhelper 7.0.51 or whatever, debhelper got it's own auto-sequencer called "dh", which is what's most people use today [10:16] argh [10:17] those are perl scripts right? [10:17] yofel: ^ [10:17] ah wait, a bit of clarification [10:17] consistent LO crashing, and calligra screws up the formatting :( [10:17] even cdbs used those scripts [10:17] it's just the content of the makefile that you saw above ^ [10:18] that was moved to the build system, so you don't need to write the build: install: etc. targets [10:18] ok [10:18] debhelper provided the dh_install, dh_auto_configure, and whatever else scripts [10:18] and it does today too [10:19] with dh7, we gained a "dh" script, which does the sequencing of the rules file inside debhelper [10:19] so most rules file's today look like this: http://paste.kde.org/659864 [10:19] yofel: so if i am not using cdbs i dont need install: build: .. in rules ? [10:19] if you use cdbs you don't need it [10:19] the long rules example I showed above was a dh6 example without any build system [10:20] tomboy uses a cdbs file [10:20] http://paste.kde.org/659864 is modern dh7 style [10:20] yofel: the version 0.4.4 changed to automake so the rules have to be updated , probably the cdbs have to be removed [10:20] not really, cdbs and automake are 2 different thigns [10:21] for now I'm not going to talk about autotools [10:21] back to dh7 [10:21] yofel: this is the min that has to be in the rules file for the new type http://paste.kde.org/659864 ? [10:21] \o/ objcopy:debian/firefox/usr/lib/firefox/libxul.so[.debug_info]: Memory exhausted [10:22] I guess I'll just upload it to the PPA and fix [10:22] yes, unless you need adjustments for the package, that alone will already work [10:22] ok [10:22] phoenix_firebrd: so, as you saw in the dh6 example, rules was a long list of dh_* commands [10:23] in dh7, "dh" runs those commands, so we don't need to write them ourselves [10:23] yofel: dh6= http://paste.kde.org/659858/ ? [10:23] yes [10:23] ok [10:23] now, if we need to tell one of those commands that we need to do something different [10:23] yofel: overriding ? [10:23] like, dh_clean needs to remove a few more files [10:24] we'll override the command right [10:24] like this: http://paste.kde.org/659870 [10:25] yofel: who decides what to be put in ch_clean, the original maintainer or the packager? [10:25] yay [10:25] I have more bandwidth now [10:25] that essentially replaces the "dh_auto_clean" command in dh, with the list of commands inside the override target [10:25] 2 Mbps [10:25] *dh_clean [10:25] (that's why you're calling dh_auto_clean there too) [10:25] * shadeslayer downloads shank [10:26] an empty override_dh_auto_clean: target would simply disable dh_auto_clean [10:26] (we often do that for dh_auto_test ;) ) [10:26] ok [10:26] junk is a user variable? [10:26] phoenix_firebrd: any packager that works on the package may change the rules file as needed [10:27] phoenix_firebrd: well, it's something, maybe the program makefile creates it. but dh_auto_clean has a fixed pattern that it deletes [10:27] so if you need to remove anything else you need to tell it to [10:28] junk is a keyword? [10:28] phoenix_firebrd: for packaging, you're free to change what you want, but if the package has a maintainer that's not you, do talk to that person/team whether your changes are fine and ask for a review [10:28] phoenix_firebrd: no, junk is a filename, this is literally "rm junk" in your shell [10:28] inside a make target you define simply shell commands [10:29] oh ok [10:29] ok [10:29] type dh_ in your shell, you'll see all of the debhelper stuff [10:29] as those are simply exectuable perl scripts [10:29] checking [10:29] got a list [10:29] nice [10:30] ok, so that's the basics of rules that you see today, dh6 style is deprecated. If you don't need anything else use the simple dh7 style [10:30] so it is necessary to specify the debhelper version >=7 right? [10:30] if you still need something special that dh7 can't do, or is hard to use for, you another buildsystem [10:31] for example our KDE SC packages use the "dhmk" build system from pkg-kde-tools [10:31] what is script-kiddy? [10:31] phoenix_firebrd: that, and you'll need to put the version of debhelper your packaging works with into debian/compat [10:32] yofel: wait [10:32] phoenix_firebrd: it's a script for translations stuff [10:32] yofel: ok [10:32] yofel: ok [10:33] what is debian/source/format for? [10:33] read the manual :P [10:33] ok [10:34] just this once, where can i specify the quilt version tghat i am using? [10:34] you don't specify a quilt version [10:34] quilt is version agnostic? [10:35] shadeslayer: the tutor said something about that yesterday [10:35] let me check [10:35] can you grab me a quote? [10:36] er, you don't need to do that these days usually [10:36] thats it ,its the debian/source/format [10:36] ahhh [10:36] there is one release that needs a manual quilt dep for 3.0 quilt and where lintian throws a warning if the version is missing [10:36] okay so there are 2 formats, native and quilt [10:36] * yofel passes the micro to shadeslayer [10:37] need to do something else for a while [10:37] the format file is to specify which format dh will use [10:37] micro? :P [10:37] keyboard [10:37] format of? [10:37] voice, whatever :P [10:37] micro keyboard? [10:37] haha [10:37] lol [10:39] phoenix_firebrd: format of source package [10:39] phoenix_firebrd: format of the source package [10:39] anyway, dpkg-source manpage explains all formats too. (ignore 2.0, that's not used) [10:39] :P [10:40] "Also known as wig&pen." [10:40] hehehe [10:44] So we are all aware the kde dalogs induce a nice LO crash? or was it only on 4.9.4 ? [10:44] shadeslayer: are you working form a desktop or a laptop? [10:44] laptop [10:45] shadeslayer: ok [10:47] yofel: does your pbuilder check for updates everytime? [10:47] yes [10:48] if you're really low on bandwidth you can disable that [10:48] remove the executable bit from the 2 apt hooks [10:48] but then remember to keep your raring pbuilder updated [10:48] yofel: sure [10:49] yofel: do we have a kcm that is python3? [10:50] no idea, we couldn't really test that witout a working kcm backend... [10:50] lol? [10:50] python3 randomfile.py [10:50] ? [10:50] if nobody ported one, then no [10:51] I tried myself on synaptiks, but that didn't go too well [11:04] oh [11:05] yofel: got time to recompile pykde? [11:16] on which system did I work on the broken kcm Oo [11:17] my workstation does not even have pykde > 4.9 [11:20] hello world, I just received an update for jockey, and I was just curious, what's new in it? I think I remember seeing in the kubuntu devel mail list that jockey is to be replaced by something else. Is that true? If yes, how's that going? [11:21] JontheEchidna ^^ [11:22] yofel: http://paste.kde.org/659936/ [11:22] I'd first run that by someone who cares, the global interpreter lock thing makes no sense to me [11:22] though that patch definitelyw orks [11:22] found the right VM again [11:35] apachelogger: I'll try that once I'm at home, here I'm on quantal [11:37] one sugestion: can it be implemented in the Kmenu, on the bottom right, next to the kubuntu logo to also say the kubuntu version? it would be a lot easier for new users to figure this out [11:38] Riddell: good morning [11:40] Riddell: been thinking about the cantata "not is users group" message, personally i think it should stay, being in that group does have it benefits, however if you don't want/need to be in it, tick the box and hide the message [11:41] hi vassie, ok you're the packager :) [11:41] Riddell: :) [11:42] ovidiu-florin: yes I'd be interested in something like that but probably not somewhere as intrusive as the kmenu [11:42] vassie: did you look at a watch file? [11:42] Riddell: still not sure what to do with the watch file [11:42] make one that points at the download page [11:42] and put it where? [11:43] is there an example of one i can use? [11:43] vassie: I suggested owncloud [11:44] from the deb? [11:44] apt-get source owncloud [11:46] ok, got it, do i need to modify it and rebuild my package? [11:46] just a random suggestion though, you might want to look at a package which is hosted on google code [11:46] modity it and test it :) [11:47] http://code.google.com/p/cantata/downloads/list [11:47] is there an example i can use? [11:47] that looks like a good page [11:48] try modifying the owncloud one [11:49] Hey all [11:50] Riddell: on the bottom of the Kmenu, right where the User's full name and host name is, [11:51] http://pastebin.com/J57bM94a [11:53] golly that looks complex [11:53] vassie: tested it? [11:53] copy one from a program that was hosted on good code [11:54] how do i test? [11:55] put it in a copy of the package sources and run uscan [11:56] k, need to power on my vm, might be on my desktop at home actually, this might take a while [11:56] vassie: you can ask me for an ec2 if that helps [11:57] thanks, but will i have to build my package from scratch? [11:57] vassie: you don't have to build anything, you just need the package source (which you can download from your PPA on launchpad) [11:58] vassie, I have Cantata running ok , just have to configure mpd to startup at boot [11:59] got my source, added my current key to my ppa [12:08] ran uscan, nothing came back [12:10] vassie: I get "uscan ERROR: debian/watch version number is unrecognised; skipping watchfile" [12:10] so it doesn't like that one [12:10] change version=1 to version=3 === mgraesslin_ is now known as mgraesslin [12:17] BluesKaj: i add "mpd" to ~/.xprofile so it starts on login [12:19] oh grrr [12:20] xnox: how do I make some code execute once a page has been loaded in ubiquity? [12:20] i.e. once the event loop is running [12:21] shadeslayer: i'm not sure what you mean. [12:21] well [12:21] in order to get the devices Phonon needs an event loop running [12:22] vassie: try kmediafactory maybe [12:23] i did, that is where i got it from [12:24] i changed 1 to 3 and i don't get an error now [12:24] vassie: if you run uscan --verbose does it say useful things? [12:25] Newest version on remote site is 0.9.2, local version is 0.9.2 [12:25] groovy [12:25] vassie: so are we ready to upload? [12:26] i'm happy with it [12:26] :) [12:26] quantal and raring? [12:26] just raring [12:26] point me at the files to upload [12:26] can it be backported? [12:27] shadeslayer: right, but when event loop is running, that means python code is not executed sequentially any more, only callbacks are called..... [12:27] yes, we can either put it into kubuntu-ppa/backports or once its in raring go through the proccess for the ubunut backports [12:27] Do you need my new cantata_0.9.2-0ubuntu3~ubuntu12.10~ppa1.debian.tar.gz? [12:27] and raring package? [12:27] shadeslayer: so in your __init__ or in your prepare funtions you need to setup callbacks that phonon will call if it finds or doesn't find a camera. [12:28] okay [12:29] vassie: yep [12:29] Riddell: ok, i need to sign them as i rebuilt my tar.gz, plus i need my raring VM, which is at home [12:30] vassie: no you don't [12:30] I need to sign them when I upload them, you don't have permission to upload to the ubuntu archive so your signature won't do anything [12:30] vassie: just point me at what needs uploading [12:31] both packages are on my ppa https://launchpad.net/~vassie/+archive/ppa [12:32] watch file http://pastebin.com/J57bM94a (change version=1 to version=3) [12:32] vassie: 0.9.2-0ubuntu3~ppa2 ? [12:32] i can't download my raring package right now as i am on quantal [12:33] you can download whatever you like, this is free software :) [12:33] that is my raring package, minus the watch file [12:33] http://ppa.launchpad.net/vassie/ppa/ubuntu/pool/main/c/cantata/ wget is your friend :) [12:33] I got it now [12:36] vassie: uploaded! [12:36] it should appear at https://launchpad.net/ubuntu/raring/+queue soon [12:36] :) [12:37] sweet [12:37] vassie: and now you need to wait for an archive admin to accept it, happens the first time you load anything [12:37] Riddell: awesome, i'll sit tight [12:38] vassie: in the mean time there's plenty more to do, rekonq, libmtp etc :) [12:38] Riddell: will the quantal package go to ppa:kubuntu-ppa/backports? [12:38] also 4.10 is being tagged tonight so that's the big one [12:38] vassie: yeah can do, point me at what to upload there [12:40] Riddell: https://www.box.com/s/6bnjtzqkvvm6lhmdavvk [12:44] vassie: uploaded! [12:44] :) [12:44] thank you [12:46] https://launchpad.net/ubuntu/raring/+queue?queue_state=4&queue_text=cantata [12:46] vassie: I just rejected it cos I noticed the control file needed some tidying [12:46] vassie: I've reuploaded with the tidying [12:46] oh, ok [12:47] you hadn't give na description and it needed word warp on the long description [12:47] oh right, sorry [12:58] xnox: is the event loop running when plugin_get_current_page is called? [12:58] or is it run right after plugin_get_current_page ? [13:02] * apachelogger pokes shadeslayer with a long stick [13:02] ? [13:02] it does not matter [13:02] change line order and suddenly you have no eventloop where you had one before [13:03] use the qevent functions [13:04] shadeslayer: look into run_main_loop / quit_main_loop. We stop mainloop between the pages, when we start mainloop again, you don't have any flow control at all. You are just hoping that an event/signal/handler is triggered by Qt and possible calls your callbacks. [13:05] aha [13:05] shadeslayer: and you still didn't tell us what you are trying to achieve that brought you down the rabbit hole of main loops. [13:05]