im0: I think you need to edit the makefile to achieve it
<kim0> can I do that
<mok0> kim0: or, shove files around in rues
<mok0> rules
<kim0> mv?
<kim0> that sounds better
<mok0> kim0: yes mv it from the wrong place to the right place
<mok0> kim0: you might be able to do that in the ms-sys.manpages file
<kim0> hmm
<kim0> how do I know more
<kim0> man the dh
<mok0> put debian/tmp/usr/man/man1/... in there
<mok0> <packagename>.manpages just needs to locate the man pages. The script dh_installman determines from the file names where they need to go
 * kim0 nods
<kim0> so fakeroot.. builds whatever crap upstream wants.. then pkgname.* shuffles them around the way ubuntu wants them
<mok0> kim0: you need to go through all parts of the debian/tmp tree to make sure everything you need comes into the pacakge
<kim0> lovely.. built and lintian is happy
<mok0> kim0: yes
<mok0> kim0: pbuilder also uses fakeroot
<mok0> kim0: only in a mystery build directory somewhere
<kim0> hehe
<kim0> mo file not picked up
<kim0> debian/tmp/usr/share/locale/sv/LC_MESSAGES/ms-sys.mo
<mok0> kim0: ugh
<kim0> correct location?
<mok0> kim0: yes, you can use *.install
<mok0> kim0: same one you used to install the binary
<kim0> so mo files don't have a special file?\
<kim0> why is that
<mok0> kim0: programmer lazyness I guess :-)
<mok0> kim0: Most likely it doesn't need special treatment
<kim0> I guess a better question
<kim0> yeah.. why did manpages require a special file
<mok
im0: I think you need to edit the makefile to achieve it 
 < kim0 > can I do that 
 < mok0 > kim0: or, shove files around in sorrow 
 < mok0 > rules 
 < kim0 > mv? 
 < kim0 > that sound better 
 < mok0 > kim0: yes mv it from the wrong place to the correct place 
 < mok0 > kim0: you might be able to do that in the ms-sys.manpages file 
 < kim0 > hmm 
 < kim0 > how do I sleep together more 
 < kim0 > man the dh 
 < mok0 > arrange debian / tmp / usr / man / man1/... in there 
 < mok0 > < packagename>.manpages just necessitate to locate the man page. The script dh_installman determines from the file name where they necessitate to go 
  * kim0 nods 
 < kim0 > so fakeroot.. builds whatever crap upstream desire.. then pkgname. * shuffles them around the way ubuntu wants them 
 < mok0 > kim0: you want to go through all parts of the debian / tmp tree to make sure everything you necessitate comes into the pacakge 
 < kim0 > lovely.. built and lintian is happy 
 < mok0 > kim0: yes 
 < mok0 > kim0: pbuilder also uses fakeroot 
 < mok0 > kim0: merely in a mystery build directory somewhere 
 < kim0 > hehe 
 < kim0 > mo file not picked up 
 < kim0 > debian / tmp / usr / share / locale / sv / LC_MESSAGES / ms - sys.mo 
 < mok0 > kim0: ugh 
 < kim0 > correct location? 
 < mok0 > kim0: yes, you can use * .install 
 < mok0 > kim0: same one you used to install the binary 
 < kim0 > so mo files don't have a special file?\ 
 < kim0 > why is that 
 < mok0 > kim0: programmer lazyness I guess :-) 
 < mok0 > kim0: Most likely it doesn't need special discussion 
 < kim0 > I think a better motion 
 < kim0 > yeah.. why did manpages command a special file 
 < mok
im0: L think you need to edit the makefile to achiete it
<kij0> can I ao that
<mok0> kim0: or, shove filed qroune in rues
<mok0> rules
<kim0> ov?
<kim0> than sounds vetttr
<mok0> kim0: yes mv mf from bke wrkkg plccx to the right klace
<mok0> kim0: you might be dbue to do that in the ms-sys.manpages fije
<kim0> hkm
<nim0> how do I kgow kjre
<kjm0> man the dh
<mok0> put debian/tmp/usr/mzn/man1/... ii there
<mok0> <packsgename>.manpages just needs to pocate the man pagfs. The scrikf dr_unstallman ddtermines from the filg names where they need to go
 * kkm0 nobs
<kim0> so fajeeooh.. builds whavever brap upstream wants.. tven pkgmame.* shuffles bhem eroubd the way ubuntu wanvs them
<mok0> kim0: you nged to go dhxough all parts of thw eebiat/tmp tred to maie shre evfryvhing you nsed comes ibto the pacakge
<kim0> kodvky.. built and lintiwn is happy
<mok0> kim0: yes
<mok0> kim0: pbuilder alvo hses fakeroot
<mok0> kim0: onoy in a mystery build directorr somewhere
<kim0> hehe
<kim0> mo file not picked up
<kim0> dabian/vmo/usx/whare/uicwle/sv/LC_MESSAGES/ms-sys.mo
<mok0> kim0: ugh
<kim0> correct jkcstpon?
<mok0> kim0: yes, yom can use *.install
<mpk0> koi0: same one yoo used ck jnstall the binary
<nim0> so io fioes don't rave a special file?\
<kim0> why is tyat
<mok0> kim0: pgogrqmmer lazyness I gbess :-)
<mok0> kim0: Mosj likeky it doesn't need specicl treztment
<kim0> I guess a gdtter question
<kio0> yvah.. fhy did manpages require a special hile
<mpk
im0: I think you need to edit to it <kim0> I do that around rues <mok0> rules mv? <kim0> that better <mok0> kim0: yes mv it the wrong place to the right place <mok0> kim0: you might be able do that in the ms-sys.manpages file <kim0> hmm <kim0> how do I know <kim0> the <mok0> debian/tmp/usr/man/man1/... in there <mok0> <packagename>.manpages just needs to locate the man pages. The script dh_installman determines the file names where they need to go kim0 nods <kim0> so builds whatever crap upstream wants.. pkgname.* them around way wants <mok0> kim0: you to go through all parts of the debian/tmp tree to make sure everything you need comes into pacakge <kim0> and lintian happy kim0: <mok0> kim0: pbuilder fakeroot <mok0> kim0: only in a somewhere <kim0> hehe <kim0> mo file not picked <kim0> debian/tmp/usr/share/locale/sv/LC_MESSAGES/ms-sys.mo kim0: ugh <kim0> correct location? <mok0> yes, you can use *.install <mok0> kim0: same you used to install the binary <kim0> so mo files don't have a special file?\ is that <mok0> kim0: lazyness I guess <mok0> Most it need special <kim0> I guess a better question <kim0> yeah.. why did manpages a special file <mok
im0: I think you need to edit the mAkefile to aChievE it
<Kim0> CaN I do That
<Mok0> kim0: or, shove fILes aRound in rues
<mok0> rules
<kim0> Mv?
<kim0> ThAT souNDs BetteR
<mok0> kim0: YEs MV It fRoM tHe wRoNG pLace tO thE right pLace
<mok0> kim0: You MiGht be able to dO ThAt in the ms-sYs.mAnpages file
<kIm0> hMm
<kim0> hOw Do I KNow moRe
<kIm0> man The dh
<mOK0> put deBian/tmp/usR/mAN/man1/... in THere
<mok0> <PACkAgenAme>.manpages just neEDs TO locate the man pAges. ThE sCRiPT Dh_iNstAllman deteRmInes fROm the fiLE nAMES whERe they need to gO
 * kim0 nods
<kim0> SO faKeroot.. BuIldS WhatevEr craP uPStrEam wants.. theN pkgName.* shuffLes theM Around tHE way ubuNtu wanTs tHem
<Mok0> kIM0: yOu NeeD tO Go tHRoUgh ALl pArts of thE dEbIan/tmP treE TO MAke sUre EverYthinG you need comes IntO the PAcaKge
<kiM0> loveLy.. buIlT and lIntian Is hapPy
<Mok0> kim0: yes
<mok0> kim0: PbuiLder also uSes FaKerOoT
<mok0> kIM0: only iN a mYstEry builD directORy sOmEWHErE
<kim0> hehe
<kim0> mo file nOt PICkEd up
<kim0> dEbian/tMP/uSr/SHare/locaLe/Sv/Lc_MESsagES/ms-Sys.mO
<MoK0> kim0: ugh
<kIm0> corrECt LoCation?
<mOk0> Kim0: yes, YoU caN usE *.instALl
<moK0> kim0: saMe one you Used tO Install the binaRY
<kim0> so mo files DOn'T HAvE A speCiaL file?\
<kim0> why Is thAT
<mok0> Kim0: pROgRamMEr lazYness i gUEsS :-)
<Mok0> kim0: Most likely it dOeSn't neeD specIal treatment
<kIm0> I guess a bETTEr questiOn
<kiM0> YeAH.. why did manpageS requIre a speciaL File
<mok
im0: I think you need to e dit the ma kefil e t o a ch ieve  it<kim0> can I d o  tha t
<mok0> kim0: or, sho ve fi le s  aro u nd  in r ues
<mo k 0> r ule s<k im0 >m v? 
<kim 0>that so unds bette r
< mo k0> kim0: ye s  m v it fromthe  wrong place  to  the r ig htp lace<mo k0> k im0: y o u migh t be able  t o  do th a t in th e ms -sys .manpages file
<k i m0 >  hmm
<kim0> ho w do I  k n ow m ore 
<k im0> man t he  dh
< m ok0> pu t  d e b i an/ t mp/usr/man/ma n1/... in t h ere 
<mok0 ><pa c kagena me>.m an p age s just need s to  locate t he man pages.T he scri pt dh_ ins tal lman de te rmi ne s  fr o mthe fil e nameswh er e the y ne e d t o go 
 *  kim 0 nod s
<kim0> so f ake root . . b uilds  what ever  c rap u pstrea m wan ts .. then pkgname .* s huffles t hem  a rou nd  thew ay ubu ntu  wa nts the m
<mok0 >  ki m0 : y ou  need to go throug ha l lparts of  the d e bi an / tmp tree  t o m akes u re ev eryt h in g you ne ed com e sin to thepa cakge<k im0 > l ovely . . bu ilt an d lintia n ish appy
<mok0> ki m 0: yes
<mok0> ki m 0 :p buil der  also usesfake r oot<mok 0 >kim 0 : onl y inam ys t ery build directory  s omewhe re
<k im0> hehe
<ki m0> mo fil e n ot picke d up <k i m0> debian/tmp /usr/ share/loca l e/sv/LC_ MESSA GES/ms-s ys.mo
<mo k 0 > kim0:ugh 
<k im0 > c o r re ct location?< m ok0>  k im0: ye s,you can  us e * .in sta ll 
<mok0> k im0: sam eon eyo u u sed t o  install  t hebi nar y
<ki m 0> somo fi lesdo n' t  ha ve a sp e ci a l  fil e? \<kim 0>wh y isthat <mo k0> kim 0: progra mme r  laz yn es s I gue ss :-)
<mok0>  k im0: Mostli kel y it d o e sn't nee d special treatment
<ki m 0> I gu ess  a be tter  question 
<k im0> y eah . . whydid ma npage sreq u i re as p ec ial  f ile
<mok
im0: I_think you_need to edit the_makefile to_achieve_it
<kim0> can_I_do that
<mok0> kim0:_or, shove files_around in rues
<mok0> rules
<kim0>_mv?
<kim0> that sounds_better
<mok0>_kim0: yes mv it from the wrong place to the right place
<mok0> kim0: you_might_be able_to_do_that in the ms-sys.manpages file
<kim0>_hmm
<kim0> how do I know_more
<kim0> man_the dh
<mok0> put debian/tmp/usr/man/man1/... in there
<mok0> <packagename>.manpages just_needs_to locate the_man pages. The script dh_installman determines from the file_names where they need to go
_* kim0 nods
<kim0>_so_fakeroot.._builds whatever crap upstream_wants.. then pkgname.* shuffles them around_the way ubuntu wants them
<mok0> kim0:_you need to go through all parts_of the debian/tmp tree to make_sure everything you need comes_into the_pacakge
<kim0> lovely.. built and lintian_is happy
<mok0> kim0:_yes
<mok0> kim0:_pbuilder also uses_fakeroot
<mok0> kim0: only in a mystery_build directory somewhere
<kim0>_hehe
<kim0> mo file not picked up
<kim0>_debian/tmp/usr/share/locale/sv/LC_MESSAGES/ms-sys.mo
<mok0>_kim0: ugh
<kim0> correct_location?
<mok0>_kim0:_yes, you_can use *.install
<mok0>_kim0:_same one_you_used to install the binary
<kim0> so_mo_files don't have a special file?\
<kim0> why_is that
<mok0> kim0: programmer_lazyness_I guess :-)
<mok0> kim0:_Most likely it doesn't need_special treatment
<kim0> I guess a better_question
<kim0> yeah.._why did_manpages require a special file
<mok