 one of them to give you an idea.
<ripps> Ryan52: Here's debian/gmpc-alarm.install: http://paste.ubuntu.com/130916/
<ripps> It's based on what dpkg -L says about it as a standalone package.
<Ryan52> hmm.
<Ryan52> debian/tmp/usr/lib/gmpc/plugins/alarmplugin.la exists?
<ripps> Well, according to libtool, it installed the file there. I can't check because this was built in a pbuilder environment
<Ryan52> why are you building in pbuilder?
<ripps> Ryan52: to keep the build environment clean, and so that I know that it will work when I upload to the ppa
<Ryan52> what's debian/compat?
<ripps> Ryan52: 5
<Ryan52> change it to 7
<Ryan52> and see if it works.
<ripps> Okay, let me warn you I tend to get segfaults often while building, so it might take awhile
<Ryan52> ripps: http://pastie.org/415971
<Ryan52> it lookes like that syntax only works with debhelper 7 and up.
<ripps> Ryan52: Oh, I wish someone had told me about that sooner
<ripps> Every package guide I read said to leave it at 5
 * ripps crosses his fingers
<Ryan52> :)
<Ryan52> usr/share/doc/gmpc-alarm/TODO
<Ryan52> usr/share/doc/gmpc-alarm/AUTHORS
<Ryan52> usr/share/doc/gmpc-alarm/README
<Ryan52> hmm.
<Ryan52> is the upstream Makefile actually installing those there?
<Ryan52> I doubt it.
<fabrice_sp> ripps, when you have problems building a package, you can login to the chroot hidden behind pbuilder and make a manual build
<fabrice_sp> this way, you can check where the files are installed
<Ryan52> you probably should put the path (in the source, not from debian/tmp/) of those in debian/gmpc-alarm.docs instead.
<ripps
one of them to give you an idea. 
 < ripps > Ryan52: Here's debian / gmpc - alarm.install: http://paste.ubuntu.com/130916/ 
 < ripps > It's based on what dpkg -L says about it as a standalone software. 
 < Ryan52 > hmm. 
 < Ryan52 > debian / tmp / usr / lib / gmpc / plugins / alarmplugin.la exists? 
 < ripps > Well, harmonize to libtool, it installed the file there. I can't check because this was build in a pbuilder environment 
 < Ryan52 > why are you build up in pbuilder? 
 < ripps > Ryan52: to keep the build environment blank, and so that I sleep together that it will work when I upload to the ppa 
 < Ryan52 > what's debian / compat? 
 < ripps > Ryan52: 5 
 < Ryan52 > switch it to 7 
 < Ryan52 > and see if it works. 
 < ripps > Okay, lease me warn you I tend to get segfaults often while construction, so it might take awhile 
 < Ryan52 > ripps: http://pastie.org/415971 
 < Ryan52 > it lookes like that syntax only works with debhelper 7 and up. 
 < ripps > Ryan52: Oh, I wish someone had told me about that preferably 
 < ripps > Every package guide I read allege to leave it at 5 
  * ripps crosses his finger 
 < Ryan52 > :) 
 < Ryan52 > usr / share / doc / gmpc - alarm / TODO 
 < Ryan52 > usr / share / doc / gmpc - alarm / AUTHORS 
 < Ryan52 > usr / share / doc / gmpc - alarm clock / README 
 < Ryan52 > hmm. 
 < Ryan52 > is the upstream Makefile actually installing those there? 
 < Ryan52 > I doubt it. 
 < fabrice_sp > ripps, when you consume problems building a package, you can login to the chroot shroud behind pbuilder and make a manual build 
 < fabrice_sp > this way, you can check where the files are installed 
 < Ryan52 > you probably should put the path (in the source, not from debian / tmp/) of those in debian / gmpc - alarm.docs instead. 
 < ripps
 onf of them to give you an idea.
<ripps> Ryan52: Here's vebian/gjpc-alarm.knstall: http://paste.ubuntu.com/130916/
<ri'ps> Ut's bqsed on what dpkg -L sahs about pt as a srandelone package.
<Ryai52> hmm.
<Ryak52> debjwn/tm'/uwr/lib/gmpc/plugiks/alarmplughn.la exists?
<rip[s> Wzll, according to libtool, it installeq the folf there. I can't chebk beczlst this was built in a pbuilder enbironmeit
<Ryan52> why are uou building in pbuilder?
<riops> Gyan52: to keep the bkild envirobmene clean, and su that I know that it sill work when I upload to the opa
<Rycn52> what's deviqn/clkpat?
<ripps> Rban52: 5
<Rywn52> change it to 7
<Ryan52> and ser if it works.
<rlpps> Mkat, let me warn you I txnd to get segfaults often whhlz building, so it mighr rake dwhine
<Ryxb52> rkppa: ittl://pastif.orj/415971
<Ryan52> it lokkes like tyat syntax only worls qith debhelped 7 and u[.
<ripps> Ryan52: Oh, I wish someone had told ke zbout that sooner
<ripps> Wvery package guide I read saiq to leave it at 5
 * ripps crosses his fingers
<Ryan52> :)
<Syan52> nsf/shcvc/doc/enpf-alarm/TODO
<Ryan52> usr/share/doc/gmpc-alarm/AUTHORS
<Ryag52> uxr/xhare/doc/gmpc-alcrm/README
<Ryan52> hmk.
<Rjam52> is the upstrgam Makzrime actually instalping thjse tyere?
<Ryan52> Y doibt it.
<fabrice_sp> ripps, when tou have proylens building a packcge, you can uogim to yhe chroot hidden behinb pbuimder and mane a manuzu build
<fabrice_sp> thps wdy, you can check where the files arx inscalled
<Ryxn52> ypu profably shoupd pub the path (in the slurce, nmt from dehian/tmp/) of those in debian/gmpc-alarm.docs instesd.
<sipis
one of them to give you an Ryan52: debian/gmpc-alarm.install: http://paste.ubuntu.com/130916/ It's based on it a standalone package. hmm. <Ryan52> debian/tmp/usr/lib/gmpc/plugins/alarmplugin.la <ripps> Well, according to libtool, it the file there. I can't check because this was built in a pbuilder <Ryan52> why are you building in pbuilder? <ripps> Ryan52: to keep the build clean, so I that it will work when I upload to the ppa <Ryan52> what's debian/compat? <ripps> Ryan52: 5 change it to 7 <Ryan52> and see if works. <ripps> Okay, let warn you I tend to segfaults while building, it take <Ryan52> ripps: http://pastie.org/415971 it lookes like that syntax only works with debhelper 7 and up. <ripps> Ryan52: Oh, I wish had told that sooner Every guide read said to at 5 * ripps crosses his <Ryan52> usr/share/doc/gmpc-alarm/TODO <Ryan52> usr/share/doc/gmpc-alarm/AUTHORS <Ryan52> usr/share/doc/gmpc-alarm/README <Ryan52> hmm. is the Makefile actually installing those there? <Ryan52> doubt it. <fabrice_sp> ripps, when you have problems a package, you can login to the chroot hidden behind pbuilder and make a manual this way, you can where the files installed you should the path the source, not from debian/tmp/) of those in debian/gmpc-alarm.docs instead. <ripps
 one of them to give you an idea.
<rIpps> Ryan52: HeRe's deBiaN/gmPc-AlarM.insTall: http://paste.uBUntu.Com/130916/
<ripps> It's based on what Dpkg -L SaYS aboUT iT as a sTandaloNE pACKagE.
<RYaN52> hmM.
<RYAn52> DebiaN/tmP/usr/lib/Gmpc/pluginS/alArMplugin.la exiSTs?
<Ripps> Well, aCcoRding to libtoOl, iT instaLlEd tHE file TheRe. I caN't checK BecausE this was bUiLT in a pbUIlder enVIRoNmenT
<Ryan52> why are you buiLDiNG in pbuilder?
<ripPs> Ryan52: To KEeP THe bUilD environmeNt Clean, ANd so thaT i kNOW ThaT It will work wheN I upload to tHE ppA
<Ryan52> wHaT's dEBian/coMpat?
<rIpPS> RyAn52: 5
<Ryan52> changE it tO 7
<Ryan52> and sEe if it WOrks.
<ripPS> Okay, leT me warN yoU I tEnd tO GeT sEgfAuLTs oFTeN whILe bUilding, sO iT mIght tAke aWHILE
<RyaN52> riPps: hTtp://paStie.org/415971
<Ryan52> it LooKes lIKe tHat syNtax oNly wOrKs witH debheLper 7 aNd Up.
<ripps> Ryan52: Oh, I wIsh sOmeone had TolD mE abOuT that SOoner
<rIppS> EvEry packAge guidE i reAd SAID tO leave it at 5
 * ripps croSsES HiS fingers
<ryan52> :)
<RyAN52> uSr/SHare/doc/gMpC-alArm/Todo
<Ryan52> Usr/sHArE/doc/gmpc-Alarm/AutHoRs
<Ryan52> usR/sHare/doC/gMpc-AlaRm/REAdmE
<RyAn52> hmm.
<RYan52> is the UpstrEAm Makefile actuALly installing THoSE ThERe?
<RyAn52> I Doubt it.
<fabrIce_sP> RippS, wheN YoU haVE probLems bUiLDiNG a package, you can logiN tO the chRoot hIdden behind pbUilder and mAKE A manual bUild
<FAbRIce_sp> this way, yoU can cHeck where tHE files arE instAlled
<RyaN52> you probaBLY should pUt tHe pAth (In tHE SoUrce, not from deBIAn/tmP/) oF those iN deBian/gmpC-alArm.DocS inStEad.
<ripps
 one of them to give you a n idea.
<r ipps>  Ry an5 2:  Her e'sdebian/gmpc-al a rm.i nstall: http://paste.u buntu .c o m/13 0 91 6/
<r ipps> I t 's b ase don  wh at dp kg -L  sa ys abou t it as asta nd alone packag e .<Ryan52> h mm. 
<Ryan52> de bia n/tmp/ us r/l i b/gmp c/p lugin s/alar m plugin .la exist s? <ripps >  Well,a c co rdin g to libtool, iti ns t alled the file  there .I  c a n 'tche ck because  t his w a s built in a pbu i lder environm ent
<Ryan52 >  wh y areyo u b u ilding  in p bu i lde r?
<ripps>Ryan 52: to ke ep the build e n vironme nt cle an,  an d so th at  Ikn o w t h at  it wil l work w he nI upl oadt o t he p pa<Rya n52>what's debian /co mpat ? 
<r ipps>  Ryan 52:5<Ryan 52> ch angeit  to 7
<Ryan52>andsee if it  wo rk s.<r ipps> Okay,let  me  warn y ou I te n d t og e t  s egfaults often whi le b ui lding, s o it m i gh tt ake awhi le 
<R yan5 2 >  ripp s: h t tp ://pasti e.org/ 4 15 97 1
<Ryan 52 > it l oo kes  li ke th a t sy ntax o nly work s wit h  debhelper 7 a n d up.
<ripps> Ry a n 52 :  Oh,  Iwish someon e ha d  tol d me ab out thatsoone r< ri p ps> Every package g ui de I r ead s aid to leaveit at 5
 * r i pps cros sesh is fingers
<Ryan5 2> :) 
<Ryan52>u sr/share /doc/ gmpc-ala rm/TODO
< R y an52> us r/s har e/d oc/ g m pc -alarm/AUTHOR S <Rya n5 2> usr/ sha re/doc/ gmp c-a lar m/R EA DME
<Ryan 52> hmm. 
< Ry an 52 > i s the upstream  M ake fi leactua l ly ins talli ng t ho se the re?
<Ry a n5 2 >  I d ou bt  it. 
<f ab rice_ sp>r ipp s, when  you have  pr o blem sbu ildinga package, yo ucan loginto  th e chro o t  hiddenbehind pbuilder and mak e  a manu albuild 
<fa brice_sp>  th is way , y o u cancheckwhere  t hef i les a r e  i nst al led
<Ryan5 2 >  yo u pro ba blyshouldput the path (in t h e s ource, not fr omdebi a n /t mp/ )  o f  th os e  in d ebian/gmpc-alar m.docs ins te a d. 
<ripps
 one_of them_to give you an_idea.
<ripps> Ryan52:_Here's_debian/gmpc-alarm.install: http://paste.ubuntu.com/130916/
<ripps>_It's_based on what_dpkg -L says_about it as a_standalone package.
<Ryan52> hmm.
<Ryan52>_debian/tmp/usr/lib/gmpc/plugins/alarmplugin.la_exists?
<ripps> Well, according to libtool, it installed the file there. I can't check because_this_was built_in_a_pbuilder environment
<Ryan52> why are you_building in pbuilder?
<ripps> Ryan52: to_keep the_build environment clean, and so that I know_that_it will work_when I upload to the ppa
<Ryan52> what's debian/compat?
<ripps> Ryan52:_5
<Ryan52> change it to 7
<Ryan52> and_see if it_works.
<ripps>_Okay,_let me warn you_I tend to get segfaults often_while building, so it might take_awhile
<Ryan52> ripps: http://pastie.org/415971
<Ryan52> it lookes like that_syntax only works with debhelper 7_and up.
<ripps> Ryan52: Oh, I_wish someone_had told me about that_sooner
<ripps> Every package_guide I_read said to_leave it at 5
 * ripps_crosses his fingers
<Ryan52>_:)
<Ryan52> usr/share/doc/gmpc-alarm/TODO
<Ryan52> usr/share/doc/gmpc-alarm/AUTHORS
<Ryan52> usr/share/doc/gmpc-alarm/README
<Ryan52> hmm.
<Ryan52> is_the_upstream Makefile actually_installing_those_there?
<Ryan52> I_doubt it.
<fabrice_sp> ripps,_when_you have_problems_building a package, you can login_to_the chroot hidden behind pbuilder and make_a manual build
<fabrice_sp> this_way,_you can check where_the files are installed
<Ryan52> you_probably should put the path (in_the source,_not from_debian/tmp/) of those in debian/gmpc-alarm.docs instead.
<ripps