Upgrade from ver 2.2 to 2.5

[Jim Jackson]

Hi,

I've downloaded version 2.5 of alpine and compiled it - on a Devuan
Beowulf system (essentially Debian without systemd).

When I run this new version it doesn't seem to interpret my existing 2.2
config correctly. I don't see my default inbox - which uses ssh to
access alpine imapd on a server.

My system has a system wide /etc/pine.conf which I don't think the 2.5
version is reading. Is this correct? Has the name changed?

cheers
Jim

[Eduardo Chappa]

Post by Jim Jackson
I've downloaded version 2.5 of alpine and compiled it - on a Devuan
Beowulf system (essentially Debian without systemd).
When I run this new version it doesn't seem to interpret my existing 2.2
config correctly. I don't see my default inbox - which uses ssh to
access alpine imapd on a server.
My system has a system wide /etc/pine.conf which I don't think the 2.5
version is reading. Is this correct? Has the name changed?

Dear Jim,

maybe Debian compiles using some options that alter the behavior of
Alpine. Maybe you can find someone who runs Alpine is a debian-like system
and aske them to give you the output of the command

$ alpine -v

current versions of Alpine give you the options that were passed to the
configure script, and hopefully that will help you in this case to return
Alpine to what it used to be.

Thank you.

[Roderick]

Post by Eduardo Chappa
Dear Jim,
maybe Debian compiles using some options that alter the behavior of Alpine.
Maybe you can find someone who runs Alpine is a debian-like system and aske
them to give you the output of the command
$ alpine -v

I have alpine on a debian computer, just installed with apt-get install.
I get this:

# alpine -v
Alpine 2.24 (DEB 510 2020-10-10) built Tue Oct 13 19:47:59 UTC 2020 on
debian
Alpine was built with the following options:
CFLAGS=-g -O2 -fdebug-prefix-map=/build/alpine-Aemf12/alpine-2.24+dfsg1=.
-fstack-protector-strong -Wformat -Werror=format-security
LDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed
CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2
./configure --build=x86_64-linux-gnu --prefix=/usr \
--includedir=${prefix}/include --mandir=${prefix}/share/man \
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var \
--disable-option-checking --disable-silent-rules \
--libdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run \
--disable-maintainer-mode --disable-dependency-tracking \
--with-system-pinerc=/etc/pine.conf \
--with-system-fixed-pinerc=/etc/pinerc.fixed \
--with-passfile=.pine-passfile --with-smtp-msa=/usr/sbin/sendmail \
--with-debug-level=0 --with-date-stamp=Tue Oct 13 19:47:59 UTC 2020 \
--with-host-stamp=debian --without-tcl --with-krb5 --with-krb5-dir=/usr \
build_alias=x86_64-linux-gnu

The alpine I use is self compiled in Free- or OpenBSD with very few
compile options.

[Jim Jackson]

Post by Eduardo Chappa

Post by Jim Jackson
I've downloaded version 2.5 of alpine and compiled it - on a Devuan
Beowulf system (essentially Debian without systemd).
When I run this new version it doesn't seem to interpret my existing 2.2
config correctly. I don't see my default inbox - which uses ssh to
access alpine imapd on a server.
My system has a system wide /etc/pine.conf which I don't think the 2.5
version is reading. Is this correct? Has the name changed?

Dear Jim,
maybe Debian compiles using some options that alter the behavior of
Alpine. Maybe you can find someone who runs Alpine is a debian-like system
and aske them to give you the output of the command
$ alpine -v
current versions of Alpine give you the options that were passed to the
configure script, and hopefully that will help you in this case to return
Alpine to what it used to be.

# alpine -v
Alpine 2.21 (DEB 202 2017-01-01) built Sat, 12 Jan 2019 07:42:50 +0100 on debian

I was wrong about the version - sorry.

[Jim Jackson]

Post by Eduardo Chappa

Post by Jim Jackson
I've downloaded version 2.5 of alpine and compiled it - on a Devuan
Beowulf system (essentially Debian without systemd).
When I run this new version it doesn't seem to interpret my existing 2.2
config correctly. I don't see my default inbox - which uses ssh to
access alpine imapd on a server.
My system has a system wide /etc/pine.conf which I don't think the 2.5
version is reading. Is this correct? Has the name changed?

Dear Jim,
maybe Debian compiles using some options that alter the behavior of
Alpine. Maybe you can find someone who runs Alpine is a debian-like system
and aske them to give you the output of the command
$ alpine -v
current versions of Alpine give you the options that were passed to the
configure script, and hopefully that will help you in this case to return
Alpine to what it used to be.
Thank you.

Ok. I've investigated further. Use strings on the 2.21 binary and the
2.25 binary I see that the debian on has the system wide config as
/etc/pine.conf and the self-compiled one is /usr/local/lib/pine.conf

I will play with this and get back.

cheers
Jim

[Jim Jackson]

Post by Jim Jackson

Post by Eduardo Chappa

Post by Jim Jackson
I've downloaded version 2.5 of alpine and compiled it - on a Devuan
Beowulf system (essentially Debian without systemd).
When I run this new version it doesn't seem to interpret my existing 2.2
config correctly. I don't see my default inbox - which uses ssh to
access alpine imapd on a server.
My system has a system wide /etc/pine.conf which I don't think the 2.5
version is reading. Is this correct? Has the name changed?

Dear Jim,
maybe Debian compiles using some options that alter the behavior of
Alpine. Maybe you can find someone who runs Alpine is a debian-like system
and aske them to give you the output of the command
$ alpine -v
current versions of Alpine give you the options that were passed to the
configure script, and hopefully that will help you in this case to return
Alpine to what it used to be.
Thank you.

Ok. I've investigated further. Use strings on the 2.21 binary and the
2.25 binary I see that the debian on has the system wide config as
/etc/pine.conf and the self-compiled one is /usr/local/lib/pine.conf
I will play with this and get back.

Ok now seems to be working. I just soft linked /usr/local/lib/pine.conf
to /etc/pine.conf

Now to test getting gmail working with OAuth2 - for one of my other
mailboxes.

cheers
Jim

[mechanic]

Post by Jim Jackson
...
I see that the debian on has the system wide config as
/etc/pine.conf and the self-compiled one is /usr/local/lib/pine.conf

If you really mean the personal prefs file that's usually in your
home directory. I use the parameter '-p' to specify a specific file
as the personal prefs file for Alpine.

[Jim Jackson]

Post by mechanic

Post by Jim Jackson
...
I see that the debian on has the system wide config as
/etc/pine.conf and the self-compiled one is /usr/local/lib/pine.conf

If you really mean the personal prefs file that's usually in your
home directory. I use the parameter '-p' to specify a specific file
as the personal prefs file for Alpine.

There is a system wide configuration file as well as the personal one in
the home directory! It's been that way for a very long time.

[mechanic]

Post by Jim Jackson

Post by mechanic

Post by Jim Jackson
...
I see that the debian on has the system wide config as
/etc/pine.conf and the self-compiled one is /usr/local/lib/pine.conf

If you really mean the personal prefs file that's usually in your
home directory. I use the parameter '-p' to specify a specific file
as the personal prefs file for Alpine.

There is a system wide configuration file as well as the personal one in
the home directory! It's been that way for a very long time.

Sure, we know that, it rather depends on what the user in question
wants.