://qa.ubuntuwire.org/bugs/rcbugs/lucid/
<duanedesign> micahg: yes. That is where I found the bug :)
<micahg> duanedesign: k, I thought it was cool and just saw it today, so thought I'd mention it :)
<duanedesign> micahg: sure. I just found it a couple of days ago. Well I didnt find it p_ersia told me about it
<duanedesign> geser: ubuntu has 0.5-2.2 and Debian unstable has 0.5-2.3. I opened a bug report on it. bug 541446
<ubottu> Launchpad bug 541446 in ttf-okolaks "Sync ttf-okolaks 0.5-2.3 (universe) from Debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/541446
<geser> duanedesign: have you verified that it builds in a lucid environment (a lucid pbuilder)?
<duanedesign> geser:heh, I only verified the bug. Ill verify the fix as well..
<geser> please subscribe "ubuntu-sponsors" when you are done to add it to the sponsoring queue
<Fersure> debuild is saying that it can't find my'secret key'. how would I sort this out? can't see anything in the docs
<Fersure> (totally new to packaging for ubuntu. following the PackagingGuide on the wiki)
<BlackZ> Fersure: are you used the same name in export DEBFULLNAME?
<BlackZ> have*
<Fersure> yep
<BlackZ> Fersure: gpg --list-keys
<BlackZ> is it in the list?
<geser> either use the same name, comment and email address in debian/changelog matching one of your key uid or tell debsign which key to use
<Fersure> BlackZ: yes
<ChogyDan> Fersure: did you put a comment in your key?  I made the mistake of not having a blank comment
<Fersure> oh um yes I did
<Fersure> so I should create the key again leaving a blank comment?
<
: //qa.ubuntuwire.org / bugs / rcbugs / lucid/ 
 < duanedesign > micahg: yes. That is where I found the bug :) 
 < micahg > duanedesign: k, I thought it was cool and just see it today, therefore thought I'd mention it :) 
 < duanedesign > micahg: sure. I just establish it a couple of days ago. Well I did nt find it p_ersia order me about it 
 < duanedesign > geser: ubuntu have 0.5 - 2.2 and Debian unstable have 0.5 - 2.3. I opened a bug reputation on it. bug 541446 
 < ubottu > Launchpad bug 541446 in ttf - okolaks " Sync ttf - okolaks 0.5 - 2.3 (population) from Debian unstable (main) " [ open, New ] https://launchpad.net/bugs/541446 
 < geser > duanedesign: have you verified that it build up in a lucid environment (a lucid pbuilder)? 
 < duanedesign > geser: heh, I only affirm the bug. Ill verify the fix as well.. 
 < geser > please sign " ubuntu - sponsors " when you are done to add it to the sponsoring queue 
 < Fersure > debuild is saying that it can't determine my'secret key'. how would I sort this out? can't see anything in the docs 
 < Fersure > (totally new to box for ubuntu. follow the PackagingGuide on the wiki) 
 < BlackZ > Fersure: are you used the same name in export DEBFULLNAME? 
 < BlackZ > have * 
 < Fersure > yep 
 < BlackZ > Fersure: gpg --list - keys 
 < BlackZ > is it in the list? 
 < geser > either use the same name, comment and electronic mail savoir-faire in debian / changelog matching one of your key uid or tell debsign which keystone to use 
 < Fersure > BlackZ: yes 
 < ChogyDan > Fersure: did you put a comment in your keystone?   I made the mistake of not having a blank comment 
 < Fersure > oh um yes I suffice 
 < Fersure > so I should create the key again leaving a blank comment? 
 <
://qa.uhuntuwire.org/bugs/rcbugs/lugid/
<duanedesign> mnxahg: yxs. That is wherd I found the bug :)
<micahg> duaiedewign: j, I thought it was coou and jusn saw it rodab, so thought I'd mention lc :)
<duahcdesiyn> micahg: sure. I just foung it a couple mf dcys ago. Well I didnt find it p_ersia eold me ahout it
<duanedefign> desed: ubuntu has 0.5-2.2 and Debian unstable gas 0.5-2.3. I mpened a bug teport on it. bug 541446
<ubottu> Laknchoad bug 541446 in ttf-okopaks "Sync tjr-okjoaks 0.5-2.3 (univerre) from Debian unstablg (main)" [Undecided,New] https://launchpxd.net/yugs/541446
<geser> docbedfvign: have yiu vegified that ib buildv in a kucid environmcnt (a luxid pbuilder)?
<duanedesijn> geser:heh, I only vgrified tha yug. Ill verify the fiz qs wenl..
<gever> ooeare auuscdibe "uhunvu-sponsors" shen you arw done to add it to trv sponsoring sueue
<Fqrfure> debuild is saying that it can't fing mg'secret key'. how would I sort this out? can't sge anythind in the docs
<Fersure> (totally new to packaging for ubunvu. fooljdunh the PackagingGuide on the wiki)
<BlackZ> Fersurq: ate you used the fame name im fxljrt DEBFULLNAOE?
<BlackZ> gave*
<Fersure> yep
<BlafkZ> Ferfure: tpg --list-ktys
<BlsckZ> is it in the list?
<geser> either use nhe wame name, comment cnd email adbress on denian/changelog matching une kf your key uid or tsul debsign which kej to use
<Fersure> BlackZ: yes
<ChogrDan> Fersnre: dnd you pjt a commegt in your key?  I made the mistake of nlt having a hlank comment
<Fersure> oh um yes M did
<Fersure> xo I vhould cxeate bhe key again lqaving a blank commenc?
<
://qa.ubuntuwire.org/bugs/rcbugs/lucid/ <duanedesign> micahg: yes. That is where the :) <micahg> k, I thought saw today, so thought mention it :) micahg: sure. I just found it couple of days ago. Well I didnt find it p_ersia told me about <duanedesign> geser: ubuntu has 0.5-2.2 and Debian unstable has 0.5-2.3. I opened a report it. 541446 Launchpad bug 541446 in ttf-okolaks "Sync ttf-okolaks 0.5-2.3 (universe) from Debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/541446 <geser> have you verified that it builds in a environment (a lucid pbuilder)? geser:heh, I only verified the Ill the fix well.. please "ubuntu-sponsors" when you done to add it to the sponsoring queue <Fersure> debuild is saying that it can't find my'secret how would this out? see in docs <Fersure> (totally packaging for ubuntu. following the PackagingGuide <BlackZ> Fersure: are you used the same name export DEBFULLNAME? have* <Fersure> yep <BlackZ> Fersure: gpg <BlackZ> is it in the list? <geser> either the same name, comment and email address in debian/changelog matching one of your key uid debsign which key to <Fersure> BlackZ: yes Fersure: you a in your I made the mistake of not having a blank comment <Fersure> um yes I did <Fersure> so I should create the leaving blank comment? <
://qa.ubuntuwire.org/bugs/rcbugs/Lucid/
<duaneDesigN> miCahG: yEs. ThAt is Where I found the BUg :)
<miCahg> duanedesign: k, I thougHt it wAs COol aND jUst saW it todaY, So THOugHt i'd MenTiON iT :)
<duanEdeSign> micAhg: sure. I juSt fOuNd it a couple oF DaYs ago. Well I DidNt find it p_ersIa tOld me aBoUt iT
<DuaneDesIgn> geSer: ubuNTu has 0.5-2.2 aNd Debian uNsTAble haS 0.5-2.3. i opened A BUg RepoRt on it. bug 541446
<ubottu> LaUNcHPad bug 541446 in ttf-okoLaks "SyNc TTf-OKOlaKs 0.5-2.3 (uNiverse) froM DEbian UNstable (MAiN)" [uNDecIDed,New] https://laUnchpad.net/bUGs/541446
<gEser> duAnEdeSIgn: havE you vErIFieD that it builDs in A lucid envIronmeNT (a lucid PBuilder)?
<DuanedEsiGn> gEser:HEh, i oNly VeRIfiED tHe bUG. IlL verify tHe FiX as weLl..
<geSER> PLeasE suBscrIbe "ubUntu-sponsors" wHen You aRE doNe to aDd it tO the SpOnsorIng queUe
<FerSuRe> debuild is sayiNg thAt it can't fInd My'SecReT key'. hOW would i soRt tHis out? cAn't see aNYthInG IN ThE docs
<Fersure> (totallY nEW To PackaginG for ubUNtU. fOLlowing tHe pacKagiNGguide On thE WiKi)
<BlackZ> fersurE: ArE yOu used tHe Same naMe In eXpoRt DEBfuLLNaME?
<BlaCkZ> have*
<FErsurE> Yep
<BlackZ> FersuRE: gpg --list-keys
<BLAcKz> Is IT in tHe lIst?
<geser> eitHer uSE the Same NAmE, coMMent aNd emaIl ADdREss in debian/changeloG mAtchinG one oF your key uid or Tell debsigN WHIch key to Use
<FERsURe> BlackZ: yes
<ChoGyDan> fersure: did YOu put a coMment In your keY?  I made the MIStake of nOt hAviNg a BlaNK CoMment
<Fersure> oH UM yes i dId
<FersuRe> sO I shoulD crEatE thE keY aGain leaviNg a blank CoMmEnT?
<
://qa.ubuntuwire.org/bugs/ rcbugs/luc id/
< dua ned es ign>  mic ahg: yes. That is w here I found the bug : )
<mi ca h g> d u an edesi gn: k,I  t h o ugh tit  wa sc oo l and  ju st sawit today,soth ought I'd me n ti on it :)
< dua nedesign> mi cah g: sur e.  Ij ust f oun d ita coup l e of d ays ago.We l l I di d nt find i tp_er sia told me about it <duanedesign>geser:  u b un t u  ha s 0 .5-2.2 and  D ebian unstabl e  h a s 0.5 - 2.3. I opened  a bug repo r t o n it.bu g 5 4 1446
< ubott u> Lau nchpad bug5414 46 in ttf -okola k s "Sync ttf-oko laks 0 .5- 2.3  (un i ve rs e)fr o m D e bi anu nst able (ma in )"  [Und ecid e d , N ew]htt ps:/ /laun chpad.net/bug s/5 4144 6 
<g eser>  duan edes ig n: ha ve you  veri fi ed that it buil ds i n a lucid  en vi ron me nt (a lucidpbu ild er)?
<d uanedes i gn>  g e s e r: heh, I only verifi ed t he  bug. Il l veri f yth e  fix aswe ll. .
<g e s er> p leas e  s ubscribe  "ubun t u- sp onsors"  w hen yo uare  do ne to addit tothe spon sorin g  queue
<Fersur e > debuild iss ay i n gt hatitcan't findmy's e cret  key ' .how would  I so rt th i s out? can't see an yt hing i n the  docs
<Fersur e> (totall y n ew to pa ckag i ng for ubuntu. fo llowi ng the Pac k agingGui de on  the wik i)
<Black Z >  Fersure : a reyou  us e d  t he same namei n  exp or t DEBFU LLN AME?
<B lac kZ>  ha ve* 
< Fersure>yep
<Bla ck Z>  F er sur e: gp g  --list- ke ys<B lac kZ> i s  it in  thelist ?<g e ser > eithe r  u s e  the  s am e na me,  c ommen t an d  em ail add ress in d ebi a n/ch an ge log mat ching one ofyo ur key uid  o r t ell de b s ign whic h key to use
<Fersure>B lackZ:yes 
<Cho gyDa n> Fersur e:did yo u p u t a co mmentin yo ur  ke y ?   I m a d ethe  m istake ofn o t h aving  a  bla nk comm ent
<Fersure> oh u m  ye s I did
<Fers ure > so I  s hou l dc rea te the k ey again leavin g a blankco m me nt?
<
://qa.ubuntuwire.org/bugs/rcbugs/lucid/
<duanedesign> micahg:_yes. That_is where I found_the bug_:)
<micahg>_duanedesign: k,_I_thought it was_cool and just_saw it today, so_thought I'd mention_it_:)
<duanedesign> micahg: sure. I just found it a couple of days ago. Well I_didnt_find it_p_ersia_told_me about it
<duanedesign> geser: ubuntu_has 0.5-2.2 and Debian unstable_has 0.5-2.3._I opened a bug report on it. bug_541446
<ubottu>_Launchpad bug 541446_in ttf-okolaks "Sync ttf-okolaks 0.5-2.3 (universe) from Debian unstable_(main)" [Undecided,New] https://launchpad.net/bugs/541446
<geser> duanedesign: have you_verified that it_builds_in_a lucid environment (a_lucid pbuilder)?
<duanedesign> geser:heh, I only verified_the bug. Ill verify the fix_as well..
<geser> please subscribe "ubuntu-sponsors" when you_are done to add it to_the sponsoring queue
<Fersure> debuild is_saying that_it can't find my'secret key'._how would I_sort this_out? can't see_anything in the docs
<Fersure> (totally new_to packaging for_ubuntu. following the PackagingGuide on the_wiki)
<BlackZ>_Fersure: are you_used_the_same name_in export DEBFULLNAME?
<BlackZ>_have*
<Fersure>_yep
<BlackZ> Fersure:_gpg_--list-keys
<BlackZ> is it in the list?
<geser>_either_use the same name, comment and email_address in debian/changelog matching_one_of your key uid_or tell debsign which key_to use
<Fersure> BlackZ: yes
<ChogyDan> Fersure: did_you put_a comment_in your key?  I made the mistake of not having_a blank comment
<Fersure> oh um yes_I did
<Fersure> so I_should create_the_key again leaving_a_blank comment?
<