Search Criteria
Package Details: lektor 3.3.11-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/lektor.git (read-only, click to copy) |
---|---|
Package Base: | lektor |
Description: | A static content management system. |
Upstream URL: | https://www.getlektor.com |
Keywords: | cms python static website |
Licenses: | BSD-3-Clause |
Submitter: | migerh |
Maintainer: | Eothred |
Last Packager: | Eothred |
Votes: | 7 |
Popularity: | 0.000000 |
First Submitted: | 2016-02-07 19:42 (UTC) |
Last Updated: | 2024-05-06 11:16 (UTC) |
Dependencies (19)
- python (python37AUR, python311AUR, python310AUR)
- python-babel
- python-click
- python-exifreadAUR
- python-filetypeAUR
- python-flask (python-flask-gitAUR)
- python-inifileAUR
- python-mistune1AUR
- python-ndg-httpsclient
- python-pip
- python-pyasn1
- python-requests
- python-setuptools
- python-slugify
- python-watchdog (python-watchdog-gitAUR)
- python-build (make)
- python-installer (python-installer-gitAUR) (make)
- python-setuptools-scm (make)
- python-wheel (make)
Latest Comments
« First ‹ Previous 1 2
thrimbor commented on 2020-11-27 04:38 (UTC) (edited on 2020-11-27 04:47 (UTC) by thrimbor)
The new 3.2.0 version fails to run: pkg_resources.DistributionNotFound: The 'Werkzeug<1' distribution was not found and is required by Lektor
The version of python-werkzeug in Arch is 1.0.1-2, which seemingly is too new.
Additionally, python-slugify and python-filetype are missing as dependencies.
Eothred commented on 2020-01-20 06:30 (UTC) (edited on 2020-01-20 06:40 (UTC) by Eothred)
Removed that former recommendation to install with pip2, as I just discovered lektor is fully compatible with python3. So it is now updated to use the default python installation instead. Worked for me, let me know if anyone has issues.
dkaparis commented on 2020-01-19 13:36 (UTC)
Current release 3.1.3-2 errors out complaining it can not find EXIFRead, even though
python-exifread
is installed:diabonas commented on 2020-01-07 16:34 (UTC)
Please update the dependency name from
exifread
topython-exifread
, the former doesn't exist any more.migerh commented on 2019-03-31 18:12 (UTC)
Thank you for the reminder. I sent mails to mrxx, pekman and shadowkyogre. The first one answered but while I was waiting on an answer from pekan I completely forgot about this. Unfortunately, I don't have the time right now to fix this. So I will disown this package. Anyone who wants to get the packages ported to python3, here is my suggestion from last year I sent to mrxx, pekman and shadowkyogre. It might be outdated, especially with regards to dependencies.
Hi pekman, Hi mrxx,
I'm currently maintaining the lektor [1] package in the Arch User Repository. Lektor depends on the exifread python library. There are currently two packages related to that library that you maintain: exifread [2]: Provides the library as well as the EXIF.py application but only for python2 (although depends lists python3) exif-py [3]: Only wants to provide the application and thus depends on exifread and has to rename the application from EXIF.py to exif-py. Unfortunately, it doesn't work. There used to be two other packages which got deleted, the reasons are unknown to me: python-exifread / python2-exifread: Both provided the application and the library. If I wanted to use exifread with python2 I could install the exifread package. But if I wanted to use it with python3 right now I can't. Instead of just resurrecting the python(2)-exifread packages I wanted to discuss with you how we can clean up this situation.
Python library modules are supposed to be prefixed with python- for python3 libraries and python2- for python2 libraries. Python applications should not have any prefix. Since exifread is both, a library and an application I would suggest to split it into three packages (which could be provided by a single PKGBUILD): python2-exifread, contains only the library part, packaged for python2 python-exifread, contains only the library part, packaged for python3 exifread, depends on python-exifread and only provides EXIF.py in /usr/bin and the license file. exif-py should be deleted. Open issue here: The metamorphose2 package probably needs to be fixed to then depend on python2-exifread instead of exif-py (maintainer is shadowkyogre, see CC)
[1] https://aur.archlinux.org/packages/lektor/ [2] https://aur.archlinux.org/packages/exifread/ [3] https://aur.archlinux.org/packages/exif-py/
mrxx agrees with me. neither pekman nor shadowkyogre ever replied.
cucullus commented on 2019-03-27 13:04 (UTC)
I beleive, that maintainer of exifread is inactive since 2015. You can request to disown exifread on mailinglist and fix it (s/python2/python/).
migerh commented on 2018-05-06 17:10 (UTC) (edited on 2018-05-06 17:10 (UTC) by migerh)
Thanks for the flag! Somehow I missed the release.
You are right, it is compatible with python3 and runs flawlessly but unfortunately the packaging situation around exifread is a little bit of a mess. There are currently two packages:
• exifread, which provides the library and application for python2 (while listing python3 as a dependency)
• exif-py, which depends on exifread and only provides the application, but renamed it to exif-py (instead of EXIF.py), because exifread already provides that…
There also used to be to packages python2-exifread and python-exifread which both provided the library and application as well but were removed for some reason. You can still check out the PKGBUILDS by cloning the python-exifread repo.
Let me first try to clean up this mess, then I'll switch this package to python3.
lowercase commented on 2018-05-06 11:24 (UTC)
As lektor is compatible with Python 3 it would make sense to default to this release.
« First ‹ Previous 1 2