_85> in the svn, mind
<imbrandon> kk
<racarr> lupine_85: Ok, SVN is still up
<racarr> lupine_85: You read what imbrandon said about the dfgs+git tarball?
<racarr> dfsg
<lupine_85> yeah
<racarr> ok
<lupine_85> so remove those two.po, do src/activation.c
<racarr> err
<racarr> I'm not sure I understand how that works
<lupine_85> meh. svn: Can't create directory '/beryl/db/transactions/4514-1.txn': Permission denied
<racarr> are the two pos removed in the upstream tarball
<lupine_85> ah, I think it's read-only
<racarr> or diff?
<crimsun> racarr: yes, in the tarball
<lupine_85> removed in teh tarball
<lupine_85> crap, snow :/
<racarr> ok
<racarr> lupine_85: Also merge all the patches we already have...
<racarr> no reason to have a debian/patches  if it's not needed
<lupine_85> racarr: yep, that's done
<racarr> fun
<crimsun> lupine_85: in debian/changelog, it's best to follow the format where you list the patch followed by a very brief synopsis of its function
<lupine_85> crimsun: ok
<lupine_85> there are no patches now ;)
<crimsun> ok
<racarr> woo
<crimsun> debian/libberylsettings0-gconf.install contains a.so (not a.so.blah). Intentional?
<imbrandon> ok just so _I'm_ clear here, all changes we've been talking about ( except removing the.po's ) are in git?
<racarr> yes
<imbrandon> yes who? hehe
<racarr> yes they are in git
<crimsun> moreover, debian/libberylsettings0.install references usr/lib/beryl
_ 85 > in the svn, mind 
 < imbrandon > kk 
 < racarr > lupine_85: Ok, SVN is still up 
 < racarr > lupine_85: You read what imbrandon said about the dfgs+git tarball? 
 < racarr > dfsg 
 < lupine_85 > yeah 
 < racarr > ok 
 < lupine_85 > therefore absent those two.po, do src / activation.c 
 < racarr > err 
 < racarr > I'm not sure I understand how that work 
 < lupine_85 > meh. svn: Can't create directory' /beryl / db / transactions/4514 - 1.txn': Permission deny 
 < racarr > are the two united states post office removed in the upstream tarball 
 < lupine_85 > ah, I remember it's read - only 
 < racarr > or diff? 
 < crimsun > racarr: yes, in the tarball 
 < lupine_85 > take out in teh tarball 
 < lupine_85 > crap, snow :/ 
 < racarr > ok 
 < racarr > lupine_85: Also blend all the mend we already have... 
 < racarr > no reason to have a debian / patches   if it's not needed 
 < lupine_85 > racarr: yep, that's act 
 < racarr > fun 
 < crimsun > lupine_85: in debian / changelog, it's best to follow the format where you list the temporary hookup followed by a very brief synopsis of its function 
 < lupine_85 > crimsun: ok 
 < lupine_85 > there be no patches now ;) 
 < crimsun > ok 
 < racarr > woo 
 < crimsun > debian / libberylsettings0 - gconf.install contains a.so (not a.so.blah). Intentional? 
 < imbrandon > ok just therefore _ I'm _ clear here, all changes we've been talking about (except removing the.po's) are in git? 
 < racarr > yes 
 < imbrandon > yes who? hehe 
 < racarr > yes they are in git 
 < crimsun > moreover, debian / libberylsettings0.install references usr / lib / beryl
_85> in the svn, mind
<imbrandon> ky
<racarr> lupine_85: Ok, SVN ms stilm up
<racafr> lupine_85: You read what imbrendob saie about the dfgs+git tafball?
<racagr> dfsg
<lupine_85> teah
<racarr> ok
<lupinc_85> so dcmove vhose two.po, do xrc/activathon.c
<racarr> err
<sazaxr> I'm not sure I understand how that works
<liplne_85> meh. svn: Cag't cgewte sprtctory '/beryl/db/transactions/4514-1.txn': Perjission denied
<racarr> are the two pos removed ij thf upstream tarball
<pupine_85> ah, I thigj it's read-onuy
<racarr> og diff?
<crimson> racarr: yes, in the tarball
<lupive_85> rekoved in tgk tagtall
<lupine_85> rrap, sgow :/
<racarr> ok
<racarr> nupine_85: Slso merge all thx parches we already have...
<cacarr> no reason to rave a deticn/patches  if it's not nweded
<nupite_85> rxxarf: ytp, vhaf's donf
<rararr> fun
<crijsun> lupine_85: in debian/changelog, ie'w best to folmow thq sormat where you list the patch followeg bg a very brief synopsis of its function
<luping_85> crimsun: jk
<lupine_85> there are no patches now ;)
<crimsun> ok
<racars> woo
<rrkmsbk> awblan/libberylsettings0-gconf.install contains a.so (gkt a.xo.blah). Intentijnal?
<imbrandpn> ol just so _I'm_ cuear hzde, all changes we've heen tajking about ( evcepy removing the.po's ) are in gut?
<racarr> yes
<pmbrqndon> yes who? hehe
<xacarr> yes tkey arg in got
<crimsun> moreover, debicn/libbsrylsettingd0.install ddferences usr/lib/cerjl
_85> in the svn, mind <imbrandon> kk Ok, is still <racarr> lupine_85: You the tarball? <racarr> dfsg yeah <racarr> ok so remove those two.po, do src/activation.c err <racarr> I'm not sure I understand how that works <lupine_85> meh. svn: create directory '/beryl/db/transactions/4514-1.txn': Permission denied <racarr> are the two pos removed in the tarball ah, think read-only <racarr> or diff? <crimsun> racarr: yes, in the tarball <lupine_85> removed in teh tarball <lupine_85> snow :/ <racarr> ok <racarr> lupine_85: Also merge the patches we already <racarr> no reason to have debian/patches it's not <lupine_85> yep, done <racarr> fun lupine_85: in debian/changelog, it's best to follow the format where you list the patch followed by a brief synopsis function <lupine_85> ok there no patches now ok <racarr> woo <crimsun> debian/libberylsettings0-gconf.install contains Intentional? <imbrandon> ok just so _I'm_ clear here, changes we've talking about ( except removing the.po's are in git? <racarr> yes <imbrandon> yes who? <racarr> yes they are in git <crimsun> moreover, debian/libberylsettings0.install references usr/lib/beryl
_85> in the svn, mind
<imbrandon> kk
<raCarr> lupine_85: ok, SVN Is sTilL uP
<racArr> lUpine_85: You read whAT imbRandon said about the dfgs+Git taRbALl?
<raCArR> dfsg
<Lupine_85> yEAh
<RACarR> oK
<lUpiNe_85> SO rEmove ThoSe two.po, Do src/activAtiOn.C
<racarr> err
<raCArR> I'm not sure i unDerstand how tHat Works
<lUpIne_85> MEh. svn: can'T creaTe direCTory '/beRyl/db/tranSaCTions/4514-1.tXN': PermisSIOn DeniEd
<racarr> are the two POs REmoved in the upsTream tArBAlL
<LUpiNe_85> aH, I think it's ReAd-onlY
<Racarr> oR DiFF?
<CRimSUn> racarr: yes, in The tarball
<lUPinE_85> removEd In tEH tarbaLl
<lupInE_85> CraP, snow :/
<racarr> Ok
<raCarr> lupinE_85: Also mERge all tHE patcheS we alrEadY haVe...
<raCArR> nO reAsON to HAvE a dEBiaN/patches  If It'S not nEedeD
<LUPIne_85> rAcaRr: yeP, that'S done
<racarr> fuN
<crImsuN> LupIne_85: in DebiaN/chaNgElog, iT's best To folLoW the format where You lIst the patCh fOlLowEd By a veRY brief SynOpsIs of its FunctioN
<LupInE_85> CRImSun: ok
<lupine_85> there arE nO PAtChes now ;)
<cRimsun> OK
<rAcARr> woo
<criMsUn> dEbiaN/LIbberYlseTTiNgs0-gconf.InstalL CoNtAins a.so (NoT a.so.blAh). intEntIonal?
<IMbraNdon> ok Just so _I'm_ Clear HEre, all changes wE'Ve been talking ABoUT ( ExCEpt rEmoVing the.po's ) aRe in GIt?
<raCarr> YEs
<ImbRAndon> Yes whO? hEHe
<RAcarr> yes they are in giT
<cRimsun> MoreoVer, debian/libbErylsettinGS0.INstall reFereNCeS Usr/lib/beryl
_85> in the svn, mind
<imb randon> kk 
<rac arr > l up ine_ 85:Ok, SVN is sti l l up 
<racarr> lupine_85: Y ou re ad what im brand on said ab o u t t he  d fgs +g i ttarba ll? 
<racar r> dfsg
<l upi ne _85> yeah
<r a ca rr> ok
<lu pin e_85> so rem ove  those  t wo. p o, do  sr c/act ivatio n .c
<ra carr> err 
< r acarr> I'm not s ur e Iunderstand how th a tw orks
<lupine_8 5> meh .s vn : Can 'tcreate dir ec tory' /beryl/ d b/ t r a nsa c tions/4514-1. txn': Permi s sio n deni ed 
<r a carr>are t he two  pos remove d in  the upst ream t a rball
< l upine_8 5> ah,  Ithi nk i t 's  r ead -o n ly< ra car r > o r diff?<c ri msun>  rac a r r :  yes , i n th e tar ball
<lupine_ 85>  rem o ved  in t eh ta rbal l<lupi ne_85>  crap ,snow :/
<racarr > ok 
<racarr>  lu pi ne_ 85 : Als o  merge  al l t he patc hes wea lre ad y h av e...
<racarr> no r ea s o nto havea debi a n/ pa t ches  if  i t's  not n eeded 
<lu p in e_85> ra carr:y ep ,that'sdo ne
<ra ca rr>  fu n
<cr i msun > lupi ne_85: i n deb i an/changelog,i t's best to f o ll o w  t h e fo rma t where you  lis t  the  pat c hfol l owedby ave r yb rief synopsis of it sfuncti on
<l upine_85> cri msun: ok
< l u p ine_85>ther e  a r e no patches n ow ;) 
<crimsun> ok
<raca rr> w oo
<crim sun> debi a n /libbery lse tti ngs 0-g c o nf .install cont a i ns a .s o (nota.s o.blah) . I nte nti ona l? 
<imbrand on> ok j us tso  _ I'm _ cle a r here,al l c ha nge s we' v e been  talk ingab ou t  (exceptr em o v ingth e. po's  )ar e ingit? <ra carr> y es
<imbra ndo n > ye swh o? hehe 
<racarr> yes  t hey are in  g it<crims u n > moreov er, debian/libberylsett i ngs0.in sta ll re fere nces usr/ lib /beryl 
_85> in_the svn,_mind
<imbrandon> kk
<racarr> lupine_85: Ok,_SVN is_still_up
<racarr> lupine_85:_You_read what imbrandon_said about the_dfgs+git tarball?
<racarr> dfsg
<lupine_85> yeah
<racarr>_ok
<lupine_85> so remove_those_two.po, do src/activation.c
<racarr> err
<racarr> I'm not sure I understand how that works
<lupine_85> meh. svn:_Can't_create directory_'/beryl/db/transactions/4514-1.txn':_Permission_denied
<racarr> are the two pos_removed in the upstream tarball
<lupine_85>_ah, I_think it's read-only
<racarr> or diff?
<crimsun> racarr: yes, in_the_tarball
<lupine_85> removed in_teh tarball
<lupine_85> crap, snow :/
<racarr> ok
<racarr> lupine_85: Also merge_all the patches we already have...
<racarr>_no reason to_have_a_debian/patches  if it's_not needed
<lupine_85> racarr: yep, that's done
<racarr>_fun
<crimsun> lupine_85: in debian/changelog, it's best_to follow the format where you list_the patch followed by a very_brief synopsis of its function
<lupine_85>_crimsun: ok
<lupine_85>_there are no patches now_;)
<crimsun> ok
<racarr> woo
<crimsun>_debian/libberylsettings0-gconf.install contains_a.so (not a.so.blah)._Intentional?
<imbrandon> ok just so _I'm_ clear_here, all changes_we've been talking about ( except_removing_the.po's ) are_in_git?
<racarr>_yes
<imbrandon> yes_who? hehe
<racarr> yes_they_are in_git
<crimsun>_moreover, debian/libberylsettings0.install references usr/lib/beryl