=== _salem is now known as salem_ === salem_ is now known as _salem === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === czchen_ is now known as czchen === _salem is now known as salem_ === JanC is now known as Guest6853 === JanC_ is now known as JanC === salem_ is now known as _salem === _salem is now known as salem_ === salem_ is now known as _salem === _salem is now known as salem_ [22:16] anyone up who knows about ppa's? [22:18] if a package is removed from a ppa, can an older version be uploaded later, or does it keep track of what it once had? [22:18] tjaalton: i believe it will remember and reject [22:18] nope. newer version number still has to be uploaded, i'm pretty sure [22:19] the history is still in the DB [22:20] right [22:20] ok [22:20] padoka ppa is busted then, accidentally put an epoch in the mesa version :P [22:20] needs to create new ones I guess === salem_ is now known as _salem [22:33] tjaalton: you can upload an older version later as long as the newer one has been removed [22:33] oh? [22:34] tjaalton: the bit about history in the DB that dobey refers to only means that the version number once uploaded is permanently burned [22:34] so you can never reuse a version in a given archive, but you can remove-then-upload to go backwards [22:34] yeah that's what I was after, thanks [22:38] (this is implemented in a very complicated way that's hard to track down; the key is Archive.getOverridePolicy, which behaves differently for the primary archive vs. PPAs [22:38] ) [22:54] oh hrmm [22:55] tjaalton: well, i guess if you can build an older version, you're going to have to tell people to manually downgrade if they managed to install the broken epoched veersion [22:58] dobey: sure, I'll tell him