Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can not mask mono-4 #62

Closed
kayvax opened this issue Jun 9, 2015 · 5 comments
Closed

Can not mask mono-4 #62

kayvax opened this issue Jun 9, 2015 · 5 comments

Comments

@kayvax
Copy link

kayvax commented Jun 9, 2015

Hi,
for some time I have problems with mono-4 from dotnet overlay. I can not mask it in any way and it breaks packages as mono-4 has removed lower targets.

I have tried asking for help at Funtoo forums and #funtoo @freenode but maintainers could not find way to mask it.

Whole topic:
http://forums.funtoo.org/topic/491-mask-problems/

Should you need more info I will try to provide it.
best regards,
kayvax

@kernelOfTruth
Copy link

When masking a higher version always go with regexp or wildcards:

Give the following a try:

=dev-lang/mono-4*
>=dev-lang/mono-4*

alternatively you could add the overlay:

=dev-lang/mono-4*::dotnet
>=dev-lang/mono-4*::dotnet

not sure if that works though.

If you only need newer versions of mono instead of all the other dotnet libraries, consider copying those over to your local overlay (e.g. /usr/local/portage) and keep them there, then removing the dotnet-overlay

Are you perhaps overriding things in /etc/portage/package.unmask (file or folder) and /etc/portage/package.keywords (file or folder) ?

@kayvax
Copy link
Author

kayvax commented Jun 10, 2015

All you advised was tried earlier and did not work. Such masks are overruled by:
/var/lib/layman/dotnet/profiles/package.unmask (or wherever one has layman configured)

cat package.unmask
dev-lang/mono
virtual/monodoc

dev-dotnet/gtk-sharp
dev-dotnet/gnome-sharp

This successfully permits any mask of this packages from dotnet overlay and I think it is outright wrong. If not for clue from funtoo forum I would never guessed that such thing could happen.

Could you please take a look on dotnet/profile/package.unmask and just check whether it needs to be in such way?

best regards,
kayvax

edit:
I have just looked in more and there is another problem with this unmask. There was commit to mask mono-4.0* with dotnet/profiles/package.mask with reason just stated with my first post. But this mask does not work also as package.unmask clearly has priority over package.mask. Thus this fix is broken.
Link 0728a42

cnd pushed a commit that referenced this issue Jun 10, 2015
@cnd
Copy link
Contributor

cnd commented Jun 10, 2015

Thank you for report, resolved in previous commit, I should also check for other unmasked packages. I'm using 9999 and it works fine and I had not tested the mask.

Check if it will install last 3.x mono from this overlay, 4.0.x is currently masked here https://github.com/gentoo/dotnet/blob/master/profiles/package.mask#L3

@cnd cnd closed this as completed Jun 10, 2015
@cnd
Copy link
Contributor

cnd commented Jun 10, 2015

@kayvax this repository is mirror, I will push it to layman some later. for now you can just pull from it

@kayvax
Copy link
Author

kayvax commented Jun 10, 2015

thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants