 really.
<Fujitsu> In fact, it's fewer.
<jdong> enyc: usually those version numbers were put there to force a build in feisty against a newer library
<Fujitsu> Go the the package page, click on version. Done.
<Fujitsu> (and click on the portlet title if you haven't got the Greasemonkey script)
<geser> LaserJock: no, I haven't filed one yet
<jdong> enyc: for backports where that is the only modification, I think I can convince cjwatson/Mithrandir to upload a source-change backport
<enyc> jdong: hrrm build-dep or  compiled dependancy??
<jdong> enyc: build-dep
<LaserJock> geser: I can do it if you don't want to
<enyc> jdong: right... but ive many times needed to change the binary-runtime-dependancies.....
<LaserJock> geser: otherwise just ping me with the bug  number
<jdong> enyc: like which packages?
<enyc> jdong: e.g. to run an edgy binary package on dapper or whatever
<Fujitsu> enyc: You're meant to rebuild them to do that. That's what backporting is.
<jdong> you should not be running edgy binaries on anything but edgy
<jdong> you must rebuild its source package on the intended distribution.
<enyc> jdong: hrrm thats very often not necessay in my experience...
<jdong> a binary runtime dependency is for real
<geser> LaserJock: filing now
<jdong> that's generated from scanning the binary.
<Tonio_> siretart: ping?
<jdong> enyc: it's russian roulette when you do that. it may work, it may crash, nobody knows.
<jdong> but it's not supported in any way, and you're on your own.
<siretart> Tonio_: pong
<enyc> jdong: that really depends if there is an ABI change or an actual requiremnet for newer lib or initscript-behaviour...
<enyc> hangon... ill try to find an example...
really. 
 < Fujitsu > In fact, it's fewer. 
 < jdong > enyc: usually those version number were place there to force a build in feisty against a newer library 
 < Fujitsu > become the the package page, click on adaptation. Done. 
 < Fujitsu > (and click on the portlet championship if you haven't got the Greasemonkey script) 
 < geser > LaserJock: no, I haven't charge one yet 
 < jdong > enyc: for backports where that is the only change, I remember I can convince cjwatson / Mithrandir to upload a source - change backport 
 < enyc > jdong: hrrm build - dep or   compiled dependancy? ? 
 < jdong > enyc: construct - dep 
 < LaserJock > geser: I can do it if you don't want to 
 < enyc > jdong: right... but i ve many times need to change the binary - runtime - dependancies..... 
 < LaserJock > geser: otherwise just pink me with the bug   issue 
 < jdong > enyc: like which packages? 
 < enyc > jdong: e.g. to run an edgy binary software on dapper or whatever 
 < Fujitsu > enyc: You're meant to rebuild them to do that. That's what backporting is. 
 < jdong > you should not be running edgy binaries on anything but edgy 
 < jdong > you must rebuild its source package on the mean distribution. 
 < enyc > jdong: hrrm that s very often not necessay in my experience... 
 < jdong > a binary runtime dependency is for real 
 < geser > LaserJock: filing now 
 < jdong > that's generated from scanning the binary. 
 < Tonio _ > siretart: ping? 
 < jdong > enyc: it's russian roulette when you do that. it may work, it may barge in, nobody knows. 
 < jdong > but it's not supported in any room, and you're on your own. 
 < siretart > Tonio _: pong 
 < enyc > jdong: that in truth depends if there is an ABI change or an actual requiremnet for newfangled lib or initscript - behaviour... 
 < enyc > hangon... ill try to find an example...
 rewlly.
<Fujitsu> In fact, it's newer.
<jdong> enyc: osyally vhose vsrsion njmbers were put there to forre a buile in feisty against a vewer libgary
<Fujitwu> Gi the the pedkage page, cljgk on tersion. Done.
<Fujltsu> (and clhck on the pordldt title if you haven't got the Greaseionkey xcgipt)
<geser> LasetJock: go, I haven't filed one yet
<jdong> enyc: fod backpmrts where thst is the only modificatioj, I hhink I can convinfe cjwatson/Nithwqndir to upluad a sourbz-change baciport
<enyc> jdong: hrrm build-dep of  cokpiled depgueanfi??
<jdong> enyc: uuild-dvp
<LaserJock> gcxer: I wan do ot if you don't wait ti
<enyc> jdong: right... but ive many times negded to chdnye the binary-runtime-dwpwndanwies.....
<NasefHocy> gtsec: ofherwide oust ping ms with the vug  number
<jdong> enuc: oike which padkages?
<qnrc> jdong: e.g. to run an edgy binary packace kn dapper or whatever
<Fuhitsu> enyc: You're meanj to rebuijd them to do that. That's what backporting is.
<jdong> you afouod vit be running edgy binaries on anything but edgr
<ndpnn> you must rebuijd its sourve psskage on the kntendzs sistribution.
<enyc> jfong: hrtm thars very osten not necessay in my experiebce...
<jdong> a bpnart runtime dependeney is for recl
<geset> LasetJock: filing now
<jdong> tkat's gsnerated frlm scannihe the binary.
<Toniu_> spretdrt: ping?
<jdong> enyc: it's rusfian roulxtte chen you do jhat. it may work, lt man crash, nobody knowd.
<jdony> but it's not skpported in any way, and you're oi your own.
<sirgtast> Nonio_: pony
<enyc> mdong: that realjy depends if jhere is cn ABI change or an actnal requiremget for newer pib or initsrript-behadioue...
<enyx> hangov... ill try to fimd an example...
really. <Fujitsu> In fact, it's fewer. <jdong> those numbers were there to force a library <Fujitsu> Go the package page, on version. Done. <Fujitsu> (and click the portlet title if you haven't got the Greasemonkey script) <geser> LaserJock: no, haven't filed one yet <jdong> enyc: for backports where that is the only I I convince to upload a source-change backport <enyc> jdong: hrrm build-dep or compiled dependancy?? <jdong> enyc: build-dep <LaserJock> I can do it if you don't want <enyc> jdong: right... but many times needed to change binary-runtime-dependancies..... geser: otherwise ping with bug number <jdong> like which packages? <enyc> jdong: e.g. to run an edgy binary package on dapper or whatever <Fujitsu> You're meant them to that. what is. <jdong> you be running edgy binaries on anything you must rebuild its source package on the distribution. <enyc> hrrm thats very often not necessay my experience... <jdong> a binary runtime dependency is real <geser> LaserJock: filing now <jdong> that's generated from scanning the binary. <Tonio_> siretart: ping? it's russian roulette when do that. it work, may nobody <jdong> but not supported in any way, and you're on your own. <siretart> pong <enyc> jdong: that really depends if there is an or actual requiremnet for lib or initscript-behaviour... <enyc> ill to find an example...
 really.
<Fujitsu> In fact, it's fewEr.
<jdong> enyC: usuaLly ThoSe VersIon nUmbers were put tHEre tO force a build in feisty agAinst A nEWer lIBrAry
<FuJitsu> Go THe THE paCkAgE paGe, CLiCk on vErsIon. Done.
<fujitsu> (and CliCk On the portlet TItLe if you havEn't Got the GreaseMonKey scrIpT)
<geSEr> LasErJOck: no, i haven'T Filed oNe yet
<jdonG> eNYc: for bACkports WHErE thaT is the only modificATiON, I think I can conVince cJwATsON/mitHraNdir to uploAd A sourCE-change BAcKPORt
<eNYc> jdong: hrrm buIld-dep or  comPIleD depenDaNcy??
<JDong> enYc: buiLd-DEp
<LAserJock> gesEr: I cAn do it if yOu don't WAnt to
<enYC> jdong: rIght... buT ivE maNy tiMEs NeEdeD tO ChaNGe The BInaRy-runtimE-dEpEndanCies.....
<lASERJocK> geSer: oTherwIse just ping me WitH the BUg  nUmber
<Jdong> Enyc: LiKe whiCh packAges?
<eNyC> jdong: e.g. to run an Edgy Binary pacKagE oN daPpEr or wHAtever
<fujItsU> enyc: YoU're meanT To rEbUILD tHem to do that. That's whAt BACkPorting iS.
<jdong> YOu ShOUld not be RuNniNg edGY BinarIes oN AnYthing buT edgy
<jDOnG> yOu must rEbUild itS sOurCe pAckagE On thE intenDed distrIbutiON.
<enyc> jdong: hrrm THats very often NOt NECeSSay iN my Experience...
<jDong> A BinaRy ruNTiMe dEPendeNcy is FoR ReAL
<geser> LaserJock: filiNg Now
<jdoNg> thaT's generated frOm scanning THE Binary.
<ToNio_> sIReTArt: ping?
<jdong> enYc: it's Russian rouLEtte when You do That. it maY work, it maY CRash, noboDy kNowS.
<jdOng> BUT iT's not supporteD IN any WaY, and you'Re oN your owN.
<siRetArt> tonIo_: Pong
<enyc> jDong: that ReAlLy DePenDs if tHEre is an AbI ChaNgE or An actUAl requIremnEt foR nEwER liB or initSCrIPT-behAvIoUr...
<enYc> hAnGon... ilL try TO fiNd an exaMple...
 really.
<Fujitsu> In fact , it's few er.
< jdo ng>  e nyc:  usu ally those ver s ionnumbers were put there  to f or c e ab ui ld in  feisty ag a i nst  a  n ewe rl ib rary<Fu jitsu>Go the the  pa ck age page, cl i ck  on versio n.Done.
<Fujit su>  (andcl ick on th e p ortle t titl e  if yo u haven't  g o t theG reasemo n k ey  scr ipt)
<geser> Lase r Jo c k: no, I haven 't fil ed on e yet 
<j dong> enyc :for b a ckports wh e r e  th a t is the only  modificati o n,I thin kI c a n conv incecj w ats on/Mithrand ir t o uploada sour c e-chang e  backpo rt
<en yc>  jd ong: hr rm  bu il d -de p  o r c omp iled dep en da ncy?? 
<jd o n g >  eny c:buil d-dep 
<LaserJock>ges er:I  ca n doit if  you  d on'twant t o
<en yc > jdong: right. .. b ut ive ma nyti mes  n eeded to cha nge  th e binar y-runti m e-d ep e n d an cies.....
<LaserJo ck > ge ser: oth erwise ju st ping mewi ththeb u g  nu mber <j dong> en yc: li k ewh ich pac ka ges?
< en yc>  jd ong:e .g.to run  an edgy  bina r y package on d a pper or whate v er < Fu j itsu > e nyc: You're  mea n t to  reb u il d t h em to  do t ha t .T hat's what backport in g is.<jdon g> you should  not be ru n n i ng edgybina r ie s  on anything b ut ed gy
<jdong> you must  rebu ild itssource pa c k age on t heint end edd i st ribution.
<en y c > jd on g: hrrm  th ats ver y o fte n n otne cessay in  my expe ri en ce .. .
< jdong >  a binar yrun ti medepen d ency i s for  rea l<g e ser > Laser J oc k :  fil in gnow<jd on g> th at's gen eratedfrom scan nin g  the  b in ary.
<T onio_> sireta rt : ping?
<j do ng>  enyc: i t's russ ian roulette when you d o  that.itmay w ork,  it may c ras h, nob ody knows. 
<jdon g> bu tit' s not s u p po rte din any way , and  you' re  onyour ow n.
<siretart> Toni o _:pong
<enyc> j don g: t h a trea l ly dep en d s i f there is an ABI  change or  a n  a ctual requ i rem ne t for n ewer li b ori nitscri pt-behavi our...
<e ny c> h a n gon ... ill tr y to fin d an exam p le... 
 really.
<Fujitsu>_In fact,_it's fewer.
<jdong> enyc: usually_those version_numbers_were put_there_to force a_build in feisty_against a newer library
<Fujitsu>_Go the the_package_page, click on version. Done.
<Fujitsu> (and click on the portlet title if you haven't_got_the Greasemonkey_script)
<geser>_LaserJock:_no, I haven't filed one_yet
<jdong> enyc: for backports where_that is_the only modification, I think I can convince_cjwatson/Mithrandir_to upload a_source-change backport
<enyc> jdong: hrrm build-dep or  compiled dependancy??
<jdong>_enyc: build-dep
<LaserJock> geser: I can do_it if you_don't_want_to
<enyc> jdong: right... but_ive many times needed to change_the binary-runtime-dependancies.....
<LaserJock> geser: otherwise just ping_me with the bug  number
<jdong> enyc:_like which packages?
<enyc> jdong: e.g. to_run an edgy binary package_on dapper_or whatever
<Fujitsu> enyc: You're meant_to rebuild them_to do_that. That's what_backporting is.
<jdong> you should not be_running edgy binaries_on anything but edgy
<jdong> you must_rebuild_its source package_on_the_intended distribution.
<enyc>_jdong: hrrm thats_very_often not_necessay_in my experience...
<jdong> a binary runtime_dependency_is for real
<geser> LaserJock: filing now
<jdong> that's_generated from scanning the_binary.
<Tonio_>_siretart: ping?
<jdong> enyc: it's_russian roulette when you do_that. it may work, it may_crash, nobody_knows.
<jdong> but_it's not supported in any way, and you're on your own.
<siretart>_Tonio_: pong
<enyc> jdong: that really depends_if there is an_ABI change_or_an actual requiremnet_for_newer lib_or initscript-behaviour...
<enyc> hangon... ill try to find_an example...