Bugzilla Bug 101070

Emerging amavisd-new-2.3.2 causes the following problem.  razor-agent.conf if
definitely writable.

>>> Completed installing amavisd-new-2.3.2 into
/var/tmp/portage/amavisd-new-2.3.2/image/

--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/var/log/sandbox/sandbox-mail-filter_-_amavisd-new-2.3.2-6061.log"

open_wr:   /etc/razor/razor-agent.conf
--------------------------------------------------------------------------------


Reproducible: Always
Steps to Reproduce:
1. emerge amavisd-new
2.
3.

Actual Results:  
Emerge failed with above results

Expected Results:  
Emerged amavisd-new sucessfully.

Please post your installed version of mail-filter/razor, and a complete
amavisd-new emerge output.

Created an attachment (id=64931) [details]
Log of attempt at Emerging Amavisd-new-2.3.2

Razor Version: 2.74

Thanks for the help! :)

Do you have razor set up in /etc/razor ? Strace of "razor-admin -create
-home=/whatever" shows that it is trying to open /etc/razor/razor-agent.conf at
certain points.

This is correct.  razor-agent.conf is in /etc/razor

This looks like a bug in razor. CCing upstream contact - Jordan, can you
comment
on this? Looks like razor-admin tries to write into
/etc/razor/razor-agent.conf,
even if a different -home= was specified.

Acknowledged, reviewing.

I believe this has been fixed -- both the bug itself and perhaps a related
sandbox violation in the ebuild 
(see the gentoo razor changelog:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/*checkout*/mail-filter/
razor/ChangeLog).  

I reviewed the full strace output of ``razor-admin -create -home=/tmp/razor''
with v2.75 and could 
not reproduce this problem.  

I am unsure of why 2.75 is still masked.  The only bug I can find in the
bugbase with ``razor'' as a 
keyword is this one.  Can someone please ping folks to unmask?

Ray, could you try upgrading to razor 2.75 ?

Jordan, 2.75 is not marked stable yet, because it hasn't passed the usual 30-day
unstable period in portage.

Unfortunately same error as before. Installed razor-2.75 and same behaviour as
previously documented.

OK, here is some more info.  If I move or delete the /etc/razor directory,
amavisd-new emerges perfectly without a problem.

Ray, would you be kind enough to attach an strace of your v2.75 attempt?  I
tried it both with ``/etc/
razor'' pre-existing and without, and in neither case when ``-home=/tmp/razor''
could I find any 
instance of the agents stat()'ing or chdir()'ing or open()'ing anything in
``/etc/razor''.

My invocation was:  strace razor-admin -create -home=/tmp/razor >
/tmp/razor-strace.log 2>&1

Created an attachment (id=64958) [details]
razor.strace.log

I can provide such strace log too. The version used is 2.75.

Created an attachment (id=64971) [details]
razor.strace.log

Bug confirmed and fixed in CVS.  Will be in the forthcoming 2.76 release. 
Thank
you for the report!

Thanks!

Can I mark FIXED?

No, this bug should stay open until 2.76 comes out and respective ebuild is
added to portage.

Ok, this problem is gone for me after upgrading to recently released
razor-2.77.
Ray, feel free to reopen this bug, if it still doesn't work for you.
Jordan, thanks. :)