No problems with it being in Jaunty. As I mentioned, take it as you will, just contributing back the package update. And I guess if more people reproduce the issue I encountered in 1.2.9 which is now in Intrepid then it could always be in intrepid-updates.
That bug (the one with "-d" values >1 not working ultimately ended up being a makefile issue- Ben Collins had changed some compile flags in the initial commit, which caused problems. Upstream now compiles with all three flags _LARGEFILE_SOURCE, _LARGEFILE64_SOURCE and _FILE_OFFSET_BITS=64 . A patch would just include changes to the compile flags to include all three. -Kevin On Wed, Oct 15, 2008 at 6:15 AM, Martin Pitt <[EMAIL PROTECTED]> wrote: > Just to let you know, we are one day before final freeze, so upgrading > to new upstream versions isn't really good any more. If there is a > particular patch which is urgent to get in, we can still apply it, but > for the full upgrade I'd rather wait for Jaunty. > > -- > Update makedumpfile package to new upstream 1.3.0 > https://bugs.launchpad.net/bugs/283490 > You received this bug notification because you are a direct subscriber > of the bug. > -- Update makedumpfile package to new upstream 1.3.0 https://bugs.launchpad.net/bugs/283490 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
