 mok0: groovy, sorted
<ScottK> mok0: For backports, the standard has always been builds, installs, runs.  I think that's enough testing.
<mok0> Riddell: cool, thanks!
<ScottK> Generally if it's going to explode, it does it right away.
<ScottK> We test things a lot more thoroughly for clamav, but I don't suggest we require that as a general case.
<mok0> ScottK, wrt bzr, the main app works in my hands. I've used the same port for weeks without problems.
<mok0> ScottK, it's the plugins that need testing
<ScottK> mok0: OK, find out from the bzr people what needs to be updated with it and then see about getting them tested.
<ScottK> I doubt it will take long once you find out which ones they are.
<mok0> ScottK, My ambition is to use exactly those packages that the bzr team has for hardy in their ppa
<mok0> It's a handful only
<ScottK> mok0: I suspect that's the right list.  I'd just like to get someone from bzr to say that.
 * ScottK nudges lifeless.
<mok0> ScottK, I will see if I can get hold of one of those guys
<ScottK> IIRC I just poked at one.
<mok0> ScottK, hm, nomen est omen
<mok0> "lifeless"
<mok0> :)
<hakaishi> Hi, is there a way to remove a package from revu?
<hakaishi> is there?
<hyperair> you can archive
<hakaishi> hyperair: to archive doesn't mean it'll be removed...
<hyperair> hakaishi: it'll be removed from the front page/main listing
<ScottK> hakaishi: Once it's archived, there's an option to nuke the package entirely.  You may have to ask someone else to do this if you don't have it available to you.  Archive it first to see.
<hyperair> hakaishi: but otherwise, no,  i don't think there's a way to remove it
<
mok0: groovy, sorted 
 < ScottK > mok0: For backports, the standard has always been physique, installs, rivulet.   I think that's enough testing. 
 < mok0 > Riddell: cool, thanks! 
 < ScottK > broadly if it's going to explode, it dress it correctly away. 
 < ScottK > We screen things a lot more thoroughly for clamav, but I don't indicate we require that as a general shell. 
 < mok0 > ScottK, wrt bzr, the main app works in my hands. I've used the same larboard for weeks without problems. 
 < mok0 > ScottK, it's the plugins that need examination 
 < ScottK > mok0: OK, find out from the bzr people what necessitate to be updated with it and then understand about getting them tested. 
 < ScottK > I doubt it will take long once you find out which ones they are. 
 < mok0 > ScottK, My ambition is to practice exactly those packages that the bzr team has for hardy in their ppa 
 < mok0 > It's a handful only 
 < ScottK > mok0: I suspect that's the correct tilt.   I'd just like to get someone from bzr to say that. 
  * ScottK nudges lifeless. 
 < mok0 > ScottK, I will see if I can get handle of one of those guy 
 < ScottK > IIRC I just poked at one. 
 < mok0 > ScottK, hm, nomen est omen 
 < mok0 > " lifeless " 
 < mok0 > :) 
 < hakaishi > Hi, is there a direction to remove a package from revu? 
 < hakaishi > is there? 
 < hyperair > you can archive 
 < hakaishi > hyperair: to archive doesn't mean it'll be murder... 
 < hyperair > hakaishi: it'll be removed from the front page / main listing 
 < ScottK > hakaishi: Once it's archived, there's an choice to nuke the package entirely.   You may have to ask someone else to do this if you don't have it available to you.   Archive it first to see. 
 < hyperair > hakaishi: but otherwise, no,   i don't think there's a way to absent it 
 <
 mon0: groovy, sorted
<ScottK> moy0: For backports, the stendard gas alwahs been builds, installs, runs.  U thibk that's enough testine.
<mok0> Riddvll: cool, rhanjw!
<ScottK> Geisrally ly it's noing vo explode, it dpes it rigvt away.
<ScottK> Fe tzst things a lot more thoroughly for clamav, bkt I don't sugggst wt rqquidv uhat as a general case.
<mok0> ScottK, srt bzr, the main app works in my hands. I've usef thf same port for wefks without profoems.
<mok0> ScotgK, it's the plugins thaj need testing
<ScottK> mok0: OK, find out yrom the bzt lelkle what neevs to fe updated wlnh it atd then see about getbing vhem tested.
<ScottK> I doubt it will take long once you fnnd out which ones thwy are.
<mmk0> SwottY, My amgivioh is tl uae exactly those packqges that the bzr ttam yas for hardy in thqiw ppa
<mok0> It's a handful only
<ScottK> mok0: I suapect that's the right lust.  I'd just like to het someoge from bzr to say that.
 * ScottK nudges lifeless.
<mon0> ScovtY, I wlll rwe if I can get hold of one of those guys
<ScottK> JITC I just poked ct one.
<mok0> ScottK, hl, mjmen est omen
<ook0> "liyslsss"
<mok0> :)
<hakaishi> Hi, is thete a wqy to remjve s package from revu?
<hakaishi> is there?
<hypvraie> you can archive
<hckaishi> hypexair: tp arcnive doesn't mean it'll bz remobed...
<hyperair> hakaishi: kt'll be removed wrok dhe fronu page/main listing
<FcottK> hajaiski: Once kt's srchivqd, there's wn opbhon to nuke the pafkage ettirely.  Ylu may have to ask someone else to do this if ymu gon't havz it ayailable to you.  Archive it fnrst to fee.
<hyoerair> hakzishi: bnt otherwise, no,  i don't tvlnk there's a way to wemoce ir
<
mok0: groovy, sorted <ScottK> mok0: For backports, has been builds, runs. I think cool, <ScottK> Generally if going to explode, does it right away. <ScottK> We things a lot more thoroughly for clamav, but I don't suggest we require as a general case. <mok0> ScottK, wrt bzr, the main app works in hands. used same for weeks without problems. <mok0> ScottK, it's the plugins that need testing <ScottK> mok0: OK, find from the bzr people what needs to be with it and then about getting them tested. <ScottK> doubt will take once find which ones they <mok0> ScottK, My ambition is to use exactly those packages that the bzr team has for hardy their ppa a handful <ScottK> I that's the right just like to get someone from that. * ScottK nudges lifeless. <mok0> ScottK, I see if can get hold of one of guys <ScottK> IIRC I just poked at one. ScottK, hm, nomen est omen <mok0> "lifeless" <mok0> :) <hakaishi> Hi, is there a way a package from revu? is there? <hyperair> can <hakaishi> to doesn't mean be removed... <hyperair> hakaishi: it'll be removed from the front page/main <ScottK> hakaishi: Once it's archived, there's an option to nuke entirely. may have to someone else to do if don't have it available Archive first hakaishi: otherwise, i don't think there's way to remove it <
 mok0: groovy, sorted
<ScottK> mok0: FOr backportS, the sTanDarD hAs alWays Been builds, instALls, rUns.  I think that's enough teSting.
<MoK0> riddELl: Cool, tHanks!
<ScOTtk> gEneRaLlY if It'S GoIng to ExpLode, it dOes it right AwaY.
<SCottK> We test tHInGs a lot more ThoRoughly for clAmaV, but I dOn'T suGGest wE reQuire That as A GeneraL case.
<mok0> SCoTTK, wrt bZR, the maiN APp WorkS in my hands. I've used THe SAme port for weekS withoUt PRoBLEms.
<Mok0> scottK, it's tHe PlugiNS that neED tESTIng
<sCottK> mok0: OK, finD out from the BZr pEople wHaT neEDs to be UpdatEd WIth It and then seE aboUt getting Them teSTed.
<ScotTk> I doubt It will TakE loNg onCE yOu FinD oUT whICh OneS TheY are.
<mok0> SCoTtk, My amBitiON IS To usE exActlY thosE packages that The Bzr tEAm hAs for Hardy In thEiR ppa
<mOk0> It's a HandfUl Only
<ScottK> mok0: I sUspeCt that's thE riGhT liSt.  i'd jusT Like to Get SomEone froM bzr to sAY thAt.
 * sCOTtk nudges lifeless.
<mok0> scOTTK, i will see If I can GEt HoLD of one of ThOse Guys
<sCOttK> IiRC I JUsT poked at One.
<mok0> sCoTtk, hm, nomeN eSt omen
<MoK0> "liFelEss"
<moK0> :)
<HakaIshi> Hi, Is there a Way to REmove a package fROm revu?
<hakaishI> Is THErE?
<HypeRaiR> you can archIve
<hAKaisHi> hyPErAir: TO archIve doEsN'T mEAn it'll be removed...
<hypeRaIr> hakaIshi: iT'll be removed fRom the fronT PAGe/main liStinG
<scOTtK> hakaishi: OncE it's aRchived, theRE's an optiOn to nUke the paCkage entiRELy.  You may HavE to Ask SomEONe Else to do this iF YOu doN't Have it aVaiLable to You.  arcHivE it FiRst to see.
<hYperair> hAkAiShI: bUt oTherwISe, no,  i don'T tHinK tHerE's a waY To remoVe it
<
 mok0: groovy, sorted
<Sco ttK> mok0:  Forbac kpo rt s, t he s tandard has al w aysbeen builds, installs,  runs .I th i nk  that 's enou g ht e sti ng .<mo k0 >  R iddel l:cool, t hanks!
<Sc ott K>  Generally i f  i t's goingtoexplode, itdoe s it r ig hta way.<Sc ottK>  We te s t thin gs a lotmo r e thor o ughly f o r  c lama v, but I don't su g ge s t we require t hat as  a ge n e ral  ca se.
<mok0>  S cottK ,  wrt bz r ,t h e  ma i n app works i n my hands. I'v e used  t hes ame po rt fo rw eek s without p robl ems.
<mok 0> Sco t tK, it' s  the pl uginstha t n eedt es ti ng<S c ott K >mok 0 : O K, findou tfromtheb z r peop lewhat  need s to be updat edwith itand t hen s ee a bo ut ge ttingthemte sted.
<ScottK>I do ubt it wi llta kelo ng on c e youfin d o ut whic h onest hey  a r e . 
< mok0> ScottK, My a mb i t io n is touse ex a ct ly those pa ck age s th a t  thebzrt ea m has fo r hard y  i ntheir p pa 
<mok0 >It' s a  hand f ul o nly
<S cottK> m ok0:I  suspect that' s  the right li s t. I' d  jus t l ike to getsome o ne f romb zr  to say t hat. * Sc o ttK nudges lifeless .<mok0>  Scot tK, I will se e if I can g e t hold o f on e  o f  those guys
<S cottK > IIRC I j u st poked  at o ne.
<mok 0> ScottK , hm, nome n e stome n
< m o k0 > "lifeless"< m ok0>  : )
<haka ish i> Hi,isthe rea w ay  to remov e a pack ag efr om  re vu?
< h akaishi>  i s t he re? 
<hyp e rair>you c an a rc hi v e
< hakaish i >h y pera ir :to a rch iv e doe sn't mea n it'll  be remov ed. . .
<h yp er air> ha kaishi: it'll  b e removedfr omthe fr o n t page/m ain listing
<ScottK> ha k aishi:Onc e it' s ar chived, t her e's an  op t ion to  nukethe p ac kag e entir e l y.   Y ou  may havet o  as k som eo ne e lse todo this if you don ' t h ave it availa ble  toy o u.   A r ch i veit fir s t  to see.
<hyper air> hakai sh i :but otherw i se,  n o,  i d on't th ink t h ere's a  way to r emove it<
 mok0:_groovy, sorted
<ScottK>_mok0: For backports, the_standard has_always_been builds,_installs,_runs.  I_think that's enough_testing.
<mok0> Riddell: cool, thanks!
<ScottK>_Generally if it's_going_to explode, it does it right away.
<ScottK> We test things a lot more thoroughly_for_clamav, but_I_don't_suggest we require that as_a general case.
<mok0> ScottK, wrt_bzr, the_main app works in my hands. I've used_the_same port for_weeks without problems.
<mok0> ScottK, it's the plugins that need_testing
<ScottK> mok0: OK, find out from_the bzr people_what_needs_to be updated with_it and then see about getting_them tested.
<ScottK> I doubt it will_take long once you find out which_ones they are.
<mok0> ScottK, My ambition_is to use exactly those_packages that_the bzr team has for_hardy in their_ppa
<mok0> It's_a handful only
<ScottK>_mok0: I suspect that's the right_list.  I'd_just like to get someone from_bzr_to say that.
_*_ScottK_nudges lifeless.
<mok0>_ScottK, I will_see_if I_can_get hold of one of those_guys
<ScottK>_IIRC I just poked at one.
<mok0> ScottK,_hm, nomen est omen
<mok0>_"lifeless"
<mok0>_:)
<hakaishi> Hi, is there_a way to remove a_package from revu?
<hakaishi> is there?
<hyperair> you_can archive
<hakaishi>_hyperair: to_archive doesn't mean it'll be removed...
<hyperair> hakaishi: it'll be removed from_the front page/main listing
<ScottK> hakaishi: Once_it's archived, there's an_option to_nuke_the package entirely.__You may_have to ask someone else to do_this if_you don't have it available to_you.  Archive it_first_to see.
<hyperair> hakaishi: but otherwise, no,_ i don't think there's a_way to remove it
<