Bug 1027379

Summary: Virtual console failed to start due to kbd package changes
Product: [openSUSE] openSUSE Tumbleweed Reporter: Dmitry Roshchin <dmitry>
Component: BasesystemAssignee: Bjørn Lie <zaitor>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: dimstar, dmitry, nsinger, sbrabec
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Dmitry Roshchin 2017-03-01 07:53:45 UTC
Due to https://build.opensuse.org/request/show/456806 virtual console failed to start as /etc/vconsole.conf contains "KEYMAP=ruwin_alt-UTF-8". System was installed as fresh setup in december of 2016.

I think we need to be more careful with breaking changes.
Comment 1 Bjørn Lie 2017-03-01 09:12:38 UTC
(In reply to Dmitry Roshchin from comment #0)
> Due to https://build.opensuse.org/request/show/456806 virtual console failed
> to start as /etc/vconsole.conf contains "KEYMAP=ruwin_alt-UTF-8". System was
> installed as fresh setup in december of 2016.
> 
> I think we need to be more careful with breaking changes.

As I said in my original sub to base:system

Request 456558 (accepted)

Hi maintainers, you need to figure out if I'm right in all corner cases here, but at least for me, this has been fine (running without legacy package installed).

---

Do you still have kdb-legacy installed? Did it get uninstalled by above change?
If it's still installed, was the content of /etc/vconsole.conf changed with that change or was the previous setup just masking an other bug
Comment 2 Stanislav Brabec 2017-03-01 15:41:01 UTC
Such change needs a migration process:

- Ensure that no tools (YaST) create configuration that depends on legacy package.

- Create a %post with migration scripts. Check whether kbd-legacy is installed. If not, update config files. Probably also %triggerun - kbd-legacy with the same will be needed (to ensure that files are correct if package is uninstaled later). This migration script has to be kept for the whole period of the upgrade support.
Comment 3 Dominique Leuenberger 2017-03-23 23:41:46 UTC
the original request was: https://build.opensuse.org/request/show/456558#

I do understand Sbrabec and I think he is right.. 

so the question would basically be why did a project maintainer, not a package maintainer accept a submission within 24 hours, when there was clearly a comment stating that "the submitter is not aware of possible side effects - it worked for him"

History: 2017-02-13T12:44:47 dirkmueller  Request got accepted
         2017-02-12T23:40:03 Zaitor       Request created

Maybe it would have been worthy to wait for somebody that understands the change and the implications (sbrabec in this case I'd assume)
Comment 4 Stanislav Brabec 2017-04-05 12:25:46 UTC
*** Bug 1030825 has been marked as a duplicate of this bug. ***
Comment 5 Bjørn Lie 2017-04-17 08:28:23 UTC
Change reverted, closing as fixed.
Comment 6 Swamp Workflow Management 2018-10-29 20:10:03 UTC
SUSE-RU-2018:3551-1: An update that has 13 recommended fixes can now be installed.

Category: recommended (moderate)
Bug References: 1010880,1027379,1056449,1062303,1069468,1085432,360993,675317,825385,830805,958562,963942,984958
CVE References: 
Sources used:
SUSE Linux Enterprise Server 12-SP3 (src):    kbd-2.0.4-8.10.2
SUSE Linux Enterprise Desktop 12-SP3 (src):    kbd-2.0.4-8.10.2
SUSE CaaS Platform ALL (src):    kbd-2.0.4-8.10.2
SUSE CaaS Platform 3.0 (src):    kbd-2.0.4-8.10.2
OpenStack Cloud Magnum Orchestration 7 (src):    kbd-2.0.4-8.10.2