Bugzilla Bug 1882

--------------------------- ACCESS VIOLATION SUMMARY
--------------------------- 
LOG FILE = "/tmp/sandbox-ntp-4.1.72-r1-9723.log" 

open_wr:   /opt/bitkeeper/bkmsg.txt 
-------------------------------------------------------------------------------- 
!!! emerge aborting on  /usr/portage/net-misc/ntp/ntp-4.1.72-r1.ebuild .

I just updated 1.4.72-r2 which compiles fine on my box, now.
If there are any problems, please re-open this bug!

 doins: warning, skipping directory scripts/monitoring 
doins: warning, skipping directory scripts/rc1 
doins: warning, skipping directory scripts/rc2 
doins: warning, skipping directory scripts/stats 
doins: warning, skipping directory scripts/support 
strip: 
/var/tmp/portage/ntp-4.1.72-r2/image/usr/bin/ntpd 
/var/tmp/portage/ntp-4.1.72-r2/image/usr/bin/ntpdate 
/var/tmp/portage/ntp-4.1.72-r2/image/usr/bin/ntptimeset 
/var/tmp/portage/ntp-4.1.72-r2/image/usr/bin/ntpdc 
/var/tmp/portage/ntp-4.1.72-r2/image/usr/bin/ntpq 
/var/tmp/portage/ntp-4.1.72-r2/image/usr/bin/ntptrace 
/var/tmp/portage/ntp-4.1.72-r2/image/usr/bin/ntptime 
/var/tmp/portage/ntp-4.1.72-r2/image/usr/bin/tickadj 
/var/tmp/portage/ntp-4.1.72-r2/image/usr/bin/genkeys 
>>> Completed installing into /var/tmp/portage/ntp-4.1.72-r2/image/ 
 
--------------------------- ACCESS VIOLATION SUMMARY --------------------------- 
LOG FILE = "/tmp/sandbox-ntp-4.1.72-r2-10430.log" 
 
open_wr:   /opt/bitkeeper/bkmsg.txt 
-------------------------------------------------------------------------------- 
!!! emerge aborting on  /usr/portage/net-misc/ntp/ntp-4.1.72-r2.ebuild . 
 

Can I get you to go into the net-misc/ntp directory, and type this:

ebuild --debug ntp-4.1.72-r2.ebuild compile
and if that works
ebuild --debug ntp-4.1.72-r2.ebuild package

?

It works for me, and grepping around for bitkeeper and bk doesn't show anything
useful.

Note that what you pasted, while useful, is only the *summary* of the access
violation.  If you watch the build, however, as soon as it complains, I'd love
to see what's on your screen.

Do you have or use bitkeeper?
Do you have an /opt/bitkeeper directory?

OK, I've found and squished a bug.

In the process I've learned that 4.1.72 isn't quite ready for prime time, so I
backed off to the latest stable version 4.1.1a, which is the most recent that
any other distro is willing to use.

Additionally, I masked 4.1.72 due to build problems on various machines, and the
fact that it *is* an alpha release.

Please try the 4.1.1a ebuild.

 did an emerge rsync but emerge ntp still try for 4.1.72-r2