Bug 1382317 - yum has been deprecated still been used in the documentation
Summary: yum has been deprecated still been used in the documentation
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: vdsm
Classification: oVirt
Component: Documentation
Version: ---
Hardware: Unspecified
OS: Linux
unspecified
low vote
Target Milestone: ovirt-4.2.0
: ---
Assignee: Dan Kenigsberg
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-06 10:55 UTC by shah.suramya
Modified: 2019-04-17 12:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 14:47:45 UTC
oVirt Team: External
rule-engine: ovirt-4.2?
rule-engine: planning_ack+
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Github https://github.com/oVirt ovirt-site pull 513/ 0 None None None 2016-10-09 10:42:47 UTC

Description shah.suramya 2016-10-06 10:55:30 UTC 
Description of problem:


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


How reproducible:
http://www.ovirt.org/develop/developer-guide/vdsm/developers/


Steps to Reproduce:
1.open fedora terminal type any yum command  
eg. yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm



Actual results: it shows yum has been depricated 


Expected results: command should have executed easily thus it is suggested to change the documentation by adding additional dnf commands to it


Additional info:
Comment 1 Dan Kenigsberg 2016-10-06 11:31:22 UTC 
Would you be kind to suggest and alternate text using

https://github.com/oVirt/ovirt-site/edit/master/source/develop/developer-guide/vdsm/developers.html.md

?

Please remember that we also support CentOS 7, where `yum` is still alive and kicking.
Comment 2 shah.suramya 2016-10-09 10:37:26 UTC 
Alternative text patch submitted by me on github.
Note You need to log in before you can comment on or make changes to this bug.