FS#46999 - [sigil] changes for the update to 0.9.0

Attached to Project: Community Packages
Opened by Eli Schwartz (eschwartz) - Sunday, 08 November 2015, 01:20 GMT
Last edited by Balló György (City-busz) - Wednesday, 21 June 2017, 10:12 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To Giovanni Scafora (giovanni)
Anatol Pomozov (anatolik)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

A while ago I marked sigil out of date for the releases 0.8.90{0,1} which were part of the 0.9.0. pre-release series.

Sigil never got updated, I don't know if it was because they weren't considered proper releases or because the maintainer didn't have time, but I've been maintaining sigil-git in the AUR now and I have a working patch to update sigil to 0.9.0 which was just released.
Release announcement: http://www.mobileread.com/forums/showthread.php?t=267232


Note: This also uses the CMakeLists rule to unbundle the bundled copies of PCRE, hunspell, hunspell-dicts, minizip, and zlib

:)
   sigil.diff (6 KiB)
This task depends upon

Closed by  Balló György (City-busz)
Wednesday, 21 June 2017, 10:12 GMT
Reason for closing:  Implemented
Additional comments about closing:  sigil 0.9.8 is already in the repository.
Comment by Doug Newgard (Scimmia) - Sunday, 08 November 2015, 02:37 GMT
Of course the stable package in the repo didn't get updated to pre-releases, why would it?
Comment by Eli Schwartz (eschwartz) - Sunday, 08 November 2015, 02:46 GMT
Because I've seen it happen before, if the release in question is in fact a stable release. Maybe it depends on the packager's whim. :)
And Sigil 0.8.90{0,1} were real releases, even if they were aimed at getting 0.9.0 out.

And if the maintainer didn't think it should be updated for 0.8.90{0,1} presumably he would mark it as NOT out-of-date -- I wouldn't presume to re-flag it.

...

In any event, 0.9.0 is not in any way shape or form a pre-release -- and it is 0.9.0 that I am discussing here.
So you can probably put the Task Type back to the way it was.
Comment by Doug Newgard (Scimmia) - Sunday, 08 November 2015, 02:52 GMT
Packages are bumped to betas/RCs if there's a need, not just because upstream releases one.

Make no mistake, that's what 0.8.9x release are, betas, not stable releases.

Edit, and no, I'm not going to change it back to a "Bug Report"; as it says at the top of every page, out of date packages are not bugs.
Comment by Eli Schwartz (eschwartz) - Sunday, 08 November 2015, 03:02 GMT
This is not an out-of-date package report, this is a diff to update the new version since it requires more than a pkgver bump.

Sigil now requires python-lxml for example.
This is because Flightcrew was replaced with a python-based sanitycheck validator which uses lxml.

Also included are reworked dependencies (I admit mostly to unbundle the 3rdparty stuff which is pre-0.8.7) as well as optional dependencies on various python libs that may be expected by plugins, since upstream recommends them and bundles them on OSX and Windows.
Comment by Doug Newgard (Scimmia) - Sunday, 08 November 2015, 03:07 GMT
Right, which is why I didn't close this, and why it's not a "Bug Report"

Loading...