Package Details: ocrodjvu-python3-git 0.14-1

Git Clone URL: https://aur.archlinux.org/ocrodjvu-python3-git.git (read-only, click to copy)
Package Base: ocrodjvu-python3-git
Description: OCR for DjVu (Python 3 port)
Upstream URL: https://github.com/FriedrichFroebel/ocrodjvu
Licenses: GPL-2.0-only
Conflicts: ocrodjvu
Provides: ocrodjvu
Submitter: ianis
Maintainer: ianis
Last Packager: ianis
Votes: 0
Popularity: 0.000000
First Submitted: 2022-11-17 00:37 (UTC)
Last Updated: 2025-01-16 20:54 (UTC)

Dependencies (19)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

ianis commented on 2025-01-16 20:57 (UTC)

I did not know there is a maintained fork. I have now updated the AUR package to point to it. I know it's not a good practice to change the origin, but a broken package is not really better.

Anyhow, does anybody else want to be a maintainer or co-maintainer of the AUR package?

FriedrichFroebel commented on 2025-01-16 20:14 (UTC)

It seems like the package for this unmaintained fork should be replaced by a new package for the corresponding PyPI package: https://pypi.org/project/ocrodjvu/ The repository has been created after the original repository had been archived and thus remained without an explicit reference.

Disclaimer: I am the current maintainer of the PyPI package, as well as the djvulibre-python dependency (you already packaged in the AUR some weeks ago).

MarsSeed commented on 2025-01-12 03:53 (UTC)

@Antiz, I don't see any fix patching here, only a hiding of the fact that upstream code does not work without python-future.

krvkir commented on 2025-01-12 02:43 (UTC) (edited on 2025-01-12 02:48 (UTC) by krvkir)

Seems that without python-future dependency, it just doesn't work:

Traceback (most recent call last):
  File "/usr/bin/djvu2hocr", line 23, in <module>
    from lib.cli import djvu2hocr as cli
  File "/usr/share/ocrodjvu/lib/cli/djvu2hocr.py", line 32, in <module>
    from .. import hocr
  File "/usr/share/ocrodjvu/lib/hocr.py", line 27, in <module>
    from past.builtins import basestring
ModuleNotFoundError: No module named 'past'

Please don't delete. Even if it doesn't work out of the box, at least one can find a clue where to get the utilities needed.

ianis commented on 2025-01-11 23:09 (UTC)

@Antiz Alright.

Antiz commented on 2025-01-11 23:08 (UTC)

@ianis Alright, thanks for the info!

[...] but we can't delete packages just because there haven't been recent commits.

Well sure but, Arch being a bleeding edge / rolling release distro, we kinda expect upstreams to keep up; otherwise related packages eventually just gets harder and harder to maintain with recent dependencies / libraries versions over time (fortunately it wasn't too much effort to make this one build with python 3.13 but you get the point).

Anyway, I'm rejecting the pending deletion request ;)
However, since you stated you have no plans to maintain this package in case it ever fails in the future (which is fair enough), may I ask you to please not just let it die unmaintained by submitting a deletion request yourself, in case it ever happens?
We have enough broken and unmaintained packages in the AUR graveyard already :P

ianis commented on 2025-01-11 22:14 (UTC)

The original project has an unfinished (not unmaintained) migration from Python 2 to Python 3. The fork points to this migration. The package was added during the discussion of an issue on GitHub [1], which is no longer relevant.

I won't care much if it gets deleted, but we can't delete packages just because there haven't been recent commits. Proceed as you see fit.

[1] https://github.com/kcroker/dpsprep/issues/5

Antiz commented on 2025-01-11 22:02 (UTC) (edited on 2025-01-11 22:03 (UTC) by Antiz)

@ianis, do you believe this package is still useful / relevant to keep? The fork this package is pointing to just seems as unmaintained at the original project itself (last commit 4 years ago [1]).

Since this package doesn't seem to have any popularity and you just claimed you don't intend to maintain it on the long run or if anything fails, maybe it should just be deleted instead?
For what it's worth, we have a pending deletion request for it [2].

[1] https://github.com/rmast/ocrodjvu/commits/python3/
[2] https://lists.archlinux.org/archives/list/aur-requests@lists.archlinux.org/thread/SSR7ZMONFXJOSQBIF3PTSZSKNSZZME4C/

ianis commented on 2025-01-11 18:52 (UTC)

I have removed python-future as a dependency. The project seems to be building fine now.

This is an AUR package of a fork of an unmaintained project. I have nothing to do with the fork, nor with the original package. If anything fails, I have no plans to maintain it. If anybody wants ownership over the AUR package, feel free to contact me; it will be much (perhaps several months) faster than requesting ownership via the AUR request system.

dreieck commented on 2025-01-11 16:04 (UTC)

If possible, please remove the dependency on python-furure/ make the package working without python-future:

WARNING: python-future package is not compatible with Python 3.13

The python-future project was created in 2013 to attempt to save Python from the schism of version incompatibility that was threatening to tear apart the language (as Perl 6 contributed to the death of Perl).

That time is now past. Thanks to a huge porting effort across the Python community, Python 3 eventually thrived. Python 2 reached its end of life in 2020 and the python-future package should no longer be necessary. Use it to help with porting legacy code to Python 3 but don’t depend on it for new code.

If you use packages that depend on it, please contact maintainers and/or upstream of these packages and try to work out whether this dependency is really needed.

Regards and thanks for this package!

1 2 Next › Last »