Bug 1214062 - unclear that changes to enabled/disabled repos are not persistent
Summary: unclear that changes to enabled/disabled repos are not persistent
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: yumex-dnf
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Lauridsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-21 20:52 UTC by John
Modified: 2015-05-01 16:45 UTC (History)
2 users (show)

Fixed In Version: dnfdaemon-0.3.7-1.fc21
Clone Of:
Environment:
Last Closed: 2015-05-01 16:38:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
repo preferences screenshoot (28.56 KB, image/png)
2015-04-24 05:24 UTC, Tim Lauridsen
no flags Details

Description John 2015-04-21 20:52:05 UTC
Description of problem:
Does not remember repos being enabled/disabled.

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

How reproducible:
100%

Comment 1 Tim Lauridsen 2015-04-22 08:26:29 UTC
yumex-dnf by default uses the repositories enabled on the local system
you can change it for the current session, but it does not change the state of the enabled repositories.

I you want to change what repositories is enabled/disabled, you must edit the .repo files in /etc/yum.repo.d

Comment 2 John 2015-04-22 14:15:34 UTC
Hi, Tim :-)

Could you explain your reasoning?

If you feel it's not yumex's place to edit the system-wide configuration, wouldn't it still make sense to save the user's preference within yumex? It is after all listed in the "Preferences" window.

Also, if it won't edit the system-wide configuration, I think it would be prudent to indicate that fact within the Repositories dialog (something like "Changes here apply to Yum Extender, only"). I expect that many users might get the impression that it affects the whole system -- for example, the packagekit GUI installer has a similar dialog to enable/disable repos and it takes effect on the whole system.

Comment 3 Tim Lauridsen 2015-04-23 16:59:04 UTC
The repotories was meant to uses where you want to temporary enable fx. updates-testing and install selected updates, I want to test.

But I don't want to have updates-enabled every time i start yumex.

maybe i could add a button to the repository page, there will save the current select repositories as yumex default and use the default when you start yumex.

then both usecases can be solved.

Comment 4 John 2015-04-23 18:19:23 UTC
I actually think it's less important that the enabled/disabled states be saved than that it's clear in what context those enabled/disabled states apply (presently within the current session of yumex).

I think answers to the following questions need to be clear for users:
1) Where does this change apply? ("yumex only" ... now that I think about it, I believe this is clear enough since it's listed in the yumex "Preferences" (it wasn't originally clear to me because of my background in using the PackageKit installer GUI, but that's an issue of my assumptions more so than an issue with your GUI))
2) Are these changes persistent? ("no" ... I don't think the fact that the changes aren't persistent is clear except after trial and error)

So if you wanted to add a way to make the changes permanent, that would be okay, but I guess probably not necessary for most use cases (not even my own). I do however think it's important to make #2 clearer. I think it would make sense to add a note on that tab that those settings are temporary to avoid the possibility of misunderstanding.

Sorry for making this topic needlessly confusing. Ultimately I think you should just clarify the fact that changes to enabled/disabled states are temporary.

Comment 5 Tim Lauridsen 2015-04-24 05:24:03 UTC
Created attachment 1018307 [details]
repo preferences screenshoot

I have changed the repo preferences to look like this
hope it make more clear how it is used

Comment 6 John 2015-04-24 12:18:14 UTC
Definitely clearer!

Comment 8 Fedora Update System 2015-04-26 16:47:04 UTC
yumex-dnf-4.1.1-1.fc22,dnfdaemon-0.3.7-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/yumex-dnf-4.1.1-1.fc22,dnfdaemon-0.3.7-1.fc22

Comment 9 Fedora Update System 2015-04-27 08:42:14 UTC
Package yumex-dnf-4.1.1-1.fc22, dnfdaemon-0.3.7-1.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing yumex-dnf-4.1.1-1.fc22 dnfdaemon-0.3.7-1.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-6975/yumex-dnf-4.1.1-1.fc22,dnfdaemon-0.3.7-1.fc22
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2015-04-27 08:43:31 UTC
yumex-dnf-4.1.1-1.fc21,dnfdaemon-0.3.7-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/yumex-dnf-4.1.1-1.fc21,dnfdaemon-0.3.7-1.fc21

Comment 11 Fedora Update System 2015-05-01 16:38:53 UTC
dnfdaemon-0.3.7-1.fc21, yumex-dnf-4.1.1-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 12 Fedora Update System 2015-05-01 16:45:28 UTC
yumex-dnf-4.1.1-1.fc22, dnfdaemon-0.3.7-1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 13 Fedora Update System 2015-05-01 16:45:29 UTC
yumex-dnf-4.1.1-1.fc22, dnfdaemon-0.3.7-1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.


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