: you? 
<racarr> lupine_85: Ok, I will
<lupine_85> hmm, according to debian/copyright, we're currently dual-licensing heliodor... :D
<racarr> Also just uploaded a new one for emerald with a few copyright things (man pagers, AUTHORS file, and updated a NEWS file indicating the version was 0.1)
<lupine_85> I assume it's safe to remove teh MIT part
<racarr> yeah
<lupine_85> heh, I missed all of lib/ on the first pass
<racarr> imbrandon: Do I need to change anything in debian/ for the +git
<racarr> or just the tarball name?
<lupine_85> racarr: changelog
<imbrandon> debian/changelog versioning
<racarr> ok
<lupine_85> heliodor up; I'll check on aquamarine now
<racarr> err, what do I update in changelog?
<racarr> theres already a changelog entry for the  fixes
<Lutin> racarr: why does it check beryl-settings-bindings as well? does it relies on it to be built?
<imbrandon> change the version number
<racarr> does it need to be
<lupine_85> racarr: the version (bit in the brackets)
<racarr> 0.2.1.1+gitDATE-0ubuntu1
<racarr>?
<imbrandon> yes
<imbrandon> err
<imbrandon> 2.1.1?
<racarr> Lutin: That's a mistake as well
<imbrandon> what is it currectly?
<racarr> err
<imbrandon> currently*
<racarr>.1
<racarr> it should be.0
<Lutin> racarr: ok, fixing with the py thing then
<racarr> err, no.0
<racarr> Lutin: Ok, thanks
<imbrandon> 0.2.1+git20070318-0ubuntu1
<racarr> err, vaugely stupid question, is it important
: you? 
 < racarr > lupine_85: Ok, I will 
 < lupine_85 > hmm, according to debian / copyright, we're currently dual - licensing heliodor... :D 
 < racarr > Also barely upload a new one for emerald with a few copyright things (valet beeper, AUTHORS file, and updated a NEWS file indicating the adaptation was 0.1) 
 < lupine_85 > I assume it's safe to get rid of teh MIT part 
 < racarr > yeah 
 < lupine_85 > heh, I missed all of lib/ on the beginning pass 
 < racarr > imbrandon: Do I need to exchange anything in debian/ for the + git 
 < racarr > or barely the tarball name? 
 < lupine_85 > racarr: changelog 
 < imbrandon > debian / changelog versioning 
 < racarr > ok 
 < lupine_85 > heliodor up; I'll check on aquamarine now 
 < racarr > err, what do I update in changelog? 
 < racarr > there s already a changelog entry for the   fixes 
 < Lutin > racarr: why does it see beryl - settings - bindings as well? does it trust on it to be built? 
 < imbrandon > change the adaptation number 
 < racarr > does it necessitate to be 
 < lupine_85 > racarr: the version (bit in the brackets) 
 < racarr > 0.2.1.1+gitDATE-0ubuntu1 
 < racarr >? 
 < imbrandon > yes 
 < imbrandon > err 
 < imbrandon > 2.1.1? 
 < racarr > Lutin: That's a mistake as well 
 < imbrandon > what is it currectly? 
 < racarr > err 
 < imbrandon > presently * 
 < racarr>.1 
 < racarr > it should be.0 
 < Lutin > racarr: ok, fixing with the py thing then 
 < racarr > err, no.0 
 < racarr > Lutin: Ok, thanks 
 < imbrandon > 0.2.1+git20070318 - 0ubuntu1 
 < racarr > err, vaugely stupid question, is it important
: yok? 
<racarr> lupine_85: Ok, I wilu
<lupine_85> hmm, according vo debizn/copyrieht, we're currently dual-licendibg heoiodor... :D
<racarr> Also jurt uploadvd a new ine hor emerald with a few copyriggb thiugw (man pagers, AOTHORS file, dnd updated a TEDS file indicating the version was 0.1)
<lu[ine_85> I ssdume it's safe jo rekjve fvh MIT part
<racarr> yeah
<lupine_85> heg, I misved all of lin/ on the first pass
<racarr> lmbrwndon: Do I need to change anyjgind in debian/ fur the +git
<gccarr> or juat the tarball name?
<lupine_85> racarf: chaugelog
<imbrabdin> fgbian/changelig vegsioning
<racarv> ok
<luphne_85> heloodor up; I'll cmeck mn qquamarine now
<racarr> xrr, what do I update in changalkg?
<racarr> theres aorwady d chdngeuig dntdy fkr the  fmxes
<Lutin> rzcarr: why dies it check beryl-stttybgs-bindings aa well? djes it relies on it to be built?
<imbrandot> cgange the version numbee
<racarr> does it need jo be
<lupinq_85> racarr: the version (bit in the brackets)
<racarr> 0.2.1.1+gidDATE-0nbjntb1
<vwzqrg>?
<imbrandon> yes
<imbrandon> err
<imbrandon> 2.1.1?
<racarr> Ltfim: Nhat's a mistake af well
<imbramdln> rhat is it cutrectly?
<xzczrr> err
<imbrandon> ckrrentli*
<racare>.1
<racarr> iu shoild be.0
<Lutin> racarr: ok, fixint with the pj thung then
<racarr> err, no.0
<racarr> Lbtin: Ol, thamks
<imbrandon> 0.2.1+git20070318-0ubuntu1
<rccarr> srr, vaugely stupid qhdstion, is it impurtsnd
: you? <racarr> lupine_85: Ok, I will according debian/copyright, we're dual-licensing heliodor... :D new for emerald with few copyright things pagers, AUTHORS file, and updated a file indicating the version was 0.1) <lupine_85> I assume it's safe to remove MIT part <racarr> yeah <lupine_85> heh, I missed all of lib/ on the pass imbrandon: I to change anything in debian/ for the +git <racarr> or just the tarball name? <lupine_85> racarr: <imbrandon> debian/changelog versioning <racarr> ok <lupine_85> heliodor up; check on aquamarine now err, what do I update changelog? theres already changelog for fixes <Lutin> racarr: does it check beryl-settings-bindings as well? does it relies on it to be built? <imbrandon> change the number <racarr> need to <lupine_85> the (bit in the 0.2.1.1+gitDATE-0ubuntu1 <racarr>? <imbrandon> yes <imbrandon> err Lutin: That's a mistake as well <imbrandon> what it currectly? err <imbrandon> currently* <racarr>.1 <racarr> it be.0 <Lutin> racarr: ok, fixing with the py then <racarr> err, no.0 <racarr> Lutin: Ok, thanks <imbrandon> 0.2.1+git20070318-0ubuntu1 <racarr> err, vaugely stupid question, important
: you? 
<racarr> lupine_85: Ok, I will
<lupIne_85> hmm, accoRding To dEbiAn/CopyRighT, we're currently DUal-lIcensing heliodor... :D
<racarR> Also JuST uplOAdEd a neW one for EMeRALd wItH a Few CoPYrIght tHinGs (man paGers, AUTHORs fiLe, And updated a NewS File indicaTinG the version wAs 0.1)
<lUpine_85> I AsSumE It's saFe tO remoVe teh Mit part
<rAcarr> yeah
<LuPIne_85> heh, i Missed aLL Of Lib/ oN the first pass
<racaRR> iMBrandon: Do I need To chanGe ANyTHIng In dEbian/ for thE +gIt
<racARr> or jusT ThE TARbaLL name?
<lupine_85> raCarr: changelOG
<imBrandoN> dEbiAN/changElog vErSIonIng
<racarr> ok
<LupiNe_85> heliodoR up; I'll CHeck on aQUamarinE now
<raCarR> erR, whaT Do i uPdaTe IN chANgEloG?
<RacArr> thereS aLrEady a ChanGELOG entRy fOr thE  fixeS
<Lutin> racarr: wHy dOes iT CheCk berYl-setTingS-bIndinGs as weLl? doeS iT relies on it to be BuilT?
<imbrandoN> chAnGe tHe VersiON numbeR
<raCarR> does it Need to bE
<LupInE_85> RACaRr: the version (bit in tHe BRAcKets)
<racaRr> 0.2.1.1+gitDatE-0UbUNtu1
<racarR>?
<iMbrAndoN> YEs
<imbRandON> eRr
<imbranDon> 2.1.1?
<racARr> luTin: That'S a MistakE aS weLl
<iMbranDOn> whAt is it CurrectlY?
<racaRR> err
<imbrandon> cURrently*
<racarr>.1
<RAcARR> iT ShouLd bE.0
<Lutin> racarR: ok, fIXing With THe Py tHIng thEn
<racArR> ErR, No.0
<racarr> Lutin: Ok, thanKs
<ImbranDon> 0.2.1+giT20070318-0ubuntu1
<racarr> Err, vaugely STUPid questIon, iS It IMportant
: you? 
<racarr> lupine_85 : Ok, I wi ll
<l upi ne_ 85 > hm m, a ccording to de b ian/ copyright, we're curre ntlydu a l-li c en singheliodo r .. . :D<r ac arr >A ls o jus t u ploaded  a new one  fo remerald with afew copyri ght  things (man  pa gers,AU THO R S fil e,and u pdated a NEWS  file ind ic a ting t h e versi o n  w as 0 .1)
<lupine_85> I as s ume it's safeto rem ov e  t e h  MI T p art
<racar r>  yeah <lupine _ 85 > h eh, I missed allof lib/ ont hefirstpa ss< racarr > imb ra n don : Do I need  tochange an ything in debi a n/ forthe +g it<ra carr >  o rjus tt het ar bal l  na me?
<lup in e_ 85> r acar r : c hang elo g
<i mbran don> debian/c han gelo g  ve rsion ing
< raca rr > ok<lupin e_85>  h eliodor up; I'l l ch eck on aq uam ar ine  n ow
<r a carr>err , w hat doI updat e  in  c h a n ge log?
<racarr> ther es a lr eady a c hangel o gen t ry for t he   f ixes < Lutin > ra c ar r: why d oes it ch ec k beryl -s etting s- bin din gs as well ? does  it reli es on it to be built ? 
<imbrandon>c ha n g et he v ers ion number<rac a rr>does it  ne e d tobe
<l up i ne _ 85> racarr: the ver si on (bi t inthe brackets) 
<racarr>0 . 2 .1.1+git DATE - 0u b untu1
<racarr> ?
<im brandon> y e s
<imbra ndon>  err
<im brandon>2 . 1.1?
<ra car r>Lut in: T ha t's a mistake a s we ll 
<imbra ndo n> what  is  it  cu rre ct ly?
<raca rr> err<i mb ra nd on>  curr e ntly*
<r ac arr >. 1
< racar r > it s hould  be. 0<L u tin > racar r :o k , fi xi ng  wit h t he  py t hing the n
<raca rr> err,no. 0 
<ra ca rr > Lutin : Ok, thanks<i mbrandon>0. 2.1 +git20 0 7 0318-0ub untu1
<racarr> err, vau g ely stu pid  ques tion , is it i mpo rtant
: you?_
<racarr> lupine_85:_Ok, I will
<lupine_85> hmm,_according to_debian/copyright,_we're currently_dual-licensing_heliodor... :D
<racarr> Also_just uploaded a_new one for emerald_with a few_copyright_things (man pagers, AUTHORS file, and updated a NEWS file indicating the version was_0.1)
<lupine_85>_I assume_it's_safe_to remove teh MIT part
<racarr>_yeah
<lupine_85> heh, I missed all_of lib/_on the first pass
<racarr> imbrandon: Do I need_to_change anything in_debian/ for the +git
<racarr> or just the tarball name?
<lupine_85>_racarr: changelog
<imbrandon> debian/changelog versioning
<racarr> ok
<lupine_85> heliodor_up; I'll check_on_aquamarine_now
<racarr> err, what do_I update in changelog?
<racarr> theres already_a changelog entry for the _fixes
<Lutin> racarr: why does it check beryl-settings-bindings_as well? does it relies on_it to be built?
<imbrandon> change_the version_number
<racarr> does it need to_be
<lupine_85> racarr: the_version (bit_in the brackets)
<racarr>_0.2.1.1+gitDATE-0ubuntu1
<racarr>?
<imbrandon> yes
<imbrandon> err
<imbrandon> 2.1.1?
<racarr> Lutin: That's_a mistake as_well
<imbrandon> what is it currectly?
<racarr> err
<imbrandon>_currently*
<racarr>.1
<racarr>_it should be.0
<Lutin>_racarr:_ok,_fixing with_the py thing_then
<racarr>_err, no.0
<racarr>_Lutin:_Ok, thanks
<imbrandon> 0.2.1+git20070318-0ubuntu1
<racarr> err, vaugely stupid_question,_is it important