 (I was confused at first, and initially thought the build was successful :)
<dholbach> gotcha :)
<lfaraone> If a package requires an API key to work, and upstream tells you "don't share this with anyone", how can we build from source without disclosing the secret?
<cody-somerville> lfaraone, Don't include the API key in the source package.
<lfaraone> cody-somerville: well, the user has to go through an email loop to apply for the key, and it looks like the key is required at build time.
<lfaraone> otoh, I ran `strings` and was able to find out their API key from their released binaries.
<cody-somerville> lfaraone, Is this package open source?
<cody-somerville> It sounds like this package doesn't qualify to be built in launchpad if it requires a secret API key.
<lfaraone> cody-somerville: yes, it is open source.
<lfaraone> cody-somerville: BSD, in fact. But to work with the webservice it is designed to use, it requires an API key, and they configured it to require the key at build time.
<james_w> persia, Laney: what shiny button?
<Laney> we were talking about different things
<Laney> I want to make a branch merge proposal go away from the sponsoring page, but don't know how
<james_w> Hi Laney
<Laney> hi!
<james_w> Laney: can you edit the status at the top?
<Laney> james_w: no
<james_w> Laney: I thought this was going to be covered by https://bugs.edge.launchpad.net/launchpad-code/+bug/504025 but evidently not
<ubottu> Ubuntu bug 504025 in launchpad-code "LP doesn't show correct permissions for packaging branches for me" [High,Fix released]
<james_w> please file a new bug
<Laney> ok then
<nigelb> is pbuilder broken for debian packages in karmic?
<nigelb> i.e. debian dists
<Laney> the apt error?
<
(I was confused at first, and initially thought the build was successful :) 
 < dholbach > gotcha :) 
 < lfaraone > If a software command an API key to work, and upriver tells you " don't partake this with anyone ", how can we build from source without disclose the mystery? 
 < cody - somerville > lfaraone, Don't include the API key in the source package. 
 < lfaraone > cody - somerville: well, the user suffer to go through an electronic mail loop to apply for the key, and it looks like the key is required at build clock time. 
 < lfaraone > otoh, I ran 'strings 'and was able to find out their API keystone from their released binaries. 
 < cody - somerville > lfaraone, Is this package exposed source? 
 < cody - somerville > It sounds like this package doesn't qualify to be built in launching pad if it requires a secret API key. 
 < lfaraone > cody - somerville: yes, it is open source. 
 < lfaraone > cody - somerville: BSD, in fact. But to work with the webservice it is design to use, it requires an API key, and they configured it to require the key at build time. 
 < james_w > persia, Laney: what shiny button? 
 < Laney > we were talk about different things 
 < Laney > I desire to name a arm merge proposal go aside from the sponsoring page, but don't know how 
 < james_w > Hi Laney 
 < Laney > hi! 
 < james_w > Laney: can you edit the status at the top? 
 < Laney > james_w: no 
 < james_w > Laney: I intend this was going to be covered by https://bugs.edge.launchpad.net/launchpad-code/+bug/504025 but evidently not 
 < ubottu > Ubuntu bug 504025 in launchpad - code " LP doesn't show correct license for packaging branches for me " [ High, Fix released ] 
 < james_w > please file a newfangled bug 
 < Laney > ok then 
 < nigelb > is pbuilder violate for debian packages in karmic? 
 < nigelb > i.e. debian dists 
 < Laney > the apt error? 
 <
 (I aas confused at first, ana initially thoogyt the build was suczessful :)
<dholbach> gotcha :)
<lfareone> If a package requires an AOI key to work, ane upwrream tells you "dok'c shadc thiv with anyone", hpw can we tuild from souscd cithout disclosing the secret?
<cody-somqrville> lvaraone, Don't igclucq ths API key in the source package.
<lfadaone> cmdy-somerville: well, the user has to go tjrouhh an email loop tl apply for the jey, and it luoks like uhz key is resuired at build time.
<lfaraone> otuh, I xan `strings` abd ads able to hind olt their API key from their teleased binarles.
<covy-sonerville> lfaraone, Is vhis package open soorce?
<cody-sokexville> It sounds like tyis pdckace duwsn'g qhakiry to he uuilt in lahnchpad if ut requires a secreu A[P key.
<lfaraone> cody-sjmqrville: yes, it is open source.
<lfaraone> cmdy-aomerville: BSD, in fact. Vut to work with the aebservicq it is designed to use, it requires an API key, ang theb zonylnurea ih to require the key at build time.
<james_w> persyz, Kakey: what shiny bmtton?
<Laney> we were twllyng about difwerent thjngs
<Laney> I want tl make w brabch merge prolosal go away from the sponworing page, yut don't know how
<jamed_w> Hi Laney
<Uanei> hi!
<jakes_w> Laney: can you edit the status at hhe top?
<Lahdy> james_w: no
<jamer_w> Katey: I thought this was goigg to be roverzd by htgps://bogs.edge.jaunchpad.nft/laukwhpad-code/+bug/504025 but egidenjly nod
<ubottu> Ubkntu bug 504025 in launchpad-code "LP doesn't show cortecd pvrmissionf for packaging brwnches for me" [Kigh,Fix xeleasdd]
<james_w> pmease fmle a new bud
<Laney> ok thet
<jigelb> is pbnilder brjken for debian oackages in katmic?
<nigely> i.e. eebian dists
<Laney> bhe akt error?
<
(I was confused at first, and initially build successful :) gotcha :) <lfaraone> API to work, and tells you "don't this with anyone", how can we from source without disclosing the secret? <cody-somerville> lfaraone, Don't include the API key the source package. <lfaraone> cody-somerville: well, the user has to go through an loop apply the and it looks like the key is required at build time. <lfaraone> otoh, I ran `strings` was able to find out their API key their released binaries. <cody-somerville> Is this package open source? It like this doesn't to built in launchpad it requires a secret API key. <lfaraone> cody-somerville: yes, it is open source. <lfaraone> cody-somerville: BSD, in But to the webservice is to it requires an and they configured it to require build time. <james_w> persia, Laney: what shiny button? we were about different things <Laney> I want make a branch merge proposal go away from sponsoring page, but don't know how <james_w> Hi Laney <Laney> hi! <james_w> Laney: can you status at the top? james_w: no <james_w> I this going be covered https://bugs.edge.launchpad.net/launchpad-code/+bug/504025 but evidently not <ubottu> Ubuntu bug 504025 in launchpad-code "LP show correct permissions for packaging branches for me" [High,Fix released] file new bug <Laney> then <nigelb> is pbuilder for packages in karmic? <nigelb> dists the
 (I was confused at first, and iniTially thouGht thE buIld WaS sucCessFul :)
<dholbach> gotCHa :)
<lfAraone> If a package requirEs an ApI KEy to WOrK, and uPstream TElLS You "DoN't ShaRe THiS with AnyOne", how cAn we build fRom SoUrce without dIScLosing the sEcrEt?
<cody-somervIllE> lfaraOnE, DoN'T inclUde The APi key in THe sourCe package.
<LfARaone> cODy-somerVILlE: welL, the user has to go thROuGH an email loop to Apply fOr THe KEY, anD it Looks like tHe Key is REquired AT bUILD tiME.
<lfaraone> otoh, i ran `strings` ANd wAs able To FinD Out theIr API KeY FroM their releaSed bInaries.
<coDy-someRVille> lfARaone, Is This paCkaGe oPen sOUrCe?
<CodY-sOMerVIlLe> IT SouNds like tHiS pAckagE doeSN'T QUaliFy tO be bUilt iN launchpad if iT reQuirES a sEcret aPI keY.
<lfaRaOne> coDy-someRvillE: yEs, it is open sourcE.
<lfaRaone> cody-SomErVilLe: bSD, in FAct. But To wOrk With the WebservICe iT iS DESiGned to use, it requireS aN apI Key, and thEy confIGuReD It to requIrE thE key AT Build Time.
<JAmEs_w> persiA, Laney: WHaT sHiny butToN?
<Laney> We WerE taLking ABout DifferEnt thingS
<LaneY> i want to make a brANch merge propoSAl GO AwAY froM thE sponsoring Page, BUt doN't knOW hOw
<jAMes_w> HI LaneY
<LANeY> Hi!
<james_w> Laney: can you EdIt the sTatus At the top?
<Laney> James_w: no
<jaMES_W> Laney: I tHougHT tHIs was going to be CoverEd by https://bUGs.edge.laUnchpAd.net/lauNchpad-codE/+BUg/504025 but eviDenTly Not
<UboTTU> UBuntu bug 504025 in lauNCHpad-CoDe "LP doeSn't Show corRecT peRmiSsiOnS for packaGing branChEs FoR mE" [HiGh,Fix REleased]
<jAmEs_w> PlEasE file A New bug
<laney> Ok thEn
<NiGElb> Is pbuilDEr BROken FoR dEbiaN paCkAges iN karMIc?
<nIgelb> i.e. Debian disTs
<LANey> tHe ApT error?
<
 (I was confused at first,  and initi allytho ugh tthebuil d was successf u l :) 
<dholbach> gotcha :)<lfar ao n e> I f  a  pack age req u ir e s  an  A PI  ke yt owork,  an d upstr eam tellsyou  " don't sharet hi s with any one ", how can w e b uild f ro m s o urcewit houtdisclo s ing th e secret? 
< c ody-so m erville > lf arao ne, Don't include th e  API key in th e sour ce pa c k age .
< lfaraone>co dy-so m erville :  w e l l , t h e user has to  go through anemaillo opt o appl y for  t h e k ey, and itlook s like th e keyi s requi r ed at b uild t ime .
< lfar a on e>  ot oh ,  Ir an  `s t rin gs` andwa sableto f i n d outthe ir A PI ke y from theirrel ease d  bi narie s.
<c ody- so mervi lle> l farao ne , Is this packa ge o pen sourc e?<c ody -s omerv i lle> I t s oun ds like  this p a cka ge d o es n't qualify to bebu i l tin launc hpad i f  i tr equiresasec retA P I key .
<l f ar aone> co dy-som e rv il le: yes ,it isop ensou rce.< lfar aone>cody-som ervil l e: BSD, in fac t . But to work wi t h  t h e we bse rvice it is  des i gned  tou se , i t  requ iresan AP I  key, and they conf ig ured i t torequire the k ey at buil d t ime.
<ja mes_ w >p ersia, Laney:whatshiny butt o n?
<Lane y> we  were ta lking abo u t  differe ntthi ngs 
<L a n ey > I want to m a k e abr anch me rge  propos algoawa y f ro m the spo nsoringpa ge ,bu t d on'tk now how<j ame s_ w>Hi La n ey
<La ney>hi!<j am e s_w > Laney :  c a n  you  e di t th e s ta tus a t th e  to p?
<Lan ey> james _w: no
< ja me s_w> La ney: I though tthis was g oi ngto bec o vered by  https://bugs.edge.laun c hpad.ne t/l aunch pad- code/+bug /50 4025 b ute vident ly not 
<ubo tt u>U b untub u g504 02 5 in launc h p ad- code"L P do esn't s how correct permis s ion s for packagi ngbran c h es  fo r  m e " [ Hi g h,F i x  released]
<jam es_w> plea se fi le a new b u g
< La ney> ok  then
< nigel b > is pb uilder br oken forde bian p ack ages in ka rmic?
<n igelb> i. e . deb i an  dist s
< Laney>  t heapt e rror?< 
 (I_was confused_at first, and initially_thought the_build_was successful_:)
<dholbach>_gotcha :)
<lfaraone> If_a package requires_an API key to_work, and upstream_tells_you "don't share this with anyone", how can we build from source without disclosing_the_secret?
<cody-somerville> lfaraone,_Don't_include_the API key in the_source package.
<lfaraone> cody-somerville: well, the_user has_to go through an email loop to apply_for_the key, and_it looks like the key is required at build_time.
<lfaraone> otoh, I ran `strings` and_was able to_find_out_their API key from_their released binaries.
<cody-somerville> lfaraone, Is this_package open source?
<cody-somerville> It sounds like_this package doesn't qualify to be built_in launchpad if it requires a_secret API key.
<lfaraone> cody-somerville: yes,_it is_open source.
<lfaraone> cody-somerville: BSD, in_fact. But to_work with_the webservice it_is designed to use, it requires_an API key,_and they configured it to require_the_key at build_time.
<james_w>_persia,_Laney: what_shiny button?
<Laney> we_were_talking about_different_things
<Laney> I want to make a_branch_merge proposal go away from the sponsoring_page, but don't know_how
<james_w>_Hi Laney
<Laney> hi!
<james_w> Laney:_can you edit the status_at the top?
<Laney> james_w: no
<james_w> Laney:_I thought_this was_going to be covered by https://bugs.edge.launchpad.net/launchpad-code/+bug/504025 but evidently not
<ubottu> Ubuntu bug_504025 in launchpad-code "LP doesn't show_correct permissions for packaging_branches for_me"_[High,Fix released]
<james_w> please_file_a new_bug
<Laney> ok then
<nigelb> is pbuilder broken for_debian packages_in karmic?
<nigelb> i.e. debian dists
<Laney> the_apt error?
<