Your message dated Fri, 28 Nov 2008 10:49:38 GMT
with message-id <[EMAIL PROTECTED]>
and subject line faqomatic has been removed from Debian, closing #149839
has caused the Debian Bug report #149839,
regarding faqomatic: saveToFile: Couldn't write to /home/pgss/fom-serve/cache// 
because Is a directory
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.)


-- 
149839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=149839
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: faqomatic
Version: 2.712-3
Severity: normal

I'm not sure what triggered these 14 error emails:

-----
The "Project Gutenberg Software Site" Faq-O-Matic (v. 2.712)
maintained by [EMAIL PROTECTED]
had a problem situation.

The command was: "submitPart"
The message is: "saveToFile: Couldn't write to /home/pgss/fom-serve/cache//
because Is a
directory".
The process number is: 8374
The user had given this ID: <(noID)>
The browser was: <Mozilla/3.01Gold (Macintosh; I; 68K)>
-----


-- System Information
Debian Release: 3.0
Kernel Version: Linux robust.colorado.edu 2.4.17 #1 SMP Sun Apr 21 21:05:15 MDT 
2002 i686 unknown

Versions of the packages faqomatic depends on:
ii  debconf        1.0.32         Debian configuration management system
ii  perl           5.6.1-7        Larry Wall's Practical Extraction and Report
ii  rcs            5.7-13         The GNU Revision Control System

--- Begin /etc/fom.conf (modified conffile)

--- End /etc/fom.conf


--- 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