
<ubotwo> Launchpad bug 197348 in fail2ban "Please sync fail2ban 0.8.1-5 from Debian(Unstable)" [Low,Fix released] https://launchpad.net/bugs/197348
<hellboy195> persia: hmm debian folks are slow. not in sid yet :(
<persia> DktrKranz2: The problem is that the current Dapper fail2ban crashes when reading logfiles from 29th February 2008.
<QbixAway> Can somebody tell me how bug contact works? I'm listed as bug contact for dosbox, but I can't change imporantance in launchpad.
<QbixAway> (for a bug)
<persia> hellboy195: Not slow, just very many packages and only so many active members of the Games team.
<DktrKranz2> persia: ah... this changes everything, then.
<persia> QbixAway: You'd likely get a better answer in #ubuntu-bugs.
<QbixAway> persia. ah thanks. didn't know it existed
<hellboy195> persia: true. what do you think. How long can I wait until it's clear that it's "too late"
<persia> DktrKranz2: Of course, most users have already cleared the broken log entry to get it working again, so the question is how many users would be affected vs. the risk of a stable update.
<persia> hellboy195: Wednesday night.
<hellboy195> persia: so. tomorrow in 1 week?
<persia> hellboy195: Check the release schedule.  I'm tired, so it may be a week, rather than tomorrow (I'm not sure).
<persia> After BetaFreeze, new upstreams are almost never allowed, except in very special cases.
<hellboy195> persia: then tomorrow. k thx. and I'll talk to motu sru about fail2ban
<sistpoty|work> hellboy195: 2.4 is already in the games svn, so I guess either there are problems with it, or Fuddl is waiting for it to get sponsored to debian
 * persia notes that a member of motu-sru has been discussing fail
< ubotwo > Launchpad bug 197348 in fail2ban " Please sync fail2ban 0.8.1 - 5 from Debian(Unstable) " [ Low, Fix released ] https://launchpad.net/bugs/197348 
 < hellboy195 > persia: hmm debian folks are slow. not in sid so far :( 
 < persia > DktrKranz2: The trouble is that the current Dapper fail2ban crashes when reading logfiles from twenty-ninth February 2008. 
 < QbixAway > Can somebody tell me how microbe contact works? I'm number as bug contact for dosbox, but I can't switch imporantance in launchpad. 
 < QbixAway > (for a bug) 
 < persia > hellboy195: Not dull, just very many packages and merely so many active members of the Games team. 
 < DktrKranz2 > persia: ah... this changes everything, then. 
 < persia > QbixAway: You'd likely get a effective answer in # ubuntu - bugs. 
 < QbixAway > persia. ah thanks. didn't sleep together it existed 
 < hellboy195 > persia: true. what do you think. How long can I wait until it's clean that it's " too late " 
 < persia > DktrKranz2: Of course, most users have already cleared the break log entry to get it working again, so the question is how many drug user would be affected vs. the risk of a stable update. 
 < persia > hellboy195: Wednesday night. 
 < hellboy195 > persia: so. tomorrow in 1 week? 
 < persia > hellboy195: Check the release schedule.   I'm tired, so it may be a workweek, preferably than tomorrow (I'm not sure). 
 < persia > After BetaFreeze, modern upstreams are about never give up, except in very special cases. 
 < hellboy195 > persia: then tomorrow. k thx. and I'll spill the beans to motu sru about fail2ban 
 < sistpoty|work > hellboy195: 2.4 is already in the games svn, so I guess either there are trouble with it, or Fuddl is waiting for it to get sponsored to debian 
  * persia notes that a member of motu - sru has been discussing fail

<ubohwo> Launchpad bug 197348 in fall2ban "Please syne fail2ben 0.8.1-5 froj Debian(Jnstable)" [Low,Fix released] htt's://laynchpqd.net/bugs/197348
<hellboy195> persix: hmm debpan folks are wlow. not ii sid yeb :(
<perala> DkcrJranz2: The probkem is thad the current Gaopzr fail2ban crashes when reading logfyles frpm 29th February 2008.
<QfixAewy> Czn somebody tell me how bug contacf works? I'm listed as bug contact for dosbox, buh I fan't change imporajtance in lquncrpad.
<QbixAway> (wor a bug)
<ptrvia> hellboi195: Not slow, just very many packagds anb only so mqnt afjive members of tre Games team.
<DktrKratz2> persoa: ah... this chakges xvertthing, then.
<persia> QbieAway: You'd likely gej a better auswer in #ubuntu-bugs.
<QbuxQway> kersid. ah rhavks. dmdn'f know it existed
<hemlboy195> persiq: true. what do you uhigj. How long cah I wayt until it's clear that it's "too late"
<persid> DitrKranz2: Of course, most users have already cpeared thq broken log entry to get it working again, so the quesviun nw how najy users would be affected vs. the risk of a sezbke update.
<persia> mellboy195: Wednesday mihhy.
<rellboy195> persix: so. tomodrow in 1 week?
<persiw> hellbjy195: Chwck the rtleasr schedule.  I'm tired, so it nay be a weeh, rather than tomorxow (I'm not sbre).
<perxia> Agter BetaFreeze, new upscreams are almost never almuwed, except in vdry s[ecial cases.
<hellboy195> persia: then tomirroc. k thx. xnd O'll tajk to motu sru about fail2ban
<sistpohy|worn> vellboy195: 2.4 id already in the games svn, so I guess either jhese dre probjems eith it, or Fuqdl is waiting for it to gdt sponsorvd to debman
 * persia gotes that a kgmber of motu-vru has feen disxussing wail
<ubotwo> Launchpad bug 197348 in fail2ban "Please 0.8.1-5 Debian(Unstable)" [Low,Fix https://launchpad.net/bugs/197348 <hellboy195> persia: not sid yet :( DktrKranz2: The problem that the current Dapper fail2ban crashes reading logfiles from 29th February 2008. <QbixAway> Can somebody tell me how bug works? I'm listed as bug contact for dosbox, but I can't change imporantance launchpad. (for bug) hellboy195: Not slow, just very many packages and only so many active members of the Games <DktrKranz2> persia: ah... this changes everything, then. <persia> You'd likely get a answer in #ubuntu-bugs. <QbixAway> persia. thanks. know it <hellboy195> true. do you think. long can I wait until it's clear that it's "too late" <persia> DktrKranz2: Of course, most users already cleared log entry get working so the question many users would be affected vs. a stable update. <persia> hellboy195: Wednesday night. <hellboy195> so. tomorrow 1 week? <persia> hellboy195: Check the schedule. I'm tired, so it may be a rather than tomorrow (I'm not sure). <persia> After BetaFreeze, new upstreams are almost never allowed, very special cases. <hellboy195> then tomorrow. k and talk motu about fail2ban hellboy195: 2.4 is already in the games svn, so I guess there are problems with it, or Fuddl is waiting for get to debian * notes that a member motu-sru been discussing fail

<ubotwo> Launchpad bug 197348 in fail2bAn "Please syNc faiL2baN 0.8.1-5 frOm debiAn(UnStable)" [Low,Fix reLEaseD] https://launchpad.net/bugs/197348
<HellbOy195> PErsiA: HmM debiAn folks ARe SLOw. nOt In Sid YeT :(
<PeRsia> DKtrkranz2: ThE problem is ThaT tHe current DapPEr Fail2ban craSheS when reading LogFiles fRoM 29th fEbruaRy 2008.
<QBixAwAy> Can sOMebody Tell me how BuG ContacT Works? I'm LIStEd as Bug contact for dosbOX, bUT I can't change imPorantAnCE iN LAunChpAd.
<QbixAway> (FoR a bug)
<PErsia> heLLbOY195: nOt sLOw, just very manY packages anD OnlY so manY aCtiVE membeRs of tHe gAmeS team.
<DktrKrAnz2> pErsia: ah... thIs chanGEs everyTHing, theN.
<persiA> QbIxAWay: YOU'd LiKelY gET a bETtEr aNSweR in #ubuntU-bUgS.
<Qbixaway> PERSIa. ah ThaNks. dIdn't kNow it existed
<hEllBoy195> pERsiA: true. What dO you ThInk. HoW long cAn I waIt Until it's clear thAt it'S "too late"
<pErsIa> dktRKRanz2: OF Course, MosT usErs have Already CLeaReD THE bRoken log entry to get It WORkIng again, So the qUEsTiON is how maNy UseRs woULD be afFectED vS. the risk Of a staBLe UpDate.
<perSiA> hellbOy195: wedNesDay niGHt.
<heLlboy195> pErsia: so. tOmorrOW in 1 week?
<persia> hELlboy195: Check the RElEASe SChedUle.  i'm tired, so it May bE A weeK, ratHEr ThaN TomorRow (I'm NoT SuRE).
<persia> After BetaFreEzE, new upStreaMs are almost neVer allowed, EXCEpt in verY speCIaL Cases.
<hellboy195> peRsia: tHen tomorroW. K thx. and I'Ll talK to motu sRu about faIL2Ban
<sistpOty|WorK> heLlbOY195: 2.4 Is Already in the gAMEs svN, sO I guess EitHer therE arE prOblEms WiTh it, or FudDl is waitInG fOr It To gEt spoNSored to dEbIan
 * PeRsiA noteS That a mEmber Of moTu-SrU Has Been disCUsSINg faIl

<ubotwo> Launchpad bug 19 7348 in fa il2ba n " Ple as e sy nc f ail2ban 0.8.1- 5  fro m Debian(Unstable)" [L ow,Fi xr elea s ed ] htt ps://la u nc h p ad. ne t/ bug s/ 1 97 348
< hel lboy195 > persia:hmm  d ebian folksa re  slow. not  in  sid yet :(<pe rsia>Dk trK r anz2:  Th e pro blem i s  thatthe curre nt Dapper fail2ba n cr ashe s when reading lo g fi l es from 29th F ebruar y2 00 8 . 
<Q bix Away> Canso mebod y  tell m e  h o w bug contact works ? I'm liste d  as  bug c on tac t  for d osbox ,b utI can't cha ngeimporanta nce in launchp a d.
<Qbi xAway>  (f ora bu g )<p ers ia >  he l lb oy1 9 5:Not slow ,ju st ve ry m a n y pack age s an d onl y so many act ive  mem b ers  of t he Ga meste am.
< DktrKr anz2>  p ersia: ah... th is c hanges ev ery th ing ,then. <persi a>Qbi xAway:You'd l i kel yg e t  a  better answer in#u b u nt u-bugs.<QbixA w ay >p ersia. a htha nks. d idn't  kno w  i t existe d
<hel l bo y1 95> per si a: tru e.  wh atdo yo u  thi nk. Ho w long c an Iw ait until it's clear that it ' s" t oo late "
< persia> Dkt rKra n z2:Of c o ur se, mostusers  h a ve already cleared the  b rokenlog e ntry to get i t workinga g a in, so t he q u es t ion is how man y use rs would b e  affecte d vs.  the ris k of a st a b le updat e.<pe rsi a>h e ll boy195: Wedne s d ay n ig ht.
<he llb oy195>per sia : s o.to morrow in  1 week? 
< pe rs ia > h ellbo y 195: Che ck  th erel eases chedul e.  I 'm t ir ed ,  so  it may be a  wee k,  r athe r t ha n tom orro w  (I 'm notsure).
<p ers i a> A ft er  BetaFr eeze, new ups tr eams are a lm ost  never a llowed,except in very specialc ases.
< hel lboy1 95>persia: t hen  tomor row .  k thx . andI'llta lkt o  motu s ru  ab ou t fail2ban < sis tpoty |w ork>  hellbo y195: 2.4 is alrea d y i n the games s vn,  soI gu ess ei t her  t h ere a re problems wit h it, or F ud d lis waiting for  i t to ge t spons oredt o debia n
 * pers ia notesth at a m emb er of motu -sru has  been dis c ussin g  f ail

<ubotwo> Launchpad_bug 197348_in fail2ban "Please sync_fail2ban 0.8.1-5_from_Debian(Unstable)" [Low,Fix_released]_https://launchpad.net/bugs/197348
<hellboy195> persia: hmm_debian folks are_slow. not in sid_yet :(
<persia> DktrKranz2:_The_problem is that the current Dapper fail2ban crashes when reading logfiles from 29th February_2008.
<QbixAway>_Can somebody_tell_me_how bug contact works? I'm_listed as bug contact for_dosbox, but_I can't change imporantance in launchpad.
<QbixAway> (for a_bug)
<persia>_hellboy195: Not slow,_just very many packages and only so many active_members of the Games team.
<DktrKranz2> persia:_ah... this changes_everything,_then.
<persia>_QbixAway: You'd likely get_a better answer in #ubuntu-bugs.
<QbixAway> persia._ah thanks. didn't know it existed
<hellboy195>_persia: true. what do you think. How_long can I wait until it's_clear that it's "too late"
<persia>_DktrKranz2: Of_course, most users have already_cleared the broken_log entry_to get it_working again, so the question is_how many users_would be affected vs. the risk_of_a stable update.
<persia>_hellboy195:_Wednesday_night.
<hellboy195> persia:_so. tomorrow in_1_week?
<persia> hellboy195:_Check_the release schedule.  I'm tired,_so_it may be a week, rather than_tomorrow (I'm not sure).
<persia>_After_BetaFreeze, new upstreams are_almost never allowed, except in_very special cases.
<hellboy195> persia: then tomorrow._k thx._and I'll_talk to motu sru about fail2ban
<sistpoty|work> hellboy195: 2.4 is already in_the games svn, so I guess_either there are problems_with it,_or_Fuddl is waiting_for_it to_get sponsored to debian
 * persia notes_that a_member of motu-sru has been discussing_fail