I got this email from my cron. -- Cron <root@vps> emerge --sync --quiet 12:02 AM (13 hours ago) q: Updating ebuild cache in /usr/portage/gentoo ... -- Not very useful information to me for a --quit command. Is this by design or a bug?
what version of portage-utils do you have installed, and how does your etc/portage/repo.postsync.d/q-reinit look like?
(In reply to Fabian Groffen from comment #1) > what version of portage-utils do you have installed, and how does your > etc/portage/repo.postsync.d/q-reinit look like? app-portage/portage-utils-0.64 chris@vps ~ $ cat /etc/portage/repo.postsync.d/q-reinit #!/bin/sh repository_name=$1 repository_path=$3 if [ -n "${repository_name}" ]; then q ${PORTAGE_QUIET:+-q} --reinitialize="${repository_path}" fi :
this problem is fixed since portage-utils-0.65, I guess it's time for requesting a new stable version
should i unmask app-portage/portage-utils-0.65 isntead?
For the time being (there's other problems why I can't request for a new stable version, which likely won't affect you) you best add an package.accept_keywords entry for portage-utils-0.73 or change the q-reinit file. Sorry for the inconvenience.
The package was stabilized and the bug is now gone. However I noticed that when I accidentally used --silent --quiet instead of just --quiet there was an error syncing and it was not displayed.
Could you please create a new bug for portage-utils regarding the new problem? The problem described in this one is fixed now, I think. Thanks
