Don’t use myrlyn much. A simple question re: myrlyn. Myrlyn says (paraphrasing) that it needs to be restarted for changes to take effect.
Does that mean that the changes take effect prior or during closing or does that mean that you need to actually close and restart myrlyn for the changes to be made, i.e., if you don’t restart myrlyn that your changes are not made.
I use Yast software management where you can just continue without needing to close and restart.
tom kosvic
The app is called Myrlyn. The popup explains that you need to restart to apply the change.
There is no way around the restart. You can’t bypass the restart when the above window popped up. It doesn’t matter if you press “OK” or try to close the information window via the “X”: the app closes. So you need to reopen the app and afterwards the changes are applied. This was also explained by @shundhammer some time ago and is intended behaviour.
Corrected my mispelling
AFAIK that happens when you change something in the repositories settings, so Myrlyn does a refresh of the repos according to the new settings, or possibly somewhere else in the configuration of the app.
That popup does not imply that changes to the packages installed in the system, for instance for upgrades or new installs, require a Myrlyn restart to be effective.
It does not say that Myrlyn should be restarted. it says that the application program you just updated must be restarted.
“The application” is Myrlyn as the header of the popup says.
And before this popup appears, Myrlyn explicitely tells you that it needs a restart next to the “Close” button. Pressing “Close” opens the above shown popup.
Then what are he changes? The OP leaves us in limbo about them.
Henk, simply try it yourself. It is enough to enable or disable a repository in this window. Or add a new one (as example a community repo). It doesn’t matter what you change in this window, it needs a restart. I can’t find Stefans’s explanation thread atm (that is why i tagged him in one of my answers). But it is completely expected behaviour.
Yes, it is a different behaviour to the old YaST Software Repositories module. But it does not hurt…or does it actually?
Yep, I just tested a couple different scenarios.
No. But reading helps to understand the topic when one used the app one time.
This is strictly only needed when you change anything about repos: Add, edit, delete, change priority, enable / disable. This is needed to maintain data integrity.
If you try to enter the repo management dialog while you have pending package changes, it will warn you that those changes will get lost if you change any repos; you have the option of not opening the repo management and apply your package changes, or to abandon the changes.
Well, it did not help me. And I refuse to take responsibility for misunderstanding such a poorly defined problem
The first thing one (at least I) think about when one talks about changes and Myrlyn, is about the installation, updating and or removal of software. It is the very reason Myrlyn is for: making changes.
Yes, but the OP failed to explain that (s)he did one of those things. In fact he did not explain anything about what (s)he was doing.
If you disable a repo, as an example, is that change made when you close myrlyn? Or is it made when you do the restart and if you never did a restart of myrlyn are the changes never made?
That was my question that I think is stated in the same manner in original post.
I suppose a few zypper reads after making a change with myrlyn could probably have answered my question.
tom kosvic
It is a quite easy test.
Open Myrlyn.
Disable a repo.
Close Myrlyn.
zypper lr -d and you will see that the repo is disabled.
As Stefan pointed out, the closing of Myrlyn is for data integrety reasons.
It is NOT. There is no mention or example what change was made in what area. And assuming that Myrlyn is mostly used to change your software packages, it is not obvious that this is about a change in repo management.
@hui, I just said the same thing re: zypper tests.
@hcvv ,
I think you only get that shutdown message when you make a repo change. Just removing some software is mute.
That might be correct, but it does not mean you should not tell us what you did. We (at least most of us) are not clairvoyant.
