Bug 1265059 - add vim package to appliance
Summary: add vim package to appliance
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Build
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.5.0
Assignee: Satoe Imaishi
QA Contact: Alex Newman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-22 03:43 UTC by dajohnso@redhat.com
Modified: 2015-12-08 13:31 UTC (History)
5 users (show)

Fixed In Version: 5.5.0.5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-08 13:31:59 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2551 0 normal SHIPPED_LIVE Moderate: CFME 5.5.0 bug fixes and enhancement update 2015-12-08 17:58:09 UTC

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


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