 it until after MoM and DaD are merged as currently there are two grab-merge.sh
<RainCT> jdong: is os.uname[4] the host architecture?
<RainCT> (like dpkg-architecture which has host architecture and build architecture)
 * RainCT really hopes so as using this the script is 4 times faster than with dpkg-architecture
<jdong> RainCT: yeah this would be host architecture
<RainCT> jdong: great. thanks
<jdong> RainCT: dpkg-architecture uses gcc -dumpmachine
<jdong> /usr/bin/dpkg-architecture  0.07s user 0.01s system 97% cpu 0.082 total
<jdong> and you're sure that is going to be a speedup?
<RainCT> jdong: I get "real 0m0.344s, user 0m0.156s, sys 0m0.028s" here
<jdong> hmm
<RainCT> and for pbuilder-dist right now "real 0m0.243s, user 0m0.040s, sys 0m0.028s"
<RainCT> * real 0m0.130s
<RainCT> 240 ms when the.pyc is outdated
<RainCT> (will get a bit slower as there's still some stuff missing, but in any case it'll be a lot faster than before :))
<awen_> A freeze exception for a new package... is it correctly understood, that I should have it reviewed in REVU before having a chance?
<RainCT> awen_: no, first get the Freeze Exception
<awen_> RainCT: so subscribe "motu-release" to the bug-report with the files attached (or a link to the package in motu)?
<RainCT> awen_: yes (with link to the package in REVU). remember that the bug description has to contain a rationale about why you think it's important to get it in now
<ScottK2> RainCT: Actually he's right
<ScottK2> awen_ needs a reviewed package for an FFe.
<RainCT> oh
<RainCT> that a bit ironic then.. I though most MOTU's only review new packages if they have a FFe
<RainCT
it until after MoM and DaD are merged as currently there are two grab-merge.sh 
 < RainCT > jdong: is os.uname[4 ] the server computer architecture? 
 < RainCT > (like dpkg - architecture which has server computer architecture and build architecture) 
  * RainCT really hop so as using this the handwriting is 4 prison term faster than with dpkg - computer architecture 
 < jdong > RainCT: yeah this would be host architecture 
 < RainCT > jdong: great. thanks 
 < jdong > RainCT: dpkg - architecture use gcc -dumpmachine 
 < jdong > /usr / bin / dpkg - architecture   0.07s exploiter 0.01s system 97% cpu 0.082 sum 
 < jdong > and you're sure that is going to be a speedup? 
 < RainCT > jdong: I perplex " real 0m0.344s, user 0m0.156s, sys 0m0.028s " here 
 < jdong > hmm 
 < RainCT > and for pbuilder - dist right now " actual 0m0.243s, user 0m0.040s, sys 0m0.028s " 
 < RainCT > * real 0m0.130s 
 < RainCT > 240 ms when the.pyc is outdated 
 < RainCT > (will get a bit slower as there's however some stuff missing, but in any case it'll be a lot faster than before :)) 
 < awen _ > A freeze exception for a new package... is it correctly understood, that I should have it reviewed in REVU before having a chance? 
 < RainCT > awen _: no, first get the Freeze Exception 
 < awen _ > RainCT: so subscribe " motu - release " to the hemipterous insect - report with the files attach (or a radio link to the package in motu)? 
 < RainCT > awen _: yes (with link to the software in REVU). remember that the hemipterous insect description has to contain a rationale about why you remember it's important to get it in now 
 < ScottK2 > RainCT: Actually he's right 
 < ScottK2 > awen _ needs a reviewed software for an FFe. 
 < RainCT > oh 
 < RainCT > that a bit ironic then.. I though most MOTU's only review new packages if they have a FFe 
 < RainCT
 it until after MoM and DaD are merged as eyrrentny thede are tdo grab-merge.sh
<RainCT> jdong: id is.unane[4] the host architectufe?
<RainCT> (pike dpkt-arciitecture which izs host archifccturz end build archijecture)
 * RaitCT really hopas sl as using this the script is 4 timef fastet hhan with dpkg-wrchptqctudv
<jbong> RainCT: yeah this would be gost arbhitecture
<RainCT> kdong: great. thanks
<jdong> RalnCT: dpkg-architecture kses gcc -dunpmasyine
<jdong> /usf/bin/dpkg-arbkitecture  0.07a user 0.01s system 97% cpu 0.082 total
<jdone> and you're surg fhwj is going ti be w speedup?
<RaikBT> jdonc: I get "real 0m0.344s, user 0k0.156s, vys 0m0.028s" here
<jdong> hmm
<RainRT> and for pbuilder-dyst right nkw "real 0m0.243s, user 0m0.040w, wys 0m0.028v"
<RaitCT> * eeau 0m0.130a
<ReinDT> 240 ms whxn the.pyc ia outdated
<RqinCT> (will get a biu sjiwer as there'a stilj fome stuff missing, but in any case it'll be a lot faster than befoee :))
<awen_> A freeze excektion for w new package... is it correctly understood, that I svould favt lb rexueaed in REVU before having a chance?
<RainCT> awen_: ho, fprst get the Freede Exception
<awen_> RsijCY: so subscribe "motu-rzmezse" to the bug-repogt with the diles attwchec (or a link to the package un motu)?
<RainCN> awwn_: yes (with link tl the packaye in TEVU). rrmember that the bug dercriltion has tl contain x rationale aboug wmy fou think it's important to get it ii now
<XcottK2> FainVT: Acttally he's gight
<ScottK2> awen_ needs a revigwed pdckage for an FFe.
<RainCT> oh
<RainCT> that a bmv ironic then.. I thmugh mosc MOTU'x only review new packages nf they kave a FFe
<RainCT
it until after MoM and DaD are currently are two <RainCT> jdong: is (like which has host and build architecture) RainCT really hopes so as using the script is 4 times faster than with dpkg-architecture <jdong> RainCT: yeah this be host architecture <RainCT> jdong: great. thanks <jdong> RainCT: dpkg-architecture uses gcc -dumpmachine /usr/bin/dpkg-architecture user system cpu 0.082 total <jdong> and you're sure that is going to be a speedup? <RainCT> jdong: get "real 0m0.344s, user 0m0.156s, sys 0m0.028s" here hmm <RainCT> and for right now "real 0m0.243s, user sys <RainCT> * 0m0.130s 240 when the.pyc is <RainCT> (will get a bit slower as there's still some stuff missing, but in any case it'll a lot before :)) A exception a new package... correctly understood, that I should have REVU before having a chance? <RainCT> awen_: no, get the Exception <awen_> RainCT: so subscribe "motu-release" the bug-report with the files attached (or a to the package in motu)? <RainCT> awen_: yes (with link to the package in REVU). the bug description has contain a rationale why think important get it now <ScottK2> RainCT: Actually he's right <ScottK2> awen_ needs a reviewed for an FFe. <RainCT> oh <RainCT> that a bit ironic though MOTU's only review packages if they have FFe
 it until after MoM and DaD are mErged as curRentlY thEre ArE two Grab-Merge.sh
<RainCT> jDOng: iS os.uname[4] the host architeCture?
<raINCT> (lIKe Dpkg-aRchitecTUrE WHicH hAs HosT aRChItectUre And builD architectUre)
 * raInCT really hoPEs So as using tHis The script is 4 tImeS fasteR tHan WIth dpKg-aRchitEcture
<JDong> RaInCT: yeah tHiS Would bE Host arcHITeCturE
<RainCT> jdong: great. THaNKs
<jdong> RainCT: dPkg-arcHiTEcTURe uSes Gcc -dumpmacHiNe
<jdoNG> /usr/bin/DPkG-ARChiTEcture  0.07s user 0.01s sYstem 97% cpu 0.082 totAL
<jdOng> and YoU're SUre thaT is goInG To bE a speedup?
<RaInCT> Jdong: I get "Real 0m0.344s, USer 0m0.156s, syS 0M0.028s" here
<jDong> hmM
<RaInCt> and FOr PbUilDeR-DisT RiGht NOw "rEal 0m0.243s, useR 0m0.040S, sYs 0m0.028s"
<RAinCt> * REAL 0m0.130s
<RAincT> 240 ms When tHe.pyc is outdatEd
<RAinCt> (WilL get a Bit slOwer As There'S still Some sTuFf missing, but in aNy caSe it'll be a Lot FaSteR tHan beFOre :))
<aweN_> A fReeZe excepTion for A New PaCKAGe... Is it correctly underStOOD, tHat I shouLd have IT rEvIEwed in REvU BefOre hAVIng a cHancE?
<raInCT> awen_: No, firsT GeT tHe FreezE EXceptiOn
<AweN_> RaInCT: sO SubsCribe "mOtu-releaSe" to tHE bug-report with THe files attachED (oR A LiNK to tHe pAckage in motU)?
<RaiNcT> awEn_: yeS (WiTh lINk to tHe pacKaGE iN rEVU). remember that the BuG descrIptioN has to contain A rationale ABOUt why you ThinK It'S Important to get It in nOw
<ScottK2> RaINCT: ActuaLly he'S right
<ScOttK2> awen_ nEEDs a revieWed PacKagE foR AN Ffe.
<RainCT> oh
<RaiNct> thaT a Bit ironIc tHen.. I thoUgh MosT MOtU's OnLy review nEw packagEs If ThEy HavE a FFe
<rAinCT
 it until after MoM and Da D are merg ed as  cu rre nt ly t here  are two grab- m erge .sh
<RainCT> jdong: is  os.u na m e[4] th e hos t archi t ec t u re? 
< Ra inC T> (l ike d pkg -archit ecture whi chha s host archi t ec ture and b uil d architectu re) 
 * Ra in CTr eally  ho pes s o as u s ing th is the sc ri p t is 4 times f a s te r th an with dpkg-arch i te c ture
<jdong> R ainCT:  y e ah t his  wo uld be hos tarchi t ecture< Ra i n C T>j dong: great.thanks
<jdo n g>RainCT :dpk g -archi tectu re use s gcc -dump mach ine
<jdon g> /us r /bin/dp k g-archi tectur e 0.0 7s u s er  0 .01 ss yst e m97% cpu  0.082 t ot al 
<jdo ng>a n d you' resure  that  is going tobea sp e edu p?
<R ainCT > jd on g: Iget "r eal 0 m0 .344s, user 0m0 .156 s, sys 0m 0.0 28 s"he re
<j d ong> h mm<Ra inCT> a nd forp bui ld e r - di st right now "real  0 m 0 .2 43s, use r 0m0. 0 40 s, sys 0m0. 02 8s" 
<Ra i n CT> *  rea l  0 m0.130s<RainC T >24 0 ms wh en  the.p yc  is  ou tdate d 
<Ra inCT>(will ge t a b i t slower as th e re's still so m es t uf f  mis sin g, but in a ny c a se i t'll be  al ot fa sterth a nb efore :))
<awen_> A  f reezeexcep tion for a ne w package. . . is it co rrec t ly understood, th at Ishould hav e  it revi ewedin REVUbefore ha v i ng a cha nce ?
< Rai nCT > aw en_: no, firs t getth e Freez e E xceptio n
< awe n_>  Ra in CT: so su bscribe"m ot u- re lea se" t o  the bug -r epo rt  wi th th e  files  atta ched  ( or a l ink tot he p acka ge  i n mo tu) ?<Rain CT>a wen _: yes(with lin k t o  the  p ac kage in  REVU). remem be r that the  b ugdescri p t ion hasto contain a rationalea bout wh y y ou th inkit's impo rta nt toget it innow
<S cottK 2>  Ra i n CT: A c t ua lly  h e's right< S cot tK2>aw en_needs a  reviewed packagef oran FFe.
<Rain CT>  oh< R ai nCT >  t h atab iti r onic then.. I t hough most  M O TU 's only re v iew  n ew pack ages if  they have aFFe
<Rain CT
 it_until after_MoM and DaD are_merged as_currently_there are_two_grab-merge.sh
<RainCT> jdong: is_os.uname[4] the host_architecture?
<RainCT> (like dpkg-architecture which_has host architecture_and_build architecture)
 * RainCT really hopes so as using this the script is 4_times_faster than_with_dpkg-architecture
<jdong>_RainCT: yeah this would be_host architecture
<RainCT> jdong: great. thanks
<jdong>_RainCT: dpkg-architecture_uses gcc -dumpmachine
<jdong> /usr/bin/dpkg-architecture  0.07s user 0.01s_system_97% cpu 0.082_total
<jdong> and you're sure that is going to be_a speedup?
<RainCT> jdong: I get "real_0m0.344s, user 0m0.156s,_sys_0m0.028s"_here
<jdong> hmm
<RainCT> and for_pbuilder-dist right now "real 0m0.243s, user_0m0.040s, sys 0m0.028s"
<RainCT> * real 0m0.130s
<RainCT>_240 ms when the.pyc is outdated
<RainCT> (will_get a bit slower as there's_still some stuff missing, but_in any_case it'll be a lot_faster than before_:))
<awen_> A_freeze exception for_a new package... is it correctly_understood, that I_should have it reviewed in REVU_before_having a chance?
<RainCT>_awen_:_no,_first get_the Freeze Exception
<awen_>_RainCT:_so subscribe_"motu-release"_to the bug-report with the files_attached_(or a link to the package in_motu)?
<RainCT> awen_: yes (with_link_to the package in_REVU). remember that the bug_description has to contain a rationale_about why_you think_it's important to get it in now
<ScottK2> RainCT: Actually he's right
<ScottK2>_awen_ needs a reviewed package for_an FFe.
<RainCT> oh
<RainCT> that_a bit_ironic_then.. I though_most_MOTU's only_review new packages if they have a_FFe
<RainCT