UbuntuIRC / 2012 /12 /16 /#kubuntu-devel.txt
niansa
Initial commit
4aa5fce
[02:43] <ronnoc> http://www.kubuntuforums.net/showthread.php?61366-Country-set-to-US-no-matter-what-country-we-choose-at-startup&p=317840#post317840
[02:56] <ScottK> ronnoc: That's fixed in raring.
[03:40] <ronnoc> ScottK: ahhh thx
=== jono is now known as Guest95318
[04:06] <ScottK> ronnoc: Look at the linked bug.
=== LordOfTime is now known as TheLordOfTime
[13:18] <BluesKaj> Hi all
[13:32] <shadeslayer> /query Quintasan_
[13:32] <shadeslayer> erm
[13:32] <Quintasan_> hi
=== Quintasan_ is now known as Quintasan
[13:32] <shadeslayer> ...
[13:33] <Quintasan> be thankful it's not your nickserv password :P
[13:33] <shadeslayer> yeah
[14:49] <Mamarok> shadeslayer: who is that guy who moved a packaging request to wishlist on bug 1090689 ?
[14:49] <ubottu> Launchpad bug 1090689 in Kubuntu PPA "Please update amarok to 2.6.90" [Undecided,In progress] https://launchpad.net/bugs/1090689
[14:50] <Mamarok> that makes totally no snese at all
[14:50] <Mamarok> and I can't change it back
[14:50] * shadeslayer looks
[14:51] <shadeslayer> idk
[14:52] <shadeslayer> Mamarok: can you test amarok from kubuntu staging?
[14:52] <Mamarok> I don't use raring
[14:52] <shadeslayer> erm
[14:52] <shadeslayer> it's for quantal
[14:52] <shadeslayer> :P
[14:52] <Mamarok> and I have a git installation
[14:52] <shadeslayer> I already uploaded amarok for raring
[14:52] <shadeslayer> drat
[14:52] <shadeslayer> Amarok needs QA for quantal : https://launchpad.net/~kubuntu-ppa/+archive/staging
[14:52] <Mamarok> so installing a package would mean a lot of shuffeling for me
[14:53] <shadeslayer> !testers
[14:53] <ubottu> Testing help needed in #kubuntu-devel ping Riddell, yofel, soee, Tm_T, shadeslayer, BluesKaj, James147, smartboyhw, Quintasan
[14:53] <Mamarok> I can test a lot of other packages in staging, but not Amarok or Phonon as I run git versions
[14:53] <Quintasan> doing amarok
[14:53] <Mamarok> you guys rock :)
[14:54] <Mamarok> but really, somebody should tell that guy he should not triage stuff he doesn't understand
[14:55] <shadeslayer> :D
[14:55] <Mamarok> also, why does he have enough karma to modify that and I can't?
[14:55] <shadeslayer> I don't think that's a criteria
[14:55] <shadeslayer> you should be on the bug squad or sth
[14:55] <shadeslayer> or a developer
[14:55] <Mamarok> I am on the bug squad
[14:56] <Mamarok> but I apparently can't change that importance status
[14:56] <Mamarok> so really, someone should tell that guy to not touch stuff he is not even involved with
[14:57] <BluesKaj> BBL
[14:57] <Quintasan> shadeslayer: any idea why Mamarok can't change stuff like this?
[14:58] <shadeslayer> like I said, bug squad?
[14:58] <Mamarok> it's funny actually,as I can edit all other elements
[14:58] <Mamarok> shadeslayer: I am in the bug squad!
[14:58] <shadeslayer> oh
[14:58] * shadeslayer is talking to too many people
[14:58] <shadeslayer> both on IRC and in real life
[14:58] <Mamarok> told you already
[14:59] <shadeslayer> yeah, sorry
[14:59] <Mamarok> ah, that doesn't work well usually :)
[14:59] <Quintasan> nah
[14:59] <Mamarok> brb, have to watch that sunset
[14:59] <Quintasan> you need to be member of https://launchpad.net/~ubuntu-bugcontrol
[14:59] <Quintasan> Mamarok: ^
[14:59] <shadeslayer> that's what I kept saying except I didn't realize it was called bugcontrol and not bugsquad
[15:00] <Quintasan> Mamarok: I'm pretty much sure they will let you join as soon as you let them know you want to join
[15:01] <shadeslayer> you have to send an email
[15:02] <shadeslayer> Mamarok: https://lists.launchpad.net/ubuntu-bugcontrol/msg03799.html
[15:07] <EagleScreen> I try to figure out why Kubuntu still has a Kopete launcher in default kickoff menu
[15:07] <Quintasan> Mamarok: lastfm plugin is broken form e
[15:07] <Quintasan> for me*
[15:08] <Quintasan> hmm
[15:08] <Quintasan> libamarok_service_lastfm_shared.so
[15:08] <Quintasan> is not found where it's apparently needed
[15:08] <Quintasan> shadeslayer: ^^
[15:09] <shadeslayer> wat
[15:09] <shadeslayer> 0.o
[15:09] <Quintasan> don't wat me
[15:09] <Quintasan> it's just not there
[15:10] * shadeslayer checks
[15:11] <shadeslayer> !find libamarok_service_lastfm_shared.so quantal
[15:11] <ubottu> Package/file libamarok_service_lastfm_shared.so does not exist in quantal
[15:11] <shadeslayer> ^
[15:12] <shadeslayer> though you're right
[15:14] <Quintasan> either you fcksed something or it was not there to begin with
[15:15] <shadeslayer> Quintasan: can you check if the archive package in quantal works?
[15:15] <shadeslayer> -- Installing: /build/buildd/amarok-2.6.90/debian/tmp/usr/lib/libamarok_service_lastfm_shared.so
[15:15] <shadeslayer> -- Removed runtime path from "/build/buildd/amarok-2.6.90/debian/tmp/usr/lib/libamarok_service_lastfm_shared.so"
[15:15] <shadeslayer> lol
[15:17] <Mamarok> Quintasan: you need liblastfm 1.0.0
[15:18] <Mamarok> specified in the packagers mail
[15:18] <shadeslayer> hm
[15:18] <Mamarok> and liblastfm is in Quantal, I have it
[15:18] <Mamarok> so somebody made an error somewhere
[15:19] <Mamarok> current liblastfm is 1.0.3 for me
[15:19] <shadeslayer> yeah that's what got pulled in raring as well
[15:19] <shadeslayer> possibly because of Drop 0001-port-to-liblastfm1-api.patch
[15:19] * shadeslayer will get to this in a bit
[15:54] <shadeslayer> Quintasan: I'm unsure as to what the issue is, I believe the liblastfm1 patch was commited upstream
[15:55] <Quintasan> What you believe that happened doesn't actually match what actually transpired :P
[15:55] <Quintasan> has happened*
[15:55] <shadeslayer> :P
[15:57] <shadeslayer> see https://projects.kde.org/projects/extragear/multimedia/amarok/repository/revisions/edb764d3736d9e2076b2d67b719ad734d76c11ee
[16:09] <Quintasan> You clearly broke something then shadeslayer
[16:09] <Quintasan> Can't help that :P
[16:10] <yofel_> Mamarok, shadeslayer: packaging requests *are* usually Wishlist unless there is some reason why it would be important
[16:12] <Mamarok> yofel_: and why was that changed after it was already marked as "Fix committed"? That just makes on sense at all
[16:13] <Mamarok> and it is WIP by the developers, one more reson for a triager not it change a status in a package he is not even invlived with
[16:13] <Mamarok> involved*
[16:14] <yofel_> hm, he seems new to u-b-c, so maybe he as overly eager to do something. But I don't really see the problem here. It would be bad if he changed the Importance - but "Undecided" simply means "not set"
[16:15] <yofel_> so that doesn't really count as "changing"
[16:15] <yofel_> and those bugs should usually be wishlist - the bot just doesn't have the permission to set that
=== yofel_ is now known as yofel
[16:15] <yofel> dinner - bbiab
[16:15] <Mamarok> well, it is now in a state I can't change it back, despite me being a member of the bug squad and a Kubuntu member, that makes even less sense
[16:17] <Mamarok> so why can a guy who is new change a status and I who am actually involved in the project can't?
[16:23] <Riddell> Mamarok: he snuck into the right team maybe?
[16:23] <yofel> Riddell, Mamarok: he was accepted into Ubuntu Bug Control 6 days ago - and thus as the permission to change it
[16:24] <Mamarok> and why can't I change it? I am in the bug squad since a while longer :)
[16:24] <yofel> Mamarok: as shadeslayer said, you can apply for bug control membership as an upstream triager (and as such don't have to submit a list of bugs as work example)
[16:24] <yofel> Mamarok: bugsquad != bug control
[16:25] <yofel> bug importance is limited to https://launchpad.net/~ubuntu-bugcontrol
[16:25] <Mamarok> so I need to apply for something differnet now?
[16:25] <yofel> bugsquad IIRC doesn't even have an application form
[16:25] <Mamarok> what is the point of having different groups for bug triaging?
[16:26] <yofel> prevent new people that have no idea what they're doing for setting important bug settings
[16:26] <yofel> *from
[16:26] <Mamarok> well, apparently that is not preventing them from doing silly things :)
[16:26] <Mamarok> I agree it is a wishlist, but it is totally pointless changing something that is in status "Fix committed" and there is wip
[16:28] <yofel> not really, Ideally all bugs should have an importance set - unless they're closed maybe, then it really doesn't make sense. Fix committed doesn't count as closed though, Fix Released does
[16:30] <yofel> this is a bit of an arguable sitation - he didn't really need to set it, but setting it doesn't really hurt anybody either
[16:34] <Mamarok> yeah, but I am sure he could do more important work than changing a report that is open since only 2 days and already almost closed, there is much more stuff that lies around he can toy with
[17:42] <shadeslayer> odd
[17:42] <shadeslayer> possibly launchpad lost my package
[18:04] <shadeslayer> can someone run backportpackage on amarok and upload it to the staging PPA?
[18:04] <shadeslayer> LP doesn't seem to acknowledge my uploads
[18:55] <ronnoc> Posted some feedback on 13.04 Alpha to the G+ page
=== apol_ is now known as apol