Baltix
command-not-found package

  1. Bug #175506
  2. Activity log

Activity log for bug #175506

Date Who What changed Old value New value Message
2007-12-11 09:44:58 Stefan Taferner bug added bug
2008-03-07 10:20:35 Michael Vogt command-not-found: status New Fix Committed
2008-03-07 10:20:35 Michael Vogt command-not-found: assignee mvo
2008-03-11 06:47:23 Mantas Kriaučiūnas bug assigned to command-not-found (Baltix)
2008-10-13 20:48:36 Colin Watson command-not-found: status Fix Committed Fix Released
2008-10-13 20:48:36 Colin Watson command-not-found: statusexplanation Thanks for your bugreport. This is fixed in bzr and will be part of the next upload. This appears to have been fixed by this upload: command-not-found (0.2.15ubuntu1) hardy; urgency=low [ Kjell Braden ] * Don't run command-not-found from the shell scripts when it has been removed in the meantime (LP: #194939) [ Michael Vogt ] * CommandNotFound/CommandNotFound.py: - do not advise on ".." (LP: # 195090) - thanks to Thomas Perl - do not crash on problems with python-apt (LP: #161804) * debian/control: - improve description (LP: #144153) * command-not-found: - make the crash message a bit more friendly * use lgettext() instead of gettext() (LP: #161159) -- Michael Vogt <michael.vogt@ubuntu.com> Fri, 07 Mar 2008 10:01:20 +0100