Your message dated Wed, 4 Feb 2009 14:27:22 GMT
with message-id <[email protected]>
and subject line ixbiff has been removed from Debian, closing #339954
has caused the Debian Bug report #339954,
regarding ixbiff: dumps core, doesn't remove log file on purge
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
339954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339954
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ixbiff
Version: 0.03d
When testing ixbiff with piuparts, specifically upgrades from sarge via
etch to sid, I get the following error:
1m48.7s ERROR: Package purging left files on system:
/core
/var/log/ixbiff.log
The core file occurs repeatably and file(1) claims it is created from
the ixbiff process. I have not attempted to investigate it further, but
for reference, here is the piuparts command line:
sudo piuparts -ab sarge.tar.gz -d sarge -d etch -d sid ixbiff
sarge.tar.gz is a tarball created with the following command:
sudo piuparts -as sarge.tar.gz -d sarge hello
The entire log file from piuparts is about 168 kilobytes, and doesn't
seem to contain any information about when the core dump happens, so I
won't attach it, but I'd be happy to send it on request.
The ixbiff.log file is probably created by the sarge version, which does
not use invoke-rc.d. The log file needs to be removed in postrm, see
Policy 10.8.
I hope this is helpful, happy hacking.
--
I've never seen anyone wear a Freudian slip.
--- End Message ---
--- Begin Message ---
Version: 0.03d+nmu1+rm
The ixbiff package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/499255 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
Kind regards,
--
Marco Rodrigues
--- End Message ---
