Monday 19 May 2014

Re: errors.ubuntu.com and upgrade crashes

On Sun, May 18, 2014 at 06:17:09PM +0200, Bjoern Michaelsen wrote:
> Hi,
>
> On Fri, May 16, 2014 at 03:21:36PM +0100, Matthew Paul Thomas wrote:
> > Oh dear. I've reported that as a bug. <http://launchpad.net/bugs/1320174>
> > [...]
> > Frequency is an absolute count. (Perhaps we should call it "Count"
> > instead?)
>
> thanks for filing the bug. I should have done that myself. My only lame excuse
> for not doing that is, given the other behaviour I saw, I wasnt sure if I
> possibly completely misinterpreted the thing. As for relabeling from frequency
> to count, Id support that, its a lot less confusing.
>
> > That's a shame. The database server is unreliable, but I don't
> > remember a case where it failed *and* the Web site didn't communicate
> > this with an error message.
>
> I probably just see more of those as LibreOffice[1] is a huge package, thus I
> trigger more demanding queries ...
>
> > Sure. And if the Software Updater developers think otherwise, you
> > should get in a room together until you agree on a solution. Don't
> > just shrug and blame each other from a distance. :-)
>
> Im not just shrugging, I have a few ideas on how to solve that (and a few other
> things) -- but I dont think we should avoid building local workarounds, esp.
> when we might reconsider the way we pack and deploy software in the next years
> anyway ... ;)
>
> Ill try to convey some of my lunatic ideas on the next sprint and check for
> feedback and how much they survive the scrutiny of my fellow engineers.
>
> > And specifically, we have no evidence that it's a problem for you.
>
> Well, there is still the mystery on why this particular issue wasnt too high
> ranked on 13.10, but is so on 14.04, with the bug unlikely having changed. No
> need to get to deep into this for just one issue (maybe e.g. audience of LTSes
> does use LibreOffice a lot more), but would be interesting if there are more
> cases like that.

As Matthew mentioned earlier there is a database migration that is still
pending and it is likely that this issue would show more 13.10
occurrences when that migration is complete.

--
Brian Murray