Bug 1193611

Summary: yumex 3.0.15 does not install/erase as the root -- NOT FIXED IN EPEL7
Product: [Fedora] Fedora EPEL Reporter: Bob Elzer <bob.elzer>
Component: yumexAssignee: Tim Lauridsen <tim.lauridsen>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: epel7CC: bjrosen, extras-qa, hafflys, irlapati, k_a_r_l_o_, tim.lauridsen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1111142 Environment:
Last Closed: 2015-04-16 08:05:16 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 Bob Elzer 2015-02-17 17:04:20 UTC
+++ This bug was initially created as a clone of Bug #1111142 +++

Description of problem:

This bug was fixed in Fedora 20/21, but it was not fixed in EPEL7


When yumex is started with the root privileges from a terminal, it is not possible to install or erase any package.


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

3.0.15

How reproducible:

100%

Steps to Reproduce:
1. Open a terminal
2. Start a root session (su or su - )
3. Start yumex --root
4. Select any package to be installed or erased. 
5. Click on the [Apply] button.

Actual results:

Nothing happens.
The response in the terminal is "DEBUG - network interface enp8s0 (r8169) is connected".

Expected results:

The process to resolve dependencies should be started.



Additional info:

yumex 3.0.13 works as expected

--- Additional comment from Tim Lauridsen on 2014-06-20 00:38:59 EDT ---

Tnaks for reporting, I will look into the issue

--- Additional comment from Stephen Haffly on 2014-06-21 21:39:04 EDT ---

Reverting to 3.0.13 works for me also.

--- Additional comment from Joshua Rosen on 2014-06-30 14:51:07 EDT ---

I'm seeing the same problem.

--- Additional comment from Joshua Rosen on 2014-07-23 09:31:40 EDT ---

It's been a month, how come nothing has happened?. This is a serious problem, it's impossible to use Yumex on a remote machine in it's current broken state.

--- Additional comment from Tim Lauridsen on 2014-07-24 02:51:56 EDT ---

(In reply to Joshua Rosen from comment #4)
> It's been a month, how come nothing has happened?. This is a serious
> problem, it's impossible to use Yumex on a remote machine in it's current
> broken state.

Easy now, yumex is a project I work on in my limited spare time, so things can take some time, its holiday season now, so i priotize spending time with my family and enjoying the good weather here in DK :-)


Fixed upstream now, see here how to test

http://www.yumex.dk/p/how-to-test.html

--- Additional comment from Stephen Haffly on 2014-07-24 10:22:37 EDT ---

Thanks for the fix. However, I will wait until it shows up in updates-testing. Hopefully, that will be soon.

--- Additional comment from Fedora Update System on 2014-10-05 05:14:57 EDT ---

yumex-3.0.16-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/yumex-3.0.16-1.fc21

--- Additional comment from Fedora Update System on 2014-10-05 05:15:07 EDT ---

yumex-3.0.16-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/yumex-3.0.16-1.fc20

--- Additional comment from Fedora Update System on 2014-10-06 01:03:54 EDT ---

Package yumex-3.0.16-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing yumex-3.0.16-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-12255/yumex-3.0.16-1.fc21
then log in and leave karma (feedback).

--- Additional comment from Fedora Update System on 2014-10-08 15:15:16 EDT ---

yumex-3.0.16-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

--- Additional comment from Fedora Update System on 2014-10-14 00:44:34 EDT ---

yumex-3.0.16-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 1 Joshua Rosen 2015-03-21 17:33:55 UTC
Hi the problem was fixed in Fedora five months ago but it still hasn't been fixed in EPEL7. Please push the change to EPEL7. I know I sound like a broken record but this is really important.

Thanks,

Comment 2 Tim Lauridsen 2015-04-07 12:00:04 UTC
Sorry for the long waiting time, I have been very busy lately

I have made a new build for el7, please check it out

https://admin.fedoraproject.org/updates/yumex-3.0.16-1.el7

Comment 3 Joshua Rosen 2015-04-07 21:31:06 UTC
Getting an RPM dependency problem. I'll wait a few days and then try it again.

Resolving Dependencies
--> Running transaction check
---> Package yumex.noarch 0:3.0.15-2.el7 will be updated
---> Package yumex.noarch 0:3.0.16-1.el7 will be an update
--> Processing Dependency: python-pexpect for package: yumex-3.0.16-1.el7.noarch
--> Finished Dependency Resolution
Error: Package: yumex-3.0.16-1.el7.noarch (epel-testing)
           Requires: python-pexpect

Comment 4 Bob Elzer 2015-04-10 16:10:08 UTC
OK, I believe the fix for this now, is to change the require python-pexpect to  require pexpect, in the .spec file.

I hade the same problem as you installing, so I downloaded the rpm file and ran the following command on it.

rpm -Uvh --force --nodeps yumex-3.0.16-1.el7.noarch.rpm

This ignored the dependency error, and now yumex --root is working fine. 

It just needs to have the dependency fixed so others won't have the problem.

Tim, thanks for updating this.

Comment 5 Joshua Rosen 2015-04-10 16:27:05 UTC
Thanks, it's working

Comment 6 Tim Lauridsen 2015-04-13 07:16:32 UTC
made a new build with the right pexpect requirement

https://admin.fedoraproject.org/updates/yumex-3.0.16-2.el7

Comment 7 Bob Elzer 2015-04-13 15:55:14 UTC
Sounds good, I'll test it out when it reaches epel-testing and let you know.

Comment 8 Bob Elzer 2015-04-16 02:58:38 UTC
Success, yumex-3.0.16-2.el7 now works as it should. You can mark this as closed now.

Thanks again Tim.