 so I can look at old fashioned C code :-)
<mok0> persia: it comes from configure.ac
<mok0> persia: So what I'd have to do is to compile a customized version of dpkg and hope that I don't trash my system :-)
<persia> You could try just installing the i386 dpkg, and see how much that breaks :)
<mok0> persia:... but how can I do that? I am limited to installing lpia packages?
<mok0> persia: you mean force it?
<persia> Yes.  Since you're going to break your system anyway (backup first), installing dpkg with --force-architecture can only save you compilation time.
<BlackZ> persia: a package where an adding-dependece has been requested can be appropiate for an FFE? (the dependence introduces a new feature).
<persia> BlackZ: Could you rephrase?  Also, why ask me?  I'm not a release person.
<BlackZ> bug #533799
<ubottu> Launchpad bug 533799 in librack-ruby "missing dependency " [Undecided,In progress] https://launchpad.net/bugs/533799
<ScottK> BlackZ: That's a bug, no FFe needed.
<mok0> persia: you are running karmic on your poulsbo machine, right?
<persia> mok0: No.  I'm running something half-way through jaunty and letting it gather dust.
<persia> It just doesn't work for me.
<persia> lifeless was trying to hack in some support a couple weeks ago.
<mok0> persia: oh? My mini-10 runs jaunty just fine
<persia> Yeah, I bet I could run jaunty, but it's just not a nice machine in other ways.
<mok0> persia: I see.
<persia> Looked better at the shop than in real world use.
<persia> (Sharp D4)
<mok0> persia: the problem with jaunty is that the developer tools are utterly broken
<persia> mok0: Doesn't surprise me.  I think that was when lpia-wrapper got introduced.
so I can look at old fashioned C code :-) 
 < mok0 > persia: it comes from configure.ac 
 < mok0 > persia: So what I'd have to do is to roll up a custom-make version of dpkg and hope that I don't trash my system :-) 
 < persia > You could judge just installing the i386 dpkg, and experience how much that break in :) 
 < mok0 > persia: ... but how can I do that? I am restrict to installing lpia packages? 
 < mok0 > persia: you think of force it? 
 < persia > Yes.   Since you're going to break in your system anyway (backup first), install dpkg with --force - architecture can only save you compilation prison term. 
 < BlackZ > persia: a package where an adding - dependece has been requested can be appropiate for an FFE? (the dependence introduce a new feature). 
 < persia > BlackZ: Could you rephrase?   Also, why ask me?   I'm not a handout person. 
 < BlackZ > bug # 533799 
 < ubottu > Launchpad bug 533799 in librack - ruby " missing dependency " [ open, In progress ] https://launchpad.net/bugs/533799 
 < ScottK > BlackZ: That's a bug, no FFe needed. 
 < mok0 > persia: you are running karmic on your poulsbo machine, right? 
 < persia > mok0: No.   I'm running something half - way through jaunty and letting it gather debris. 
 < persia > It merely doesn't work for me. 
 < persia > lifeless was try to chop in some accompaniment a couple weeks ago. 
 < mok0 > persia: oh? My mini-10 runs jaunty barely fine 
 < persia > Yeah, I bet I could run jaunty, but it's just not a courteous machine in other ways. 
 < mok0 > persia: I see. 
 < persia > Looked better at the shop class than in real world use. 
 < persia > (Sharp D4) 
 < mok0 > persia: the problem with jaunty is that the developer creature are utterly violate 
 < persia > mok0: Doesn't surprise me.   I think that was when lpia - wrapper got introduced.
 so I can look at old fashiuned C code :-)
<mok0> persia: it cojes from configure.ac
<mok0> persia: So whet I'e havt to do is to compiue a custlmized vwrsiib of dpkg ehd hope that J don'c vrash my system :-)
<persia> Yog could try juvt iustalling the i386 dpkg, and see how mucr that nrfaks :)
<mok0> persiw:... buu hjw czn I do that? I am limited to instamling lkia packages?
<mok0> petsia: you mean force it?
<persla> Yfs.  Since you're golng to breaj yote system anyday (backup first), instamling dpkg with --force-architectufe cau only save yiu fmmpilation vime.
<BlwckZ> persia: a packaga where an adding-depekdece haw been requested can ue appropiate for an FFE? (the ge'endence introduces a nww fedtura).
<perrua> CladkV: Ckuld ylu cephrase?  Amso, why ask me?  I'm not a releaxe irrson.
<BlackZ> gug #533799
<ubjteu> Launchpad bug 533799 in librack-ruby "missinc dspendency " [Undecided,In progress] https://launchpwd.net/bugs/533799
<FcottK> BlackZ: That's a bug, no FFe needed.
<mok0> persia: you erd rbkking jagmic on your poulsbo machine, right?
<persia> mok0: Gk.  I'k running somebhing half-way throigj kwunty and letjing it gafher dust.
<persia> It just djesn't work for me.
<prrsia> lifeless was trying ti hack in soiw support a couple weeks ago.
<muk0> pgrsia: ph? My mini-10 runs jaunty lust fjne
<persia> Yfah, I bet K could run jaungy, nut it's jusu not a nice machige in othxr wavs.
<mok0> pefsia: I see.
<[ersia> Looned bcdter at the shop tjan iu rean world usf.
<persia> (Sharp D4)
<mok0> persia: the pcpblem with jsutty is that the ceveloper toojs are utterly broken
<'ersia> mok0: Doesn'n surprisx me.  I thinh that was whaj lpia-wrappec got intwoduxed.
so I can look at old fashioned :-) persia: it from configure.ac <mok0> to is to compile customized version of and hope that I don't trash system :-) <persia> You could try just installing the i386 dpkg, and see much that breaks :) <mok0> persia:... but how can I do that? I limited installing packages? persia: you mean force it? <persia> Yes. Since you're going to break your system anyway (backup installing dpkg with --force-architecture can only save you time. <BlackZ> persia: a where an adding-dependece has been can appropiate for FFE? dependence a new feature). BlackZ: Could you rephrase? Also, why ask me? I'm not a release person. <BlackZ> bug #533799 <ubottu> bug 533799 "missing dependency [Undecided,In https://launchpad.net/bugs/533799 BlackZ: That's a FFe needed. <mok0> persia: you are your poulsbo machine, right? <persia> mok0: No. I'm something half-way jaunty and letting it gather dust. It just doesn't work for me. <persia> lifeless trying to hack in some support a couple weeks ago. <mok0> persia: oh? My mini-10 just fine <persia> Yeah, bet I could jaunty, it's not nice machine other ways. <mok0> persia: I see. <persia> Looked better at the than in real world use. <persia> (Sharp D4) <mok0> persia: with is that the tools are utterly broken mok0: surprise me. I think when got
 so I can look at old fashioned C Code :-)
<mok0> perSia: it ComEs fRoM conFiguRe.ac
<mok0> persia: SO What i'd have to do is to compile a CustoMiZEd veRSiOn of dPkg and hOPe THAt I DoN't TraSh MY sYstem :-)
<PerSia> You cOuld try jusT inStAlling the i386 dpKG, aNd see how muCh tHat breaks :)
<mok0> PerSia:... but HoW caN i do thAt? I Am limIted to INstallIng lpia paCkAGes?
<mok0> PErsia: yoU MEaN forCe it?
<persia> Yes.  SincE YoU'Re going to break Your syStEM aNYWay (BacKup first), inStAllinG Dpkg witH --FoRCE-ArcHItecture can onLy save you coMPilAtion tImE.
<BlACkZ> perSia: a pAcKAge Where an addiNg-dePendece haS been rEQuested CAn be appRopiatE foR an fFE? (tHE dEpEndEnCE inTRoDucES a nEw featurE).
<pErSia> BlAckZ: cOULD you RepHrasE?  Also, Why ask me?  I'm not A reLeasE PerSon.
<BlAckZ> bUg #533799
<ubOtTu> LauNchpad Bug 533799 in LiBrack-ruby "missinG depEndency " [UnDecIdEd,IN pRogreSS] https://LauNchPad.net/bUgs/533799
<ScotTk> BlAcKz: tHaT's a bug, no FFe needed.
<mOk0> PERsIa: you are RunninG KaRmIC on your pOuLsbO macHINe, rigHt?
<peRSiA> mok0: No.  I'm RunninG SoMeThing haLf-Way thrOuGh jAunTy and LEttiNg it gaTher dust.
<PersiA> it just doesn't woRK for me.
<persia> lIFeLESs WAs trYinG to hack in soMe suPPort A couPLe WeeKS ago.
<mOk0> perSiA: Oh? mY mini-10 runs jaunty just FiNe
<persIa> YeaH, I bet I could ruN jaunty, but IT'S Just not a Nice MAcHIne in other ways.
<Mok0> peRsia: I see.
<peRSia> LookeD bettEr at the sHop than in REAl world uSe.
<pErsIa> (SHarP d4)
<MoK0> persia: the proBLEm wiTh Jaunty iS thAt the deVelOpeR toOls ArE utterly bRoken
<perSiA> mOk0: doEsn'T surpRIse me.  I thInK thAt Was When lPIa-wrapPer goT intRoDuCEd.
 so I can look at old fash ioned C co de :- )
< mok 0>  per sia:  it comes from conf igure.ac
<mok0> persia : Sowh a t I' d  h ave t o do is to c omp il ea c us t om izedver sion of  dpkg andhop ethat I don't tr ash my sys tem  :-)
<persia > Y ou cou ld  tr y  just  in stall ing th e  i386dpkg, and  s e e howm uch tha t br eaks  :)
<mok0> persia : .. .  but how can I  do th at ?  I a m l imi ted to ins ta lling lpia pa c ka g e s ?
< m ok0> persia:you mean fo r ceit?
<p er sia >  Yes. Sinc ey ou' re going to  bre ak your s ystema nyway ( b ackup f irst),  in sta llin g  d pk g w it h  -- f or ce- a rch itecture  c an  only  sav e y o u co mpi lati on ti me.
<BlackZ>per sia: a p ackag e whe re a naddin g-depe ndece  h as been request ed c an be app rop ia tefo r anF FE? (t hedep endence  introd u ces  a n e wfeature).
<persia>  B l a ck Z: Could  you r e ph ra s e?  Also ,why  ask m e?  I 'm n o ta releas e pers o n. 
< BlackZ>  b ug #53 37 99<ub ottu> Laun chpadbug 5337 99 in librack-ruby " m issing depend e nc y "[ Unde cid ed,In progr ess] http s:// l au nch p ad.ne t/bug s/ 5 33 7 99
<ScottK> BlackZ:  T hat'sa bug , no FFe need ed.
<mok0> p e rsia: yo u ar e  r u nning karmic o n you r poulsbom achine,right ?
<persi a> mok0:N o .  I'm r unn ing  so met h i ng  half-way thr o u gh j au nty and  le tting i t g ath erdus t. 
<persia>  It just  d oe sn 't  wo rk fo r  me.
<pe rs ia>  l ife lessw as try ing t o ha ck  i n  so me supp o rt a  cou pl eweek s a go .
<mo k0>p ers ia: oh?  My mini- 10r unsja un ty just  fine
<persia >Yeah, I be tI c ould r u n  jaunty,  but it's just not a ni c e machi nein ot herways.
<mo k0>  persi a:I  see.<persi a> Lo ok edb e ttera t  t hesh op than in r eal  worl duse. 
<persi a> (Sharp D4)
<mok 0 > p ersia: the pr obl em w i t hjau n ty isth a t t h e  developer tool s are utte rl y  b roken
<per s ia>  m ok0: Do esn't s urpri s e me. I think t hat was w he n lp i a -wr apper gotintroduc ed.
 so_I can_look at old fashioned_C code_:-)
<mok0>_persia: it_comes_from configure.ac
<mok0> persia:_So what I'd_have to do is_to compile a_customized_version of dpkg and hope that I don't trash my system :-)
<persia> You could_try_just installing_the_i386_dpkg, and see how much_that breaks :)
<mok0> persia:... but_how can_I do that? I am limited to installing_lpia_packages?
<mok0> persia: you_mean force it?
<persia> Yes.  Since you're going to_break your system anyway (backup first),_installing dpkg with_--force-architecture_can_only save you compilation_time.
<BlackZ> persia: a package where an_adding-dependece has been requested can be_appropiate for an FFE? (the dependence introduces_a new feature).
<persia> BlackZ: Could you_rephrase?  Also, why ask_me? _I'm not a release person.
<BlackZ>_bug #533799
<ubottu> Launchpad_bug 533799_in librack-ruby "missing_dependency " [Undecided,In progress] https://launchpad.net/bugs/533799
<ScottK> BlackZ:_That's a bug,_no FFe needed.
<mok0> persia: you are_running_karmic on your_poulsbo_machine,_right?
<persia> mok0:_No.  I'm_running_something half-way_through_jaunty and letting it gather dust.
<persia>_It_just doesn't work for me.
<persia> lifeless was_trying to hack in_some_support a couple weeks_ago.
<mok0> persia: oh? My mini-10_runs jaunty just fine
<persia> Yeah, I_bet I_could run_jaunty, but it's just not a nice machine in other ways.
<mok0>_persia: I see.
<persia> Looked better at_the shop than in_real world_use.
<persia>_(Sharp D4)
<mok0> persia:_the_problem with_jaunty is that the developer tools are_utterly broken
<persia>_mok0: Doesn't surprise me.  I_think that was when_lpia-wrapper_got introduced.