ing the sponsors is how one gets it to show up on the queue.
<persia> Cool.  Some things change, some don't.  Now to wait for a better time of day (as I recall this being about the time of day that #ubuntu-* went silent for a few hours) :)
<persia> I'm surprised linking a.dsc works.  We used to get really fussy about that, as there was no way to demonstrate provenance (vs. having all the artifacts (or artifacts to generate the artifacts, like interdiffs) in launchpad).
 * persia has read that interdiffs are now deprecated, to little surprise, as nobody else ever seemed to like them very much
<Unit193> Well sometimes you have to, debdiffs have caused a need to re-upload before that I know of even.  The "preferred" way to do it is from a PPA build (see my irssi sponsor bug), but that allows you to upload a prospective version only once, otherwise you have to incriment the version (and sometimes sponsors will forget to change it back.)
<Unit193> I have been known to just link from /source/ on my httpd. >_>
<persia> Now I'm confused.  if working off the same tarball, I can't think of any reason a debdiff wouldn't be sufficient.
<Unit193> Native package, png/jpg file changes.
<persia> That said, I had a sponsor upload a debdiff from "persia@localhost" once, which remains an embarassment (and caused me, when I was a sponsor, to be extra careful checking changelog entries).
<Unit193> Eg, xubuntu-docs. :P
<Unit193> lintian would shout so very loudly now.
<persia> Yes :)
<Unit193>...I presume all sponsors run that, at least.  It's part of my build process (pbuilder hook, after complete.)
<persia> For generating binary files, I used to store them in 7-bit safe encodings (e.g. base64, uuencode, etc.), and then "build" them at package build time.
<persia> When I was a sponsor, I used to run a bunch of quality checkers, and I think running lintian is part of the default calls to
ing the sponsors is how one gets it to show up on the queue. 
 < persia > Cool.   Some things transfer, some causen't.   Now to wait for a better fourth dimension of day (as I recall this being about the prison term of sidereal day that # ubuntu- * went silent for a few hours) :) 
 < persia > I'm surprised linking a.dsc works.   We use to get really busy about that, as there constitute no way to demonstrate provenance (vs. having all the artifacts (or artifact to generate the artifacts, like interdiffs) in launchpad). 
  * persia has read that interdiffs are immediately deprecated, to little surprise, as nobody else always seemed to wish them very much 
 < Unit193 > Well sometimes you have to, debdiffs have caused a need to re - upload before that I know of even.   The " preferred " direction to do it is from a PPA build (see my irssi sponsor bug), but that allows you to upload a prospective version only once, otherwise you have to incriment the version (and sometimes sponsors will forget to change it back .) 
 < Unit193 > I have been known to just link from /source/ on my httpd. > _ > 
 < persia > Now I'm baffled.   if working off the same tarball, I can't intend of any rationality a debdiff wouldn't be sufficient. 
 < Unit193 > Native package, png / jpg file changes. 
 < persia > That said, I have a sponsor upload a debdiff from " persia@localhost " once, which remains an embarassment (and caused me, when I was a sponsor, to be extra careful check changelog entries). 
 < Unit193 > Eg, xubuntu - docs. :P 
 < Unit193 > lintian would shout so very loudly now. 
 < persia > Yes :) 
 < Unit193>... I presume all presenter run that, at least.   It's part of my build process (pbuilder bait, after complete .) 
 < persia > For generate binary files, I used to store them in 7 - bit safe encodings (for example base64, uuencode, etc .), and then " build " them at package build time. 
 < persia > When I was a sponsor, I used to run a bunch of quality checker, and I think running lintian is region of the default call to
ing the sponsors is how one gets it to shoc up on the qheue.
<perska> Cool.  Some things change, done dob't.  Now to wait for a cetter tile of dat (as U recall tijs beinn abohb the vime of day thaj #ubuntu-* wend silent for a fdw hours) :)
<persia> I'm surprised linking w.dsc wotkd.  We used to det gewlly fussy about that, as there was no say to vemonstrate profenance (vs. having all the wrtivacts (or artifacts to generatg thq artifacts, lkke interdpyfs) in laundhpad).
 * persia has read that intdrdifys are now eeprefdted, to litvle sugprise, as nobody else ever sremed to like bhem tery much
<Unit193> Well sometikes you have to, defdiffs haee caused a need to rw-uplodd baford thxt J lnkw of fvei.  The "prefsrred" way ti do it is from a PKA flold (see my idssi s[ogsor bug), but that allows you to upload d pdospective version only once, otherwise you hwve to insriment the version (and sometimes sponsors will fmrget go emwvte it back.)
<Unit193> I have been known to just link fwkm /spurce/ on my htbpd. >_>
<persia> Now I'm vojfifed.  if workivg off ths same tarball, I cwn't thigk of any reasjn a debdiff wouldn't be sufficiwnt.
<Unit193> Natine pqckage, png/jpg file changes.
<perria> Jhat ssid, I had a sponsor upluad z debdiff fgom "persiz@uocalhost" once, wficm ramains an embarassment (and caused mx, wheu I was x sppnsor, eo be extrw carcxul checking changflog gntriev).
<Unit193> Eg, xkbuntu-docs. :P
<Unit193> lintian would shout so very kogdlj now.
<persna> Yes :)
<Unit193>...I presumq all sponsors run thct, at ueast.  It's part oh my build pwocess (pbuildat hook, after romplete.)
<pqrsiq> Foe generxging binary fikes, I useb to wtore them in 7-bit xafg sncodings (e.g. bawe64, oyencode, etc.), anc tfen "blilv" thei at package tuila tkke.
<perria> When I car a xponsor, I used to rut a gunch of quality cnegkers, and I think running lintoan is part of the defanlt cauls tp
ing the sponsors is how one gets show on the <persia> Cool. Some to for a better of day (as recall this being about the time day that #ubuntu-* went silent for a few hours) :) <persia> I'm surprised a.dsc works. We used to get really fussy about that, as there was way demonstrate (vs. all the artifacts (or artifacts to generate the artifacts, like interdiffs) in launchpad). * persia has that interdiffs are now deprecated, to little surprise, nobody else ever seemed like them very much <Unit193> sometimes have to, have a to re-upload before I know of even. The "preferred" way to do it is from a PPA build (see my sponsor bug), allows you upload prospective only once, otherwise to incriment the version (and sometimes to change it back.) <Unit193> I have been to just from /source/ on my httpd. >_> Now I'm confused. if working off the same I can't think of any reason a debdiff wouldn't be sufficient. <Unit193> Native package, png/jpg <persia> That said, I a sponsor upload debdiff "persia@localhost" which an embarassment caused me, when I was a sponsor, to be extra careful changelog entries). <Unit193> Eg, xubuntu-docs. :P <Unit193> lintian would shout loudly <persia> Yes :) presume all sponsors run at It's part of my (pbuilder after generating files, used to store them 7-bit safe encodings (e.g. base64, etc.), and then "build" <persia> When I was a sponsor, I used run a bunch of quality checkers, and think running lintian is part of the default calls to
ing the sponsors is how one getS it to show uP on thE quEue.
<PeRsia> cool.  some things chanGE, somE don't.  Now to wait for a bettEr timE oF Day (aS i rEcall This beiNG aBOUt tHe TiMe oF dAY tHat #ubUntU-* went siLent for a feW hoUrS) :)
<persia> I'm surPRiSed linking A.dsC works.  We used To gEt realLy FusSY abouT thAt, as tHere waS No way tO demonstrAtE ProvenANce (vs. haVINg All tHe artifacts (or artiFAcTS to generate the ArtifaCtS, LiKE IntErdIffs) in launChPad).
 * peRSia has rEAd THAT inTErdiffs are now Deprecated, tO LitTle surPrIse, AS nobodY else EvER seEmed to like tHem vEry much
<UnIt193> Well SOmetimeS You have To, debdIffS haVe caUSeD a NeeD tO Re-uPLoAd bEForE that I knOw Of Even.  THe "prEFERRed" wAy tO do iT is frOm a PPA build (seE my IrssI SpoNsor bUg), but That AlLows yOu to upLoad a PrOspective versioN onlY once, otheRwiSe You HaVe to iNCrimenT thE veRsion (anD sometiMEs sPoNSORs Will forget to change It BACk.)
<unit193> I havE been kNOwN tO Just link FrOm /sOurcE/ ON my htTpd. >_>
<pERsIa> Now I'm cOnfuseD.  If WoRking ofF tHe same TaRbaLl, I Can't tHInk oF any reAson a debDiff wOUldn't be sufficiENt.
<Unit193> Native pACkAGE, pNG/jpg FilE changes.
<perSia> THAt saId, I hAD a SpoNSor upLoad a DeBDiFF from "persia@localhosT" oNce, whiCh remAins an embarasSment (and caUSED me, when I Was a SPoNSor, to be extra caReful Checking chANgelog enTries).
<unit193> Eg, xuBuntu-docs. :p
<uNit193> lintiAn wOulD shOut SO VeRy loudly now.
<peRSIa> YeS :)
<UNit193>...I preSumE all spoNsoRs rUn tHat, At Least.  It's pArt of my bUiLd PrOcEss (PbuilDEr hook, afTeR coMpLetE.)
<persIA> For geNeratIng bInArY FilEs, I used TO sTORe thEm In 7-Bit sAfe EnCodinGs (e.g. BAse64, UuencodE, etc.), and thEn "bUIld" tHeM aT packagE build time.
<perSiA> When I was a SpOnsOr, I useD TO run a bunCh of quality checkers, and I THink runNinG lintIan iS part of thE deFault cAllS To
ing the sponsors is how on e gets itto sh owupon  the  que ue.
<persia> C o ol. Some things change, s ome d on ' t. N ow  to w ait for ab e tte rti meof da y (as  Irecallthis being  ab ou t the time o f  d ay that #u bun tu-* went si len t forafew hours ) : )
<pe rsia>I 'm sur prised li nk i ng a.d s c works .  W e us ed to get reallyf us s y about that,as the re wa s noway  to demons tr ate p r ovenanc e  ( v s .  ha v ing all the a rtifacts (o r  ar tifact stog enerat e the  a r tif acts, likeinte rdiffs) i n laun c hpad).* persi a hasrea d t hati nt er dif fs are no w d e pre cated, t oli ttlesurp r i s e , as  no body  else  ever seemedtolike the m ver y muc h
<U ni t193>  Wellsomet im es you have to,  deb diffs hav e c au sed  a  need to re- upl oad  before  that I kno wo f ev en.  The "preferre d" w ay  to do i t is f r om  a PPA buil d(se e my i rssispon s or  bug), b ut tha t  a ll ows you  t o uplo ad  apro spect i ve v ersion  only on ce, o t herwise you ha v e to incrimen t  t h e  v e rsio n ( and sometim es s p onso rs w i ll  fo r get t o cha ng e  i t  back.)
<Unit193> I  h ave be en kn own to just l ink from / s o u rce/ onmy h t tp d . >_>
<persia>  NowI'm confus e d.  if w orkin g off th e same ta r b all, I c an' t t hin k o f an y reason a de b d iffwo uldn'tbesuffici ent .
< Uni t19 3>  Native p ackage,pn g/ jp gfil e cha n ges.
<pe rs ia>  T hat  said ,  I had  a sp onso rup l oad  a debd i ff f rom"p er sia@ loc al host"  onc e , w hich re mains anemb a rass me nt  (and c aused me, whe nI was a sp on sor , to b e extra ca reful checking changelo g  entrie s). 
<Uni t193 > Eg, xub unt u-docs . : P 
<Unit 193> l intia nwou l d  shou t so  ve ry  loudly no w . 
<p ersia >Yes:)
<Uni t193>...I presumea llsponsors runtha t, a t le ast .  I t's  p a rto f  my build proce ss (pbuild er ho ok, afterc omp le te.)
<p ersia>For g e neratin g binaryfiles, Ius ed t o sto re them in  7-bit s afe encod i ngs ( e .g . bas e64 , uuen co de,  etc. ), and the n "bu ild" t he m at p ackag ebuild ti me.
<persia> When I was  a spo nsor,  Iused to r una  bu nch of qu alit y checkers , a ndI thi nkr unnin g li n ti ani s par t of the defau l tcal l s  t o
ing the_sponsors is_how one gets it_to show_up_on the_queue.
<persia>_Cool.  Some_things change, some_don't.  Now to_wait for a_better_time of day (as I recall this being about the time of day that_#ubuntu-*_went silent_for_a_few hours) :)
<persia> I'm surprised_linking a.dsc works.  We_used to_get really fussy about that, as there was_no_way to demonstrate_provenance (vs. having all the artifacts (or artifacts to_generate the artifacts, like interdiffs) in_launchpad).
 * persia_has_read_that interdiffs are now_deprecated, to little surprise, as nobody_else ever seemed to like them_very much
<Unit193> Well sometimes you have to,_debdiffs have caused a need to_re-upload before that I know_of even._ The "preferred" way to_do it is_from a_PPA build (see_my irssi sponsor bug), but that_allows you to_upload a prospective version only once,_otherwise_you have to_incriment_the_version (and_sometimes sponsors will_forget_to change_it_back.)
<Unit193> I have been known to_just_link from /source/ on my httpd. >_>
<persia>_Now I'm confused. _if_working off the same_tarball, I can't think of_any reason a debdiff wouldn't be_sufficient.
<Unit193> Native_package, png/jpg_file changes.
<persia> That said, I had a sponsor upload a debdiff_from "persia@localhost" once, which remains an_embarassment (and caused me,_when I_was_a sponsor, to_be_extra careful_checking changelog entries).
<Unit193> Eg, xubuntu-docs. :P
<Unit193> lintian_would shout_so very loudly now.
<persia> Yes :)
<Unit193>...I_presume all sponsors run_that,_at least.  It's part of_my build process (pbuilder hook, after_complete.)
<persia> For generating binary files,_I_used_to store them in 7-bit_safe encodings (e.g. base64, uuencode, etc.),_and then "build"_them at package build time.
<persia> When I_was_a sponsor, I used to run_a_bunch of quality checkers, and I_think_running_lintian is part of the_default calls to