
<tumbleweed> fair enough, but there are more important FTBFSs to deal with
<geser> I doubt shadeslayer is working on such a package
 * shadeslayer reads backlog
 * tumbleweed doubts so too
<shadeslayer> my main gripe is that pbuilder is not smart enough
<shadeslayer> building on armel takes time
<shadeslayer> and when you get FTBFS's.... more time is lost
<shadeslayer> so by default, pbuilder should not build arch all pacakges unless the pbuilder is a i386 pbuilder
<shadeslayer> \end gripe
<tumbleweed> shadeslayer: you can achive that with 3 lines of pbuilderrc
<geser> not in general, as it is useful to check if the arch:all package builds too before uploading even if test building on amd64
<tumbleweed> geser: totally agreed
<shadeslayer> ok, if the pbuilder is amd64 or i386, build arch all
<shadeslayer> else don't build arch all
<shadeslayer> tumbleweed: I'm talking about defaults here :)
<shadeslayer> it just doesn't make sense to me personally
<tumbleweed> shadeslayer: I think it's fairly sensible for pbuilder to build arch-all packages by default
<tumbleweed> I don't see why one wouldn't want to do that
<shadeslayer> tumbleweed: because it takes time to build pacakges on arm?
<tumbleweed> sbuild doesn't build them by default, but that's because it aims to be like a buildd
<geser> shadeslayer: and then you test-build a package you want to try which has an strict version check on e.g. -common which is arch:all and you can't install it without --force-deps
<tumbleweed> shadeslayer: right, but then you've got less confidence that your package still builds
<shadeslayer> also, this brings in a interesting question, kipi-plugins-common ftbfs on armel because of missing files, should it be made arch any?
<geser> no
<tumbleweed> I see absolutely no reason to do anything like that
<geser> why are those files missing when
< tumbleweed > fair enough, but there are more important FTBFSs to deal with 
 < geser > I doubt shadeslayer is work on such a software 
  * shadeslayer reads backlog 
  * tumbleweed doubts therefore besides 
 < shadeslayer > my main gripe is that pbuilder is not smart enough 
 < shadeslayer > construction on armel fill time 
 < shadeslayer > and when you scram FTBFS's.... more time is lost 
 < shadeslayer > indeed by default, pbuilder should not build arch all pacakges unless the pbuilder is a i386 pbuilder 
 < shadeslayer > \end gripe 
 < tumbleweed > shadeslayer: you can achive that with 3 lines of pbuilderrc 
 < geser > not in cosmopolitan, as it is useful to check if the arch: all software builds excessively before upload even if test building on amd64 
 < tumbleweed > geser: totally agree 
 < shadeslayer > ok, if the pbuilder is amd64 or i386, build arch all 
 < shadeslayer > else don't build arch all 
 < shadeslayer > tumbleweed: I'm spill the beans about defaults here :) 
 < shadeslayer > it merely doesn't make sense to me personally 
 < tumbleweed > shadeslayer: I think it's fairly sensible for pbuilder to build up arch - all packages by default 
 < tumbleweed > I don't see why one wouldn't want to do that 
 < shadeslayer > tumbleweed: because it takes time to build pacakges on arm? 
 < tumbleweed > sbuild doesn't build them by default, but that's because it aims to be like a buildd 
 < geser > shadeslayer: and then you test - build a package you want to try which have an strict version check on e.g. -common which is arch: all and you can't install it without --force - deps 
 < tumbleweed > shadeslayer: right, but then you've catch less confidence that your package still builds 
 < shadeslayer > also, this brings in a interesting question, kipi - plugins - common ftbfs on armel because of miss files, should it be made arch any? 
 < geser > no 
 < tumbleweed > I see absolutely no reason to do anything like that 
 < geser > why are those files miss when

<tumhleweed> fair enough, but uhere are more imkoetant HTBFSs fo deal dith
<geser> I doubt shadeslayec is workung on such a package
 * shadeslajer reads bacjoog
 * tumblxseed domyts sk too
<viadeslayer> my msin gripe hs that pbuildar id not smart enough
<shadeslayer> buildyng on srlel takes time
<fhadtslwyer> and when you get FTBFS's.... more time is losu
<shadeslayer> so by default, pbuilder should nlt bkild arch all pacanges unless the pbuilder is x i386 pbuildtr
<vhadeslayet> \end gripe
<tumbleweed> shadeslayef: you can achivg fhwj with 3 linew of ibuilderrc
<gescg> not it genersl, as it is uscful vo cyeck if the arch:all peckage builds too besore uploddnng even if test buileibg on amd64
<dumbuwwedd> fexed: totaply agreed
<shaseslayer> ok, if the pbuilder is aie64 or i386, build zrch ajl
<fhadeslayer> else don't build arch all
<shagesmayer> tumbleweed: I'm taljing about defaults hgre :)
<shadesjayer> it just doesn't make sense to me personally
<tgmblexedd> whwawspayer: I think it's fairly sensible for pbuildew tp nuild arch-all pagkages by default
<timhlrreed> I don't sge why one wouldn't want to dl that
<sradesoayer> tumflewred: because it takes time ti build pacahtes on arm?
<tumblewezd> sbuild dozsn't boild tnem by default, but that'r bedause it ails to be mkke a buildd
<gesef> smadaslayer: and then you test-btild a parkage you wavt tp try rhich has wn stvhct version check ln e.g. -cmmmon whicj is arch:all and you can't install it without --gosce-geps
<tumbjeweec> shadeslayer: right, but theu you've yot lers confidehce thav your packade still builgd
<shadeslayer> also, thys beingw in a kvteresting quextion, kipp-pjugibs-common ftbfs on ermeu because of miswint files, should ot ce iafe awwh any?
<geser> to
<tuobldeeed> K see absolmteuy np reason to do anythhng mike that
<geser> why ave those diles mifsing when
<tumbleweed> fair enough, but there are more to with <geser> doubt shadeslayer is * reads backlog * doubts so too my main gripe is that pbuilder not smart enough <shadeslayer> building on armel takes time <shadeslayer> and when you FTBFS's.... more time is lost <shadeslayer> so by default, pbuilder should not build all unless pbuilder a i386 pbuilder <shadeslayer> \end gripe <tumbleweed> shadeslayer: you can achive that with 3 lines of <geser> not in general, as it is useful check if the arch:all builds too before uploading even test on amd64 geser: agreed ok, if the is amd64 or i386, build arch all <shadeslayer> else don't build arch all <shadeslayer> tumbleweed: I'm talking defaults here it just make to personally <tumbleweed> shadeslayer: it's fairly sensible for pbuilder to by default <tumbleweed> I don't see why one want to that <shadeslayer> tumbleweed: because it takes to build pacakges on arm? <tumbleweed> sbuild doesn't them by default, but that's because it aims to be like a buildd <geser> shadeslayer: you test-build a package want to try has strict check e.g. -common is arch:all and you can't install it without --force-deps <tumbleweed> shadeslayer: but then you've got less confidence that your package still also, brings in a question, kipi-plugins-common ftbfs on because missing files, should it arch <geser> see no to do anything like <geser> why are those files when

<tumbleweed> fair enough, but thEre are more ImporTanT FTbFss to Deal With
<geser> I doubT ShadEslayer is working on such A packAgE
 * ShadESlAyer rEads bacKLoG
 * TUmbLeWeEd dOuBTs So too
<ShaDeslayeR> my main griPe iS tHat pbuilder iS NoT smart enouGh
<sHadeslayer> buIldIng on aRmEl tAKes tiMe
<sHadesLayer> aND when yOu get FTBFs's.... MOre timE Is lost
<sHADeSlayEr> so by default, pbuiLDeR Should not build Arch alL pACaKGEs uNleSs the pbuilDeR is a i386 PBuilder
<SHaDESLayER> \end gripe
<tumbLeweed> shadeSLayEr: you cAn AchIVe that With 3 lInES of Pbuilderrc
<gEser> Not in geneRal, as iT Is usefuL To check If the aRch:All PackAGe BuIldS tOO beFOrE upLOadIng even iF tEsT builDing ON AMD64
<tumBleWeed> Geser: Totally agreed
<ShaDeslAYer> Ok, if tHe pbuIldeR iS amd64 oR i386, builD arch AlL
<shadeslayer> elsE don'T build arcH alL
<sHadEsLayer> TUmblewEed: i'm tAlking aBout defAUltS hERE :)
<ShAdeslayer> it just doeSn'T MAkE sense to Me persONaLlY
<TumbleweEd> ShaDeslAYEr: I thInk iT'S fAirly senSible fOR pBuIlder to BuIld arcH-aLl pAckAges bY DefaUlt
<tumBleweed> I Don't sEE why one wouldn't WAnt to do that
<shADeSLAyER> tumBleWeed: because It taKEs tiMe to BUiLd pACakgeS on arM?
<tUMbLEweed> sbuild doesn't buIlD them bY defaUlt, but that's beCause it aimS TO Be like a bUildD
<GeSEr> shadeslayer: aNd theN you test-buILd a packaGe you Want to trY which has AN Strict veRsiOn cHecK on E.G. -CoMmon which is arCH:All aNd You can't InsTall it wIthOut --ForCe-dEpS
<tumbleweEd> shadesLaYeR: rIgHt, bUt theN You've got LeSs cOnFidEnce tHAt your PackaGe stIlL bUIldS
<shadesLAyER> Also, ThIs BrinGs iN a InterEstiNG quEstion, kIpi-pluginS-coMMon fTbFs On armel Because of missInG files, shouLd It bE made aRCH any?
<geseR> no
<tumbleweed> I see absoluTEly no reAsoN to do AnytHing like tHat
<Geser> wHy aRE those Files mIssinG wHen

<tumbleweed> fair enough,  but there  aremor e i mp orta nt F TBFSs to dealw ith<geser> I doubt shades layer  i s  wor k in g onsuch ap ac k a ge *  s had es l ay er re ads  backlo g
 * tumbl ewe ed  doubts so t o o<shadeslay er>  my main gri peis tha tpbu i lderisnot s mart e n ough
< shadeslay er >  build i ng on a r m el  tak es time
<shadesla y er >  and when youget FT BF S 's . . ..mor e time islo st
<s h adeslay e r> s o  by default, pbui lder should not  build  a rch all pa cakge su nle ss the pbui lder  is a i38 6 pbui l der
<sh a deslaye r> \en d g rip e
<t u mb le wee d> sha d es lay e r:you canac hi ve th at w i t h 3 li nes  ofpbuil derrc
<geser>  no t in gen eral,  as i t is  u seful  to ch eck i fthe arch:all pa ckag e buildstoo  b efo re  uplo a ding e ven  if  test b uilding onam d 6 4 
< tumbleweed> geser:  t o t al ly agree d
<sha d es la y er> ok,if  th e pb u i lderis a m d6 4 or i38 6, bui l dar ch all<s hadesl ay er>  el se do n 't b uild a rch all<shad e slayer> tumble w eed: I'm talk i ng a bo u t de fau lts here :) 
<sh a desl ayer >  i t j u st do esn't  m a ke sense to me persona ll y
<tum blewe ed> shadeslay er: I thin k i t's fair ly s e ns i ble for pbuild er to  build arc h -all pac kages  by defa ult
<tumb l e weed> Idon 'tsee  wh y on e wouldn't wa n t  todo  that
< sha deslaye r>tum ble wee d:  becauseit takes  t im eto  bu ild p a cakges o narm ?<tu mblew e ed> sb uilddoes n' tb uil d themb yd e faul t,  b ut t hat 's  beca usei t a ims tobe like a  bu i ldd<g es er> sha deslayer: and  t hen you te st -bu ild ap a ckage yo u want to try which has an stri ctversi on c heck on e .g.  -comm onw hich i s arch :allan d y o u  can' t in sta ll  it withou t --f orce- de ps
< tumblew eed> shadeslayer:r igh t, but then y ou' ve g o t  l ess co n fid en c e t h a t your packagestill buil ds <s hadeslayer >  al so , thisbringsin ai nterest ing quest ion, kipi -p lugi n s -co mmon ftbfs  on arme l because of mi s si ng fi les , shou ld  it  be m ade ar c h a ny?
< geser>  n o
<tum blewe ed > I seeabsolutely no reason to  do an ythin g l ike that<ge s er>  why arethos e files mi ssi ngwhen

<tumbleweed> fair_enough, but_there are more important_FTBFSs to_deal_with
<geser> I_doubt_shadeslayer is working_on such a_package
 * shadeslayer reads_backlog
 * tumbleweed_doubts_so too
<shadeslayer> my main gripe is that pbuilder is not smart enough
<shadeslayer> building on_armel_takes time
<shadeslayer>_and_when_you get FTBFS's.... more time_is lost
<shadeslayer> so by default,_pbuilder should_not build arch all pacakges unless the pbuilder_is_a i386 pbuilder
<shadeslayer>_\end gripe
<tumbleweed> shadeslayer: you can achive that with 3_lines of pbuilderrc
<geser> not in general,_as it is_useful_to_check if the arch:all_package builds too before uploading even_if test building on amd64
<tumbleweed> geser:_totally agreed
<shadeslayer> ok, if the pbuilder is_amd64 or i386, build arch all
<shadeslayer>_else don't build arch all
<shadeslayer>_tumbleweed: I'm_talking about defaults here :)
<shadeslayer>_it just doesn't_make sense_to me personally
<tumbleweed>_shadeslayer: I think it's fairly sensible_for pbuilder to_build arch-all packages by default
<tumbleweed> I_don't_see why one_wouldn't_want_to do_that
<shadeslayer> tumbleweed: because_it_takes time_to_build pacakges on arm?
<tumbleweed> sbuild doesn't_build_them by default, but that's because it_aims to be like_a_buildd
<geser> shadeslayer: and then_you test-build a package you_want to try which has an_strict version_check on_e.g. -common which is arch:all and you can't install it without_--force-deps
<tumbleweed> shadeslayer: right, but then you've_got less confidence that_your package_still_builds
<shadeslayer> also, this_brings_in a_interesting question, kipi-plugins-common ftbfs on armel because_of missing_files, should it be made arch_any?
<geser> no
<tumbleweed> I see_absolutely_no reason to do anything like_that
<geser> why are those files missing_when