v3.7.1

Change:
Reintroduce the ability to override the "omitting stop release prevention" for upgrades in "SSU mode" (to satisfy feature request #42).

v3.7.0

Change:
Introduce --verify option, see: sfos-upgrade --help

v3.6.3

Changes:

• Refined technique to extract battery information even further
• Switch embedded icon from 128 px² to 256 px² in order to accommodate modern hi-res displays
  ... and embed a GIF (v89a) icon in RPMs, but never in XPM (v3) file format!
  Background: XPM is absolutely antiquated (it translates a picture in characters!), results in large file sizes (no built-in compression) and of lower image quality than GIF (though both are "8 bit colour palette plus transparency, with 24 bit colours" formats). GIF89a is technically much more modern than XPMv3 and rpmbuild only accepts GIF and XPM icons!

v3.6.2

Changes:

• Added icon in various sizes
• Refined sed statement to extract battery information a bit further
• Streamlined spec file a bit
• Added icon to spec file and consequently to the generated rpm file

v3.6.1

Changes:

• Enhance battery information parsing a bit
• Fully switch to three field semantic versioning
• Omitting any use of %{release} in the spec file
• Make "Release:" field merely indicate the estimated software quality
• Release tags strictly adhere to the format %{version} (being x.y.z with three positive, natural numbers) from now on
• Archive file names (of TAR balls and ZIP archives) strictly adhere to the format %{name}-%{version} from now on

v3.6.0

Update sfos-upgrade.spec

v3.5-8

Change:
Workaround for Gemini's kernel broken battery information, which contains spaces: Use eval and sed instead of source / ".".
For details, see issue #39. Thanks to @nephros for reporting and analysis.

v3.5-6

Changes:

• Add SailfishOS 3.2.0.12 as a new stop release
• Documentation enhancements
• Omitting set -f (aka -o noglob), because bash 3.2.57(1)-release does not perform a set +f (or +o noglob; plus setopt is not built-in) correctly, which would be needed later!
  This fixes failing to find the battery information uevent sysfs file since commit b3288b5 with affected bash versions. This change, which broke retrieving the battery information at all, was released per v3.5-1, hence retracting all releases since then.
  Thanks to @nephros for reporting per issue #39.

v3.5-7

Merge pull request #40 from Olf0/Gemini-battery

Workaround: Gemini battery info

v3.5-4

Changes:

• Fixed reading battery information for unusual paths (e.g. on Aigo Tablets) again, which was inadvertently broken meanwhile.
• Now post_sfos-upgrade and tidy_log-dupes both exit with proper exit codes (as usual, "0" is for "O.K.", any higher number indicates a failure).
• Enhanced fault behaviour and error handling in tidy_log-dupes to an extent, that it was mostly rewritten.
• Rectified a mishap when applying the (seemingly trivial) fix "Fixed a longstanding, formal oversight in the scripts proper." per v3.3 to the sfos-upgrade script, breaking it. Hence retracting v3.3-1 to v3.5-2.