Hi, I'm a Unix user who is new to Mac and MacPorts. I've just started installing things using `port' today, i.e. after the release of MacPorts 1.5.1, which I understand does these `mtree' checks. I'm not able to install much without getting the "mtree violation" error. It fails to install `Xemacs' with: Error: violation by /opt/local/man Error: Target org.macports.destroot returned: mtree violation! and `gnome-doc-utils' with the same error on the way to installing other things. What should I do? Thanks. -- View this message in context: http://www.nabble.com/mtree-violations-tf4259267.html#a12121099 Sent from the MacPorts - Users mailing list archive at Nabble.com.
mpu78 wrote:
I'm a Unix user who is new to Mac and MacPorts. I've just started installing things using `port' today, i.e. after the release of MacPorts 1.5.1, which I understand does these `mtree' checks.
I'm not able to install much without getting the "mtree violation" error. It fails to install `Xemacs' with:
Error: violation by /opt/local/man Error: Target org.macports.destroot returned: mtree violation!
and `gnome-doc-utils' with the same error on the way to installing other things.
What should I do?
Downgrade to MacPorts-1.5.0, upgrade to SVN trunk, or wait until next release... --anders
Hi,
I'm not able to install much without getting the "mtree violation" error. It fails to install `Xemacs' with:
Error: violation by /opt/local/man Error: Target org.macports.destroot returned: mtree violation!
and `gnome-doc-utils' with the same error on the way to installing other things.
What should I do?
If you can, please file these as Trac tickets on the MacPorts website [1] (you'll need to create an account to do so) or, failing that, email the port maintainers. The problem is that the ports are installing files outside MacPorts' prescribed directory layout; raising this as an error is new in the latest release of MacPorts. Kind regards, Maun Suang [1] http://trac.macports.org/projects/macports/newticket -- Boey Maun Suang (Boey is my surname) Email: boeyms at macports dot org
On 2007-08-13 02:40:21 -0400, Anders F Björklund <afb@macports.org> said:
mpu78 wrote:
I'm a Unix user who is new to Mac and MacPorts. I've just started installing things using `port' today, i.e. after the release of MacPorts 1.5.1, which I understand does these `mtree' checks.
I'm not able to install much without getting the "mtree violation" error. It fails to install `Xemacs' with:
Error: violation by /opt/local/man Error: Target org.macports.destroot returned: mtree violation!
and `gnome-doc-utils' with the same error on the way to installing other things.
What should I do?
Downgrade to MacPorts-1.5.0, upgrade to SVN trunk, or wait until next release...
--anders
Are maintainers supposed to be fixing these errors somehow? I maintain a port that has this error and I don't know if I'm supposed to add destroot.violate_mtree yes or let it go until the next release. Sean
On Aug 14, 2007, at 22:23, Sean Fulton wrote:
On 2007-08-13 02:40:21 -0400, Anders F Björklund said:
mpu78 wrote:
I'm a Unix user who is new to Mac and MacPorts. I've just started installing things using `port' today, i.e. after the release of MacPorts 1.5.1, which I understand does these `mtree' checks. I'm not able to install much without getting the "mtree violation" error. It fails to install `Xemacs' with: Error: violation by /opt/local/man Error: Target org.macports.destroot returned: mtree violation! and `gnome-doc-utils' with the same error on the way to installing other things. What should I do?
Downgrade to MacPorts-1.5.0, upgrade to SVN trunk, or wait until next release... --anders
Are maintainers supposed to be fixing these errors somehow? I maintain a port that has this error and I don't know if I'm supposed to add destroot.violate_mtree yes or let it go until the next release.
Yes, you are supposed to be fixing this. You are not supposed to be violating the mtree. The next release of MacPorts will downgrade these from fatal errors to warnings, but that's only temporary, until people fix the ports. For example, if you are installing things into / opt/local/man, you should change your port to install those things into /opt/local/share/man. If you are installing things into other nonstandard places, you should evaluate whether those were intentional or not. If intentional, then you can add "destroot.violate_mtree yes" to the portfile to indicate this intent. If you are installing things in places that are being reported as an mtree violation, but you do not believe it is, then you should report that to the -dev list where it can be decided whether or not to amend the mtree checker.
On 2007-08-15 01:29:09 -0400, Ryan Schmidt <ryandesign@macports.org> said:
On Aug 14, 2007, at 22:23, Sean Fulton wrote:
On 2007-08-13 02:40:21 -0400, Anders F Björklund said:
mpu78 wrote:
I'm a Unix user who is new to Mac and MacPorts. I've just started
installing things using `port' today, i.e. after the release of MacPorts 1.5.1, which I understand does these `mtree' checks. I'm not able to install much without getting the "mtree violation" error. It fails to install `Xemacs' with: Error: violation by /opt/local/man Error: Target org.macports.destroot returned: mtree violation! and `gnome-doc-utils' with the same error on the way to installing other things. What should I do?
Downgrade to MacPorts-1.5.0, upgrade to SVN trunk, or wait until next release... --anders
Are maintainers supposed to be fixing these errors somehow? I maintain a port that has this error and I don't know if I'm supposed to add destroot.violate_mtree yes or let it go until the next release.
Yes, you are supposed to be fixing this. You are not supposed to be violating the mtree. The next release of MacPorts will downgrade these from fatal errors to warnings, but that's only temporary, until people fix the ports. For example, if you are installing things into / opt/local/man, you should change your port to install those things into /opt/local/share/man. If you are installing things into other nonstandard places, you should evaluate whether those were intentional or not. If intentional, then you can add "destroot.violate_mtree yes" to the portfile to indicate this intent. If you are installing things in places that are being reported as an mtree violation, but you do not believe it is, then you should report that to the -dev list where it can be decided whether or not to amend the mtree checker.
OK, thanks. Is there documentation for the mtree standards? Sean
Le 15 août 07 à 16:36, Sean Fulton a écrit :
On 2007-08-15 01:29:09 -0400, Ryan Schmidt <ryandesign@macports.org> said:
On Aug 14, 2007, at 22:23, Sean Fulton wrote:
On 2007-08-13 02:40:21 -0400, Anders F Björklund said:
mpu78 wrote:
I'm a Unix user who is new to Mac and MacPorts. I've just started installing things using `port' today, i.e. after the release of MacPorts 1.5.1, which I understand does these `mtree' checks. I'm not able to install much without getting the "mtree violation" error. It fails to install `Xemacs' with: Error: violation by /opt/local/man Error: Target org.macports.destroot returned: mtree violation! and `gnome-doc-utils' with the same error on the way to installing other things. What should I do? Downgrade to MacPorts-1.5.0, upgrade to SVN trunk, or wait until next release... --anders Are maintainers supposed to be fixing these errors somehow? I maintain a port that has this error and I don't know if I'm supposed to add destroot.violate_mtree yes or let it go until the next release. Yes, you are supposed to be fixing this. You are not supposed to be violating the mtree. The next release of MacPorts will downgrade these from fatal errors to warnings, but that's only temporary, until people fix the ports. For example, if you are installing things into / opt/local/man, you should change your port to install those things into /opt/local/share/man. If you are installing things into other nonstandard places, you should evaluate whether those were intentional or not. If intentional, then you can add "destroot.violate_mtree yes" to the portfile to indicate this intent. If you are installing things in places that are being reported as an mtree violation, but you do not believe it is, then you should report that to the -dev list where it can be decided whether or not to amend the mtree checker.
OK, thanks. Is there documentation for the mtree standards?
Sean
See porthier(7) manpage. -- Anthony Ramine, the infamous MacPorts Trac slave. nox@macports.org
participants (6)
-
Anders F Björklund
-
Boey Maun Suang
-
mpu78
-
N_Ox
-
Ryan Schmidt
-
Sean Fulton