linux/poky.git/meta/recipes-extended/sysstat, branch uninative-2.6

systat: systemd never enables the service

2019-06-19T11:46:43+00:00

Even if SYSTEMD_AUTO_ENABLE is set to "enable", the service is never activated by systemd. The cause is the postinst function in the recipe: pkg_postinst_${PN} () { if [ -n "$D" ]; then exit 0 fi if [ -e /etc/init.d/populate-volatile.sh ]; then /etc/init.d/populate-volatile.sh update fi } This generates with activated systemd the following postinst script: set -e if [ -n "$D" ]; then exit 0 fi if [ -e /etc/init.d/populate-volatile.sh ]; then /etc/init.d/populate-volatile.sh update fi OPTS="" if [ -n "$D" ]; then OPTS="--root=$D" fi if type systemctl >/dev/null 2>/dev/null; then if [ -z "$D" ]; then systemctl daemon-reload fi systemctl $OPTS enable sysstat.service if [ -z "$D" -a "enable" = "enable" ]; then systemctl --no-block restart sysstat.service fi fi Due to the exit statement, systemctl is never called and the service is never enabled in rootfs. Invert the logic for the check to let run the rest of postinst script. (From OE-Core rev: 24ccfd80edb74871d0d69ddbe83c358f04ac0844) Signed-off-by: Stefano Babic Signed-off-by: Richard Purdie

sysstat: add UPSTREAM_VERSION_UNKNOWN

2019-06-01T10:27:07+00:00

We are taking a development version from an odd-even versioned project, so upstream version check reports that the latest version is less than the one the recipe is using. UPSTREAM_VERSION_UNKNOWN avoids a version check failure until there is a new stable series. (From OE-Core rev: 0e7a4a14dc63588cfd5f6adff527f7613bb69c55) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

sysstat: Add PACKAGECONFIG[cron] for '--enable-install-cron' option

2019-05-16T15:35:12+00:00

If 'cron' is added into PACKAGECONFIG, for sysvinit, the related cron scripts will be installed; for systemd, the services of data collect and summary will be installed. (From OE-Core rev: 3ee977629331843cc811b6571d13fa02f5593a10) Signed-off-by: Haiqing Bai Signed-off-by: Richard Purdie

sysstat: inherit upstream-version-is-even

2019-05-09T15:31:55+00:00

Currently a development version is being used. (From OE-Core rev: ddc2baa8b7ef6ecd6ed450bb8b3ed986b6797d9f) Signed-off-by: Adrian Bunk Signed-off-by: Richard Purdie

sysstat: upgrade to 12.1.3

2019-02-20T11:37:37+00:00

(From OE-Core rev: ca407f2409328740dac7af34e0e6a0ede578cb2f) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

sysstat: upgrade to 12.1.1

2018-12-05T22:30:19+00:00

(From OE-Core rev: af912ac17f406ff11319eb33bc0d3910bcea39ef) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

sysstat: upgrade 11.7.3 -> 11.7.4

2018-07-24T10:52:26+00:00

(From OE-Core rev: 8a50ab1ebf1b9b274521c194662d9144f99304fc) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

sysstat: upgrade to 11.7.3

2018-05-15T09:56:50+00:00

(From OE-Core rev: cbfabe9aeb2d1876a41119df126cdac3034762ab) Signed-off-by: Chen Qi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

sysstat: refresh patches

2018-03-11T13:27:01+00:00

The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 53f2bbba35c63afa14c5fcb33b83b0ee061840ca) Signed-off-by: Ross Burton Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

sysstat: refresh patches

2018-03-07T14:34:51+00:00

The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 4a0c9bb514ff3d6966f1da480cd48c076403f58d) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie