 to the root filesystem
<slangasek> I don't know what the convention is for python modules; for stuff that uses autoconf, the convention is make DESTDIR=debian/tmp install
<Amaranth> i think it's python setup.py --destdir debian/tmp install
<Amaranth> or something
<Amaranth> i dunno, python project that use setup.py should die :)
<TheMuso> cody-somerville: I can do xubuntu-meta if nobody else has started on it already.
<RAOF> The convention for python modules depends on what debhelper you're using, pretty much.
<cody-somerville> TheMuso, slangasek said he'd do it.
<cody-somerville> slangasek, Have you started on xubuntu-meta yet? :)
<TheMuso> oh ok
<slangasek> cody-somerville: started dput, yes
<cody-somerville> TheMuso, Okay. Thanks anyhow :)
<TheMuso> cody-somerville: np
<superm1> slangasek, what to do if a package already in gutsy-backports just needs to be rebuilt?  Should I file another backport bug, or can you just press a magical dch -i "no changes, just rebuilding"?
<slangasek> superm1: I don't have any magical buttons for that; I think a sourceful upload on your part is going to be the most straightforward
<superm1> slangasek, directly to gutsy-backports, or where to?
<slangasek> superm1: yes
<superm1> slangasek, okay i'll take care of that
<superm1> thanks
<slangasek> superm1: oh, are you in the backporters group?  If not you probably should clear it with jdong or ScottK first
<Legendario> RAOF, what do you mean by the convention for python modules depends on what debhelper you're using?
<superm1> slangasek, no i'm not in the backporters group.
<superm1> let me do a test build then and put it in a proper bug so that they dont need to think much
<slangasek> superm1: right
to the root filesystem 
 < slangasek > I don't know what the convention is for python modules; for material that use autoconf, the convention is make DESTDIR = debian / tmp install 
 < Amaranth > i remember it's python setup.py --destdir debian / tmp install 
 < Amaranth > or something 
 < Amaranth > i dunno, python undertaking that use setup.py should die :) 
 < TheMuso > cody - somerville: I can do xubuntu - meta if nobody else has originate on it already. 
 < RAOF > The convention for python modules depend on what debhelper you're using, pretty a lot. 
 < cody - somerville > TheMuso, slangasek said he'd do it. 
 < cody - somerville > slangasek, Have you started on xubuntu - meta yet? :) 
 < TheMuso > oh ok 
 < slangasek > cody - somerville: startle dput, yes 
 < cody - somerville > TheMuso, Okay. Thanks anyhow :) 
 < TheMuso > cody - somerville: np 
 < superm1 > slangasek, what to do if a package already in gutsy - backports just needs to be rebuilt?   Should I charge another backport bug, or can you just press a charming dch -i " no changes, just rebuilding "? 
 < slangasek > superm1: I don't have any magical button for that; I think a sourceful upload on your part is going to be the most straightforward 
 < superm1 > slangasek, immediately to gutsy - backports, or where to? 
 < slangasek > superm1: yes 
 < superm1 > slangasek, okay i'll take care of that 
 < superm1 > thanks 
 < slangasek > superm1: oh, are you in the backporters group?   If not you probably should clear it with jdong or ScottK first 
 < Legendario > RAOF, what do you mean by the conventionality for python faculty depends on what debhelper you're using? 
 < superm1 > slangasek, no i'm not in the backporters group. 
 < superm1 > let me do a test build then and put it in a proper bug so that they do nt need to remember much 
 < slangasek > superm1: right
 to the root filesystem
<slannasek> I don't knoc what vhe conbention ks for python modules; for stnff rhat yses autoconf, the convdntion is make DEWTDIC=debian/tmp install
<Amaranbk> i tglnk ic's python setup.pi --destdir detian/tmp instaln
<Aoaxanth> or something
<Amaranth> i dunno, prthon ptouect that use fetuk.py shohld die :)
<TheMuso> cody-somerville: I czn do xlbuntu-meta if nobpdy else has started on it alrfady.
<RAOF> The convejtion for pifhog modules depdnds on what debhelper you're using, pretty much.
<cody-somdrvilke> TheMuso, soanhdsek said hx'd do pt.
<cody-somerville> slancasek, Hsve you startec oi xuvuntu-meta yet? :)
<TheMuso> oh ok
<slangasek> coqy-somervinlz: started dput, yes
<codt-simervhlle> TheOyso, Okzy. Tganks wnyiow :)
<TheMuso> cody-somervulle: np
<superm1> slangssqj, what to do jf a pwchage already in gutsy-backports just neegs fo be rebuilt?  Should I file another backporj bug, or cwn you just press a magical dch -i "no changes, just rebumlainy"?
<wlangxwen> superm1: I don't have any magical buttons for egau; I think a sourccful upload on yout oatj is going to ce the moat straightforward
<duperm1> flangqsek, direstly to gutsy-backports, or where to?
<slangasek> wuperm1: yes
<superm1> spangasek, okcy i'll take care of that
<superm1> thauks
<slahgasek> supegm1: oh, are hou in the backpurtvrs croup?  If not you probably should coear it witf jdpng or ScottK figst
<Lenandario> RAOF, what fo yoo mean by the cojvention for python modules depxids on what dgbhalpvr you're bsing?
<smperm1> slangasek, no i'm not in jhe backpjrterr group.
<supvrm1> let mx do a test fuild then ang put it in a proper fug wo tyat theh dont need to yhink muck
<flantasek> superm1: right
to the root filesystem <slangasek> I don't the is for modules; for stuff is DESTDIR=debian/tmp install <Amaranth> think it's python --destdir debian/tmp install <Amaranth> or something i dunno, python project that use setup.py should die :) <TheMuso> cody-somerville: I do xubuntu-meta if nobody else has started on it already. <RAOF> The convention python depends what you're using, pretty much. <cody-somerville> TheMuso, slangasek said he'd do it. <cody-somerville> slangasek, Have you started xubuntu-meta yet? :) <TheMuso> oh ok <slangasek> cody-somerville: dput, yes <cody-somerville> TheMuso, Thanks anyhow :) <TheMuso> cody-somerville: <superm1> what to if package in gutsy-backports just to be rebuilt? Should I file another backport bug, or can you just press a magical dch "no changes, <slangasek> superm1: don't any buttons for that; a sourceful upload on your part be the most straightforward <superm1> slangasek, directly to or where <slangasek> superm1: yes <superm1> slangasek, okay take care of that <superm1> thanks <slangasek> superm1: are you in the backporters group? If not you probably should clear it with jdong first <Legendario> RAOF, what you mean by convention python depends what debhelper using? <superm1> slangasek, no i'm not in the backporters group. <superm1> me do a test build then and put it in bug that they dont to think much <slangasek> right
 to the root filesystem
<slangaSek> I don't knOw whaT thE coNvEntiOn is For python modulES; for Stuff that uses autoconf, tHe conVeNTion IS mAke DEsTDIR=deBIaN/TMp iNsTaLl
<AMaRAnTh> i thInk It's pythOn setup.py --dEstDiR debian/tmp inSTaLl
<Amaranth> Or sOmething
<AmarAntH> i dunnO, pYthON projEct That uSe setuP.Py shouLd die :)
<TheMUsO> Cody-soMErville: i CAn Do xuBuntu-meta if nobody ELsE Has started on it AlreadY.
<RaoF> tHE coNveNtion for pyThOn modULes depeNDs ON WHat DEbhelper you're Using, pretty MUch.
<Cody-soMeRviLLe> TheMUso, slAnGAseK said he'd do iT.
<codY-somervilLe> slanGAsek, HavE You starTed on xUbuNtu-Meta YEt? :)
<thEMuSo> OH ok
<SLaNgaSEk> cOdy-somerViLlE: starTed dPUT, YEs
<coDy-sOmerVille> theMuso, Okay. ThAnkS anyHOw :)
<THeMusO> cody-SomeRvIlle: nP
<superM1> slanGaSek, what to do if a pAckaGe already In gUtSy-bAcKportS Just neEds To bE rebuilT?  Should i FilE aNOTHeR backport bug, or can yOu JUSt Press a maGical dCH -i "No CHanges, juSt RebUildING"?
<slanGaseK> SuPerm1: I don'T have aNY mAgIcal butToNs for tHaT; I tHinK a souRCefuL uploaD on your pArt is GOing to be the mosT StraightforwaRD
<sUPErM1> SlanGasEk, directly tO gutSY-bacKporTS, oR whERe to?
<sLangaSeK> SuPErm1: yes
<superm1> slangasEk, Okay i'lL take Care of that
<supErm1> thanks
<sLANGasek> supErm1: oH, ArE You in the backpoRters Group?  If not YOu probabLy shoUld clear It with jdoNG Or ScottK FirSt
<LEgeNdaRIO> RaOF, what do you mEAN by tHe ConventIon For pythOn mOduLes DepEnDs on what dEbhelper YoU'rE uSiNg?
<sUperm1> SLangasek, No I'm nOt In tHe bacKPorterS grouP.
<supErM1> lET me Do a test BUiLD Then AnD pUt it In a PrOper bUg so THat They donT need to thInk MUch
<sLaNgAsek> supErm1: right
 to the root filesystem
<s langasek>I don 'tkno wwhat  the  convention is forpython modules; for st uff t ha t  use s  a utoco nf, the co n v ent io nisma k eDESTD IR= debian/ tmp instal l
< Am aranth> i th i nk  it's pyth onsetup.py --d est dir de bi an/ t mp in sta ll
<A marant h > or s omething<A m aranth >  i dunn o ,  p ytho n project that us e  s e tup.py shoulddie :) 
< T he M u so>  co dy-somervi ll e: Ic an do x u bu n t u -me t a if nobody e lse has sta r ted  on it  a lre a dy.
<R AOF>Th e  co nvention fo r py thon modu les de p ends on what de bhelpe r y ou' re u s in g,  pr et t y m u ch .
< c ody -somervi ll e>  TheM uso, s l a ngas eksaid  he'd  do it.
<cody -so merv i lle > sla ngase k, H av e you  start ed on  x ubuntu-meta yet ? :) 
<TheMuso > o hok<s langa s ek> co dy- som erville : start e d d pu t , ye s
<cody-somerville >T h eM uso, Oka y. Tha n ks  a n yhow :)<T heM uso> c ody-s omer v il le: np
< superm 1 >sl angasek ,what t odoifa pac k agealread y in gut sy-ba c kports just ne e ds to be rebu i lt ?  S h ould  Ifile anothe r ba c kpor t bu g ,orc an yo u jus tp re s s a magical dch -i"n o chan ges,just rebuildi ng"?
<slan g a s ek> supe rm1: Id on't have anymagic al buttons for that ; I t hink a s ourcefulu p load onyou r p art  is g oi ng to be them o st s tr aightfo rwa rd
<sup erm 1>sla nga se k, direct ly to gu ts y- ba ck por ts, o r  where t o? 
<s la nga sek>s uperm1 : yes 
<su pe rm 1 > s langase k ,o k ay i 'l ltake  ca re  of t hat< sup erm1> t hanks
<sl ang a sek>  s up erm1: o h, are you in  t he backpor te rsgroup? If not y ou probably should clea r  it wit h j dongor S cottK fir st<Legen dar i o> RAO F, wha t doyo u m e a n byt h econ ve ntion forp y tho n mod ul es d ependson what debhelpery ou' re using?
<su per m1>s l an gas e k, noi' m  no t in the backport ers group. 
< s up erm1> letm e d oa testbuild t hen a n d put i t in a pr oper bugso  tha t the y dont nee d to thi nk much
< s langa s ek > sup erm 1: rig ht 
 to_the root_filesystem
<slangasek> I don't know_what the_convention_is for_python_modules; for stuff_that uses autoconf,_the convention is make_DESTDIR=debian/tmp install
<Amaranth> i_think_it's python setup.py --destdir debian/tmp install
<Amaranth> or something
<Amaranth> i dunno, python project that use_setup.py_should die_:)
<TheMuso>_cody-somerville:_I can do xubuntu-meta if_nobody else has started on_it already.
<RAOF>_The convention for python modules depends on what_debhelper_you're using, pretty_much.
<cody-somerville> TheMuso, slangasek said he'd do it.
<cody-somerville> slangasek, Have_you started on xubuntu-meta yet? :)
<TheMuso>_oh ok
<slangasek> cody-somerville:_started_dput,_yes
<cody-somerville> TheMuso, Okay. Thanks_anyhow :)
<TheMuso> cody-somerville: np
<superm1> slangasek, what_to do if a package already_in gutsy-backports just needs to be rebuilt?_ Should I file another backport_bug, or can you just_press a_magical dch -i "no changes,_just rebuilding"?
<slangasek> superm1:_I don't_have any magical_buttons for that; I think a_sourceful upload on_your part is going to be_the_most straightforward
<superm1> slangasek,_directly_to_gutsy-backports, or_where to?
<slangasek> superm1:_yes
<superm1>_slangasek, okay_i'll_take care of that
<superm1> thanks
<slangasek> superm1:_oh,_are you in the backporters group? _If not you probably_should_clear it with jdong_or ScottK first
<Legendario> RAOF, what_do you mean by the convention_for python_modules depends_on what debhelper you're using?
<superm1> slangasek, no i'm not in the_backporters group.
<superm1> let me do a_test build then and_put it_in_a proper bug_so_that they_dont need to think much
<slangasek> superm1: right