8f6e1fdae7
clean up: remove .gz and .ipk files in /var/cache/opkg
2024-10-08 15:03:43 +02:00
50357997c2
Do not use cleanPath() on an url-path
2024-07-17 14:04:53 +02:00
fa7d1ba879
Allow empty lines in opkg_commands.
2024-06-28 12:50:30 +02:00
1dc7578645
Clean repository path from multiple slashes.
2024-06-28 12:49:53 +02:00
6683b925aa
Fix: remove hard-coded path to gitea repository (mimbach).
2024-06-28 10:03:10 +02:00
55c82eb509
Fix: send output to CONSOLE if directories are actually not equal.
2024-05-17 12:26:36 +02:00
f60cd9e4ef
Again: improved ISMAS messages.
2024-05-17 12:26:03 +02:00
a9fb7a3630
Improve messages sent to ISMAS during update process.
2024-05-17 12:25:26 +02:00
db82f2af0d
Fix: do not send a message to ISMAS about a check of the ISMAS
...
trigger (WAIT-button). For an automatic update this meant that
two messages have been visible in ISMAS which confused many users.
2024-05-17 12:22:38 +02:00
d191020caa
Configure new update-step values.
...
INSERT_ELEMENT(UPDATE_STEP::DOWNLOAD_CASH_FILE),
INSERT_ELEMENT(UPDATE_STEP::DOWNLOAD_CASH_FILE_FAILURE),
INSERT_ELEMENT(UPDATE_STEP::DOWNLOAD_CASH_FILE_SUCCESS),
INSERT_ELEMENT(UPDATE_STEP::DOWNLOAD_DEVICE_FILE),
INSERT_ELEMENT(UPDATE_STEP::DOWNLOAD_DEVICE_FILE_FAILURE),
INSERT_ELEMENT(UPDATE_STEP::DOWNLOAD_DEVICE_FILE_SUCCESS),
INSERT_ELEMENT(UPDATE_STEP::DOWNLOAD_JSON_FILE),
INSERT_ELEMENT(UPDATE_STEP::DOWNLOAD_JSON_FILE_FAILURE),
INSERT_ELEMENT(UPDATE_STEP::DOWNLOAD_JSON_FILE_SUCCESS),
2024-05-17 08:47:10 +02:00
cafd16a744
Read versions of JSON files installed on PSA (DC!).
...
If version is available, use as blob-value to be visible
in ISMAS.
2024-05-15 14:57:15 +02:00
5876c50a32
Make sure that SEND-LAST-VERSION is executed exactly once.
2024-05-15 14:56:41 +02:00
a3aef7594e
Minor: add comment
2024-05-14 12:52:09 +02:00
05c7d11ef8
Only create m_update-object if it is configured to update hardware (JSONs and DC).
2024-05-03 13:32:39 +02:00
8402fde6b5
Reformat m_versionInfo in case a version is included in the commit-message.
2024-04-29 15:00:52 +02:00
f15cc636c6
FIX: set m_pulledNewBranch = false in case no new branch has to be fetched from remote repository.
2024-04-29 14:59:10 +02:00
adaa12395e
Trigger CHECK_ISMAS_TRIGGER_SUCCESS-message to ISMAS.
2024-04-29 14:58:29 +02:00
20681b0d6c
If we have pull a new remote branch, the behave as if the customer-repo
...
did not exist before: especially download all json-files inside
the new local branch.
2024-04-11 16:20:46 +02:00
763647c145
If customer-repo is already existent (i.e. not cloned),
...
then check for the existence of remote branch (zg/zone<zone-number of psa>).
If it exists remotely, but not locally, then execute 'git pull'
(could also be 'git pull origin zg1/zone<zone-number>').
A follwing 'git checkout zg1/zone<zone-number>' will switch to the
now local branch.
2024-04-11 16:16:34 +02:00
4aad14b181
Added PULL_NEW_BRANCH, PULL_NEW_BRANCH_FAILED, PULL_NEW_BRANCH_SUCCESS and corresponding output messages.
2024-04-11 16:15:49 +02:00
24f2ba7c44
Move rsyncing the customer-repository after filesToUpdate(), as
...
the repository is pulled in filesToUpdate().
2024-04-09 14:56:25 +02:00
175b8fd3a1
If the update-trigger (aka WAIT-button) is empty and we have an automatic
...
update (i.e. time is 0:00 - 4:00 am), then do not inform ISMAS with an U0003
error signal, but send an U0002 (setting the trigger-value to "OK").
2024-03-19 12:41:42 +01:00
753954ecd7
Use <DeviceController/interfaces.h>
2024-03-15 12:07:15 +01:00
a5e0154757
Do not check if etc/psa_tariff and /etc/psa_tariff are equal after the rsync:
...
reason is that this might be not the case if the customer-number has been changed.
2024-03-08 08:44:39 +01:00
074e60d8dc
Merge remote-tracking branch 'UpdatePTUDevCtrl/dc-download'
2024-02-29 14:48:59 +01:00
8eff6e5d10
Move UpdatePTUDevCtrl files into subdir UpdatePTUDevCtrl
2024-02-29 14:41:45 +01:00
