Package Details: ly-git 0.5.3.r5.g609b3f9-1

Git Clone URL: https://aur.archlinux.org/ly-git.git (read-only, click to copy)
Package Base: ly-git
Description: TUI display manager
Upstream URL: https://github.com/nullgemm/ly
Licenses: custom:WTFPL
Conflicts: ly, python-ly-git
Submitter: nullgemm
Maintainer: steffeno
Last Packager: steffeno
Votes: 23
Popularity: 0.77
First Submitted: 2017-05-23 22:29 (UTC)
Last Updated: 2022-01-16 23:38 (UTC)

Latest Comments

steffeno commented on 2022-06-13 11:36 (UTC) (edited on 2022-06-13 12:55 (UTC) by steffeno)

Hey, xorg-xauth is a dependency as required by the author.

You can see xauth being used before starting xorg:

Feel free to argue if I'm wrong.

antoniovazquez commented on 2022-06-11 11:32 (UTC)

Why does this package depend on xorg-xauth?

I have manually edited the PKGBUILD to not include this dep and gladly report that it compiles and flawlessly runs without any issue.

It would be nice to be able to avoid X deps if not being in use. Maybe moving this package to optional deps?

lberrymage commented on 2022-01-15 07:49 (UTC)

I am orphaning this package as I no longer use it or have time to maintain and test it. Apologies for the late response to the build errors - my email notifications from the AUR were being marked as spam, so I didn't see them

4le34n commented on 2021-12-20 04:07 (UTC)

Who does not intend to replace the "make github" line on "git submodule update --init --recursive"

xuv commented on 2020-08-25 18:02 (UTC)

@lberrymage I had done a yay -Sc which I believe clears the whole yay cache. But that did not change anything. Removing the folder, as you suggested it, fixed it. Thx for the help.

lberrymage commented on 2020-08-25 17:00 (UTC)

@xuv Try deleting the ~/.cache/yay/ly-git directory and reinstalling - the entire repository was rebased recently, causing git to not recognize the repositories as the same.

xuv commented on 2020-08-25 16:56 (UTC)

I'm getting ERROR: ~/.cache/yay/ly-git/ly is not a clone of https://github.com/nullgemm/ly.git and does not update when running with yay.

mser commented on 2020-07-27 22:17 (UTC)

@lberrymage Thanks for the quick fix!

lberrymage commented on 2020-07-27 20:24 (UTC)

@imtbl We should be good to go now thanks to nullgemm's quick action!

I'll update the git URL even though it redirects to the right place.

lberrymage commented on 2020-07-27 20:10 (UTC)

Yes I noticed this too, but it appears that more than the URL was changed; it looks like every commit commited as cygolm was rebased to be commited as nullgemm. I've created a GitHub issue and we're working the problem out right now.

mser commented on 2020-07-27 18:59 (UTC) (edited on 2020-07-27 19:07 (UTC) by mser)

Updating fails for me with the following error:

==> Starting pkgver()...
fatal: No tags can describe 'f6658f83a9bb935edc553a02fc005b98028cab20'.
Try --always, or create some tags.
==> ERROR: pkgver is not allowed to be empty.
==> ERROR: pkgver() generated an invalid version

Edit: I just saw the upstream URL changed: https://github.com/nullgemm/ly/commit/f6658f83a9bb935edc553a02fc005b98028cab20 Maybe that's the cause?

abouvier commented on 2020-07-20 13:51 (UTC) (edited on 2020-07-20 13:51 (UTC) by abouvier)

If tag contains a prefix, like v or project name then it should be cut off

See: https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver()_function

lberrymage commented on 2020-03-16 21:53 (UTC)

@qubidt @loserMcloser

Done

qubidt commented on 2020-03-16 15:57 (UTC)

@lberrymage can you address the request made by @loserMcloser (to add /etc/ly/config.ini to backup)?

diabonas commented on 2020-03-05 20:53 (UTC)

@4le34n This is a problem with the upstream Makefile, it should really be fixed upstream by submitting a pull request instead of modifying the PKGBUILD.

loserMcloser commented on 2020-02-01 20:40 (UTC)

Please add

backup=('etc/ly/config.ini')

to the PKGBUILD.

4le34n commented on 2019-11-12 04:33 (UTC)

Invalid file permissions /etc/ly/config.ini /etc/ly/lang/*.ini

Add to PKGBUILD:

chmod 644 ${pkgdir}/etc/ly/config.ini

chmod 644 ${pkgdir}/etc/ly/lang/*.ini

tkrizek commented on 2019-06-04 16:04 (UTC)

There's no need to include inih.git and termbox-next.git in sources, since they're git submodules of ly.git

LeonisCuriosity commented on 2019-03-10 14:34 (UTC)

Pour les compatriotes !

nullgemm commented on 2018-09-26 13:53 (UTC)

@dreieck: done, thank you for reporting @lll2yu: I'm figuring out how things work, sorry for inconvenience :p

lll2yu commented on 2018-09-24 03:21 (UTC) (edited on 2018-09-24 06:38 (UTC) by lll2yu)

EDIT:- Fixed with new update

fails to build 

==> Starting prepare()...
==> Starting pkgver()...
==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: 0.2-1-gce56ce4

dreieck commented on 2018-09-03 12:10 (UTC)

Should conflict with the package python-ly, as both install the file /usr/bin/ly.

nullgemm commented on 2017-11-07 20:42 (UTC)

I just tried to make a full update and it fixed the issue. As it included a new version of the ncurses package, I assume something was broken on their side and they fixed it. Sorry for the inconvenience and late answer :(

160R commented on 2017-11-05 00:39 (UTC)

It compiles after installing "ncurses-full"

runical commented on 2017-11-04 20:44 (UTC)

I can confirm that this error detuur mentioned also occurs for me (in a clean chroot). Is there anything that can be done to solve this?

detuur commented on 2017-10-25 23:28 (UTC)

:: Building ly-git package(s)... ==> Making package: ly-git 0.0.1-1 (Thu Oct 26 01:24:16 CEST 2017) [...] ==> Starting build()... mkdir -p ./build cc -std=c99 -pedantic -Wall -I src -L/usr/lib/security -o build/ly src/main.c src/utils.c src/login.c src/ncui.c src/desktop.c -lform -lncurses -lpam -lpam_misc -lX11 -l:pam_loginuid.so /usr/bin/ld: /tmp/ccxDBvqM.o: undefined reference to symbol 'newscr' /usr/lib/libtinfo.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make: *** [makefile:3: build/ly] Error 1 Have any idea what could be causing this?