Package Details: python-weasyprint 53.0-2

Git Clone URL: https://aur.archlinux.org/python-weasyprint.git (read-only, click to copy)
Package Base: python-weasyprint
Description: Convert web documents (HTML, CSS, SVG, ...) to PDF
Upstream URL: https://weasyprint.org
Licenses: BSD
Provides: weasyprint=53.0
Submitter: SimonSapin
Maintainer: alerque
Last Packager: alerque
Votes: 14
Popularity: 0.42
First Submitted: 2012-03-01 16:12
Last Updated: 2021-08-07 20:50

Dependencies (20)

Required by (11)

Sources (1)

Latest Comments

1 2 3 Next › Last »

alerque commented on 2021-08-02 13:43

I see that 53.0 is out, and I packaged up the new dependency as python-pydyf, but there is what I can only assume is an upstream bug with the installer that is not generating the /usr/bin/weasyprint script properly. I'm going to hold off on posting the update package here until that is in place, but if you are in a hurry and/or only use this as a library you can check out the new PKGBUILD here.

cinatic commented on 2021-06-09 21:49

i think we talk about two different things, if you plan to modify the build script, let's say the deps, then ideally it should be tested before pushing it. But from my experience the deps or something along the build process rarely changes and then we still can intervene manually in time or rollback. Additionally it would be easy to verify "automatically" if the py build was successfull before bumping the version

alerque commented on 2021-06-09 21:33

@cinatic "they"? If you mean upstream what they are testing is their software, not Arch's packaging of it. The manual testing I suggest needs doing is making sure the package actually builds without error (ideally in a chroot), installs to a system without conflicts and the resulting executable runs. In other words test the packaging process to make sure you don't make mistakes like including the wrong deps, installing to the wrong paths, typos, forgetting to update the .SRCINFO, etc.

cinatic commented on 2021-06-09 21:20

thanks for the update and also the remarks about to automate this package build. In general i agree with the observation you described, but for a python module, and in particular weasyprint i would rather trust the testing they are doing than a "manual testing"

alerque commented on 2021-06-09 21:02

@nka It does not require pip to install! You read the error message a bit too fast, what it actually needed was something else and it tried to install that something else with pip when it didn't find it. Adding the correct python dependencies (as I just did while overhauling other aspects of this build) fixed that so pip is not needed.

alerque commented on 2021-06-09 21:00

@cinatic In most cases I've ever seen automated package generation creates more problems that it fixes. I suggest you reconsider. That being said updates don't have to be a chore, lots of tooling exists to make that easier: aur-out-of-date and aurpublish are a couple I use, plus a script to make the sequence of bumping, building, signing, and uploading easier (not well shown in that script is that my git show always waits for input, so it gives me a place to install and check the package manually before actually uploading). Finding the latest upstream version would be easy to add, but don't forget to actually test builds rather than blindly posting a bump! Not doing so is a good way to get you blocked from the AUR.

I overhauled this build with Arch's Python package guidelines in mind, you can see the commit message for some highlights. The biggest upshot is that this now builds properly in a chroot.

cinatic commented on 2021-06-09 18:29

@caleb

sorry for the inconvenience i have the automated package generation task on my stack, and not only for the reason to get rid of annoying flag messages :p

alerque commented on 2021-06-09 11:18

Just a friendly poke to maybe review how you are handling OOD flags. This was flagged for months without an update, then got updated within a few minutes of my filing an orphan request. Maybe you need to enable notifications? Or filter the OOD flag emails differently? Just saying...

nka commented on 2021-06-07 08:48

It requires python-pip to be installed, otherwise if not present installation fails. It should be added in makdepends.

anselmolsm commented on 2021-03-05 19:25

Any plans to have this updated to 52? Thanks.