I got caught out by this apt bug when handling sasview. I had installed
a local build of sasview with my patch for 4.2.0~git20180309-3. Stuart
Prescott added another patch and uploaded.

I assumed apt had picked up on the update and installed the final,
official version.  But it hadn't, even though the contents and
changelog had changed.  I was left wondering why the "new" version was
misbehaving (still showing the bug that Stuart had patched).

Drew

Reply via email to