You're getting this semi-automated bug report because your package was found to use scm eclasses to download a fixed source file, instead of using proper tarballs in SRC_URI. This is a violation of QA to keep the package unmasked; please do convert your package to proper tarball. If neither upstream nor the scm service provide downloads, you might have to create the tarball yourself and upload it on the mirrors (scp it to dev.gentoo.org:/space/distfiles-local), then using mirror:// . If the download system does not allow for arbitrarily named tarballs, you can also use the redirection/rename feature of EAPI=2 (-> operator in SRC_URI). If you're not going to act in one week time (at least by getting the bug assigned), the QA team reserves the right of masking your package. Note: the exception here is that we spared the straight mask because it's not a live ebuild; live ebuilds _are_ to be masked and have been masked already. Thank you for your collaboration.
FYI - just leaving a comment per the instructions that action will be taken - please do not auto-mask the build. Is this QA policy documented someplace?
Yup in devmanual; I guess wording *could* have to be extended, but it already states that live ebuilds (and fixed or not, an scm ebuild is considered "live") should be p.masked.
Ok, updated in cvs. No revbump for this.
