On Fri, 2005-08-26 at 20:37 +0200, Denis Barbier wrote: > On Fri, Aug 26, 2005 at 06:36:39PM +0100, Ian Jackson wrote: > > Adam Heath writes ("Re: comments/string changes and issues with dpkg's messages"): > > > ohshite should really be for internal errors only. Things that "Should Not > > > Happen(tm)". > > > > This is totally 100% INcorrect. ohshite is used nearly everywhere for > > system call failures, eg `disk full'. > > But ohshite already prints strerror(errno), so it could eg print > > dpkg: /var/lib/dpkg/status: No space left on device > dpkg: /var/lib/dpkg/available: No such file or repertory > > instead of > > dpkg: failed to write status record about `tcl8.4' to `/var/lib/dpkg/status': No space left on device > dpkg: failed to open package info file `/var/lib/dpkg/available' for reading: No such file or repertory > > in order to remove many cryptic error messages from PO files. > Yes, because god forbid a developer should be able to understand what's going on when a user files a bug report. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
Description: This is a digitally signed message part