From: "Clément Lassieur" <clement@lassieur.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Andy Wingo <wingo@igalia.com>,
Bake Timmons <b3timmons@speedymail.org>,
25802-done@debbugs.gnu.org
Subject: bug#25802: Unable to run dovecot w/ non-opaque configuration
Date: Sun, 23 Apr 2017 01:50:20 +0200 [thread overview]
Message-ID: <87pog4uhmr.fsf@lassieur.org> (raw)
In-Reply-To: <87a878f1yv.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Hi Bake,
>
> Bake Timmons <b3timmons@speedymail.org> skribis:
>
>> Trying to reconfigure my system running guix 0.12.0 for dovecot with
>> the default configuration object created by '(dovecot-configuration)'
>> results in:
>>
>> guix system: error: exception thrown: #<condition %compound [message: "Invalid value for field path: \"lmtp\""] 4a6a140>
>>
>> Adding a services list to the above works around the above error and
>> allows 'guix system reconfigure' to complete successfully. However,
>> the generated dovecot.conf is rejected by doveconf:
>>
>> doveconf: Error in configuration file /gnu/store...dove.cot.conf line 1: Expecting '{'
>>
>>From my limited acquaintance with dovecot, the guix-generated syntax of, say,
>> ImapMaxLineLength 64000
>>
>> disagrees with what I gather to be the normal dovecot.conf syntax of
>> imap_max_line_length = 64000
>
> Clément, Andy: WDYT? :-)
>
> I suspect commit 56aef188a2a014e254d3c93c8a79cd1fb5a1ece6 by Clément
> might have fixed the syntax issue reported here.
Indeed this has been fixed, I'm closing the bug. Bake, if you still
reproduce after making sure you're up-to-date, do not hesitate to
re-open. :)
Clément
next prev parent reply other threads:[~2017-04-22 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 22:20 bug#25802: Unable to run dovecot w/ non-opaque configuration Bake Timmons
2017-04-22 23:37 ` Ludovic Courtès
2017-04-22 23:50 ` Clément Lassieur [this message]
2017-04-23 0:01 ` Clément Lassieur
2017-04-23 13:45 ` Bake Timmons
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=87pog4uhmr.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=25802-done@debbugs.gnu.org \
--cc=b3timmons@speedymail.org \
--cc=ludo@gnu.org \
--cc=wingo@igalia.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).