Your message dated Fri, 28 Nov 2008 10:49:47 GMT
with message-id <[EMAIL PROTECTED]>
and subject line faqomatic has been removed from Debian, closing #455047
has caused the Debian Bug report #455047,
regarding faqomatic -- Doesn't purge all files after piuparts 
Install+Upgrade+Purge test
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.)


-- 
455047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455047
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: faqomatic
Version: 2.721-9.1
Severity: important
User: [EMAIL PROTECTED]
Usertags: piuparts-stable-upgrade piuparts-stable-upgrade-20071130

Hi!

I have been analyzing packages for the piuparts test, and have
observed that faqomatic fails the piuparts because it doesn't purge
some files.

The gzipped log of the piuparts run for faqomatic is
attached. The problem is that the process

Install Etch faqomatic -> upgrade to sid -> purge

seems to let the following files remain unremoved:

   /usr/lib/cgi-bin      owned by: faqomatic
   /usr/lib/cgi-bin/fom  not owned

Please consider fixing this bug, as it is a Lenny release
recommendation [1].

Thanks.

Kumar

[1]: http://release.debian.org/lenny-goals.txt
-- 
Kumar Appaiah,
458, Jamuna Hostel,
Indian Institute of Technology Madras,
Chennai - 600 036

Attachment: faqomatic.log.gz
Description: Binary data

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
Version: 2.721-9.2+rm

The faqomatic 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/506901 . 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.

--
Marco Rodrigues
http://Marco.Tondela.org


--- End Message ---

Reply via email to