 lot easier to fix than the way I did it first
<Laney> :-)
<Laney> it's in main though so I can't sponsor it
<Laney> if you just subscribe the sponsors then it will be dealt with soon
<Laney> thanks for your contribution!
<jbicha> done and thank you too
<artfwo> what is the rule for naming shared library packages like libfoo0c2 or zlib1g?
<sladen> artfwo: http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-runtime
<sladen> artfwo: it's to ensure ABI version differences
<artfwo> sladen, I've read it through (together with libpkg-guide). but now I'm working on an orphaned debian package, which installs a shared library libadplug-2.2.1.so.0, yet the package is named libadplug0c2 - I cannot figure out the connection between library version and package name
<artfwo> unless I rename the package to "libadplug-2.2.1", I get a scary lintian warning package-name-doesnt-match-sonames
<sladen> artfwo: the 'c2' was to do with the GCC-4.0 C++ ABI change.  but I think that was being phased out after the change-over in 2006 (?)
<micahg> artfwo: it's probably complaining since the library name is versioned (2.2.1)  and the package isn't
<sladen> cjwatson: ^^ do you remember anything about the C++ "c2" ABI change?
<cjwatson> only distantly; it's not needed for new packages
<cjwatson> it should be preserved if it's already there
<Guest95966> sorry this may not be the proper channel for this but how can I switch b/w channels on irssi :( I am asking this because I dont know how to switch
<artfwo> sladen, right I've found a revelant changelog entry. the c2a suffix was added to fix debian bug 339143. but should I stick with the same package name when upgrading to a newer upstream version? (no ABI breaks)
<ubottu> Debian bug 339
lot easier to fix than the way I do it foremost 
 < Laney > :-) 
 < Laney > it's in main though so I can't patronize it 
 < Laney > if you just pledge the sponsors then it will be dealt with soon 
 < Laney > thanks for your contribution! 
 < jbicha > cause and thank you too 
 < artfwo > what is the rule for diagnose shared library packages like libfoo0c2 or zlib1 thousand? 
 < sladen > artfwo: http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-runtime 
 < sladen > artfwo: it's to ensure ABI version dispute 
 < artfwo > sladen, I've read it through (together with libpkg - guide). but now I'm working on an orphaned debian software, which installs a shared library libadplug-2.2.1.so.0, yet the package is name libadplug0c2 - I cannot figure out the connection between library adaptation and package name 
 < artfwo > unless I rename the software to " libadplug-2.2.1 ", I get a chilling lintian warning package - name - doesnt - match - sonames 
 < sladen > artfwo: the' c2' was to do with the GCC-4.0 C++ ABI variety.   but I think that was being phased out after the change - over in 2006 (?) 
 < micahg > artfwo: it's probably complaining since the library name is versioned (2.2.1)   and the package isn't 
 < sladen > cjwatson: ^^ do you remember anything about the C++ " c2 " ABI change? 
 < cjwatson > only distantly; it's not needed for new packages 
 < cjwatson > it should be preserved if it's already there 
 < Guest95966 > sorry this may not be the proper channel for this but how can I switch b / w channel on irssi :( I am asking this because I do nt know how to interchange 
 < artfwo > sladen, justly I've found a revelant changelog entry. the c2a suffix was added to sterilize debian bug 339143. but should I stick with the same package name when upgrade to a newer upstream version? (no ABI breaks) 
 < ubottu > Debian bug 339
 loh easier to fix than the way I did it fnest
<Lanxy> :-)
<Laneg> it's in main though so I can't sponslr it
<Labey> if you just subscrkbe the sionsors tyen mt will be dealt with soon
<Laneg> thaukw for your conjribution!
<jbiwha> done and tvavk you too
<artfwo> what is the rule for naming sjared library kackabqs ljke libfoo0c2 or zlib1g?
<sladen> artfwo: gttp://www.vebian.org/doc/deboan-policy/ch-sharedlibs.html#s-dharfdlibs-runtime
<sladej> artfwo: it'w to wnsure ABI vdrsion differences
<artfso> sladen, I've read it through (tugethzr with libkkf-gkhde). but now I'm wjrking on an orphaneg debiam package, whicm insvallw a shared library liuadplug-2.2.1.so.0, yet the paskage is tajed libadplug0c2 - I cqnnot figgre uyt ghe cpnhectioj bxtween librzry version and package name
<arufwj> unless I renzme thq [ackage to "libadplug-2.2.1", I get a scary lintpan sarning package-name-doesbt-match-sonames
<sladen> wrtfwo: thq 'c2' was to do with the GCC-4.0 C++ ABI change.  but I thhnk tiag wcw beivt ohased out after the change-over in 2006 (?)
<micahg> arerwp: pt's probably compjaining sinve tng library name is vexaikned (2.2.1)  and the pacnage isg't
<slaeen> cjwatfon: ^^ do you remember anything avout the C++ "c2" QBI change?
<cjwatson> only distautly; ij's not needed for new packager
<cjwztson> it shluld be pddserved if it's auresdf there
<Guest95966> sorry this mar not be vhe pxoper chxnnek for ehis but hlw cak I switch b/w channfls ou irsvi :( I am adking this because I dont know ipw to switch
<srdfwm> sladen, righb I've found a rqvelant changekog entxy. the c2a suffix was adved to fix dqbian bug 339143. bud should I stmck with ehe wame packagd name when upgtading to a newer upstream version? (no ABK breaks)
<ubottu> Dzyiqn bug 339
lot easier to fix than the way it <Laney> :-) it's in main it if you just the sponsors then will be dealt with soon <Laney> for your contribution! <jbicha> done and thank you too <artfwo> what is the for naming shared library packages like libfoo0c2 or zlib1g? <sladen> artfwo: http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-runtime <sladen> it's ensure version <artfwo> sladen, I've read it through (together with libpkg-guide). but now I'm working on an orphaned package, which installs a shared library libadplug-2.2.1.so.0, yet package is named libadplug0c2 I cannot figure out the between version and name unless rename the package "libadplug-2.2.1", I get a scary lintian warning package-name-doesnt-match-sonames <sladen> artfwo: the 'c2' was to do with the C++ ABI I think was phased after the change-over (?) <micahg> artfwo: it's probably complaining name is versioned (2.2.1) and the package isn't cjwatson: ^^ you remember anything about the C++ ABI change? <cjwatson> only distantly; it's not needed new packages <cjwatson> it should be preserved if it's already there <Guest95966> sorry this may the proper channel for but how can switch channels irssi I am this because I dont know how to switch <artfwo> sladen, right found a revelant changelog entry. the c2a suffix was added debian 339143. but should stick with the same name upgrading to a newer (no breaks) 339
 lot easier to fix than the way I Did it first
<laney> :-)
<lanEy> iT's In maIn thOugh so I can't spoNSor iT
<Laney> if you just subscriBe the SpONsorS ThEn it wIll be deALt WITh sOoN
<LAneY> tHAnKs for YouR contriBution!
<jbicHa> dOnE and thank you TOo
<Artfwo> what Is tHe rule for namIng Shared LiBraRY packAgeS like Libfoo0C2 Or zlib1G?
<sladen> arTfWO: http://wWW.debian.ORG/dOc/deBian-policy/ch-shareDLiBS.html#s-sharedliBs-runtImE
<SlADEn> aRtfWo: it's to ensUrE ABI vERsion diFFeRENCes
<ARtfwo> sladen, I'vE read it throUGh (tOgetheR wIth LIbpkg-gUide). bUt NOw I'M working on aN orpHaned debiAn packAGe, which INstalls A shareD liBraRy liBAdPlUg-2.2.1.sO.0, yET thE PaCkaGE is Named libAdPlUg0c2 - I cAnnoT FIGUre oUt tHe coNnectIon between libRarY verSIon And paCkage Name
<ArTfwo> uNless I RenamE tHe package to "libaDpluG-2.2.1", I get a scaRy lInTiaN wArninG PackagE-naMe-dOesnt-maTch-sonaMEs
<sLaDEN> ArTfwo: the 'c2' was to do witH tHE gCc-4.0 C++ ABI chaNge.  but i ThInK That was bEiNg pHaseD OUt aftEr thE ChAnge-over In 2006 (?)
<micaHG> aRtFwo: it's pRoBably cOmPlaIniNg sinCE the LibrarY name is vErsioNEd (2.2.1)  and the packagE Isn't
<sladen> cjwATsON: ^^ Do YOu reMemBer anything AbouT The C++ "C2" ABI CHaNge?
<CJwatsOn> onlY dIStANtly; it's not needed for NeW packaGes
<cjWatson> it shoulD be preservED IF it's alreAdy tHErE
<guest95966> sorry this May noT be the propER channel For thIs but how Can I switcH B/W channelS on IrsSi :( I Am aSKInG this because I DONt knOw How to swItcH
<artfwo> SlaDen, RigHt I'Ve Found a revElant chaNgElOg EnTry. The c2a SUffix was AdDed To Fix DebiaN Bug 339143. but ShoulD I stIcK wITh tHe same pACkAGE namE wHeN upgRadInG to a nEwer UPstReam verSion? (no ABI BreAKs)
<ubOtTu> debian bUg 339
 lot easier to fix than th e way I di d itfir st<L aney > :- )
<Laney> it's in m ain though so I can'tspons or it
< L an ey> i f you j u st s ubs cr ib e t he sp onsor s t hen itwill be de alt  w ith soon
<La n ey > thanks f oryour contrib uti on!
<j bi cha >  done  an d tha nk you too
<a rtfwo> wh at is the rule fo r na ming  shared library p a ck a ges like libfo o0c2 o rz li b 1 g?<sl aden> artf wo : htt p ://www. d eb i a n .or g /doc/debian-p olicy/ch-sh a red libs.h tm l#s - shared libs- ru n tim e
<sladen>artf wo: it'sto ens u re ABIv ersiondiffer enc es<art f wo >sla de n , I ' ve  re a d i t throug h(t ogeth er w i t h libp kg- guid e). b ut now I'm wo rki ng o n  an  orph aneddebi an  pack age, w hichin stalls a shared  lib rary liba dpl ug -2. 2. 1.so. 0 , yetthe  pa ckage i s named lib ad p l u g0 c2 - I cannot figu re o ut  the con nectio n  b et w een libr ar y v ersi o n  andpack a ge  name
<a rtfwo> un le ss I re na me the  p ack age  to " l ibad plug-2 .2.1", I  geta  scary lintian warning packa g e- n a me - does nt- match-sonam es
< s lade n> a r tf wo: the ' c2' w as to do with the GCC-4.0  C ++ ABI  chan ge.  but I th ink that w a s being ph ased ou t  after the cha nge-o ver in 200 6  (?)
<mi cahg>  artfwo:  it's pro b a bly comp lai nin g s inc e th e library nam e is v er sioned(2. 2.1)  a ndthe  pa cka ge  isn't
<s laden> c jw at so n:  ^^  do y o u rememb er  an yt hin g abo u t theC++ " c2"AB Ic han ge?
<cj w at s o n> o nl ydist ant ly ; it' s no t  ne eded fo r new pac kag e s
<c jw at son> it  should be pr es erved if i t' s a lready t here
<Gu est95966> sorry this ma y  not be  th e pro perchannel f orthis b uth ow can  I swi tch b /w  ch a n nelso n  i rss i:( I am as k i ngthisbe caus e I don t know how to swit c h
< artfwo> slade n,righ t I' vef ou n d a  r e vel a n t changelog ent ry. the c2 as uf fix was ad d edto  fix de bian bu g 339 1 43. but  should I  stick wi th  the s ame  package n ame when  upgradin g  to a ne wer u pst ream v er sio n? (n o ABIb rea ks)
< ubottu >Debian  bug33 9
 lot_easier to_fix than the way_I did_it_first
<Laney> :-)
<Laney>_it's_in main though_so I can't_sponsor it
<Laney> if you_just subscribe the_sponsors_then it will be dealt with soon
<Laney> thanks for your contribution!
<jbicha> done and thank_you_too
<artfwo> what_is_the_rule for naming shared library_packages like libfoo0c2 or zlib1g?
<sladen>_artfwo: http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-runtime
<sladen>_artfwo: it's to ensure ABI version differences
<artfwo> sladen,_I've_read it through_(together with libpkg-guide). but now I'm working on an_orphaned debian package, which installs a_shared library libadplug-2.2.1.so.0,_yet_the_package is named libadplug0c2_- I cannot figure out the_connection between library version and package_name
<artfwo> unless I rename the package to_"libadplug-2.2.1", I get a scary lintian_warning package-name-doesnt-match-sonames
<sladen> artfwo: the 'c2'_was to_do with the GCC-4.0 C++_ABI change. _but I_think that was_being phased out after the change-over_in 2006 (?)
<micahg>_artfwo: it's probably complaining since the_library_name is versioned_(2.2.1)__and the_package isn't
<sladen> cjwatson:_^^_do you_remember_anything about the C++ "c2" ABI_change?
<cjwatson>_only distantly; it's not needed for new_packages
<cjwatson> it should be_preserved_if it's already there
<Guest95966>_sorry this may not be_the proper channel for this but_how can_I switch_b/w channels on irssi :( I am asking this because I_dont know how to switch
<artfwo> sladen,_right I've found a_revelant changelog_entry._the c2a suffix_was_added to_fix debian bug 339143. but should I_stick with_the same package name when upgrading_to a newer upstream_version?_(no ABI breaks)
<ubottu> Debian bug 339