[00:02] phoenix_firebrd: what's from sourceforge? [00:02] phoenix_firebrd: I'm about to go to bed but can verify things in the morning [00:02] Riddell: sure, good night [00:05] phoenix_firebrd: kolab is at http://git.kolab.org/libkolab - but as both kolab and kolabxml have watch files you can just use uscan/uupdate to fetch the new versions [00:06] yofel: so is this page outdated http://qa.ubuntuwire.com/uehs/no_updated.html [00:07] yofel: whats the time now? here it us 5 37 am [00:10] bah, great time for a connection reset === yofel_ is now known as yofel [00:10] phoenix_firebrd: kolab is at http://git.kolab.org/libkolab - but as both kolab and kolabxml have watch files you can just use uscan/uupdate to fetch the new versions [00:10] (in case you didn't get it) [00:11] yofel: i am going through it right now [00:11] yofel: Do you have some time to guide me now [00:11] a few minutes, then I'm off to bed too [00:13] yofel: I am trying to compile freeimage from here freeimage [00:13] oops [00:13] yofel: http://qa.ubuntuwire.com/uehs/no_updated.html [00:14] hm, we usually just sync that from debian [00:14] yofel: can you walkthrough for compiling a single package for the first time? [00:15] yofel: if its too late, i can wait till tomorrow [00:17] will have to wait then. But maybe someone else can answer a question or two [00:18] phoenix_firebrd: I cd to the package source and do debuild -us -uc [00:18] allee: we dont need bazaar? [00:18] phoenix_firebrd: do you need freeimage for something? Otherwise kolab would be more helpful currently (library packages are a bit tricky in general for beginners though) [00:18] phoenix_firebrd: ah, one step back ;-) [00:19] yofel: ok, i will start with kolab [00:19] phoenix_firebrd: rename the tar file so it ends _.orig.tar.gz [00:19] or .bz [00:19] allee: wait i will clone first [00:20] that, or let uscan and uudate do the initial updating [00:20] *uupdate [00:20] yofel: ok [00:21] hm, do we even have branches for kolab... [00:21] I doubt [00:21] nope [00:22] KDAP dudes did pkging for debian. So there should be something already ... [00:22] whats the syntax for uupdate [00:22] we have kolab 0.2.1, can be updated to 0.4.1 [00:23] but I don't see anything in debian so far [00:23] phoenix_firebrd: sec [00:24] phoenix_firebrd: if you've unpackaged the old package and ran uscan, then "uupdate ../libkolab_0.4.1.orig.tar.gz" [00:25] yofel: so initially i have to git clone right? [00:25] no, you don't need git at all [00:26] we package tarballs if available, not git snapshots. (even if for kolab the tarball is a snapshot of the git tag) [00:26] yofel: so now i have to download this libkolab-0.4.1.tar.gz ? [00:26] phoenix_firebrd: uscan does that for you [00:26] using the watch file in the package [00:27] phoenix_firebrd: but first things first: start with 'pull-lp-source libkolab raring' [00:27] go into the source and run uscan there [00:27] yofel,phoenix_firebrd: here's the mailing list aktivity of the debian kolag pkging: http://lists.alioth.debian.org/pipermail/pkg-kolab-devel/ [00:28] yofel: sudo apt-get install ubuntu-dev-tools [00:28] yofel: installing [00:28] phoenix_firebrd: yep, you'll need those frequently [00:29] allee: i will join the mailing list [00:29] phoenix_firebrd: add https://code.launchpad.net/~bulldog98/+archive/kubuntu-dev-tools to the mix, you won't need them immediatly, but they'll be handy [00:30] yofel: mix? [00:30] just add the ppa to your sources [00:30] yofel: oh :D [00:32] yofel: source pulled [00:33] go into the unpacked source and run uscan [00:33] yofel: ran uscan [00:33] kolab debian pkg summary: http://wiki.debian.org/Teams/pkg-kolab [00:33] good, now run uupdate on the tarball [00:36] yofel: i have 2 new items one an new version traball and a sym link [00:36] use the tar with orig in its name [00:38] yofel: http://imagebin.org/243876 [00:39] phoenix_firebrd: yeah, now run uupdate [00:41] yofel: "uupdate libkolab_0.2.1.orig.tar.gz" [00:41] no, not 0.2.1, 0.4.1 [00:41] yofel: "uupdate: cannot find debian/changelog.Are you in the top directory of the source tree? [00:41] " [00:41] you need to be inside libkolab-0.2.1 [00:41] yofel: ok [00:41] there run [00:41] uupdate ../libkolab_0.4.1.orig.tar.gz [00:42] yofel: done [00:43] yofel: i have the new source [00:44] yofel: the rest is the packaging procedure [00:44] yeah, now it's the standard way of building and fixing [00:44] yofel: For maintainer's name and email , should i put your's? [00:45] no, those are supposed to be set to what it's set now [00:45] for now just try to build the package [00:45] i.e. debuild -S and throw it into pbuilder [00:45] yofel: ok [00:46] from a quick build here: a few tests fail, a few new files, and new symbols [00:47] yofel: ok [00:49] yofel: Are you waiting for me? [00:49] phoenix_firebrd: not really, where are you at? [00:50] yofel: creating gpg key [00:51] yofel: gpg: skipped "Prasad Murthy ": secret key not available [00:51] yofel: the email is wrong [00:51] is $DEBEMAIL set? [00:51] yofel: no [00:52] best put that in your .bashrc: [00:52] export DEBFULLNAME='Philip Muškovac' [00:52] export DEBEMAIL='yofel@kubuntu.org' [00:52] with your data [00:53] yofel: if i put that there wont be a problem in using key [00:54] dch will use that to fill in the name in the changelog, which debsign then uses to search for the ky [00:54] *key [00:55] yofel: ok [00:57] yofel: so after setting that i have to download the source again? [00:58] ok, I need to be off to bed, a few hints: [00:58] if you don't have a pbuilder chroot yet, look at pbuilder-dist which should be easy to understand [00:58] if you can't fix the tests (I'm too tried to make sense of the errors right now) disabel them by putting 'override_dh_auto_test:' a the end of debian/rules [00:58] if you don't know what a symbol diff (which you'll see after fixing the install file), look at http://pkg-kde.alioth.debian.org/symbolfiles.html (and no, you don't need to immediately understand that) [00:58] phoenix_firebrd: no, just fix your name in debian/changelog [00:59] yofel: ok good night, see you later [00:59] feel free to throw questions at the channel anyway, someone might answer while you stick around [01:00] good night [02:25] why apturl-kde depends on software-properties-kde? does it really need it? [03:10] SteveRiley_: ping ping ping! [06:39] wow [06:39] php closely resembles C++ [06:40] shadeslayer: pardon? [06:40] Tm_T: my ISP uses a web based login page, and I found this : https://github.com/vercingetorix/Reliance-Broadband/blob/master/index.php [06:40] which is a php script to login from the command line [06:40] looks alot like C++ [06:41] it's very OOP oriented [06:42] it's more like C with classes [06:42] heh :) [10:16] Hey all [10:17] hi BluesKaj [10:17] hi shadeslayer [10:27] hi guys, it looks like this bug is present in kubuntu 13.04 https://bugreports.qt-project.org/browse/QTBUG-28843 should i report it? or will it be resolved automatically ? [10:33] jdrab: it'll be fixed when Qt releases the next bug fix revision and we package it [10:34] shadeslayer: ty [10:34] I think it's in [10:34] ( in the next bug fix release ) [10:34] do you think it will be fixed in neon sooner than 13.04? [10:35] yes [10:35] yofel_: care to upload a new snapshot of Qt ^ ? [10:35] jdrab: this is assuming the fix was committed to Qt itself [10:36] like I said, I *think* it was committed but I don't see a commit url to confirm on jira [10:36] https://codereview.qt-project.org/#change,42266 [10:38] i always wanted to try neon :P now it's the time [10:38] shadeslayer: qtjob is still running, so it should be in when it's committed [10:38] ah you have a cron job running? [10:38] awesome [10:38] cronjob? what for? [10:39] https://code.launchpad.net/~neon/+recipe/project-neon-qt [10:41] err [10:42] nvm [10:42] I thought qt had issues being imported [10:42] those were fixed ages ago ^^ [10:42] I see [10:43] I thought we still had cronjob running and what not [10:43] yofel_: btw http://www.golem.de/news/linux-distribution-ubuntu-erwaegt-umstieg-auf-rolling-releases-1301-97086.html [10:43] yofel_: have you heard of this? [10:43] hum, not yet [10:44] I wouldn't really be against it. You would essentially have a 2-year stable platform and a bit more flexibility in between that [10:44] yeah [10:44] although that's what debian is [10:44] heh [10:45] I'd use sid if only their KDE version wasn't so outdated [10:45] and I don't want to roll my own [10:46] well, I prefer ubuntu as it's generally more up-to-date === yofel_ is now known as yofel [10:47] I'm just worrying how "release packages when they're done" would work [10:47] we would essentially have as rolling and as dev? [10:47] not that we're not already going in that direction [10:47] I'm not sure how the convinced sabdfl because iirc he was against rolling releases [10:47] ack [10:48] ;-)))))))) [10:48] well, he'll keep the LTS releases, and it simplyfies support in general [10:48] as you would essentially drop needs for SRU's the 3 in-between releases [10:49] xnox: oh oh I was installing Netrunner and wanted to ask you something [10:49] xnox: so in the timzone selector I have to select Kolkata [10:49] yofel: security updates as well. [10:49] right [10:49] xnox: which is like this tiny point on the map [10:49] and defines the timezone for the whole of India [10:50] would it be possible to just click India and make it automatically select 'Kolkata' [10:50] * yofel notes that this would make our job easier too - as we wouldn't have to worry about providing updates and backports for X releases in parallel but only 2 mostly [10:50] * xnox vaguely remembers some bugs about Kolkata as it's not the first time I'm looking it's location up =/ [10:50] *nod* [10:51] xnox: so, plz2fix? :D [10:51] I've done about 3-4 installs for friends over the last month and all of them complained about this [10:52] ( I just watched as they did the install so I could see what issues they usually hit ) [10:58] shouldn't the time-zone usually be auto recognised? [10:59] yes, but for some reason it failed on 12.10 when I was installing it [10:59] didn't debug why [11:00] hm [11:00] anyway [11:00] -> lunch, bbl [11:04] cya === ximion is now known as ximion-afk === ximion-afk is now known as ximion === ximion is now known as ximion-afk [12:35] can someone else please try to reproduce bug 1103135? I can't [12:35] bug 1103135 in Kubuntu PPA "kate crashes on startup since rc3 upgrade" [Undecided,New] https://launchpad.net/bugs/1103135 [12:35] this is precise [12:39] yofel: i can test, rc3 for which version? [12:42] phoenix_firebrd: precise + 4.9.98 from beta ppa [12:42] I just asked the reporter if he really did restart his session after the upgrade [12:42] as that symbol error looks fishy [12:43] yofel: Its working in 12.10 [12:43] phoenix_firebrd: how far did you get with kolab yesterday? [12:43] yofel: i dont have 12.04 [12:43] no problem [12:43] yofel: its in launchpad 4 min to build for i386 [12:44] I tried to reproduce it in a VM, but either it's not broken or I'm missing something [12:44] yofel: build successful with pbuilder, some tests fail [12:45] yofel: for the kate thing, there was some problem with qt that make many qt apps crah [12:45] *crash [12:46] hm, that doesn't look like a qt error though [12:48] yofel: in pbuilder kdeinit needs klauncher, so do i have to install the minimum kde packages? [12:48] yofel: thats for testing [12:50] phoenix_firebrd: for testing what? [12:50] yofel: the tests fail because kdeinit cant find klauncher binary [12:50] oh, good catch [12:51] I guess adding a build-dep for kdelibs5-plugins for the tests is acceptable [12:53] yofel: so after the tests should i have to remove the build-dep? [12:53] no, just add it to the Build-Depends in the control file [12:54] phoenix_firebrd: what's your launchpad id again? === ximion-afk is now known as ximion [12:54] yofel: https://launchpad.net/~murthy [12:54] yofel: dep wait https://launchpad.net/~murthy [12:55] oops [12:55] yofel: https://launchpadlibrarian.net/129196232/buildlog_ubuntu-raring-i386.libkolab_0.4.1-0ubuntu1_MANUALDEPWAIT.txt.gz [12:55] thanks [12:56] phoenix_firebrd: what's libkcalccore4 ? [12:56] yofel: its in universe , it is needed [12:56] no, wait, we need to clear something up here [12:56] yofel: how can i add universe to the ppa? [12:57] that you can do from the main ppa page -> Edit Dependencies [12:57] phoenix_firebrd: now back to the lib: it's needed by what? [12:58] phoenix_firebrd: and it's libkcalcore4 not libkcalccore4 [12:58] yofel: during build it failed at a point and i went it to the source and found it needs this [12:59] let me try this again [12:59] yofel: checking [13:00] yofel: yes its a typo [13:00] phoenix_firebrd: and another thing: when you upload a package to a ppa, at least append ~ppa1 to the version, as you now won't be able to properly put an updated package into the PPA that can later be updated to the archive package [13:01] note that ~ lowers the version [13:01] yofel: ya, i usually put - [13:01] - is higher, so that won't help either [13:02] * yofel tries to build without libkcalcore4 and libkabc [13:02] ok [13:04] phoenix_firebrd: see http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version on how the package version is calculated [13:05] this is heaven [13:10] builds without those libs, but tests still fail [13:11] yofel: for raring right? [13:11] * yofel wonders if this is the problem: [13:11] (13:10:19) commonconversion.cpp(43): ktimezoned is not available and required for timezone interpretation [13:11] raring, yes [13:12] yofel: ktimezoned fails because of dbus not available [13:12] oh, right, now I saw that error too [13:12] yofel: need dbus and dbus-x11 [13:12] yofel: what error? [13:12] already installed [13:12] yofel: in that case kdelibs-plugin? [13:13] klauncher(21427) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. [13:13] thats it [13:14] yofel: does pbuilder store every build log and if so where? [13:14] did you use pbuilder-dist? I think that stores a .build file somewhere near the source or the build result [13:14] only the last build though [13:17] yofel: i used pbuilder [13:17] yofel: i am confused [13:18] not sure where that puts it, I have this in my .pbuilderrc: [13:18] PKGNAME_LOGFILE_EXTENTION="_$(dpkg --print-architecture).build" [13:18] PKGNAME_LOGFILE=yes [13:18] which puts a logfile in the result folder [13:20] yofel: can using pbuilder-dist be different from pbuilder in building process? I am wondering how it failed for me [13:21] phoenix_firebrd: do you have universe enabled in pbuilder? [13:21] yofel: ya, i put that in the pbuilderrc file [13:21] hum, can't say it then without a buildlog [13:23] yofel: what is the universe repository string [13:23] my sources list has: [13:23] deb http://archive.ubuntu.com/ubuntu/ raring main restricted universe multiverse [13:27] yofel: no the string which i should be adding in the launchpad [13:27] why launchpad? [13:27] yofel: testing [13:28] we're not at a point where the package will even build [13:28] yofel: no i wont build [13:28] yofel: just to know [13:28] cyphermox: mathieu-tl AT ubuntu ? [13:28] the ppa already has universe enabled [13:29] you see that in the buildlog [13:29] Get:11 http://ftpmaster.internal raring/universe i386 Packages [5407 kB] [13:29] apparently yes [13:29] shadeslayer: do you know how to use dbus in package tests? [13:30] yofel: I need more info, the kind that KDE ships with ? [13:30] the ones you can start with make check/test [13:30] or autopkg tests and what not [13:30] the ones that dh_auto_test will run [13:31] right, make test/check [13:31] right [13:32] ideally those tests should use dbus-launch? [13:32] or you could override dh_auto_test and manually start a session if the test doesn't do it already? [13:34] that's what I tried, let me try again to get a clean log [13:39] shadeslayer: http://paste.kde.org/654422/ [13:40] and are you sure that dbus was launched? [13:40] maybe dbus needs other stuff setup first or sth [13:40] well, I probably did it the wrong way [13:40] now I did 'dbus-launch dh_auto_test' and it hung up [13:40] heh [13:41] oh fun [13:41] QSYSTEM: FormatTest::testIncidence(v2eventSimple) startkdeinitlock(8895)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "The name org. [13:41] kde.kded was not provided by any .service files" [13:41] this won't work... [13:41] first start dbus, then launch org.kde.kded? [13:42] or kded even [13:43] builds without those deps [13:43] yofel: ^ [13:43] shadeslayer: how does one do that? [13:43] doesn't matter, just pull it in? [13:44] kde-runtime-data: /usr/share/kde4/services/kded/ktimezoned.desktop [13:44] is installed [13:46] just run kded4 [13:47] but dbus should be running I think [13:47] never tried running kded4 without dbus :P [13:50] shadeslayer: running dbus-launch is fine, but I fail at getting DBUS_SESSION_BUS_ADDRESS and DBUS_SESSION_BUS_PID into the environment after that [13:51] oh, how do you do dbus-launch? just dbus-launch? [13:51] can you try eval `dbus-launch` [13:51] eval `dbus-launch` [13:51] export DBUS_SESSION_BUS_ADDRESS DBUS_SESSION_BUS_PID [13:51] kded4 [13:51] dh_auto_test [13:52] fails at kded4 [13:53] can you do a echo $DBUS_SESSION_BUS_ADDRESS $DBUS_SESSION_BUS_ADDRESS ? [13:57] shadeslayer: hm, DBUS_SESSION_BUS_PID is unset [13:58] shadeslayer: http://paste.kde.org/654446 [13:58] whaaaa [13:59] hmm how odd [14:01] yofel: try kdeini4 kded4 [14:01] great, putting the stuff into a subscript worked... but now: [14:01] kded4: cannot connect to X server :0 [14:01] * yofel resigns [14:01] xD [14:01] xvfb :P [14:02] why do people assume that kde is running during a build... [14:03] hey, dummy question: are kde packages built with -DQT_NO_DEBUG ? [14:05] agateau: I think yes [14:06] yofel: ok, thanks. Do you know if other distros do the same? [14:09] That I fear I don't know [14:09] cyphermox: sent [14:10] shadeslayer: that hangs even earlier, I think we'll skip this for now [14:10] phoenix_firebrd: still there? [14:10] yofel: ya [14:10] yofel: give it to me :P [14:10] yofel: watching [14:10] * shadeslayer can work on it a bit [14:10] shadeslayer: how about you fix this up once I'm done explaining the rest to phoenix_firebrd? [14:10] ah sure [14:10] whatcha guys packaging? [14:11] libkolab [14:12] phoenix_firebrd: put this in your debian/rules: http://paste.kde.org/654464/ - that will make the test not hold everything up [14:12] I see [14:12] * shadeslayer would have gone for a .PHONY target there [14:13] why? [14:14] just to be safer? [14:14] though that's fine as well :) [14:14] well, I just wanted to get the error out of the way, not the tests themselves [14:14] ah [14:15] yofel: next? [14:16] phoenix_firebrd: try to build it again, it'll end at missing files this time [14:16] * shadeslayer notes that we should put up a wiki page explaining what can be shipped and what's blacklisted [14:17] blacklisted as in? [14:17] well [14:17] blacklisted from the seeds [14:17] libav for eg [14:17] ah, look at the seeds? [14:17] sure, but no user looks at the seeds [14:17] hum, true [14:18] they're like "The thing thats used to grow plants?" [14:18] why apturl-kde depends on software-properties-kde, doues it really need it? is to enable repositories on the fly? [14:18] hmm [14:19] probably uses some python function? [14:21] doEnableSection() runs software-properties-kde so that's ok [14:21] EagleScreen: that's the case it seems [14:21] I see, thanks [14:23] yofel: you and shadeslayer were discussing about running processes before in testing process, how to do that? [14:24] phoenix_firebrd: things like dbus-launch and kded4? [14:24] and that kind of functions shouldn't be go to software-properties-common? [14:24] just add them to the required target [14:24] shadeslayer: ya [14:24] shadeslayer: for example dolphin [14:24] shadeslayer: ship: * !libavcodec* [14:24] ship: * !phonon-backend-null [14:25] ! means blacklist [14:25] Sorry, I don't know anything about means blacklist [14:25] Riddell: that too [14:25] EagleScreen: not as long as it does this: http://paste.kde.org/654482 [14:27] wow [14:29] phoenix_firebrd: rules is a Makefile, there you can define a target which you can then add a list of command to. So in dh7 packaging we would add an override target and just run the commands we want to add before the overridden command [14:30] yofel: ok. installing fails. http://paste.kde.org/654488/ [14:31] phoenix_firebrd: right, as those are header files, you'll have to add them to libkolab-dev.install [14:32] yofel: what is this file libkolab-dev.install ? [14:32] afiestas: does webaccounts have a release? [14:32] a .install files tells debhelper what files will end up in a package [14:32] shadeslayer: ? [14:32] afiestas: a versioned release [14:32] development .so links and header files go into a -dev package by convention [14:33] don't think so [14:33] like 0.1 or sth [14:33] phoenix_firebrd: so libkolab-dev.install is the list of files that will be put into libkolab-dev [14:33] yofel: what about be the location of the libkolab-dev.install? [14:33] inside the debian/ folder as always [14:33] it's already there, you just need to add the 3 files to it [14:34] yofel: so the output of debuild would be two packages? [14:34] yes, debian/control has 2 Package: definitions, i.e. you'll get 2 packages [14:35] you can add an install file for every package. (Actually once you have more than one package you need install files) [14:36] yofel: ok i have added the 3 lines to the install files,should i build ? [14:36] phoenix_firebrd: yep, but for the next step make sure that pbuilder saves the buildlog somewhere [14:39] yofel: sorry i started the build process without routing to a file, i will do it the next time [14:39] just let pbuilder do that for you... [14:40] phoenix_firebrd: do you have any .build files in /var/cache/pbuilder/result/ ? [14:40] yofel: on call [14:40] or wherever the build result gets put for you [14:42] my toolbars keep disappearing :( [14:43]