Re: [Pan-users] [ANNOUNCE] Pan release 0.150

[Duncan]

Dominique Dumont posted on Wed, 02 Mar 2022 19:02:34 +0100 as excerpted:

> On Wednesday, 2 March 2022 11:31:00 CET Duncan wrote:
> 
>> Working here (gentoo, building from git), but still crashy.  In
>> particular I've found pan crashes quite reliably if I hover the mouse
>> over the body pane, so apparently some pointer event triggering it. 
>> I've not debugged beyond that.  If I steer clear of the body pane
>> (literally, maneuver the mouse around it so as to avoid triggering that
>> crash), pan's reasonably stable.
> 
> Weird, I've no such crash on Debian unstable.
> 
> What autogen flags are you using ?

My autotools foo isn't the best (it's an old gentoo pan live-git ebuild 
which I've updated with new deps and options over the years, they dropped 
the live ebuild years ago and dropped pan entirely a year or so ago, once 
it stabilizes on gtk3/gmime3 I'll put in a bug request to add it again) so 
I'm not entirely sure this answers your question, but...

./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-
linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/
usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-
tracking --disable-silent-rules --docdir=/usr/share/doc/pan-9999 --
htmldir=/usr/share/doc/pan-9999/html --libdir=/usr/lib64 --disable-
maintainer-mode --disable-nls --without-yelp-tools --without-webkit --
without-gmime-crypto --with-dbus --disable-gkr --with-gtkspell --disable-
libnotify --with-gnutls

... and the summary...

Configuration:

Prefix:                 /usr
Source code location:   .
Compiler:               x86_64-pc-linux-gnu-g++
With D-Bus:             yes
With GMime crypto:      no
With GtkSpell:          yes (3.0.10 2.3.2)
With GTK 3:             yes (3.24.31)
With WebKitGTK:         no
With GnuTLS:            yes (3.7.3)
With libnotify:
With password storage:
With yelp-tools:        no
With user manual:       no

And FWIW, the direct deps with versions -- versions listed outside 
parentheses are what I have, in-parantheses are what the ebuild says is 
needed, and in-square-brackets is the USE flags (configure options) 
required on the deps, if any (elt-patches are libtool related, xz-utils 
was probably for the tarball only and unnecessary for the git build but 
other things pull it in anyway so no big deal):


* dependency graph for net-nntp/pan-9999
`--  net-nntp/pan-9999  ~amd64
`--  dev-libs/glib-2.70.4  (>=dev-libs/glib-2.26) ~amd64
`--  sys-libs/zlib-1.2.11-r4  (>=sys-libs/zlib-1.2.0) amd64
`--  x11-libs/gtk+-3.24.31  (x11-libs/gtk+) ~amd64
`--  x11-libs/libnotify-0.7.9-r1  (>=x11-libs/libnotify-0.4.1) amd64
`--  dev-libs/gmime-3.2.7  (dev-libs/gmime) amd64  [crypt=]
`--  app-text/enchant-2.3.2  (app-text/enchant) ~amd64
`--  app-text/gtkspell-3.0.10  (app-text/gtkspell) amd64
`--  net-libs/gnutls-3.7.3  (>=net-libs/gnutls-3) ~amd64
`--  sys-devel/gettext-0.21-r1  (>=sys-devel/gettext-0.19.7) amd64
`--  virtual/pkgconfig-2-r1  (virtual/pkgconfig) amd64
`--  sys-devel/gnuconfig-20210107  (sys-devel/gnuconfig) ~amd64
`--  app-portage/elt-patches-20211104  (>=app-portage/elt-
patches-20170815) ~amd64
`--  sys-devel/automake-1.16.5  (>=sys-devel/automake-1.16.4) ~amd64
`--  sys-devel/autoconf-2.71-r1  (>=sys-devel/autoconf-2.71) ~amd64
`--  sys-devel/libtool-2.4.6-r6  (>=sys-devel/libtool-2.4) amd64
`--  app-arch/xz-utils-5.2.5-r1  (app-arch/xz-utils) amd64
`--  dev-util/desktop-file-utils-0.26-r1  (dev-util/desktop-file-utils) 
amd64
`--  x11-misc/shared-mime-info-2.1  (x11-misc/shared-mime-info) amd64
`--  dev-vcs/git-2.35.1  (>=dev-vcs/git-1.8.2.1) ~amd64  [curl]
[ net-nntp/pan-9999 stats: packages (20), max depth (1) ]

>> And some of my replies still aren't showing up, tho that's using gmane
>> so could be a problem with its forwarding to the mailing lists or with
>> the mailing list processing, as opposed to a problem with pan.  It's
>> also possible it could be a bug in the particular gmime version (3.2.7)
>> gentoo currently has available.
> 
> You can check what's sent to gmane using --debug option. The trick is to
> check whether the message is valid or not.

For awhile gmane was rejecting them -- the activity log (not debug, just 
activity log) said so.  Now it says accepted and forwarded to moderators 
(the mailing lists in gmane's case).  So it seems they're valid enough to 
get accepted by gmane now, but some still aren't showing up on the gmane 
"groups" after forwarding thru the lists.  Like I said, could be a list 
thing (there were definitely invalidity problems before but I've not seen 
any for awhile).

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman