summaryrefslogtreecommitdiffstats
path: root/src/usr/local/sbin/pfSense-upgrade
Commit message (Collapse)AuthorAgeFilesLines
* Move to Apache License 2.0Renato Botelho2016-07-151-41/+9
|
* Review license / copyright on all files (1st round)Renato Botelho2016-07-141-2/+6
|
* Ignore cp result for cases when files are the same. Ticket #6557Renato Botelho2016-07-141-1/+3
|
* Make sure resolv.conf is present during nanobsd upgrade. Fixes #6557Renato Botelho2016-07-061-0/+3
|
* Unlock kernel package to make dry-run output more consistentRenato Botelho2016-05-051-0/+2
|
* Reboot after upgrade when meta package version changedRenato Botelho2016-05-021-3/+10
|
* Reduce values of FETCH_TIMEOUT and FETCH_RETRY to help ticket #6177Renato Botelho2016-04-271-0/+2
|
* Setup HTTP_PROXY environment variable for pkg when it's called from the GUI ↵jim-p2016-04-191-0/+10
| | | | and also for pfSense-upgrade
* Silence /etc/rc.notify_message garbage outputRenato Botelho2016-04-061-2/+3
| | | | (cherry picked from commit eb3491d99e939ab21d84122ededf9e7e9462ed71)
* Fix code used to read config repo pathRenato Botelho2016-04-061-2/+1
| | | | (cherry picked from commit e429ac7134ac2080af9117c11e2f294d4dd8c5d0)
* Do all steps to replace repo package and make sure symlink is in placeRenato Botelho2016-04-061-22/+29
| | | | (cherry picked from commit 5caee0ba0f8782ea7bf1df54ad0848da1d5084d2)
* Force update after reinstall repo pkgRenato Botelho2016-04-061-0/+1
| | | | (cherry picked from commit 3e7c1ea74a8c0600c785e9588349afd927719d23)
* Simplify logicRenato Botelho2016-04-061-6/+5
|
* Make sure directory existsRenato Botelho2016-04-061-0/+1
| | | | (cherry picked from commit cc1b7ddd0ba2d7eee6ee7ec1cae83efda91427d0)
* Make sure source file existsRenato Botelho2016-04-051-3/+6
|
* Add a workaround on pfSense-upgrade to make sure repo package is replaced by ↵Renato Botelho2016-04-051-0/+7
| | | | | | correct one (cherry picked from commit a491ec98d8ffc5663cca84df402c2d6274a78a07)
* Rework the way repo packages workRenato Botelho2016-04-051-5/+21
| | | | | | | | - Distribute only a single pfSense-repo package containing all templates - Create a symlink pointing to selected repo - Do not limit it only to pfSense-repo and pfSense-repo-devel (cherry picked from commit a90f1c9b12c4d31ea845fa04188e599ba28dbaf1)
* Do not return -1, sh doesn't like itRenato Botelho2016-04-051-1/+1
| | | | (cherry picked from commit a35bf546b57558535e3fc1958cf3fb2b4d18ade7)
* Make sure repo metadata is updated before any other package when repo conf ↵Renato Botelho2016-04-041-0/+23
| | | | | | changes. Fixes #6052 (cherry picked from commit 78aee67a9e8ddb40d10c965ee8ce1ad1389d25f6)
* Use PHP CLI explicitly to run rc.conf_mount_r(w|o) from pfSense-upgrade, it ↵Renato Botelho2016-02-161-2/+2
| | | | fixes #5875
* Fix #5837Renato Botelho2016-02-051-23/+23
| | | | | | | | | | | | | | | | | | | Since the introduction of pkg_with_pb(), direct calls to this function were added using the following format: if ! pkg_with_pb ... | tee -a $logfile; then What happened in this case is if was always getting a successfull return code from tee call, and pkg_with_pb return was always being ignored leading pfSense-upgrade to keep running when a fatal error happened. Since we need to print pkg output and also send it to log, _exec() call is the best option here. Added necessary flags to make sure necessary actions (unlock additional packages or cleaning up kernel package annotation) are executed on _exit call in fatal cases and replaced all direct calls by _exec()
* Fix #5831 using a simpler approach, just setting REPO_AUTOUPDATE=false when ↵Renato Botelho2016-02-021-0/+4
| | | | it's booting
* Revert "Fix #5831"Renato Botelho2016-02-021-4/+4
| | | | This reverts commit 93a8ddf7a4c5d43cbeb623c923eb76659e6f49e0.
* Save pkg call return code to use on return. The way it is now is always ↵Renato Botelho2016-02-011-1/+2
| | | | returning 0. It should fix #5837
* Make additional packages install/delete operations to respect -n (dry-run)Renato Botelho2016-02-011-3/+3
|
* Reorder pkg_reinstall_all(), no functional changesRenato Botelho2016-02-011-11/+11
|
* Respect ALL_PACKAGES for package removalRenato Botelho2016-02-011-1/+16
|
* Fix #5831Renato Botelho2016-02-011-4/+4
| | | | | | | | | | After PKG_AUTOUPDATE=false was removed, operations done during boot, 2nd and 3rd stages of upgrade process, are trying to update repository metadata. The problem is during this stage we don't have a network available yet and all needed packages were previously downloaded. Add -U parameter to all read/write pkg calls during at these stages to prevent pkg(8) to try to update metadata
* Test duplicated slice with fsck after cloning during an upgradejim-p2016-01-281-0/+1
|
* Make sure LANG = C for pkg callsRenato Botelho2016-01-221-0/+2
|
* Change pfSense-upgrade to return time for reboot so GUI can use itRenato Botelho2016-01-141-6/+17
|
* Do not set PKG_AUTOUPDATE=false anymore and let pkg to update metadata when ↵Renato Botelho2016-01-071-23/+2
| | | | it's necessary. Some users reported to see issues in cases where update was necessary
* Only ask Proceed with upgrade question oncePhil Davis2015-12-111-1/+5
| | | | | | | | | | | On nanoBSD there is a "Proceed with upgrade?" question warning about the duplicate slice. After answering "y" to that, the system does the duplicate slice, which takes some minutes. Then it asks again "Proceed with upgrade?" after displaying all the packages it will install. That is a bit annoying at the console - I answer "y" and go off to make a cup of tea, only to come back and find that it is waiting asking again. On nanoBSD a reboot is known to be required anyway, because even if it is some little package that gets upgraded, and not the core OS, the partition is always switched. So we can say that in the first warning and then skip asking "Proceed with upgrade?" a second time. What do you think? Should it ask a 2nd time after displaying the packages to be installed? Or is it OK to skip that confirmation prompt? Also, I moved the call to setup_nanobsd_env inside the "if nanobsd" - it worked like it was because setup_nanobsd_env returns without doing anything if the system is not nanobsd, but it just looked odd and there seems no point calling it when not nanobsd.
* Fix #5598 - Nanobsd upgrade fails on GUIRenato Botelho2015-12-101-4/+4
| | | | | | When -p is used on nanobsd, progres socket must be created on secondary partition (chroot_dir) otherwise pkg, that runs with -c chroot_dir, will not be able to find UNIX socket to connect and send events
* Track nc PID and kill it on _exit()Renato Botelho2015-12-101-0/+9
|
* pfSense-upgrade script textPhil Davis2015-12-081-3/+3
| | | Just a few extra words to put in this text, while I am reading it and waiting for the upgrade to complete.
* Remove extra )Renato Botelho2015-11-271-1/+1
|
* Implement -n (dry-run) option in pfSense-upgradeRenato Botelho2015-11-271-1/+11
|
* Use _exec() to call gitsyncRenato Botelho2015-11-241-2/+3
|
* Teach pfSense-upgrade to run gitsync after upgradeRenato Botelho2015-11-231-0/+12
|
* Define user-agent on pfSense-upgradeRenato Botelho2015-11-231-0/+9
|
* Duplicate slice before upgrade, fixes #5483Renato Botelho2015-11-191-25/+36
|
* Add a workaround on pfSense-upgrade to prevent breaking strongswan port due ↵Renato Botelho2015-11-161-0/+18
| | | | to the symlinks we create
* Improve languageRenato Botelho2015-11-131-1/+1
|
* Fix copyright yearRenato Botelho2015-11-131-1/+1
|
* Improve languageRenato Botelho2015-11-131-1/+1
|
* Fix spell issue spotted by JimRenato Botelho2015-11-131-1/+1
|
* Add a new option to force upgrade script to don't rebootRenato Botelho2015-11-131-13/+18
|
* Wait 10 seconds before reboot, also notify adminRenato Botelho2015-11-131-5/+12
|
* Do not consider only meta package, but also other pfSense main packages, ↵Renato Botelho2015-11-051-4/+17
| | | | also change exit code from -1 to 2
OpenPOWER on IntegriCloud