> On December 28, 2017 at 12:39 AM Noel Butler wrote:
>
>
> On 28/12/2017 07:38, Howard Leadmon wrote:
>
> > Saw the new repository notification, and figured what the heck I would try
> > letting it upgrade me from the current v2.2.22 release that apparently is
> >
On 12/27/17 4:38 PM, Howard Leadmon wrote:
> Saw the new repository notification, and figured what the heck I
> would try letting it upgrade me from the current v2.2.22 release that
> apparently is in the Ubuntu 16.04 packages, to the new repository
> release of v2.3.0.
>
> I followed the
Another thing to check is the RPM scripts that run during an upgrade.
Compare the output of "rpm -q --scripts dovecot" for the old and new
package. See if the new package is doing all the necessary things
expected by Ubuntu. Scripts are the most platform-specific part of the
package and the
The problem would appear that pam is reporting a system error, which fails your
authentication. Are you supposed to be using pam?
Aki
> On December 28, 2017 at 12:50 AM Howard Leadmon wrote:
>
>
> I hear what your saying, but if you read and follow the repo page, it
>
I hear what your saying, but if you read and follow the repo page, it
says run update, and then upgrade. Also as a test, I did remove the
old 2.2 code, and installed the new 2.3 code, and again authentication
fails.
I am sure I may be missing something stupid, but the bottom line is,
On 28/12/2017 07:38, Howard Leadmon wrote:
> Saw the new repository notification, and figured what the heck I would try
> letting it upgrade me from the current v2.2.22 release that apparently is in
> the Ubuntu 16.04 packages, to the new repository release of v2.3.0.
>
> I followed the info
Saw the new repository notification, and figured what the heck I
would try letting it upgrade me from the current v2.2.22 release that
apparently is in the Ubuntu 16.04 packages, to the new repository
release of v2.3.0.
I followed the info on repo.dovecot.org, and first it started