[00:32] Riddell and apachelogger: What's the solution for kde-l10n-sv FTBFS? === lool- is now known as lool === ramanK is now known as Guest86976 [10:46] lex79: I already have a package for digikam ready to upload, but I will step back from this bug, if you want to fix it? [10:47] neversfelde: I don't understand, do you have already the package with the fix? [10:47] I uploaded the fix in my ppa for testing [10:48] if it resolves the crash we can upload it [10:48] lex79: yes, but I cannot upload at the moment, I am not at home [10:48] and I do not know, if it resolves the bug, because I cannot reproduce the crash [10:49] neversfelde: ah ok, well if my package fix the bug we can upload my package [10:49] ok [10:49] neversfelde: if not, we will see :) [11:57] amarok 2.3.1 beta is in staging, if someone wants to test [11:58] for lucid [15:20] \o [15:23] \o === mgraesslin_ is now known as mgraesslin === bipolar_ is now known as bipolar [16:11] Fresh Kubuntu install, 64 bit this time. Nice and fast. [16:12] Only abnormality that I've detected is that all my email from Scott K. lost it's date info, until I clicked on them. === mcas is now known as mcas1 [16:37] JontheEchidna: can you upload digikam from bzr ? [16:38] lex79: sure [16:38] :) [16:44] it's taking a bit to get all the packaging infastructure back after the new install [16:47] take your time [16:48] lex79: btw, do you have any package upload statistics for this cycle? === amik is now known as amichair [16:49] JontheEchidna: not yet, but I can have [16:51] lex79: uploaded. an archive admin will need to push it through now [16:51] kk, thanks [16:55] huh, I am sorry, I pushed amarok to the ppa before it was released [16:57] neversfelde: you are too fast :D [16:57] yes, indeed :) [17:23] amarok moved to beta backports [17:24] mhh, I probably should have called it ~lucid1~ppa1 [17:27] Nightrose: is there a schedule for Amarok 2.3.1 or when is the next beta planned? [17:28] neversfelde: final tagging planned for 15th [17:29] ok, so problem then. Thank you. [17:29] oh yay... my calendar seems to have diappeared. I only have time in the clock widget now... [17:43] File "install-package.py", line 206, in showDetails [17:43] self.konsoleFrame.setVisible(false) [17:43] NameError: global name 'false' is not defined [17:43] * JontheEchidna facepalms [17:43] oh, python loves the capital letters [17:45] still, that is dumb [17:53] eek @ bug 551456 [17:53] Launchpad bug 551456 in kcm-touchpad "systemsettings crashes when clicking "Keyboard & Mouse"" [Medium,Triaged] https://launchpad.net/bugs/551456 [17:53] crashing for all non-admin users is very ungood [17:55] really, it's bad [17:59] I suppose that if it comes to it, we'll have to remove it from the final release... :( [17:59] though I can't reproduce it with a second user... [17:59] lex79: Where did this digikam patch come from? [18:00] ScottK: from here: http://bugs.kde.org/show_bug.cgi?id=232628 [18:00] KDE bug 232628 in Albums GUI "crash on startup in RatingWidget" [Crash,Resolved: fixed] [18:01] lex79: Is it committed upstream? [18:01] ... and did you test it? [18:01] I don't know, yes I tested [18:01] kde svn 1109177 [18:01] http://websvn.kde.org/trunk/?rev=1109177&view=rev | svn://anonsvn.kde.org/home/kde/trunk -r 1109177 | Fix crash in rating widget. Thanks for the hint. BUG: 232628 [18:01] Great. [18:02] Accepting. [18:02] thanks [18:02] shtylman was right. Chromium is fast. [18:03] Launchpad on the other hand .... [18:03] lex79: Let me amend that: Accepting if I can get Launchpad to play nice. [18:04] I imagine that the nice null return here is the root of our problems... http://paste.ubuntu.com/417082/ [18:04] * ScottK runs through his list of installed browsers [18:05] Does LP is slow? strange... [18:05] :D [18:06] Done. [18:06] k === yofel_ is now known as yofel [18:21] ScottK: I'm a bit confuse :) If we have switched from network-manager-kde to plasma-widget-networkmanagement, kubuntu-desktop shouldn't recommends plasma-widget-networkmanagement ? now it recommends network-manager-kde [18:21] bug 565584 [18:21] Launchpad bug 565584 in plasma-widget-networkmanagement "network-manager-kde removes plasma-widget-networkmanagement" [Undecided,Incomplete] https://launchpad.net/bugs/565584 [18:21] * ScottK looks at Riddell to fix. [18:22] * ScottK has lost track, but that sounds right. [18:22] we (should be) still using knetworkmanager [18:22] which is packaged as network-manager-kde [18:22] OK. I thought we switched. [18:23] and Conflicts: plasma-widget-networkmanagement is a sensible thing to do since the kded from that will get in the way of knetworkmanager [18:23] lo guys [18:23] any reason why you don't package KAudioCreator? [18:23] Tonio_: we're still using knetworkmanager (packaged as network-manager-kde) right? you haven't sneaked in plasma-widget-networkmanagement have you? [18:23] Riddell: something is wrong in the package then [18:24] tsdgeos: apachelogger was doing that, let me grep some logs to see what happened to it [18:24] if you want upgrade from karmic to lucid, plasma-widget wants install [18:25] tsdgeos: Because the KDE4 version appeared too late for this release. apachelogger put it in a PPA for now. [18:25] too late??? [18:25] Generally. [18:26] tsdgeos: we are in final freeze [18:26] Not sure if it appeared recently or we became aware of it recently. [18:26] apachelogger has the details. [18:27] logs say he hasn't put it in the archive because it's a beta [18:27] it's in the beta PPA [18:27] https://launchpad.net/~kubuntu-ppa/+archive/beta [18:27] otoh doesn't seems to work ... [18:28] OTOH this is a LTS release and we get all kinds of crap for releasing with beta stuff. [18:28] well, kaudiocreator has existed since 5 years at least [18:28] KDE3 version [18:28] waving the "too new" flag is a joke [18:29] Once it's final, we can do a backport from Maverick to Lucid. [18:29] it's not too new, ScottK is mistaken there, it's been out since October [18:29] Riddell: It's the beta release part I guess [18:29] but it is a beta and putting beta software into a main archive for an LTS isn't good practice [18:30] * ScottK clearly misremebered [18:30] upstreams get grumpy when we do that and we don't like to upset upstreams [18:31] Riddell: I have the debian/ dir for KOffice beta 2 ready, if you could upload it I would be grateful - http://dl.dropbox.com/u/69524/koffice_2.1.82-0ubuntu1.debian.tar.gz [18:31] Quintasan: groovy [18:32] Riddell: you care about grumpy upstreams now ;-) that card never worked for me [18:32] * tsdgeos teases poor Riddell [18:35] JontheEchidna: Did you upload install-package with a .bzr directory in it on purpose? [18:35] ScottK: oops [18:35] * ScottK rejects. [18:35] JontheEchidna: Feel free to reupload. You can use the same version again. [18:37] oh man [18:37] kaudiocreator code sucks :D [18:38] maybe beta PPA is too risky and we should put it in experimental :) [18:39] lex79: did you do a test upgrade from karmic? [18:39] Riddell: I left network-manager-kde as the default [18:39] Riddell: no issue on that point [18:39] Riddell: no, a guy here: https://launchpad.net/bugs/565584 [18:39] Launchpad bug 565584 in plasma-widget-networkmanagement "network-manager-kde removes plasma-widget-networkmanagement" [Undecided,Incomplete] [18:40] from the description "After upgrade the network applet has switched to new plasma-widget-networkmanagement." [18:41] lex79: that's a wanted purpose [18:41] it is normal [18:41] if he had both installed previously, that might have been why [18:42] lex79: that sounds like a very confused bug report [18:42] I know [18:42] :) [18:42] lex79: the plasma applet conflicts knetworkmanager [18:42] we don't want the plasma applet by default [18:42] so yes installing one drops the other [18:43] I'll be doing upgrade testing tomorrow so I'll make sure to check it's all sane [18:43] lex79: one thing : knetworkmanager was inside plasma-widget-networkmanagement in karmic [18:43] no split [18:43] I know also that..but if you have knetworkmanager and not kubuntu-desktop installed, why after upgrade you found plasma-applet instead networkmanager? [18:43] lex79: if the guy dist-upgrades and as no kubuntu-desktop, then I can understand why it ends with the plasmoid [18:44] lex79: but if you get the updated kubuntu-desktop, it all should work [18:44] lex79: hum, that's strange indeed [18:44] yes, we neead an upgrade test [18:45] lex79: yep [18:45] lex79: there is no reason why [18:45] knetworkmnager is provided by network-manager-kde [18:45] I see nothing in the deps that would explain this...... [18:45] lex79: I tested myself and saw no problem on that point [18:46] The reason I thought we switched was I got switched on upgrade. [18:46] Tonio_: ok thanks, did you do a test upgrade from karmic? [18:46] * ScottK didn't realize it was a bug. [18:46] lex79: lex79read the bug report [18:46] it "NORMAL" [18:46] :) [18:47] lex79: no kubnutu-desktop -> [18:47] for (int i; i < pendingJobs.count(); ++i) { [18:47] you have plasma-widget-networkmanagement, you keep it [18:47] ↑ AAAAAAAAAAAAAAAAAAAAAAAAAAa [18:47] the problem is that this package, previously did not contain the plasmoid, but the binary (stupid but that's it) [18:47] so yes, keeping the same package, the guy switched from the binary to the plasmoid, now the packaging is correct [18:48] Tonio_: the problem is not that ^^, the problem is why that guy with network-manager-kde after upgrade without kubuntu-desktop he found plasma applet in his system ;) [18:48] lex79: then he installed kubuntu-desktop, which depends on the network-manager-kde package, and that removed the plasmoid [18:48] I see no problem here [18:48] lex79: that's impossible :) [18:48] we hope ;) [18:49] lex79: the guy did NOT have network-manager-kde before the update [18:49] lex79: cause the package did NOT exist for karmic :) [18:49] it was plasma-applet-networkmanagement [18:49] oh [18:49] and knetworkmanager was in it [18:50] so yes, keeping the same package, it ended up with a switch [18:50] the guy always had the same package except the content was fixed [18:50] and installing kubuntu-desktop ended up installing the good package [18:50] so network-manager-kde [18:51] lex79: I hope it's clear now :) the packaging wfor karmic was stupid [18:51] cause we dropped the plasmoid [18:51] yes it's clear :) thanks [18:51] kept the binary, and got everything in a plasma-widget-networkmanagment package [18:51] now the packaging makes sense [18:52] lex79: one thing is sure, for people doing dist-upgrade and not having kubuntu-desktop package, there will be a switch [18:52] lex79: for those who will use the upgrade manager tool, no problem [18:52] dist-upgrade not supported, la la not our problem :) [18:52] ScottK: install-package is back in queue. Once you get a chance I'd appreciate a second look [18:53] Riddell: disyt-upgrade with no metapackage installed, not my problem [18:53] :) [18:53] ok, it seems a bit mess imho, but ok ;) [18:53] Riddell: metapackages are the base to get the new distro content [18:53] :) [18:54] Riddell: if you drop it, how can we make sure to switch correctly to new packages ? :) [18:54] lex79: yes, it is messy, cause the packaging was crap in the past [18:54] you can't [18:54] kk [18:54] cause we renamed it 3 times (plasma-widget -> plasma-applet, then -networkmanager to -networkmanagement [18:54] etc... [18:55] I just tried to make the packaging nice once and for all, I think it is nice now [18:55] and yes, without metapackages, there might be a little trouble [18:55] although people ending with the plasmoid isn't a big problem, it works very well [18:56] Riddell: so for testing upgrade karmic->lucid you don't use dist-upgrade? [18:56] lex79: you do, but also you reinstall the metapackage [18:57] ah [18:57] and that's were is the good transition from the old packaging to the new one [18:57] s/were/where/ [18:57] lex79: no, only the upgrade tool is supported [18:58] Riddell: but the upgrade tool is performing a dist-upgrade right ? along with many other tests... [18:59] yes, a dist-upgrade but with policies [18:59] so enforcing kubuntu-desktop or other meta package, allowing some file overwrites, forcing some packages to be removed and forcing others to be installed [19:00] and anything else we choose to include [19:00] kk ;) [19:00] just as I thought [19:00] any other method of disto version upgrade is liable to quirks [19:02] Riddell: I've done at least one dist-upgrade with backports enabled Hardy -> Lucid and Karmic -> Lucid and fixed all the replaces I ran into. [19:03] hi nookie^ [19:03] Such tests are, however, sensitive to package upgrade order which is not deterministic, so it takes multiple tries to get them all. [19:04] hi Riddell [19:04] nookie^: fancy doing a release countdown for us? [19:04] or indeed a release image of some sort [19:05] sure that could be done =) [19:05] Riddell: i'll try to start tomorrow... to busy today === ramanK is now known as Guest84881 [19:12] JontheEchidna: Unfortunately it would take more time than I have right now to understand the diff, so I'll leave install-package for Riddell. [19:24] I'll look at if after dinner, ping me if I forget === m4v is now known as MrTuerca === MrTuerca is now known as m4v [19:26] I use the beta2+latest updates on a thinkpad notebook [19:27] after booting the battery monitor shows that the ac adaptor is pugged in [19:27] but it's not plugged in! [19:28] if I type the cat /proc/acpi/ac_adapter/ACAD/state [19:28] it shows: state: off-line === mgraesslin_ is now known as mgraesslin [19:29] but if I plug in the ac adaptor and then unplug it , after that battery monitor works normally [19:29] wha'ts wrong? === ghostcube_ is now known as ghostcube [21:17] ScottK: re kde-l10n-sv FTBFS - be upset with upstream and shoot a deployment-fail report up their arse ... or mess with the common rules file to delete the breaking stuff for -svg, generall though I would simply not care because there was a successful build and hence the stuff is all imported + users have a 4.4.2 kde-l10n-sv to install [21:17] it just happens to not be the most recent one [21:18] apachelogger: Could you find a minion to fix it? [21:18] ScottK, Riddell: frankly, I think that I just forgot to poke into kaudiocreator upload ... IIRC it stroke me rather low on the quality and thus let me stop bothering getting it in [21:18] something like that [21:19] ScottK: our minons only know how to add dh magic line and cdbs magic lines [21:19] also, I think we are short on minions [21:19] because you were endorsing propsective motus without having them get new minions first :P [21:20] Sigh. [21:20] * ScottK bets lex79 could fix it. [21:21] thanks for consider me a minion...thanks thanks :( [21:22] btw someone should upload kdeplasma-addons from bzr :P [21:22] lex79: No. apachelogger said a minion couldn't fix it and I said you could [21:22] markey: I am wondering why a QCore class requires a gui? [21:22] That's the opposite of being a minion. [21:22] uhmmm [21:22] lex79: You should be recruiting though. [21:22] * apachelogger nods [21:23] apachelogger, ScottK: upstream l10n team said on kde-packager to lart the -sv team and to remove the files that are failing to compile [21:23] now [21:23] I know that [21:23] but [21:23] it is wrong on so many levels [21:23] remove the files ? lol [21:24] " [21:24] lex79: well, the lang team failed to QA their sources [21:24] My suggestion is to remove the file and not fix it, if the translator didn't [21:24] care to make sure it compiles, that is the first step, you can be sure it is [21:24] nto even been tested. [21:24] lex79: the other approach would be adding the appropriate entities to the list of entities [21:24] apachelogger: well, in this case I can do late or tomorrow morning [21:24] JontheEchidna: I fixed it for ubuntu2 [21:24] BUT [21:24] friends [21:25] the problem is of much greater influence than that [21:25] see [21:25] kde-l10n-* is built from the kde-l10n-common branch [21:25] that means the only way to prevent -sv from breaking at next upload is to add appropriate magic there [21:25] and then there is the implication that magic added there must not break the other packages [21:26] True, but I'd settle for just fixing that one for today. [21:26] so you'd first need to probe the current source package, then go awoga on it IF it is -sv [21:26] ScottK: I did that for ubuntu2 :P [21:26] there is no gain from fixing it again other than it not having show up on FTBFS liists [21:26] unless it is done in the rules of -common [21:27] except maybe larting the kde -sv team even harder if it shows up in 4.4.3 [21:27] that said, doing this implies that at least the changelog of -common gets bumped [21:27] Well we're stuck with https://launchpad.net/ubuntu/+source/kde-l10n-sv/4:4.4.2-0ubuntu6 not building [21:27] ScottK: ubuntu2 built [21:27] OK, so make ubuntu7 and have it biuld [21:27] build even [21:27] that implies that someone fixes up the /rules file in -common [21:27] and that said [21:28] THE ONLY solution is to lart upstream into realeasing a freaking fixed tarball [21:28] because honest to god, if KDE considers themself source-only distributors then I seriously wonder what kind of source distributor distributes broken soruces [21:29] which is another level of "why the approach of having distros fix this on their own" wrongness [21:29] markey: I dont get it, I really dont ... http://doc.trolltech.com/4.6//qcoreapplication.html#details [21:30] according to the docu QCoreApplicatoin is meant for non-GUI usage [21:31] it is [21:31] it's what quasselcore uses [21:32] apachelogger: what's markey's problem? [21:32] http://gitorious.org/amarok/amarok/commit/ac6fff90596e1f207dc7ae6e7c2b0f024b60c340 [21:32] http://gitorious.org/amarok/amarok/commit/8950ebc7726669011ab5369c334d059f8edee1d4 [21:32] I think that arch's qt is just $broken [21:32] because [21:33] ubuntu's buildds and chroot magic certainly doesnt give access to any X server (if even available) [21:33] apachelogger: Can't be. We suck compared to Arch. Everyone says so. [21:33] ScottK: non, see, we suck compared to chakra [21:33] apachelogger: no idea about QtScript [21:33] Well that too [21:33] Sput: well, take a look at the change [21:34] from QCoreApplication to QApplication [21:34] but QCoreApplication doesn't need X11 by itself [21:34] ScottK: see ... chakra is a fancy condom you pull over arch, so you dont have to call it arch, because the name sucks [21:34] apachelogger: no idea what those commits are supposed to save :) [21:34] Sput: that is my point, so what difference does that change make [21:34] Nice [21:35] s/save/solve/ [21:35] very odd really [21:37] yeah, well, so what's the bug it's supposed to solve? [21:38] Sput: unbuildability on systems without GUI I suppose [21:38] oh [21:38] * apachelogger just noticed that he patched it away in ubuntu ^^ [21:39] hm [21:42] heh, I got a chuckle out of the title for kde bug 234634 [21:42] KDE bug 234634 in general "took about an hour to update the dbinfo since i was using mc donalds free wifi so i forgot :(" [Crash,Unconfirmed] http://bugs.kde.org/show_bug.cgi?id=234634 [21:42] Oo [21:49] Sput: well, IMHO arch is bogus [21:49] even in a xless chroot the qtscript test works just fine with QCoreApplication [21:50] also it seems debian does have that too, since we inherit that get-rid-of-check-patch from tehre [21:50] apachelogger: can't comment on that without a build log [21:50] no clue what they do [21:51] Sput: nvm, I was just wondering since the change seems a bit mad [21:53] apachelogger: can't comment on that without a build log [21:53] :) [21:53] great [21:53] I get mail for xubuntu testers [21:53] \o/ [21:53] ScottK: can you please go poke some people in the eye? [21:54] apachelogger: That one is on my TODO, but I got distracted from my mail. [21:54] with a rusty spork! [21:55] * apachelogger is feeling busy for no apparent reason [21:55] very weird [21:57] I won't take Arch seriously until they get debug packages [21:57] otherwise I might as well just use Gentoo [21:57] lol [21:57] at least gentoo has a working Qt ;) [22:00] ScottK: mind throwing an ack at bug 566223 too, please? [22:00] Launchpad bug 566223 in gtk2-engines-qtcurve "Sync gtk2-engines-qtcurve 1.3.0-1 (main) from Debian sid (main)" [Wishlist,Confirmed] https://launchpad.net/bugs/566223 [22:03] JontheEchidna: maybe also merging kde-style-qtcurve... [22:03] lex79: that's why I said "too" ;) [22:03] oh :P [22:05] ScottK: actually, please reject. Breaks string freeze [22:05] Looking [22:05] OK [22:06] string freeze is that time of the year when translators have all the time they need to happily break upstream's translations ;) [22:06] well in this case upstream doesn't do translations, but... [22:06] * apachelogger takes that cynical reply of JontheEchidna's and tries to find some late night snack [22:09] actually, they do ship turkish translations [22:10] JontheEchidna: kde-style-qtcurve has new strings and at least one change. [22:10] Would you please review it and consider if we want it anyway or not. [22:12] ScottK: it's not vital. Just looks prettier [22:12] please reject it [22:12] OK. Doing. [22:13] Thanks. [22:14] Done [22:14] * ScottK ponders how best to use the 17% battery he has remaining.... [22:17] save it for an emergency? [22:18] Nah. [22:20] apachelogger: we also have debug packages :) [22:20] cool [22:20] see [22:20] gentoo is way better than arch [22:20] or... well, we have debug symbols, not packages [22:20] I mean, separate packages don't make sense for a source distro :) [22:21] that said, I've installed Chakra for my dad's computer, and it was quite a nice experience from an enduser perspective... installation was quick and smooth, and everything worked out of the box... also nice theming/branding [22:23] Quassel in the default install? [22:25] Sput: always that source distro excuse, it is getting old you know :P [22:27] Battery's about to go. This is a nice test of the double suspend fix. [22:27] See you all later. [22:27] ScottK: google alerts linked me to some chakra forum entry that suggests quassel recently made default in Chakra, yes [22:28] not using it myself, and wasn't contacted, so I can't tell if it's true really [22:29] apachelogger: what! no need to install an extra package if symbols are simply installed by building the binaries :) [22:29] Sput: and that is a reason not to have debug packages? :P [22:29] weak [22:29] simply weak [22:30] * Sput assumes apachelogger is joking rather than being stupid [22:31] Sput: you question my stupidness? [22:31] nah, it's unquestionable [22:31] good [22:34] schleep [22:41] * debfx is really annoyed by the dbus tray icon which isn't able to focus restored windows [22:49] ScottK: ping [22:49] ScottK: you dont happen to rember the city kwii is in , in germany do you ? [22:49] or Riddell ^^ [22:51] imbrandon: Hallstadt I think [22:53] apachelogger: ahh, thank you [23:00] debfx: that bug was in KStatusNotifierItem too [23:04] JontheEchidna: KStatusNotifierItem is the class that implements the dbus system tray [23:04] oh, I thought you meant dbusmenu [23:12] I wonder if most users aren't affected as I couldn't find a bug on launchpad [23:12] JontheEchidna: do you use chromium daily from ppa? [23:13] lex79: yes [23:13] debfx: Just took my netbook down to 5% power and then it autosuspended (once) and then resumed after I got to power. All very nice and smooth. Thanks again for fixing. [23:13] JontheEchidna: http://code.google.com/p/chromium/issues/detail?id=41467 [23:13] ^^ that is very annoying [23:14] yeah, I have that [23:15] it's really bad when you have to paste here the url from pastebin site [23:15] you have to write http:// manually [23:15] bah [23:16] and...it's not a bug...it's a feauture lol [23:16] ScottK: you're welcome :) [23:18] re [23:18] Sput: you pinged me? [23:20] ScottK: I have a fix in bzr for kdeplasma-addons...I tested it and works [23:20] maybe you can upload... [23:21] lex79: If I upload it, I can't be the release person that accepts it, so see if you can get JontheEchidna or apachelogger to upload. [23:22] kk [23:52] Riddell: quick, like a bunny. shouldn't you be sleeping?