Hi Michiel: On 05/24/2019 09:17:11 AM Fri, [email protected] wrote:
Hello Peter,Thanks for your reply, On 23-05-19 05:35:58, Peter Bloomfield wrote: > This seems to be a Fedora packaging issue. Builds from GitLab's master > branch show HTML content correctly in my experience. The F30 package > seems to link correctly to the webkit lib, but I see the same issue > with HTML content.
I was wrong there: it's not the Fedora packaging, it seems to be the tarball <URL:https://pawsa.fedorapeople.org/balsa/balsa-2.5.6.tar.bz2> itself. I just built Balsa from it with: ./configure --with-libsecret --with-gtksourceview --with-gpgme make src/balsa and again it shows no HTML content. I'm puzzled about what has happened. I was using Balsa built from git's master branch around the time the tarball was made, and I don't recall any version that had HTML issues. Balsa's HTML code has seen a few changes since 2.5.6 was released, and of course WebKit has been updated continually, but as far as I know none of the changes were related to a blank page.
So if I understand correctly, upgrading to F30 won't resolve the issue? So I guess the best way to proceed is to file a bug at Fedora? I have a https://bugzilla.redhat.com account. (Any addional information I should submit?)
So no, a Fedora bug would just be bumped upstream, because any build from that tarball can show the issue. Waiting for the forthcoming new release may be the best option. Best, Peter
pgp0CnhadVHcL.pgp
Description: PGP signature
_______________________________________________ balsa-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/balsa-list
