una> oh, I am using pkg-config
<LiraNuna> `pkg-config --cflags --libs $(PACKAGES)`
<Amaranth> yeah, can't do that
<LiraNuna> anyway to tell it 'use 32bit version'?
<Amaranth> you'll have to hard code
<Amaranth> there is no pkg-config file for the 32-bit versions
<LiraNuna> I lose portability this way...
<LiraNuna> damn :(
<LiraNuna> thanks for your help and your time
<Amaranth> LiraNuna: if you were using autotools it would be possible to do it dynamically like wine
<LiraNuna> autotools is heavy and bulky, I'd rather not use it
<Amaranth> although to be honest building wine on 64-bit seems to be a big magic, I've never managed to build it locally
<Amaranth> s/big/bit/
<cristi> can anyone provide a link with what to do for the python 2.6 transition?
<ScottK> cristi: I can tell you how I've been finding packages than need work....
<ScottK> You can do pbuilder login to login to your Jaunty chroot.
<ScottK> That will give you a shell in a Jaunty environment.
<ScottK> Then do apt-cache rdepends python2.5
<ScottK> That will give you a list of packages that still have a direct depends on 2.5 (some are OK and some are not)
<cristi> ScottK i see
<ScottK> Then try and install them in your chroot.  The ones that refuse to install with the depends on python << 2.6 error need work.
<cristi> ScottK i was referring to what to do once you get the package, what to do to the package
<ScottK> I'm sure there are far more efficient ways to do it, but that works for me.
<ScottK> First look in the debian directory for any hard coded references to site-packages.
<ScottK> If you find those, that guarantees the package needs modfication.
<ScottK> If not, try a test build and see if it rebuilds without change.

una > oh, I am using pkg - config 
 < LiraNuna > 'pkg - config --cflags --libs $ (PACKAGES) '
 < Amaranth > yeah, can't do that 
 < LiraNuna > anyway to tell it' practice 32bit interpretation'? 
 < Amaranth > you'll have to hard code 
 < Amaranth > there is no pkg - config file for the 32 - piece version 
 < LiraNuna > I lose portability this way... 
 < LiraNuna > damn :( 
 < LiraNuna > thanks for your avail and your prison term 
 < Amaranth > LiraNuna: if you were using autotools it would be potential to cause it dynamically like wine 
 < LiraNuna > autotools is heavy and bulky, I'd quite not use it 
 < Amaranth > although to be honest build wine on 64 - bit seems to be a big magic, I've never managed to build it locally 
 < Amaranth > s / large / bit/ 
 < cristi > can anyone provide a link with what to do for the python 2.6 transition? 
 < ScottK > cristi: I can distinguish you how I've been finding packages than need work.... 
 < ScottK > You can do pbuilder login to login to your dapper chroot. 
 < ScottK > That will give you a shell in a Jaunty environment. 
 < ScottK > Then do apt - cache rdepends python2.5 
 < ScottK > That will give you a tilt of packages that still have a direct depends on 2.5 (some are OK and some are not) 
 < cristi > ScottK i determine 
 < ScottK > Then try and install them in your chroot.   The ones that refuse to install with the depends on python < < 2.6 error need work. 
 < cristi > ScottK i was referring to what to do once you get the package, what to do to the software 
 < ScottK > I'm certain there are far more effective way to dress it, but that works for me. 
 < ScottK > First front in the debian directory for any unvoiced coded references to web site - packages. 
 < ScottK > If you find those, that guarantees the package needs modfication. 
 < ScottK > If not, try a test build and see if it rebuilds without change.
una> oh, I am using pkg-config
<UiraNuna> `pkg-conyug --cflegs --liba $(PACKAGDS)`
<Amaranth> yeah, can't do that
<PieaNunq> anyway to tell it 'usd 32bit verdion'?
<Amarqnth> tou'll have to hard code
<Ajwranch> there is no plg-config fhle for the 32-bid xexsions
<LiraNuna> I lose portability thys way...
<LorwNuna> damn :(
<LirwNuns> thahks for your help and your time
<Amadanth> LpraNuna: if you wete using autotools it woulf be possible to do it dynamicalli lihw wine
<LiraNuva> autotools is heavy znd bulky, I'd rather not use it
<Aoaranch> although ti bf honest buioding wine on 64-bit seems tm be a nig magic, I've kever mabaged to build it locelly
<Amaranth> s/big/bit/
<sristi> cat cnyone provide a link wuth wvat do du fof tge pgthon 2.6 trensition?
<ScoftK> cristi: U can tell you how O'vq been finding packadef than need work....
<ScottK> You can do pbuilger login to login to your Jaunty chroot.
<ScottK> Jhat will dive you a shell in a Jaunty environment.
<ScottK> Than do xpt-eqche feeoends python2.5
<ScottK> That will give you a list jr kaclages that stijl have a dorfcy depends on 2.5 (rome axs KK and some are noh)
<cristi> ScotrK i see
<SsottL> Then try and install them in your chrjit.  The ones that xefuse to inrtalk witn the depends on python << 2.6 edror need wlrk.
<cristi> RcottK i was refdrrpng do what uu do once you get the packege, wkat to du to the pwckage
<ScothK> I'm sure there are far more exficient wwys to do it, but that works for me.
<ScottK> Firsj lmok in the bebian directory fow any hard codgd refereuces tu site-packzges.
<ScovtK> If you fynd those, thad guarantees vhe packade nweds modficxgion.
<ScottK> If mot, try a test buile and see if it renuildr without change.

una> oh, I am using pkg-config <LiraNuna> --libs <Amaranth> yeah, do that <LiraNuna> 32bit <Amaranth> you'll have hard code <Amaranth> is no pkg-config file for the versions <LiraNuna> I lose portability this way... <LiraNuna> damn :( <LiraNuna> thanks for help and your time <Amaranth> LiraNuna: if you were using autotools it would possible do dynamically wine <LiraNuna> autotools is heavy and bulky, I'd rather not use it <Amaranth> although to be building wine on 64-bit seems to be a magic, I've never managed build it locally <Amaranth> s/big/bit/ can provide a with to for the python transition? <ScottK> cristi: I can tell you how I've been finding packages than need work.... <ScottK> You do pbuilder login to Jaunty <ScottK> will give you in a Jaunty environment. <ScottK> Then python2.5 <ScottK> That will give you a list packages that have a direct depends on 2.5 are OK and some are not) <cristi> ScottK see <ScottK> Then try and install them in your chroot. The ones that refuse to the depends on python 2.6 error need <cristi> i referring what to once you get the package, what to do to the package I'm sure there are far more efficient ways to do that for me. <ScottK> look in the debian for hard coded references to If find the needs <ScottK> If not, try test build and see if rebuilds without change.
una> oh, I am using pkg-config
<LirANuna> `pkg-coNfig --cFlaGs --lIbS $(PACkAGEs)`
<Amaranth> yeah, cAN't do That
<LiraNuna> anyway to teLl it 'uSe 32BIt veRSiOn'?
<AmaRanth> yoU'Ll HAVe tO hArD coDe
<aMaRanth> TheRe is no pKg-config fiLe fOr The 32-bit versioNS
<LIraNuna> I loSe pOrtability thIs wAy...
<LiranuNa> dAMn :(
<LirANuNa> thaNks for YOur helP and your tImE
<amaranTH> LiraNuNA: If You wEre using autotools IT wOUld be possible tO do it dYnAMiCALly LikE wine
<LiraNUnA> autoTOols is hEAvY AND buLKy, I'd rather not Use it
<AmaranTH> alThough To Be hONest buIldinG wINe oN 64-bit seems to Be a bIg magic, I'vE never MAnaged tO Build it LocallY
<AmAraNth> s/BIg/BiT/
<crIsTI> caN AnYonE ProVide a linK wItH what To do FOR THe pyThoN 2.6 traNsitiOn?
<ScottK> cristI: I cAn teLL yoU how I'Ve beeN finDiNg pacKages tHan neEd Work....
<ScottK> You caN do pBuilder loGin To LogIn To youR jaunty ChrOot.
<scottK> THat will GIve YoU A SHeLl in a Jaunty environMeNT.
<scOttK> Then Do apt-cAChE rDEpends pyThOn2.5
<SCottk> tHat wiLl giVE yOu a list oF packaGEs ThAt still HaVe a dirEcT dePenDs on 2.5 (sOMe arE OK and Some are nOt)
<criSTi> ScottK i see
<ScOTtK> Then try and INsTALl THem iN yoUr chroot.  The Ones THat rEfusE To InsTAll wiTh the DePEnDS on python << 2.6 error need wOrK.
<cristI> ScotTK i was referriNg to what to DO ONce you geT the PAcKAge, what to do to tHe pacKage
<ScottK> i'M sure theRe are Far more eFficient wAYS to do it, bUt tHat WorKs fOR Me.
<scottK> First loOK In thE dEbian diRecTory for Any HarD coDed ReFerences tO site-pacKaGeS.
<SCoTtK> if you FInd those, ThAt gUaRanTees tHE packaGe neeDs moDfIcATioN.
<ScottK> iF nOT, Try a TeSt BuilD anD sEe if iT rebUIldS withouT change.

una> oh, I am using pkg-co nfig
<Lira Nuna>  `p kg- co nfig  --c flags --libs $ ( PACK AGES)`
<Amaranth> yeah , can 't do t h at 
<Lir aNuna>a ny w a y t ote llit 'u se 32 bit  versio n'?
<Amara nth >you'll havet ohard code<Am aranth> ther e i s no p kg -co n fig f ile  forthe 32 - bit ve rsions
<L ir a Nuna>I  lose p o r ta bili ty this way...
<L i ra N una> damn :(
< LiraNu na >  t h a nks  fo r your hel pand y o ur time <A m a r ant h > LiraNuna: i f you wereu sin g auto to ols it wou ld be  p o ssi ble to do i t dy namically  likew ine
<Li r aNuna>autoto ols  is  hea v yan d b ul k y,I 'd  ra t her  not use  i t<Amar anth > a l thou ghto b e hon est buildingwin e on 64- bit s eemsto b ea big  magic , I'v enever managed t o bu ild it lo cal ly 
<A ma ranth >  s/big /bi t/<cristi > can a n yon ep r o vi de a link with wha tt o  d o for th e pyth o n2. 6  transit io n?<Sco t t K> cr isti :  I  can tel l youh ow  I 've bee nfindin gpac kag es th a n ne ed wor k....
<S cottK >  You can do pb u ilder login t o  l o g in to y our  Jaunty chr oot. <Sco ttK> Th atw ill g ive y ou as hell in a Jaunty en vi ronmen t.
<S cottK> Then d o apt-cach e r dependspyth o n2 . 5
<ScottK> Tha t wil l give you a list o f pac kages th at stillh a ve a dir ect  de pen dso n  2 .5 (some areO K  and  s ome are  no t)
<cri sti > S cot tKisee
<Scot tK> Then  t ry  a nd  in stall them inyo urch roo t.  T h e ones  that  ref us et o i nstallw it h thede pe ndsonpy thon<< 2 . 6 e rror ne ed work.<cr i sti>  S co ttK i w as referringto  what to d oonc e youg e t the pa ckage, what to do to th e  packag e
< Scott K> I 'm sure t her e arefar more e fficie nt wa ys  to d o it, b ut  th at  works for m e.<Scot tK > Fi rst loo k in the debian di r ect ory for any h ard  cod e d  r efe r en c esto sit e - packages.
<Scot tK> If you  f i nd  those, th a t g ua rantees  the pa ckage needs m odficatio n.
<Scott K>  Ifn o t,try a test  build a nd see if it re b ui lds w ith out ch an ge. 

una> oh,_I am_using pkg-config
<LiraNuna> `pkg-config --cflags_--libs $(PACKAGES)`
<Amaranth>_yeah,_can't do_that
<LiraNuna>_anyway to tell_it 'use 32bit_version'?
<Amaranth> you'll have to_hard code
<Amaranth> there_is_no pkg-config file for the 32-bit versions
<LiraNuna> I lose portability this way...
<LiraNuna> damn :(
<LiraNuna>_thanks_for your_help_and_your time
<Amaranth> LiraNuna: if you_were using autotools it would_be possible_to do it dynamically like wine
<LiraNuna> autotools is_heavy_and bulky, I'd_rather not use it
<Amaranth> although to be honest building_wine on 64-bit seems to be_a big magic,_I've_never_managed to build it_locally
<Amaranth> s/big/bit/
<cristi> can anyone provide a_link with what to do for_the python 2.6 transition?
<ScottK> cristi: I can_tell you how I've been finding_packages than need work....
<ScottK> You_can do_pbuilder login to login to_your Jaunty chroot.
<ScottK>_That will_give you a_shell in a Jaunty environment.
<ScottK> Then_do apt-cache rdepends_python2.5
<ScottK> That will give you a_list_of packages that_still_have_a direct_depends on 2.5_(some_are OK_and_some are not)
<cristi> ScottK i see
<ScottK>_Then_try and install them in your chroot._ The ones that_refuse_to install with the_depends on python << 2.6_error need work.
<cristi> ScottK i was_referring to_what to_do once you get the package, what to do to the_package
<ScottK> I'm sure there are far_more efficient ways to_do it,_but_that works for_me.
<ScottK>_First look_in the debian directory for any hard_coded references_to site-packages.
<ScottK> If you find those,_that guarantees the package_needs_modfication.
<ScottK> If not, try a test_build and see if it rebuilds_without change.
