Package Details: lagrange 1.13.6-1

Git Clone URL: https://aur.archlinux.org/lagrange.git (read-only, click to copy)
Package Base: lagrange
Description: Beautiful Gemini Client
Upstream URL: https://git.skyjake.fi/skyjake/lagrange
Licenses: BSD
Submitter: Roshless
Maintainer: Roshless
Last Packager: Roshless
Votes: 33
Popularity: 0.28
First Submitted: 2020-10-10 19:45 (UTC)
Last Updated: 2022-05-28 15:07 (UTC)

Pinned Comments

Roshless commented on 2020-11-04 08:20 (UTC) (edited on 2020-11-09 18:20 (UTC) by Roshless)

Instead of flagging this package out of date please send patches to repo using mailing list linked in index.md.

Tutorial: https://git-send-email.io/

Latest Comments

TrialnError commented on 2022-06-08 11:52 (UTC)

It isn't entirely impossible to have different build steps for split packages. In such cases the source directory will be duplicated.
One example for such a split package is doublecmd from the repos.
I may take a look at this. Depends if I'm getting to my system, don't forget it etc :D

m040601 commented on 2022-05-29 15:36 (UTC) (edited on 2022-05-29 16:16 (UTC) by m040601)

... and tried creating separate package for clagrange,...
....  now I'm even wondering how it's building ...
... 

I must also add that the Lagrange developer is very receptive and willing to help and troubleshoot any issues attempting this.

Although he doesnt like github, he mirrors Lagrange there. And responds to issues there.

I had opened an issue regarding "clagrange" and "lagrange-bin" previously, https://github.com/skyjake/lagrange/issues/508

Might be usefull for future AUR maintainers.

... I'm planning to make a binary TUI release, too, but I want to polish it still a bit more....

Regarding the "AppImage" and "Flatpaks" binaries he releases:

    On Archlinux it fails with "segmentation fault". ... meant to be used only on Ubuntu right ? ...

... It's not Ubuntu-specific, however AppImages are not fully self-contained so it's not universal either

And,

    wanted to install some man page in root "/", like "/lagrange/resources.lgr" and "/man/lagrange". Probably needs some adjustment.

Oops, let me fix that...

Roshless commented on 2022-05-28 17:28 (UTC)

Hey @m040601,

Wow, didn't know lagrange had cli version. I gave it a go and tried creating separate package for clagrange, since split packages can't have different build steps. Unfortunately I failed, can't get CMake to work, now I'm even wondering how it's building the_Fundation by itself in this package and why sealcurses can't get the same treatment.

I have to admit I'm not using lagrange very much these days, so I don't plan to spend much more time on researching CMake magic, if anyone is up for the task feel free to create clagrange package! :)

m040601 commented on 2022-05-26 07:25 (UTC) (edited on 2022-05-26 07:36 (UTC) by m040601)

First of all thank you for maintaining this PKGBUILD for this extraordinary piece of software.

And a small request.

As you can see at, https://git.skyjake.fi/gemini/lagrange

Compiling the TUI version

Lagrange has an optional text-mode interface that enables running the app in the terminal.
 This is disabled by the default build settings. Setting the ENABLE_TUI option to YES 
will replace the SDL dependency with a library called SEALCurses 
that implements the required parts of the SDL API on top of Curses. The resulting executable is called clagrange.

The requirements for building the TUI version are the same as with the GUI, 
except ncurses is required instead of SDL. HarfBuzz 
and all the image and audio dependencies are excluded from the TUI build.
....

And,

Build options
...
ENABLE_TUI  Build the TUI version (clagrange). The SEALCurses library is required: it is used instead of SDL.
....

It's not a different repo or project. It's the same source code as for the GUI version, that this "lagrange" PKGBUILD already fetches.

I'm very limited in understanding "cmake", "make", editing flags etc. But I desperately wanted to test this TUI version. So I just went ahead, git cloned, and just used the,

.... The build-tui.sh helper script is provided for building the TUI version. ....

It compiled OK, but wanted to install some man page in root "/", like "/lagrange/resources.lgr" and "/man/lagrange". Probably needs some adjustment.

Anyway. In the end you get an executable "clagrange".

Wow !!! What a nice piece of software for all the command line users lovers. It works with keyboard hints, key "f", for clicking the links. Just like Qutebrowser and Firefox Tridactyl etc. A must have for all keyboard fanatics. Really, really, snappy, performant and smooth experience. I think it even has some kind of acceleration. I havent seen another polished piece of terminal browser CLI software being developed lately.

I am not an expert in PKGBUILD's so my request would be:

  • Could you also build the "clagrange" from this same PKGBUILD ?
  • Or alternative provide a different/complementary PKGBUILD "clagrange" ? (That of course doesnt "clash" with the GUI Lagrange)

Thanks in advance.

Roshless commented on 2022-02-14 17:09 (UTC)

@dpirate Hi, according to this commit it should be autodetected. If it's not detected, you should probably report this on https://codeberg.org/skyjake/the_Foundation/issues

dpirate commented on 2022-02-14 05:37 (UTC)

Please consider adding -DTFDN_ENABLE_SSE41=OFF so this package doesn't SIGILL on AMD x86_64 CPUs older than Bulldozer.

TrialnError commented on 2022-01-29 17:59 (UTC)

I suppose mpg123 needs to be changed to depends. One machine didn't have it installed and lagrange failed to start, because it was missing libmpg123.so.0.
And readelf lists it as NEEDED.

Roshless commented on 2021-12-25 20:37 (UTC)

@xanc what fonts do you mean specifically? from what I remember lagrange uses fonts packed into zip font packs, is there even any reason to add these as opts?

xanc commented on 2021-12-23 07:35 (UTC)

Can you please put some fonts as optional dependencies? You can see that in about:version

Roshless commented on 2021-12-10 16:49 (UTC)

@Schnouki

Problem is, it works for me and I doubt many users have this problem.

https://imgur.com/O9BYeA0

From what you've told me sounds like you both have buggy drivers.

Schnouki commented on 2021-12-09 23:16 (UTC) (edited on 2021-12-09 23:17 (UTC) by Schnouki)

@Roshless @primalmotion I recently switched to Wayland (also with sway), and gave it a try.

Without ENABLE_POPUP_MENUS=NO:

  • lagrange starts with [window] renderer: opengl (accelerated)

  • then, when I click the hamburger menu, it doesn't open, and [window] renderer: software appears in my terminal. No crash, though.

  • (currently using sway-git, but also had the same issue with the latest stable version)

With ENABLE_POPUP_MENUS=NO:

  • lagrange starts with [window] renderer: opengl (accelerated)

  • then, when I click the hamberger menu, it opens, and there's nothing new in my terminal

So, adding ENABLE_POPUP_MENUS=NO looks like a great option to me :)

primalmotion commented on 2021-11-24 23:06 (UTC)

Interesting. I'm also using sway, but I use the master branch.

Roshless commented on 2021-11-24 21:39 (UTC)

I'm also on wayland (sway), lagrange works just fine for me.

[roshless@desktop ~]% lagrange Lagrange: A Beautiful Gemini Client [window] renderer: opengl (accelerated)

You sure it's not problem on your end? Looks like you are using software rendering for some reason.

primalmotion commented on 2021-11-24 20:15 (UTC)

The produced binary is broken for me (trying to open a popup makes Lagrange de crash). It seems an additional option is necessary (at least for wayland). Please refer to this Github discussion:

https://github.com/skyjake/lagrange/issues/398#issuecomment-978099585

TrialnError commented on 2021-11-08 07:56 (UTC)

Is zip a runtime or buildtime dep?
Reading the changelog they only name it as a builddep. If so it should be adjusted in the PKGBUILD.

Roshless commented on 2021-11-04 12:38 (UTC)

https://github.com/skyjake/lagrange/issues/369 dependency added

dmerejkowsky commented on 2021-11-04 09:18 (UTC)

I can reproduce the bug using extra-x86-64-build (to build the package in a clean chroot), so there's probably a missing dep in the PKGBUILD

riri commented on 2021-11-03 19:32 (UTC)

I have the same problem when compiling on x86-64 (building from aur with yay)

aur/lagrange  1.7.2-1 -> 1.8.0-1

I was able to build previous versions on the Pinebook Pro using Manjaro ARM. Sadly 1.8 isn't building. Here are my errors: https://paste.sr.ht/~skyfaller/7ee71bc1a156693265d354c6bf4c3a311b0f02ea

dmerejkowsky commented on 2021-11-02 09:16 (UTC)

That would make sense, given that unbundling fonts was the major change for this release

Agreed. But I don't have a Arm machine to check it out. Maybe open an issue upstream ?

skyfaller commented on 2021-11-01 18:40 (UTC)

I was able to build previous versions on the Pinebook Pro using Manjaro ARM. Sadly 1.8 isn't building. Here are my errors: https://paste.sr.ht/~skyfaller/7ee71bc1a156693265d354c6bf4c3a311b0f02ea

Any idea what the problem may be? Looks to me like it might need a fontpack? That would make sense, given that unbundling fonts was the major change for this release: gemini://skyjake.fi/gemlog/2021-10_lagrange-1.8.gmi

dmerejkowsky commented on 2021-07-31 12:33 (UTC)

I've built this package on an armv7h Arch Linux ARM device and am using it without problems. Would you consider adding armv7h to the archs?

Sure thing !

autumnontape commented on 2021-07-31 11:06 (UTC)

I've built this package on an armv7h Arch Linux ARM device and am using it without problems. Would you consider adding armv7h to the archs?

dmerejkowsky commented on 2021-07-08 10:59 (UTC) (edited on 2021-07-08 11:00 (UTC) by dmerejkowsky)

The high CPU usage bug when scrolling should have been fixed in 1.5.2-2 - thank you for the bug report :)

dmerejkowsky commented on 2021-07-05 10:23 (UTC)

Patch sent. I think it's a good idea - also, it's done in for the Debian packages.

central_thing commented on 2021-07-03 21:34 (UTC)

Even on my relatively powerful ThinkPad T490, I must set -DENABLE_KERNING=OFF to prevent high CPU usage when scrolling through moderate amounts of text (a few screens). In the project README, this option is recommended for "slower cpus" and RPis, though.

autumnontape commented on 2021-05-17 20:46 (UTC)

Indeed, 1.4.1-1 builds fine for me with the default CFLAGS. Thanks!

dmerejkowsky commented on 2021-05-13 16:01 (UTC)

Patch for 1.4.1-1 has been sent and compiles fine here :)

dmerejkowsky commented on 2021-05-09 19:14 (UTC) (edited on 2021-05-09 19:14 (UTC) by dmerejkowsky)

aaronfischer: we're on the right track - the bug should be fixed in the text Lagrange release after 1.4.0.

Note that the workaround described below should still work :)

aaronfischer commented on 2021-05-09 19:06 (UTC)

Can you please apply this fix to the package? https://github.com/skyjake/lagrange/issues/270

dmerejkowsky commented on 2021-05-08 11:33 (UTC)

The error persists with a clean build of 1.4.0-1

Indeed, we went from

"cc1: all warnings being treated as errors"

to

"cc1: some warnings being treated as errors"

To be continued ...

autumnontape commented on 2021-05-08 05:12 (UTC)

The error persists with a clean build of 1.4.0-1 with the default CFLAGS. It seems gcc treats this as an error even without -Werror.

dmerejkowsky commented on 2021-05-04 11:10 (UTC) (edited on 2021-05-04 11:14 (UTC) by dmerejkowsky)

That's expected. The PKGBUILD has been fixed to add the appropriate flags, but the upstream source code does not use it yet. You should wait for version 1.3.5 or something - or use the workaround described below.

autumnontape commented on 2021-05-04 06:49 (UTC)

I still get the same error when building 1.3.4-3 with the default CFLAGS in /etc/makepkg.conf. It shouldn't make a difference in this case, but it was a clean build.

dmerejkowsky commented on 2021-05-03 14:43 (UTC)

Good news: the_Foundation can now be built without -Werror.

I've send a patch to set TFDN_ENABLE_WERROR=OFF so the issue should be fixed in the next lagrange release

xanc commented on 2021-05-02 11:43 (UTC)

I get this error:

[code] [ 1%] Building C object lib/the_Foundation/CMakeFiles/the_Foundation.dir/src/the_foundation.c.o cc1: error: ‘-Wformat-security’ ignored without ‘-Wformat’ [-Werror=format-security] cc1: all warnings being treated as errors make[2]: [lib/the_Foundation/CMakeFiles/the_Foundation.dir/build.make:76: lib/the_Foundation/CMakeFiles/the_Foundation.dir/src/the_foundation.c.o] Error 1 make[2]: Leaving directory '/home/xan/aur/gemini-lagrange/lagrange/src/build' make[1]: [CMakeFiles/Makefile2:126: lib/the_Foundation/CMakeFiles/the_Foundation.dir/all] Error 2 make[1]: Leaving directory '/home/xan/aur/gemini-lagrange/lagrange/src/build' make: *** [Makefile:136: all] Error 2 make: Leaving directory '/home/xan/aur/gemini-lagrange/lagrange/src/build' ==> ERROR: Ha ocorregut una fallada a build(). Es cancel·la...

[/code]

dmerejkowsky commented on 2021-04-29 14:02 (UTC) (edited on 2021-04-29 14:06 (UTC) by dmerejkowsky)

Good news! The bug in the_Foundation is being fixed upstream.

https://codeberg.org/skyjake/the_Foundation/issues/6

I'll update the pkgbuild when the fix is available, and I'll take care of the CMAKE_BUILD_TYPE issue then.

As a workaround, you can build the package this way:

rm -fr src/build/

makepkg \
  CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \
  -Wp,-D_FORTIFY_SOURCE=2,-D_GLIBCXX_ASSERTIONS \
   -fstack-clash-protection -fcf-protection" \
   -f

dmerejkowsky commented on 2021-04-29 13:15 (UTC)

I think I understood what happened.

First, there was an RFC https://gitlab.archlinux.org/archlinux/rfcs/-/blob/master/rfcs/0003-buildflags.rst to change the default flags in makepkg.conf

It was implemented in the pacman package itself in this commit: https://github.com/archlinux/svntogit-packages/commit/a790c389cb0fd2ddd35e1f581ee337f6891801fc#diff-8da5d04d27b7ace195751c5e1e5e52c0bbd59e1ec3fd89d656496cc1d272d4b0

Finally, the_foundation also sets some warning flags, and crucially, -Werror, which causes the build to fail because the warning flags are not compatible with each other.

jarek: good point about CMAKE_BUILD_TYPE, but I'm not sure it fixes the issue - I'll take a look.

autumnontape commented on 2021-04-29 05:51 (UTC)

Removing -Werror=format-security from CFLAGS in /etc/makepkg.conf fixed the build for me.

Jarek_jre commented on 2021-04-29 01:47 (UTC)

@dmerejkowsky check your /etc/makepkg.conf, I bet there's something like Wformat in CFLAGS.

Also, I noticed that this PKGBUILD uses CMAKE_BUILD_TYPE=Release which is agains the guidelines. https://wiki.archlinux.org/index.php/CMake_package_guidelines

dmerejkowsky commented on 2021-04-28 15:45 (UTC)

No error in a clean chroot either. This is really weird

dmerejkowsky commented on 2021-04-28 14:35 (UTC)

Upstream bug here : https://codeberg.org/skyjake/the_Foundation/issues/6

It's a bad idea to enable Werror anyway, but it sure would be nice to know what package is causing the issue ;)

Roshless commented on 2021-04-28 14:33 (UTC)

Just tried compiling with extra-x86_64-build in clean chroot and no errors there, can you two also try?

dmerejkowsky commented on 2021-04-28 14:28 (UTC)

OK, the error comes when compiling the_Foundation, not lagrange. I'll open a bug upstream

BachoSeven commented on 2021-04-28 14:15 (UTC)

@Roshless I had tried cloning and using makepkg -si, I get the same build error.

dmerejkowsky commented on 2021-04-28 14:14 (UTC)

works for me with makepkg and yay

Interesting. I'm also using makepkg and yay and have the same failure. It worked when I made the patch on March 30th. Further investigation is required

Roshless commented on 2021-04-28 14:11 (UTC)

@dmerejkowsky its your aur pkg manager, works for me with makepkg and yay

dmerejkowsky commented on 2021-04-28 14:08 (UTC)

I think the culprit is here

cc1: error: ‘-Wformat-security’ ignored without ‘-Wformat’ [-Werror=format- security cc1: all warnings being treated as errors

but I don't get what's happening here :/

BachoSeven commented on 2021-04-28 14:02 (UTC)

Build is failing:

[  3%] Building C object lib/the_Foundation/CMakeFiles/the_Foundation.dir/src/block.c.o
cc1: error: ‘-Wformat-security’ ignored without ‘-Wformat’ [-Werror=format-security]
[  4%] Building C object lib/the_Foundation/CMakeFiles/the_Foundation.dir/src/blockhash.c.o
[  5%] Building C object lib/the_Foundation/CMakeFiles/the_Foundation.dir/src/audience.c.o
cc1: error: ‘-Wformat-security’ ignored without ‘-Wformat’ [-Werror=format-security]
cc1: error: ‘-Wformat-security’ ignored without ‘-Wformat’ [-Werror=format-security]
cc1: error: ‘-Wformat-security’ ignored without ‘-Wformat’ [-Werror=format-security]
cc1: error: ‘-Wformat-security’ ignored without ‘-Wformat’ [-Werror=format-security]
cc1: all warnings being treated as errors
make[2]: *** [lib/the_Foundation/CMakeFiles/the_Foundation.dir/build.make:76: lib/the_Foundation/CMakeFiles/the_Foundation.dir/src/the_foundation.c.o] Error 1
make[2]: *** Waiting for unfinished jobs....
cc1: all warnings being treated as errors
make[2]: *** [lib/the_Foundation/CMakeFiles/the_Foundation.dir/build.make:90: lib/the_Foundation/CMakeFiles/the_Foundation.dir/src/audience.c.o] Error 1
cc1: all warnings being treated as errors
make[2]: *** [lib/the_Foundation/CMakeFiles/the_Foundation.dir/build.make:132: lib/the_Foundation/CMakeFiles/the_Foundation.dir/src/blockhash.c.o] Error 1
cc1: all warnings being treated as errors
make[2]: *** [lib/the_Foundation/CMakeFiles/the_Foundation.dir/build.make:104: lib/the_Foundation/CMakeFiles/the_Foundation.dir/src/array.c.o] Error 1
cc1: all warnings being treated as errors
make[2]: *** [lib/the_Foundation/CMakeFiles/the_Foundation.dir/build.make:118: lib/the_Foundation/CMakeFiles/the_Foundation.dir/src/block.c.o] Error 1
make[2]: Leaving directory '/home/fra/.cache/paru/clone/lagrange/src/build'
make[1]: *** [CMakeFiles/Makefile2:126: lib/the_Foundation/CMakeFiles/the_Foundation.dir/all] Error 2
make[1]: Leaving directory '/home/fra/.cache/paru/clone/lagrange/src/build'
make: *** [Makefile:136: all] Error 2

asterisc commented on 2021-01-15 16:37 (UTC)

This package does not need an extra desktop file. The "make install" step is already creating one, leading to two application shortcuts.

makeworld commented on 2020-12-31 17:59 (UTC)

As per the README, pcre, zlib, and libunistring should all be listed as depedencies. mpg123 should be listed as an optional dependency.

Also, could this package add a .desktop file for Lagrange?

Roshless commented on 2020-11-28 20:34 (UTC)

@Aicaya it probably is rspamd's greylisting, seems like 10-15 minutes delay.

Yeah that's the main reason why I stopped bothering updating it myself, skyjake's speed is insane.

Aicaya commented on 2020-11-28 20:15 (UTC) (edited on 2020-11-28 20:17 (UTC) by Aicaya)

Sent patch to update version to 0.11.0 (my goodness, Lagrange updates fast). Mailing list doesn't seem to update automatically, so posting a comment here just in case someone else planned on sending one.

dmerejkowsky commented on 2020-11-16 20:11 (UTC)

Well, the patch is here now : https://lists.roshless.me/~roshless/public-inbox/patches/1

Sorry for the noise.

dmerejkowsky commented on 2020-11-16 19:55 (UTC)

I used:

git send-email --to ~roshless/public-inbox@lists.roshless.me HEAD~1

dmerejkowsky commented on 2020-11-16 19:51 (UTC)

Patch sent but for some reason it does not show up in the archives here : https://lists.roshless.me/~roshless/public-inbox

Roshless commented on 2020-11-04 08:20 (UTC) (edited on 2020-11-09 18:20 (UTC) by Roshless)

Instead of flagging this package out of date please send patches to repo using mailing list linked in index.md.

Tutorial: https://git-send-email.io/