/srv/irclogs.ubuntu.com/2017/02/10/#launchpad.txt

=== _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_
tjaaltonanyone up who knows about ppa's?22:16
tjaaltonif 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
nacctjaalton: i believe it will remember and reject22:18
dobeynope. newer version number still has to be uploaded, i'm pretty sure22:18
dobeythe history is still in the DB22:19
tjaaltonright22:20
tjaaltonok22:20
tjaaltonpadoka ppa is busted then, accidentally put an epoch in the mesa version :P22:20
tjaaltonneeds to create new ones I guess22:20
=== salem_ is now known as _salem
cjwatsontjaalton: you can upload an older version later as long as the newer one has been removed22:33
tjaaltonoh?22:33
cjwatsontjaalton: the bit about history in the DB that dobey refers to only means that the version number once uploaded is permanently burned22:34
cjwatsonso you can never reuse a version in a given archive, but you can remove-then-upload to go backwards22:34
tjaaltonyeah that's what I was after, thanks22:34
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. PPAs22:38
cjwatson)22:38
dobeyoh hrmm22:54
dobeytjaalton: 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 veersion22:55
tjaaltondobey: sure, I'll tell him22:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!