On Wed, Nov 15, 2000 at 02:35:49AM +0100, Michael Moerz wrote:
> Hi!
>
> On Wed, Nov 15, 2000 at 12:19:48AM +0000, Julian Gilbey wrote:
> > On Wed, Nov 15, 2000 at 01:07:46AM +0100, Michael Moerz wrote:
> > >
> > > I am contacting you, cause I am in the NM-queue (new-maintainer)
> > > of debian and I am trying to have all metamail bugs fixed.
> >
> > That's a great idea! Thanks.
> I think that I am lucky that your email address is still valid. :)
>
> >
> > > To acomplish that task I am contacting you to get more information
> > > about the behaviour you did observe in the metamail-2.7-31 package.
> >
> > This email should have been copied to [EMAIL PROTECTED], so that
> > there's a record of it.
>
> very nice, thank you.
And so should this have been. I'm including the whole of your reply
so that the essential content gets archived.
> > > Since I only have got the source of 2.7.34 (stable) and 2.7.35
> > > (unstable), I don't have any possibility to know if this bug still
> >
> > 2.7-34 and 2.7-35, not 2.7.34 and 2.7.35. Nevertheless, I'm currently
> > running potato and the problem persists.
>
> uuups, yeah, the numbering you know when you're tyring and should already
> be in bed then typos happen, sorry.
>
> >
> > > exists. I was only possible to track the /tmp/mm.* files down to
> > > metamail, but since metamail uses unlink to release & delete files
> > > I wounder if this is still a bug. Tracking that bug down shouldn't
> > > be a problem with more information about the environment where you
> > > did run metamail.
> >
> > Test case: save a multipart email to a file /tmp/multi. Run:
> > metamail /tmp/multi
> > You'll find /tmp/mm.* files left after the invocation of metamail, and
> > they're empty. If you don't, we can investigate further.
> >
> mmh, that's really strange what I did observe not only that metamail
> leaves mm.* files behind, it also creates far more than it needs.
> That's definitive a bug. Very interesting is also the case when you
> use the proposed tool for having a look at the mime content. Then
> the file that did hold the content gets removed. So the files that
> are left behind are files that are never filled with information
> and files that are created by no direct seeable purpose.
> Since I have began to trace the bug, I hope that I will be able to
> solve it in reasonable time, so that it'll be history soon.
>
> > > If you personally think that this bug is already solved please
> > > close it since I cannot do that (I am not a debian maintainer for
> > > now, but I hope that I will be one soon).
> >
> > You could always set one of the flags or set the bug priority to
> > 'fixed'. Only the maintainer or submitter should close bug reports.
> >
> mmh, that I wasn't really aware of. thanx for pointing me out to it.
> --
> kind regards,
> Michael Moerz
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, QMW, Univ. of London. [EMAIL PROTECTED]
Debian GNU/Linux Developer, see http://www.debian.org/~jdg
Donate free food to the world's hungry: see http://www.thehungersite.com/
