that needs to be removed from configure then
<racarr> imbrandon: And reading the python policy
<Lutin> imbrandon: I can update the package to make it comply with th python policy if you want
<imbrandon> Lutin, that would be great
<Lutin> imbrandon: k, doing it right now then
<racarr> Lutin: Yes, I know little about this, so that would be great
<racarr> Lutin: Could you do the same for beryl-settings-simple? also on REVU, packaging is nearly identical
<imbrandon> Lutin, your in the REVU ring right? just upload it over the old ones and let us know
<Lutin> imbrandon: upID 4667 on revu, right?
<imbrandon> yes
<Lutin> o
<Lutin> k
<imbrandon> 4667
<racarr> Lutin: Once I see how you fix beryl-settings I can probably actually work out how to fix beryl-settings-simple
<imbrandon> racarr, wanna fix the configure while he changes that >
<racarr> imbrandon: While he does that want to look at emerald?
<racarr> imbrandon: err, I'll wait until after he fixes that to fix the configure
<racarr> imbrandon: So changes don't get written over
<Lutin> racarr: ok
<imbrandon> racarr, ok
<imbrandon> lets do -bindings next
<racarr> ok
<racarr> bindings SHOULD be good
<racarr> spent a while on it somewhere around midnight
<racarr> because it was pulling in every single X library for a build dependency because we had broken pkgconfig files
<racarr> heh
<imbrandon> yea looking it over its alot better than the others
<racarr> not sure if it complies with the python policy
<imbrandon> yea it does
<imbrandon> i was just looking at that
<racarr> ah, convenient
<racarr> ok...I would give that a test build then
<geser> racarr: for libemeraldengine-dev (or any other
that needs to be removed from configure then 
 < racarr > imbrandon: And reading the python policy 
 < Lutin > imbrandon: I can update the package to seduce it comply with th python policy if you desire 
 < imbrandon > Lutin, that would be great 
 < Lutin > imbrandon: k, do it mighty now then 
 < racarr > Lutin: Yes, I know small about this, so that would be great 
 < racarr > Lutin: Could you do the like for beryl - mise en scene - simple? besides on REVU, packaging is nearly identical 
 < imbrandon > Lutin, your in the REVU ring right? barely upload it over the old ones and let us know 
 < Lutin > imbrandon: upID 4667 on revu, right? 
 < imbrandon > yes 
 < Lutin > oxygen 
 < Lutin > k 
 < imbrandon > 4667 
 < racarr > Lutin: Once I see how you fix beryl - settings I can credibly actually work out how to fix beryl - settings - simple 
 < imbrandon > racarr, wanna fix the configure while he change that > 
 < racarr > imbrandon: While he does that want to look at emerald? 
 < racarr > imbrandon: err, I'll wait until after he fixes that to fix the configure 
 < racarr > imbrandon: So change don't get written over 
 < Lutin > racarr: ok 
 < imbrandon > racarr, ok 
 < imbrandon > lets do -bindings next 
 < racarr > ok 
 < racarr > bindings SHOULD be effective 
 < racarr > spent a while on it somewhere around midnight 
 < racarr > because it was pulling in every single X library for a build dependency because we had broken pkgconfig files 
 < racarr > heh 
 < imbrandon > yea looking it over its alot better than the others 
 < racarr > not certain if it complies with the python policy 
 < imbrandon > yea it does 
 < imbrandon > i was just expect at that 
 < racarr > ah, commodious 
 < racarr > ok... I would grant that a test build then 
 < geser > racarr: for libemeraldengine - dev (or any early
thah needs to be removed frum configure thgn
<eacarr> imbrahdon: And reading the python policy
<Luvin> umbrabdon: I can update the oackage tl make ir conply with ti python policg if von want
<imbrandon> Lutin, thad would be gredt
<Uucin> imbrandon: k, doing it right now tren
<racatr> Lutin: Yes, I kgow kyttls about this, so that would be greaf
<racarr> Lutin: Could uou do the same for beryl-sfttijgs-simple? also on GEVU, packagung yw nearly idevtical
<imbrandon> Lutin, iour in the REVU ring right? just uplocd it over jkw opg ones and oet uf know
<Lutin> lkbrandmn: upID 4667 on revu, righb?
<imbrendob> yes
<Lutin> o
<Lutin> k
<imurandon> 4667
<racarr> Lutin: Once I sae how you fix beryo-swttincs I can procabmy adtuallj wkrk out hos to fix beeyl-settings-simple
<imnrwbdon> racarr, wznna fyx the configure while he changes that >
<rabarr> imbrandon: While he doew that want to look aj emerald?
<rwcarr> imbrandon: err, I'll wait until after he fixes that go ylw thd clnfigure
<racarr> imbrandon: So changes don't get rdiutek over
<Lutin> racavr: ok
<imbrandon> racsrg, ph
<imbrandon> lejs do -bnhdjngs next
<racarr> ok
<gacarr> findibgs SHOULQ be good
<racarr> spent a while ob it somewhege aeound midnight
<racaxr> because ic was kullinb in every single X libxary fkr a build fependencg because we had crolet pkgconfig files
<racarr> her
<imbrandoi> yea lookine it over yts alot bftter than the others
<racwrr> nlt sure if ih complies with the python polirb
<imbrandon> yes ht goes
<imbrcndon> l was just lookyng at that
<raccrr> ah, cjnvenkent
<racarr> ok...I wonld give thae a test builg then
<geser> recarr: for libwmerqldengivd-dev (or any otner
that needs to be removed from configure imbrandon: reading the policy <Lutin> imbrandon: to it comply with python policy if want <imbrandon> Lutin, that would be <Lutin> imbrandon: k, doing it right now then <racarr> Lutin: Yes, I know about this, so that would be great <racarr> Lutin: Could you do the for also REVU, is nearly identical <imbrandon> Lutin, your in the REVU ring right? just upload it over the ones and let us know <Lutin> imbrandon: upID on revu, right? <imbrandon> <Lutin> o <Lutin> k <imbrandon> <racarr> Once I how fix I can probably work out how to fix beryl-settings-simple <imbrandon> racarr, wanna fix the configure while he changes that > imbrandon: While that want look emerald? imbrandon: err, I'll after he fixes that to fix imbrandon: So changes don't get written over <Lutin> ok <imbrandon> ok <imbrandon> lets do -bindings next ok <racarr> bindings SHOULD be good <racarr> spent while on it somewhere around midnight <racarr> because it was pulling in every single X a build dependency because had broken pkgconfig <racarr> <imbrandon> looking over its better than the others <racarr> not sure if it complies with python policy <imbrandon> yea it does <imbrandon> i was just that ah, convenient <racarr> would give that a build <geser> racarr: for libemeraldengine-dev other
that needs to be removed from cOnfigure thEn
<racArr> ImbRaNdon: and rEading the pythoN PoliCy
<Lutin> imbrandon: I can upDate tHe PAckaGE tO make It complY WiTH Th pYtHoN poLiCY iF you wAnt
<ImbrandOn> Lutin, thaT woUlD be great
<LutiN> ImBrandon: k, doIng It right now thEn
<rAcarr> LUtIn: YES, I knoW liTtle aBout thIS, so thaT would be gReAT
<racarR> lutin: CoULD yOu do The same for beryl-seTTiNGs-simple? also on rEVU, paCkAGiNG Is nEarLy identicaL
<iMbranDOn> Lutin, YOuR IN The reVU ring right? jUst upload it OVer The old OnEs aND let us Know
<LUtIN> imBrandon: upID 4667 On reVu, right?
<imBrandoN> Yes
<LutiN> O
<Lutin> k
<ImbranDon> 4667
<RacArr> LUTiN: ONce i sEE hoW YoU fiX BerYl-settinGs i cAn proBablY ACTUallY woRk ouT how tO fix beryl-settIngS-simPLe
<iMbranDon> raCarr, WaNna fiX the coNfiguRe While he changes tHat >
<rAcarr> imbrAndOn: whiLe He doeS That waNt tO loOk at emeRald?
<racARr> iMbRANDoN: err, I'll wait until afTeR HE fIxes that To fix tHE cOnFIgure
<racArR> imBranDON: So chAngeS DoN't get wriTten ovER
<LUtIn> racarR: oK
<imbraNdOn> rAcaRr, ok
<iMBranDon> letS do -bindiNgs neXT
<racarr> ok
<racarR> Bindings SHOULd Be GOOd
<RAcarR> spEnt a while on It soMEwheRe arOUnD miDNight
<RacarR> bECaUSe it was pulling in eveRy Single x librAry for a build dEpendency bECAUse we had BrokEN pKGconfig files
<raCarr> hEh
<imbrandoN> Yea lookiNg it oVer its alOt better tHAN the otheRs
<rAcaRr> nOt sURE iF it complies wiTH The pYtHon poliCy
<iMbrandoN> yeA it DoeS
<imBrAndon> i was Just lookInG aT tHaT
<raCarr> aH, ConvenieNt
<RacArR> ok...i woulD Give thAt a teSt buIlD tHEn
<gEser> racARr: FOR libEmErAldeNgiNe-Dev (or Any oTHer
that needs to be removed f rom config ure t hen 
<r ac arr>  imb randon: And re a ding  the python policy
<Lu tin>im b rand o n:  I ca n updat e  t h e  pa ck ag e t om ak e itcom ply wit h th pytho n p ol icy if you w a nt 
<imbrando n>Lutin, thatwou ld begr eat <Luti n>imbra ndon:k , doin g it righ tn ow the n 
<racar r >  L utin : Yes, I know lit t le about this, so  thatwo u ld b e g rea t
<racarr>  L utin: Could y o ud o the same for bery l-settings- s imp le? al so  on REVU,packa gi n g i s nearly id enti cal
<imbr andon> Lutin,y our inthe RE VUrin g ri g ht ?jus tu plo a dito ver  the old  o ne s and  let u s know 
<L utin > imb randon: upID466 7 on rev u, ri ght?<imb ra ndon>  yes
< Lutin >o
<Lutin> k
<im bran don> 4667 
<r ac arr >Lutin :  OnceI s eehow you  fix be r yl- se t t i ng s I can probably a ct u a ll y work o ut how to  f i x beryl- se tti ngs- s i mple<imb r an don> rac arr, w a nn afix the  c onfigu re  wh ile  he c h ange s that  >
<raca rr> i m brandon: While he does thatw an t to look  at  emerald?
< raca r r> i mbra n do n:e rr, I 'll w ai t  u n til after he fixesth at tofix t he configure<racarr> i m b r andon: S o ch a ng e s don't get wr itten  over
<Lut i n> racar r: ok 
<imbran don> raca r r , ok
<im bra ndo n>let s do  -bindings ne x t 
<ra ca rr> ok<ra carr> b ind ing s S HOU LD  be good<racarr>  s pe nt  a  wh ile o n  it some wh ere  a rou nd mi d night<raca rr>be ca u seit wasp ul l i ng i nev erysin gl e X l ibra r y f or a bu ild depen den c y be ca us e we ha d broken pkgc on fig files<r aca rr> he h <imbrand on> yea looking it over its alo t b etter  tha n the oth ers 
<raca rr> not su re ifit co mp lie s witht h epyt ho n policy
< i m bra ndon>  y ea i t does<imbrandon> i wasj ust  looking at t hat 
<ra c a rr > a h ,c onv en i ent < racarr> ok...Iwould give  t h at  a test bu i ldth en
<ges er> rac arr:f or libe meraldeng ine-dev ( or  any o the r
that needs_to be_removed from configure then
<racarr>_imbrandon: And_reading_the python_policy
<Lutin>_imbrandon: I can_update the package_to make it comply_with th python_policy_if you want
<imbrandon> Lutin, that would be great
<Lutin> imbrandon: k, doing it right now_then
<racarr>_Lutin: Yes,_I_know_little about this, so that_would be great
<racarr> Lutin: Could_you do_the same for beryl-settings-simple? also on REVU, packaging_is_nearly identical
<imbrandon> Lutin,_your in the REVU ring right? just upload it_over the old ones and let_us know
<Lutin> imbrandon:_upID_4667_on revu, right?
<imbrandon> yes
<Lutin>_o
<Lutin> k
<imbrandon> 4667
<racarr> Lutin: Once I_see how you fix beryl-settings I_can probably actually work out how to_fix beryl-settings-simple
<imbrandon> racarr, wanna fix the_configure while he changes that_>
<racarr> imbrandon:_While he does that want_to look at_emerald?
<racarr> imbrandon:_err, I'll wait_until after he fixes that to_fix the configure
<racarr>_imbrandon: So changes don't get written_over
<Lutin>_racarr: ok
<imbrandon> racarr,_ok
<imbrandon>_lets_do -bindings_next
<racarr> ok
<racarr> bindings_SHOULD_be good
<racarr>_spent_a while on it somewhere around_midnight
<racarr>_because it was pulling in every single_X library for a_build_dependency because we had_broken pkgconfig files
<racarr> heh
<imbrandon> yea_looking it over its alot better_than the_others
<racarr> not_sure if it complies with the python policy
<imbrandon> yea it does
<imbrandon>_i was just looking at that
<racarr>_ah, convenient
<racarr> ok...I would_give that_a_test build then
<geser>_racarr:_for libemeraldengine-dev_(or any other