This line is found inside file `/etc/portage/package.unmask/gcc-forward`: ~sys-devel/gcc-4.7.2 # portpeek -ruq No masked versions of ~net-misc/mediatomb-0.12.1 found. Tagged for removal. No masked versions of ~sys-devel/gcc-4.7.2 found. Tagged for removal. Now, of those two packages, with mediatomb it is right - but as of 2012-12-01, sys-devel/gcc-4.7* still remains hardmasked: !!! The following installed packages are masked: - sys-devel/gcc-4.7.2::gentoo (masked by: package.mask) /usr/portage/profiles/package.mask: # Ryan Hill <dirtyepic@gentoo.org> (02 Apr 2011) # Masked for testing Changing the line to =sys-devel/gcc-4.7.2 solves it. But that can't be intentional behaviour?
That's not correct. I will take a look
Can you try portpeek-2.1.3 when it hits the tree and let me know if this solves your issue?
Same result with 2.1.3!
Ok, the problem is that is has a tilde. I want to fix this, but if you did this: 10:09:10-root@kiowa{chroot}:/ #cat /etc/portage/package.unmask/gcc-forward ~sys-devel/gcc-4.7.2 10:09:20-root@kiowa{chroot}:/ #portpeek -ruqt package.unmask: 10:09:27-root@kiowa{chroot}:/ # Then it works. I should ignore the tilde lines if 't' is not specified.
True, it works with -t. However, that reveals two new issues with tilde and unusual package names: # grep + /etc/portage/package.keywords/stabletransition ~dev-libs/libsigc++-2.2.11 ~x11-libs/gtk+-2.24.13 The first one makes portpeek crash when tracing the line (will attach log). The second is incorrectly detected as 'not installed': x11-libs/gtk+-2.24.13: Not Installed : /etc/portage/package.keywords/stabletransition ...while # equery l -ip gtk+:2 * Searching for gtk+:2 ... [-P-] [ ] x11-libs/gtk+-2.24.12:2 [IP-] [ ] x11-libs/gtk+-2.24.13-r1:2 [-P-] [ ~] x11-libs/gtk+-2.24.14:2 Again, no problems when changing the lines to: =dev-libs/libsigc++-2.2.11* =x11-libs/gtk+-2.24.13*
Created attachment 332380 [details] portpeek error log on ~dev-libs/libsigc++-2.2.11 After issuing the following command: # portpeek -rkqt
This looks like a gentoolkit bug. I plan on opening one as I was able to create a 20 line program that shows the issue.
The initial issue seems to be fixed in 2.1.4. :)
great