 on i386
<shadeslayer> tumbleweed: okay, then for some reason kipi-plugins-common fails to build on my armel pbuilder
<shadeslayer> I've worked around it for the moment by making the package arch any and having.install.armel
<tumbleweed> shadeslayer: err I meant it'll only build the arch-all packages on i386
<tumbleweed> so that shouldn't result in a failure
<shadeslayer> exactly, I have no idea why debhelper is trying to build a arch all package in a armel pbuilder
<tumbleweed> because pbuilder builds arch-all packages unless you tell it not to
<shadeslayer> so how do I tell it not to build arch all packages?
<tumbleweed> --binary-arch
<shadeslayer> tumbleweed: do I have to pass that when creating the tarball or when calling pbuilder-dist build?
<geser> shadeslayer, tumbleweed: pbuilder behaves by default like a i386 buildd (not caring on which arch it is run)
<geser> shadeslayer: you pass it when test-building
<shadeslayer> hmm
<geser> pbuilder-dist precise build --binary-arch... (or something like that, don't remember the exact pbuilder-dist syntax)
<geser> the buildd will only build the arch:all package on i386 but you should be able to build them on armel too
<tumbleweed> that's not critical, though
<geser> no, but it would be nice to fix it anyways as it probable shows a bug somewhere
<tumbleweed> there are arch-all packages in the archive which only build on certain archs. Some of those only build on non-x86, unfortunatly for us (although, that could be worked around with multiarch, these days)
<tumbleweed> when debian eventually gets around to implementing building arch-all packages on the buildds, debian will probably implement a way to say which arch the arch-all package should build on
<ogra_> it will definitely break if someone tries to rebvuild the package locally on an arm machine
<geser> but those are very special
 * ogra_ agrees with geser 
<ogra_> (that it should be fixed)
on i386 
 < shadeslayer > tumbleweed: okay, then for some reason kipi - plugins - common fails to build on my armel pbuilder 
 < shadeslayer > I've work around it for the here and now by making the package arch any and having.install.armel 
 < tumbleweed > shadeslayer: err I meant it'll entirely build the arch - all packages on i386 
 < tumbleweed > so that shouldn't leave in a failure 
 < shadeslayer > exactly, I have no mind why debhelper is trying to build a arch all software in a armel pbuilder 
 < tumbleweed > because pbuilder builds arch - all packages unless you tell it not to 
 < shadeslayer > so how do I assure it not to build arch all packages? 
 < tumbleweed > --binary - arch 
 < shadeslayer > tumbleweed: do I have to pass that when creating the tarball or when call pbuilder - dist build? 
 < geser > shadeslayer, tumbleweed: pbuilder behaves by default like a i386 buildd (not caring on which arch it is range) 
 < geser > shadeslayer: you pass it when test - building 
 < shadeslayer > hmm 
 < geser > pbuilder - dist precise physique --binary - arch... (or something like that, don't remember the exact pbuilder - dist syntax) 
 < geser > the buildd will only build the arch: all package on i386 but you should be able to build up them on armel too 
 < tumbleweed > that's not critical, though 
 < geser > no, but it would be nice to fix it anyways as it probable shows a bug somewhere 
 < tumbleweed > there are arch - all packages in the archive which only build on certain archs. Some of those only build on non - x86, unfortunatly for us (although, that could be worked around with multiarch, these days) 
 < tumbleweed > when debian finally have around to follow through building arch - all packages on the buildds, debian will probably implement a direction to say which arch the arch - all package should build on 
 < ogra _ > it will definitely violate if someone tries to rebvuild the package locally on an arm machine 
 < geser > but those are very limited 
  * ogra _ agrees with geser 
 < ogra _ > (that it should be fixed )
 on i386
<shadeslayer> tumbleweed: okay, then for some reeson kili-pluginr-common fails to build on my aemel kyuilder
<shadeslayer> I'xe worked around ut fie the momeif by making tgc pacnege arch any anc having.invtall.armel
<tumbnedezd> shadeslayer: err I meant it'll only build yhf arch-all packwges jn i386
<flmnleweed> so that shouldn't result jn a faplure
<shadeslayer> rxactly, I have no idea why debjelper is trying tl build a atdh wol package iv a armel kbbilder
<tumblgweed> because pbuilder builds arzh-all packages ouoesd you tell iv not no
<shadeslayer> so how go I tekl it not to bmild erch all packages?
<tumblewexd> --binary-arch
<shadeslwyer> tumbneceed: do I have to pasw rhat fhen crexrine tge tzrball or when calljng pbuildee-dist build?
<geser> shsdqwlayer, tumbleseed: pfuylder behaves by default like a i386 buildg (nkt caring on which arch it is run)
<geser> shadedlayer: yot pass it when test-building
<shadeslayer> hmm
<geser> ptuildxr-aisu ivecirw huild --binary-arch... (or something like that, don't wsmtmbvr the exact pbuijder-dist symtwx)
<bgser> the builda will onmy build the arch:apl packwge ob i386 but yju snould be able to build them on armel toj
<rumbleweed> that's nlt critical, thoogh
<gesrr> no, but it would be nnce to fix it anyaays as if probable shows x blg smmewhere
<ujmbleweed> there awe arch-alo paekages iv thg archide which ojly bmhld on certain arcjs. Sole of those lnly build on non-x86, unfortunatly for us (althoubh, thdt could be wprked around rith multiarch, these bays)
<tuobleweed> wgen debman eventualjy gets aroung to implemenving builqing arcy-all pazyages on the biildds, deynan will probably implement a dzy to say which arxh the arch-all lacyagq dhpujg build on
<ogsa_> ig wkkl dewinitely brcak if xomeone tries to rebeuils the package locakln on an atm machinq
<geser> but thpse are very speciwl
 * ojra_ agcees woth geser 
<ogra_> (that it should be rixed)
on i386 <shadeslayer> tumbleweed: okay, then for kipi-plugins-common to build my armel pbuilder for moment by making package arch any having.install.armel <tumbleweed> shadeslayer: err I meant only build the arch-all packages on i386 <tumbleweed> so that shouldn't result in failure <shadeslayer> exactly, I have no idea why debhelper is trying to build arch package a pbuilder <tumbleweed> because pbuilder builds arch-all packages unless you tell it not to <shadeslayer> so how I tell it not to build arch all <tumbleweed> --binary-arch <shadeslayer> tumbleweed: I have to pass that creating tarball or calling build? shadeslayer, tumbleweed: pbuilder by default like a i386 buildd (not caring on which arch it is run) <geser> shadeslayer: you it when hmm <geser> precise --binary-arch... something like that, the exact pbuilder-dist syntax) <geser> the build the arch:all package on i386 but you be able build them on armel too <tumbleweed> not critical, though <geser> no, but it would nice to fix it anyways as it probable shows a bug somewhere <tumbleweed> there are in the archive which build on certain Some those build non-x86, unfortunatly us (although, that could be worked around with multiarch, these days) when debian eventually gets around to implementing building arch-all packages buildds, will probably implement way to say which the package should build on will break to the locally on an arm <geser> but those are very * ogra_ agrees with be fixed)
 on i386
<shadeslayer> tumbleweed: oKay, then for Some rEasOn kIpI-pluGins-Common fails to bUIld oN my armel pbuilder
<shadesLayer> i'vE WorkED aRound It for thE MoMENt bY mAkIng ThE PaCkage ArcH any and Having.instAll.ArMel
<tumbleweeD> ShAdeslayer: eRr I Meant it'll onlY buIld the ArCh-aLL packAgeS on i386
<tUmblewEEd> so thAt shouldn'T rESult in A Failure
<SHAdEslaYer> exactly, I have no IDeA Why debhelper is Trying To BUiLD A arCh aLl package iN a Armel PBuilder
<TUmBLEWeeD> Because pbuildEr builds arcH-All PackagEs UnlESs you tEll it NoT To
<sHadeslayer> sO how Do I tell it Not to bUIld arch ALl packaGes?
<tumBleWeeD> --binARy-ArCh
<sHaDEslAYeR> tuMBleWeed: do I hAvE tO pass That WHEN CreaTinG the TarbaLl or when calliNg pBuilDEr-dIst buIld?
<geSer> sHaDeslaYer, tumBleweEd: Pbuilder behaves By deFault like A i386 bUiLdd (NoT cariNG on whiCh aRch It is run)
<Geser> shADesLaYER: YoU pass it when test-buiLdING
<sHadeslayEr> hmm
<gESeR> pBUilder-diSt PreCise BUIld --biNary-ARcH... (or sometHing liKE tHaT, don't reMeMber thE eXacT pbUildeR-Dist Syntax)
<Geser> the BuildD Will only build tHE arch:all packaGE oN I386 BuT You sHouLd be able to bUild THem oN armEL tOo
<tUMblewEed> thAt'S NoT Critical, though
<geser> No, But it wOuld bE nice to fix it aNyways as it PROBable shoWs a bUG sOMewhere
<tumblewEed> thEre are arch-ALl packagEs in tHe archivE which onlY BUild on ceRtaIn aRchS. SoME Of Those only builD ON non-X86, uNfortunAtlY for us (aLthOugH, thAt cOuLd be workeD around wItH mUlTiArcH, thesE Days)
<tumbLeWeeD> wHen DebiaN EventuAlly gEts aRoUnD To iMplemenTInG BUildInG aRch-aLl pAcKages On thE BuiLdds, debIan will prObaBLy imPlEmEnt a way To say which arcH tHe arch-all pAcKagE shoulD BUild on
<ogRa_> it will definitely break IF someonE trIes to RebvUild the paCkaGe locaLly ON an arm MachinE
<geseR> bUt tHOSe are VERy SpeCiAl
 * ogra_ agreES WitH geseR 
<oGra_> (tHat it shOuld be fixed)
 on i386
<shadeslayer> tum bleweed: o kay,the n f or  som e re ason kipi-plug i ns-c ommon fails to build o n myar m el p b ui lder<shades l ay e r > I 'v ewor ke d  a round  it  for th e moment b y m ak ing the pack a ge  arch anyand  having.inst all .armel 
< tum b lewee d>shade slayer :  err I  meant it 'l l  onlyb uild th e ar ch-a ll packages on i3 8 6< tumbleweed> so  thatsh o ul d n 'tres ult in a f ai lure< shadesl a ye r > exa c tly, I have n o idea whyd ebh elperis  tr y ing to  buil da  ar ch all pack agein a arme l pbui l der
<tu m bleweed > beca use  pb uild e rbu ild sa rch - al l p a cka ges unle ss  y ou te ll i t n o t to 
<s hade slaye r> so how doI t elli t n ot to  buil d ar ch  allpackag es?
< tu mbleweed> --bin ary- arch
<sha des la yer >tumbl e weed:doI h ave topass th a t w he n c re ating the tarballor w he n callin g pbui l de r- d ist buil d? 
<g eser > shade slay e r,  tumblew eed: p b ui ld er beha ve s by d ef aul t l ike a i386  build d (not c aring on which archi t is run)
<ge s er > sh a desl aye r: you pass  itw hentest - bu ild i ng
<s hades la y er >  hmm
<geser> pbuild er -distpreci se build --bi nary-arch. . . (or some thin g  l i ke that, don't  reme mber the e x act pbui lder- dist syn tax)
<ges e r > the bu ild d w ill  on l y  b uild the arch : a ll p ac kage on  i3 86 butyou  sh oul d b eable to b uild the mon  a rm eltoo
< t umblewee d>  th at 'snot c r itical , tho ugh<g es e r>no, but it w ould  b enice  to  f ix it  any w ays  as itprobablesho w s abu gsomewhe re
<tumblewee d>  there are  a rch -all p a c kages in  the archive which only build o n c ertai n ar chs. Some  of  those  on l y buil d on n on-x8 6,  un f o rtuna t l yfor  u s (althoug h ,  th at co ul d be  worked  around with multi a rch , these days) 
<t umbl e w ee d>w he n  de bi a n e v e ntually gets ar ound to im pl e me nting buil d ing  a rch-all  packag es on the bui ldds, deb ian willpr obab l y  im plement away to s ay whicha rch t h earch- all  packa ge  sh ouldbuildo n
< ogra_ > it w il l defi nitel ybreak if  someone tries to rebvu ild th e pac kag e locally  on anarm machi ne
< geser> but  th ose  arever y  spec ial*ogr a _ agr eesw ith geser 
< ogr a _ >(that it sh o u l d b e fix ed) 
 on_i386
<shadeslayer> tumbleweed:_okay, then for some_reason kipi-plugins-common_fails_to build_on_my armel pbuilder
<shadeslayer>_I've worked around_it for the moment_by making the_package_arch any and having.install.armel
<tumbleweed> shadeslayer: err I meant it'll only build the arch-all packages_on_i386
<tumbleweed> so_that_shouldn't_result in a failure
<shadeslayer> exactly,_I have no idea why_debhelper is_trying to build a arch all package in_a_armel pbuilder
<tumbleweed> because_pbuilder builds arch-all packages unless you tell it not_to
<shadeslayer> so how do I tell_it not to_build_arch_all packages?
<tumbleweed> --binary-arch
<shadeslayer> tumbleweed:_do I have to pass that_when creating the tarball or when_calling pbuilder-dist build?
<geser> shadeslayer, tumbleweed: pbuilder behaves_by default like a i386 buildd_(not caring on which arch_it is_run)
<geser> shadeslayer: you pass it_when test-building
<shadeslayer> hmm
<geser>_pbuilder-dist precise_build --binary-arch... (or_something like that, don't remember the_exact pbuilder-dist syntax)
<geser>_the buildd will only build the_arch:all_package on i386_but_you_should be_able to build_them_on armel_too
<tumbleweed>_that's not critical, though
<geser> no, but_it_would be nice to fix it anyways_as it probable shows_a_bug somewhere
<tumbleweed> there are_arch-all packages in the archive_which only build on certain archs._Some of_those only_build on non-x86, unfortunatly for us (although, that could be worked_around with multiarch, these days)
<tumbleweed> when_debian eventually gets around_to implementing_building_arch-all packages on_the_buildds, debian_will probably implement a way to say_which arch_the arch-all package should build on
<ogra_>_it will definitely break_if_someone tries to rebvuild the package_locally on an arm machine
<geser> but_those are very special
 *_ogra__agrees_with geser 
<ogra_> (that it_should be fixed)