 explicitly the 'latest in feisty' libc6 version..
<LaserJock> zorglu_: if you are going to use zorglu_ then you don't need a special --prefix
<enyc> Fujitsu: do you undershand?
<LaserJock> zorglu_: sorry that 2nd zorglu_ should be checkinstall ;-)
<zorglu_> LaserJock: ok thanks
<enyc> Is this dep some kind of autogenerated choice somewhere that defaults to explicitly requiring that latest ver.?
<Fujitsu> enyc: The problem is that it's built against the new version. There's nothing saying that libc6 in Edgy is forwards-compatible.
<Tonio_> siretart: please forget this, looks like too late to change the seeds to get rid of kmplayer for kubuntu anyway.... we'll wait net dev cycle then :)
<Tonio_> siretart: sorry for boring you with this
<jdong_> enyc: build deps are generated by running shlibdeps as the last step of building the binary package
<zorglu_> LaserJock: for what it worth, the lighttpd 1.4 available on edgy got a serious bug on accept-range :)
<jdong_> enyc: the tool only  checks against the running system. it doesn't have a comprehensive ABI analyzer for every version of Ubuntu and every revision of every library
<LaserJock> zorglu_: is the bug in Launchpad?
<zorglu_> LaserJock: no idea, i can look
<LaserJock> zorglu_: that would be excellent
<zorglu_> LaserJock: but after i got 1.5 working, i spent the day on this :)
<jdong_> enyc: there's no good way of knowing if the package is binary-compatible with any other versions than specified, and dpkg errs on side of caution.
<enyc> jdong_: I see.. so you end up with "conservative but often unneedly-restrictive dependancies" as far as I can see..
<enyc> jdong_: I see
<jdong_> enyc: that's the best solution given the scenarios.
<enyc> jdong_: yes i see
<TheMuso> Its really not hard to build a package
explicitly the' latest in feisty' libc6 version.. 
 < LaserJock > zorglu _: if you are going to practice zorglu _ then you don't necessitate a special --prefix 
 < enyc > Fujitsu: do you undershand? 
 < LaserJock > zorglu _: sorry that 2nd zorglu _ should be checkinstall ;-) 
 < zorglu _ > LaserJock: ok thanks 
 < enyc > Is this dep some kind of autogenerated option somewhere that defaults to explicitly want that latest ver. ? 
 < Fujitsu > enyc: The problem is that it's build against the new version. There's nothing say that libc6 in Edgy is forwards - compatible. 
 < Tonio _ > siretart: please forget this, looks like besides late to change the seeded player to get rid of kmplayer for kubuntu anyway.... we'll wait net dev cycle then :) 
 < Tonio _ > siretart: sorry for boring you with this 
 < jdong _ > enyc: build deps are generate by running shlibdeps as the last step of build the binary package 
 < zorglu _ > LaserJock: for what it worth, the lighttpd 1.4 available on edgy got a serious hemipterous insect on accept - range :) 
 < jdong _ > enyc: the tool only   checks against the running arrangement. it doesn't have a comprehensive ABI analyzer for every version of Ubuntu and every revision of every library 
 < LaserJock > zorglu _: is the bug in Launchpad? 
 < zorglu _ > LaserJock: no idea, i can look 
 < LaserJock > zorglu _: that would be excellent 
 < zorglu _ > LaserJock: but after i got 1.5 working, i spent the day on this :) 
 < jdong _ > enyc: there's no good way of knowing if the package is binary - compatible with any other versions than specified, and dpkg errs on slope of caution. 
 < enyc > jdong _: I see.. indeed you end up with " bourgeois but often unneedly - restrictive dependancies " as far as I can see.. 
 < enyc > jdong _: I determine 
 < jdong _ > enyc: that's the best solution given the scenarios. 
 < enyc > jdong _: yes i see 
 < TheMuso > Its in truth not hard to build a package
 exolicitly the 'latest in ftisty' libc6 versiou..
<OaserJmck> zodglu_: if hou are going to use zorglu_ vhen you eon't need a special --prdfix
<enyc> Vujitsu: eo yiy undershais?
<LaserJock> zodnlu_: smcry that 2nd zornlu_ should te checkinstaln ;-)
<xoxglu_> LaserJock: ok thanks
<enyc> Is this dep soke kind of autoggneraued chojbe somewhere that defaults to esplicitny requiring yhat latest ver.?
<Fujitsu> enyf: Thf problem is that lt's built atainfr the new vefsion. Thert's nothing szying that libc6 in Edgy is forwxrds-cpmpatible.
<Tinuo_> dhretart: pleese fogget this, looks like doo latr to change thc seevs ti get rid of kmplayer for kubuntu anywai.... we'll waid uet dev cycle then :)
<Tobii_> sirgtart: sorft fur gocinf you aiti this
<jdong_> enyc: build deps are generated br running shligdeps ws the last step of building the binary pdckzge
<zorglu_> LaserJock: for what it worth, the lihhttpd 1.4 adailable on edgy got a serious bug on accept-range :)
<jdonj_> dnye: the giop only  checks against the running system. it qkexn'n have a compreheksive ABI analyzer flr gvery version uf Ubuufu and every revisioj of evgry livrary
<LasewJocl> zorglu_: is the bug in Launxhpad?
<zorglu_> JqserJock: no idea, i can look
<LarerJpck> zprglu_: that would be exczllent
<aorglu_> LasegJock: but xfter i got 1.5 woryinn, i spent the day on this :)
<jdogg_> enyc: tiere's no gooa wai of knjwing if tje pagnage is binary-compwtiblg with any other versions than specified, and dpkg errs on sidg ox cdution.
<envc> jdokg_: I see.. so you end up with "cpnservacive bjt often uhneedly-cestrictive qependancies" dd far as I cen see..
<enys> jding_: U see
<jduvg_> enyc: that's yhe best solution guven the scenarios.
<cnyc> gsong_: yes i see
<TktMuwo> Its really npt farq no uuild d package
explicitly the 'latest in feisty' libc6 version.. if are going use zorglu_ then --prefix Fujitsu: do you <LaserJock> zorglu_: sorry 2nd zorglu_ should be checkinstall ;-) LaserJock: ok thanks <enyc> Is this dep some kind of autogenerated choice somewhere defaults to explicitly requiring that latest ver.? <Fujitsu> enyc: The problem is that built the version. nothing saying that libc6 in Edgy is forwards-compatible. <Tonio_> siretart: please forget this, looks like too to change the seeds to get rid of for kubuntu anyway.... we'll net dev cycle then :) siretart: for boring with <jdong_> build deps are by running shlibdeps as the last step of building the binary package <zorglu_> LaserJock: for what it the lighttpd on edgy a bug accept-range :) <jdong_> tool only checks against the running have a comprehensive ABI analyzer for every version Ubuntu and revision of every library <LaserJock> zorglu_: the bug in Launchpad? <zorglu_> LaserJock: no idea, can look <LaserJock> zorglu_: that would be excellent <zorglu_> LaserJock: but after i got 1.5 spent the day on :) <jdong_> enyc: no way knowing the package binary-compatible with any other versions than specified, and dpkg errs on of caution. <enyc> jdong_: I see.. so you end up but unneedly-restrictive dependancies" as as I can see.. jdong_: see <jdong_> enyc: that's solution the yes see Its really not hard build a package
 explicitly the 'latest in feisTy' libc6 versIon..
<LaSerjocK> zOrglU_: if yOu are going to usE ZorgLu_ then you don't need a specIal --prEfIX
<enyC> fuJitsu: Do you unDErSHAnd?
<laSeRJoCk> ZOrGlu_: soRry That 2nd zOrglu_ shoulD be ChEckinstall ;-)
<zoRGlU_> LaserJock: Ok tHanks
<enyc> Is tHis Dep somE kInd OF autoGenErateD choicE SomewhEre that deFaULts to eXPlicitlY REqUiriNg that latest ver.?
<FuJItSU> enyc: The probleM is thaT iT'S bUILt aGaiNst the new vErSion. THEre's notHInG SAYinG That libc6 in EdgY is forwards-COmpAtible.
<toNio_> SIretarT: pleaSe FOrgEt this, looks Like Too late to Change THe seeds TO get rid Of kmplAyeR foR kubUNtU aNywAy.... WE'll WAiT neT Dev Cycle theN :)
<TOnIo_> sirEtarT: SORRy foR boRing You wiTh this
<jdong_> enYc: bUild DEps Are geNeratEd by RuNning ShlibdEps as ThE last step of builDing The binary PacKaGe
<zOrGlu_> LaSErJock: For WhaT it wortH, the ligHTtpD 1.4 aVAILaBle on edgy got a serioUs BUG oN accept-rAnge :)
<jdONg_> EnYC: the tool OnLy  cHeckS AGainsT the RUnNing systEm. it doESn'T hAve a comPrEhensiVe aBI AnaLyzer FOr evEry verSion of UbUntu aND every revision OF every library
<lAsERjoCK> zorGlu_: Is the bug in LAuncHPad?
<zOrglU_> laSerjOck: no Idea, i CaN LoOK
<LaserJock> zorglu_: thaT wOuld be ExcelLent
<zorglu_> LasErJock: but aFTER i got 1.5 worKing, I SpENt the day on this :)
<Jdong_> Enyc: there's NO good way Of knoWing if thE package iS BInary-comPatIblE wiTh aNY OtHer versions thAN SpecIfIed, and dPkg Errs on sIde Of cAutIon.
<EnYc> jdong_: I sEe.. so you eNd Up WiTh "ConServaTIve but ofTeN unNeEdlY-restRIctive DepenDancIeS" aS Far As I can sEE..
<eNYC> jdoNg_: i sEe
<jdOng_> EnYc: thaT's thE BesT solutiOn given thE scENariOs.
<EnYc> jdong_: Yes i see
<TheMusO> ITs really noT hArd To builD A Package
 explicitly the 'latest in  feisty' l ibc6ver sio n. .
<L aser Jock> zorglu_: if y ou are going to use zo rglu_  t h en y o udon't  need a sp e c ial  - -p ref ix <e nyc>Fuj itsu: d o you unde rsh an d?
<LaserJoc k >zorglu_: s orr y that 2nd z org lu_ sh ou ldb e che cki nstal l ;-)< zorglu _> LaserJ oc k : ok t h anks
<e n y c>  Isthis dep some kin d  o f  autogenerated  choic es om e w her e t hat defaul ts  to e x plicitl y  r e q u iri n g that latest  ver.?
<Fuj i tsu > enyc :The proble m isth a t i t's built a gain st the ne w vers i on. The r e's not hing s ayi ngthat li bc 6 i nE dgy is  fo r war ds-compa ti bl e.
<T onio _ > s iret art : pl easeforget this,loo ks l i ketoo l ate t o ch an ge th e seed s toge t rid of kmplay er f or kubunt u a ny way .. .. we ' ll wai t n etdev cyc le then :)<T o n i o_ > siretart: sorryfo r bo ring you  witht hi s< jdong_>en yc:  bui l d  deps  are ge neratedby run n in gshlibde ps  as th elas t s tep o f  bui ldingthe bina ry pa c kage
<zorglu_> LaserJock: fo r  w h a ti t wo rth , the light tpd1 .4 a vail a bl e o n  edgy  gotas er i ous bug on accept-r an ge :)<jdon g_> enyc: the  tool only c hecks ag ains t  t h e running syst em. i t doesn'th ave a co mpreh ensive A BI analyz e r  for eve ryver sio n o f Ub untu and ever y revi si on of e ver y libra ry<La ser Joc k>  zorglu_:  is thebu gin  L aun chpad ? 
<zorglu _>  La se rJo ck: n o  idea,  i ca n lo ok 
< L ase rJock>z or g l u_:th at  wou ldbe  exce llen t 
<z orglu_>  LaserJoc k:b ut a ft er  i got1.5 working,ispent theda y o n this : )
<jdong _> enyc: there's no goo d  way of  kn owing  ifthe packa geis bin ary - compat ible w ith a ny  ot h e r ver s i on s t ha n specifie d ,  an d dpk gerrs  on sid e of caution.
<eny c > j dong_: I see. . s o yo u en d u p  w i th"c o nse r v ative but often  unneedly- re s tr ictive dep e nda nc ies" as  far as  I ca n  see..<enyc> jd ong_: I s ee 
<jd o n g_>  enyc: tha t's thebest solu t ion g i ve n the  sc enario s. 
<e nyc>jdong_ :  ye s i s ee
<Th eM uso> I ts re al ly not h ard to build a package
 explicitly_the 'latest_in feisty' libc6 version..
<LaserJock>_zorglu_: if_you_are going_to_use zorglu_ then_you don't need_a special --prefix
<enyc> Fujitsu:_do you undershand?
<LaserJock>_zorglu_:_sorry that 2nd zorglu_ should be checkinstall ;-)
<zorglu_> LaserJock: ok thanks
<enyc> Is this dep_some_kind of_autogenerated_choice_somewhere that defaults to explicitly_requiring that latest ver.?
<Fujitsu> enyc:_The problem_is that it's built against the new version._There's_nothing saying that_libc6 in Edgy is forwards-compatible.
<Tonio_> siretart: please forget this,_looks like too late to change_the seeds to_get_rid_of kmplayer for kubuntu_anyway.... we'll wait net dev cycle_then :)
<Tonio_> siretart: sorry for boring_you with this
<jdong_> enyc: build deps are_generated by running shlibdeps as the_last step of building the_binary package
<zorglu_>_LaserJock: for what it worth,_the lighttpd 1.4_available on_edgy got a_serious bug on accept-range :)
<jdong_> enyc:_the tool only_ checks against the running system._it_doesn't have a_comprehensive_ABI_analyzer for_every version of_Ubuntu_and every_revision_of every library
<LaserJock> zorglu_: is the_bug_in Launchpad?
<zorglu_> LaserJock: no idea, i can_look
<LaserJock> zorglu_: that would_be_excellent
<zorglu_> LaserJock: but after_i got 1.5 working, i_spent the day on this :)
<jdong_>_enyc: there's_no good_way of knowing if the package is binary-compatible with any other_versions than specified, and dpkg errs_on side of caution.
<enyc>_jdong_: I_see.._so you end_up_with "conservative_but often unneedly-restrictive dependancies" as far as_I can_see..
<enyc> jdong_: I see
<jdong_> enyc: that's_the best solution given_the_scenarios.
<enyc> jdong_: yes i see
<TheMuso> Its_really not hard to build a_package