Bug 8725 - claws-mail-newmail-plugin is not functional - Error: No such file or directory
Summary: claws-mail-newmail-plugin is not functional - Error: No such file or directory
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Julien Moragny
QA Contact:
URL: http://www.thewildbeast.co.uk/claws-m...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-17 20:11 CET by claire robinson
Modified: 2013-11-23 16:13 CET (History)
0 users

See Also:
Source RPM: claws-mail-plugins
CVE:
Status comment:


Attachments
Fix problem when ~/Mail does not exist (1012 bytes, patch)
2013-02-11 21:50 CET, Yann Lejeune
Details | Diff

Description claire robinson 2013-01-17 20:11:19 CET
Please also see bug 8291 (claws-mail-plugins update) where this was discovered.

The newmail plugin errors when loaded..

Error: No such file or directory
Plugin is not functional.

Newmail plugin needs an existing Mail directory inside
$HOME and doesn't create one if it isn't present before loading.

Upstream bug report..

http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2859
Comment 1 Yann Lejeune 2013-02-11 21:50:34 CET
Created attachment 3510 [details]
Fix problem when ~/Mail does not exist

Hi,
Can you consider this patch to fix the problem ?

regards
Yann.
Comment 2 Julien Moragny 2013-02-11 22:15:11 CET
I just pushed claws-mail-extra-plugins-3.9.0-6.mga3 which seems to fix the issue, thanks Yann.

Claire > do you think it's worth an update for mga2 or is it a waste of QA time ?
Julien Moragny 2013-02-11 22:17:55 CET

Status: NEW => ASSIGNED

Comment 3 claire robinson 2013-02-11 22:19:02 CET
It's completely up to you Julien. We are quiet right now *touch wood* so it wouldn't be a huge burden to test it loads ok.

Have you had any other bugs?
Comment 4 Julien Moragny 2013-02-12 20:36:49 CET
I don't have other bug ATM for this package.

Since, it's a low impact bug and after talking with yann, he doesn't use the plugin (and he's just very nice :), I'll check the patch in svn and wait for another bug before pushing an update for mga2.

I leave the bugreport open just in case.

regards
Julien
Comment 5 Manuel Hiebel 2013-10-22 12:09:30 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 6 Manuel Hiebel 2013-11-23 16:13:07 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: ASSIGNED => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.