[00:00] hurray, wine finished, off to bed I am then [00:00] night night [00:01] sweet dreams, shadeslayer === ScottK2 is now known as ScottK [00:02] happy new year, ScottK [00:02] ooo, and scarlett [00:02] Thanks. [00:02] nice to see you again [00:02] Same to you valorie [00:03] I noticed that you are giving our docs the once-over [00:03] yeah between flu and holidays I am back logged, but working on Kubuntu userbase now, and going to learn packaging [00:03] which is awesome; thanks so much [00:03] sgclark: Any questions bout pbuilder? [00:03] i've forgotten a lot of what I knew on userbase [00:03] Note that we are working on trusty so you need only trusty pbuilders for now [00:06] Quintasan: yofel: http://community.kde.org/Promo/Events/FOSDEM/2014 [00:07] if you didn't see it already [00:15] Quintasan: still working on it, fresh install so adding missing repo, updates etc [00:15] mmkay [00:15] I won't be sticking for too long though since uni [00:16] at least I assume pbuilder is in kubuntu-dev-tools, command not found atm [00:16] happy new year, Quintasan [00:16] sgclark: no, pbuilder is in it's own package [00:16] Quintasan: I talked to you last about Kubuntu Active; is it dead in the water? [00:17] no worries, I will be around alot more now [00:17] valorie: I haven't finished up the KubuntuLinks page yet; however, I've added the Social Section. [00:17] sgclark: generally you want to install ubuntu-dev-tools and kubuntu-dev-tools [00:17] ok, thanks! [00:17] cool, SonikkuAmerica [00:17] so uh... [00:17] SonikkuAmerica: Don't really want to get into details now since I have to to go bed if I'm to get up at a reasonable hour. In short: no. [00:18] Quintasan: That's OK, tell me about it later :) [00:18] to whom do I report a broken file for the 13.10 iso repository? [00:18] or... wait what? [00:18] Long version, wait for me to get back here tomorrow or email me at quintasan at kubuntu.org so I can reply in details or something [00:18] Huh, thats odd... [00:18] MangaKaDenza: How is it broken? [00:19] last I tried, I couldn't get the .torrent file for 13.10 64 bit... [00:19] but now I can... [00:19] looking good, SonikkuAmerica [00:19] like... just a few hours ago I couldn't... [00:19] anyways... sorry for wasting your time :P it seems to work now [00:19] well, it's...magic? [00:19] it took you like 30 seconds so it's not a huge waste of time [00:20] file in question, just in case: http://cdimage.ubuntu.com/kubuntu/releases/13.10/release/kubuntu-13.10-desktop-amd64.iso.torrent [00:20] valorie: I hope the Facebook link is right, but the only Kubuntu community page I could find is in French, and it's all screenshots of KDE being contorted every which way. [00:20] (actually it's only you who wasted 30 seconds :P) [00:20] well see you guys around [00:20] valorie: (Which of course is a good thing) [00:20] night [00:21] yeah, I don't know about that fb page [00:21] maybe ask on the kubuntu-devel list [00:22] the thing about having a facebook page is that someone has to maintain it [00:22] Mhm === apachelogger_ is now known as apachelogger [09:17] shadeslayer: do we have a timeline for touchpad-kcm inclusion? [10:46] apachelogger: is everything good to go from the source side? ( haven't read your last conversation ) [10:47] * shadeslayer is going to patch kde-workspace now [10:47] shadeslayer: I never blocked on the source :P [10:47] none of the issues was in any way a showstopper [10:52] python3-aptdaemon.pkcompat pulled in by ubuntu-drivers-common [10:52] shadeslayer: didn't you do something about that? [10:52] or did we decide not to do anything for .10? [10:52] I need to write 2 things for the KCM, the installation stuff and the second one being generic interface name support using udev [10:53] I am thinking of working on install support today, generic names for interfaces isn't a priority and requires me learning udev api pieces [10:54] bug 704597 [10:54] bug 704597 in ubuntu-meta (Ubuntu) "Depend on nvidia-common" [Medium,Fix released] https://launchpad.net/bugs/704597 [10:54] shadeslayer: how does that affect the dependency on polkit? [10:54] eh [10:54] packagekit [10:55] aha [10:55] apachelogger: I don't think that package is required [10:55] it's recommended [10:55] and we kinda get ubuntu-drivers-common forced on us by the platform seed [10:56] it's required for the pkkit interface [10:56] not for the stuff we need tbh [10:56] yeah [10:56] I figured that, hence why I want it gone :P [10:56] why I wanted it gone for .10 already [10:56] pulls in all sorts of rubbish [10:56] I thought we can twiddle around and make recommends disappear [10:57] with the fancy braces [10:57] hm no, that was to make foo a Depends or Recommends [10:57] but I distinctly remember twiddling so that packages don't pull in Recommends [10:58] never seen that [10:59] point is [10:59] it shouldn't be a recommend to begin with [10:59] or should be fullfilled by some kde bit [10:59] just not having it on the seed still means the packaging is wrong [11:01] yofel: did you not push kde-workspace 4.11.5 packaging to bzr? [11:06] shadeslayer: I did not package it for trusty [11:06] if you do you'll need to refresh a patch, but I think that's all [11:08] Ack, will have a look later if I get the time [11:19] apachelogger: what were your thoughts on the "IDE in your face" wrt the kde developer meta package? [11:19] IIRC I argued that it was merely a suggests [11:20] yofel: how about kde-workspace? [11:21] sgclark: did you get anyone to look at packaging [11:21] ? [11:21] Quintasan: yeah come to fosdem [11:27] apparently Riddell is giving a talk there [11:28] you can cheer me on [11:28] yeah ... that's what I plan to do .... ;) [11:32] hm, no mitya57 [11:45] and I don't think moc-boost148-53.patch is required [12:09] Riddell: uh, same question as shadeslayer or..? [12:12] I hate live build [12:13] the only way to get live build to reliably work is to assume the docs are wrong [12:13] and to look at the code [12:21] good morning [12:22] morning sgclark [12:22] what timezone are you in? [12:22] Pacific in the US [12:22] yofel: oh yeah, I didn't read his question properly :) [12:22] sgclark: way over there! [12:23] sgclark: I'm happy to show you packaging any time we have a couple of hours spare that cross over [12:23] hehe yeah, I am an early bird though. [12:23] I am around all day, so whenever you have time :) [12:24] sgclark: I'll set up an ec2 server, do you have a launchpad account with your ssh key? [12:24] yep! I got that all updated last night [12:34] hmm [12:34] Riddell: does muon updater work for you [12:35] let me try [12:37] shadeslayer: runs fine and downloading updates now [12:37] in trusty [12:37] what's not working? [12:37] ack, so some weird auth issue with my system [12:37] need to reinstall everything anyway, partitions are totally full [12:39] 'Morning all [12:40] sgclark: where your lp account? [12:41] Riddell: not sure I understand the question, my username is scarlett-7 [12:42] sgclark: https://launchpad.net/~scarlett-7 [12:42] is that you? [12:42] that is me :) [12:43] yeah, that's your LP page then :) === Blizzzek is now known as Blizzz [12:51] apachelogger: http://bazaar.launchpad.net/~neon/neon/neon5-image/revision/4 [13:12] sgclark: want to get started? [13:12] ssh ubuntu@ubuntu@ec2-50-19-157-239.compute-1.amazonaws.com if so [13:12] and run byobu [13:12] Riddell: ok [13:13] type something if you get in [13:14] Riddell: denied public key [13:15] bother, scarlett@scarlett-dev is in the authorized_keys [13:15] sgclark: try again [13:16] fail :( [13:16] let me double check my key [13:16] sgclark: bother, are you sure you have that ssh key on your system? [13:22] Riddell: copied again and it was exactly the same. Could it be my configuration? [13:23] hmm, dunno [13:24] sgclark: are you in byobu now? [13:24] type something if so [13:24] is there supposed to be a double ubuntu@ in that address ? [13:25] jussi: la la la [13:25] sgclark: gosh you have a narrow terminal [13:25] sgclark: yay!! [13:25] Riddell: Im sending you stickers tomorrow :) (I has envelopes and everything :D) you should have them very soon. [13:25] Riddell:lol [13:26] sgclark: so this is an ec2 cloud computer from amazon's cloud platform AWS [13:26] sgclark: we're both in that gnu screen session (which has byobu a profile for gnu screen) and can both interact [13:27] sgclark: would you like me to take you through a package? [13:27] Riddell: neato [13:27] you in control me telling you want to do [13:27] Riddell: yes please [13:27] sgclark: let's take a look at one I did yesterday, threadweaver [13:27] sgclark: make a new directory and apt-get update then apt-get source threadweaver [13:28] I added kubuntu-ppa/experimental to sources.list so it should find it [13:29] sgclark: you have sudo [13:29] hmm bother [13:29] I know, hang on [13:30] oh maybe I didn't add it [13:31] sgclark: ok try again [13:31] grr [13:31] no source by default [13:31] sgclark: ok try again [13:31] yay! [13:32] sgclark: so here you can see the sources for the package [13:32] the .orig.tar is what we get from upstream [13:32] ok [13:32] the debian.tar.gz contains the debian/ directory with the various instructions for packaging it [13:32] ok [13:32] and the .dsc is just a description meta file with md5sums etc for checking uploading and downloading [13:33] you ran apt-get source with sudo so those files were root, no need for that, I just ran it again as the user [13:33] sgclark: take a look in the extracted threadwaver directory [13:33] gotcha [13:34] Riddell: where are the notes for kf5 [13:34] shadeslayer: http://notes.kde.org/p/kubuntu-ninjas-frameworks [13:34] cheers [13:34] sgclark: ever compiled sources before? [13:35] Riddell: everyday, main computer is Gentoo hehe [13:35] elite! [13:35] Riddell: lol [13:35] sgclark: so take a look in the debian/ directory, that's where our magic happens [13:36] changelog has the packaging changelog [13:37] compat is a version number, most of the work is done by debhelper scripts and that has new versions occationally, compat tells it what version to run as [13:37] * allee lurks to learn last stuff about library pkging ... :-) [13:37] allee: want to join in? [13:37] yes [13:37] give me an ssh key if so [13:37] public ssh key [13:38] * Riddell thinks allee knows all this already [13:38] sgclark: control lists the packages that will be made [13:38] Riddell: key -> launchpad.net/~allee Never used api tracing [13:39] allee: ssh ubuntu@ec2-50-19-157-239.compute-1.amazonaws.com [13:39] byobu [13:39] sgclark: .install files list the files which get made and what .deb packages they go into [13:40] sgclark: rules is the Makefile which actually compiles then installs everything [13:40] ahh [13:40] sgclark: that is mostly a simple target to run everything through dh but for more complex stuff you need to know what's going on in there [13:40] sgclark: and source just has a version of source packaging we're using [13:40] sgclark: do take a look in each file [13:41] ok [13:41] * Riddell gets a drink [13:45] Riddell: done [13:46] sgclark: lets compile this baby [13:46] sgclark: cd ..; debuild [13:46] dpkg-checkbuilddeps: Unmet build dependencies: cmake extra-cmake-modules qtbase5-dev [13:46] sgclark: apt-get install them [13:48] sgclark: it's compiling! [13:48] Riddell :) [13:49] sgclark: running it with debuild -nc -j2 [13:49] -nc is no clear and just means it resumes compiling rather than starting again [13:49] -j2 is build in parallel cos I note this ec2 has 2 processors [13:49] sgclark: it compiled! [13:49] gotcha [13:49] sgclark: take a look in the directory above [13:50] yay we have our .deb files! [13:50] you can use lesspipe to see what's in them [13:50] oh cool [13:50] lesspipe? [13:50] lesspipe just runs files through a useful command, in this case dpkg --info [13:51] oh cool, learned something new [13:51] looking good [13:51] sgclark: you can also run them through lintian which is a tool to look for common errors [13:53] no errors :) [13:53] yay [13:53] sgclark: so voila, that's a package [13:53] sgclark: if you have another hour spare we can have a go at making a new package [13:53] Riddell: i do [13:54] Riddell: give me a sec to make more coffee [13:54] Riddell: where there file that store the info about methods + version of 1st appearance? [13:54] allee: you're right I don't seem to have added a .symbols file [13:55] strange I thought I did but maybe that was another package [13:55] there was something in the rules file ... [13:56] sgclark: allee .symboles files list every symbol in a library to make sure upstream hasn't sneakily removed any and made it binary incompatible [13:56] doing with with c++ is surprisingly faffy and difficult [13:56] those clever people at debian have a nice setup for it which we use and is documented at http://pkg-kde.alioth.debian.org/symbolfiles.html [13:56] ok [13:56] let me add one to threadweaver [13:58] so a couple of faffy commands needed [13:58] debian/libkf5threadweaver5.symbols [13:59] nope [13:59] pkgkde-symbolshelper create -o debian/libkf5threadweaver5.symbols -v 4.95.0 symbols.amd64 [13:59] pkgkde-gensymbols -plibkf5threadweaver5 -v4.95.0 -Osymbols.amd64 -edebian/libkf5threadweaver5/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 [13:59] but the other way around [13:59] then we end up with debian/libkf5threadweaver5.symbols which is checked when a new version comes out [14:00] also any packages which depend on this library will know which version is the minimum it needs [14:00] so I'll upload this change to the PPA on launchpad [14:00] Riddell: thoughts about not doing separate dbg packages [14:00] dch -i add to the debian changelog [14:01] but then if we want to backport frameworks to PPA's that won't work .. hmmm [14:01] debuild -S builds the source only files [14:02] shadeslayer: what's changed to allow us to do that? [14:03] dbgsym? [14:03] but won't work out well for PPA's is the problem [14:03] shadeslayer: right but debian will still want dbg packages [14:04] and I hope this packaging will be useful to them [14:04] sgclark: dput then uploads it to the launchpad PPA where it will compile and hopefully all will work [14:04] ack [14:04] Riddell: you're missing "include /usr/share/pkg-kde-tools/qt-kde-team/2/debian-qt-kde.mk" in threadweaver [14:05] shadeslayer: hmm I was just using dh9 rather than dhmk [14:07] which I suppose might not be how debian wants to do it [14:07] well I'll e-mail them in a bit and get feedback [14:07] sgclark: shall we do karchive? [14:07] ok [14:08] sgclark: make a new directory [14:08] and wget http://download.kde.org/unstable/frameworks/4.95.0/karchive-4.95.0.tar.xz [14:08] dunno why but I can't get dbg package extraction to work :/ [14:08] sgclark: no apt-get possible, it's not packaged yet :) [14:09] sgclark: copy and paste is your friend :) [14:09] irc on diff computer [14:09] doh [14:10] sgclark: now the tar needs renamed so the - is a _ [14:10] and the end is .orig.tar.xz [14:11] sgclark: extract it [14:11] shadeslayer: what are you trying? [14:11] sgclark: tab completion is your friend :) [14:12] not working [14:12] err [14:12] ah nvm [14:12] why not? [14:12] made it work somehow [14:13] sgclark: now it's probably easiest just to copy over the debian/ directory from threadweaver into the karchive sources [14:13] you could also use dh_make which is a command to give you a template === kfunk_ is now known as kfunk [14:14] ok [14:15] sgclark: now using your favourite editor edit debian/changelog and update the bits for this package [14:16] hmm, vi eh? oh well nobody is perfect :) [14:16] sgclark: just remove the top block and change my name/address to yours [14:18] version? no idea [14:18] sgclark: that's the right version [14:18] quite a few bits in that version number just to confuse you [14:19] 4.95.0-0ubuntu1~ubuntu14.04~ppa1 [14:19] hm [14:19] 4.95.0 is upstream kde version [14:19] ok [14:19] 0 is debian version (0 because it's not in debian) [14:19] ubuntu1 is ubuntu version [14:19] gotcha [14:19] time? [14:19] ~ubuntu14.04 is a backport version because it's not in the archive [14:19] and ~ppa1 is more backport because it's in a PPA [14:19] sgclark: just leave the time [14:19] ok [14:19] Riddell, ScottK, yofel: anyone knows what the 34m/33m stuff is in pykde4? http://paste.ubuntu.com/6715011/ pykde4 in trusty is essentially twice as big as the one in saucy [14:20] https://docs.google.com/spreadsheet/pub?key=0AiHh-WCutt3jdEotb2RFaWh1dl9YbFdhdGUwQkgyNWc&output=html [14:20] sgclark: control is next to edit [14:21] sgclark: good start [14:21] sgclark: Homepage next to change [14:21] check on projects.kde.org for the right url [14:24] sgclark: now we need to tell it what .deb packages we want it to make [14:24] sgclark: since I've not compiled this I'm not sure what it'll end up with but it's very likely just the same as threadweaver but with a different name [14:24] so lets change libkf5threadweaver to libkf5archive [14:25] apachelogger: some magic for python 3.3 and 3.4? who does the changelog blame? [14:25] sgclark: please ask any questions as we're going along of course [14:26] sgclark: libkf5archive should be libkf5archive5 [14:26] that final 5 is the soname version which gets bumped if there is some binary incompatible change in a new version [14:27] sgclark: ah but not in the -dev package [14:27] no so name needed there [14:27] you just want to compile against whatever the latest version is [14:30] is that right? [14:30] sgclark: looking good [14:30] all done in that file I think [14:31] why is dev different? and how do I figure that out? [14:31] sgclark: different how? [14:31] 5 at the end [14:32] sgclark: applications typically don't care what version of the library they build against, they just want the latest version, so we don't usually put a version number in there [14:32] sometimes we do such as with qt4 vs qt5 applications will care what version they build with so we do for that case [14:33] but .deb binary packages do care they have the right version of the library so we need to version them [14:33] oh ok [14:33] else the library version might get upgraded and not the application then it'll crash [14:33] for the gory details you can read the debian policy on shared libraries which has exact specifications for packaging [14:33] but that's not much use when getting started, too much detail [14:34] ok [14:34] Riddell: * debian/rules: Fix support for multiple Python 3 versions. [14:34] -- William Grant Mon, 30 Dec 2013 13:38:41 +1100 [14:34] suppose that's the cause [14:34] sgclark: in rules you'll need to update the dbg package name I think [14:35] apachelogger: we've found our culprit, he'll likely know what it'll take to reduce it again [14:35] Riddell: also, http://packages.ubuntu.com/saucy/language-pack-kde-en these packages are pulled onto the ISO and bring kdevelop l10n with it for no good reason [14:35] sgclark: right I'm bored of this, let's try and compile and see what happens! [14:35] lol ok [14:35] apachelogger: I don't know another way of doing that,you either have translations installed or people will install packages and not get them translated [14:36] sgclark: boom! [14:36] Riddell: [14:36] recommends [14:36] need to install zlib? [14:36] apachelogger: downgrade it to a recommends if you want but it'll still be installed on the images by default [14:37] sgclark: yep it needs libraries for zip bzip and zx I think [14:37] nono [14:37] I mean kdevelop should recommend kdevelop-l10n [14:37] sgclark: let me look up the old kde4libs to see what it uses [14:37] sgclark: zlib1g-dev [14:37] the language pack shouldn't [14:37] sgclark: libbz2-dev [14:37] because kdevelop isn't part of our default delivery [14:37] sgclark: liblzma-dev [14:37] sgclark: add those to the build-depends in debian/control and install them and rebuild [14:38] Riddell: generally speaking the issue is with muon though... it ought to manually craft language packs into the depency tree of a package [14:38] i.e. an interactive version of the langauge kcm logic [14:38] apachelogger: yes that would be nice, although then you'd have people using other ways to install stuff and not getting translations [14:38] JT also agreed with that notion, but things we talked about rarely got to see the light of day ^^ [14:39] sgclark: remember commas [14:39] Riddell: you have that regardless [14:40] right now the people are thos that are using packages that are not recommends of the languagepack and do not have a proper package relationship [14:40] sgclark: yay it's compiling! [14:40] with muon supporting it the group people are those that are using packages that are not recommends of a languagepack and do not have a proper package relationship and were not installed via muon [14:40] sgclark: just looked at the cmake configure output there, looks like it's all happy [14:40] so actually it would reduce the amount of people affected ;) [14:41] anyway, IMO if you use a non-user-centric tool then don't expect it to do everything for you [14:41] sgclark: success! (of some description) [14:42] dbg error? [14:42] Riddell: german l10n removed from seed, this at least should fix the oversize [14:42] "debug package libkf5karchive5-dbg is not listed in the control file" hmm, what's up with that? [14:43] it is there [14:43] hurray for source without attribution [14:43] incorrect formatting can make it so that it is technically not there (the dbg package) [14:44] sgclark: I think we don't use a version number in the dbg package [14:44] although suddenly I realise there's mixed practice on that [14:44] sgclark: ah you misspelt it in debian/rules, an extra k [14:44] for dbg packages? Oo [14:45] or are we missing that k everywhere? [14:45] apachelogger: to version or not to version dbg? [14:45] version [14:45] libKF5Archive.so only 1 K [14:45] otherwise you can't debug libfoo1 and libfoo2 on the same system [14:46] apachelogger: the majority are against you http://paste.ubuntu.com/6715111/ [14:46] (also technically speaking again ... you can debug libfoo1 and libfoo2 because debug symbols are named with uuids so there is no actual file conflict, but you have to update/downgrade the dbg packge as needed ;)) [14:46] Riddell: the majority is wrong [14:47] I may be lost now. So do I need to change stuff to archive rather than karchive? [14:47] Riddell: it's like some libraries have stuff in /usr/share and that is packaged in libfoo1 ... [14:47] sgclark: yes should all be kf5archive [14:47] defeats the purpose of calling it libfoo1 in the first place [14:47] sgclark: next you need the .install files moved and changed for kf5archive [14:49] Riddell: btw random thought on the kf5 packaging ... please do that in bzr and please bzr branch it from kdelibs [14:49] kppp packaging has no history because it was manually copied :S [14:49] apachelogger: good idea [14:50] Riddell: correct? [14:51]