[12:16] <fdoving> imbrandon: it's a compilefix to make the package compile on ppc. + minor improvements.
[12:18] <fdoving> it'll probably be the last version of that package, as schedutils will be included in the next util-linux release (2.13).
[12:23] <imbrandon> fdoving: ok uploaded , /me is afk for ~1 hour
[12:23] <fdoving> imbrandon: ok, thanks a bunch :)
[12:45] <hollywoodb> I'm curious about sudo behaviour in (k)ubuntu... after a few days using 6.10 I have anywhere from 5 to 20 'sudo' processes Sleeping, and similar numbers for kdesu
[12:46] <orkid> try asking in #kubuntu
[12:46] <Riddell> it's a fair developer question
[12:47] <Riddell> although I can't recreate the problem
[12:47] <orkid> true, but i thought it might get better support there
[12:47] <hollywoodb> I've asked there a couple times this past week, no real answers.
[12:47] <Riddell> yes, you'll get more of a developer answer here :)
[12:47] <hollywoodb> I'm not really familiar with sudo other than how to use it, same goes for kdesu ;)
[12:47] <Riddell> kdesu does start a redundant sudo, before the real sudo
[12:47] <Riddell> but there's no reason why it should be sleeping
[12:47] <fdoving> does sudo on the commandline work as expected?
[12:48] <hollywoodb> fdoving: yep, works fine
[12:49] <hollywoodb> although I can't always recreate the problem, it seems a bit random
[12:49] <fdoving> do you have a bunch of sudos running now?
[12:50] <fdoving> sleeping.. that is.
[12:50] <hollywoodb> fdoving: no, fresh boot not too long ago
[12:50] <fdoving> ok.
[12:54] <hollywoodb> I believe it may be linked to running synaptic from Kmenu, as it seems there's about a 30% chance nothing will happen (visually) other than startup notification... one second
[12:54] <hollywoodb> http://rafb.net/paste/results/Ddp5wJ22.html
[12:55] <hollywoodb> that's what I get immediately after a 'failed' attempt to start synaptic via kmenu
[12:55] <fdoving> hollywoodb: next time you experience it, you can run: 'for pid in `pidof sudo`;do cat /proc/$pid/cmdline;echo \n;done' from konsole, and then save the output to a file and come back. I guess it'll say something like '/usr/bin/sudo-uroot/usr/bin/kdesu_stub-n' - then it'll be kdesu magic.
[12:56] <fdoving> correct.
[12:56] <fdoving> but that's only one.
[12:56] <hollywoodb> fdoving: I bet if I keep launching synaptic I can get some more ;)
[12:56] <fdoving> it didn't start, it just sleeps in the background?
[12:57] <hollywoodb> fdoving: correct, its working now, but about 30% of the time I get the startup notification (bouncing cursor, etc), and nothing else but that
[12:57] <fdoving> hmm.. is this edgy?
[12:57] <hollywoodb> fdoving: aye
[01:00] <fdoving> you're in the admin group, and the admin group is in /etc/sudoers, right?
[01:00] <fdoving> you haven't modified /etc/sudoers?
[01:00] <fdoving> do you experience problems with the Administration Mode.. buttons in system settings?
[01:02] <hollywoodb> fdoving: no problems there, I'm in admin, /etc/sudoers is correct...
[01:03] <fdoving> you can -try- to add your user on a separate line in /etc/sudoers, If it works it must be a bug in sudo.
[01:03] <fdoving> .. i've seen various threads on forums etc. with that solution.
[01:03] <fdoving> s/solution/workaround/
[01:04] <fdoving> haven't experienced problems with kdesu in edgy though..
[01:04] <hollywoodb> fdoving: I'm wondering if it isn't kdesu... I'll keep playing around and seeing if its just synaptic, or I can get the same effect with 'Administrator Mode', Adept, other things that use kdesu... if it persists I'll try adding myself to /etc/sudoers as well
[01:04] <fdoving> good.
[01:04] <fdoving> please come back with your testresults :)
[01:05] <hollywoodb> fdoving: will do, though will probably take a few days to get some reliable numbers ;)
[01:06] <fdoving> sure, not a problem :)
[01:14] <fdoving> nite.
[02:35] <jjesse> so i can change my repositories to fiesty yet and start upgrading?
[02:36] <nixternal> sure
[02:36] <nixternal> i did it on my test machine
[02:36] <jjesse> any big changes yet?
[02:37] <nixternal> there is a memory leak somewhere though, and i haven't put my finger on it just yet
[02:37] <nixternal> no
[02:37] <nixternal> pretty much just the kernel that you have to manually update after doing the dist-upgrade
[02:55] <nixternal> alrighty...looks like i have some packaging free time tonight...what "needs" to get done?  don't sling me kde4 or something like that either, or i will /part and run away crying
[05:00] <Jucato> imbrandon: are you free for a question?
[05:03] <nixternal> no Jucato, he charges
[05:03] <Jucato> lol
[05:04] <Jucato> btw nixternal, I think there might be a typo or error in UWN. I'm not sure what the sentence really means, though
[05:04] <Jucato> nixternal: "No, this is a team for representing Ubuntu at Burning Man, rather to work on the burning infrastructure in Ubuntu."
[05:05] <Jucato> ah
[05:05] <Jucato> sorry, I just thought, you were partly involved :)
[05:05] <nixternal> isn't Burning Man like 6 months away?
[05:05] <nixternal> i have a friend who goes to those things
[05:06] <nixternal> actually it is a year away now
[05:06] <nixternal> it was end of aug, beginning of sep
[05:06] <Jucato> ah
[05:10] <nixternal> man..i want to get to packaging..but i don't want to step on some toes
[05:11] <nixternal> get some of the upstream releases rockin'
[05:11] <nixternal> if there are any ;)
[05:11] <Jucato> haha
[05:12] <nixternal> i stepped on toes for gwenview last release..don't want to do that again
[05:14] <Jucato> ouch.. quite traumatic. did they get mad?
[05:15] <nixternal> not publically, but it was already someone elses project
[05:15] <Jucato> ah
[05:48] <viviersf> Riddell, ping
[06:06] <lnxkde> a present for kubuntu-devs
[06:06] <lnxkde> http://www.destructoid.com/elephant/ul/27909-SantasDead.jpg
[06:17] <nixternal> hahaha
[06:25] <jjesse> that's a funy picutre
[06:26] <Mez> present for the kubuntu devs - http://bazaar-vcs.org/
[06:27] <crimsun> (surely you meant tailor?)
[06:28] <Jucato> excuse me crimsun, what do you think about this sentence in UWN? it looks/sounds a bit strange: "No, this is a team for representing Ubuntu at Burning Man, rather to work on the burning infrastructure in Ubuntu."
[06:28] <jjesse> i think it should be no this is not a team
[06:30] <jjesse> just edit the wiki page
[06:31] <Jucato> ah I'm allowed to do that?
[06:31] <jjesse> sure
[06:31] <Jucato> ok editing :)
[06:32] <Mez> wheres the link for UWN (seeing as I work on the burning team)
[06:32] <Jucato> Mez: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue21 but I just edited it :(
[06:33] <Jucato> I think I just did... ouch...
[06:34] <crimsun> imo, it should be clarified to mention "programs used for CD and DVD creation in Ubuntu" instead of "burning infrastructure in Ubuntu"
[06:34] <crimsun> it's not immediately obviously to unclueful people what burning entails
[08:54] <Jucato> poor desk...
[08:55] <Jucato> ouch... poor me :)
[08:55] <Mez> :lart Jucato
[08:55] <Jucato> @lart Mez
[08:55] <Jucato> oops.. not working in here :)
[08:56] <Mez> lol
[08:56] <Jucato> Hobbsee: !!!!!
[08:57] <Hobbsee> hey Jucato!
[08:57] <Jucato> go go go!! :)
[08:57] <Jucato> Hobbsee: btw, were you involved much already during Dapper's development?
[08:57] <Jucato> uh oh...
[08:57] <Mez> /kb Hobbsee mwahahaa
[08:57] <Hobbsee> Jucato: some of it.  the merging, yes
[08:58] <Hobbsee> i left a couple of days before feature freeze, and didnt end up doing much after that.  apart from all teh dh_iconcache stuff
[08:58] <Jucato> ah
[08:58] <Hobbsee> Mez: traitor
[08:58] <nixternal> Kubuntu is like a box of chocolates, you never know what your gonna get
[08:58] <Mez> Hobbsee, i believe i turned off ctvp replies
[08:59] <nixternal> hiya Hobbsee!
[08:59] <Hobbsee> hey nixternal
[08:59] <Hobbsee> Mez: you didnt
[08:59] <Hobbsee> Mez: and you're still a traitor
[08:59] <Hobbsee> [18:58]  [CTCP]  Received CTCP-VERSION reply from Mez: xchat 2.6.6 Ubuntu
[08:59] <Jucato> O_O
[08:59] <Mez> Hobbsee, weird,
[08:59] <nixternal> g'nite all
[08:59] <Mez> i've set it to null in xchat
[08:59] <Hobbsee> night nixternal
[09:00] <Jucato> goodnight nixternal!
[09:01] <Mez> y am i a traitor ?
[09:01] <Mez> and Hobbsee try the ctcp version again
[09:01] <Jucato> xchat 2.6.6 Ubuntu <---
[09:01] <Mez> Jucato, so? I dont use kopete either, I dont like the interfaces and xchat does more for me
[09:01] <Jucato> I think that's what Hobbsee meant...
[09:02] <Hobbsee> hah
[09:02] <Hobbsee> [19:01]  [CTCP]  Received CTCP-VERSION reply from Mez: foo baaaaaaaaaaaaaahhhhhhhhhhhh
[09:02] <Hobbsee> Mez: was meaning traitor for not using konversatoin
[09:02] <Jucato> lol
[09:10] <Riddell> viviersf: hi
[09:14] <Hobbsee> raphink: ping?
[09:14] <Hobbsee> hey Riddell
[09:20] <Riddell> dear kdebase, why can't you just be a good boy and compile!
[09:21] <Mez> Riddell, is that s2d or s2r ?
[09:22] <Hobbsee> Riddell: because it's fun not compiling!
[09:35] <raphink> pong Hobbsee
[09:35] <raphink> writing your letter to father christmas, asking for a kdebase that builds?
[09:35] <Hobbsee> raphink: i've just fixed bug 72116 in feisty - what did you want to do in dapper?  (it's installing bible time in arabic)
[09:35] <Ubugtu> Malone bug 72116 in bibletime "Bibletime installation defaults in Arabic" [Undecided,Fix released]  http://launchpad.net/bugs/72116
[09:36] <raphink> huh?
[09:36] <Hobbsee> sorry, s/dapper/edgy/
[09:36] <Hobbsee> raphink: you're the maintainer, arent you?
[09:36] <Hobbsee> or the one involved in it?
[09:36] <raphink> it's not about bibletime
[09:36] <raphink> it's about the sword-text-arasvd package
[09:37] <Hobbsee> they're all providing sword-text
[09:37] <raphink> the problem is that bibletime suggests sword-frontend
[09:37] <Lathiat> Hobbsee: hrm i cant stand gui irc clients
[09:37] <Lathiat> Hobbsee: irssi beats all
[09:37] <raphink> yes osrry
[09:37] <Hobbsee> Lathiat: heh
[09:37] <raphink> sword-text
[09:37] <raphink> which is a virtual package provided by all sword-text_*
[09:37] <raphink> and arasvd is just the first one in the list
[09:37] <Hobbsee> raphink: yes, so i changed it to recommend sword-text-web, so it's in engly
[09:37] <Hobbsee> *eng
[09:37] <Hobbsee> yes
[09:37] <raphink> yes, but no
[09:37] <raphink> I don't agree
[09:38] <raphink> it should recommend the sword-text virtual package
[09:38] <Lathiat> Hobbsee: also has the added advantage of being available to me from everywhere i go and sometimes even from my phone :)
[09:38] <Hobbsee> Lathiat: true
[09:38] <raphink> it's aptitude that's faulty, the not the package
[09:38] <raphink> :p
[09:38] <Hobbsee> raphink: but the sword-text virtual package that doesnt exist
[09:38] <raphink> if people want to use aptitude and install suggested packages by default
[09:38] <raphink> it's not my fault
[09:38] <raphink> yes it does exist Hobbsee
[09:38] <Hobbsee> raphink: yes, well, you can fix aptitude instead.
[09:38] <raphink> it's not about fixing aptitude
[09:38] <Hobbsee> it's provided by - it's not a straight package
[09:39] <raphink> if people choose to use aptitude, they deal with the consequences
[09:39] <raphink> which is that it installs tons of crap you don't need
[09:39] <Hobbsee> how would you prefer to fix it?  you're free to revert my changes, if you want
[09:39] <Hobbsee> how does apt handle it?  doesnt apt install recommends by default too now?
[09:39] <raphink> apt doesn't install suggested packages
[09:39] <raphink> not that I know of
[09:39] <raphink> or recommends
[09:39] <raphink> it only install depends
[09:40] <Hobbsee> sarah@sarah:~$ show bibletime | grep sword-text
[09:40] <Hobbsee> Recommends: sword-text, sword-dict, sword-comm
[09:40] <raphink> and considers that people are smart enough to read the recommends and suggests fields
[09:40] <Hobbsee> it's recommends.  and i believe that's changing?
[09:40] <Hobbsee> you're right, apt still doesnt install by default
[09:40] <raphink> thankfully
[09:40] <raphink> it'd be a mess otherwise
[09:40] <raphink> dealing with server installations
[09:40] <Hobbsee> so the bug is really only about aptitude - are you suddenly saying that you dont care about aptitude users?
[09:40] <Hobbsee> true that
[09:40] <raphink> if apt installed all the recommends each time
[09:41] <raphink> so well
[09:41] <raphink> people choose to use aptitude
[09:41] <Lathiat> recommends should be used better i guess
[09:41] <raphink> they deal with the fact that they get lots of stuff
[09:41] <Lathiat> for 'dependencies' that wont break the apckage if not installed
[09:41] <raphink> I'm not responsible for this
[09:41] <raphink> I'm sorry to take it this way Hobbsee
[09:41] <raphink> but I've seen aptitude break things, break metapackages stuff and so on
[09:41] <Hobbsee> true.  so the recommends only affect aptitude users.  do we fix the recommends for them?  or do we just say "screw you, for not using the deafult install method"
[09:41] <raphink> while apt-get works properly
[09:42] <Hobbsee> i know that.  but we probably do need to support it.
[09:42] <raphink> what is the spec for the recommendation field in Policy?
[09:43] <crimsun> 7.2
[09:43] <crimsun> it doesn't say that virtuals can't be used.
[09:43] <raphink> right
[09:43] <raphink> I think aptitude shouldn't take the first package matching the virtual package
[09:43] <raphink> it should use debconf to give a list of available packages providing it
[09:43] <raphink> and let the user choose one or more
[09:44] <raphink> that's where the problem is
[09:44] <raphink> that aptitude will take the first matching package
[09:44] <raphink> same for apt actually
[09:44] <raphink> when dependencies are |
[09:44] <Hobbsee> true
[09:44] <raphink> it takes the first one
[09:44] <raphink> instead of asking to choose
[09:45] <viviersf> Riddell, hello, i need sum info [;z
[09:45] <viviersf> *plz
[09:45] <raphink> so if you want the second option, you have to install it first, otherwise it will installl the first one
[09:45] <raphink> Hobbsee: you get the reason why I didnt' fix this bug though
[09:45] <raphink> (didn't know it was reported on LP in the first place, I some users had complained about this arasvd thing)
[09:45] <Hobbsee> raphink: true that.
[09:45] <raphink> (and everytime they were using aptitude)
[09:46] <Hobbsee> raphink: indeed.  so obviously aptitude's screwed, but the workaround to that is to default to english, presumably
[09:46] <raphink> so I just told them to use an install manager that let them control what they install, and it would be better
[09:46] <raphink> Hobbsee: I don't call that a workaround
[09:46] <Hobbsee> seeing as the arabic package anyway is installed with all the arabic language packs, as a rdep of ichutux live
[09:46] <Hobbsee> what's better?
[09:46] <raphink> Hobbsee: although if you're going to do that, please put sword-text-kjv instead
[09:47] <Hobbsee> you're free to change it, if you wanted
[09:47] <raphink> because web is not a recognized translations by many people
[09:47] <raphink> sure
[09:47] <Hobbsee> yet kjv is old english?
[09:47] <raphink> I'd rather think of a better solution though
[09:47] <Hobbsee> i'm fine doing it, if you want
[09:47] <Hobbsee> true
[09:47] <Hobbsee> raphink: want me to take care of it, as i've got it here?
[09:47] <raphink> yes Hobbsee, but some people (for some reason) consider it to be the only proper translation into english
[09:47] <Hobbsee> true
[09:47] <Hobbsee> i think they're nuts, but true :)
[09:47] <raphink> I don't agree with them either Hobbsee, but they are numerous
[09:48] <raphink> and it's true that KJV is a very good translation
[09:48] <Hobbsee> yeah
[09:48] <raphink> my choice would be to recommend WLC and TR though
[09:48] <raphink> :)
[09:48] <Hobbsee> what's TR?
[09:48] <raphink> Textus Receptus, Old Greek New Testament
[09:48] <raphink> and WLC is Westminster Codec, Old Hebrew Old Testament
[09:48] <raphink> :)
[09:49] <raphink> to me, that's the default
[09:49] <Hobbsee> ahhhh
[09:49] <Hobbsee> hehe
[09:49] <raphink> original texts :)
[09:49] <Hobbsee> yes, but most people cant read that :P
[09:49] <raphink> well as original as possible that is
[09:49] <Hobbsee> true
[09:49] <raphink> Hobbsee: then they will install additional modules
[09:49] <Hobbsee> yes
[09:49] <raphink> that's why I've made the sword-language-packs
[09:49] <raphink> apt-get install sword-language-pack-en
[09:49] <Hobbsee> yep
[09:49] <raphink> and you get english texts and commentaries
[09:49] <raphink> even, language-selector will take care of it
[09:49] <Hobbsee> raphink: fixed.  true
[09:49] <raphink> if you have libsword6 installed
[09:50] <raphink> brb
[09:51] <fdoving> raphink, hobbsee, did you read https://wiki.ubuntu.com/RecommendsSupport ?
[09:52] <Hobbsee> fdoving: ages ago, yes. i thought that might be happening someimte soonish
[10:16] <raphink> I wouldn't want apt to install recommends
[10:16] <raphink> if that were to happen, a lot of companies would remove Debian/Ubuntu from their machines
[10:17] <raphink> think of the cli packages that recommend guis and how it would install GNOME or KDE on servers
[10:17] <raphink> just an example
[10:27] <fdoving> for the metapackage section, it's nice.
[03:15] <seaLne> should feisty actually work?  i appear to have a machine that doesn't even start now
[03:19] <hunger> seaLne: It does here...
[03:20] <hunger> seaLne: But actually I try to avoid rebooting this early in the development cycle:-)
[03:22] <seaLne> i'd replaced to much to continue :)
[03:22] <seaLne> ah it appears to not like lvm everything (apart from /boot)
[03:32] <seaLne> but i have no idea how to get around this, anyone know if you could mount lvm stuff from knoppix?
[03:33] <seaLne> or i suppose kubuntu live cd
[03:42] <bddebian> Heya
[03:42] <Jucato> hi bddebian
[03:42] <bddebian> Hi Jucato
[06:12] <fdoving> hmm.. and suddenly xrandr doesn't work.
[06:54] <Tm_T> Hmm, some different hardware under test now, old random pc stuff, have some difficulties to install succesfully.
[08:32] <nixternal> \sh_away: im trying my hand at kdiff3 merge right now, if everything goes well and it is alright with you, i can have it uploaded
[08:33] <nixternal> anyone else want some help on mergest, let me know
[08:59] <ubotu> Announcement from my owner (Seveas): ubuntusecurity
[09:03] <allee> fdoving: about UNRELEASED.  I would just  replace the unreleased entry with the kubuntu entry and only add a note :  Added debian changes from alioth: ..
[09:03] <fdoving> allee: ok.
[09:03] <allee> fdoving: at the top you can then list what you changed additionaly
[09:04] <allee> fdoving: about branches....
[09:04] <allee> fdoving: have not investigated how this works.  fabo (ping;) wanted to look into it.
[09:05] <fdoving> ok.
[09:05] <allee> fdoving: as long as the change is valid for debian & kubuntu  just commit to trunk
[09:05] <fdoving> Would be great to have a central place to commit changes.
[09:05] <allee> s/just//
[09:06] <allee> when we need kubuntu specific changes, then we have to use branches of course
[09:06] <fdoving> I could version this the debian-way then.. and have the changes commited to alioth.
[09:07] <allee> fdoving: pkg-kde-extras was added to buildserver.net wich build sid/etch/sarge & edgy,dapper pkgs automaticly.
[09:07] <fdoving> not that it's in any way necessary.
[09:07] <fdoving> nice :)
[09:07] <fdoving> where are those packages to be found?
[09:07] <fdoving> multiple arches too?
[09:08] <allee> fdoving: for this work automaticly I assume the kubuntu branch needs to be at a special place.  Not looked into this yet
[09:08] <doelman> hi
[09:09] <doelman> anyone experience with pptp?\
[09:10] <fdoving> doelman: what's the problem with it?
[09:10] <doelman> i can't connect to the windows vpn on my work using pptpconfig
[09:10] <allee> fdoving: http://buildserver.net   (but today it seem to have (web?) problems)
[09:10] <doelman> not on kubuntu, not on mandriva
[09:11] <fdoving> doelman: ok. I have very little experience with the client side, I have setup the server side a few times..
[09:12] <doelman> the server is running windows
[09:13] <allee> fdoving: ah, one more thing about UNRELEASED.  It's kept like that until upload to debian happens.  If you kwlan changes are valid for debian too.  Leave it, commit to trunk and ask on pkg-kde-extras ml for an upload.
[09:14] <fdoving> allee: ah.. smart :)
[09:14] <allee> fdoving: yeah, then you can pick the original and no ubuntu1, no merging later ;)
[09:15] <fdoving> that's the idea, do everything once, and proper. in debian, and then just let the magic-scripts do the rest for ubuntu and universe.
[09:16] <allee> fdoving: yeah. this may I maintain digikam* kipi* pkg for a long time :)
[09:16] <allee> s/may/way/
[09:19] <toma> allee: do the ftp masters have to accept mailody before the builds happen?
[09:19] <allee> toma: yes
[09:20] <toma> allee: how long does that take approx?
[09:20] <allee> toma: in my between 1 day and 6 weeks (worst ;)
[09:20] <toma> allee: what happens when i release rc2?
[09:21] <allee> toma: I'm not sure how fast stuff is currently handled.  Depends on time in release cicle.  Maybe #debian-qt-kde knows more
[09:21] <toma> hmpf
[09:21] <toma> okay
[09:22] <allee> toma: rc2 is no problem.  when rc2 is upload, ftpmaster checks latest one
[09:22] <toma> o ok
[09:22] <toma> great
[09:22] <allee> toma: my last pkgs (some moon back) took only 1-3 days
[09:23] <toma> allee: i'ld like to see some build logs before the final
[09:23] <allee> toma: and that it's for experimental  on the other hand may speed it up ;)   AFAIR the work in first upload first served mode.
[09:24] <allee> toma: mhmm, should buildserver.net give you this?  AFAIK they check and build as long as it's UNRELEASED
[09:24] <toma> allee: its down since the upload
[09:24] <toma> cant chack
[09:24] <allee> yeah. :(
[09:25] <toma> before that it had data of june, so i'm starting to think its doing something now ;-)
[09:25] <allee> did you bug kk@ about it (as listed in the web page?
[09:25] <toma> no
[09:25] <toma> i'm the patient type ;-)
[09:26] <allee> :)
[09:27] <fdoving> allee: are the upstream orig.tar.gzs commited to svn aswell?
[09:27] <fdoving> for ../tarballs that is..
[09:27] <allee> toma: about the -dbg pkgs.  Doesn't krashmanager in kubunt download gdb and -dbg on demand
[09:27] <allee> ^ AFAIK
[09:28] <allee> fdoving: no orig.tar files   as well as upstream no sources
[09:28] <toma> allee: no idea at all
[09:28] <allee> fdoving: so in 95% of the cases alioth has content only in debian/
[09:29] <allee> fdoving: but svn-buildpkg has support to only svn add/remove upstream files that are patched + debian dir of course
[09:29] <fdoving> allee: where does buildserver.net go for orig.tar.gzs ?
[09:29] <allee> fdoving: but I'm a fan of all changes in debian/
[09:30] <fdoving> Let's say I bump the version in pkg-kwlan/trunk/debian/changelog to 0.5.6-1
[09:30] <allee> fdoving: look that the rules file: the all (should) end with
[09:30] <allee> +get-orig-source:
[09:30] <allee> +       @@dh_testdir
[09:30] <allee> +       @@[ -d ../tarballs/. ]
[09:30] <allee> +       @@dpatch-get-origtargz ../tarballs
[09:30] <fdoving> it does.
[09:30] <allee> (without +)
[09:30] <allee> that the way the buildnet server download the orig file
[09:31] <fdoving> ah.. it's the watch file.
[09:31] <fdoving> that is so smart.
[09:31] <allee> never tried it, because I usually work on pkg before the official release
[09:31] <fdoving> why doesn't ubuntu have this?
[09:32] <allee> what? watch files?  They have
[09:32] <fdoving> (launchpad got soemthing, but it's to complicated and lacks docs all over the place)
[09:32] <fdoving> watch files, yes, but i'm thinking of the idea with a huge repo with most packages debian/ dirs in.
[09:33] <fdoving> and a debian/rules entry to get the orig.tar.gz. It's so clever.
[09:33] <allee> fdoving: they try hard with bzr in lauchpad.
[09:34] <fdoving> I uploaded kio-apt to bzr/launchpad. but I think the idea is to get the upstream source into launchpad aswell.. and that's not so clever imho. (you can add upstream svn/bzr/repos, etc).
[09:34] <fdoving> didn't really understand it that well.
[09:34] <fdoving> I'll do it the debian way for now. It's more elegant.
[09:34] <allee> fdoving: well having all source as other advantages, but needs much more resources.
[09:35] <fdoving> what about the homegrown projects with only tar.gz releases?
[09:36] <allee> fdoving: then debian in in the tarball and to run the rules file you already need to have the tarball ;)
[09:36] <allee> brb
[09:38] <fdoving> hmm.. how is get-orig-source trigered from svn-buildpackage?
[09:39] <allee> fdoving: svn-buildpkg uses the watch file
[09:40] <allee> fdoving: get-orig-source was newly added when the buildserver.net support was added
[09:41] <allee> fdoving: about 0.5.6-1  when it's out, replace current kwlan (0.5.5-2)  with it.  As long as UNRELEASED is used, the is no official 0.5.5-2 pkg
[09:43] <fdoving> allee: http://rafb.net/paste/results/slcBcJ94.html
[09:44] <fdoving> That's what happens when i move the orig.tar.gz away from ../tarballs/
[09:44] <fdoving> it doesn't download anything. because nothing triggers debian/rules get-orig-source
[09:44] <fdoving> is there a switch to svn-buildpackage I can't find?
[09:45] <fdoving> to make it download?
[09:52] <fdoving> ah.. there is --svn-prebuild
[10:03] <allee> fdoving: heh, I don't use svn-buildpkg.  I would have tried  make -f debian/rules get-orig-source ;)
[10:04] <allee> I've to leave.  until tomorrow night
[10:04] <allee> bye
[10:04] <fdoving> bye.
[10:04] <fdoving> :)
[10:43] <fdoving> hmm.. doesn't dpatch-get-origtargz understand the svn-ugrade part of the watch file?
[10:43] <Hobbsee> hey fdoving
[10:43] <fdoving> looks like it's just renaming the .tar.bz2s..  to tar.gz and continues happily.
[10:43] <fdoving> hi hobbsee.
[10:44] <fdoving> experienced with debian/watch files and  dpatch-get-origtargz ?
[10:44] <Hobbsee> nope
[10:45] <nixternal> sudo apt-get install nixternals-universe-domination
[10:45] <nixternal> why doesn't that work?
[10:45] <nixternal> i must have packaged it wrong
[10:46] <nixternal> ahhh, it seems i need to 'sudo apt-get --purge remove Hobbsees-sharp-pointy-stick-of-doom' first
[10:46] <nixternal> Hobbsee: i was already in there
[10:46] <toma> *eeks* pointy sticks?
[10:46] <nixternal> so it isn't null anymore
[10:46] <Hobbsee> then you cant talk!
[10:46] <nixternal> lol
[10:46] <Hobbsee> toma: yep.  there's a new version of kvpnc out, btw
[10:47] <nixternal> i think i found a vulnerability with /dev/null
[10:47] <toma> Hobbsee: ok, and you want me to make a mess of it?
[10:47] <toma> i'm very good at relicensing stuff to LGPL
[10:48] <Hobbsee> toma: well, if it's for debian...
[10:48] <Hobbsee> toma: or get allee to do it, but you're here :P
[10:48] <Hobbsee> whoever likes putting new versions of things in
[10:49] <toma> Hobbsee: i remember you have an account there as well, so maybe point a stick at yourself?
[10:49] <toma> as a good excersice (or however you write that word)
[10:50] <Hobbsee> toma: that's true.  that means i have to figure out how to use it?
[10:50] <Hobbsee> hehe.  exercise, i believe
[10:50] <toma> ah. thats a problem for me too
[10:51] <Hobbsee> toma: does that mean i have to NMU it?   presumably not
[10:52] <toma> Hobbsee: hmm. who is the regular maintainer?
[10:52] <Hobbsee> toma: kde extras
[10:52] <toma> keep that
[10:53] <Hobbsee> sorry?
[10:54] <toma> Hobbsee: you can prepare everything and send a mail to the ml with a request to upload
[10:55] <Hobbsee> oh right :)
[10:58] <Hobbsee> toma: oh damn, but i dont have a sid pbuilder.
[10:58] <Hobbsee> hmmm
[10:59] <toma> Hobbsee: sid and feisty should not be very different, i assume
[11:01] <Hobbsee> true
[11:01] <fdoving> you can make a sid pbuilder too :9
[11:02] <Hobbsee> true that
[11:02] <Hobbsee> or i can use a friend's
[11:02] <fdoving> I'm getting more and more pro working with a central vcs for packages, like alioth.
[11:02] <toma> i dont have one (assume i'm a friend here ;-))
[11:06] <Hobbsee> hehe
[11:20] <fdoving> ..try to remember something about converting tar.bz2s to tar.gz on the fly when running debian/rules get-orig-source (which again uses dpatch-get-origtargz, which uses the info in the debian/watch file if everything else fails.. ).
[11:23] <Hobbsee> unbz<tab>, gzip -9 resulting tar.  easy
[11:24] <fdoving> i know, but some existing tool -must- provide this functionality.
[11:24] <fdoving> uscan,uupdate,svn-upgrade.. something.
[11:24] <Hobbsee> maybe
[11:24] <Hobbsee> it's nto that long, anyway
[11:25] <fdoving> i have no plans on doing it manually, i want this to happen automatically.
[11:26] <Hobbsee> write a shell script for it
[11:54] <seele> imbrandon: wtf is going on in kansas?  from what i hear on the news its turning in to baltimore :P


[15:42] <nahuel_> Hi people
[15:42] <nahuel_> is there someone ?
[15:42] <nahuel_> I have a big issue in my ubuntu narwhal
[15:43] <nahuel_> I juste installed it, and I can have diacritics in my console
[15:43] <nahuel_> I have some "?" characters
[15:43] <nahuel_> Any idea what I can fix ?
[15:44] <nahuel_> any idea ?
[15:47] <charlie-tca> nahuel_: maybe a different font?
[15:47] <nahuel_> Hmmm
[15:48] <nahuel_> charlie-tca, I use "courier" that support diacritics, at least french diacritics...
[15:48] <nahuel_> I use it in my other computer under maveric
[15:55] <jibel> Riddell, which kubuntu flavor/arch did you smoketest ?
[15:56] <jibel> I mean variant not flavor
[15:57] <Riddell> jibel: i386 desktop and mobile
[15:58] <jibel> Riddell, thanks.
[16:00] <jibel> charlie-tca, did you test today's xubuntu images, does it looks good ?
[16:01] <charlie-tca> jibel: I did not test them all.
[16:01] <charlie-tca> upgrade failed completely, when I did not get an upgrade available prompt
[16:01] <charlie-tca> bug 756763
[16:01] <ubot4> Launchpad bug 756763 in update-manager (Ubuntu) "update-manager -d fails to allow upgrade from 10.10 (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/756763
[16:02] <charlie-tca> The good news is, what I was able to test worked really good
[16:02] <jibel> charlie-tca, oh yes. I've seen your bug report. I've tried to reproduce with a fresh maverick xubuntu but the upgrade button is there in update manager and it starts the upgrade when I click on it
[16:03] <charlie-tca> I actually went to my old maverick, which has the files and settings I used, and that is what fails.
[16:03] <charlie-tca> I fear if a fresh install passes, but a install someone is using fails, we have problems
[16:06] <jibel> charlie-tca, does 'DEBUG_UPDATE_MANAGER=1 update-manager -d' outputs something interesting ?
[16:06] <charlie-tca> Let me bring the system up and see
[16:10] <charlie-tca> jibel: I don't know how to read that output, I will have to pastebin it
[16:13] <charlie-tca> jibel: http://paste.ubuntu.com/592656
[17:08] <jibel> skaet, if you agree, I'll add a run once testcase for memtest (bug 683904) for Ubuntu alternate. the test is very easy to run, basically, it's 'select test memory and wait'
[17:08] <ubot4> Launchpad bug 683904 in grub2 (Ubuntu Natty) (and 1 other project) "natty: memtest86+ fails to run, reboots immediately (affects: 9) (dups: 1) (heat: 48)" [High,Confirmed] https://launchpad.net/bugs/683904
[17:09] <skaet> jibel,  sounds good.    go ahead.
[17:12] <samantha-jian> skaet: ping
[17:14] <skaet> samantha-jian, pong
[22:16] <jibel> mvo, around ?
[22:17] <mvo> jibel: yes, a bit sleepy though
[22:18] <jibel> mvo, oh, I didn't expect a reply :-)
[22:18] <jibel> hi btw.
[22:19] <jibel> mvo, what's your opinion about bug 757754. Not an emergency and this can wait tomorrow.
[22:19] <ubot4> Launchpad bug 757754 in xubuntu-meta (Ubuntu) (and 1 other project) "On XUbuntu upgrade maverick->natty update manager offers to install the whole gnome (xubuntu-desktop recommends indicator-messages) (affects: 1) (heat: 10)" [Medium,Triaged] https://launchpad.net/bugs/757754
[22:21] <mvo> jibel: well, I need to have a close look, but if that is undesired, then the recommend should become a suggests
[22:23] <mvo> jibel: oh, from reading the report its a virtual package? in thise case I could add a workaround in u-m or the xubuntu-desktop would recommend a non-gnome package first in the or dependency, does that make sense?
[22:28] <mvo> jibel: i commented in the bug
[22:28] <jibel> mvo, many thanks.I'll check with mrpouit tomorrow when he's online. Have a good night!
[22:29] <mvo> jibel: it looks a bit tricky, I will try to come up with a good idea over night
[22:29] <stgraber> mvo: did you start doing something for bug 745532 ? otherwise I'll probably have some time tonight to poke at it
[22:30] <ubot4> Launchpad bug 745532 in pam (Ubuntu Oneiric) (and 2 other projects) "fails to restart (not running) gdm on maverick->natty upgrade (affects: 1) (heat: 432)" [Undecided,New] https://launchpad.net/bugs/745532
[22:30] <stgraber> it's a not common use case that happens to be very common for LTSP servers :)
[22:31] <stgraber> (not that I usually upgrade these, but still worth fixing)
[22:31] <mvo> stgraber: please do then, I won't work on this tonight
[23:57] <skaet> all,  first set of images for beta2 are now getting uploaded to the iso tracker.   ubuntu desktop/alternate,  kubuntu desktop/alternate now available...


[00:55] <xxx> hi
[01:29] <tomorrow> the tinyurl in topic seems wrong
[01:29] <tomorrow> for friday are developers who use non-ubuntu invited?
[01:29] <tomorrow> (feel free to answer after I disconnect; I'll check logs)
[04:54] <avihay> anyone know what tomorrow was talking bout?
[15:21] <avihay> matanya: משרת סטודנט באזור חיפה במקרה?
[15:21] <matanya> עיר הקודש. משרה מלאה
[20:41] <rindolf> Hi all.
[20:42] <rindolf> moshe742: here?


[07:51] <persia> So, I'm a little confused by https://launchpad.net/builders
[07:51] <wgrant> What about it?
[07:51] <persia> I see some stuff as "private source" and other stuff in detail, when I know other folk see it as "private source".  What governs how it gets seen?
[07:51] <wgrant> persia: Whether you can view the archive in which it is building.
[07:52] <wgrant> Or the branch, soon.
[07:52] <persia> Ah.  So if it's building for a P3A to which I've been granted access, I can also see the builds, and if not, not?
[07:53] <wgrant> For the P3A case, 'granted access' meaning upload access, not just a subscription.
[07:53] <persia> OK.  That makes more sense.
[07:54]  * persia has to go dig through indirect memberships at some point : the mess is too complex
[10:56] <mrintegrity> hi, is there any integration between launchpad and netbeans?
[10:58] <persia> Not directly.  What sort of integration do you seek?
[10:59] <mrintegrity> versioning with bazaar
[10:59] <persia> Based on http://wiki.bazaar-vcs.org/IDEIntegration there is an open call for a plugin.
[11:00] <mrintegrity> cool
[11:00] <persia> Well, kinda.  Needs someone to write it :)
[11:00] <wgrant> #bzr may be better informed about Bazaar integration issues.
[11:00] <persia> Indeed.
[11:00] <mrintegrity> thanks
[11:01] <persia> And #netbeans on netbeans
[11:01] <mrintegrity> I have been using netbeans because of it's relatively good php and symfony support.. was wanting to use launchpad too
[11:01] <persia> Just needs a plugin.  Both bzr and netbeans have good plugin support.  This just isn't the best channel to ask :)
[11:02] <mrintegrity> ok, thanks :)
[11:10] <mrintegrity> think i will just have to use netbeans local versioning and then manually bzr it to launchpad
[11:26] <persia> How long should "Scanning for processes to kill in build" take?  https://launchpad.net/ubuntu/+source/gedit/2.29.9-0ubuntu2/+build/1569828 seems like it ought to have finished some time ago.
[11:26] <wgrant> Gnargh.
[11:27] <wgrant> How long has it been at that point?
[11:28] <persia> Dunno precisely.  At least half an hour.
[11:28] <persia> Finished was > 2 hours ago, but I'm unsure if there's lag in the rest of the commands for some reason.
[11:32] <wgrant> Oh, right, it's been a while, yeah.
[11:32] <wgrant> I've not seen a build hang there before.
[11:32] <persia> https://launchpad.net/ubuntu/+source/likewise-open/<IP_ADDRESS>111-1/+build/1568679 is even more extreme
[11:32] <manish> wgrant: You there?
[11:33] <wgrant> And let's not even mention https://edge.launchpad.net/ubuntu/+source/ghc6/6.12.1-12/+build/1526050
[11:33] <wgrant> manish: I am.
[11:33] <manish> wgrant: As you recommened using .NET libraries, I was digging through them
[11:33] <persia> wgrant: That's intentional, actually.  it has an infinite activity loop because it's expected to take 1-2 weeks to build.
[11:33] <manish> I stumbled across X509 certificates
[11:33] <wgrant> Hah.
[11:33] <manish> is it used in launchpad?
[11:34] <manish> i could not find it any the hacking document
[11:34] <wgrant> manish: Launchpad uses SSL, yes.
[11:34] <wgrant> Normal HTTP libraries take care of that for you.
[11:34] <manish> wgrant: just have a look at this http://code.google.com/p/devdefined-tools/wiki/OAuthConsumer
[11:35] <manish> this guy is using X509 certificates which he generated
[11:35] <manish> Google allows uploading X509 cerificates.. IIRC Lauchpad has no such option
[11:35] <wgrant> Oh, no, Launchpad doesn't use client certificates.
[11:35] <manish> then what should be done in this case?
[11:36] <manish> should I set that client certificate section to null?
[11:38] <manish> wgrant: so should I still use .NET Oauth libraries or continue from the code I showed you last night?
[11:38] <manish> means re-doing things
[11:38] <wgrant> I think you should use the provided library.
[11:38] <wgrant> You shouldn't need a certificate. I would check the code and see what it does with it.
[11:40] <manish> wgrant: even I am trying how to deal with it
[11:49] <qense> Will lazr-js get packaged for Lucid? I assume it's already too late, but I'd love it when it would.
[11:52] <wgrant> I don't know of any plans.
[11:53] <qense> ok
[11:53] <qense> then I'll use the branch
[11:54] <lifeless> bst way to get it packaged: do it
[11:55] <qense> of course
[11:55] <qense> maybe I'll provide a PPA, most of the work needed for packaging it is already done in setup.py and distribute_setup.py
[12:09] <persia> lifeless: Hey.  You use netbeans, don't you?
[12:37] <lifeless> persia: when I'm doing java stuff, yes
[12:38] <persia> lifeless: How do you use it with bzr?  Just bounce to CLI?
[12:45] <lifeless> persia: yes
[12:46] <lifeless> we need someone that use netbeans for java, knows bzr, and wants to build and maintain a bzr vcs plugin
[12:46] <lifeless> I don't have time :(
[12:46] <persia> Oh well.  I understand, but you meet all the other criteria so well :)
[12:48] <lifeless> I know :P
[12:48] <lifeless> I did actually branch netbeans to have a look
[12:48] <lifeless> but I ended up yak shaving bzr fast-import performance
[12:55] <persia> So instead of actually working on netbeans, you just made bzr good at hg?  That's still a win.
[12:55] <lifeless> better at
[14:04] <slacker_nl> hi,
[14:06] <slacker_nl> i'm backporting an appliction, did a backport to karmic, now want to do the same for jaunty. I only changed the release in the changelog and now I keep getting the following error File <UPLOADED_FILE> already exists in <LOCATION>, but uploaded version has different contents
[14:06] <nhandler> slacker_nl: Change the version to append something like ~jaunty1
[14:07] <slacker_nl> that is the only solution?
[14:07] <slacker_nl> mkay
[14:07] <persia> It is often wise, when uploading to PPAs, to upload to the *oldest* release you plan to support, and copy the packages to the newer releases, rather than work in reverse-chronological order.
[14:07] <mok0> slacker_nl: yes
[14:08] <persia> (it being usually more unsafe to copy backwards than copy forwards)
[14:09] <slacker_nl> persia: yes.. but.. i made the original backport request for karmic, just wanted to see if it would work in jaunty, if so, create a backport request for that..
[14:10] <persia> If you're using PPAs to preview the Ubuntu backport procedure then you need a new upload for each release, versioned as nhandler recommends.
[14:10] <slacker_nl> persia: but the oldest to newest approach would give me the same error?
[14:10] <slacker_nl> ok
[14:11] <persia> For normal PPA use (not backports prep), oldest to newest lets you copy without uploading again.  Usually this is fine.  Sometimes you need to reupload to fix something.
[14:11] <mok0> slacker_nl: this is also what happens when Ubuntu moves from one release to the next... binary packages are copied
[14:12] <slacker_nl> mok0: that I know
[14:13] <slacker_nl> i was just suprised that I need to change the version to upload the same package for different releases
[14:13] <slacker_nl> ce'st tout :)
[14:14] <mok0> slacker_nl: so if you do like persia says, you will understand that it works
[14:14] <slacker_nl> yes
[14:14] <slacker_nl> thnx for the help
[14:15] <slacker_nl> mok0/persia/nhandler ^^
[17:09] <rdb> Where can I change my password? This is a stupid question, but I can't find a link to change it anywhere.
[17:13] <nigelb> rdb: login.launchpad.net
[17:14] <rdb> nigelb, thanks!
[18:23] <slacker_nl> question, will it be possible to support debian release pockets for ppa's? is this somewhere on a roadmap/wishlist?
[18:30] <cwickert> maybe this is a comletely stupid question, but...
[18:30] <cwickert> when I'm on bugs.launchpad.net, where is the link to file a new bug or to the advanced search?
[18:39] <crimsun> cwickert: you need to pick a project
[18:39] <crimsun> e.g., bugs.launchpad.net/ubuntu
[18:40] <cwickert> crimsun, I don't want to query bugs, I want to file one.
[18:42] <cwickert> say I'm on bugs.launchpad.net and want to file a bug against launchpad. where is the link or where would I start?
[18:52] <crimsun> cwickert: bugs.launchpad.net/launchpad
[18:52] <crimsun> cwickert: trailing vertical edge, see e.g., https://bugs.launchpad.net/launchpad/+filebug
[18:53] <cwickert> crimsun, and how to i get from bugs.lp.net to bugs.pl.net/lp without googeling?
[18:54] <cwickert> IMO the start page of a bug tracker should have direct links to file and query bugs
[18:54] <cwickert> I just filed a bug, see https://bugs.launchpad.net/malone/+bug/542889
[18:55] <cwickert> bug why is it in "malone" and not in "launchpad"?
[18:55] <cwickert> https://bugs.launchpad.net/launchpad reads "bugs in launchpad itself"
[18:55] <crimsun> probably hysterical raisins
[18:56] <crimsun> it was originally called malone
[18:56] <cwickert> when I filed the bug I selected "launchpad itself" as project and the bug ended up in malone
[18:56]  * cwickert is confused
[18:57] <crimsun> I would be just as confused
[18:58] <cwickert> oh, I selected "launchpad bugs". not launchpad itself
[18:58] <cwickert> but I still don't get the difference
[18:59] <cwickert> anyway, thanks for your help
[18:59] <cwickert> c u
[19:24] <geser> "launchpad" is all of launchpad and should be used when filing a bug about launchpad and you don't know which LP sub-project is the correct one
[22:21] <geser> does https://edge.launchpad.net/builders/ list all available buildds? as I've a PPA build running on samarium which isn't listed on the builders page
[22:24] <wgrant> geser: Unless samarium has been marked un-OK or inactive recently, it should be listed.
[22:24] <wgrant> lamont: ^^?
[22:26] <lamont> hrm
[22:26] <lamont> I'll check that before filing my virt-manager bug
[22:27] <geser> it's just the listing on the overview page, as my PPA build got dispatched to samarium (10 min ago and currently building)
[22:27] <geser> I was just surprised to the see the amd64 build in the buildd overview page
[22:28] <geser> https://edge.launchpad.net/~geser/+archive/ppa/+build/1571098
[22:36] <lamont> geser: it's an interesting feature of the UI
[22:37] <lamont>  Active == Whether or not to present the builder publicly.
[22:37] <lamont> because that's a totally correct definition of the word
[22:37] <wgrant> Heh, yes, that was my suspicion.
[22:37] <wgrant> The field is unavailable publicly.
[22:38] <lamont> and I suspect that someone marked it inactive, and then it got cycled through the airlock.  I'll make sure that we mark the buildd active when we give it back to buildds
[22:39] <wgrant> Of course, I don't think inactive builders are actually listed anywhere.
[22:40] <lamont> wgrant: you can still go .../builder/$NAME
[22:40] <wgrant> lamont: Right, but you can't find them except by looking at build listings.
[22:41] <lamont> on the bright side, having fixed samarium, there are no builders where  active=false and manual=false and builderok=true
[22:41] <wgrant> How do you determine that? DB query?