Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revisionBoth sides next revision
meta:infobox:upgrade_packages_warning [2020/04/28 22:22] – Rewriting to add details and increase the strength of the warning. pshermanmeta:infobox:upgrade_packages_warning [2020/05/11 16:21] – adding clarification about the LuCI upgrade button psherman
Line 1: Line 1:
 <WRAP center round important 100%> <WRAP center round important 100%>
 +====== Upgrading packages may cause serious problems, including soft-bricking your device!======
 +
 +
 Blindly upgrading packages (manually or via script) can lead you into all sorts of trouble.\\ Blindly upgrading packages (manually or via script) can lead you into all sorts of trouble.\\
  
-**''opkg upgrade'' may even cause a soft-brick**, rendering the device essentially inoperable!+Just because there is an updated version of a given package does not mean it should be installed or that it will function properly. Inform yourself **before** doing any upgrades to determine if it is safe to upgrade. [[https://forum.openwrt.org/t/upgrade-the-packages-on-snapshot/53158/2?u=tmomas|Avoid upgrading core packages]], 
 + 
 + 
 +---- 
 +There are two ways to manage/install packages in OpenWrt: With the LuCI web interface Software menu (System > Software), and via the command line interface (CLI). Both methods invoke the same CLI [[https://openwrt.org/docs/guide-user/additional-software/opkg|opkg]] executable, and as of OpenWrt 19.07.0, the LuCI interface now has an 'Updates' tab with a listing of packages that have available upgrades. The LuCI ''Upgrade...'' button performs the same ''opkg upgrade'' command that is discussed in this article. 
 +**The same warnings apply to upgrading packages using LuCI and the CLI.** 
 +---- 
  
 Generally speaking, **the use of ''opkg upgrade'' is very highly discouraged**, It should be avoided in almost all circumstances. In particular, bulk upgrading is very likely to result in major problems, but even upgrading individual packages may cause issues. It is also important to stress that this is distinctly different from the ''sysupgrade'' path for upgrading OpenWrt releases (major versions as well as maintenance upgrades). ''opkg upgrade'' will not update the OpenWrt version, only ''sysupgrade'' can do that -- the two are not equivalent. Generally speaking, **the use of ''opkg upgrade'' is very highly discouraged**, It should be avoided in almost all circumstances. In particular, bulk upgrading is very likely to result in major problems, but even upgrading individual packages may cause issues. It is also important to stress that this is distinctly different from the ''sysupgrade'' path for upgrading OpenWrt releases (major versions as well as maintenance upgrades). ''opkg upgrade'' will not update the OpenWrt version, only ''sysupgrade'' can do that -- the two are not equivalent.
  
-Just because there is an updated version of a given package does not mean it should be installed or that it will function properly. Inform yourself **before** doing any upgrades to determine if it is safe to upgrade. [[https://forum.openwrt.org/t/upgrade-the-packages-on-snapshot/53158/2?u=tmomas|Avoid upgrading core packages]], 
  
 Unlike the 'big distros' of Linux, OpenWrt is optimized to run on systems with limited resources. This includes the opkg package manager, which does not have built-in ABI (Application Binary Interface) compatibility and kernel version dependencies verification. Although sometimes there may be no issues, there is no guarantee and the ugprade can result in various types of incompatibilities that can range from minor to severe, and it may be very difficult to troubleshoot. In addition, the ''opkg upgrade'' process will consume flash storage space. Since it does not (and cannot) overwrite the original (stored in ROM), it must store the upgraded packages in the r/w overlay. Unlike the 'big distros' of Linux, OpenWrt is optimized to run on systems with limited resources. This includes the opkg package manager, which does not have built-in ABI (Application Binary Interface) compatibility and kernel version dependencies verification. Although sometimes there may be no issues, there is no guarantee and the ugprade can result in various types of incompatibilities that can range from minor to severe, and it may be very difficult to troubleshoot. In addition, the ''opkg upgrade'' process will consume flash storage space. Since it does not (and cannot) overwrite the original (stored in ROM), it must store the upgraded packages in the r/w overlay.
  • Last modified: 2024/03/12 21:59
  • by stokito