same problem again for actual package version Why not trying my proposal (see comment #4)? You could hold back the new version in testing until Chromium itself is available in updates ... But now again, the default update procedure doesn't work for most users of this library ...