Arch Linux User Repository

Thanks for orphaning it @TurtleRuss, I adopted it and added @bulletmark as a co-maintainer. :)

Sorry, my system is broken these days and I'm sorry for getting you guys back late. I will mark this package orphan now and a new maintainer is needed.

I'm moving calibre-web to python-pypdf, but since there is no conflicts, you have to pacman -Rdd this one to replace it w/ the right one. I actually emailed him asking if he needed help maintaining, it seems like this could install into a different folder/package as well.

@fryfrog, that won't fix the issue described here. Given the maintainer is not responding to comments I have put in an orphan request.

Hey @TurtleRuss, could you add conflicts=('python-pypdf')?

That should work. But still doesn't really the answer the question, why this PKGBUILD was updated and brought alongside python-pypdf. If there is a python program, which needs pypdf >3.0.0 to work it needs to depend on python-pypdf and not this. If it is somehow really checking for pypdf2 and still requires >3.0.0 to work, this should be brought up upstream, as there may be something going wrong.

Try this for the PKGBUILD:

# Maintainer: Turtle Russ <tttturtleruss@gmail.com>
# Contributor: mark.blakeney at bullet-systems dot net
# Contributor: Yuanji <self@gimo.me>
# Contributor: Antonio Rojas <arojas@archlinux.org>
# Contributor: Francois Boulogne <fboulogne at april dot org>

_name=PyPDF2
pkgname=python-pypdf2
pkgver=2.12.1
pkgrel=4
epoch=2
pkgdesc='Python library for manipulating pages of PDF files (legacy v2)'
arch=(any)
url="https://github.com/py-pdf/$_name"
license=(BSD)
depends=(python python-pillow python-cryptography python-pycryptodome python-typing_extensions)
makedepends=(python-setuptools python-build python-installer python-wheel python-flit-core)
source=($_name-$pkgver.tar.gz::"https://files.pythonhosted.org/packages/77/d6/afcbdb452c335bccf22ec8ac5ac27b03222f9be8b96043bcce87ba1ce32a/PyPDF2-2.12.1.tar.gz")
sha256sums=('e03ef18abcc75da741a0acc1a7749253496887be38cd9887bcce1cee393da45e')

build() {
  cd $_name-$pkgver
  python -m build --wheel --no-isolation
}

package(){
  cd $_name-$pkgver
  python -m installer --destdir="$pkgdir" dist/*.whl
  install -D -m644 LICENSE "$pkgdir"/usr/share/licenses/$pkgname/LICENSE
}

@TurtleRuss, yes TriainError is correct. Please restore this package back to 2.12.1. You will have to bump the epoch to 2. Perhaps also change the url in the PKGBUILD to https://pypi.org/project/PyPDF2/ which is more appropriate now. The current 4.2.0 version is available in the standard packages at python-pypdf which you have inadvertently duplicated.

Isn't this package now broken for other programs that requires pypdf2 with the bump to the latest release? It was deliberatly left at version 2.x, because afterwards upstream unified the various pypdf project attempts and 3.x and forward weren't compatible with the old API?
https://github.com/py-pdf/pypdf/pull/1489
Of note is that 3.0.0 apparantly already broke things and therefore this was left at the latest 2.x release.
Didn't test with stapler-git yet, but for that reason also avoiding to build a new package pypdf2 package because I am still irritated why this legacy got updated to the latest version of pypdf (which is not pypdf2).

Yeah this package as been completely borked with the recent change; thank you @alan1world for the fix :)