The title says it all. ebuild manifest respects RESTRICT="mirror". I try all 2.2 portage versions available, all portage-2.2.0_alpha are affected, but portage-2.2_rc67 is not. I can attach a sample shell session and/or emerge --info, but I don't think it would be useful/relevant. Please ask if one or the other is needed.
If the file is required to create the manifest, then wouldn't you expect it to download the file automatically when possible? In that case, shouldn't we fix ebuild manifest to download the files when necessary?
BTW I think repoman may be even supposed to not use mirrors in any case. I guess it's mostly supposed to do initial Manifests, and in this case the file is obviously not on the mirrors. Or remanifests, where it is better to check whether the mirrors haven't diverged.
I think the title was not clear at all, reformulated. (In reply to comment #1) > If the file is required to create the manifest, then wouldn't you expect it to > download the file automatically when possible? In that case, shouldn't we fix > ebuild manifest to download the files when necessary? Yes, but not from mirrors, as there are specific sources specified in SRC_URI.
(In reply to comment #2) > BTW I think repoman may be even supposed to not use mirrors in any case. I > guess it's mostly supposed to do initial Manifests, and in this case the file > is obviously not on the mirrors. Or remanifests, where it is better to check > whether the mirrors haven't diverged. Yeah, I guess it makes sense to automatically trigger behavior like RESTRICT="primaryuri" in this case. (In reply to comment #3) > Yes, but not from mirrors, as there are specific sources specified in SRC_URI. Right, it's even more desirable to avoid trying to fetch from mirrors when RESTRICT=mirror is set.
repoman support has been removed per bug 835013. Please file a new bug (or, I suppose, reopen this one) if you feel this check is still applicable to pkgcheck and doesn't already exist.