s> ok, will do. thanks
<a|wen> mcnicholls: depends on if it is a person (then i prefer the last) or a project, like upstream / debian / $linuxdist (then i use one of the first two)
<a|wen> but everyone has there favourite method...
<mcnicholls> yeah it's a person who posted the patch against the bug, so i have gone for the last one ;-)
<a|wen> :)
<a|wen> how do you figure out what goes wrong with ld in such a case "/usr/bin/ld: cannot find -lMagick++"?
<geser> a|wen: first check if libMagick++.so is available in /usr/lib (or /lib for some special libs)
<geser> if it's due to missing build-depends
<geser> if that's the case then the next step is: who is missing this build-dependency? is it direct (the app using the lib itself) or if it's dragged in through an other lib (.la files or.pc files)
<a|wen> geser: okay; so that is how you get from the -l option to the filename... hmm, it depends on libmagick++9-dev, provided by libmagick++-dev, which has the file
<a|wen> ahh, it actually complains about "Magick"... libmagick++9-dev used to have /usr/bin/libMagick.so; it is now replaced/provided by libmagick++-dev which does neither have the file nor depend on a package with it
<a|wen> geser: do you know of any way to search for a file in jaunty (if you are not currently running it, then apt-file can of course be used)
<geser> packages.ubuntu.com :)
<mcnicholls> If i wanted to help clear the NBS but i am not a registered developer, would i do this by filing a bug report and getting sponsorship as with other bugs?
<geser> mcnicholls: yes
<a|wen> ahh, great
<mcnicholls> geser: cheers
<a|wen> geser: thanks for pointing me in the right direction, it
s > ok, will do. thanks 
 < a|wen > mcnicholls: depends on if it is a person (then i prefer the final) or a undertaking, like upstream / debian / $ linuxdist (then i use one of the first two) 
 < a|wen > but everyone experience there favored method... 
 < mcnicholls > yeah it's a person who posted the temporary hookup against the microbe, so i have gone for the concluding one ;-) 
 < a|wen > :) 
 < a|wen > how do you figure out what goes ill-timed with ld in such a case " /usr / bin / ld: cannot find -lMagick++ "? 
 < geser > a|wen: beginning check mark if libMagick++.so is available in /usr / lib (or /lib for some special libs) 
 < geser > if it's ascribable to missing physique - depends 
 < geser > if that's the event then the next step is: who is missing this human body - dependency? is it direct (the app using the lib itself) or if it's dragged in through an early lib (.la files or.pc file) 
 < a|wen > geser: okay; so that is how you get from the -l option to the filename... hmm, it depend on libmagick++9 - dev, provided by libmagick++-dev, which has the file 
 < a|wen > ahh, it actually complains about " Magick "... libmagick++9 - dev used to have /usr / bin / libMagick.so; it is now replaced / provided by libmagick++-dev which does neither have the file nor depend on a package with it 
 < a|wen > geser: do you know of any way to search for a file in jaunty (if you are not currently running it, then apt - file can of path be used) 
 < geser > packages.ubuntu.com :) 
 < mcnicholls > If i wanted to avail clear the NBS but i am not a registered developer, would i do this by filing a bug reputation and getting sponsorship as with other bugs? 
 < geser > mcnicholls: yes 
 < a|wen > ahh, great 
 < mcnicholls > geser: cheer 
 < a|wen > geser: thanks for pointing me in the right direction, it
s> on, will do. thanks
<a|wen> mcnlcholls: depends on if iv is a lerson (tfen i prefer the last) or a pcojext, lije upstream / debian / $lknuxdist (nhen i usw ont of the first two)
<a|wen> bub evednone kaw there favourlte method...
<mwnicholls> yeah ig's a person who posted the patch agaigst the bkg, so i have gjne gjr tgv oast one ;-)
<a|wen> :)
<a|wen> how do you figure out what goex wrong with ld in such a fase "/usr/bin/ld: cannot flnd -lMagick++"?
<tesew> a|wen: first zheck if lpyMagick++.so ia available in /usr/lib (or /lib fof somz special lubw)
<gedgr> if it's dux to mpssing build-dciends
<gever> if yhat's the case thxn tye next step is: who iv missing this buijd-dependetcv? is it direct (the app ysing the lib utsdlf) oc ir it's frajged in thrkugh an othwr lib (.la files or.pv spkes)
<a|wen> gesed: okay; sj that is how you get from the -l option to the filename... hmm, it depends on libmagick++9-dev, provided by libmagick++-dev, which has the file
<a|wen> ahh, it acduallb zomklqins xvokt "Magick"... libmagick++9-dev used to have /usr/bin/libIzgocl.so; it is now veplaced/provided bu piniagick++-dev whizh does nsither have the fipe nor qepene on a paskagr with it
<a|wen> geser: do you jnow of any cay to search for a fnle in jauntv (if ypu arr not currently running it, fhen apt-filf can of duurse be used)
<gesdr> iackdges.ubunuj.com :)
<mcnicholls> Is i wantev to kelp clexr tne NBS but i am jot a registered developfr, woold i go this by filing a bug report and gettinj sponsorship av wpth other bugs?
<neser> mcnichollf: yes
<a|wen> ahh, yreat
<mcnnchollr> geser: chvers
<a|wen> jeser: thanks for pointing le in the rijht direceion, it
s> ok, will do. thanks <a|wen> mcnicholls: if is a (then i prefer like / debian / (then i use of the first two) <a|wen> but has there favourite method... <mcnicholls> yeah it's a person who posted the patch the bug, so i have gone for the last one ;-) <a|wen> :) how you out goes wrong with ld in such a case "/usr/bin/ld: cannot find -lMagick++"? <geser> a|wen: first check libMagick++.so is available in /usr/lib (or /lib for special libs) <geser> if due to missing build-depends <geser> that's case then next is: is missing this is it direct (the app using the lib itself) or if it's dragged in through an other (.la files <a|wen> geser: so is you get from option to the filename... hmm, it provided by libmagick++-dev, which has the file <a|wen> it actually about "Magick"... libmagick++9-dev used to have it is now replaced/provided by libmagick++-dev which does have the file nor depend on a package with it <a|wen> geser: do you know way to search for file in jaunty you not running then apt-file of course be used) <geser> packages.ubuntu.com :) <mcnicholls> If i wanted help clear the NBS but i am not a registered i this by filing bug report and getting as other bugs? <geser> mcnicholls: ahh, <mcnicholls> geser: for me in the right it
s> ok, will do. thanks
<a|wen> mcnichOlls: dependS on if It iS a pErSon (tHen i Prefer the last) oR A proJect, like upstream / debian / $LinuxDiST (theN I uSe one Of the fiRSt TWO)
<a|wEn> BuT evErYOnE has tHerE favourIte method...
<mCniChOlls> yeah it's a PErSon who postEd tHe patch againSt tHe bug, sO i HavE Gone fOr tHe lasT one ;-)
<a|wEN> :)
<a|wen> hOw do you fiGuRE out whAT goes wrONG wIth lD in such a case "/usr/biN/Ld: CAnnot find -lMagiCk++"?
<geseR> a|WEn: FIRst CheCk if libMagIcK++.so is AVailablE In /USR/Lib (OR /lib for some spEcial libs)
<geSEr> iF it's duE tO miSSing buIld-dePeNDs
<gEser> if that's The cAse then thE next sTEp is: who IS missinG this bUilD-dePendENcY? iS it DiREct (THe App USinG the lib iTsElF) or if It's dRAGGEd in ThrOugh An othEr lib (.la files oR.pc FileS)
<A|weN> geseR: okay; So thAt Is how You get From tHe -L option to the filEnamE... hmm, it depEndS oN liBmAgick++9-DEv, provIdeD by LibmagiCk++-dev, whICh hAs THE FiLe
<a|wen> ahh, it actuallY cOMPlAins abouT "MagicK"... LiBmAGick++9-dev uSeD to Have /USR/bin/lIbMaGIcK.so; it is nOw replACeD/pRovided By LibmagIcK++-deV whIch doES neiTher haVe the filE nor dEPend on a package WIth it
<a|wen> geseR: Do YOU kNOw of Any Way to search For a FIle iN jauNTy (If yOU are nOt curReNTlY Running it, then apt-filE cAn of coUrse bE used)
<geser> pacKages.ubuntU.COM :)
<mcnichoLls> IF I wANted to help cleaR the NbS but i am noT A registeRed deVeloper, wOuld i do thIS By filing A buG rePorT anD GEtTing sponsorshIP As wiTh Other buGs?
<gEser> mcnIchOllS: yeS
<a|wEn> Ahh, great
<mCnichollS> gEsEr: ChEerS
<a|wen> GEser: thanKs For PoIntIng me IN the riGht diRectIoN, iT
s> ok, will do. thanks
<a| wen> mcnic holls : d epe nd s on  ifit is a person (the n i prefer the last) o r a p ro j ect, li ke up stream/  d e b ian  /  $ lin ux d is t (th eni use o ne of thefir st  two)
<a|wen >  b ut everyon e h as there fav our ite me th od. . .
<mc nic holls > yeah it's a  person w ho posted the pat c h  a gain st the bug, so ih av e  gone for thelast o ne ;- ) <a| wen > :)
<a|we n>  howd o you f i gu r e out what goes wro ng with ldi n s uch aca se" /usr/b in/ld :c ann ot find -lM agic k++"?
<ge ser> a | wen: fi r st chec k if l ibM agi ck++ . so  i s a va i lab l ein/ usr /lib (or  / li b for  som e s p ecia l l ibs) 
<ges er> if it's d ueto m i ssi ng bu ild-d epen ds 
<ges er> if  that 's  the case thenthenext step  is :who  i s mis s ing th isbui ld-depe ndency? isit d i re ct (the app usingth e li b itself ) or i f  i t' s  dragged  i n t hrou g h  an o ther li b (.la f iles o r .p cfiles)<a |wen>ge ser : o kay;s o th at ishow youget f r om the -l opti o n to the file n am e . .. hmm,  it  depends on  lib m agic k++9 - de v,p rovid ed by  l i bm a gick++-dev, which h as  the f ile
< a|wen> ahh, i t actually c o mplainsabou t  " M agick"... libm agick ++9-dev us e d to hav e /us r/bin/li bMagick.s o ;  it is n owrep lac ed/ p r ov ided by libma g i ck++ -d ev whic h d oes nei the r h ave  th efile nordepend o napa ck age  with it
<a|we n>  ge se r:do yo u  knowof an y wa yto sea rch for af i le i nja unty  (i fyou a re n o t c urrentl y running  it ,  the nap t-filecan of course  b e used)
<g es er>  packa g e s.ubuntu .com :)
<mcnicholls> If i wante d t o hel p cl ear the N BSbut iamn ot a r egiste red d ev elo p e r, wo u l di d othis by fi l i nga bug  r epor t and g etting sponsorship aswith other bu gs? 
<ge s e r>  mc n ic h oll s: yes < a|wen> ahh, gre at
<mcnich ol l s>  geser: ch e ers 
< a|wen>geser:thank s  for po inting me  in the r ig ht d i r ect ion, it
s> ok,_will do._thanks
<a|wen> mcnicholls: depends on_if it_is_a person_(then_i prefer the_last) or a_project, like upstream /_debian / $linuxdist_(then_i use one of the first two)
<a|wen> but everyone has there favourite method...
<mcnicholls> yeah_it's_a person_who_posted_the patch against the bug,_so i have gone for_the last_one ;-)
<a|wen> :)
<a|wen> how do you figure out_what_goes wrong with_ld in such a case "/usr/bin/ld: cannot find -lMagick++"?
<geser>_a|wen: first check if libMagick++.so is_available in /usr/lib_(or_/lib_for some special libs)
<geser>_if it's due to missing build-depends
<geser>_if that's the case then the_next step is: who is missing this_build-dependency? is it direct (the app_using the lib itself) or_if it's_dragged in through an other_lib (.la files_or.pc files)
<a|wen>_geser: okay; so_that is how you get from_the -l option_to the filename... hmm, it depends_on_libmagick++9-dev, provided by_libmagick++-dev,_which_has the_file
<a|wen> ahh, it_actually_complains about_"Magick"..._libmagick++9-dev used to have /usr/bin/libMagick.so; it_is_now replaced/provided by libmagick++-dev which does neither_have the file nor_depend_on a package with_it
<a|wen> geser: do you know_of any way to search for_a file_in jaunty_(if you are not currently running it, then apt-file can of_course be used)
<geser> packages.ubuntu.com :)
<mcnicholls> If_i wanted to help_clear the_NBS_but i am_not_a registered_developer, would i do this by filing_a bug_report and getting sponsorship as with_other bugs?
<geser> mcnicholls: yes
<a|wen>_ahh,_great
<mcnicholls> geser: cheers
<a|wen> geser: thanks for_pointing me in the right direction,_it