paperwork is stuck at 0.3.2 release. It is just passed to 1.0.2 Thanks.
CC: (none) => geiger.david68210Assignee: bugsquad => dglent
Summary: PLease update paperwork before release => Please update paperwork before releaseSource RPM: (none) => paperwork
Talking about being "stuck" at 0.3.2 release is not really fair: https://github.com/jflesch/paperwork/releases - 0.3.2 was released on April 2016 - 1.0, the _immediate_ next release, was released on 9 Nov 2016 (5 days ago) - 1.0.2 was released 18 hours ago, and 1.0.1 before that, so it clearly shows that 1.0 was not as stable as it should be if it required 2 bugfix releases in 5 days. So yeah, updating to 1.0.2 would be cool, but where's the fire?
Severity: normal => enhancementPriority: Normal => Low
The current release of paperwork in github is the 1.1.2 - it has switched to python3 - It uses the python-pyinsane2 which replaces the current python-pyinsane rpm - It uses a new library python3-pypillowfight - It uses an extra package paperwork-backend Do you think that we can update this for mga6 ? Tests needed For mga 5 : http://www.mageia-gr.org/rpm/5/noarch/paperwork-1.1.2-1mgr5.noarch.rpm http://www.mageia-gr.org/rpm/5/noarch/paperwork-backend-1.1.2-1mgr5.noarch.rpm http://www.mageia-gr.org/rpm/5/noarch/python3-enchant-1.6.6-1mgr5.noarch.rpm http://www.mageia-gr.org/rpm/5/noarch/python3-pycountry-1.18-1mgr5.noarch.rpm http://www.mageia-gr.org/rpm/5/noarch/python3-pyinsane2-2.0.9-1mgr5.noarch.rpm http://www.mageia-gr.org/rpm/5/noarch/python3-pyocr-0.4.7-1mgr5.noarch.rpm http://www.mageia-gr.org/rpm/5/x86_64/python3-pypillowfight-0.2.1-1mgr5.x86_64.rpm
It seems that this bug got something forgotten. We are now at paperwork-1.3.1 in MGA8. Closing OLD.
Resolution: (none) => OLDStatus: NEW => RESOLVED