Package Details: ly-git 1.4.0.r6.g864f5f2-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://codeberg.org/fairyglade/ly.git
Licenses: WTFPL
Conflicts: ly
Provides: ly
Submitter: nullgemm
Maintainer: steffeno
Last Packager: steffeno
Votes: 28
Popularity: 0.82
First Submitted: 2017-05-23 22:29 (UTC)
Last Updated: 2026-05-02 22:19 (UTC)

Dependencies (6)

Required by (2)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

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.

<deleted-account> 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

nicki 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 :(

« First ‹ Previous 1 2 3 4 5 6 Next › Last »