Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1451876 - gnome 3.22 -> 3.14 downgrade path
gnome 3.22 -> 3.14 downgrade path
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: Red_Hat_Enterprise_Linux-Release_Notes-7-en-US (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Lenka Špačková
Jana Heves
: Documentation
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-05-17 13:57 EDT by Tomas Pelka
Modified: 2018-04-10 09:41 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
GNOME downgrade does not work With the new version of GNOME (3.22) introduced in Red Hat Enterprise Linux 7.4, downgrading GNOME from version 3.22 to 3.14 using the "yum downgrade" or "dnf downgrade" commands is no longer possible. The only workaround lies in replacing the GNOME-related packages with their old versions. If you decide to downgrade manually, read the GNOME 3.16-3.22 release notes to find which functionalities you are losing.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 09:41:47 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tomas Pelka 2017-05-17 13:57:18 EDT
Document URL: 

Section Number and Name: 

Describe the issue: 

With rhel7.4 we are going to update whole gnome to new version 3.22. Together with this new release we are also going to introduce coupe of brand new pkgs and few renaming and splitting of existing ones. This change makes downgrade near to impossible. It would be nice to document this fact in our desktop guides or release notes.

We have been in this situation also in rhel7.2 time frame too. Everything ok back than so it should be fine now too.  

Suggestions for improvement: 

Additional information:

Note You need to log in before you can comment on or make changes to this bug.