1 from multiverse to universe" [Undecided,New]
<c_korn> they are fine
<stgraber> pochu: works?
<stgraber> pochu: that should be a "no new feature but everything's fixed" release, a bit last minute for Jaunty but we couldn't keep the one we had in so...
<pochu> stgraber: didn't update yet... shouldn't it?
<pochu> stgraber: you're a good upstream for that! :)
<stgraber> even the translations seem to work (except one string as it's been added yesterday and isn't translated on LP yet)
<Laney> jcfp: I need your python 2.5 wizardry. How did you manage to get rid of the << 2.6 dep on sab? I've a similar problem with another package...
<jcfp> Laney: it had to do with trying to provide a public module without supporting the default python version
<jcfp> which apparently isn't allowed unless the package name is something like pythonX.Y-modulename
<Laney> guh
<jcfp> In case of sab, solution was to make the module private
<Laney> might work, thanks
<torkel> siretart: thanks!
<sistpoty|work> hi folks
<ScottK> Hi sistpoty|work.
<sistpoty|work> hi ScottK
<cristi> savvas: hy!
<cristi> savvas: so what should i do in order to help out with the python packages update to 2.6 (i think)
<geser> cristi: you mean the python 2.6 transition?
<cristi> geser: yes
<geser> cristi: have you read the mail on ubuntu-devel what needs to be changed in the packaging of a package?
<cristi> geser: i am just getting started, i am still reading articles on the wiki. however i was told that it's not that hard to contribute to the python 2.6 transition
<cristi> geser: so the answer is no
<geser> cristi: it's really easy
<geser> (in most cases)
<cristi> what is really easy lol
1 from multiverse to universe " [ Undecided, New ] 
 < c_korn > they are fine 
 < stgraber > pochu: works? 
 < stgraber > pochu: that should be a " no newfangled feature of speech but everything's fixed " release, a piece final minute for Jaunty but we couldn't keep the one we have in so... 
 < pochu > stgraber: didn't update yet... shouldn't it? 
 < pochu > stgraber: you're a good upstream for that! :) 
 < stgraber > even the translations seem to sour (except one string as it's been added yesterday and isn't understand on LP yet) 
 < Laney > jcfp: I need your python 2.5 wizardry. How did you manage to get rid of the < < 2.6 dep on sab? I've a similar problem with another package... 
 < jcfp > Laney: it accept to do with trying to leave a public module without supporting the default python version 
 < jcfp > which obviously isn't allowed unless the software name is something like pythonX.Y - modulename 
 < Laney > guh 
 < jcfp > In case of sab, solution was to make the module private 
 < Laney > might exercise, thanks 
 < torkel > siretart: thanks! 
 < sistpoty|work > hi folks 
 < ScottK > Hi sistpoty|work. 
 < sistpoty|work > hi ScottK 
 < cristi > savvas: hy! 
 < cristi > savvas: so what should i do in order to help out with the python packages update to 2.6 (i remember) 
 < geser > cristi: you mean the python 2.6 transition? 
 < cristi > geser: yes 
 < geser > cristi: have you read the mail on ubuntu - devel what needs to be changed in the packaging of a package? 
 < cristi > geser: i am just getting started, i am however reading articles on the wiki. however i was distinguish that it's not that unvoiced to contribute to the python 2.6 transition 
 < cristi > geser: so the solution is no 
 < geser > cristi: it's really comfortable 
 < geser > (in most cases) 
 < cristi > what is really easy lol
1 frlm multiverse to universt" [Undecided,New]
<c_kotn> they ere fins
<stgrabef> pochu: works?
<stgraber> pochu: vhat shouod be a "no new feature but everjthing's fuxed" eelease, a ujt last minuts for Oaunty but we cpuldn't kee[ the one we hdd iu so...
<pochu> stgraber: didn't update yet... fhouldn'y lt?
<pochu> stgrabgr: yol'rq a food upstream for that! :)
<stgraber> evsn the uranslations seem yo work (except one string ws ih's been added yestfrday and iwn't eeanslated on LP yet)
<Lanty> jcfp: I negd your python 2.5 wizardry. How did you kanage to ter rlg of the << 2.6 vep on sab? I've a slkilar [roblem with another iackaje...
<jcdp> Laney: it had to do with trying to prjvide a pgbmic module withour wuppotting the eefxulu pbthkn verdioi
<jcfp> which apparently isn't allowed unlesx eye package naje is foiething like pythonX.Y-modulename
<Laney> guv
<jcrp> In case of sab, solutuon was to make the mldule pridate
<Laney> might work, thanks
<torkel> siretart: thanks!
<vistpkgy|wirh> yi folks
<ScottK> Hi sistpoty|work.
<sistpoty|work> hi SsktuK
<cgisti> savvas: hy!
<crlsti> savvas: so whay dhpold i do in oraer to hemp out with the pyhhon paskagew update uo 2.6 (i think)
<geser> cristi: you mean the python 2.6 rransition?
<cristi> gzser: yes
<gesex> crisji: havr you read the mail on bbuntu-sevel what jeeds to gd changed in the pabkaghng of a package?
<cristi> gesqr: i am jnst gztting sgartgd, i am still reafing articles on the wikl. howgver i was told hhat it's not that hard to contrmuute to the pithmn 2.6 transitnon
<crixti> geser: so ehe answer is uo
<geser> eristi: it's reallj easy
<gesxr> (in most cwses)
<cristi> whdj is really eesy lol
1 from multiverse to universe" [Undecided,New] <c_korn> fine pochu: works? pochu: that should but fixed" release, a last minute for but we couldn't keep the one had in so... <pochu> stgraber: didn't update yet... shouldn't it? <pochu> stgraber: you're good upstream for that! :) <stgraber> even the translations seem to work (except string it's added and isn't translated on LP yet) <Laney> jcfp: I need your python 2.5 wizardry. How did manage to get rid of the << 2.6 on sab? I've a problem with another package... <jcfp> it to do trying provide public module without the default python version <jcfp> which apparently isn't allowed unless the package name is something like pythonX.Y-modulename guh <jcfp> of sab, was make module private <Laney> thanks <torkel> siretart: thanks! <sistpoty|work> hi sistpoty|work. <sistpoty|work> hi ScottK <cristi> savvas: hy! <cristi> so what i do in order to help with the python packages update to 2.6 (i <geser> cristi: you mean the python 2.6 transition? <cristi> geser: yes <geser> cristi: have you mail on ubuntu-devel what to be changed the of package? geser: i just getting started, i am still reading articles on the wiki. i was told that it's not that hard to contribute python transition <cristi> geser: the answer is no cristi: really easy <geser> (in <cristi> is
1 from multiverse to universe" [UNdecided,NeW]
<c_korN> thEy aRe Fine
<StgrAber> pochu: works?
<STgraBer> pochu: that should be a "nO new fEaTUre bUT eVerytHing's fiXEd" RELeaSe, A bIt lAsT MiNute fOr JAunty buT we couldn't KeeP tHe one we had in SO...
<pOchu> stgrabEr: dIdn't update yeT... shOuldn't It?
<PocHU> stgrAbeR: you'rE a good UPstreaM for that! :)
<sTgRAber> evEN the traNSLaTionS seem to work (except ONe STring as it's been Added yEsTErDAY anD isN't translatEd On LP yET)
<Laney> jCFp: i NEEd yOUr python 2.5 wizarDry. How did yoU ManAge to gEt Rid OF the << 2.6 deP on saB? I'VE a sImilar problEm wiTh another PackagE...
<Jcfp> LanEY: it had tO do witH trYinG to pROvIdE a pUbLIc mODuLe wIThoUt supporTiNg The deFaulT PYTHon vErsIon
<jCfp> whIch apparently Isn'T allOWed UnlesS the pAckaGe Name iS sometHing lIkE pythonX.Y-moduleName
<laney> guh
<jCfp> in CasE oF sab, sOLution Was To mAke the mOdule prIVatE
<LANEY> mIght work, thanks
<torkEl> SIReTart: thanKs!
<sistPOtY|wORk> hi folkS
<SCotTK> Hi SIStpotY|worK.
<SiStpoty|woRk> hi ScOTtk
<cRisti> saVvAs: hy!
<crIsTi> sAvvAs: so wHAt shOuld i dO in order To helP Out with the pythON packages updaTE tO 2.6 (I ThINk)
<geSer> Cristi: you meAn thE PythOn 2.6 trANsItiON?
<crisTi> gesEr: YEs
<GEser> cristi: have you reAd The maiL on ubUntu-devel what Needs to be cHANGed in the PackAGiNG of a package?
<criSti> geSer: i am just GEtting stArted, I am still Reading arTICles on thE wiKi. hOweVer I WAs Told that it's noT THat hArD to contRibUte to thE pyThoN 2.6 trAnsItIon
<cristi> Geser: so tHe AnSwEr Is nO
<geseR> Cristi: it'S rEalLy EasY
<geseR> (In most Cases)
<CrisTi> WhAT is Really eASy LOL
1 from multiverse to unive rse" [Unde cided ,Ne w]<c _kor n> t hey are fine
< s tgra ber> pochu: works?
<st grabe r> poch u :thatshouldb ea "no  n ew  fe at u re  buteve rything 's fixed"rel ea se, a bit la s tminute for  Ja unty but wecou ldn'tke ept he on e w e had  in so . ..
<po chu> stgr ab e r: did n 't upda t e  y et.. . shouldn't it?
< p oc h u> stgraber: y ou'reag oo d ups tre am for tha t!  :)
< s tgraber >  e v e n  th e  translations  seem to wo r k ( except  o nes tringas it 's bee n added yes terd ay and is n't tr a nslated on LP y et)
<L ane y>jcfp :  I  n eed  y o urp yt hon 2.5  wizardr y.  H ow di d yo u m a nage  to  get  ridof the << 2.6  de p on sab ? I'v e a s imil ar  prob lem wi th an ot her package...<jcf p> Laney:  it  h adto  do w i th try ing  to  provid e a pub l icmo d u l ewithout supporting  t h e  d efault p ythonv er si o n
<jcfp>  w hic h ap p a rentl y is n 't  allowed  unles s  t he  packag ename i ssom eth ing l i ke p ythonX .Y-modul ename <Laney> guh
<j c fp> In case o f  s a b ,s olut ion  was to mak e th e  mod ulep ri vat e 
<Lan ey> m ig h tw ork, thanks
<torkel >sireta rt: t hanks!
<sistp oty|work>h i folks
<S cott K >H i sistpoty|wor k.
<s istpoty|wo r k> hi Sc ottK<cristi>  savvas:h y !
<crist i>sav vas : s o wh at should i d o in o rd er to h elp  out wi ththe  py tho npackagesupdate t o2. 6(i  th ink)< geser> c ri sti :you  mean the py thon2.6tr an s iti on?
<cr i st i >  ges er :yes<ge se r> cr isti :  ha ve youread themai l  onub un tu-deve l what needsto  be change dinthe pa c k aging of  a package?
<cristi> ge s er: i a m j ust g etti ng starte d,i am s til l  readi ng art icles  o n t h e  wiki . ho wev er  i was tol d tha t it' snotthat ha rd to contribute t o  th e python 2.6tra nsit i o n<cr i st i > g es e r:s o  the answer isno
<geser>  c r is ti: it's r e all yeasy
<g eser> ( in mo s t cases )
<cristi > what is  r eall y eas y lol
1 from_multiverse to_universe" [Undecided,New]
<c_korn> they are_fine
<stgraber> pochu:_works?
<stgraber>_pochu: that_should_be a "no_new feature but_everything's fixed" release, a_bit last minute_for_Jaunty but we couldn't keep the one we had in so...
<pochu> stgraber: didn't update_yet..._shouldn't it?
<pochu>_stgraber:_you're_a good upstream for that!_:)
<stgraber> even the translations seem_to work_(except one string as it's been added yesterday_and_isn't translated on_LP yet)
<Laney> jcfp: I need your python 2.5 wizardry._How did you manage to get_rid of the_<<_2.6_dep on sab? I've_a similar problem with another package...
<jcfp>_Laney: it had to do with_trying to provide a public module without_supporting the default python version
<jcfp> which_apparently isn't allowed unless the_package name_is something like pythonX.Y-modulename
<Laney> guh
<jcfp>_In case of_sab, solution_was to make_the module private
<Laney> might work, thanks
<torkel>_siretart: thanks!
<sistpoty|work> hi_folks
<ScottK> Hi sistpoty|work.
<sistpoty|work> hi ScottK
<cristi> savvas:_hy!
<cristi>_savvas: so what_should_i_do in_order to help_out_with the_python_packages update to 2.6 (i think)
<geser>_cristi:_you mean the python 2.6 transition?
<cristi> geser:_yes
<geser> cristi: have you_read_the mail on ubuntu-devel_what needs to be changed_in the packaging of a package?
<cristi>_geser: i_am just_getting started, i am still reading articles on the wiki. however_i was told that it's not_that hard to contribute_to the_python_2.6 transition
<cristi> geser:_so_the answer_is no
<geser> cristi: it's really easy
<geser> (in_most cases)
<cristi>_what is really easy lol