Bug#295422: e2fsprogs for Sarge

[Theodore Ts'o <tytso@mit.edu>]

On Fri, Apr 08, 2005 at 02:36:58PM +0900, Horms wrote:
> Hi Ted,
> 
> It seems that I missunderstood the preferences expressed
> by Steve Langasek in my discussions with him. As it turns
> out he feels that it would be best to get 0.37-2 ready,
> as 0.37-1 is currently in sarge and has been beaten upon
> by users quite a bit. This should mittigate most of
> the need for review. And hopefully make your life
> a bit easier too.

OK, I've just uploaded e2fsprogs 1.37-2.  It is more than just the
IA-64 core dump fix, but they are all extremely low-risk bugfixes:

  * Fix filefrag so that it works non ext2/3 filesystems again.
    (Closes: #303509)
  * Make sure we include stdlib.h to fix a core dump bug in mke2fs on the
    IA64 architecture (or other platforms where sizeof(ptr) > sizeof(int))
    (Closes: #302200)
  * Add missing return values so that we don't return garbage in certain
    error cases in ext2fs_write_new_inode() and ext2fs_read_int_block().
  * Fix minor spelling typo in the mke2fs man page
  * Avoid doing the LOW_DTIME checks if the superblock last mount time
    indicates that the system clock may not be set correctly.
  * Add further paranoia checks to the blkid, ext2fs, and ss libraries to
    make them safe to call from setuid or setgid applications.

The diff file is quite small and easy to sanity check.

							- Ted