Bug 529942

Summary:	app-portage/eix-0.29.3 shows that net-im/skype-4.3.0.37-r3 is masked (^msd) though it was removed from package.mask.
Product:	Portage Development	Reporter:	Barbudos <ghost-87>
Component:	Third-Party Tools	Assignee:	Portage Tools Team <tools-portage>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	Normal
Version:	2.2
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	emerge --info

Description Barbudos 2014-11-20 12:27:46 UTC

Due to the recent buggy net-im/skype-4.3.0.37-r3 ebuild, which depended on unstable pulseaudio, I found the old net-im/skype-4.3.0.37-r1 and placed it in my usr/local/portage overlay, and then masked it (add >net-im/skype-4.3.0.37-r1 in package.mask) to save ebuild from upgrading. It worked fine. But net-im/skype-4.3.0.37-r3 has been repaired soon, and was updated with working version in main tree. I decided to install main tree version, which was corrected, and remove the old ebuild from local overlay. It was done, and I didn't forget to delete the ">net-im/skype-4.3.0.37-r1" string from package.mask. Then I did env-update && source /etc/profile and eix-update. But since these manipulations eix shows me that net-im/skype-4.3.0.37-r3, which I have now installed, is still masked. All forks fine for now, I think it's only about eix output.

Comment 1 Barbudos 2014-11-20 12:31:30 UTC

Created attachment 389856 [details]
emerge --info

Comment 2 Martin Väth 2014-11-20 14:26:10 UTC

^msd in eix does not mean masked. It means that the ebuild sets some RESTRICT values (mirror, strip, bindist). Search the eix manpage for "^"