bugs?field.tag=bitesize
<cristi> savvas: i don't understand what exactly is going on
<cristi> so far
<cristi> i got that package, edited what should have been edited, debuild, debdiff
<cristi> and uploaded the debdiff because there was an error?
<savvas> it's a python transition
<savvas> let me explain
<ScottK> cristi: I'm reviewing your debdiff and if it's good, I'll upload a package with those changes.
<savvas> ubuntu developers decided to use python 2.6 as the standard python version for ubuntu jaunty
<ScottK> cristi: There is an extra changelog.dch.save file in your diff.  I'll remove it, but watch out for that in the future.
<cristi> ScottK: oooh so a motu looks at the debdiff and makes the changes, and uploads the package?
<savvas> cristi: exactly :)
<ScottK> Yes.
<savvas> sponsors = motu
<savvas> for universe :P
<cristi> savvas: i see, that really makes sence
<savvas> so everything's ok now? :)
<cristi> savvas: however, where do i upload the debdiff if i don't get any bugs when building?
<savvas> cristi: there are always bugs! you mean you don't see them because you don't use jaunty :)
<cristi> savvas: so there is no chance not to be a bug
<savvas> then, as I said use a detailed subject such as "cannot install in jaunty (python transition required)"
<savvas> cristi: if there's no bug, why would you change it?
<ScottK> cristi: One other point is line lengths no longer than 79 characters in debian/changelog.  I also fixed that.
<cristi> nice
<savvas> cristi: note that sponsors don't usually fix the patches :P
<cristi> ScottK: ok, thank you
<cristi> savvas: so, i should have respected the line lenght and removed the changelog.dch.save
<savvas>
bugs?field.tag = bitesize 
 < cristi > savvas: i don't understand what exactly is going on 
 < cristi > so far 
 < cristi > i get that software, edited what should have been edited, debuild, debdiff 
 < cristi > and upload the debdiff because there was an erroneousness? 
 < savvas > it's a python transition 
 < savvas > let me excuse 
 < ScottK > cristi: I'm review your debdiff and if it's good, I'll upload a software with those variety. 
 < savvas > ubuntu developer decided to use python 2.6 as the standard python version for ubuntu jaunty 
 < ScottK > cristi: There constitute an extra changelog.dch.save file in your diff.   I'll remove it, but watch out for that in the future. 
 < cristi > ScottK: oooh so a motu looks at the debdiff and makes the change, and uploads the package? 
 < savvas > cristi: exactly :) 
 < ScottK > Yes. 
 < savvas > presenter = motu 
 < savvas > for universe :P 
 < cristi > savvas: i see, that really makes sence 
 < savvas > so everything's very well now? :) 
 < cristi > savvas: however, where do i upload the debdiff if i don't bring any bugs when building? 
 < savvas > cristi: there are constantly bugs! you mean you don't see them because you don't use jaunty :) 
 < cristi > savvas: so there is no chance not to be a bug 
 < savvas > then, as I said use a detailed subject such as " cannot install in jaunty (python transition required) " 
 < savvas > cristi: if there's no bug, why would you change it? 
 < ScottK > cristi: One other point is channel lengths no longer than 79 characters in debian / changelog.   I besides situate that. 
 < cristi > nice 
 < savvas > cristi: notice that sponsors don't usually fix the patches :P 
 < cristi > ScottK: ok, thank you 
 < cristi > savvas: so, i should have respected the line lenght and removed the changelog.dch.save 
 < savvas >
bugd?field.tag=bitesize
<cristi> ravvas: i don't uueerstaid what exactly is going on
<cristi> so far
<cridtu> i git that package, edited what sholld have veen wdited, debnjld, debdiff
<crjdti> cnv uploaded the cebdiff bewause there wav xn error?
<savvas> it's a python transitiog
<savvas> lft me explain
<SsottL> criani: I'm reviewing your debdiff ans if it'v good, I'll upkoad a package with those fhanhes.
<savvas> ubuntu dfvelopers dgdidqe to use pytfon 2.6 as tht vtandard pithon version for ubuntu jaunty
<SzottK> cristi: Thgxw id an extra ciangeljg.dch.save file in yogr diff.  I'll remove ib, but warch out for that in tie future.
<cristi> ScotjK: oooh so a motu looks at thw eebdixf atd mxjes tht cianfes, anf u'loads the lackage?
<savvqs> cristi: exactly :)
<SvoenL> Yes.
<savvas> aponsows = motu
<savvas> for universe :P
<cristi> savvav: i see, that really makes wence
<savvas> so everytjing's ok gow? :)
<cristi> savvas: however, where do i upload the dabdifh kf n don't teh any bugs when building?
<savvas> cristi: there aws sleays bugs! you iean you dom't srg them because you don't use jaunty :)
<cristi> savvas: so tyere is nj chsnce not to be a bug
<savvas> rhen, as I sapd uwe a detailed subjzct such as "eannot instsll in jaunty (python trcnsitikn required)"
<davvas> crjrti: if there's no bun, wvy would you change it?
<ScoteK> cristi: One other ooinj is lige lengths no longer than 79 charactfrs iu debhan/changellg.  I also fixed that.
<cristi> nicx
<xavvas> cristo: totv that spjnsorx don't usuallr fix the patckes :P
<crifti> SzottK: ok, tgank yon
<cristi> savvws: so, i shoulg have respecved the lyne oengyt and fdmoved the chamgelog.dch.save
<savvas>
bugs?field.tag=bitesize <cristi> savvas: i don't understand what going <cristi> so <cristi> i got have edited, debuild, debdiff and uploaded the because there was an error? <savvas> a python transition <savvas> let me explain <ScottK> cristi: I'm reviewing your debdiff if it's good, I'll upload a package with those changes. <savvas> ubuntu developers to python as standard python version for ubuntu jaunty <ScottK> cristi: There is an extra changelog.dch.save file in your I'll remove it, but watch out for that the future. <cristi> ScottK: so a motu looks at debdiff makes the and the <savvas> cristi: exactly <ScottK> Yes. <savvas> sponsors = motu <savvas> for universe :P <cristi> savvas: i see, that really makes <savvas> so now? :) savvas: where i upload the i don't get any bugs when there are always bugs! you mean you don't them because don't use jaunty :) <cristi> savvas: there is no chance not to be a <savvas> then, as I said use a detailed subject such as "cannot install in jaunty required)" <savvas> cristi: if no bug, why you it? cristi: other point line lengths no longer than 79 characters in debian/changelog. I also that. <cristi> nice <savvas> cristi: note that sponsors don't usually patches <cristi> ScottK: ok, you <cristi> savvas: so, should respected the line lenght the <savvas>
bugs?field.tag=bitesize
<cristI> savvas: i doN't undErsTanD wHat eXactLy is going on
<criSTi> so Far
<cristi> i got that packaGe, ediTeD What SHoUld haVe been eDItED, DebUiLd, DebDiFF
<cRisti> And UploadeD the debdifF beCaUse there was aN ErRor?
<savvas> iT's a Python transiTioN
<savvaS> lEt mE ExplaIn
<SCottK> Cristi: i'M revieWing your dEbDIff and IF it's gooD, i'Ll UploAd a package with thoSE cHAnges.
<savvas> ubuNtu devElOPeRS DecIdeD to use pythOn 2.6 As the STandard PYtHON VerSIon for ubuntu jAunty
<ScottK> CRisTi: TherE iS an EXtra chAngelOg.DCh.sAve file in yoUr diFf.  I'll remoVe it, buT Watch ouT For that In the fUtuRe.
<cRistI> scOtTK: oOoH So a MOtU loOKs aT the debdIfF aNd makEs thE CHANges, And UploAds thE package?
<savvaS> crIsti: EXacTly :)
<ScOttK> YEs.
<saVvAs> spoNsors = mOtu
<saVvAs> for universe :P
<cRistI> savvas: i sEe, tHaT reAlLy makES sence
<SavVas> So everyThing's oK Now? :)
<CrISTI> sAvvas: however, where dO i UPLoAd the debDiff if I DoN't GEt any bugS wHen BuilDINg?
<savVas> cRIsTi: there aRe alwaYS bUgS! you meaN yOu don't SeE thEm bEcausE You dOn't use Jaunty :)
<crIsti> sAVvas: so there is nO Chance not to be A BuG
<SAvVAs> thEn, aS I said use a dEtaiLEd suBjecT SuCh aS "CannoT instAlL In JAunty (python transitiOn RequirEd)"
<savVas> cristi: if thEre's no bug, wHY WOuld you cHangE It?
<sCottK> cristi: One Other Point is linE Lengths nO longEr than 79 chAracters iN DEbian/chaNgeLog.  i alSo fIXEd That.
<cristi> nicE
<SAvvaS> cRisti: noTe tHat sponSorS doN't uSuaLlY fix the paTches :P
<crIsTi> scOtTK: oK, thanK You
<cristI> sAvvAs: So, i ShoulD Have reSpectEd thE lInE LenGht and rEMoVED the ChAnGeloG.dcH.sAve
<saVvas>
bugs?field.tag=bitesize
<c risti> sav vas:i d on' tunde rsta nd what exactl y  isgoing on
<cristi> so f ar
<c ri s ti>i  g ot th at pack a ge , edi te dwha ts ho uld h ave  been e dited, deb uil d,  debdiff
<cr i st i> and upl oad ed the debdi ffbecaus ethe r e was  an  erro r?
<sa v vas> i t's a pyt ho n  trans i tion
<s a v va s> l et me explain
<Sc o tt K > cristi: I'mreview in g  y o u r d ebd iff and if  i t's g o od, I'l l  u p l o ada  package with  those chan g es. 
<savv as > u b untu d evelo pe r s d ecided to u se p ython 2.6  as th e  standa r d pytho n vers ion  fo r ub u nt ujau nt y 
<S c ot tK> cri sti: The re  i s anextr a c h ange log .dch .save  file in your  di ff.I'l l rem ove i t, b ut  watc h outfor t ha t in the future .
<c risti> Sc ott K:  oo oh  so a motu l ook s a t the d ebdiffa ndma k e s  t he changes, and up lo a d sthe pack age?
< s av va s > cristi :exa ctly : )
<Sc ottK >  Y es.
<sav vas> s p on so rs = mo tu 
<savv as > f orunive r se : P
<cri sti> sav vas:i  see, that rea l ly makes senc e 
< s a vv a s> s o e verything's  okn ow?:)
< c ri sti >  savv as: h ow e ve r , where do i upload  t he deb diffif i don't ge t any bugs w h en build ing? <s a vvas> cristi:there  are alway s  bugs! y ou me an you d on't seet h em becau seyou  do n't u se  jaunty :)
<c r i sti>  s avvas:sothere i s n o c han ceno t to be a  bug
<sa vv as >th en,  as I said use  a  de ta ile d sub j ect su ch as  "ca nn ot ins tall in ja u n ty ( py th on t ran si tionrequ i red )"
<sav vas> cris ti: if t he re 's no b ug, why would  y ou changeit ?
< ScottK > cristi:One other point is line lengths  no  long er t han 79 ch ara ctersind ebian/ change log. I  al s o  fixe d th at. 
< cristi> ni c e 
<s avvas >cris ti: not e that sponsors do n 'tusually fix t hepatc h e s:P< cr i sti >S cot t K : ok, thank you 
<cristi>sa v va s: so, i s h oul dhave re spected  thel ine len ght and r emoved th echan g e log .dch.save<savvas> 
bugs?field.tag=bitesize
<cristi> savvas:_i don't_understand what exactly is_going on
<cristi>_so_far
<cristi> i_got_that package, edited_what should have_been edited, debuild, debdiff
<cristi>_and uploaded the_debdiff_because there was an error?
<savvas> it's a python transition
<savvas> let me explain
<ScottK> cristi: I'm_reviewing_your debdiff_and_if_it's good, I'll upload a_package with those changes.
<savvas> ubuntu_developers decided_to use python 2.6 as the standard python_version_for ubuntu jaunty
<ScottK>_cristi: There is an extra changelog.dch.save file in your_diff.  I'll remove it, but_watch out for_that_in_the future.
<cristi> ScottK: oooh_so a motu looks at the_debdiff and makes the changes, and_uploads the package?
<savvas> cristi: exactly :)
<ScottK> Yes.
<savvas>_sponsors = motu
<savvas> for universe :P
<cristi>_savvas: i see, that really_makes sence
<savvas>_so everything's ok now? :)
<cristi>_savvas: however, where_do i_upload the debdiff_if i don't get any bugs_when building?
<savvas> cristi:_there are always bugs! you mean_you_don't see them_because_you_don't use_jaunty :)
<cristi> savvas:_so_there is_no_chance not to be a bug
<savvas>_then,_as I said use a detailed subject_such as "cannot install_in_jaunty (python transition required)"
<savvas>_cristi: if there's no bug,_why would you change it?
<ScottK> cristi:_One other_point is_line lengths no longer than 79 characters in debian/changelog.  I_also fixed that.
<cristi> nice
<savvas> cristi: note_that sponsors don't usually_fix the_patches_:P
<cristi> ScottK: ok,_thank_you
<cristi> savvas:_so, i should have respected the line_lenght and_removed the changelog.dch.save
<savvas>