Bug 1575186

Summary: dnf system-upgrade from FC 27 to 28 fails to pull in required glibc-langpack-XX
Product: [Fedora] Fedora Reporter: Arne Ahrend <aahrend>
Component: dnf-plugin-system-upgradeAssignee: Orphan Owner <extras-orphan>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 28CC: aahrend, extras-orphan, mhatina
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-07 11:15:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Arne Ahrend 2018-05-05 01:18:25 UTC
Description of problem:
I am (and have been for many years) on a de_DE.UTF-8 system locale.
After upgrading to Fedora 28 via dnf system-upgrade gnome-terminal-server.service failed to start and shells in the "text mode" virtual consoles emitted warnings about locales.

Running 
dnf install glibc-langpack-de
resolved the issue.

Version-Release number of selected component (if applicable):
Not sure. It was the latest FC-27 version of dnf.


How reproducible:
Maybe install FC-27 from scratch, set a system locale LANG=de_DE.UTF-8
and upgrade to FC-28 using
dnf upgrade --refresh
dnf install dnf-plugin-system-upgrade
dnf system-upgrade download --refresh --releasever=25
dnf system-upgrade reboot



Steps to Reproduce:
1.
2.
3.

Actual results:
Shells in virtual consoles emitted warnings about locales (setlocale: LC_TIME: Cannot change default settings) and Gnome Terminal under Wayland fails to start.

Expected results:
Working Gnome Terminal

Additional info:
Running 
dnf install glibc-langpack-de
resolved the issue.

Comment 1 Arne Ahrend 2018-05-05 01:23:03 UTC
--releasever=25 is, of course, a typo.

--releasever=28 ist the correct parameter for upgrading.

Comment 2 Martin Hatina 2018-05-07 11:15:32 UTC

*** This bug has been marked as a duplicate of bug 1574222 ***