/srv/irclogs.ubuntu.com/2013/12/18/#kubuntu-devel.txt

* apachelogger blinks at Riddell00:18
Riddellshadeslayer: that's cos 4.12 is first00:32
* Riddell bats eyelids at apachelogger 00:32
apacheloggerI thought .12 aint gonna make alpha1?00:33
shadeslayerthink again *presses red button of doom*00:33
apacheloggerohhohohohohohho00:33
apacheloggerproblem00:33
apacheloggerrekonq bookmarksies don't get imported into fireringdingding it seems00:34
shadeslayerNooooooooooooooooooooooooo00:34
apacheloggernot sure how to make that happen00:36
ahoneybun_ping valorie00:37
apachelogger'Ubuntu 13.10 should be upgraded to LTS status'00:38
apacheloggerlawl00:38
=== rdieter_work is now known as rdieter
valoriehi ahoneybun_02:50
valoriejussi: I've heard a person on #kubuntu asking where our merch is on the website02:52
valorieso perhaps whip up a link on the main page this time?02:53
valorieRiddell: got my cards!02:53
valorie\o/02:53
valoriethank you02:53
ahoneybunvalorie: ping03:06
valorieo/03:07
valorieI said hello earlier, but you must have pinged out03:07
valorieyou sounded pretty happy last night!03:08
ahoneybunYea away and did not mark away03:08
ahoneybunBut of course03:08
ahoneybunYou got us a space on user base03:08
valorieonce we got a few pages the way we want them, I'll write to the translators03:08
valorieso once you take off the "under construction" thingie03:09
valoriethen the tools auto-mark it ready for translation03:09
ahoneybunI got the welcome main and basic pages over03:09
ahoneybunAlso made a card on trello03:09
valorieawesome03:09
ahoneybunUserbase.KDE.org/kubuntu03:10
ahoneybunYep03:11
ahoneybunAmazing this mediawiki03:11
valoriewhen I click the basic link, I get to https://wiki.kubuntu.org/Kubuntu/KubuntuDocs/Basic03:11
valorieit really is awesome, yes03:12
ahoneybunGot to fix then links03:12
valorieWelcome too03:12
ahoneybunYea03:12
valorieok, as long as you know03:13
ahoneybunYea03:13
ahoneybunThanks03:13
ahoneybunBut amazing work valorie 03:13
ahoneybunGetting us a spot03:13
valoriethat was fun03:14
valoriegetting us connected feels great03:14
ahoneybunYea we are all a whole03:14
valorieI agree03:15
ahoneybunBrb03:15
valorieand it's good for everyone here to get used to working directly with KDE03:15
ahoneybunMedia wiki is much more powerful03:18
ahoneybunBut not too much of a stretch for new comers03:19
ahoneybun_mediawiki and moinmoin share somethings in common04:03
valoriesure, both wikis, but beyond that?04:13
ahoneybun_valorie: beyond?04:25
valoriesec04:26
manchickenapachelogger: JonT came and saved the day on that apt-pkg deprecation warning.04:31
ahoneybun_g2g 04:31
manchickenI've gotten that out and I now have no warnings in libqapt with my changes.04:32
frank1who knows how to get  wifi working  for hp f4500?04:43
valoriefrank1: sorry, support is in #kubuntu04:44
valoriemanchicken: awesome04:45
valorieso have you submitted it to reviewboard yet?04:45
manchickenStill running through tests.04:47
manchickenI'm wondering if anybody's going to have time to help test it.04:48
valorieyou are being very thorough04:48
manchickenYeah, I submitted many of my changes before to apachelogger just to find out that I completely failed to see something. Just learning from my mistakes :)04:53
manchickenC++ is my weakest language, and I'm not going to get better by making the same mistakes again and again :)04:53
valorieheh05:04
manchickenkrazy2 has found a bunch of stuff in libqapt.05:37
manchickenMost of it was there when I got there, I'm trying to decide whether or not I need to fix the issues since they're legacy.05:37
manchickenI got the QPointers bit in for modal dialogs opened via exec(), that seemed like an important one.05:41
wifistinkshello???06:35
lordievaderGood morning.08:26
prem_hi08:30
lordievaderHey prem_ 08:30
prem_how much ram is reqd. to install kubuntu08:30
prem_64 biy08:30
prem_64 bit08:31
lordievaderprem_: User support is in #kubuntu.08:31
prem_oh..08:31
lordievaderprem_: This tells me 1GB is recommended: http://en.wikipedia.org/wiki/Kubuntu#System_requirements08:32
prem_thanks but i was looking for 64 bit distribution because for ubuntu 64 bit requires minimum of 2gb ram08:33
lordievaderprem_: Sounds reasonable. The bare minimum is probably somewhere around there, 1~2Gb of ram. But please join #kubuntu for support, I'm in there too ;)08:36
=== schmidtm_ is now known as schmidtm
waliarubalcan anyone tell me advantages over standard ubuntu?09:25
waliarubalanyone?09:26
waliarubalI am pretty bored from Ubuntu now and need a change in distro.09:26
waliarubalno one can answer my question? :(09:27
tsimpsonKDE SC, that's an advantage in itself09:27
waliarubaltahnks simpson. can u please tell me something about KDE SC and its advantages? please09:29
tsimpsonis a different UI and is generally more configurable than most other desktop environments09:29
tsimpsonit looks nice too09:30
lordievaderFor me the biggest advantage is that I can find things. Unity seems to hide a lot of things.09:30
waliarubalsounds good, actually I have a dual monitor coniguration and I am also a gamer.09:30
waliarubalYes, unity hides a lot... twisted part by canonical. :(09:31
waliarubalI generally game, program and watch movies. that's what I do. earlier I used to be windows user, but now I use Linux because of freedom.09:31
waliarubalI guess KDE has looks like windows also?09:32
tsimpsonit can look like whatever you want, but its default look is not dissimilar to how windows looked before they went all metro09:33
waliarubalsounds good, maybe I shall switch to it.09:34
waliarubalThanks a lot simpsons and dievader.09:34
waliarubalcan you guys help me with a problem too? actually I have Canon LBP3000 printer and I can't make it work under linux. It worked perfect under windows.09:35
waliarubalCanon support is worst.. they haven't answered any questions. maybe you geeks can help.???09:36
waliarubalanyone of you GEEKS.... help???09:37
lordievaderwaliarubal: Kubuntu support is in #kubuntu. Canon isn't know for their Linux support I'm afraid.09:37
waliarubalsounds bad... but I just can't throw away my piece of hardware. any help will be appreciated.09:38
waliarubalMaybe I will setup KUbuntu today, in that also I will need printer installation.09:38
lordievaderwaliarubal: Join #kubuntu ;)09:38
waliarubalYa, I will install K ubuntu today.09:39
waliarubalso now I expect help from u guys on my printer installation. :)09:40
lordievaderwaliarubal: Like I said, join the channel #kubuntu for support. This is not a support channel.09:41
waliarubalThanks vader. much appreciated.09:42
waliarubalbby, thanks all for ur time. :D09:42
apacheloggeryofel: piiiiiing09:56
apacheloggeryofel: kf5 is now split... so I started wondering ... why exactly does each neon branch have the full debian/ shebang09:57
apacheloggeroh wait, launchpad can't do tempalte processing09:58
* apachelogger rolls eyes09:58
apacheloggeryofel: different question ... what do you think about moving the 3000 new repositories to builder and use *one* template debian/ to create them09:59
yofelwhat do you mean? In neon4, we had a 'dummy-ubuntu' branch that we took for each package and simply regex replaced the new package names to have a new packaging branch10:00
yofelneon5 had that too IIRC10:00
apacheloggerright but you still had 3000 branches with packging10:00
apacheloggerwhat I am proposing is something like kde-l10n-common10:00
yofelthat needs non-launchpad pre-processing which we couldn't do back then10:01
apacheloggerone branch that is regex-subbed at build time to the actual package10:01
apacheloggeryofel: yeah, so what do you think about doin git now xD10:01
apacheloggerbecause to me maintaining 30000 former kdelibs packages/branches/projects seems like a major hassle10:01
yofeljust so I understand this right, you essentially want to deprecate the branches *and* the recipes?10:04
apacheloggerI want to deprecate launchpad really :P10:05
yofelwell, sure, we can do this all by ourselves, if you go and provide the infrastructure10:05
apacheloggeralready there :P10:05
apacheloggerit's just very much hand crafted towards neon10:06
apacheloggerwhich ain't a bad thing, just saying ;)10:06
yofelwell, I don't really care what builds the packages and how they get to the PPA really, as long as there's a way to edit it and run it manually10:07
apacheloggerright10:08
apacheloggerthere has been talk of a general purpose build infrastructure btw10:08
yofelanyone else getting http://paste.kde.org/p32313f5e when trying to open a mail print preview in kmail?10:49
Riddelljose: how's the feature tour?10:55
apacheloggeryofel: http://paste.ubuntu.com/6593706/11:31
Peace-Riddell: btw do you know how to start a nested session of plasma-desktop ?  this doesn't work :S  Xephyr :1 -screen 1280x800 & sleep 3 && export DISPLAY=:1 && plasma-desktop11:41
Peace-with plasma-netbook instead works11:41
BluesKaj'Morning all12:13
Riddell!testers | alpha 1 candidates need testing14:24
ubottualpha 1 candidates need testing: Help is needed in #kubuntu-devel. Please ping Riddell, yofel, soee, Tm_T, shadeslayer, BluesKaj, James147, smartboyhw, Quintasan, lordievader, shrini, tester56, parad1se  for information14:24
shadeslayerwill have a look14:25
BluesKajRiddell, alpha 1 is out today ? thought tomorrow was the release day.14:26
soee:O14:26
soeei shall test it later at home after gym14:26
shadeslayerRiddell: might be useful to have muon on the CD btw14:42
shadeslayerunless muon-updater works, in which case, it's fine14:42
shadeslayerRiddell: link to CD's missing :)14:43
BluesKajno alpha images available in https://wiki.kubuntu.org/TrustyTahr/Alpha1/Kubuntu14:46
soee smartboyhw is on the testers list but isnt he inactive since unknown date?14:46
soee*till14:46
soeeas he studing hard ? :)14:46
shadeslayerhttp://iso.qa.ubuntu.com/qatracker/milestones/309/builds/59389/downloads14:47
shadeslayerhttp://iso.qa.ubuntu.com/modules/qatracker/misc/cdrom.png14:47
shadeslayerhttp://iso.qa.ubuntu.com/qatracker/milestones/309/builds/59391/downloads14:47
RiddellBluesKaj: needs testing14:50
Riddellshadeslayer: do you think muon-updater isn't working?14:51
shadeslayerIt wasn't working on Netrunner Saucy14:51
shadeslayerand it had muon from Ubuntu archives14:51
Riddelldidn't we fix the problems with muon?14:51
Riddellwe did a load of post-release fixes14:51
shadeslayerplz check if muon-updater works in Trusty14:51
shadeslayerI can't because I've screwed up my muon install somehow14:52
=== vHanda_ is now known as vHanda
BluesKajmuon-updater works here shadeslayer, Riddell, says trusty system is up to date15:00
shadeslayerokay then15:00
shadeslayeridk why, but it didn't work on a derivative15:00
* shadeslayer needs to SRU15:00
Riddellyeah we had that bug at release15:01
Riddellbut (I hope) we fixed it as an SRU15:01
BluesKajshadeslayer, netrunner doesn't use all the same repos as kubuntu , it restricts a few , but i can't recall which ones15:01
shadeslayerBluesKaj: it was a bug in muon15:02
shadeslayerwhich Aleix fixed15:02
BluesKajshadeslayer, does the first url you posted above contain the alpha-1 image ?15:06
shadeslayerBluesKaj: yes15:06
BluesKajshadeslayer, ok thanks15:06
* BluesKaj wonders how different it is than yesterday's daily build15:08
ahoneybunvalorie: ping15:24
shadeslayerScottK: Riddell muon in saucy-proposed15:25
shadeslayerbug 126181215:25
ubottubug 1261812 in muon (Ubuntu Saucy) "Please update muon to 2.1.2" [Undecided,New] https://launchpad.net/bugs/126181215:25
shadeslayerRiddell: installer keeps throwing up errors15:56
shadeslayerand crashed15:56
Riddellshadeslayer: err16:12
Riddellwhat sort of errors?16:12
apacheloggerhm16:15
apacheloggerxnox: I think your cmake upload broke something16:16
apacheloggerxnox: https://launchpadlibrarian.net/160121636/buildlog_ubuntu-trusty-i386.project-neon5-dbusmenu-qt_0.0%2Bbzr20131218%2Br255%2Bneon20~ubuntu14.04.1_FAILEDTOBUILD.txt.gz16:16
apacheloggerhappens with every package apparently16:17
apacheloggerkdelibs for example https://launchpadlibrarian.net/159748514/buildlog_ubuntu-trusty-amd64.project-neon5-kdelibs_0.0%2Bgit20131214%2Br97583~de0aa0b%2Bneon12~ubuntu14.04.1_FAILEDTOBUILD.txt.gz16:17
xnoxapachelogger: possible.16:17
xnoxapachelogger: can you point me to the actual source/build-record instead of the logs?16:18
xnoxapachelogger: there is no way to go from the build-log back to the actual build-record.16:18
xnoxapachelogger: can  you open about against cmake with links to source-package builds and assign it to me?16:18
apacheloggercan do16:19
apacheloggerhttps://code.launchpad.net/~neon/+archive/kf5/+build/536242916:19
apacheloggeralso happens regardless of architecture16:19
xnoxapachelogger: do you also have a link to a previously working build for comparison what's "good" ? such that I don't hunt red-herrings16:20
apacheloggerxnox: https://code.launchpad.net/~neon/+archive/kf5/+build/532396116:20
apacheloggeroh wait, that';s saucy16:21
apacheloggerxnox: https://code.launchpad.net/~neon/+archive/kf5/+build/532395916:21
apacheloggerthis one is trusty ^^16:21
Riddellrunning archive-upload script for 4.12.0 to trusty16:22
xnoxapachelogger: could it be just new cmake upstream release regression though? i'll try with my patches reversed.16:22
apacheloggerxnox: possible but unlikely, agateau has the same version (built from source) and cannot reproduce the issue16:23
xnoxack.16:23
apacheloggerbug 126227316:24
ubottubug 1262273 in cmake (Ubuntu) "2.8.12.1-1ubuntu2 broke automoc" [Undecided,New] https://launchpad.net/bugs/126227316:24
apacheloggeragateau: ^ in case you want to subscribe as well16:24
xnoxapachelogger: does project neon builds it's own qt5?16:25
xnoxapachelogger: and is it multiarched like the stock qt5 in ubuntu?16:25
manchickenapachelogger: Should I fix all of the krazy2 findings in libqapt, you think?16:26
xnoxapachelogger: cause in my tool chain I set an explicit path to qt5::moc16:26
agateauapachelogger: does the cmake package has any patch?16:26
xnoxapachelogger: is proejct-neon-qt5 multiarched?16:26
xnoxapachelogger: if it isn't you are really ought to build project-neon-cmake, as cmake package in the distribution has been tailor specifically to the qt5 package as shipped in ubuntu.16:27
apacheloggerhm16:28
xnoxapachelogger: i think there are variables that you can export to make it act more like stock "cmake", i've made sure there is a fallback, but it's rather "opt-out" kind of thing as by default i enabled cross-compilation without modifying all sources.16:28
apacheloggerthat's a bug16:28
* apachelogger puts on his kde developer hat16:28
xnoxapachelogger: what is the full path to "moc" in qt5? as in not the qtchooser one.16:28
* xnox adjusts my kubuntu-developer badge16:28
apacheloggerwhen working on kde libraries I often want to have my own qt build, this is not working properly on ubuntu :P16:29
apacheloggerxnox: /opt/project-neon5/bin/moc16:29
apacheloggerhttp://paste.ubuntu.com/6595065/16:30
* xnox points out, that the correct interface, is to explicitely set QT5::moc in that case, in your toolchain file used for custom/prefix installed system libraries, as advised by CMake.16:30
xnoxapachelogger: you are pointing to the last resort path. in cmake there is Qt5::moc already set to a different location.16:31
apacheloggerOo16:31
xnox(as in the code path before that paste)16:31
apacheloggerwhy?16:31
* apachelogger fails to compute this just now xD16:31
xnoxapachelogger: because the one generated at qt5 package build-time is always wrong for the cross-compile case on Debian OS.16:32
apacheloggerI think the solution is to fix the qt5 cmake config, not hardcode stuff into cmake?16:32
xnoxapachelogger: thus, it's adjusted to the right one. Which is also, a wild guess, if you don't happen to use stock-cmake with stock-qt5. Both of them are failing to guess it at all times.16:32
xnoxi can guard my changes better, but your are exploiting implementation details of cmake here.16:33
xnoxand it's sad to see that project-neon is diverging so much.16:33
apacheloggerit's exploiting the fact that cmake is not supposed to hardcode stuff :P16:34
apacheloggeras for neon diverging ... ultimately (in my dreams) I'd like to have it running on actual production packaging16:34
xnoxapachelogger: wrong. in CMake one should use a Toolchain file for any non-standard locations. Actual modules are, last fallback, not the first look up.16:35
apacheloggerso you have a rolling packaging so to speak and at release time you simply branch the latest version and have your ready to go release packaging16:35
xnoxapachelogger: if toolchain file sets all variables, none of the Find* foo modules are loaded, nor executed.16:35
xnoxapachelogger: please start using multiarch qt5 packaging then.16:35
apacheloggerI'll put it on my todo16:36
xnoxcause at the moment one can co-install qt5:i386 and qt5:amd64 which doesn't look possible with project-neon at all.16:36
xnoxapachelogger: when you'll do that, you will find your automoc broken, fyi ;-)16:37
xnoxapachelogger: what's your pkg-config? what's your location of .pc files? this should be passed to CMake via Toolchain file!16:40
apacheloggerexport PKG_CONFIG_PATH := $(NEONDIR)/lib/pkgconfig:$(NEONDIR)/lib/$(DEB_HOST_MULTIARCH)/pkgconfig:$(PKG_CONFIG_PATH)16:42
apacheloggerxnox: build foo is here http://bazaar.launchpad.net/~neon/project-neon5/project-neon5-runtime/view/head:/opt/project-neon5/share/pkg-project-neon5/0/default-settings.mk16:42
xnoxapachelogger: cmake_defaults and all the LD_LIBRARY_PATH, PKG_CONFIG_PATH, QT_PLUGIN_PATH, QML2_IMPORT_PATH, are ought to live in a Toolchain file which is passed to CMake by default.16:43
xnoxapachelogger: anything else is fragile, and is free to be changed by CMake both upstream and distribution.16:44
xnoxapachelogger: a Toolchain file is the only contract-based interface to guarantee correct and expected compilation in CMake.16:44
apacheloggerxnox: you should probably raise that at kde-buildsystem@kde.org because that is the actuall way they expect things to be done16:45
xnoxapachelogger: Anybody who uses CMake and does reproducible builds is using Toolchain files (to e.g. enforce compiler versions / editions / pick this or that) it's pretty standard.16:47
xnoxapachelogger: it's not my problem at all, that project-neon builds chooses to have non-deterministic builds.16:47
apacheloggerok16:47
xnoxapachelogger: CMake upstream, and Qt upstream, and KDE upstream all support deterministic builds, for a given environment.16:48
xnoxapachelogger: the one who picks the environment must provide a matching toolchain file to make it deterministic.16:48
xnoxapachelogger: i took special care to honor and not break any existing users of toolchain files =/16:51
xnoxapachelogger: this is very low priority, as it doesn't actually affect any packages build for the distribution, by the distribution provided sources.16:51
xnoxapachelogger: don't get me wrong, it's "incompatability" between the two and all 4 parties can claim it's a bug in the other three. (parties being: upstreams qt, cmake, kde, ubuntu)16:53
xnoxthat's what toolchain files are for, to assert ones expectations.16:53
lordievaderahoneybun_: Ping16:58
shadeslayerRiddell: couldn't find errors in syslog16:59
shadeslayerso I restarted and it works now16:59
Riddellshadeslayer: what works?17:00
shadeslayerthe installer17:00
Riddellshadeslayer: you started a fresh install and it completed without complaining?17:00
shadeslayerwell, it's at 93% 17:04
Riddellkdeframeworks is split!17:06
Riddellnow where do we have qt5 5.2 packages so I can try and build something?17:06
shadeslayerRiddell: kwalletd doesn't run here on the live cd17:12
apacheloggerthat's intentional I think17:15
apacheloggerwe casper that away17:15
apacheloggermanchicken: judgement call, technically yes tho17:15
apacheloggersometimes excluding a check may be more appropriate though17:16
shadeslayerapachelogger: causes issues when trying to add a ktp account17:16
apacheloggerhttp://techbase.kde.org/Development/Tutorials/Code_Checking#In-Code_directives17:16
shadeslayerwhy do we casper it away17:16
apacheloggershadeslayer: I do not know17:16
apacheloggermem consumption and stuff17:16
apacheloggerand you'd get a popup to create a wallet in the past17:16
shadeslayerwhat is this, the 90's17:16
apacheloggertho it's le unnecessary17:16
apacheloggershadeslayer: yes, apparently people still bother with 1gib ram :P17:17
apacheloggeror so my inbox says17:17
shadeslayerxD17:17
shadeslayerSince afiestas is writing us PAM integration, it won't be necessary at some point I think17:17
shadeslayeroh what fun : http://i.imgur.com/AznluXM.png17:31
apacheloggerstop having fun and get some work done :@17:32
apacheloggerthat looks excitingly broken17:32
shadeslayerI think the video driver is broken17:32
shadeslayernot KDE's fault ( it's using nouveau )17:32
shadeslayerseeing such artifacts all over the place17:33
Riddellwoo, karchive from kf5 is looking good17:40
manchicken_I think I'm going to ignore the pre-existing d-pointer issues in a couple of the classes, but I'll update the explicit constructors.17:47
manchicken_The d-pointer stuff seems like it'll be a much larger risk in the change.17:48
apacheloggermind the binary compatibility17:48
manchicken_Isn't explicit just a compile-time check?17:50
shadeslayermanchicken_: y u no post patches to RB17:50
manchicken_shadeslayer: Still cleaning up17:50
=== rdieter_work is now known as rdieter_laptop
shadeslayerokay17:50
manchicken_And what I've ended up doing here is much bigger than just a single patch.17:50
manchicken_sourceslist.cpp got a lot of work done on it.17:51
* Riddell high fives manchicken_ 17:51
manchicken_:)17:51
=== debfx_ is now known as debfx
manchicken_I kinda took the approach that the maintainer needed to step away from this library, he had conceded there were some issues, so I just kinda took over a little bit.17:52
manchicken_There may already be binary compatibility issues, which is why I've been trying to get someone who maintains a package depending on this library to jump in and help me verify that I haven't broken their world (or if I have, where).17:54
shadeslayerRiddell: full install looks good17:55
Riddellmanchicken_: just look at the symbol files?17:55
manchicken_I guess I could do that, just compare the current version with the existing one.17:57
vethi there17:57
manchicken_That said, most of the dependencies (muon included) seem like they should be updated to take advantage of the new functionality in this version, namely tracking separate sources.list files.17:57
manchicken_But I suppose that's probably a future task given all of the things likely going on in muon.17:59
Riddellhi vet 18:00
vethaving some wifi issues on Kubuntu. After rebooting the wifi doesn't connect as it appears with no key on the configuration menu. 18:00
Riddellvet: user support in #kubuntu (I'm afraid I don't know a quick answer)18:00
vetthank you very much Riddell ;)18:01
vetfirst time I install kubuntu and I am way lost... :S18:02
shadeslayerapachelogger: do you have a regex handy for that upstart version parsing?18:03
apacheloggerlol, no?18:04
apacheloggerI don't even know what the string looks like18:04
apacheloggerbecause dat code was shit :P18:04
apacheloggersplit.strip.chop.setsize.join.yourmom.yolo.morestringoperations.meow.bad.kitteh.toInt()18:05
shadeslayer:|18:07
manchicken_I don't think that I broke binary compatibility compared to the stable version of libqapt running right now... but it's in no way binary compatible with the unreleased 2.1 version JonT was working on before.18:12
manchicken_apol is my new favorite person.18:23
xnoxapachelogger: i'm deeply upset and pissed off about your email message, which puts my conversation with you here, out of context, in the spotlight, with widely exaggerated claims.18:23
* vHanda should switch off alerts for spotlight18:23
xnoxapachelogger: none of my cmake changes are complete, and are only known to not regress native compilation against system libraries for a wide subset of packages (~20% of the archive) whilst at the same time enabling as less intrusively as possible a really cool feature.18:23
xnoxapachelogger: you on the other hand, give me what, an irc conversation and a bug report and no time to review, respond, code, prototype and fix a bug in an unstable distribution code-named trusty, which is yet to do any milestone release.18:24
xnoxapachelogger: yet, implying that it's the final state and final implementation of 14.04 LTS.18:25
xnoxapachelogger: i will respond to that email, but on my own time, not by your schedule.18:25
xnoxapachelogger: i'm off to volleyball now, and will return to computers tomorrow GMT time.18:26
xnoxapachelogger: do note, that no toolchain changes are validated until full archive rebuild, which has not happened for trusty yet.18:27
xnoxapachelogger: as kubuntu/ubuntu developer, i would have expected you to know better.18:27
apacheloggerxnox: upsetting was not intended, sorry for that18:27
xnoxapachelogger: appologies are accepted. i'll calm down and respond in calm manner.18:27
apacheloggersee you tomorrow and have fun at volleyball18:27
xnoxapachelogger: but i'm already getting personal messages and attacks from unknown to me people about this.18:28
xnoxapachelogger: see ya =)18:28
apachelogger!find xmllint18:52
ubottuFile xmllint found in bash-completion, cluster-glue, libxml2-doc, libxml2-utils, manpages-tr, tclxml, vim-runtime, webgen0.4, webgen0.4-doc, webgen0.5 (and 1 others) http://packages.ubuntu.com/search?searchon=contents&keywords=xmllint&mode=&suite=saucy&arch=any18:52
shadeslayermanchicken: fwiw I talked to Aleix today and he says that there is a file search API in libqapt18:58
* shadeslayer will have another look 18:58
shadeslayerapachelogger: updated18:58
manchickenshadeslayer: I wonder if it is just using the libapt-pkg interfaces consumed by libqapt.18:59
manchickenI looked through the code and didn't see anything that looked like that, but I could be wrong. It's not a huge codebase, but it's not tiny either.18:59
shadeslayer*nod*19:03
shadeslayerapachelogger: see RB19:03
apacheloggerunicorns19:03
apacheloggerso much betterz19:03
ahoneybunping valorie21:22
Riddellwhy don't you come on over valorie?21:22
* Riddell votes for Tm_T for Ubuntu IRC Council21:23
ahoneybunhey Riddell21:23
ahoneybunRiddell: is it ok if I fix the link on http://www.kubuntu.org/community/contribute linking to https://wiki.kubuntu.org/Kubuntu/Documentation ?21:31
Riddellapachelogger: of course21:51
Quintasanshadeslayer: KTp 0.7.0 in PPA for saucy22:04
Quintasanthoughts?22:04
Quintasanshadeslayer: wait, we do have it22:11
QuintasanI'm dumb and can't filter by release22:11
RiddellQuintasan: does ktp need synced in trusty?22:15
QuintasanNope22:16
QuintasanIt's 0.7.0 in trusty alright22:16
Quintasanand we have 0.7.0 in ppa for saucy22:16
QuintasanI just couldn't find it since I filtered by the wrong release.22:16
Riddellah but it would be synced with debian22:20
ahoneybunRiddell: I did not see a answer if you did22:47
Riddellahoneybun: of course22:50
Riddellsorry bad tab competion22:51
ahoneybunok cool22:51
ahoneybunI'll work on it when I get home I'm porting more docs over22:52
ahoneybunthe software page is the last one I think22:52
xnoxRiddell: was the alpha1 block lifted? or are all of those kde packages are for the alpha1 images?22:59
* Riddell publishes http://www.kubuntu.org/news/kde-sc-4.1223:02
Riddellxnox: I'm hoping they'll be caught by the block23:03
xnoxRiddell: =/ did you check that. i think most of it will. anyway not helping alpha1, cause now for all of these packages you have no option to upload bugfix & respin with it. you'll have to go with 4.12 or release-note bugs =( so i'm a bit surprised you traded "respins option" for upload 4.12 now, instead tomorrow / friday.23:04
xnoxRiddell: on the other hand if kubuntu alpha1 images are all dandy good =) then all is good.23:05
xnoxRiddell: it's just doesn't look co-ordinated to me.23:05
Riddellxnox: I had to get those .orig in the archive so we can get the packages into backports PPA without taking up many GB of disk space and have them released promptly23:07
Riddellxnox: but I'm not sure I see a problem, if we do need to upload a package we can just delete the one in -proposed and upload the bugfix instead23:08
RiddellI guess there will be a dependency chain for some of them on the relevant library23:08
* Riddell snoozes23:11
xnoxRiddell: yeah, you could cowboy it. just ugly =)23:23

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!