[ebuild U ] x11-libs/libXtst-1.0.2 [1.0.1] USE="-debug" 220 kB [?=>0] I have no idea what the last thing is so I went to look at man emerge where there is the OUTPUT section. OUTPUT When utilizing emerge with the --pretend and --verbose flags, the output may be a little hard to understand at first. This section explains the abbreviations. This new last format is not explained in the man page.
So if I understand it correctly it is trying to tell me that the source repository of the current version could not be determined but it would be update to 0 (/usr/portage/.
(In reply to comment #1) > So if I understand it correctly it is trying to tell me that the source > repository of the current version could not be determined but it would be > update to 0 (/usr/portage/. Correct.
(In reply to comment #0) > [ebuild U ] x11-libs/libXtst-1.0.2 [1.0.1] USE="-debug" 220 kB [?=>0] > > I have no idea what the last thing is But there is: Portage tree and overlays: [0] /usr/portage [?] indicates that the source repository could not be determined
Created attachment 126194 [details, diff] to avoid spam during the transition period, ignore a missing repo labels for installed packages I think this patch will help a lot during the transition period. It's in svn r7409.
(In reply to comment #4) > Created an attachment (id=126194) [edit] > to avoid spam during the transition period, ignore a missing repo labels for > installed packages > > I think this patch will help a lot during the transition period. It's in svn > r7409. Heh, actually the plan was to let 2.1.3* seed vdb with the repository information, and only make use of it in 2.2, the backport of the display code wasn't intended (but now it's too late to revert it). Also IMO this hack should only be a temporary measure until 2.1.3 is done.
Yeah, I think we should revert this hack eventually too. It's just a temporary solution to prevent people from whining about being spammed with useless info because the packages in their vdb aren't labeled yet.
This has been released in 2.1.3.