Let us continue this discussion in chat. No, indeed, those are not new releases but only new "point releases", and they're not supposed to introduce new dependencies either. HalosGhost 4, 10 10 gold badges 30 30 silver badges 40 40 bronze badges. Wendell Wendell 11 1 1 bronze badge. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete?
Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta. Now live: A fully responsive profile. Linked 5. Related 0. Hot Network Questions. Contents hide. Backup your system. Perform a full system update. Get current status. Change repositories. Perform a full system update again. Upgrade system. Fix Apache 2. Remove unused packages. Get new status. Setting up liblvm2cmd2. At the very least, you'll want to generate full backups of all your Virtual Servers.
These packages are already installed, but the following command will tell apt not include them anytime "apt-get autoremove" is run:. There is a problem with the Dovecot package during the upgrade process which frequently causes the upgrade to fail. The simplest fix is to temporarily remove it, and then reinstall it again after the upgrade completes.
The next few steps will have you installing various packages. Some of those will ask you questions. If you do not see any output, then you will either need to install a new linux-image package by hand or install a linux-image metapackage.
To see a list of available linux-image metapackages, run:. If you are unsure about which package to select, run uname -r and look for a package with a similar name. For example, if you see ' 2. You may also use apt-cache to see a long description of each package in order to help choose the best one available. For example:. You should then use apt-get install to install it. Once this new kernel is installed you should reboot at the next available opportunity to get the benefits provided by the new kernel version.
However, please have a look at Section 4. For the more adventurous there is an easy way to compile your own custom kernel on Debian. Install the kernel sources, provided in the linux-source package. You can make use of the deb-pkg target available in the sources' makefile for building a binary package. More information can be found in the Debian Linux Kernel Handbook , which can also be found as the debian-kernel-handbook package.
If possible, it is to your advantage to upgrade the kernel package separately from the main dist-upgrade to reduce the chances of a temporarily non-bootable system.
Note that this should only be done after the minimal upgrade process described in Section 4. If the RTC real time clock is set to local time and the local time is ahead of UTC, e2fsck will print a warning during boot about the time changing backward bug When upgrading from Wheezy to Jessie, it can be a good idea to purge old packages before the first reboot. In particular, obsolete init scripts may cause issues.
Remove newly redundant or obsolete packages as described in Section 4. You should review which configuration files they use and consider purging the packages to remove their configuration files.
See also Section 4. It is generally advisable to purge removed packages. This is especially true if these have been removed in an earlier release upgrade e. In particular, old init. Purging a package will generally also purge its log files, so you might want to back them up first.
The following command displays a list of all removed packages that may have configuration files left on the system if any :. The packages can be removed by using apt-get purge. Assuming you want to purge all of them in one go, you can use the following command:. If you use aptitude , you can also use the following alternative to the commands above:.
With the next release of Debian 9 codenamed stretch some features will be deprecated. Users will need to migrate to other alternatives to prevent trouble when updating to 9. The hardening-wrapper package is deprecated and is expected to be removed in Stretch.
Introducing lot of new packages, jessie also retires and omits quite some old packages that were in wheezy. It provides no upgrade path for these obsolete packages. While nothing prevents you from continuing to use an obsolete package where desired, the Debian project will usually discontinue security support for it a year after jessie's release [5] , and will not normally provide other support in the meantime. Replacing them with available alternatives, if any, is recommended.
There are many reasons why packages might have been removed from the distribution: they are no longer maintained upstream; there is no longer a Debian Developer interested in maintaining the packages; the functionality they provide has been superseded by different software or a new version ; or they are no longer considered suitable for jessie due to bugs in them.
The Debian Bug Tracking System often provides additional information on why the package was removed. You should review both the archived bug reports for the package itself and the archived bug reports for the ftp.
Once the operating system upgrade is finished, you should plan to also upgrade your PostgreSQL 9. Version 2. Please install the package ruby to automatically track the current ruby version.
Whilst the former is mostly compatible with mplayer in terms of command-line arguments and configuration and adds a few new features too , the latter adds a lot of new features and improvements, and it is actively maintained upstream. Some packages from wheezy have been split into several packages in jessie, often to improve system maintainability. Most but not all dummy packages' descriptions indicate their purpose.
Note that some dummy packages are not intended to be removed after an upgrade but are, instead, used to keep track of the current available version of a program over time. In the DHCP case end-users might be disconnected from the network if the lease time is lower than the time it takes for the upgrade process to complete.
Typically only two stable releases are supported at any given time. Chapter 4. Upgrades from Debian 7 wheezy. Table of Contents 4. Preparing for the upgrade 4.
Back up any data or configuration information 4. Inform users in advance 4. Prepare for downtime on services 4. Prepare for recovery 4.
Prepare a safe environment for the upgrade 4. Checking system status 4. Review actions pending in package manager 4. Disabling APT pinning 4. Checking packages status 4.
The proposed-updates section 4. Unofficial sources 4. Preparing sources for APT 4. Adding APT Internet sources 4. Adding APT sources for a local mirror 4. Adding APT sources from optical media 4.
Upgrading packages 4. Recording the session 4. Updating the package list 4. Make sure you have sufficient space for the upgrade 4. Minimal system upgrade 4. Upgrading the system 4. Possible issues during upgrade 4.
0コメント