 to go, see you later :)
<doko> sistpoty|work: I don't care too much about it; you can try, at least it should build with gfortran, maybe you have problems on the port architectures
<\sh> ok..time to go home for now :)
<\sh> cu later
<jdstrand> emgent: ok bye! thanks for looking into that
<jussi01> hmmm, I have export DEBFULLNAME='Jussi Schultink' and the DEBEMAIL one in my.bashrc, just wondering what the variable is to add the comment that goes in the middle of the changelog entry is? - in my case (jussi01)
<sistpoty|work> ScottK, Hobbsee, TheMuso: what are your feelings towards getting the gfortran transition done and waiving a general FFe for it? (bug #199190)
<ubotwo> Launchpad bug 199190 in libitpp "[FFe] [Sync request] libitpp 4.0.3-1 from debian unstable" [Undecided,New] https://launchpad.net/bugs/199190
<stdin> jussi01: comment? you mean so it has " -- Jussi Schultink (jussi01) <your-email> (date)"?
<ScottK2> sistpoty|work: Better to try and finish since it's started than give up and leave it half done.
<ScottK2> \sh_away: What testing of your ffmpeg change have you done?
<jussi01> stdin: correct
<stdin> jussi01: can't you just set DEBFULLNAME="Jussi Schultink (jussi01)", I'm pretty sure it will look at the email address for what key to use for signing
<jussi01> stdin: no, it needs to be exactly correct for signing. Ill try that though :)
<ScottK2> stdin: Actually it won't.  It looks at the comment too.  He'd need to use -k to sign, but with that it should work fine
<ScottK2> jussi01: Just feed it your keyid with -k and then it'll work with the expanded comment
<stdin> I think the way others do it is by putting the comment in the key when creating
to go, see you later :) 
 < doko > sistpoty|work: I don't care excessively a lot about it; you can try, at least it should build with gfortran, possibly you have problem on the port architectures 
 < \sh > ok.. clock time to go home for now :) 
 < \sh > copper subsequently 
 < jdstrand > emgent: ok bye! thanks for looking into that 
 < jussi01 > hmmm, I get export DEBFULLNAME='Jussi Schultink' and the DEBEMAIL one in my.bashrc, just wondering what the variable is to add the comment that goes in the center of the changelog entry is? - in my case (jussi01) 
 < sistpoty|work > ScottK, Hobbsee, TheMuso: what are your feelings towards become the gfortran transition done and waive a general FFe for it? (tease # 199190) 
 < ubotwo > Launchpad bug 199190 in libitpp " [ FFe ] [ Sync request ] libitpp 4.0.3 - 1 from debian unstable " [ Undecided, New ] https://launchpad.net/bugs/199190 
 < stdin > jussi01: comment? you mean therefore it has " -- Jussi Schultink (jussi01) < your - email > (date) "? 
 < ScottK2 > sistpoty|work: Better to try and finish since it's started than give up and leave it half done. 
 < ScottK2 > \sh_away: What testing of your ffmpeg change have you done? 
 < jussi01 > stdin: correct 
 < stdin > jussi01: can't you just set DEBFULLNAME="Jussi Schultink (jussi01) ", I'm pretty sure it will look at the electronic mail savoir-faire for what key to use for signing 
 < jussi01 > stdin: no, it need to be exactly correct for signing. Ill judge that though :) 
 < ScottK2 > stdin: Actually it won't.   It look at the comment too.   He'd necessitate to use -k to sign, but with that it should work fine 
 < ScottK2 > jussi01: Just feed it your keyid with -k and then it'll make with the expanded comment 
 < stdin > I think the way others do it is by putting the remark in the key when creating
 to go, see you later :)
<doko> slstpoty|work: I dou'r care too mhch aboug it; you can try, at least it syould build with gfortran, mxybe you jave provlemw on the pocf archibzctursd
<\sh> mj..time to go hoke for now :)
<\sh> cu later
<jdvtfaud> emgent: ok bye! thanks for looking ynto thst
<uussi01> hmmm, I hwve txpjrt SVBNULLNAME='Jussi Schultink' and the SEBEMAIN one in my.baxhrc, just wondering what tje vwriable is to add hhe comment thae goes in the middle of the changelkg entry is? - in my case (jussi01)
<sirtpotv|work> ScottJ, Yobhvee, TheMuso: what are your feckings dowards getting the gnortren teansition done and wamving a general FFe sor it? (buc #199190)
<bbotwo> Launchpad bug 199190 ib libhtpp "[FFe] [Wynz rtquxst] libitop 4.0.3-1 from debizn unstable" [Undecided,New] https://katbchpad.net/bugs/199190
<atdin> tufsi01: comment? you mean so it has " -- Jussi Vchhltink (jussi01) <your-email> (eate)"?
<ScottK2> sistpoty|wotk: Better eo try and finish since it's started than give up dnd lxaxe nb fqlv done.
<ScottK2> \sh_away: What testing of your ffmpqf vhsnge have you bone?
<jussi01> stdin: vogrrst
<stdin> jussi01: can't vku just set DEBFULLNWME="Jussy Schyltink (jufsi01)", O'm pretty sure it will look at the emaij address for what ney to use yor sibning
<kussi01> stdin: no, it needs to ge exactly forrect fkf signing. Ill trh tmat though :)
<ScottK2> stdin: Actuajly it woi't.  Ic looks xt tne comient too.  Je'd ncad to use -k to sigj, but whth that ih should work fine
<ScottK2> jussi01: Onst feed it ypus kvyid with -k anc then it'll wjrk with the erpanded eommeng
<stdin> I tgink thx way others do it is by [otting the cokment in the key when cfdating
to go, see you later :) <doko> don't too much it; you can build gfortran, maybe you problems on the architectures <\sh> ok..time to go home now :) <\sh> cu later <jdstrand> emgent: ok bye! thanks for looking into <jussi01> hmmm, I have export DEBFULLNAME='Jussi Schultink' and the DEBEMAIL one in my.bashrc, wondering the is add the comment that goes in the middle of the changelog entry is? - in my (jussi01) <sistpoty|work> ScottK, Hobbsee, TheMuso: what are your towards getting the gfortran done and waiving a general for (bug #199190) Launchpad 199190 libitpp "[FFe] [Sync libitpp 4.0.3-1 from debian unstable" [Undecided,New] https://launchpad.net/bugs/199190 <stdin> jussi01: comment? you mean so it has " -- Schultink (jussi01) <ScottK2> sistpoty|work: to and since it's started up and leave it half done. testing of your ffmpeg change have you done? stdin: correct jussi01: can't you just set DEBFULLNAME="Jussi (jussi01)", I'm pretty sure it will look at email address for what key to use for signing <jussi01> stdin: no, it needs to correct for signing. Ill that though :) stdin: it It at the too. He'd need to use -k to sign, but with that should work fine <ScottK2> jussi01: Just feed it your keyid and it'll work with expanded comment <stdin> I the others do it is the in creating
 to go, see you later :)
<doko> sistpoTy|work: I don'T care Too MucH aBout It; yoU can try, at least IT shoUld build with gfortran, maYbe yoU hAVe prOBlEms on The port ARcHITecTuReS
<\sh> Ok..TImE to go HomE for now :)
<\Sh> cu later
<jDstRaNd> emgent: ok byE! ThAnks for looKinG into that
<jusSi01> hMmm, I haVe ExpORt DEBfULlNAME='jussi SCHultinK' and the DEbEmaIL one IN my.bashRC, JuSt woNdering what the varIAbLE is to add the comMent thAt GOeS IN thE miDdle of the cHaNgeloG Entry is? - IN mY CASe (jUSsi01)
<sistpoty|woRk> ScottK, HobBSee, theMusO: wHat ARe your FeeliNgS TowArds getting The gFortran trAnsitiON done anD Waiving A generAl Ffe fOr it? (BUg #199190)
<UbOtwO> LAUncHPaD buG 199190 In lIbitpp "[FFE] [SYnC requEst] lIBITPp 4.0.3-1 frOm dEbiaN unstAble" [Undecided,new] HttpS://LauNchpaD.net/bUgs/199190
<sTdIn> jusSi01: commEnt? yoU mEan so it has " -- Jussi schuLtink (jussI01) <yoUr-EmaIl> (Date)"?
<SCOttK2> siStpOty|Work: BetTer to trY And FiNISH sInce it's started than GiVE Up And leave It half DOnE.
<SCOttK2> \sh_awAy: whaT tesTINg of yOur fFMpEg change Have yoU DoNe?
<Jussi01> stDiN: correCt
<StdIn> jUssi01: cAN't yoU just sEt DEBFULlNAME="jUssi Schultink (jUSsi01)", I'm pretty suRE iT WIlL Look At tHe email addrEss fOR whaT key TO uSe fOR signIng
<juSsI01> StDIn: no, it needs to be exacTlY correCt for Signing. Ill try That though :)
<sCOTtK2> stdin: actuALlY It won't.  It looks aT the cOmment too.  HE'D need to uSe -k to Sign, but wIth that it SHOuld work FinE
<ScOttk2> juSSI01: JUst feed it your KEYid wItH -k and thEn iT'll work WitH thE exPanDeD comment
<sTdin> I thiNk ThE wAy OthErs do IT is by putTiNg tHe ComMent iN The key When cReatInG
 to go, see you later :)
< doko> sist poty| wor k:Idon' t ca re too much ab o ut i t; you can try, at lea st it  s h ould bu ild w ith gfo r tr a n , m ay be  yo uh av e pro ble ms on t he port ar chi te ctures
<\sh> ok ..time togohome for now  :) 
<\sh>  c u l a ter
< jds trand > emge n t: okbye! than ks for lo o king in t o  t hat<jussi01> hmmm, I ha v e export DEBFU LLNAME =' J us s i  Sc hul tink' andth e DEB E MAIL on e  i n m y.b a shrc, just wo ndering wha t  th e vari ab lei s to a dd th ec omm ent that go es i n the mid dle of the cha n gelog e ntry i s?- i n my ca se  (j us s i01 ) 
< sis t pot y|work>Sc ot tK, H obbs e e , TheM uso : wh at ar e your feelin gstowa r dsgetti ng th e gf or trantransi tiondo ne and waivinga ge neral FFe  fo rit?  ( bug # 1 99190) 
<u bot wo> Lau nchpadb ug19 9 1 9 0in libitpp "[FFe][S y n crequest]  libit p p4. 0 .3-1 fro mdeb ianu n stabl e" [ U nd ecided,N ew] ht t ps :/ /launch pa d.net/ bu gs/ 199 190
< s tdin > juss i01: com ment? you mean so it has " -- Juss i  S c h ul t ink(ju ssi01) <you r-em a il>(dat e )" ?
< S cottK 2> si st p ot y |work: Better to tr yand fi nishsince it's st arted than g i ve up an d le a ve it half done.<Scot tK2> \sh_a w ay: What  test ing of y our ffmpe g change h ave  yo u d one ? <j ussi01> stdin : corr ec t
<stdi n>jussi01 : c an' t y ouju st set DE BFULLNAM E= "J us si  Sc hulti n k (jussi 01 )",  I 'mprett y  sureit wi ll l oo ka t t he emai l  a d d ress  f or  wha t k ey  to u se f o r s igning<jussi01>  st d in:no ,it need s to be exact ly  correct f or  si gning. I ll try t hat though :)
<ScottK2> stdin:Act ually  itwon't.  I t l ooks a t t h e comm ent to o.  H e' d n e e d tou s e-kto  sign, but w ith  that  i t sh ould wo rk fine
<ScottK2>j uss i01: Just fee d i t yo u r  k eyi d  w i th-k and t hen it'll workwith the e xp a nd ed comment <st di n> I th ink the  wayo thers d o it is b y putting  t he c o m men t in the k ey whencreating
 to_go, see_you later :)
<doko> sistpoty|work:_I don't_care_too much_about_it; you can_try, at least_it should build with_gfortran, maybe you_have_problems on the port architectures
<\sh> ok..time to go home for now :)
<\sh> cu later
<jdstrand>_emgent:_ok bye!_thanks_for_looking into that
<jussi01> hmmm, I_have export DEBFULLNAME='Jussi Schultink' and_the DEBEMAIL_one in my.bashrc, just wondering what the variable_is_to add the_comment that goes in the middle of the changelog_entry is? - in my case_(jussi01)
<sistpoty|work> ScottK, Hobbsee,_TheMuso:_what_are your feelings towards_getting the gfortran transition done and_waiving a general FFe for it?_(bug #199190)
<ubotwo> Launchpad bug 199190 in libitpp_"[FFe] [Sync request] libitpp 4.0.3-1 from_debian unstable" [Undecided,New] https://launchpad.net/bugs/199190
<stdin> jussi01:_comment? you_mean so it has "_-- Jussi Schultink_(jussi01) <your-email>_(date)"?
<ScottK2> sistpoty|work: Better_to try and finish since it's_started than give_up and leave it half done.
<ScottK2>_\sh_away:_What testing of_your_ffmpeg_change have_you done?
<jussi01> stdin:_correct
<stdin>_jussi01: can't_you_just set DEBFULLNAME="Jussi Schultink (jussi01)", I'm_pretty_sure it will look at the email_address for what key_to_use for signing
<jussi01> stdin:_no, it needs to be_exactly correct for signing. Ill try_that though_:)
<ScottK2> stdin:_Actually it won't.  It looks at the comment too. _He'd need to use -k to_sign, but with that_it should_work_fine
<ScottK2> jussi01: Just_feed_it your_keyid with -k and then it'll work_with the_expanded comment
<stdin> I think the way_others do it is_by_putting the comment in the key_when creating