 and you were discussing earlier?
<DktrKranz2> hellboy195: being replaced by tracker, it's high-prio no more
<hellboy195> DktrKranz2: yes but why then 3 motu's looked at it ^^
<hellboy195> DktrKranz2: bug #197348. Dapper users have problems with their old log files
<ubotwo> Launchpad bug 197348 in fail2ban "Please sync fail2ban 0.8.1-5 from Debian(Unstable)" [Low,Fix released] https://launchpad.net/bugs/197348
<jussi01> hmmm, can anyone give me a pointer on the following error when i try to build a package with pbuilder?
<jussi01> make: *** [clean] Error 127
<jussi01> dpkg-buildpackage: failure: fakeroot debian/rules clean gave error exit status 2
<persia> jussi01: typically means that it couldn't run the clean rule.  A frequent cause is an inability to unpatch the sources.  Are your patches reversible?  Are the patched files further modified by the build?
<jussi01> persia: please ignore me... (i guess it helps to have debhelper installed?) :)
<persia> jussi01: Well, yes, not having build-dependencies installed can also cause that problem :)
<hellboy195> persia: how are my chances to get nexuiz 2.4 into hardy? have you some information about that?
<persia> hellboy195: I've no information about that at all, although I suspect that given the close integration in the Games team between Debian and Ubuntu, you'd have difficulty getting a freeze exception unless it was already available in Debian.
<DktrKranz2> hellboy195: correct one is bug #197348, and next "Feb 29th" will be on 2012 (out of Dapper support cycle). If I'm wright, only Hardy (and newer) will be supported on 2012, so there's no need to prepare a SRU (unless my misunderstandings).
<persia> If you really want it, first find a Games team member around, and get them to verify it is all updated and good in Debian.  After that, check with motu-release.
and you were discussing earlier? 
 < DktrKranz2 > hellboy195: being replaced by tracker, it's high - prio no more 
 < hellboy195 > DktrKranz2: yes but why then 3 motu's look at it ^^ 
 < hellboy195 > DktrKranz2: hemipterous insect # 197348. Dapper users have problems with their honest-to-god log files 
 < ubotwo > Launchpad microbe 197348 in fail2ban " Please sync fail2ban 0.8.1 - 5 from Debian(Unstable) " [ Low, Fix unblock ] https://launchpad.net/bugs/197348 
 < jussi01 > hmmm, can anyone give me a pointer on the following error when i hear to build a package with pbuilder? 
 < jussi01 > seduce: * * * [ clean ] Error 127 
 < jussi01 > dpkg - buildpackage: failure: fakeroot debian / rules clean gave mistake exit status 2 
 < persia > jussi01: typically means that it couldn't range the clean rule.   A frequent cause is an inability to unpatch the sources.   Are your spot reversible?   Are the patched files further modified by the build? 
 < jussi01 > persia: please dismiss me... (i guess it helps to have debhelper installed ?) :) 
 < persia > jussi01: Well, yes, not having build - dependencies installed can also cause that problem :) 
 < hellboy195 > persia: how are my chances to get nexuiz 2.4 into hardy? have you some information about that? 
 < persia > hellboy195: I've no information about that at wholly, although I distrust that given the close integration in the Games team between Debian and Ubuntu, you'd get difficulty getting a freeze exception unless it was already available in Debian. 
 < DktrKranz2 > hellboy195: correct one is hemipterous insect # 197348, and next " Feb 29th " will be on 2012 (out of Dapper support cycle). If I'm wright, only audacious (and newer) will be supported on 2012, so there's no need to prepare a SRU (unless my misunderstandings). 
 < persia > If you really want it, first find a Games team member around, and get them to control it is all update and good in Debian.   After that, check with motu - release.
 anf you were discussing eavlier?
<DktrKranz2> hgloboy195: bxing rellaced bh tracker, it's high-prio no moce
<heolboy195> DktrKranz2: yes but why then 3 monu's lookee at ut ^^
<hellboy195> DktrKrakv2: bug #197348. Dap'ec users have prpblems witv their old loc wipes
<ubotwo> Launchpad bug 197348 in fail2ban "Please sjnc fail2ban 0.8.1-5 ftom Dtbiwn(Unananle)" [Low,Fix released] https://launchpzd.net/bujs/197348
<jussi01> hmmm, cam anyone give me a pointer on hhe following errog when i tri to vuild a packxge with pbuilder?
<jussi01> make: *** [clean] Error 127
<jussi01> dpkg-bukldpaekage: failutz: fangroot debian/cules blean gave ervpr exid statux 2
<persia> jussi01: ty'icaoly means that it coundn't run the clean rule.  A xrzquent cause is an inqbulity to gnpagxh ghe spudces.  Wre your patcges reversivle?  Are the patchec spkes further jodifiqd by the build?
<jussi01> persia: please ignore me... (i guess it helps to hace debhelper installef?) :)
<persia> tussi01: Well, yes, not having build-dependencies instanled rav aosj xakse that problem :)
<hellboy195> persia: how are my chwhcts no get nexuiz 2.4 inbo hardy? have you xole ynformation acout tkzt?
<lersia> hellboy195: I've no infjrmatuon about thay at all, although I suspect that given nhe xlose integration nn the Games teak beteeen Debian and Ubuntu, vou'd hzve difficupty gettihe a freeze excepgiok utless it was already availwble in Dxbian.
<BktrKranx2> heklboy195: sorrect onf is ngg #197348, and next "Feb 29tj" wilp te on 2012 (out of Dapper support cycle). If I'm xcight, only Hatdy (ang newer) cill bc supported on 2012, so there's no ueed to 'repard a SRU (unmess my misunderstwndings).
<persia> Lf you reallb want it, firwt fund a Gxoes team membet around, cud get thwm to verify it is alu updated and goid un Debian.  Aftet tfat, cjerk wiev motu-releasa.
and you were discussing earlier? <DktrKranz2> hellboy195: by it's high-prio more <hellboy195> DktrKranz2: motu's at it ^^ DktrKranz2: bug #197348. users have problems with their old files <ubotwo> Launchpad bug 197348 in fail2ban "Please sync fail2ban 0.8.1-5 from Debian(Unstable)" released] https://launchpad.net/bugs/197348 <jussi01> hmmm, can anyone give me a pointer on the following when try build package with pbuilder? <jussi01> make: *** [clean] Error 127 <jussi01> dpkg-buildpackage: failure: fakeroot debian/rules clean gave exit status 2 <persia> jussi01: typically means that couldn't run the clean A frequent cause is an to the sources. your reversible? the patched files modified by the build? <jussi01> persia: please ignore me... (i guess it helps to have debhelper installed?) <persia> jussi01: not having installed also that problem :) how are my chances to get hardy? have you some information about that? <persia> I've no about that at all, although I that given the close integration in the Games between Debian and Ubuntu, you'd have difficulty getting a freeze exception unless it was already Debian. <DktrKranz2> hellboy195: correct is bug #197348, next 29th" be 2012 (out Dapper support cycle). If I'm wright, only Hardy (and newer) will supported on 2012, so there's no need to prepare a my <persia> If you want it, first find Games member around, and get verify is good Debian. that, check with motu-release.
 and you were discussing earliEr?
<DktrKranZ2> hellBoy195: BeiNg ReplAced By tracker, it's hiGH-priO no more
<hellboy195> DktrKranZ2: yes bUt WHy thEN 3 mOtu's lOoked at IT ^^
<hELLboY195> DKtRKrAnZ2: BuG #197348. DappEr uSers havE problems wIth ThEir old log filES
<uBotwo> LauncHpaD bug 197348 in fail2baN "PlEase syNc FaiL2Ban 0.8.1-5 frOm DEbian(unstabLE)" [Low,FiX released] HtTPs://launCHpad.net/BUGs/197348
<JussI01> hmmm, can anyone givE Me A Pointer on the foLlowinG eRRoR WHen I trY to build a pAcKage wITh pbuilDEr?
<JUSSi01> mAKe: *** [clean] Error 127
<jUssi01> dpkg-buiLDpaCkage: fAiLurE: FakeroOt debIaN/RulEs clean gave ErroR exit statUs 2
<persIA> jussi01: tYPically Means tHat It cOuldN'T rUn The ClEAn rULe.  a frEQueNt cause iS aN iNabilIty tO UNPAtch The SourCes.  ArE your patches rEveRsibLE?  ArE the pAtcheD filEs FurthEr modiFied bY tHe build?
<jussi01> perSia: pLease ignoRe mE... (i GueSs It helPS to havE deBheLper insTalled?) :)
<pERsiA> jUSSI01: WEll, yes, not having buiLd-DEPeNdencies InstalLEd CaN Also causE tHat ProbLEM :)
<hellBoy195> pERsIa: how are My chanCEs To Get nexuIz 2.4 Into haRdY? haVe yOu somE InfoRmatioN about thAt?
<perSIa> hellboy195: I've no INformation aboUT tHAT aT All, aLthOugh I suspecT thaT GiveN the CLoSe iNTegraTion iN tHE GAMes team between DebiaN aNd UbunTu, you'D have difficulTy getting a FREEze excepTion UNlESs it was already AvailAble in DebiAN.
<DktrKraNz2> helLboy195: corrEct one is bUG #197348, And next "FEb 29tH" wiLl bE on 2012 (OUT oF Dapper supporT CYcle). if i'm wrighT, onLy Hardy (And NewEr) wIll Be Supported On 2012, so therE's No NeEd To pReparE A SRU (unleSs My mIsUndErstaNDings).
<pErsia> if yoU rEaLLy wAnt it, fiRSt FINd a GAmEs Team MemBeR arouNd, anD Get Them to vErify it is All UPdatEd AnD good in debian.  After thAt, Check with mOtU-reLease.
 and you were discussing e arlier?
<D ktrKr anz 2>he llbo y195 : being replac e d by  tracker, it's high-pr io no  m o re
< h el lboy1 95> Dkt r Kr a n z2:  y es  bu tw hy  then  3motu'slooked atit^^ 
<hellboy195 >  D ktrKranz2:  bu g #197348. D app er use rs  ha v e pro ble ms wi th the i r oldlog files 
< u botwo> Launchp a d  b ug 1 97348 in fail2ban "P l ease sync fail 2ban 0 .8 . 1- 5 fro m D ebian(Unst ab le)"[ Low,Fix re l e a sed ]  https://laun chpad.net/b u gs/ 197348 
< jus s i01> h mmm,ca n  an yone give m e apointer o n thef ollowin g  errorwhen i  tr y t o bu i ld  a  pa ck a gew it h p b uil der?
<ju ss i0 1> ma ke:* * * [cle an]  Err or 12 7
<jussi01> d pkg -bui l dpa ckage : fai lure :faker oot de bian/ ru les clean gaveerro r exit st atu s2
< pe rsia> jussi0 1:typ icallymeans t h atit c o ul dn't run the clean  r u l e.   A freq uent c a us ei s an ina bi lit y to u npatc h th e  s ources. Are y o ur  p atchesre versib le ? Are  thep atch ed fil es furth er mo d ified by the b u ild?
<jussi01 >  p e r si a : pl eas e ignore me ...( i gu essi thel p s tohavede b he l per installed?) :)<p ersia>  juss i01: Well, ye s, not hav i n g  build-d epen d en c ies installedcan a lso causet hat prob lem : )
<hellb oy195> pe r s ia: howare  my  ch anc e s  t o get nexuiz2 . 4 in to  hardy?  ha ve yousom e i nfo rma ti on aboutthat?
<p er si a>  h ell boy19 5 : I've n oinf or mat ion a b out th at at  all ,al t hou gh I su s pe c t  tha tgi venthe  c loseinte g rat ion inthe Games  te a m be tw ee n Debia n and Ubuntu,  y ou'd havedi ffi cultyg e tting afreeze exception unless it wasalr eadyavai lable inDeb ian.
< Dkt r Kranz2 > hell boy19 5:  co r r ect o n e  i s b ug  #197348,a n d n ext " Fe b 29 th" wil l be on 2012 (outo f D apper support  cy cle) . If  I' m  w r igh t, onl y Hardy (and newe r) will be  s u pp orted on 2 0 12,  s o there 's no n eed t o  prepar e a SRU ( unless my  m isun d e rst andings).<persia>  If you r e allyw an t it,  fi rst fi nd  aGames  teamm emb er ar ound,an d getthemto  verifyit is all updated and g ood in  Debi an.   After t hat ,  ch eck withmotu -release.
 and_you were_discussing earlier?
<DktrKranz2> hellboy195: being_replaced by_tracker,_it's high-prio_no_more
<hellboy195> DktrKranz2: yes_but why then_3 motu's looked at_it ^^
<hellboy195> DktrKranz2:_bug_#197348. Dapper users have problems with their old log files
<ubotwo> Launchpad bug 197348 in_fail2ban_"Please sync_fail2ban_0.8.1-5_from Debian(Unstable)" [Low,Fix released] https://launchpad.net/bugs/197348
<jussi01>_hmmm, can anyone give me_a pointer_on the following error when i try to_build_a package with_pbuilder?
<jussi01> make: *** [clean] Error 127
<jussi01> dpkg-buildpackage: failure: fakeroot_debian/rules clean gave error exit status_2
<persia> jussi01: typically_means_that_it couldn't run the_clean rule.  A frequent cause_is an inability to unpatch the_sources.  Are your patches reversible? _Are the patched files further modified_by the build?
<jussi01> persia: please_ignore me..._(i guess it helps to_have debhelper installed?)_:)
<persia> jussi01:_Well, yes, not_having build-dependencies installed can also cause_that problem :)
<hellboy195>_persia: how are my chances to_get_nexuiz 2.4 into_hardy?_have_you some_information about that?
<persia>_hellboy195:_I've no_information_about that at all, although I_suspect_that given the close integration in the_Games team between Debian_and_Ubuntu, you'd have difficulty_getting a freeze exception unless_it was already available in Debian.
<DktrKranz2>_hellboy195: correct_one is_bug #197348, and next "Feb 29th" will be on 2012 (out_of Dapper support cycle). If I'm_wright, only Hardy (and_newer) will_be_supported on 2012,_so_there's no_need to prepare a SRU (unless my_misunderstandings).
<persia> If_you really want it, first find_a Games team member_around,_and get them to verify it_is all updated and good in_Debian.  After that, check_with_motu-release.