When updating from 0.9.7-r1 to 0.9.8, I get this: /var/tmp/portage/ethereal-0.9.8/image/usr/bin/randpkt /var/tmp/portage/ethereal-0.9.8/image/usr/bin/text2pcap >>> Completed installing into /var/tmp/portage/ethereal-0.9.8/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-ethereal-0.9.8-18093.log" open_wr: /usr/share/snmp/mibs/.index open_wr: /usr/share/snmp/mibs/.index -------------------------------------------------------------------------------- System is up-to-date rsync wise and ~x86 is in ACCEPT_KEYWORDS. Maybe this is a new instance of Bug #7953 ?
Sorry, forgot the contents of the log file: open_wr: /usr/share/snmp/mibs/.index open_wr: /usr/share/snmp/mibs/.index
I'm confused? to get ethereal to use snmp u need it in your USE and when its in your use that directory causing the violation is excluded from sandbox. I cannot reproduce the error here. Make sure if u want snmp support to add it to your USE
I hadn't specified SNMP in my USE vars (neither the one in /etc/make.profile/make.defaults nor /etc/make.conf). After adding it, ethereal emerged fine. Can there be no ethereal *without* SNMP support? And if so, why does it bomb if it's not in the USE var? KDE for example pulls in the QT dep no matter if I have QT in my use var or not. Even if the ethereal ebuild can not pull this dep on its own, it might check the USE var for snmp and complain (informatively) about that.
That's what's confusing me, if u don't have snmp in your USE it should build without support for it via a configure switch, I'm totally unable to reproduce your error with or without snmp in USE and snmp already installed etc. use snmp || myconf="${myconf} --without-ucdsnmp" is the pertinent line
I'm marking worksforme, but thanks for the new bug...it's always good to have info and reports on packages for future reference :)
Created attachment 7219 [details] ethereal ebuild including support for net-snmp Brad, I'm guessing the confusing part is that if net-snmp is installed instead of ucd-snmp, the ethereal configure will detect that and try to compile in support for it; but write permission (addwrite) has not been added in this case. I've attached a new ebuild that includes support for net-snmp. I added a new USE flag of 'netsnmp' to differentiate between the two snmp packages (in the context of the ethereal ebuild a USE flag of 'snmp; means ucd-snmp).
better that I just take out the condition than add another USE flag, as we already are bloated with them. Thanks for submitting this fix though :)
