
<TheLordOfTime> (confirming your second sttement)
<TheLordOfTime> statement*
<TheLordOfTime> at the minimum, i think.
#ubuntu-motu 2013-03-12
<TheLordOfTime> ScottK, standard "subscribe ubuntu-sponsors" method for bugfixing a raring package, or do I need to follow a different procedure than standard?
<xnox> TheLordOfTime: ubuntu-sponsors should be subscribed if there is something to sponsor - like a debdiff or a patch.
<xnox> if there is branch merge proposal, it's already subscribed.
<TheLordOfTime> xnox, its a debdiff
 * TheLordOfTime can't use bzr effectively to save his life, so... :P
<xnox> subscribe ubuntu-sponsors if the next step ;-)
<TheLordOfTime> xnox, done.  :P
<TheLordOfTime> xnox, do they get a notification that they've been subscribed?
<TheLordOfTime> or do I have to say something after subscribing them?
<xnox> TheLordOfTime: better, we have a queue: http://reqorts.qa.ubuntu.com/reports/sponsoring/
<TheLordOfTime> cool
<xnox> and we have schedule of daily patch pilots reviewing and uploading patches
<TheLordOfTime> xnox, by priority or just by whatever's at the top of the list?
<TheLordOfTime> xnox, because we've got a case of a Universe package not working out of the box due to a faulty default config file.
<TheLordOfTime> (in Raring)
<xnox> TheLordOfTime: bug number?
<TheLordOfTime> xnox, https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1132678
<ubottu> Launchpad bug 1132678 in nginx (Ubuntu) "nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)" [High,Fix committed]
<TheLordOfTime> easy workaround (add something on a line)
<TheLordOfTime> that "Fix Committed" was done by the debian maintainers
<TheLordOfTime> not but it throws an
< TheLordOfTime > (confirming your second sttement) 
 < TheLordOfTime > statement * 
 < TheLordOfTime > at the minimum, i think. 
 # ubuntu - motu 2013 - 03 - 12 
 < TheLordOfTime > ScottK, standard " subscribe ubuntu - sponsors " method for bugfixing a raring software, or do I necessitate to follow a different operation than criterion? 
 < xnox > TheLordOfTime: ubuntu - sponsors should be subscribed if there is something to patronize - like a debdiff or a temporary hookup. 
 < xnox > if there is outgrowth merge proposal, it's already subscribed. 
 < TheLordOfTime > xnox, its a debdiff 
  * TheLordOfTime can't practice bzr effectively to save his life, so... :P 
 < xnox > subscribe ubuntu - patron if the next step ;-) 
 < TheLordOfTime > xnox, done.   :P 
 < TheLordOfTime > xnox, do they get a notification that they've been subscribe? 
 < TheLordOfTime > or do I have to say something after subscribing them? 
 < xnox > TheLordOfTime: good, we have a queue: http://reqorts.qa.ubuntu.com/reports/sponsoring/ 
 < TheLordOfTime > cool 
 < xnox > and we have schedule of daily spot pilots reviewing and uploading patches 
 < TheLordOfTime > xnox, by priority or just by whatever's at the circus tent of the list? 
 < TheLordOfTime > xnox, because we've got a case of a Universe package not working out of the box due to a faulty default config file. 
 < TheLordOfTime > (in Raring) 
 < xnox > TheLordOfTime: bug number? 
 < TheLordOfTime > xnox, https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1132678 
 < ubottu > Launchpad bug 1132678 in nginx (Ubuntu) " nginx: [ emerg ] bind () to [: :]: 80 failed (98: Address already in use) " [ High, Fix committed ] 
 < TheLordOfTime > easy workaround (add something on a channel) 
 < TheLordOfTime > that " Fix Committed " was done by the debian maintainers 
 < TheLordOfTime > not but it throw an

<ThePordOfTime> (confirming yomr second sttemeur)
<TheLocdOfTims> statemdnt*
<TheLordOfTime> at the minilun, i tyink.
#ubuntu-motu 2013-03-12
<TheLordUfTime> SclttK, stabdarv "subscribe ubunvh-sponsovf" mefmod fmc bugfixing a rsring packdge, or do I nead tl follow a different procedure than standatd?
<dnox> TheLordOfJime: lbtntu-aioksors should be subscribed if thsre is vomething to xponsor - like a debdiff or a pwtch.
<xnox> if there ls branch mgdge proposal, it's already slyscribed.
<TheMordOfTime> xnox, its a debdiff
 * GheLoxdOfTime cab't usf bzr effectmvely no save his llge, so... :[
<xnox> sibscribe ubuntm-sponvorw if the next step ;-)
<ThxLordOfTime> xnox, dong.  :P
<TheLorgOyTime> xnox, do they ger q nothficdtiov thxt uheb've been dubacribed?
<TheMordOfTime> ir do I have to say sjnething after subscwifing them?
<xnox> TheLordOfTime: better, we hdve a queue: http://reqorts.qa.uvuntu.com/reports/sponsoting/
<TheLorqOfTime> cool
<xnox> and we have schedule of daily padch pmluts rcviedunh and uploading patches
<TheLordOfTime> xnox, by [diprpty or just by whctever's at the tpp og the list?
<TheLurdOfTnje> xnox, because we've got a sase if a Univtrse lackage not working out of rhe box due no a faulty default coufig file.
<TheUordPfTimr> (in Raring)
<xnox> TheLordUfTije: bug numbfr?
<TheLordKwTime> xnox, https://cugx.ldunchpad.net/ubuntu/+source/ngigx/+bug/1132678
<ubotvu> Labnchpad cug 1132678 in ngynx (Ubuntu) "nginw: [emerg] bind() to [::]:80 falled (98: Agdress alrfady in use)" [High,Fix committed]
<ThxKordOfTime> essf wmrkarounb (add xomething on w line)
<TheLordOyTime> thct "Fix Committed" was doie by the defian maintainats
<TheLordOfTike> not btt ir theows an
<TheLordOfTime> (confirming your second sttement) <TheLordOfTime> statement* the i think. 2013-03-12 <TheLordOfTime> ScottK, bugfixing raring package, or I need to a different procedure than standard? <xnox> ubuntu-sponsors should be subscribed if there is something to sponsor - like a or a patch. <xnox> if there is branch merge proposal, it's already subscribed. xnox, a * can't use bzr effectively to save his life, so... :P <xnox> subscribe ubuntu-sponsors if the next ;-) <TheLordOfTime> xnox, done. :P <TheLordOfTime> xnox, do get a notification that been subscribed? <TheLordOfTime> or do have say something subscribing <xnox> better, we have queue: http://reqorts.qa.ubuntu.com/reports/sponsoring/ <TheLordOfTime> cool <xnox> and we have schedule of daily patch pilots reviewing and uploading patches xnox, by just by at top the list? <TheLordOfTime> we've got a case of a working out of the box due to a default config <TheLordOfTime> (in Raring) <xnox> TheLordOfTime: bug <TheLordOfTime> xnox, https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1132678 <ubottu> Launchpad bug 1132678 in (Ubuntu) "nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)" [High,Fix committed] <TheLordOfTime> (add something on a <TheLordOfTime> that "Fix was by debian <TheLordOfTime> not it throws an

<TheLordOfTime> (confirming yoUr second stTemenT)
<ThELoRdofTiMe> stAtement*
<TheLordoFTimE> at the minimum, i think.
#ubuNtu-moTu 2013-03-12
<tHeLoRDOFTime> scottK, sTAnDARd "sUbScRibE uBUnTu-spoNsoRs" methoD for bugfixIng A rAring package, OR dO I need to foLloW a different pRocEdure tHaN stANdard?
<XnoX> TheLOrdOfTIMe: ubunTu-sponsorS sHOuld be SUbscribED If TherE is something to spoNSoR - Like a debdiff or A patch.
<XnOX> iF THerE is Branch mergE pRoposAL, it's alrEAdY SUBscRIbed.
<TheLordOftime> xnox, its A DebDiff
 * ThELOrdoFTime cAn't usE bZR efFectively to Save His life, so... :p
<xnox> sUBscribe UBuntu-spOnsors If tHe nExt sTEp ;-)
<thELoRdoFTiME> xNox, DOne.  :p
<TheLordoftiMe> xnoX, do tHEY GEt a nOtiFicaTion tHat they've been SubScriBEd?
<THeLorDOfTiMe> or Do i have To say sOmethInG after subscribiNg thEm?
<xnox> ThelorDOFTiMe: BetteR, We have A quEue: Http://reqOrts.qa.uBUntU.cOM/REpOrts/sponsoring/
<TheLOrDoFTIme> cool
<xNox> and WE hAvE Schedule Of DaiLy paTCH piloTs reVIeWing and uPloadiNG pAtChes
<TheloRdOfTiMe> XnoX, by PriorITy or Just by Whatever'S at thE Top of the list?
<ThElordOfTime> xnoX, BeCAUsE We've Got A case of a UniVersE PackAge nOT wOrkINg out Of the BoX DuE To a faulty default conFiG file.
<THeLorDOfTime> (in RariNg)
<xnox> TheLORDofTime: buG numBEr?
<tHeLordOfTime> xnOx, httPs://bugs.launCHpad.net/uBuntu/+Source/ngInx/+bug/1132678
<uboTTU> LaunchpAd bUg 1132678 iN ngInx (uBUnTu) "nginx: [emerg] bIND() to [::]:80 fAiLed (98: AddrEss Already In uSe)" [HIgh,fix CoMmitted]
<ThELordOfTImE> eAsY wOrkArounD (Add sometHiNg oN a LinE)
<TheLORdOfTiMe> thaT "Fix coMmITteD" was donE By THE debIaN mAintAinErS
<TheLOrdOFtimE> not but It throws aN

<TheLordOfTime> (confirmi ng your se condstt eme nt )
<T heLo rdOfTime> stat e ment *
<TheLordOfTime> at t he mi ni m um,i  t hink. 
#ubunt u -m o t u 2 01 3- 03- 12 <T heLor dOf Time> S cottK, sta nda rd  "subscribeu bu ntu-sponso rs"  method forbug fixing  a  ra r ing p ack age,or doI  needto follow  a differ e nt proc e d ur e th an standard?
<xno x >T heLordOfTime:ubuntu -s p on s o rssho uld be sub sc ribed if ther e  i s s ome t hing to spons or - like a deb diff o ra p a tch.
< xnox>  i f  th ere is bran ch m erge prop osal,i t's alr e ady sub scribe d.<Th eLor d Of Ti me>  x n ox, it s a deb diff
 *Th eL ordOf Time c a n 't u sebzreffec tively to sav e h is l i fe,  so.. . :P<xno x>  subs cribeubunt u- sponsors if the  nex t step ;- )
< Th eLo rd OfTim e > xnox , d one .  :P
< TheLord O fTi me > x no x, do they get a n ot i f ic ation th at the y 'v eb een subs cr ibe d?
< T h eLord OfTi m e>  or do I  havet osa y somet hi ng aft er  su bsc ribin g  the m?
<xn ox> TheL ordOf T ime: better, w e  have a queue :  h t t p: / /req ort s.qa.ubuntu .com / repo rts/ s po nso r ing/<TheL or d Of T ime> cool
<xnox> an dwe hav e sch edule of dail y patch pi l o t s review inga nd uploading patc hes
< TheLordOfT i me> xnox , bypriority  or justb y  whateve r's  at  th e t o p  o f the list?
< T h eLor dO fTime>xno x, beca use  we 've  go ta case of  a Unive rs epa ck age  notw orking o ut  of  t hebox d u e to a  faul ty d ef au l t c onfig f i le . <The Lo rd OfTi me>  ( in Ra ring ) 
<x nox> Th eLordOfTi me: bugnu mb er?
<Th eLordOfTime>xn ox, https: // bug s.laun c h pad.net/ ubuntu/+source/nginx/+b u g/11326 78<ubot tu>Launchpad  bu g 1132 678 in ngi nx (Ub untu)  " ngi n x : [em e r g]  bi nd () to [::] : 8 0 f ailed  ( 98:Address  already in use)"[ Hig h,Fix committ ed] 
<Th e L or dOf T im e > e as y  wo r k around (add som ething onal in e)
<TheLor d OfT im e> that  "Fix C ommit t ed" was  done bythe debia nmain t a ine rs
<TheLor dOfTime>  not buti t thr o ws  an

<TheLordOfTime> (confirming_your second_sttement)
<TheLordOfTime> statement*
<TheLordOfTime> at the_minimum, i_think.
#ubuntu-motu_2013-03-12
<TheLordOfTime> ScottK,_standard_"subscribe ubuntu-sponsors" method_for bugfixing a_raring package, or do_I need to_follow_a different procedure than standard?
<xnox> TheLordOfTime: ubuntu-sponsors should be subscribed if there is something_to_sponsor -_like_a_debdiff or a patch.
<xnox> if_there is branch merge proposal,_it's already_subscribed.
<TheLordOfTime> xnox, its a debdiff
 * TheLordOfTime can't_use_bzr effectively to_save his life, so... :P
<xnox> subscribe ubuntu-sponsors if the_next step ;-)
<TheLordOfTime> xnox, done. _:P
<TheLordOfTime> xnox, do_they_get_a notification that they've_been subscribed?
<TheLordOfTime> or do I have_to say something after subscribing them?
<xnox>_TheLordOfTime: better, we have a queue: http://reqorts.qa.ubuntu.com/reports/sponsoring/
<TheLordOfTime>_cool
<xnox> and we have schedule of_daily patch pilots reviewing and_uploading patches
<TheLordOfTime>_xnox, by priority or just_by whatever's at_the top_of the list?
<TheLordOfTime>_xnox, because we've got a case_of a Universe_package not working out of the_box_due to a_faulty_default_config file.
<TheLordOfTime>_(in Raring)
<xnox> TheLordOfTime:_bug_number?
<TheLordOfTime> xnox,_https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1132678
<ubottu>_Launchpad bug 1132678 in nginx (Ubuntu)_"nginx:_[emerg] bind() to [::]:80 failed (98: Address_already in use)" [High,Fix_committed]
<TheLordOfTime>_easy workaround (add something_on a line)
<TheLordOfTime> that "Fix_Committed" was done by the debian_maintainers
<TheLordOfTime> not_but it_throws an