From: Julien Lepiller <julien@lepiller.eu>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 30123-close@debbugs.gnu.org
Subject: bug#30123: claws-mail plugins not updated
Date: Wed, 24 Nov 2021 20:28:23 -0500 [thread overview]
Message-ID: <A52C4067-4132-4DDD-89AE-BA0C58CF9B79@lepiller.eu> (raw)
In-Reply-To: <86czmpt9iz.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
The problem seems to be solved now. Thanks for reminding me of my old bugs :). Closing.
Le 24 novembre 2021 18:32:20 GMT-05:00, zimoun <zimon.toutoune@gmail.com> a écrit :
>Hi Julien,
>
>On Mon, 15 Jan 2018 at 14:52, julien lepiller <julien@lepiller.eu> wrote:
>
>> claws-mail has a plugin system to add functionnality. For instance, to add PGP
>> support, one has to load 3 plugins from the claws-mail package. By default,
>> claws-mail looks in its store directory to propose available plugins.
>>
>> When upgrading claws-mail, the configuration doesn't change. Plugins are still
>> looked for in the old store location, so old plugins are still used. This is
>> bad for security and compatibility. Another issue is when running guix gc
>> afterwards: the old plugins are deleted and claws-mail issues an error message
>> on startup because it cannot find them anymore.
>
>Reading the recent activity about claws-mail, is it still an issue?
>
>Cheers,
>simon
[-- Attachment #2: Type: text/html, Size: 1390 bytes --]
prev parent reply other threads:[~2021-11-25 1:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 13:52 bug#30123: claws-mail plugins not updated julien lepiller
2018-01-15 16:18 ` Danny Milosavljevic
2018-01-19 16:55 ` Julien Lepiller
2018-01-21 11:59 ` Danny Milosavljevic
2018-01-21 13:34 ` Julien Lepiller
2018-01-21 14:44 ` Danny Milosavljevic
2018-01-21 18:25 ` Julien Lepiller
2021-11-24 23:32 ` zimoun
2021-11-25 1:28 ` Julien Lepiller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A52C4067-4132-4DDD-89AE-BA0C58CF9B79@lepiller.eu \
--to=julien@lepiller.eu \
--cc=30123-close@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).