at least the ones that matter)
<siretart> sistpoty: just fakesync it
<sistpoty> siretart: ok, will do
<crimsun> I love the term "fakesync"
<siretart> crimsun: I hate it, because it should better not be necessary :(
<LaserJock> why is it necessary?
<siretart> syncs havn't been processed since the switch to launchpad
<LaserJock> so are we giving up on it then?
<LaserJock> for right now
<crimsun> well if it continues this way, we may not have a choice but to fakesync
<LaserJock> hmm, but then NEW is still stuck
<LaserJock> that sounds like a mess
<slomo> LaserJock: NEW is processed again since ~2 weeks
<siretart> NEW is processed quite regularily
<slomo> siretart: we approved dosemu already at the mailinglist :) no need to approve it again
<LaserJock> not NEW syncs ;-)
<sistpoty> hm... I tried to get an answer on ETA for syncs on #lp tonite, but daf didn't even know syncs weren't processed
<siretart> I uploaded a NEW package yesterday, it was processed through new in a few hours. THATS service :)
<slomo> LaserJock: fakesync the NEW packages :)
<LaserJock> hmmm
<LaserJock> one of the packages is one I maintain in Debian
<LaserJock> I guess if syncs aren't going to be done any time soon I could fakesync it
<LaserJock> it just seems like a bad solution. but I don't know what else we can do
<sistpoty> should we fakesync as -XbuildY or -(X-1)ubuntuY?
<Erlang> netzmeister: you are the guy packaging Code::Blocks right?
<slomo> sistpoty: -Xbuild1 should be better as this would be automatically synced later
<sistpoty> slomo: ok
<sistpoty> slomo: if an ubuntu-specific version is already present in the
at least the ones that matter) 
 < siretart > sistpoty: just fakesync it 
 < sistpoty > siretart: ok, will do 
 < crimsun > I sleep together the condition " fakesync " 
 < siretart > crimsun: I hate it, because it should better not be necessary :( 
 < LaserJock > why is it necessary? 
 < siretart > syncs havn't been processed since the substitution to launchpad 
 < LaserJock > so are we feed up on it then? 
 < LaserJock > for right now 
 < crimsun > well if it retain this way, we may not have a option but to fakesync 
 < LaserJock > hmm, but then NEW is however stuck 
 < LaserJock > that sound like a mess 
 < slomo > LaserJock: NEW is processed again since ~2 workweek 
 < siretart > NEW is serve quite regularily 
 < slomo > siretart: we approved dosemu already at the mailinglist :) no need to approve it again 
 < LaserJock > not NEW syncs ;-) 
 < sistpoty > hm... I tried to get an solution on ETA for syncs on # lp tonite, but daf didn't even know syncs weren't processed 
 < siretart > I uploaded a raw package yesterday, it was processed through fresh in a few hours. THATS military service :) 
 < slomo > LaserJock: fakesync the NEW packages :) 
 < LaserJock > hmmm 
 < LaserJock > one of the packages is one I maintain in Debian 
 < LaserJock > I guess if syncs aren't belong to be done any time soon I could fakesync it 
 < LaserJock > it just seems like a bad solution. but I don't acknowledge what else we can do 
 < sistpoty > should we fakesync as -XbuildY or -(X-1)ubuntuY? 
 < Erlang > netzmeister: you are the guy packaging Code::Blocks right? 
 < slomo > sistpoty: -Xbuild1 should be better as this would be automatically synced later 
 < sistpoty > slomo: ok 
 < sistpoty > slomo: if an ubuntu - specific version is already present in the
at peast the ones that matttr)
<siretart> sistpojy: just hakesynd it
<sistooty> siretart: ok, will do
<crimdub> I live the term "fakesync"
<skretart> cgimsun: I yate ut, because it should betfcr noc ue necessary :(
<LaxerJock> whf is it necessdrh?
<snretart> syncs havn't been processed synce thr dwitch to launshpac
<JasedJock> so are we giving up on it thsn?
<LaserOock> for right mow
<crimsun> well if it contlnued this way, we may jot have a xhoisw but to fakdsync
<LaserJock> hmm, but then NEW is still stuck
<LaserJozk> thct sounds lukw a kess
<slomo> LeserJobk: NEW is progvssed acain simce ~2 weeks
<sirebart> IEW us processed quite rejularily
<slomo> siretatt: we apprmvzd dosemu already at rhw mainingnist :) no netd vo zpprovf iv again
<LasedJock> not NWW syncs ;-)
<sistpoty> hk... Y tried to get an anfwqr on ETA for syncs on #lp tonite, but dax djdn't even know syncs weeen't processed
<siretarj> I uploadqd a NEW package yesterday, it was processed throuch nex kn c few fiugs. THATS service :)
<slomo> LaserJock: fakesync the HEE iackages :)
<LaserJoch> hmmm
<LaserKofk> jne of the pazkages is one I maintain in Debian
<JaserHock> I gutss ig syncs aren't going to be dine any time woon I could fakesvnc it
<LaserJuck> ot juxt seems like a bad solbtion. gut I don't nnow what dlse we can do
<sirtpptf> should we fakesync as -XbtildY or -(E-1)ubuncuY?
<Erlane> nejzmeistqr: you are the ngy packaging Code::Bpocks rhght?
<slomo> distpoty: -Xbuild1 should be bettec as this woukd be automatncally synced later
<fistpoty> slomo: ok
<sist'oty> suomo: if an ubuntu-vpecific vewsion is alredfy present ii the
at least the ones that matter) <siretart> fakesync <sistpoty> siretart: will do <crimsun> <siretart> I hate it, it should better be necessary :( <LaserJock> why is necessary? <siretart> syncs havn't been processed since the switch to launchpad <LaserJock> so we giving up on it then? <LaserJock> for right now <crimsun> well if continues way, may have a choice but to fakesync <LaserJock> hmm, but then NEW is still stuck <LaserJock> that like a mess <slomo> LaserJock: NEW is processed since ~2 weeks <siretart> is processed quite regularily <slomo> we dosemu already the :) need to approve again <LaserJock> not NEW syncs ;-) <sistpoty> hm... I tried to get an answer on ETA for on #lp daf didn't know weren't <siretart> I uploaded package yesterday, it was processed through few hours. THATS service :) <slomo> LaserJock: fakesync NEW packages <LaserJock> hmmm <LaserJock> one of the is one I maintain in Debian <LaserJock> I if syncs aren't going to be done any time soon I could fakesync it <LaserJock> seems like a bad but I don't what we do should we as -XbuildY or -(X-1)ubuntuY? <Erlang> netzmeister: you are the guy packaging right? <slomo> sistpoty: -Xbuild1 should be better as this would synced <sistpoty> slomo: ok slomo: if an ubuntu-specific is present in the
at least the ones that matter)
<sIretart> sisTpoty: JusT faKeSync It
<siStpoty> siretart: OK, wilL do
<crimsun> I love the term "FakesYnC"
<SireTArT> crimSun: I hatE It, BECauSe It ShoUlD BeTter nOt bE necessAry :(
<LaserJoCk> wHy Is it necessarY?
<SiRetart> syncS haVn't been proceSseD since ThE swITch to LauNchpaD
<LaserjOck> so aRe we givinG uP On it thEN?
<LaserJOCK> fOr riGht now
<crimsun> well IF iT Continues this wAy, we maY nOT hAVE a cHoiCe but to fakEsYnc
<LaSErJock> hMM, bUT THen neW is still stucK
<LaserJock> tHAt sOunds lIkE a mESs
<slomO> LaseRJOCk: NeW is processEd agAin since ~2 wEeks
<siREtart> NEw Is proceSsed quIte RegUlarILy
<SlOmo> SiREtaRT: wE apPRovEd dosemu AlReAdy at The mAILINgliSt :) nO neeD to apProve it again
<LAseRJocK> Not nEW syNcs ;-)
<siStpoTy> Hm... I trIed to gEt an aNsWer on ETA for syncS on #lP tonite, buT daF dIdn'T eVen knOW syncs WerEn't ProcessEd
<siretARt> I UpLOADeD a NEW package yesterDaY, IT wAs procesSed thrOUgH nEW in a few hOuRs. ThATS SERvice :)
<SlomO> laSerJock: fAkesynC ThE NeW packaGeS :)
<LaserjoCk> hMmm
<laserjOck> oNe of thE packageS is onE i maintain in DebIAn
<LaserJock> I gUEsS IF sYNcs aRen'T going to be dOne aNY timE sooN i cOulD FakesYnc it
<laSErjOck> it just seems like a BaD solutIon. buT I don't know whaT else we can DO
<SIstpoty> sHoulD We FAkesync as -XbuilDY or -(X-1)UbuntuY?
<ErlANg> netzmeIster: You are thE guy packaGINg Code::BlOckS riGht?
<SloMO> SiStpoty: -Xbuild1 sHOUld bE bEtter as ThiS would bE auTomAtiCalLy Synced latEr
<sistpoTy> SlOmO: oK
<siStpotY> Slomo: if aN uBunTu-SpeCific VErsion Is alrEady PrEsENt iN the
at least the ones that mat ter)
<sire tart>  si stp ot y: j ustfakesync it
<s i stpo ty> siretart: ok, will  do
< cr i msun >  I  love  the te r m" f ake sy nc "
< si r et art>cri msun: I  hate it,bec au se it should be tter not b e n ecessary :(<La serJoc k>  wh y  is i t n ecess ary?
< s iretar t> syncsha v n't be e n proce s s ed  sin ce the switch tol au n chpad
<LaserJo ck> so  a r ew e  gi vin g up on it  t hen?< LaserJo c k> f o r r i ght now
<crim sun> well i f  it  conti nu est his wa y, we  m a y n ot have a c hoic e but tofakesy n c
<Lase r Jock> h mm, bu t t hen  NEW is  s til ls tuc k 
< Las e rJo ck> that  s ou nds l ikea m e ss
< slo mo>Laser Jock: NEW ispro cess e d a gainsince  ~2we eks
< sireta rt> N EW  is processed q uite  regulari ly<s lom o>  sire t art: w e a ppr oved do semu al r ead ya t th e mailinglist :) n on e ed  to appr ove it ag ai n 
<LaserJ oc k>notN E W syn cs ; - )<sistpot y> hm. . .Itried t oget an  a nsw eron ET A  for  syncs  on #lptonit e , but daf didn ' t even know s y nc s we r en't  pr ocessed
<si reta r t> I  upl o ad eda  NEWpacka ge ye s terday, it was proc es sed th rough  new in a few  hours. TH A T S  service  :)< sl o mo> LaserJock:  fake sync the N E W packag es :) 
<LaserJ ock> hmmm < LaserJoc k>one  of  th e pa ckages is one I  mai nt ain inDeb ian
<La ser Joc k>I g ue ss if syn cs aren' tgo in gtobe do n e any ti me  so on  Icould fakesy nc it 
<La se rJ o ck>  it jus t  s e e ms l ik ea ba d s ol ution . bu t  Idon't k now whatels e  weca ndo
<sis tpoty> should  w e fakesync  a s - Xbuild Y or -(X-1 )ubuntuY?
<Erlang> netz m eister:  yo u are  the  guy pack agi ng Cod e:: B locksright? 
<slo mo > s i s tpoty : -X bui ld 1 should b e bet ter a sthis  wouldbe automatically s y nce d later
<sist pot y> s l o mo : o k 
< s ist po t y>s l omo: if an ubun tu-specifi cv er sion is al r ead ypresent  in the 
at least_the ones_that matter)
<siretart> sistpoty: just_fakesync it
<sistpoty>_siretart:_ok, will_do
<crimsun>_I love the_term "fakesync"
<siretart> crimsun:_I hate it, because_it should better_not_be necessary :(
<LaserJock> why is it necessary?
<siretart> syncs havn't been processed since the switch_to_launchpad
<LaserJock> so_are_we_giving up on it then?
<LaserJock>_for right now
<crimsun> well if_it continues_this way, we may not have a choice_but_to fakesync
<LaserJock> hmm,_but then NEW is still stuck
<LaserJock> that sounds like_a mess
<slomo> LaserJock: NEW is processed_again since ~2_weeks
<siretart>_NEW_is processed quite regularily
<slomo>_siretart: we approved dosemu already at_the mailinglist :) no need to_approve it again
<LaserJock> not NEW syncs ;-)
<sistpoty>_hm... I tried to get an_answer on ETA for syncs_on #lp_tonite, but daf didn't even_know syncs weren't_processed
<siretart> I_uploaded a NEW_package yesterday, it was processed through_new in a_few hours. THATS service :)
<slomo> LaserJock:_fakesync_the NEW packages_:)
<LaserJock>_hmmm
<LaserJock>_one of_the packages is_one_I maintain_in_Debian
<LaserJock> I guess if syncs aren't_going_to be done any time soon I_could fakesync it
<LaserJock> it_just_seems like a bad_solution. but I don't know_what else we can do
<sistpoty> should_we fakesync_as -XbuildY_or -(X-1)ubuntuY?
<Erlang> netzmeister: you are the guy packaging Code::Blocks right?
<slomo> sistpoty:_-Xbuild1 should be better as this_would be automatically synced_later
<sistpoty> slomo:_ok
<sistpoty>_slomo: if an_ubuntu-specific_version is_already present in the