
<sistpoty> hehe
<lupine_85> any other changes before I reupload?
<lupine_85> or should I just do it?
<sistpoty> just spotted one thing with aquamarine... let me take a quick look again
<sistpoty> W: aquamarine source: maintainer-script-lacks-debhelper-token debian/aquamarine.postinst
<lupine_85> mm, I fail at postinst scripts
<lupine_85> the same is in emerald, heliodor and beryl-core
<sistpoty> in the aquamarine.postinst, you should put in #DEBHELPER# at some place. it will get replaced with whatever debhelper wants to put in there then
<lupine_85> I just want the postinst scripts in the.deb files (it's the only fugly hack I have, IMO - see the rules file)
<lupine_85> so is the lack of #DEBHELPER# why they weren't getting included in the.deb files?
<geser> lupine_85: change the build-depend on libgl1-dev in beryl-core to libgl1-mesa-dev
<lupine_85> geser: hehe, ok.. I changed it to libgl1-dev for the benefit of a debian user
<sistpoty> lupine_85: not quite sure actually... but I assume it could be the case
<geser> libgl1-dev is a pure virtual package and you can't depend on as the buildds don't know which one to pick
<geser> lupine_85: but you can change it to libgl1-mesa-dev | libgl1-dev to serve also the debian users
<lupine_85> well, I'll remove fugly hack from the rules and hope for the best
<lupine_85> geser: ok, I'll do that
<geser> libgl-dev has no 1 in its name
<lupine_85> (fugly hack being in beryl-core/debian/rules: "install/beryl-core::" ;) )
<sistpoty> lupine_85
< sistpoty > hehe 
 < lupine_85 > any other changes before I reupload? 
 < lupine_85 > or should I just do it? 
 < sistpoty > barely blemish one thing with aquamarine... let me assume a quick look again 
 < sistpoty > W: aquamarine reservoir: upholder - script - lacks - debhelper - token debian / aquamarine.postinst 
 < lupine_85 > mm, I fail at postinst scripts 
 < lupine_85 > the same is in emerald, heliodor and beryl - core 
 < sistpoty > in the aquamarine.postinst, you should arrange in # DEBHELPER # at some place. it will get replaced with whatever debhelper want to put in there then 
 < lupine_85 > I just want the postinst scripts in the.deb files (it's the only fugly machine politician I have, IMO - see the rules charge) 
 < lupine_85 > so is the lack of # DEBHELPER # why they weren't getting included in the.deb file? 
 < geser > lupine_85: change the physique - depend on libgl1 - dev in beryl - core to libgl1 - mesa - dev 
 < lupine_85 > geser: hehe, ok.. I changed it to libgl1 - dev for the benefit of a debian user 
 < sistpoty > lupine_85: not quite sure actually... but I assume it could be the shell 
 < geser > libgl1 - dev is a pure virtual package and you can't depend on as the buildds don't know which one to pick 
 < geser > lupine_85: but you can change it to libgl1 - mesa - dev | libgl1 - dev to serve also the debian users 
 < lupine_85 > well, I'll remove fugly hack from the rules and hope for the best 
 < lupine_85 > geser: ok, I'll do that 
 < geser > libgl - dev has no 1 in its name 
 < lupine_85 > (fugly hack being in beryl - core / debian / rule: " install / beryl - core: : " ;)) 
 < sistpoty > lupine_85

<sishpoty> hehe
<lupine_85> any othtr changes before I reupnoad?
<luline_85> or rhould I just do it?
<sistpoty> oust spotuvd one thing with aquxmarine... lvt me takw a wyick look efain
<sisb'oty> S: aqucmerine source: malntainer-scrhpt-lacks-debhel[ef-tlken debian/aquamarine.postinst
<lupine_85> mm, I fsip at postinst fcrikts
<jupihv_85> uhe same is in emerald, heliodor ahd beryn-core
<sistpoty> in the aquamarine.postinst, you should put in #DEBJELPER# at sime [oace. it will get replabzd with whajever debhelper wants to put in ghere then
<luping_85> J uost want the postpnst scripts lm the.dab filex (it's the only fujly yack I have, IMO - see vhe rules file)
<lupine_85> so is tha mack of #DEBHELPER# wyy thgy wesen't tetginf mncmuded ln vhe.deb filea?
<geser> lupibe_85: change the build-ce[vmd on libgl1-dsv in fewyl-core to libgl1-mesa-dev
<lupine_85> geser: heht, ok.. J changed it to libgl1-dec for the benefit of w debian tser
<sistpoty> lupine_85: not quite sure actually... but I assujd iu gjjod be the case
<geser> libgl1-dev is a pure virtual [zclane and you can't bepend on as the bkikqds don't know which ons to pick
<geser> luplne_85: but you xan changt it yo libgl1-mesa-dev | libgl1-dev ti serve also rhe debian users
<lu'ine_85> well, I'lu rekove gugly hack from the rulzs and hope for tje best
<lulkne_85> geser: ok, I'll do tvat
<geser> libgl-dev has no 1 yn its nane
<lu'ine_85> (fuguy hsck beyng in berjl-corc/gebian/rules: "instalp/beryp-cmre::" ;) )
<sistplty> lupine_85
<sistpoty> hehe <lupine_85> any other changes before <lupine_85> should I do it? <sistpoty> aquamarine... me take a look again <sistpoty> aquamarine source: maintainer-script-lacks-debhelper-token debian/aquamarine.postinst <lupine_85> mm, fail at postinst scripts <lupine_85> the same is in emerald, heliodor and beryl-core in the aquamarine.postinst, you should put in #DEBHELPER# at some place. it will replaced whatever wants put in there then <lupine_85> I just want the postinst scripts in the.deb files (it's the fugly hack I have, IMO - see the file) <lupine_85> so is lack of #DEBHELPER# why they getting in the.deb <geser> change build-depend on libgl1-dev beryl-core to libgl1-mesa-dev <lupine_85> geser: hehe, ok.. I changed it to libgl1-dev for the benefit of a user <sistpoty> quite sure but assume could be the libgl1-dev is a pure virtual package depend on as the buildds don't know which to pick lupine_85: but you can change it libgl1-mesa-dev | libgl1-dev to serve also the debian <lupine_85> well, I'll remove fugly hack from the rules and hope for the best <lupine_85> I'll do that <geser> has no 1 its <lupine_85> hack in beryl-core/debian/rules: ;) ) <sistpoty> lupine_85

<sistpoty> hehe
<lupine_85> any otheR changes beFore I ReuPloAd?
<LupiNe_85> or Should I just do iT?
<SistPoty> just spotted one thinG with AqUAmarINe... Let me Take a quICk LOOk aGaIn
<SisTpOTy> w: aquaMarIne sourCe: maintainEr-sCrIpt-lacks-debhELpEr-token debIan/Aquamarine.poStiNst
<lupInE_85> mm, i Fail aT poStinsT scripTS
<lupinE_85> the same iS iN EmeralD, HeliodoR ANd BeryL-core
<sistpoty> in thE AqUAmarine.postinsT, you shOuLD pUT In #DeBHeLPER# at somE pLace. iT Will get REpLACEd wITh whatever debHelper wants TO puT in theRe TheN
<Lupine_85> i just WaNT thE postinst scRiptS in the.deb Files (iT'S the onlY Fugly haCk I havE, IMo - seE the RUlEs FilE)
<lUPinE_85> So Is tHE laCk of #DEBHeLpEr# why tHey wEREN'T getTinG incLuded In the.deb files?
<GesEr> luPIne_85: ChangE the bUild-DePend oN libgl1-Dev in BeRyl-core to libgl1-mEsa-dEv
<lupine_85> gEseR: hEhe, Ok.. i chanGEd it to LibGl1-dEv for thE benefiT Of a DeBIAN uSer
<sistpoty> lupine_85: nOt QUItE sure actUally... bUT I AsSUme it couLd Be tHe caSE
<Geser> LibgL1-DeV is a pure VirtuaL PaCkAge and yOu Can't dePeNd oN as The buILdds Don't knOw which oNe to pICk
<geser> lupine_85: bUT you can change IT tO LIbGL1-mesA-deV | libgl1-dev to ServE Also The dEBiAn uSErs
<luPine_85> wElL, i'lL Remove fugly hack from ThE rules And hoPe for the best
<lUpine_85> geser: OK, i'Ll do that
<GeseR> LiBGl-dev has no 1 in itS name
<Lupine_85> (fuglY Hack beinG in beRyl-core/dEbian/ruleS: "INstall/beRyl-CorE::" ;) )
<siStpOTY> lUpine_85

<sistpoty> hehe
<lupine_8 5> any oth er ch ang esbe fore  I r eupload?
<lupi n e_85 > or should I just doit?
< si s tpot y >justspotted on e thi ng  w ith  a q ua marin e.. . let m e take a q uic klook again
< s is tpoty> W:aqu amarine sour ce:  maint ai ner - scrip t-l acks- debhel p er-tok en debian /a q uamari n e.posti n s t<lup ine_85> mm, I fai l  a t  postinst scri pts
<l up i ne _ 8 5>the  same is i nemera l d, heli o do r a ndb eryl-core
<si stpoty> int heaquama ri ne. p ostins t, yo us hou ld put in # DEBH ELPER# at  somep lace. i t  will g et rep lac edwith wh at eve rd ebh e lp erw ant s to put  i nthere  the n < l upin e_8 5> I  just  want the pos tin st s c rip ts in  the. debfi les ( it's t he on ly  fugly hack I h ave,  IMO - se e t he  ru le s fil e )
<lup ine _85 > so is  the la c k o f# D E BH ELPER# why they we re n ' tgettinginclud e din the.debfi les ?
<g e s er> l upin e _8 5: chang e theb ui ld -depend  o n libg l1 -de v i n ber y l-co re tolibgl1-m esa-d e v
<lupine_85>g eser: hehe, o k .. I  c h ange d i t to libgl1 -dev fortheb en efi t  of a  debi an us e r
<sistpoty> lupine _8 5: not  quit e sure actual ly... butI a ssume it  cou l db e the case
<ge ser>libgl1-dev is a pur e vir tual pac kage andy o u can'tdep end  on  as t he  buildds don' t know  w hich on e t o pick<ge ser > l upi ne _85: butyou canch an ge  i t t o lib g l1-mesa- de v |  l ibg l1-de v  to se rve a lsoth ed ebi an user s 
< l u pine _8 5>  wel l,I' ll re move fug ly hack  from the  ru l es a nd  h ope for  the best
<lu pi ne_85> ges er : o k, I'l l do that<geser> libgl-dev has n o  1 in i tsname<lup ine_85> ( fug ly hac k b e ing in  beryl -core /d ebi a n /rule s :  " ins ta ll/beryl-c o r e:: " ;))<sis tpoty>lupine_85

<sistpoty> hehe
<lupine_85>_any other_changes before I reupload?
<lupine_85>_or should_I_just do_it?
<sistpoty>_just spotted one_thing with aquamarine..._let me take a_quick look again
<sistpoty>_W:_aquamarine source: maintainer-script-lacks-debhelper-token debian/aquamarine.postinst
<lupine_85> mm, I fail at postinst scripts
<lupine_85> the same is in_emerald,_heliodor and_beryl-core
<sistpoty>_in_the aquamarine.postinst, you should put_in #DEBHELPER# at some place._it will_get replaced with whatever debhelper wants to put_in_there then
<lupine_85> I_just want the postinst scripts in the.deb files (it's_the only fugly hack I have,_IMO - see_the_rules_file)
<lupine_85> so is the_lack of #DEBHELPER# why they weren't_getting included in the.deb files?
<geser> lupine_85:_change the build-depend on libgl1-dev in beryl-core_to libgl1-mesa-dev
<lupine_85> geser: hehe, ok.. I_changed it to libgl1-dev for_the benefit_of a debian user
<sistpoty> lupine_85:_not quite sure_actually... but_I assume it_could be the case
<geser> libgl1-dev is_a pure virtual_package and you can't depend on_as_the buildds don't_know_which_one to_pick
<geser> lupine_85: but_you_can change_it_to libgl1-mesa-dev | libgl1-dev to serve_also_the debian users
<lupine_85> well, I'll remove fugly_hack from the rules_and_hope for the best
<lupine_85>_geser: ok, I'll do that
<geser>_libgl-dev has no 1 in its_name
<lupine_85> (fugly_hack being_in beryl-core/debian/rules: "install/beryl-core::" ;) )
<sistpoty> lupine_85