Bug 1265059

Summary: add vim package to appliance
Product: Red Hat CloudForms Management Engine Reporter: dajohnso <dajo>
Component: BuildAssignee: Satoe Imaishi <simaishi>
Status: CLOSED ERRATA QA Contact: Alex Newman <anewman>
Severity: medium Docs Contact:
Priority: high    
Version: 5.5.0CC: cpelland, jfrey, jhardy, mfeifer, obarenbo
Target Milestone: GA   
Target Release: 5.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.5.0.5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-08 13:31:59 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 dajohnso@redhat.com 2015-09-22 03:43:01 UTC
Description of problem:
==========================
vim package was part of the appliance, now it is not.


Version-Release number of selected component (if applicable):
===========================
5.5.0.1

Comment 2 Jason Frey 2015-09-24 19:56:07 UTC
Do you literally need vim, or is vi enough?

Comment 3 Dave Johnson 2015-10-05 14:29:18 UTC
vim is out of habit and it is on the older appliances, I'd be ok with an alias from vim to vi but annoyed with hitting 'vim not found error' and having to use vi when switching between different appliance versions.

Does it matter, is there concern on the size of the appliance?   What's the delta?

Comment 4 Satoe Imaishi 2015-10-08 15:50:08 UTC
@base no longer contains vim.  Added explicitly in 5.5.0.5.

Comment 5 Alex Newman 2015-10-26 13:44:39 UTC
Version: 5.5.0.7-beta1.3.20151021133253_ed40d96
VIM version: 7.4.160

# which vim
/usr/bin/vim

# which vi
/usr/bin/vi

Comment 7 errata-xmlrpc 2015-12-08 13:31:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2015:2551