From: Leah Neukirchen <leah@vuxu.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [ANNOUNCE] public-inbox 1.6.0
Date: Sat, 19 Sep 2020 22:01:18 +0200 [thread overview]
Message-ID: <87y2l5r0xd.fsf@vuxu.org> (raw)
In-Reply-To: <20200916200309.public-inbox-1.6.0-rele@sed> (Eric Wong's message of "Wed, 16 Sep 2020 20:03:24 +0000")
Hi,
thanks for the release!
Eric Wong <e@80x24.org> writes:
> * Upgrading for new features in 1.6
>
> The ordering of these steps is only necessary if you intend to
> use some new features in 1.6. Future releases may have
> different instructions (or be entirely transparent).
>
> 0. install (use your OS package manager, or "make install")
>
> 1. restart public-inbox-watch instances if you have any
>
> 2. Optional: remove Plack::Middleware::Deflater if you're using
> a custom .psgi file for PublicInbox::WWW. This only saves
> some memory and CPU cycles, and you may also skip this step
> if you expect to roll back to 1.5.0 for any reason.
>
> Steps 3a and 3b may happen in any order, 3b is optional
> and is only required to use new WWW and IMAP features.
>
> 3a. restart existing read-only daemons if you have them
> (public-inbox-nntpd, public-inbox-httpd)
>
> 3b. run "public-inbox-index -c --reindex --rethread --all"
> to reindex all configured inboxes
>
> 4. configure and start the new public-inbox-imapd. This
> requires reindexing in 3b, but there's no obligation to
> run an IMAP server, either.
I did all these steps in this order, NNTP works fine but IMAP shows
all folders as empty. Any ideas how to debug this?
thx,
--
Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org/
next prev parent reply other threads:[~2020-09-19 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 20:03 [ANNOUNCE] public-inbox 1.6.0 Eric Wong
2020-09-19 20:01 ` Leah Neukirchen [this message]
2020-09-19 21:17 ` Eric Wong
2020-09-19 21:24 ` Leah Neukirchen
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2l5r0xd.fsf@vuxu.org \
--to=leah@vuxu.org \
--cc=e@80x24.org \
--cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.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).