[04:52] wgrant: thanks :) [05:37] bigjools: np! === frankban|afk is now known as frankban === mup_ is now known as mup === frankban is now known as frankban|afk [21:46] if I really took the time to fix this and present an MP against Launchpad, would it be accepted? My PPA says You can update your system with unsupported packages from this untrusted PPA by adding ppa:tsimonq2/test to your system's Software Sources. (Read about installing) sudo add-apt-repository ppa:tsimonq2/test sudo apt-get update" [21:46] it could be fixed to sudo apt update [21:47] but the thing is, in precise, that's not supported yet [21:47] you have to use apt-get [21:47] so I assume that sort of change wouldn't be appropriate yet? [21:49] tsimonq2: indeed; and it wouldn't be a "fix", it's just a bit cosmetically better [21:49] or maybe it could be corrected to that but show something like, "On systems running Ubuntu 12.04, run this instead:" ? [21:49] tsimonq2: no point in causing compatibility confusion for the sake of somewhat nicer progress output [21:49] I see cjwatson [21:49] no, sudo apt-get update is still perfectly valid on more recent systems too [21:49] it's not wrong, it's just not the newest hotness [21:49] but that's fine [21:49] let's not complicate the UI further [21:50] I mean, yes, I use sudo apt update myself, but changing LP can wait a bit more :) [21:50] cjwatson: maybe I could wait until precise is EOL? ;) [21:51] I mean, totally the choice of the Launchpad team [21:51] we would probably consider it after that point, yes [21:51] ok :) [21:51] maybe not like the next day, there'll still be a whole bunch of precise users around and we don't delete precise PPAs or anything [21:52] but with some kind of respectable interval :) [21:52] well which is why I suggested adding that switch, to make that show up only if there's precise packages (if even possible) and then just reverting it when the time comes :) [21:53] but I guess I can live with it until then [21:56] thanks cjwatson