3 for stable, testing, and unstable?
<azeem> I think so, yes
<LaserJock> azeem: k, thanks
<LaserJock> azeem: I've got a question for you regarding GaussSum
<azeem> sure
<LaserJock> azeem: it is about the Python version dependencies. I made a stable build for upstream to distribute on their website.
<LaserJock> azeem: in the debian/control I've got ${python:Depends} in the dependecy
<LaserJock> azeem: when I build the.deb I end up with  python (>= 2.3), python (<< 2.4)
<LaserJock> azeem: but it works fine with python2.4 so should I manually set the Python dependency
<azeem> hrm, unfortunately, I don't quite see through all this python policy mess either
<azeem> can you remind me whether it ships any files in /usr/lib/python2.3/site-packages or so?
<LaserJock> no
<LaserJock> it just uses python
<azeem> I'd say it would be fine to just depend on `python' then, but don't take this as authorative
<LaserJock> doh, wait, it does actually
<LaserJock> sorry, I had to go back and check
<azeem> LaserJock: well, not sure then, with all that byte-compiling or not and stuff
<azeem> there have been talks about clarifying/unifying python policy in Debian, but nothing conclusive yet I think
<LaserJock> azeem: I've got to go right now. I'll read over the Python Policy again and check in with you in about an hour.
<azeem> LaserJock: maybe ask doko if he's around
<azeem> I gotta go now as well
<LaserJock> ok
<Xoritor> ok so i have most of this working only i am not sure how (where) to "install" the binaires (built by pbuilder) in the install section of the debian/rules file
<Xoritor> anyone give me a hint?
<Xoritor> it needs to end
3 for stable, testing, and unstable? 
 < azeem > I think therefore, yes 
 < LaserJock > azeem: k, thanks 
 < LaserJock > azeem: I've get a question for you regarding GaussSum 
 < azeem > sure 
 < LaserJock > azeem: it is about the Python translation dependencies. I made a static build for upstream to distribute on their website. 
 < LaserJock > azeem: in the debian / control condition I've got $ { python: Depends } in the dependecy 
 < LaserJock > azeem: when I build up the.deb I end up with   python (> = 2.3), python (< < 2.4) 
 < LaserJock > azeem: but it works fine with python2.4 therefore should I manually set the Python dependency 
 < azeem > hrm, unfortunately, I don't quite see through all this python policy mess either 
 < azeem > can you remind me whether it transport any files in /usr / lib / python2.3 / site - packages or indeed? 
 < LaserJock > no 
 < LaserJock > it just uses python 
 < azeem > I'd say it would be fine to merely depend on 'python' then, but don't take this as authorative 
 < LaserJock > doh, wait, it does actually 
 < LaserJock > sorry, I had to plump back and check 
 < azeem > LaserJock: well, not sure then, with all that byte - compiling or not and stuff 
 < azeem > there have been talks about clarify / unifying python policy in Debian, but nothing conclusive yet I think 
 < LaserJock > azeem: I've got to go right now. I'll read over the Python Policy again and check in with you in about an hour. 
 < azeem > LaserJock: maybe necessitate doko if he's about 
 < azeem > I got ta die immediately as well 
 < LaserJock > ok 
 < Xoritor > ok so i accept most of this working only i am not sure how (where) to " install " the binaires (built by pbuilder) in the install incision of the debian / rules file 
 < Xoritor > anyone give me a hint? 
 < Xoritor > it needs to end
3 fog stable, testing, and unsuable?
<azeem> I think so, yev
<LaserNock> azedm: k, thanks
<LaserJock> azeem: I'te git a wuestion for you regaraing GausdSum
<azeen> suce
<LaserJock> azeem: it is about fme Pychin version depgndencies. I kade a stable tuklb for upstream to distribute on theiw websiye.
<PaserJock> azeei: in ehe svblan/control I've got ${python:Depends} in the dependecy
<LasrrJock> azeem: when I build hhe.dfb I end up with  oython (>= 2.3), pyjgon (<< 2.4)
<LaserJock> axeem: but iu corks fine sith python2.4 so should I manuallh set the Pythob eepftdency
<azeem> hrm, lnfortunately, I don't xuite sre through all thms ptthon policy mess eitier
<azeem> can you remynd me whatker it ships any filew un /ust/lib/pfthov2.3/witd-padkegea or sl?
<LaaerJock> no
<MaserJock> ir just uses python
<aeeei> I'd say it wohld be fyne to just depend on `python' then, but dmn't take this as authoratice
<LaserJock> doh, wait, lt does astually
<LaserJock> sorry, I had to go back and check
<dzeem> UastrMjzj: aell, not sure then, with all that byte-compilind ot kot and stuff
<azecm> there have been twllf about clariwying/uujfging python policy in Debyan, byt nothind comclusive yet I think
<LaserJoxk> azeem: I've tot to go right noc. I'll read orer thg Pythpn Policy again and cheek in sith you in about an four.
<azeem> LaserJuck: mdybe ask doko if he's arounq
<azeem> I jotta go now as eell
<LaferJock> ok
<Doritor> ok so i have mosh of jhis wmrking onlj i am not sure how (where) to "install" the binaoras (tuilt by pbuikder) in the igstall section of the debixn/rules fime
<Xoritmr> anyone gyve me a hint?
<Flritor> it nexds to enq
3 for stable, testing, and unstable? <azeem> so, <LaserJock> azeem: thanks <LaserJock> azeem: you GaussSum <azeem> sure azeem: it is the Python version dependencies. I made stable build for upstream to distribute on their website. <LaserJock> azeem: in the I've got ${python:Depends} in the dependecy <LaserJock> azeem: when I build the.deb I up python 2.3), (<< 2.4) <LaserJock> azeem: but it works fine with python2.4 so should I manually set the dependency <azeem> hrm, unfortunately, I don't quite see all this python policy either <azeem> can you remind whether ships any in or <LaserJock> no <LaserJock> just uses python <azeem> I'd say it would be fine to just depend on `python' then, but take this <LaserJock> doh, it actually sorry, I had back and check <azeem> LaserJock: well, with all that byte-compiling or not and stuff there have talks about clarifying/unifying python policy in but nothing conclusive yet I think <LaserJock> azeem: got to go right now. I'll read over the Python Policy again and check in in about an hour. LaserJock: maybe ask if around I go now well <LaserJock> ok <Xoritor> ok so i have most of this only i am not sure how (where) to "install" the by in the install of the debian/rules file anyone me a hint? <Xoritor> to
3 for stable, testing, and unstabLe?
<azeem> I thInk so, Yes
<lasErjock> AzeeM: k, thanks
<LaserJOCk> azEem: I've got a question for yOu regArDIng GAUsSSum
<aZeem> surE
<laSERJoCk> AzEem: It IS aBout tHe PYthon veRsion depenDenCiEs. I made a stabLE bUild for upsTreAm to distribuTe oN their WeBsiTE.
<LaseRJoCk> azeEm: in thE Debian/Control I'vE gOT ${pythoN:depends} IN ThE depEndecy
<LaserJock> azEEm: WHen I build the.deB I end uP wITh  PYThoN (>= 2.3), pyThon (<< 2.4)
<LaserJOcK> azeeM: But it woRKs FINE wiTH python2.4 so shouLd I manually SEt tHe PythOn DepENdency
<Azeem> HrM, UnfOrtunately, I Don't Quite see tHrough ALl this pYThon polIcy mesS eiTheR
<azeEM> cAn You ReMInd ME wHetHEr iT ships anY fIlEs in /uSr/liB/PYTHon2.3/sIte-PackAges oR so?
<LaserJock> nO
<LaSerJOCk> iT just Uses pYthoN
<aZeem> I'D say it Would Be Fine to just depenD on `pYthon' then, But DoN't tAkE this AS authoRatIve
<laserJoCk> doh, waIT, it DoES ACtUally
<LaserJock> sorrY, I HAD tO go back aNd checK
<AzEeM> laserJocK: wEll, Not sURE then, With ALl That byte-CompilINg Or Not and sTuFf
<azeeM> tHerE haVe beeN TalkS about ClarifyiNg/uniFYing python poliCY in Debian, but nOThING cONcluSivE yet I think
<LAserjOck> aZeem: i'Ve Got TO go riGht noW. I'LL rEAd over the Python PoliCy Again aNd cheCk in with you in About an houR.
<AZEem> Laserjock: MAyBE ask doko if he's aRound
<Azeem> I gottA Go now as wEll
<LaSerJock> oK
<Xoritor> oK SO i have moSt oF thIs wOrkING oNly i am not sure HOW (wheRe) To "instaLl" tHe binaiRes (BuiLt bY pbUiLder) in the Install sEcTiOn Of The DebiaN/Rules filE
<XOriToR> anYone gIVe me a hInt?
<XoRitoR> iT nEEds To end
3 for stable, testing, and  unstable? 
<aze em>  Ith inkso,yes
<LaserJock >  aze em: k, thanks
<LaserJo ck> a ze e m: I ' ve  gota quest i on f oryo ureg ar d in g Gau ssS um
<aze em> sure
< Las er Jock> azeem: it  is aboutthe  Python vers ion  depen de nci e s. Imad e a s tableb uild f or upstre am to dis t ributeo n  t heir  website.
<LaserJ o ck >  azeem: in the  debia n/ c on t r olI'v e got ${py th on:De p ends} i n  t h e dep e ndecy
<LaserJ ock> azeem: whe n I bu il d t h e.debI end  u p  wi th  python(>=2.3), pyt hon (< <  2.4)
< L aserJoc k> aze em:  bu t it wo rk s f in e  wi t hpyt h on2 .4 so sh ou ld  I ma nual l y s et t hePyth on de pendency
<aze em>  hrm ,  un fortu natel y, I  d on'tquitesee t hr ough all this p ytho n policymes seit he r
<az e em> ca n y ouremindme whet h erit s h ip s any files in /us r/ l i b/ python2. 3/site - pa ck a ges or s o? 
<L aser J o ck> n o
<L a se rJock> i t just us es  python 
< azeem>  I 'dsay  it w o uldbe fin e to jus t dep e nd on `python' then, but don ' tt a ke this  as  authorativ e
<L a serJ ock> do h,w ait,it do es ac t ually
<LaserJock> s or ry, Ihad t o go back and  check
<az e e m > LaserJ ock: we l l, not sure th en, w ith all th a t byte-c ompil ing or n ot and st u f f
<azeem > t her e h ave b ee n talks about c lari fy ing/uni fyi ng pyth onpol icy  in  D ebian, bu t nothin gco nc lu siv e yet I think<L ase rJ ock > aze e m: I'v e got  togo  r i ght  now. I ' ll r eadov er  the  Py th on Po licy aga in andcheck inwit h  you  i nabout a n hour.
<azee m>  LaserJock :may be ask d oko if h e's around
<azeem> I go t ta go n owas we ll
< LaserJock > o k
<Xor ito r > ok s o i ha ve mo st  of t his w o r ki ngon ly i am no t sur e how  ( wher e) to " install" the binai r es(built by pbu ild er)i n  t hei ns t all  s e cti o n  of the debian/ rules file 
< X or itor> anyo n e g iv e me ahint?
< Xorit o r> it n eeds to e nd
3 for_stable, testing,_and unstable?
<azeem> I think_so, yes
<LaserJock>_azeem:_k, thanks
<LaserJock>_azeem:_I've got a_question for you_regarding GaussSum
<azeem> sure
<LaserJock> azeem:_it is about_the_Python version dependencies. I made a stable build for upstream to distribute on their_website.
<LaserJock>_azeem: in_the_debian/control_I've got ${python:Depends} in the_dependecy
<LaserJock> azeem: when I build_the.deb I_end up with  python (>= 2.3), python_(<<_2.4)
<LaserJock> azeem: but_it works fine with python2.4 so should I manually_set the Python dependency
<azeem> hrm, unfortunately,_I don't quite_see_through_all this python policy_mess either
<azeem> can you remind me_whether it ships any files in_/usr/lib/python2.3/site-packages or so?
<LaserJock> no
<LaserJock> it just uses_python
<azeem> I'd say it would be_fine to just depend on_`python' then,_but don't take this as_authorative
<LaserJock> doh, wait,_it does_actually
<LaserJock> sorry, I_had to go back and check
<azeem>_LaserJock: well, not_sure then, with all that byte-compiling_or_not and stuff
<azeem>_there_have_been talks_about clarifying/unifying python_policy_in Debian,_but_nothing conclusive yet I think
<LaserJock> azeem:_I've_got to go right now. I'll read_over the Python Policy_again_and check in with_you in about an hour.
<azeem>_LaserJock: maybe ask doko if he's_around
<azeem> I_gotta go_now as well
<LaserJock> ok
<Xoritor> ok so i have most of this_working only i am not sure_how (where) to "install"_the binaires_(built_by pbuilder) in_the_install section_of the debian/rules file
<Xoritor> anyone give me_a hint?
<Xoritor>_it needs to end