From: TwinkleToes777 <TwinkleToes777@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Dovecot package is broken in various ways
Date: Tue, 09 Aug 2022 21:05:57 +0200 [thread overview]
Message-ID: <20220809190557.gKGkFhGMzVE8QLm7RbS3QFD8PpppBDHStq5AwGIitoM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38551@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
New comment by TwinkleToes777 on void-packages repository
https://github.com/void-linux/void-packages/issues/38551#issuecomment-1209767981
Comment:
I'm glad it works for you, I am using a VPS too.
here are the install logs (I uninstalled and installed again):
```
[*] Verifying package integrity
mit-krb5-libs-1.18.3_2: verifying RSA signature...
dovecot-2.3.19.1_1: verifying RSA signature...
[*] Collecting package files
mit-krb5-libs-1.18.3_2: collecting files...
dovecot-2.3.19.1_1: collecting files...
[*] Unpacking packages
mit-krb5-libs-1.18.3_2: unpacking ...
dovecot-2.3.19.1_1: unpacking ...
[*] Configuring unpacked packages
mit-krb5-libs-1.18.3_2: configuring ...
mit-krb5-libs-1.18.3_2: installed successfully.
dovecot-2.3.19.1_1: configuring ...
Updated _dovecot system user.
Updated _dovenull system user.
dovecot-2.3.19.1_1: installed successfully.
```
This is a pretty clean void linux install, hasn't been running for long yet, I just migrated from ubuntu where dovecot worked
next prev parent reply other threads:[~2022-08-09 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 9:09 [ISSUE] " TwinkleToes777
2022-08-09 11:21 ` Anachron
2022-08-09 19:04 ` TwinkleToes777
2022-08-09 19:05 ` TwinkleToes777 [this message]
2022-08-09 19:25 ` Anachron
2022-08-09 19:47 ` TwinkleToes777
2022-08-09 19:58 ` Anachron
2022-08-09 20:28 ` [ISSUE] [CLOSED] " TwinkleToes777
2022-08-09 20:28 ` TwinkleToes777
2022-08-09 20:31 ` Anachron
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220809190557.gKGkFhGMzVE8QLm7RbS3QFD8PpppBDHStq5AwGIitoM@z \
--to=twinkletoes777@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).