[00:18] * apachelogger blinks at Riddell [00:32] shadeslayer: that's cos 4.12 is first [00:32] * Riddell bats eyelids at apachelogger [00:33] I thought .12 aint gonna make alpha1? [00:33] think again *presses red button of doom* [00:33] ohhohohohohohho [00:33] problem [00:34] rekonq bookmarksies don't get imported into fireringdingding it seems [00:34] Nooooooooooooooooooooooooo [00:36] not sure how to make that happen [00:37] ping valorie [00:38] 'Ubuntu 13.10 should be upgraded to LTS status' [00:38] lawl === rdieter_work is now known as rdieter [02:50] hi ahoneybun_ [02:52] jussi: I've heard a person on #kubuntu asking where our merch is on the website [02:53] so perhaps whip up a link on the main page this time? [02:53] Riddell: got my cards! [02:53] \o/ [02:53] thank you [03:06] valorie: ping [03:07] o/ [03:07] I said hello earlier, but you must have pinged out [03:08] you sounded pretty happy last night! [03:08] Yea away and did not mark away [03:08] But of course [03:08] You got us a space on user base [03:08] once we got a few pages the way we want them, I'll write to the translators [03:09] so once you take off the "under construction" thingie [03:09] then the tools auto-mark it ready for translation [03:09] I got the welcome main and basic pages over [03:09] Also made a card on trello [03:09] awesome [03:10] Userbase.KDE.org/kubuntu [03:11] Yep [03:11] Amazing this mediawiki [03:11] when I click the basic link, I get to https://wiki.kubuntu.org/Kubuntu/KubuntuDocs/Basic [03:12] it really is awesome, yes [03:12] Got to fix then links [03:12] Welcome too [03:12] Yea [03:13] ok, as long as you know [03:13] Yea [03:13] Thanks [03:13] But amazing work valorie [03:13] Getting us a spot [03:14] that was fun [03:14] getting us connected feels great [03:14] Yea we are all a whole [03:15] I agree [03:15] Brb [03:15] and it's good for everyone here to get used to working directly with KDE [03:18] Media wiki is much more powerful [03:19] But not too much of a stretch for new comers [04:03] mediawiki and moinmoin share somethings in common [04:13] sure, both wikis, but beyond that? [04:25] valorie: beyond? [04:26] sec [04:31] apachelogger: JonT came and saved the day on that apt-pkg deprecation warning. [04:31] g2g [04:32] I've gotten that out and I now have no warnings in libqapt with my changes. [04:43] who knows how to get wifi working for hp f4500? [04:44] frank1: sorry, support is in #kubuntu [04:45] manchicken: awesome [04:45] so have you submitted it to reviewboard yet? [04:47] Still running through tests. [04:48] I'm wondering if anybody's going to have time to help test it. [04:48] you are being very thorough [04:53] Yeah, 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] C++ is my weakest language, and I'm not going to get better by making the same mistakes again and again :) [05:04] heh [05:37] krazy2 has found a bunch of stuff in libqapt. [05:37] Most 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:41] I got the QPointers bit in for modal dialogs opened via exec(), that seemed like an important one. [06:35] hello??? [08:26] Good morning. [08:30] hi [08:30] Hey prem_ [08:30] how much ram is reqd. to install kubuntu [08:30] 64 biy [08:31] 64 bit [08:31] prem_: User support is in #kubuntu. [08:31] oh.. [08:32] prem_: This tells me 1GB is recommended: http://en.wikipedia.org/wiki/Kubuntu#System_requirements [08:33] thanks but i was looking for 64 bit distribution because for ubuntu 64 bit requires minimum of 2gb ram [08:36] prem_: 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 ;) === schmidtm_ is now known as schmidtm [09:25] can anyone tell me advantages over standard ubuntu? [09:26] anyone? [09:26] I am pretty bored from Ubuntu now and need a change in distro. [09:27] no one can answer my question? :( [09:27] KDE SC, that's an advantage in itself [09:29] tahnks simpson. can u please tell me something about KDE SC and its advantages? please [09:29] is a different UI and is generally more configurable than most other desktop environments [09:30] it looks nice too [09:30] For me the biggest advantage is that I can find things. Unity seems to hide a lot of things. [09:30] sounds good, actually I have a dual monitor coniguration and I am also a gamer. [09:31] Yes, unity hides a lot... twisted part by canonical. :( [09:31] I 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:32] I guess KDE has looks like windows also? [09:33] it can look like whatever you want, but its default look is not dissimilar to how windows looked before they went all metro [09:34] sounds good, maybe I shall switch to it. [09:34] Thanks a lot simpsons and dievader. [09:35] can 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:36] Canon support is worst.. they haven't answered any questions. maybe you geeks can help.??? [09:37] anyone of you GEEKS.... help??? [09:37] waliarubal: Kubuntu support is in #kubuntu. Canon isn't know for their Linux support I'm afraid. [09:38] sounds bad... but I just can't throw away my piece of hardware. any help will be appreciated. [09:38] Maybe I will setup KUbuntu today, in that also I will need printer installation. [09:38] waliarubal: Join #kubuntu ;) [09:39] Ya, I will install K ubuntu today. [09:40] so now I expect help from u guys on my printer installation. :) [09:41] waliarubal: Like I said, join the channel #kubuntu for support. This is not a support channel. [09:42] Thanks vader. much appreciated. [09:42] bby, thanks all for ur time. :D [09:56] yofel: piiiiiing [09:57] yofel: kf5 is now split... so I started wondering ... why exactly does each neon branch have the full debian/ shebang [09:58] oh wait, launchpad can't do tempalte processing [09:58] * apachelogger rolls eyes [09:59] yofel: different question ... what do you think about moving the 3000 new repositories to builder and use *one* template debian/ to create them [10:00] what 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 branch [10:00] neon5 had that too IIRC [10:00] right but you still had 3000 branches with packging [10:00] what I am proposing is something like kde-l10n-common [10:01] that needs non-launchpad pre-processing which we couldn't do back then [10:01] one branch that is regex-subbed at build time to the actual package [10:01] yofel: yeah, so what do you think about doin git now xD [10:01] because to me maintaining 30000 former kdelibs packages/branches/projects seems like a major hassle [10:04] just so I understand this right, you essentially want to deprecate the branches *and* the recipes? [10:05] I want to deprecate launchpad really :P [10:05] well, sure, we can do this all by ourselves, if you go and provide the infrastructure [10:05] already there :P [10:06] it's just very much hand crafted towards neon [10:06] which ain't a bad thing, just saying ;) [10:07] well, 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 manually [10:08] right [10:08] there has been talk of a general purpose build infrastructure btw [10:49] anyone else getting http://paste.kde.org/p32313f5e when trying to open a mail print preview in kmail? [10:55] jose: how's the feature tour? [11:31] yofel: http://paste.ubuntu.com/6593706/ [11:41] 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-desktop [11:41] with plasma-netbook instead works [12:13] 'Morning all [14:24] !testers | alpha 1 candidates need testing [14:24] alpha 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 information [14:25] will have a look [14:26] Riddell, alpha 1 is out today ? thought tomorrow was the release day. [14:26] :O [14:26] i shall test it later at home after gym [14:42] Riddell: might be useful to have muon on the CD btw [14:42] unless muon-updater works, in which case, it's fine [14:43] Riddell: link to CD's missing :) [14:46] no alpha images available in https://wiki.kubuntu.org/TrustyTahr/Alpha1/Kubuntu [14:46] smartboyhw is on the testers list but isnt he inactive since unknown date? [14:46] *till [14:46] as he studing hard ? :) [14:47] http://iso.qa.ubuntu.com/qatracker/milestones/309/builds/59389/downloads [14:47] http://iso.qa.ubuntu.com/modules/qatracker/misc/cdrom.png [14:47] http://iso.qa.ubuntu.com/qatracker/milestones/309/builds/59391/downloads [14:50] BluesKaj: needs testing [14:51] shadeslayer: do you think muon-updater isn't working? [14:51] It wasn't working on Netrunner Saucy [14:51] and it had muon from Ubuntu archives [14:51] didn't we fix the problems with muon? [14:51] we did a load of post-release fixes [14:51] plz check if muon-updater works in Trusty [14:52] I can't because I've screwed up my muon install somehow === vHanda_ is now known as vHanda [15:00] muon-updater works here shadeslayer, Riddell, says trusty system is up to date [15:00] okay then [15:00] idk why, but it didn't work on a derivative [15:00] * shadeslayer needs to SRU [15:01] yeah we had that bug at release [15:01] but (I hope) we fixed it as an SRU [15:01] shadeslayer, netrunner doesn't use all the same repos as kubuntu , it restricts a few , but i can't recall which ones [15:02] BluesKaj: it was a bug in muon [15:02] which Aleix fixed [15:06] shadeslayer, does the first url you posted above contain the alpha-1 image ? [15:06] BluesKaj: yes [15:06] shadeslayer, ok thanks [15:08] * BluesKaj wonders how different it is than yesterday's daily build [15:24] valorie: ping [15:25] ScottK: Riddell muon in saucy-proposed [15:25] bug 1261812 [15:25] bug 1261812 in muon (Ubuntu Saucy) "Please update muon to 2.1.2" [Undecided,New] https://launchpad.net/bugs/1261812 [15:56] Riddell: installer keeps throwing up errors [15:56] and crashed [16:12] shadeslayer: err [16:12] what sort of errors? [16:15] hm [16:16] xnox: I think your cmake upload broke something [16:16] xnox: https://launchpadlibrarian.net/160121636/buildlog_ubuntu-trusty-i386.project-neon5-dbusmenu-qt_0.0%2Bbzr20131218%2Br255%2Bneon20~ubuntu14.04.1_FAILEDTOBUILD.txt.gz [16:17] happens with every package apparently [16:17] kdelibs for example https://launchpadlibrarian.net/159748514/buildlog_ubuntu-trusty-amd64.project-neon5-kdelibs_0.0%2Bgit20131214%2Br97583~de0aa0b%2Bneon12~ubuntu14.04.1_FAILEDTOBUILD.txt.gz [16:17] apachelogger: possible. [16:18] apachelogger: can you point me to the actual source/build-record instead of the logs? [16:18] apachelogger: there is no way to go from the build-log back to the actual build-record. [16:18] apachelogger: can you open about against cmake with links to source-package builds and assign it to me? [16:19] can do [16:19] https://code.launchpad.net/~neon/+archive/kf5/+build/5362429 [16:19] also happens regardless of architecture [16:20] apachelogger: do you also have a link to a previously working build for comparison what's "good" ? such that I don't hunt red-herrings [16:20] xnox: https://code.launchpad.net/~neon/+archive/kf5/+build/5323961 [16:21] oh wait, that';s saucy [16:21] xnox: https://code.launchpad.net/~neon/+archive/kf5/+build/5323959 [16:21] this one is trusty ^^ [16:22] running archive-upload script for 4.12.0 to trusty [16:22] apachelogger: could it be just new cmake upstream release regression though? i'll try with my patches reversed. [16:23] xnox: possible but unlikely, agateau has the same version (built from source) and cannot reproduce the issue [16:23] ack. [16:24] bug 1262273 [16:24] bug 1262273 in cmake (Ubuntu) "2.8.12.1-1ubuntu2 broke automoc" [Undecided,New] https://launchpad.net/bugs/1262273 [16:24] agateau: ^ in case you want to subscribe as well [16:25] apachelogger: does project neon builds it's own qt5? [16:25] apachelogger: and is it multiarched like the stock qt5 in ubuntu? [16:26] apachelogger: Should I fix all of the krazy2 findings in libqapt, you think? [16:26] apachelogger: cause in my tool chain I set an explicit path to qt5::moc [16:26] apachelogger: does the cmake package has any patch? [16:26] apachelogger: is proejct-neon-qt5 multiarched? [16:27] apachelogger: 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:28] hm [16:28] apachelogger: 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] that's a bug [16:28] * apachelogger puts on his kde developer hat [16:28] apachelogger: what is the full path to "moc" in qt5? as in not the qtchooser one. [16:28] * xnox adjusts my kubuntu-developer badge [16:29] when working on kde libraries I often want to have my own qt build, this is not working properly on ubuntu :P [16:29] xnox: /opt/project-neon5/bin/moc [16:30] http://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:31] apachelogger: you are pointing to the last resort path. in cmake there is Qt5::moc already set to a different location. [16:31] Oo [16:31] (as in the code path before that paste) [16:31] why? [16:31] * apachelogger fails to compute this just now xD [16:32] apachelogger: because the one generated at qt5 package build-time is always wrong for the cross-compile case on Debian OS. [16:32] I think the solution is to fix the qt5 cmake config, not hardcode stuff into cmake? [16:32] apachelogger: 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:33] i can guard my changes better, but your are exploiting implementation details of cmake here. [16:33] and it's sad to see that project-neon is diverging so much. [16:34] it's exploiting the fact that cmake is not supposed to hardcode stuff :P [16:34] as for neon diverging ... ultimately (in my dreams) I'd like to have it running on actual production packaging [16:35] apachelogger: 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] so 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 packaging [16:35] apachelogger: if toolchain file sets all variables, none of the Find* foo modules are loaded, nor executed. [16:35] apachelogger: please start using multiarch qt5 packaging then. [16:36] I'll put it on my todo [16:36] cause at the moment one can co-install qt5:i386 and qt5:amd64 which doesn't look possible with project-neon at all. [16:37] apachelogger: when you'll do that, you will find your automoc broken, fyi ;-) [16:40] apachelogger: what's your pkg-config? what's your location of .pc files? this should be passed to CMake via Toolchain file! [16:42] export PKG_CONFIG_PATH := $(NEONDIR)/lib/pkgconfig:$(NEONDIR)/lib/$(DEB_HOST_MULTIARCH)/pkgconfig:$(PKG_CONFIG_PATH) [16:42] xnox: 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.mk [16:43] apachelogger: 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:44] apachelogger: anything else is fragile, and is free to be changed by CMake both upstream and distribution. [16:44] apachelogger: a Toolchain file is the only contract-based interface to guarantee correct and expected compilation in CMake. [16:45] xnox: you should probably raise that at kde-buildsystem@kde.org because that is the actuall way they expect things to be done [16:47] apachelogger: 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] apachelogger: it's not my problem at all, that project-neon builds chooses to have non-deterministic builds. [16:47] ok [16:48] apachelogger: CMake upstream, and Qt upstream, and KDE upstream all support deterministic builds, for a given environment. [16:48] apachelogger: the one who picks the environment must provide a matching toolchain file to make it deterministic. [16:51] apachelogger: i took special care to honor and not break any existing users of toolchain files =/ [16:51] apachelogger: this is very low priority, as it doesn't actually affect any packages build for the distribution, by the distribution provided sources. [16:53] apachelogger: 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] that's what toolchain files are for, to assert ones expectations. [16:58] ahoneybun_: Ping [16:59] Riddell: couldn't find errors in syslog [16:59] so I restarted and it works now [17:00] shadeslayer: what works? [17:00] the installer [17:00] shadeslayer: you started a fresh install and it completed without complaining? [17:04] well, it's at 93% [17:06] kdeframeworks is split! [17:06] now where do we have qt5 5.2 packages so I can try and build something? [17:12] Riddell: kwalletd doesn't run here on the live cd [17:15] that's intentional I think [17:15] we casper that away [17:15] manchicken: judgement call, technically yes tho [17:16] sometimes excluding a check may be more appropriate though [17:16] apachelogger: causes issues when trying to add a ktp account [17:16] http://techbase.kde.org/Development/Tutorials/Code_Checking#In-Code_directives [17:16] why do we casper it away [17:16] shadeslayer: I do not know [17:16] mem consumption and stuff [17:16] and you'd get a popup to create a wallet in the past [17:16] what is this, the 90's [17:16] tho it's le unnecessary [17:17] shadeslayer: yes, apparently people still bother with 1gib ram :P [17:17] or so my inbox says [17:17] xD [17:17] Since afiestas is writing us PAM integration, it won't be necessary at some point I think [17:31] oh what fun : http://i.imgur.com/AznluXM.png [17:32] stop having fun and get some work done :@ [17:32] that looks excitingly broken [17:32] I think the video driver is broken [17:32] not KDE's fault ( it's using nouveau ) [17:33] seeing such artifacts all over the place [17:40] woo, karchive from kf5 is looking good [17:47] 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:48] The d-pointer stuff seems like it'll be a much larger risk in the change. [17:48] mind the binary compatibility [17:50] Isn't explicit just a compile-time check? [17:50] manchicken_: y u no post patches to RB [17:50] shadeslayer: Still cleaning up === rdieter_work is now known as rdieter_laptop [17:50] okay [17:50] And what I've ended up doing here is much bigger than just a single patch. [17:51] sourceslist.cpp got a lot of work done on it. [17:51] * Riddell high fives manchicken_ [17:51] :) === debfx_ is now known as debfx [17:52] 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:54] 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:55] Riddell: full install looks good [17:55] manchicken_: just look at the symbol files? [17:57] I guess I could do that, just compare the current version with the existing one. [17:57] hi there [17:57] 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:59] But I suppose that's probably a future task given all of the things likely going on in muon. [18:00] hi vet [18:00] having some wifi issues on Kubuntu. After rebooting the wifi doesn't connect as it appears with no key on the configuration menu. [18:00] vet: user support in #kubuntu (I'm afraid I don't know a quick answer) [18:01] thank you very much Riddell ;) [18:02] first time I install kubuntu and I am way lost... :S [18:03] apachelogger: do you have a regex handy for that upstart version parsing? [18:04] lol, no? [18:04] I don't even know what the string looks like [18:04] because dat code was shit :P [18:05] split.strip.chop.setsize.join.yourmom.yolo.morestringoperations.meow.bad.kitteh.toInt() [18:07] :| [18:12] 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:23] apol is my new favorite person. [18:23] apachelogger: 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 spotlight [18:23] apachelogger: 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:24] apachelogger: 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:25] apachelogger: yet, implying that it's the final state and final implementation of 14.04 LTS. [18:25] apachelogger: i will respond to that email, but on my own time, not by your schedule. [18:26] apachelogger: i'm off to volleyball now, and will return to computers tomorrow GMT time. [18:27] apachelogger: do note, that no toolchain changes are validated until full archive rebuild, which has not happened for trusty yet. [18:27] apachelogger: as kubuntu/ubuntu developer, i would have expected you to know better. [18:27] xnox: upsetting was not intended, sorry for that [18:27] apachelogger: appologies are accepted. i'll calm down and respond in calm manner. [18:27] see you tomorrow and have fun at volleyball [18:28] apachelogger: but i'm already getting personal messages and attacks from unknown to me people about this. [18:28] apachelogger: see ya =) [18:52] !find xmllint [18:52] File 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=any [18:58] manchicken: fwiw I talked to Aleix today and he says that there is a file search API in libqapt [18:58] * shadeslayer will have another look [18:58] apachelogger: updated [18:59] shadeslayer: I wonder if it is just using the libapt-pkg interfaces consumed by libqapt. [18:59] I 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. [19:03] *nod* [19:03] apachelogger: see RB [19:03] unicorns [19:03] so much betterz [21:22] ping valorie [21:22] why don't you come on over valorie? [21:23] * Riddell votes for Tm_T for Ubuntu IRC Council [21:23] hey Riddell [21:31] Riddell: is it ok if I fix the link on http://www.kubuntu.org/community/contribute linking to https://wiki.kubuntu.org/Kubuntu/Documentation ? [21:51] apachelogger: of course [22:04] shadeslayer: KTp 0.7.0 in PPA for saucy [22:04] thoughts? [22:11] shadeslayer: wait, we do have it [22:11] I'm dumb and can't filter by release [22:15] Quintasan: does ktp need synced in trusty? [22:16] Nope [22:16] It's 0.7.0 in trusty alright [22:16] and we have 0.7.0 in ppa for saucy [22:16] I just couldn't find it since I filtered by the wrong release. [22:20] ah but it would be synced with debian [22:47] Riddell: I did not see a answer if you did [22:50] ahoneybun: of course [22:51] sorry bad tab competion [22:51] ok cool [22:52] I'll work on it when I get home I'm porting more docs over [22:52] the software page is the last one I think [22:59] Riddell: was the alpha1 block lifted? or are all of those kde packages are for the alpha1 images? [23:02] * Riddell publishes http://www.kubuntu.org/news/kde-sc-4.12 [23:03] xnox: I'm hoping they'll be caught by the block [23:04] Riddell: =/ 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:05] Riddell: on the other hand if kubuntu alpha1 images are all dandy good =) then all is good. [23:05] Riddell: it's just doesn't look co-ordinated to me. [23:07] xnox: 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 promptly [23:08] xnox: 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 instead [23:08] I guess there will be a dependency chain for some of them on the relevant library [23:11] * Riddell snoozes [23:23] Riddell: yeah, you could cowboy it. just ugly =)