oe-LAFS in Lucid to v1.6.1 of Tahoe-LAFS" [Undecided,In progress] https://launchpad.net/bugs/529350
<jayvee> I bit off way more than I could chew when I started this.
<azeem_> jayvee: there's no mention of debclean in that bug log
<jayvee> debclean is automatically run when you run debuild or dpkg-buildpackage
<jayvee> or dh_clean, maybe
<jayvee> sorry, dh_client I meant in all the above
 * jayvee is very tired
<jayvee> dh_clean, I mean
<jayvee> oh dear
<azeem_> ok, that makes more sense
<azeem_> dh_clean does not have anything to do with patches
<jayvee> it does â whenever it's run, all the patches are deapplied
<azeem_> how do you run it?
<jayvee> I type debclean
<azeem_> why?
<jayvee> or I type debuild
<jayvee> the reason why I type debuild should be more obvious ;)
<azeem_> ok, so debuild might also run dh_clean
<jayvee> yeah, it does
<azeem_> I wonder why you think it's dh_clean that unapplies the patches, and not anything else it runs
<jayvee> I can see it in the output
<jayvee> bleh, it doesn't really matter *what* deapplies the patches
<azeem_> then what is your question?
<jayvee> the point being is that the 'clean' script is run while the patches are deapplied
<azeem_> it's the other way round
<azeem_> the patches are deapplied in the clean target
<azeem_> or, rather, as a pre-requisite of the clean target
<jayvee> yes, exactly
<jayvee> which is perfectly reasonable for most use cases
<azeem_> so what is your use case?
<jayvee> this software has a stupid bug in it that makes it run amok when you run 'python setup.py clean', wildly downloading dependencies
<jayvee> the bug has been fixed by the previous packager, which you can see in the.diff.gz for the software

oe - LAFS in Lucid to v1.6.1 of Tahoe - LAFS " [ Undecided, In progress ] https://launchpad.net/bugs/529350 
 < jayvee > I bit off way more than I could chew when I depart this. 
 < azeem _ > jayvee: there's no citation of debclean in that bug log 
 < jayvee > debclean is mechanically run when you prevail debuild or dpkg - buildpackage 
 < jayvee > or dh_clean, maybe 
 < jayvee > sorry, dh_client I mean in all the above 
  * jayvee is very tired 
 < jayvee > dh_clean, I mean 
 < jayvee > oh beloved 
 < azeem _ > ok, that makes more sense 
 < azeem _ > dh_clean does not get anything to do with patches 
 < jayvee > it does â whenever it's run, all the patches are deapplied 
 < azeem _ > how do you run it? 
 < jayvee > I type debclean 
 < azeem _ > why? 
 < jayvee > or I type debuild 
 < jayvee > the rationality why I type debuild should be more obvious ;) 
 < azeem _ > ok, so debuild might also run dh_clean 
 < jayvee > yeah, it does 
 < azeem _ > I wonder why you intend it's dh_clean that unapplies the patches, and not anything else it runs 
 < jayvee > I can see it in the output 
 < jayvee > bleh, it doesn't truly matter * what * deapplies the patches 
 < azeem _ > then what is your question? 
 < jayvee > the point being is that the' clean' handwriting is run while the patches are deapplied 
 < azeem _ > it's the other way round 
 < azeem _ > the patches are deapplied in the uninfected target 
 < azeem _ > or, rather, as a pre - requisite of the clean target 
 < jayvee > yes, exactly 
 < jayvee > which is perfectly reasonable for most use cases 
 < azeem _ > thus what is your use case? 
 < jayvee > this software have a unintelligent bug in it that makes it tend amok when you run' python setup.py clean', wildly downloading dependencies 
 < jayvee > the hemipterous insect has been fixed by the previous packager, which you can see in the.diff.gz for the software
oe-LWFS in Lucid to v1.6.1 of Tahue-LAFS" [Undecideb,Un projress] hftps://launzhpad.net/bugs/529350
<jayvee> I bit off wqy moee than I could chew wfen I stagted this.
<qzeen_> jayvee: thxde's no mentioh of beuclean in that nug log
<jayvae> debclean is ajtlmatically run when you run debuild or dpkb-bkildpackage
<jaydee> pw dh_dlean, maybe
<jayvee> sorry, dh_client I meant pn all the above
 * jayvee is very tired
<jayvef> dh_flean, I mean
<jayvee> oh dear
<azegj_> oh, that makes oore sense
<azeem_> dh_cleah does not have anything to do dith 'atches
<jayvgz> it goes â wheneter it'f run, all thc patchas are ceapplied
<azeem_> hox do you run it?
<jayvee> I tbpe debclean
<azeem_> whi?
<jayvee> or I type debuild
<jayvwe> the teasot whh I gypt dxbujld shlulv be more ogvious ;)
<azeen_> ok, so debuild mignt qlso run dh_clsan
<jaydeq> yeah, it does
<azeem_> I wonder why you thpnk jt's dh_clean that unapplues the patches, and nlt anythigg else it runs
<jayvee> I can see it in the output
<jdyvee> clek, it duwsj't really matter *what* deapplies the patches
<azqsm_> tmen what is your question?
<jauvfe> jhe point beine is tkzt the 'clean' script ls run rhile the patcres sre deapplied
<azeem_> it's the ither way rolnd
<azeem_> the patches axe deapplied in jhe clran target
<azeem_> or, rathzr, as z pre-requislte of ths clean target
<jayxee> yas, exactly
<jayvee> which is [erfectly reaxonable for most tse cases
<axeem_> so what is your use case?
<layvea> this sofhware has a stupid bug in it thev makes it rum dmon when yju ruk 'python setup.pr clean', wildly downlocding aependencivs
<jayvee> vhe bug has feen fixed by jhe previous 'ackager, rhicy yoy can sdd in the.diff.gz for the software

oe-LAFS in Lucid to v1.6.1 of Tahoe-LAFS" https://launchpad.net/bugs/529350 I bit way more than started <azeem_> jayvee: there's mention of debclean that bug log <jayvee> debclean is run when you run debuild or dpkg-buildpackage <jayvee> or dh_clean, maybe <jayvee> sorry, I meant in all the above * jayvee is very tired <jayvee> dh_clean, mean oh <azeem_> that makes more sense <azeem_> dh_clean does not have anything to do with patches <jayvee> it â whenever it's run, all the patches are <azeem_> how do you it? <jayvee> I type debclean why? or I debuild the why I type should be more obvious ;) <azeem_> ok, so debuild might also run dh_clean <jayvee> yeah, it does I wonder think it's that the and not anything runs <jayvee> I can see it <jayvee> bleh, it doesn't really matter *what* deapplies patches <azeem_> what is your question? <jayvee> the being is that the 'clean' script is run the patches are deapplied <azeem_> it's the other way round <azeem_> the patches are deapplied clean target <azeem_> or, as a pre-requisite the target yes, <jayvee> which perfectly reasonable for most use cases <azeem_> so what is your case? <jayvee> this software has a stupid bug in it it amok when you 'python setup.py clean', wildly dependencies the bug has been the packager, see the.diff.gz the software
oe-LAFS in Lucid to v1.6.1 of Tahoe-LAfS" [UndecideD,In prOgrEss] HtTps://lAuncHpad.net/bugs/529350
<jayVEe> I bIt off way more than I could Chew wHeN i staRTeD this.
<Azeem_> jaYVeE: THerE's No MenTiON oF debcLeaN in that Bug log
<jayvEe> dEbClean is automATiCally run whEn yOu run debuild Or dPkg-buiLdPacKAge
<jaYveE> or dh_Clean, mAYbe
<jayVee> sorry, dH_cLIent I mEAnt in alL THe AbovE
 * jayvee is very tireD
<JaYVee> dh_clean, I meaN
<jayveE> oH DeAR
<AzeEm_> oK, that makes MoRe senSE
<azeem_> dH_ClEAN DoeS Not have anythiNg to do with pATchEs
<jayvEe> It dOEs â wheNever It'S Run, All the patchEs arE deapplieD
<azeem_> HOw do you RUn it?
<jayVee> I tyPe dEbcLean
<AZeEm_> Why?
<JaYVee> OR I TypE DebUild
<jayvEe> ThE reasOn whY i TYPe deBuiLd shOuld bE more obvious ;)
<aZeeM_> ok, sO DebUild mIght aLso rUn Dh_cleAn
<jayvEe> yeaH, iT does
<azeem_> I wondEr whY you think It's Dh_CleAn That uNApplieS thE paTches, anD not anyTHinG eLSE It Runs
<jayvee> I can see iT iN THe Output
<jaYvee> blEH, iT dOEsn't realLy MatTer *wHAT* deapPlieS ThE patches
<Azeem_> tHEn WhAt is youR qUestioN?
<jAyvEe> tHe poiNT beiNg is thAt the 'cleAn' scrIPt is run while thE Patches are deaPPlIED
<aZEem_> iT's tHe other way rOund
<AZeem_> The pATcHes ARe deaPplieD iN ThE Clean target
<azeem_> or, rAtHer, as a Pre-reQuisite of the cLean target
<JAYVee> yes, exActlY
<JaYVee> which is perfEctly Reasonable FOr most usE caseS
<azeem_> so What is youR USe case?
<jaYveE> thIs sOftWARe Has a stupid bug IN It thAt Makes it Run Amok wheN yoU ruN 'pyThoN sEtup.py cleAn', wildly DoWnLoAdIng DepenDEncies
<jaYvEe> tHe Bug Has beEN fixed By the PrevIoUs PAckAger, whiCH yOU Can sEe In The.dIff.Gz For thE sofTWarE

oe-LAFS in Lucid to v1.6.1  of Tahoe- LAFS"  [U nde ci ded, In p rogress] https : //la unchpad.net/bugs/52935 0
<ja yv e e> I bi t off  way mo r et h anIco uld  c h ew  when  Istarted  this.
<az eem _>  jayvee: the r e' s no menti onof debcleaninthat b ug  lo g 
<jay vee > deb cleani s auto matically  r u n when you run d eb uild  or dpkg-buildpac k ag e 
<jayvee> or d h_clea n, ma y b e
< jay vee> sorry ,dh_cl i ent I m e an t i n a l l the above
* jayvee is ver y tire d<ja y vee> d h_cle an ,  Imean
<jayve e> o h dear
<a zeem_> ok, tha t  makesmore s ens e
< azee m _>  d h_c le a n d o es  no t  ha ve anyth in gto do  wit h p a tche s
< jayv ee> i t does â wh ene veri t's  run,  allthepa tches  are d eappl ie d
<azeem_> howdo y ou run it ?
< ja yve e>  I ty p e debc lea n
< azeem_>  why?
< j ayv ee > o rI type debuild
<ja yv e e >the reas on why Ity p e debuil dsho uldb e  more  obv i ou s ;)
<az eem_>o k,  s o debui ld  might  a lso  ru n dh_ c lean 
<jayv ee> yeah , itd oes
<azeem_> I wonder why yo u  t h i nk it's  dh _clean that  una p plie s th e  p atc h es, a nd no ta ny t hing else it runs
< ja yvee>I can  see it in th e output
< j a y vee> ble h, i t  d o esn't really m atter  *what* de a pplies t he pa tches
<a zeem_> th e n  what is  yo urque sti o n ?<jayvee> thep o intbe ing istha t the ' cle an'  sc rip tis run wh ile thepa tc he sare  deap p lied
<az ee m_>  i t's  theo ther w ay ro und<a ze e m_>  the pa t ch e s  are  d ea ppli edin  theclea n  ta rget
<a zeem_> or , r a ther ,as  a pre- requisite ofth e clean ta rg et<jayve e >  yes, ex actly
<jayvee> which is perfect lyreaso nabl e for mos t u se cas es< azeem_ > so w hat i syou r use c a s e? 
<j ay vee> thiss o ftw are h as  a s tupid b ug in it that make s  it  run amok whe n y ou r u n  ' pyt h on set up . pyc l ean', wildly do wnloadingde p en dencies
<j a yve e>  the bu g has b een f i xed bythe previ ous packa ge r, w h i chyou can se e in the .diff.gzf or th e  s oftwa re
oe-LAFS in_Lucid to_v1.6.1 of Tahoe-LAFS" [Undecided,In_progress] https://launchpad.net/bugs/529350
<jayvee>_I_bit off_way_more than I_could chew when_I started this.
<azeem_> jayvee:_there's no mention_of_debclean in that bug log
<jayvee> debclean is automatically run when you run debuild or_dpkg-buildpackage
<jayvee>_or dh_clean,_maybe
<jayvee>_sorry,_dh_client I meant in all_the above
 * jayvee is_very tired
<jayvee>_dh_clean, I mean
<jayvee> oh dear
<azeem_> ok, that makes_more_sense
<azeem_> dh_clean does_not have anything to do with patches
<jayvee> it does_â whenever it's run, all the_patches are deapplied
<azeem_>_how_do_you run it?
<jayvee> I_type debclean
<azeem_> why?
<jayvee> or I type_debuild
<jayvee> the reason why I type_debuild should be more obvious ;)
<azeem_> ok,_so debuild might also run dh_clean
<jayvee>_yeah, it does
<azeem_> I wonder_why you_think it's dh_clean that unapplies_the patches, and_not anything_else it runs
<jayvee>_I can see it in the_output
<jayvee> bleh, it_doesn't really matter *what* deapplies the_patches
<azeem_>_then what is_your_question?
<jayvee>_the point_being is that_the_'clean' script_is_run while the patches are deapplied
<azeem_>_it's_the other way round
<azeem_> the patches are_deapplied in the clean_target
<azeem_>_or, rather, as a_pre-requisite of the clean target
<jayvee>_yes, exactly
<jayvee> which is perfectly reasonable_for most_use cases
<azeem_>_so what is your use case?
<jayvee> this software has a stupid_bug in it that makes it_run amok when you_run 'python_setup.py_clean', wildly downloading_dependencies
<jayvee>_the bug_has been fixed by the previous packager,_which you_can see in the.diff.gz for the_software
