I think it's ok to mask to the package from entropy. Just make sure to run 'equo rescue spmsync' each time you update the package via portage. It would certainly make it much easier to keep track of when you need to upgrade it if it's masked by entropy.

sabayonino, I'm not the one with the issue, not sure why you're replying to me.

And he should still keep the package masked, or else the next time there's an upgrade, entropy will install over it. It's better, in my opinion, for entropy to tell you to upgrade the package via portage (by saying it can't because of the mask), then to overwrite it without asking.

hm, somehow that Wiki-article is changed.equo rescue spmsync is only useful if you change your client.conf. It should be mentioned in the article, but got removed.open "/etc/entropy/client.conf" and change the line that says:

Please remember that once you've manually changed client.confeverytime you upgrade the system wants to revert it back, by asking you to "equo conf update"And when invoking "equo rescue spmsync" , please use the --ask flag.

Normally you don't need to mask the package in Entropy.The above setting in client.conf together with "equo rescue spmsync" only prevents Entropy to not downgrade.However, if Entropy has a new version, it WILL be overwritten, with default flags, predefined by Entropy, and you will lose the flags you've defined.It's nice to mix Entropy and Portage, and it can be done., but you must really know what you are doing.A good knowledge of both package managers is advised.As for both package managers, i also would advise you to always use --ask., and never blindly upgrade the system."emerge -a packagename" for Portage and "equo i packagename --ask" for Entropy