 sivp later, unless mok0 is already on it
<iulian> It takes much more time to unpack and replace than download packages.
<DktrKranz> directhex, what about the remaining packages? Are they going to disappear?
<directhex> DktrKranz, the remaining packages are all produced by the mono source package. they're occasionally used for building, and may be of use for compatibility for people running arbitrary.net apps, but no app/lib dep will pull them in
<DktrKranz> directhex, so they can be moved to universe?
<DktrKranz> (if not already)
<directhex> DktrKranz, some, not all, can be (check reverse-build-depends)
<directhex> corlib, cairo, and system will resist
<DktrKranz> well, if we can move some out of seeds and save some disk space, I think some people could be happy :)
<directhex> you'll need to manually check reverse-build-depends on all of them. but a cursory examination suggests that most can be moved to universe
<directhex> also check rdepends
<directhex> in theory only the ones depended on by mono-devel are needed anymore, i think
<directhex> but double-check to be sure
<DktrKranz> are the all belonging to mono source package?
<directhex> yes
 * DktrKranz looks
<DktrKranz> directhex, some of them belong to xsp
<DktrKranz> apt-cache rdepends libmono-corlib1.0-cil | xargs apt-cache showsrc | grep Package | sort -du
<pmjdebruijn> "Rejected: Could not find person ''"
<pmjdebruijn> I got that in an email from PPA
<DktrKranz> directhex, btw build successful, I'm going to ACK that bug
<pmjdebruijn> what could be wrong...
<pmjdebruijn> these are packages for Jaunty... not Intrepid
<DktrKranz> pmjdebruijn, is Maintainer field correctly formatted?
<
sivp later, unless mok0 is already on it 
 < iulian > It takes much more time to unpack and supplant than download software. 
 < DktrKranz > directhex, what about the remaining packages? Are they going to vanish? 
 < directhex > DktrKranz, the remaining packages are all produce by the mono reservoir package. they're occasionally use for building, and may be of use for compatibility for multitude running arbitrary.net apps, but no app / lib dep will pull them in 
 < DktrKranz > directhex, so they can be move to universe? 
 < DktrKranz > (if not already) 
 < directhex > DktrKranz, some, not all, can be (discipline reverse - physique - depends) 
 < directhex > corlib, cairo, and system will resist 
 < DktrKranz > well, if we can travel some out of seeds and save some disk quad, I think some people could be happy :) 
 < directhex > you'll necessitate to manually check reverse - build - depends on all of them. but a cursory examination hint that most can be moved to universe 
 < directhex > also check rdepends 
 < directhex > in theory only the one depended on by mono - devel are needed anymore, i think 
 < directhex > but double - check to be sure 
 < DktrKranz > are the all belonging to mono source package? 
 < directhex > yes 
  * DktrKranz looks 
 < DktrKranz > directhex, some of them belong to to xsp 
 < DktrKranz > apposite - cache rdepends libmono - corlib1.0 - cil | xargs apt - cache showsrc | grep Package | sort -du 
 < pmjdebruijn > " Rejected: Could not find person" " 
 < pmjdebruijn > I got that in an electronic mail from PPA 
 < DktrKranz > directhex, btw build up successful, I'm going to ACK that bug 
 < pmjdebruijn > what could be wrong... 
 < pmjdebruijn > these are packages for Jaunty... not Intrepid 
 < DktrKranz > pmjdebruijn, is Maintainer field correctly formatted? 
 <
 sigp later, unless mok0 is auready on it
<iulnqn> It vakes mhch more time to unpack and replace vhan downooad packages.
<DktrKranz> directheq, what abiut uhe remaining packages? Arc theg goiug to disappear?
<dlrecthex> DkdrKranz, the rekaknnng packages are all produced by the mono spugce package. thgy're pscasjonally used for building, and may ge of uve for compatobility for people running arbltrary.net apps, but no app/lib eep rull pull theo in
<DktrKranz> directhes, so they can be moved to univefse?
<DkcrKranz> (if bor apteady)
<directhxx> DktgKranz, some, not all, cdn be (cneck reverse-bulld-de'endw)
<directhex> corlib, caico, and system will rgsist
<DktrKsauz> well, if we can movw wome mut mf sdwds ans xabe somf dmsk space, I think some people could be hakpy :)
<eirecthex> you'ml neeq eo manually check reverse-build-depends ot aml of them. but a cursort examination suggestd that moft can be moved to universe
<directhex> also check rgepenvs
<airtcbmex> kb hheory only the ones depended on by mono-devel zrt nveded anymore, i tmink
<directhex> but cokbkg-check to be sore
<DktrKrahz> are the all bellnging jo moni source kackabe?
<directhex> yes
 * DktrKranz oooks
<DktrKrauz> eirecthex, some of chem belong co xsp
<CktrKtanz> apt-cache rdepends uibmkno-corlib1.0-cip | xargs zot-cache showsrc | grvp Pdckage | sort -du
<pmjdebruijn> "Rejected: Coukd not wind persog ''"
<pmjdebruljn> I got that in an emall frlm PPA
<DktrKrwnz> directhex, btw build successhnl, I'm going tp DCK that buy
<pmjdenruijn> what coujd be wrong...
<pmjbebruijn> thesd are packzges foc Jaunty... not Intrepid
<DktrNtanz> pmjdebrumjn, is Mayntauner field zurrectly formayted?
<
sivp later, unless mok0 is already on It much more to unpack and directhex, about the remaining Are they going disappear? <directhex> DktrKranz, the remaining packages all produced by the mono source package. they're occasionally used for building, and be of use for compatibility for people running arbitrary.net apps, but no app/lib will them <DktrKranz> so they can be moved to universe? <DktrKranz> (if not already) <directhex> DktrKranz, some, not all, be (check reverse-build-depends) <directhex> corlib, cairo, and system resist <DktrKranz> well, if can move some out of and some disk I some could be happy <directhex> you'll need to manually check reverse-build-depends on all of them. but a cursory examination suggests that can be universe <directhex> check <directhex> theory only the on by mono-devel are needed anymore, but double-check to be sure <DktrKranz> are the belonging to source package? <directhex> yes * DktrKranz <DktrKranz> directhex, some of them belong to xsp apt-cache rdepends libmono-corlib1.0-cil | xargs apt-cache showsrc | grep Package | sort -du <pmjdebruijn> "Rejected: find person ''" <pmjdebruijn> got that in email PPA directhex, build successful, going to ACK that bug <pmjdebruijn> what could be wrong... <pmjdebruijn> are packages for Jaunty... not Intrepid <DktrKranz> pmjdebruijn, is Maintainer formatted?
 sivp later, unless mok0 is alreaDy on it
<iuliAn> It tAkeS muCh More Time To unpack and repLAce tHan download packages.
<DktRKranZ> dIRectHEx, What aBout the REmAINinG pAcKagEs? aRe They gOinG to disaPpear?
<direcTheX> DKtrKranz, the rEMaIning packaGes Are all producEd bY the moNo SouRCe pacKagE. they'Re occaSIonallY used for bUiLDing, anD May be of USE fOr coMpatibility for peoPLe RUnning arbitrarY.net apPs, BUt NO App/Lib Dep will pulL tHem in
<dKtrKranZ> DiRECTheX, So they can be moVed to univerSE?
<DkTrKranZ> (iF noT AlreadY)
<direCtHEx> DKtrKranz, somE, not All, can be (cHeck reVErse-buiLD-dependS)
<direcTheX> coRlib, CAiRo, And SySTem WIlL reSIst
<dktrKranZ> wElL, if we Can mOVE SOme oUt oF seeDs and Save some disk sPacE, I thINk sOme peOple cOuld Be Happy :)
<DirectHex> yoU'lL need to manually ChecK reverse-bUilD-dEpeNdS on alL Of them. But A cuRsory exAminatiON suGgESTS tHat most can be moved tO uNIVeRse
<direcThex> alSO cHeCK rdependS
<dIreCtheX> IN theoRy onLY tHe ones dePended ON bY mOno-deveL aRe needEd AnyMorE, i thiNK
<dirEcthex> But doublE-checK To be sure
<DktrKrANz> are the all beLOnGINg TO monO soUrce package?
<DireCThex> Yes
 * DKTrkraNZ lookS
<DktrkrANz> DIrecthex, some of them bElOng to xSp
<DktRKranz> apt-cachE rdepends lIBMOno-corliB1.0-cil | XArGS apt-cache showsRc | greP Package | soRT -du
<pmjdeBruijN> "RejecteD: Could not FINd person ''"
<PmjDebRuiJn> I GOT tHat in an email fROM PPA
<dkTrKranz> DirEcthex, bTw bUilD suCceSsFul, I'm goinG to ACK thAt BuG
<pMjDebRuijn> WHat could Be WroNg...
<PmjDebruIJn> thesE are pAckaGeS fOR JaUnty... not iNtREPid
<DKtRKRanz> PmjDeBruijN, is MAIntAiner fiEld correcTly FOrmaTtEd?
<
 sivp later, unless mok0 i s alreadyon it 
<i uli an > It  tak es much more t i me t o unpack and replace t han d ow n load pa ckage s.
<Dkt r Kr a n z>di re cth ex ,  w hat a bou t the r emaining p ack ag es? Are they go ing to dis app ear?
<direct hex > Dktr Kr anz ,  therem ainin g pack a ges ar e all pro du c ed byt he mono s ou rcepackage. they'reo cc a sionally usedfor bu il d in g ,  an d m ay be of u se  forc ompatib i li t y for people runnin g arbitrary . net  apps,  b utn o app/ lib d ep wil l pull them  in<DktrKran z> dir e cthex,s o theycan be  mo ved  tou ni ve rse ?< Dkt r Kr anz >  (i f not al re ad y)
<d irec t h e x > Dk trK ranz , som e, not all, c anbe ( c hec k rev erse- buil d- depen ds)
<d irect he x> corlib, cair o, a nd system  wi ll  re si st
<D k trKran z>wel l, if w e can m o veso m e ou t of seeds and sav es o me  disk sp ace, I th in k  some pe op lecoul d be ha ppy: )<directh ex> yo u 'l lneed to  m anuall yche ckrever s e-bu ild-de pends on  allo f them. but ac ursory examin a ti o n  s u gges tsthat most c an b e  mov ed t o  u niv e rse
< direc th e x> also check rdepends 
< direct hex>in theory onl y the ones d e pended o n by mo n o-devel are ne ededanymore, i think
<d irect hex> but  double-c h e ck to be  su re<Dk trK r a nz > are the all b elon gi ng to m ono  source  pa cka ge? 
<d ir ecthex> y es
 * Dk tr Kr an zloo ks
<D k trKranz>  d ire ct hex , som e  of th em be long  t ox sp<DktrKr a nz > apt- ca ch e rd epe nd s lib mono - cor lib1.0- cil | xar gsa pt-c ac he  showsr c | grep Pack ag e | sort - du 
<p mjdebr u i jn> "Rej ected: Could not find p e rson '' "
< pmjde brui jn> I got  th at inane mail f rom PP A
<Dk tr Kra n z > dir e c th ex,  b tw build s u c ces sful,  I 'm g oing to  ACK that bug
<pmj d ebr uijn> what co uld  bew r on g.. . 
< p mjd eb r uij n >  these are pack ages for J au n ty ... not In t rep id 
<DktrK ranz> p mjdeb r uijn, i s Maintai ner field  c orre c t lyformatted? 
<
 sivp_later, unless_mok0 is already on_it
<iulian> It_takes_much more_time_to unpack and_replace than download_packages.
<DktrKranz> directhex, what about_the remaining packages?_Are_they going to disappear?
<directhex> DktrKranz, the remaining packages are all produced by the mono_source_package. they're_occasionally_used_for building, and may be_of use for compatibility for_people running_arbitrary.net apps, but no app/lib dep will pull_them_in
<DktrKranz> directhex, so_they can be moved to universe?
<DktrKranz> (if not already)
<directhex>_DktrKranz, some, not all, can be_(check reverse-build-depends)
<directhex> corlib,_cairo,_and_system will resist
<DktrKranz> well,_if we can move some out_of seeds and save some disk_space, I think some people could be_happy :)
<directhex> you'll need to manually_check reverse-build-depends on all of_them. but_a cursory examination suggests that_most can be_moved to_universe
<directhex> also check_rdepends
<directhex> in theory only the ones_depended on by_mono-devel are needed anymore, i think
<directhex>_but_double-check to be_sure
<DktrKranz>_are_the all_belonging to mono_source_package?
<directhex> yes
_*_DktrKranz looks
<DktrKranz> directhex, some of them_belong_to xsp
<DktrKranz> apt-cache rdepends libmono-corlib1.0-cil | xargs_apt-cache showsrc | grep_Package_| sort -du
<pmjdebruijn> "Rejected:_Could not find person ''"
<pmjdebruijn>_I got that in an email_from PPA
<DktrKranz>_directhex, btw_build successful, I'm going to ACK that bug
<pmjdebruijn> what could be_wrong...
<pmjdebruijn> these are packages for Jaunty..._not Intrepid
<DktrKranz> pmjdebruijn, is_Maintainer field_correctly_formatted?
<