id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	blockedby	blocking	distribution
435	information about news-items and configuration-files missing when using --continue-on-failure	ddanier	ciaranm	"If paludis finishes successful it displays information like this:
{{{
 * Checking whether the GNU info directory needs updating...
 * No updates needed

 * No unread news items found

 * Searching for configuration files requiring action...
 * Found 12 files in /etc
 * Found files in 1 directories
 * Your action is required
}}}
Now if --continue-on-failure is active paludis will only display that
some packages failed and the resume-command. As most of the time only
minor packages fail, that might be written by the user (on my machine
most of the time my ebuilds fail, not ebuilds out of the portage-tree),
I think this information should be displayed even if some packages
failed. Perhaps even when --continue-on-failure is not used, as the
packages already installed until reaching the broken ebuild might have
provided updated config-files and as paludis merges packages in the
right order all these packages should be able to run using the new
configuration.

Anyway it would save me some headache after I fixed my ebuilds next time
they get broken. Now I have to update tons of configs. ;-)

Btw. I don't know, if skipping this ""GNU info directory""-stuff may cause problems. I just missed the infos.

Tested with ""--continue-on-failure if-independent"", ""if-satisfied"" is untested, but should behave similar I think.

I first posted here this here (for reference):[[BR]]
http://lists.pioto.org/pipermail/paludis-user/2007-November/000112.html"	enhancement	closed	Sometime		clients/paludis	0.26.0_alpha3	fixed				445