DISCLAIMER: This article has been modified from its original version due to changes while upgrading to Deepin 15.10.1.
Deepines 3.0 has been updated to version 3.1 due to changes in Deepin 15.10.1, If you already have 2.0 installed do not need to remove, to upgrade to the latest version of Deepines 3.1, just type the following command in the terminal:
sudo apt update && sudo apt full-upgrade
Updated 18 May 2019 13:15 UTC: In the words of our beloved collaborator Hugo Florentino:
"The Chinese, in their infinite ancient wisdom, decided it was good idea to name as" stable "version also Deepin based on Debian unstable, and incidentally put the same version number."
It has been reported that upgrading to Deepin 15.10.1 without any installation from scratch with the ISO version 15.10, running the lsb_release -a command parameter obtained in Codename: stable. We are reviewing the data, currently anticipate that the window manager and the kernel have not changed, so there has been a change based on actual unstable stable at this time. We are also working on the installer Deepines 3.0 repository to avoid problems with unstable base. If you have not installed from scratch with ISO Deepin 15.10 or 15.10.1, we recommend not installing Deepines 3.0 to prevent your system from breaking. Additional sorry this is causing confusion and in the coming hours will be updating the information.
Updated 18 May 2019 21:01 UTC: And we reviewed in detail the changes made unstable Deepin when upgrading from 15.10 to 15.10.1. We can ensure that the base remains Debian SID 9 (unstable), the kernel was not updated and continues with the 4.15.0-29deepin-generic version did not change the window manager, remains Mutter (DeepinGala), although the output of -a lsb_release the report as "stable".
Build a computer system it has many similarities to the construction of buildings. Are built in sections or modules, you can make room to build more in the future and, above all, you must make changes and improvements over time, as a kind of remodeling.
In the case of GNU / Linux operating systems, when a new feature is built or you make changes, you need to try and make sure they work perfectly. These tests take time. Then developers (builders) have versions of well-proven system but older and newer versions but are still in the testing process and continue to find problems that are fixed on the fly.
The well tested and well functioning old versions are called stable and undergo little change versions that work very well. The newest versions, which are still being tested and is still being worked on are called unstable versions because they are undergoing changes frequently.
Deepin is based on other distribution, Debian, which has a stable and unstable another version. Previous to Deepin 15.10 Deepin was based on Debian unstable, but this brought disadvantages resulting from constant changes and failures not yet detected.
Deepin From 15.10 onwards, Deepin is based on Debian stable, this makes the system has far fewer failures, work and behave more evenly over time and not be constantly changing.
With an unstable base, Deepin developers should be reviewed very often the new changes and adapting the system to changes in the base, this is very tiring and consume many resources and working hours.
With a stable base, developers should review fewer times changes the base, which gives them time to develop the system more calmly and higher quality.
Deepin unstable stable stable beta Deepin and Deepin
There was considerable confusion when it began to mention on a stable beta version Deepin, but then clarify.
|Debian unstable Deepin +||=||Deepin unstable|
|Deepin + Debian stable||=||Deepin stable|
We explained the disadvantages of using an unstable base and that is why developers started migrating an unstable base for stable, they made a parallel process can be better understood with the following timeline.
Deepin in the beginning used as a base Ubuntu, but that does not include the timeline for being "old" story. Then he went on to use as a base unstable Debian was the version that we all knew and used in recent years, we used unstable Deepin, but since there was no other version, there was no need to differentiate or declare anything else, so it was called Deepin to dry.
When version 15.9.2 was released, developers took the Deepin environment and mounted on Debian stable, thus giving birth to a new version, stable Deepin, then it was necessary to declare Deepin stable and unstable to differentiate Deepin.
It was not a small change, in contrast, operate at Deepin on Debian stable required many changes and adjustments, which had not been tested, so the new version with stable base should be also declared as beta version, so they named Deepin stable 15.9.2 Beta, because I was not ready for the general public to wear it.
Continued parallel development of unstable and stable Deepin, while developing version 15.9.3 and 15.10 of the unstable version, preparations continued to post stable Deepin 15.10.
At the time of publication Deepin 15.10, its environment was able to function both stable base and unstable, but the bases are different enough to not allow change unstable base stable through a process of renovation, so it is necessary make a clean installation to move from the unstable to the stable basis. Considering users, Deepin from China will continue to provide updates until July 2019, giving chance to program and make reinstatements calmly.
Will I pass immediately to the Deepin stable or hope?
15.10 Deepin still stable is a territory that is not fully explored, the first to install stable Deepin 15.10 will be a kind of pioneer, and pioneers always find unexpected problems will be solved. In the new version there are things to polish, many versions of software are older than in unstable, so some applications installed from external sources may be inconvenient to install.
What comes installed in the distribution and what can be installed in the store work perfectly, most problems encountered are details of customization or install applications that are not part of the distribution, that is, which are discharged manually or need repositories additional.
As for Flatpak applications and snap function as usual.
In short, if you intend to install clean, every detail work exactly as they did so far and does not get to solve virtually anything better to wait a few weeks for others have already worked out the details, but if you have courage and time to be pioneer, no problem, so be it.
Again we recall that has until July 2019 to make a clean installation with ISO 15.10 Deepin stable.
How to identify if you have stable or unstable base?
We have published a new article which shows you how to identify the exact version of the system you're using a tool created by our friend Hugo FlorentinoYou can read the aforementioned article you here.
The Deepines repository also had to adapt to the new stable base, as a result was presented Deepines 3.0, this version supports only stable Deepin 15.10 and higher.
You can find instructions for installing Deepines 3.0 on the following link - deepinenespañol.org / present-our-repository-deepines-3-0.
Unfortunately Deepines unstable repository for Deepin stops working, it keeps this because consume the limited resources of time and effort of the volunteers who maintain it, and decided to focus those resources into the new repository. This means that you can no longer install applications Deepines Deepin unstable, but what you have installed will continue running smoothly.
If someone tries to install Deepines 3.0 unstable Deepin or any other distribution other than stable Deepin, the installation will fail. The installer detects whether Deepin 15.10 is stable or higher, if not, displays an error message and is not installed. This is for safety reasons, to prevent damage to the system (to break the system). Here are all the error messages for the most common installation methods.
Deepin installation Package Manager
Installation command DPKG
If you have unstable Deepin we recommend uninstalling Deepines 2.0 to avoid inconvenience. Follow these steps:
Run in a terminal the following command.
sudo apt purge deepines-repository
If your password is requested, type and press the ENTER key. It is normal if the password is not displayed anything.
When you are prompted to continue to press the key ENTER.
An optional procedure to ensure remove all traces of Deepines 2.0 after a regular uninstallation is as follows:
1- Download the following script and save it on Desktop.
2- Verify that the file eliminar-deepines-2.0.sh is Desktop.
3- Minimize all windows to view the desktop.
4- Right-click an empty spot on the desktop and then click the option to open the terminal.
5- Run the command
sudo sh eliminar-deepines-2.0.sh
We hope this article helps the community to be clear about the new landscape after the publication of 15.10 Deepin stable, because it is necessary to install from scratch and Deppines changes to the repository.
DISCLAIMER: We are investigating new reports that apparently change any of the information contained in this article, please see later for clarifications and adjustments to the publication. PLEASE LOOK AT BUTT OF THIS ARTICLE FOR THE LATEST INFORMATION BECOMES AVAILABLE.
*Special thanks to Hugo Florentino, Jose Fenoll Y Opik O for their help in reviewing and correcting this article.
Isaiah Gätjens He is the author and Collaborating Deepin in Spanish. You can read several articles on our home page, as well as help messages both in the community forum and in our chat room Telegram.