[22:16] <tjaalton> anyone up who knows about ppa's?
[22:18] <tjaalton> 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] <nacc> tjaalton: i believe it will remember and reject
[22:18] <dobey> nope. newer version number still has to be uploaded, i'm pretty sure
[22:19] <dobey> the history is still in the DB
[22:20] <tjaalton> right
[22:20] <tjaalton> ok
[22:20] <tjaalton> padoka ppa is busted then, accidentally put an epoch in the mesa version :P
[22:20] <tjaalton> needs to create new ones I guess
[22:33] <cjwatson> tjaalton: you can upload an older version later as long as the newer one has been removed
[22:33] <tjaalton> oh?
[22:34] <cjwatson> 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] <cjwatson> so you can never reuse a version in a given archive, but you can remove-then-upload to go backwards
[22:34] <tjaalton> yeah that's what I was after, thanks
[22:38] <cjwatson> (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] <cjwatson> )
[22:54] <dobey> oh hrmm
[22:55] <dobey> 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] <tjaalton> dobey: sure, I'll tell him