On Fri, 12 Jun 2009 19:04:35 -0400 Yaroslav Halchenko wrote: > brr -- but what do you really consider a bug? it crashes since you have > no free space available, as exception reports: > > > File "/usr/bin/impressive", line 1527, in AddToCache > > CacheFile.write(data) > > IOError: [Errno 28] No space left on device > > so what is actually a bug? that it would fail more gracefully asking to > free up more space for impressive?
Did you re-read the bug log? I think I clearly explained that a robust program should handle exceptions gracefully, rather than just crash. As I stated in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482336#15 impressive should check (by catching relevant exceptions) whether a required resource (mass memory, central/virtual memory, ...) could be successfully acquired. In case it could not, impressive should refrain from caching the entire presentation and cache only a (moving) part of it... without crashing! It seems that upstream agreed that there is a bug and promised to fix it "in the next upstream version": http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482336#23 Hence, I repeat: there is a bug, upstream agrees and we are waiting for an upstream version that fixes the issue. I don't see why the bug report should be closed: this bug report should stay open, until the bug is fixed in the Debian package (either because a fixed upstream version is packaged and uploaded to the Debian archive or because a patch able to fix the bug is applied to the Debian package). -- New location for my website! Update your bookmarks! http://www.inventati.org/frx ..................................................... Francesco Poli . GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4
pgpnWE6IMZW3j.pgp
Description: PGP signature
