 and upload for hardy
<emgent> s/task/tasks/
<Fujitsu> Isn't that how smarty works?
<emgent> Fujitsu: it'snt critical bug, smarty work but it's vulnerable
<Hobbsee> emgent: the sponsorship queue was overrated?
<emgent> Hobbsee: i prefer used IRC for security sponsor in hardy, because the rest of upload are by security team.
<emgent> argh my english sux
<nixternal> fooey
<emgent> ls
<emgent> ups, worng window
<Iulian> G'morning.
<Iulian> DktrKranz: Thanks for uploading nxtvepg.
<Iulian> Hello btw :)
<vik_3278> Hello, I have a quick question on naming conventions for back-ports.
<Hobbsee> jdong: ^
<Hobbsee> vik_3278: would help if you say your question
<vik_3278> I'm trying to backport  libestools1.2_1.2.96~beta from Hardy to Gutsy
<DktrKranz> Iulian, hey. Thank *you*
<vik_3278> Hobbsee: yeah I already posted on jdong's thread, but I thought I'd do a little bit of digging myself :)
<vik_3278> sorry the package is called libestools1.2_1.2.96~beta-2
<vik_3278> if I'm not mistaken, I should name it something like libestools1.2_1.2.96~beta-2~7.10backport1
<vik_3278> or atleast that's what jdong's prevu utility does
<vik_3278> but apt doesn't seem to like the 2 ~'s in the name
<DktrKranz> hellboy195,!
<vik_3278> So my question is, what is the correct way to name this package?
<jpatrick> vik_3278: ~gutsy1
<hellboy195> DktrKranz: sry?
<vik_3278> drop the ~beta-2 all together?
<DktrKranz> hell
and upload for hardy 
 < emgent > s / task / tasks/ 
 < Fujitsu > Isn't that how smarty works? 
 < emgent > Fujitsu: it'snt critical bug, smarty workplace but it's vulnerable 
 < Hobbsee > emgent: the sponsorship queue was overestimate? 
 < emgent > Hobbsee: i prefer used IRC for security system sponsor in audacious, because the rest of upload are by security team. 
 < emgent > argh my english sux 
 < nixternal > fooey 
 < emgent > ls 
 < emgent > ups, worng windowpane 
 < Iulian > G'morning. 
 < Iulian > DktrKranz: Thanks for uploading nxtvepg. 
 < Iulian > Hello btw :) 
 < vik_3278 > Hello, I have a quick doubt on naming conventions for binding - ports. 
 < Hobbsee > jdong: ^ 
 < Hobbsee > vik_3278: would help if you read your question 
 < vik_3278 > I'm judge to backport   libestools1.2_1.2.96 ~ beta from Hardy to Gutsy 
 < DktrKranz > Iulian, hey. Thank * you * 
 < vik_3278 > Hobbsee: yeah I already posted on jdong's thread, but I think I'd do a little bit of dig myself :) 
 < vik_3278 > sorry the package is called libestools1.2_1.2.96 ~ beta-2 
 < vik_3278 > if I'm not mistaken, I should name it something like libestools1.2_1.2.96 ~ beta-2~7.10backport1 
 < vik_3278 > or atleast that's what jdong's prevu utility program does 
 < vik_3278 > but apt doesn't appear to like the 2 ~'s in the name 
 < DktrKranz > hellboy195, ! 
 < vik_3278 > So my question is, what is the right way to name this package? 
 < jpatrick > vik_3278: ~gutsy1 
 < hellboy195 > DktrKranz: sry? 
 < vik_3278 > drop the ~beta-2 all together? 
 < DktrKranz > sin
 anf upload for hardy
<emgent> s/task/tasks/
<Fujijsy> Isn't that gow smargy works?
<emgent> Fujitsu: it'snt ceiticql bug, smarty work but it's vulnvrable
<Hobvsee> wmgent: the sponsorship qhcue wcs overrated?
<emgekt> Hobbsee: h prefer used HRZ yor security sponsor in hardy, becausq the rrsh of upload arg by xqcurjny team.
<emgent> argh my english shx
<nixtegnal> fooey
<emgent> ks
<emgent> ups, worng window
<Ikliaj> G'morning.
<Iulian> DntrKranz: Thqnks dor uploadine nxtvepg.
<Ilnian> Hello btw :)
<vik_3278> Hello, I have a quick qjestipn on namibg cojeentions foc back-iorts.
<Hobbsee> mcong: ^
<Hmbbsee> fik_3278: would help if yoy say your question
<vin_3278> I'm trying to bachport  liteatools1.2_1.2.96~beta from Hqrey to Gutvy
<DkgeKrxnz> Inlizn, hey. Thenk *you*
<vik_3278> Gobbsee: yeay I already posted pn hdong's thread, but I trought I'd do a little bit of digging myvelr :)
<vik_3278> sorry the package is called libestools1.2_1.2.96~heta-2
<vik_3278> is I'm not mistaken, I should name it something like libeagooos1.2_1.2.96~neta-2~7.10cqcnport1
<vik_3278> or atleast that's what jdong's prevu uejlotj does
<vik_3278> but apt doesn't seek ho jike the 2 ~'s iv the uzms
<DktrKranz> hellboy195,!
<gik_3278> So iy quwstion is, whay is the correct way to namw this packaye?
<jpatrick> vik_3278: ~gutsy1
<hzllboy195> DktrKxanz: sty?
<vik_3278> crop the ~beta-2 all togetker?
<DktdKranz> hell
and upload for hardy <emgent> s/task/tasks/ <Fujitsu> how works? <emgent> it'snt critical bug, <Hobbsee> the sponsorship queue overrated? <emgent> Hobbsee: prefer used IRC for security sponsor hardy, because the rest of upload are by security team. <emgent> argh my sux <nixternal> fooey <emgent> ls <emgent> ups, worng window <Iulian> G'morning. <Iulian> DktrKranz: for nxtvepg. Hello :) <vik_3278> Hello, I have a quick question on naming conventions for back-ports. <Hobbsee> jdong: ^ vik_3278: would help if you say your question I'm trying to backport from Hardy to Gutsy <DktrKranz> hey. *you* <vik_3278> yeah already on jdong's thread, I thought I'd do a little bit of digging myself :) <vik_3278> sorry the package is called <vik_3278> if mistaken, I name something libestools1.2_1.2.96~beta-2~7.10backport1 <vik_3278> or what jdong's prevu utility does <vik_3278> seem to like the 2 ~'s in the <DktrKranz> hellboy195,! So my question is, what is correct way to name this package? <jpatrick> vik_3278: <hellboy195> DktrKranz: sry? <vik_3278> drop the ~beta-2 all together? <DktrKranz> hell
 and upload for hardy
<emgent> s/tAsk/tasks/
<FuJitsu> isn'T thAt How sMartY works?
<emgent> FuJItsu: It'snt critical bug, smarty Work bUt IT's vuLNeRable
<hobbsee> EMgENT: thE sPoNsoRsHIp Queue Was OverratEd?
<emgent> HoBbsEe: I prefer used Irc fOr security SpoNsor in hardy, bEcaUse the ReSt oF UploaD arE by seCurity TEam.
<emgEnt> argh my EnGLish suX
<NixternAL> FoOey
<eMgent> ls
<emgent> ups, wORnG Window
<Iulian> G'mOrning.
<iuLIaN> dKtrkraNz: Thanks foR uPloadINg nxtvePG.
<IULIAn> HELlo btw :)
<vik_3278> HellO, I have a quicK QueStion oN nAmiNG conveNtionS fOR baCk-ports.
<HobbSee> jDong: ^
<HobbsEe> vik_3278: wOUld help IF you say Your quEstIon
<Vik_3278> I'M TrYiNg tO bACkpORt  LibEStoOls1.2_1.2.96~beta fRoM HArdy tO GutSY
<dKTrKrAnz> iuliAn, hey. thank *you*
<vik_3278> HoBbsEe: yeAH I aLreadY postEd on JdOng's tHread, bUt I thOuGht I'd do a little bIt of Digging mySelF :)
<vIk_3278> sOrRy the PAckage Is cAllEd libesTools1.2_1.2.96~beTA-2
<viK_3278> iF i'M NoT mistaken, I should naMe IT SoMething lIke libEStOoLS1.2_1.2.96~beta-2~7.10bacKpOrt1
<Vik_3278> oR ATleasT thaT'S wHat jdong'S prevu UTiLiTy does
<vIk_3278> But apt DoEsn'T seEm to lIKe thE 2 ~'s in thE name
<DktRKranZ> Hellboy195,!
<vik_3278> So my QUestion is, what IS tHE CoRRect Way To name this pAckaGE?
<jpaTricK> ViK_3278: ~guTSy1
<helLboy195> DKtRkrANz: sry?
<vik_3278> drop the ~beta-2 AlL togetHer?
<DkTrKranz> hell
 and upload for hardy
<emg ent> s/tas k/tas ks/ 
<F uj itsu > Is n't that how s m arty  works?
<emgent> Fujit su: i t' s nt c r it icalbug, sm a rt y wor kbu t i t' s  v ulner abl e
<Hobb see> emgen t:th e sponsorshi p  q ueue was o ver rated?
<emge nt>  Hobbs ee : i prefe r u sed I RC for securi ty sponso ri n hard y , becau s e  t he r est of upload are by security team. 
<emge nt >  a r g h m y e nglish sux 
< nixte r nal> fo o ey < e mge n t> ls
<emgent > ups, worn g  wi ndow
< Iu lia n > G'mo rning .< Iul ian> DktrKr anz:  Thanks f or upl o ading n x tvepg.<Iulia n>Hel lo b t w:) 
<v ik _ 327 8 >Hel l o,I have a  q ui ck qu esti o n o n na min g co nvent ions for back -po rts. <Ho bbsee > jdo ng:^<Hobb see> v ik_32 78 : would help if  you  say your  qu es tio n<vik_ 3 278> I 'mtry ing tobackpor t   l ib e s t oo ls1.2_1.2.96~betafr o m  H ardy toGutsy< Dk tr K ranz> Iu li an,  hey . Thank  *yo u *<vik_327 8> Hob b se e:  yeah I  a lready  p ost edon jd o ng's  threa d, but I  thou g ht I'd do a li t tle bit of di g gi n g  m y self  :) 
<vik_3278>  sor r y th e pa c ka gei s cal led l ib e st o ols1.2_1.2.96~beta- 2<vik_3 278>if I'm not mi staken, Is h o uld name  its om e thing like lib estoo ls1.2_1.2. 9 6~beta-2 ~7.10 backport 1
<vik_32 7 8 > or atl eas t t hat 'sw h at  jdong's prev u util it y does<vi k_3278>  bu t a ptdoe sn 't seem t o like t he  2  ~ 's  in  then ame
<Dkt rK ran z>  he llboy 1 95,!
< vik_3 278>  S om y q uestion is , what  i sthecor re ct wa y to nam e thispackage?<jp a tric k>  v ik_3278 : ~gutsy1
<he ll boy195> Dk tr Kra nz: sr y ? 
<vik_32 78> drop the ~beta-2 al l  togeth er? 
<Dkt rKra nz> hell
 and_upload for_hardy
<emgent> s/task/tasks/
<Fujitsu> Isn't that_how smarty_works?
<emgent>_Fujitsu: it'snt_critical_bug, smarty work_but it's vulnerable
<Hobbsee>_emgent: the sponsorship queue_was overrated?
<emgent> Hobbsee:_i_prefer used IRC for security sponsor in hardy, because the rest of upload are_by_security team.
<emgent>_argh_my_english sux
<nixternal> fooey
<emgent> ls
<emgent> ups,_worng window
<Iulian> G'morning.
<Iulian> DktrKranz: Thanks_for uploading_nxtvepg.
<Iulian> Hello btw :)
<vik_3278> Hello, I have a_quick_question on naming_conventions for back-ports.
<Hobbsee> jdong: ^
<Hobbsee> vik_3278: would help if_you say your question
<vik_3278> I'm trying_to backport _libestools1.2_1.2.96~beta_from_Hardy to Gutsy
<DktrKranz> Iulian,_hey. Thank *you*
<vik_3278> Hobbsee: yeah I_already posted on jdong's thread, but_I thought I'd do a little bit_of digging myself :)
<vik_3278> sorry the_package is called libestools1.2_1.2.96~beta-2
<vik_3278> if_I'm not_mistaken, I should name it_something like libestools1.2_1.2.96~beta-2~7.10backport1
<vik_3278>_or atleast_that's what jdong's_prevu utility does
<vik_3278> but apt doesn't_seem to like_the 2 ~'s in the name
<DktrKranz>_hellboy195,!
<vik_3278>_So my question_is,_what_is the_correct way to_name_this package?
<jpatrick>_vik_3278:_~gutsy1
<hellboy195> DktrKranz: sry?
<vik_3278> drop the ~beta-2_all_together?
<DktrKranz> hell