Overview
Request 1114947 superseded
- drop reportlab-missing-includes.patch
- add importlib.patch to fix support for python3.12
- update to 4.0.5:
* add in test for alpha composite colour
* Added an SvgPath class; as used in github.com/deeplook/svglib
* Added a simple log axis ticklabeller class
* Allow for strokeWidth in LineSwatch
* update extension alias'
* allow BalancedColumns to work in a container flowable (ie with no frame)
* allow custom styles for inrowsplitStaart & inrowsplitend
* setup.py test --failfast works
* allow running all tests without renderPM support
* AR made some changes to allow running without renderPM support
* AR merged accessibility branch and released 4.0.0
* initial support for rml ul ol dl tagging
* added support for an ol/ul/dl caption paragraph
* implement a safer toColor with rl_config.toColorCanUse option and rl_extended_literal_eval
* added _ExpandedCellTupleEx for more tagging support
- Created by mimi_vx
- In state superseded
- Superseded by 1115544
Request History
mimi_vx created request
- drop reportlab-missing-includes.patch
- add importlib.patch to fix support for python3.12
- update to 4.0.5:
* add in test for alpha composite colour
* Added an SvgPath class; as used in github.com/deeplook/svglib
* Added a simple log axis ticklabeller class
* Allow for strokeWidth in LineSwatch
* update extension alias'
* allow BalancedColumns to work in a container flowable (ie with no frame)
* allow custom styles for inrowsplitStaart & inrowsplitend
* setup.py test --failfast works
* allow running all tests without renderPM support
* AR made some changes to allow running without renderPM support
* AR merged accessibility branch and released 4.0.0
* initial support for rml ul ol dl tagging
* added support for an ol/ul/dl caption paragraph
* implement a safer toColor with rl_config.toColorCanUse option and rl_extended_literal_eval
* added _ExpandedCellTupleEx for more tagging support
superseded by 1115544
could you please document where the patch came from in
*.spec
or*.changes
? A single word "upstream" helps the people after you to outright delete the patch when updating.Are there any guidelines, btw? I personally really like the lines
# PATCH-FIX-WHATEVER ...
over the patch, but the format of the lines is not clear (I've seen at least 3 ways of# PATCH-FIX-UPSTREAM
) and some people don't do them.https://en.opensuse.org/openSUSE:Packaging_Patches_guidelines
cool, so it looks like there are two standards :P anyway, this patch complies to none of them