Package Details: lyvi-git v2.0.0.23.g6777afe.g6777afe-1

Git Clone URL: (read-only, click to copy)
Package Base: lyvi-git
Description: Command-line lyrics, guitar tabs, and artist information viewer
Upstream URL:
Licenses: WTFPLv2
Submitter: stormdragon2976
Maintainer: Poroing
Last Packager: Poroing
Votes: 5
Popularity: 0.052835
First Submitted: 2015-09-03 14:30
Last Updated: 2020-11-25 14:57

Dependencies (8)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

Poroing commented on 2020-12-06 14:13

If you are encountering issues with lyvi-git due to a importlib.metadata.PackageNotFoundError, this is due to the recent update of Python on the main repository from 3.8 to 3.9. lyvi was stored in the directory the directory for python3.8, but, now, Python search ins the directory for python3.9. To solve this issue, juste rebuild and install this package. Do not forget to do the same for python-glyr-git.

nobicycle commented on 2020-11-26 06:37

Merci beaucoup Poroing

Great to see lyvi still alive at, which I tested successfully.

Best wishes

Poroing commented on 2020-11-25 15:05

I adopted this package.

@nobicycle Since the installation error was coming from the script using a function interns to pip, I decided that the best course of action was to fix the upstream repository rather than make some patch before the installation. As the original owner doesn't seem to be active anymore (old issue and pull requests are not answered) I decided to fork the repository and make the change myself. The PKGBUILD is now fetching the source code from my fork.

I also changed the makedepends array. Since does not depend on pip anymore due to my fix, I removed it from the makedepends array. I also added python-setuptools to the makedepends array as it should have been there since the beginning.

nobicycle commented on 2020-09-15 07:16

Is anyone willing and qualified to take this package now stormdragon2976 has disowned it? Being a little rusty on PKGBUILD I would not be best placed, but will take it if no one better steps forward.

nobicycle commented on 2020-09-05 02:59

In change req to requirement:

OLD: install_requires=[str(ir.req) for ir in install_reqs],

NEW: install_requires=[str(ir.requirement) for ir in install_reqs],

Then it compiled.

I was lead to this by:

stormdragon2976 commented on 2020-09-04 14:30

@nobicycle: I have checked the requirements file, and we have all the dependancies it lists. It has failed to install here as well though. I guess they have forgotten to add something to the docs.

Do you know what would provide str(ir.req)? I did a quick search but didn't find anything useful.

nobicycle commented on 2020-09-04 13:16


$ makepkg ==> Making package: lyvi-git v2.0.0.23.g6777afe.g6777afe-1 (Fri 04 Sep 2020 21:16:46 WITA) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Updating lyvi git repo... Fetching origin ==> Validating source files with md5sums... lyvi ... Skipped ==> Extracting sources... -> Creating working copy of lyvi git repo... Cloning into 'lyvi'... done. ==> Starting pkgver()... ==> Removing existing $pkgdir/ directory... ==> Entering fakeroot environment... ==> Starting package()... Traceback (most recent call last): File "", line 28, in <module> install_requires=[str(ir.req) for ir in install_reqs], File "", line 28, in <listcomp> install_requires=[str(ir.req) for ir in install_reqs], AttributeError: 'ParsedRequirement' object has no attribute 'req' ==> ERROR: A failure occurred in package().

stormdragon2976 commented on 2018-08-23 10:28

@sicariusnoctis: Thanks, added to the PKGBUILD.

yodaembedding commented on 2018-08-23 05:07

If you receive the following error:

Traceback (most recent call last):
  File "", line 3, in <module>
    from pip.req import parse_requirements
ModuleNotFoundError: No module named 'pip.req'

Paste the following line into the PKGBUILD above the call to python install --root=$pkgdir:

sed -i 's/from pip.req/from pip._internal.req/'

More info:

vredesbyrd commented on 2018-08-08 01:03

This now requires a change to successfully build against python3.7. It should be fixed upstream to be compatible with different python versions, but in the meantime if anyone has trouble here is what I did.

In, line 3, change 'pip.req' to 'pip._internal.req'

Than build the package with the --no-extract option, 'makepkg -e'. This could also be accomplished with a patch I suppose, but I think I will report this upstream so this workaround is not required.