Re: MacPorts missing links
> On 12 Sep 2016, at 17:39, Lawrence Velázquezwrote: >> I should read more documentation on “port select”. I think that “man port” >> does not give an adequate explanation, and I would welcome a pointer to >> fuller documentation about “port select”. > > The new documentation system has a "port-select" manpage, but I'm not sure if > that has been released. > I agree that some of the select group entry names we've chosen are not optimal in the way in which they differ from the name of the port they provide. It might be a pain to fix that at this late date. >> >> Presumably you have hard-wired this connection between a select group entry >> name and some particular Apple binary. How do I find out which Apple binary? > > They're not really hardcoded. It's just that they've been out there for a > while, and presumably people are using them. > > The symlinks to be created are described in a *_select port's "base" file. > https://trac.macports.org/browser/trunk/dports/sysutils/python_select/files/base > > The *_select port itself can create select entries corresponding to the > system-provided installations. > https://trac.macports.org/browser/trunk/dports/sysutils/python_select/Portfile > > The paths to the system files are described in separate files. > https://trac.macports.org/browser/trunk/dports/sysutils/python_select/files > > vq You refer above to the “documentation system”. Could you be more explicit? Are you referring to something that is part of a MacPorts installation—if so, what is the file/directory name—or to an online document—if so what is the web address? I tried “man port-select” and got "No manual entry for port-select" I had a look at the trac documents you refer to, but I cannot understand them or their relevance to my question. They seem to be aimed at someone with more competence and understanding. David ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts missing links
> On 13 Sep 2016, at 03:19, Ryan Schmidtwrote: > > >> On Sep 12, 2016, at 9:08 PM, Brandon Allbery wrote: >> >> On Mon, Sep 12, 2016 at 9:59 PM, Ryan Schmidt >> wrote: >> What do you get when you run: >> port provides /opt/local/lib/libpng.la >> >> They actually provided that earlier: >> >>> /opt/local/lib/libpng.la is provided by: libpng > > David provided this information about his installation but Sinan didn't yet. > > But you know, not only should /opt/local/lib/libpng.la not exist on Mavericks > or later, it shouldn't be a symlink on any system; it should be a text file. > > If it's a symlink on your system, what's it a symlink to? Here is the story from my file system Macintosh-2:/<2>lib% pwd /opt/local/lib Macintosh-2:/<2>lib% ls -l libpng.la lrwxr-xr-x 1 root admin 11 6 Sep 10:13 libpng.la@ -> libpng16.la Macintosh-2:/<2>lib% port provides libpng.la /opt/local/lib/libpng.la is provided by: libpng Macintosh-2:/<2>lib% ls libpng* libpng.a@ libpng.la@ libpng16.a libpng.dylib@ libpng16.16.dylib* libpng16.dylib@ Macintosh-2:/<2>lib% ls -l libpng16.la ls: libpng16.la: No such file or directory Macintosh-2:/<2>lib% port installed libpng The following ports are currently installed: libpng @1.6.21_0 libpng @1.6.22_0 libpng @1.6.23_0 libpng @1.6.25_0 (active) This looks to me as though it is saying that Ryan was right. the .la file does not exist, only a shadow of it which presumably won’t cause any harm. One question: why the 6 Sept date. Would my uninstall of python have changed the date on the broken symlink? One thing that seems to be brought out (by the erroneous answer by “port provides ligpng.la") is that I made a mistake when updating the OS, to have updated my MacPorts installation, rather than reinstalled. I have been hankering after reinstalling, but Ryan persuaded me not to. This seems to be a new bit of evidence that I ought to reinstall, but I would like Ryan to confirm that he now agrees with this, in the light of the new evidence. David ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts missing links
In view of all my moans and groans, I would like to make it clear that I think MacPorts is great, and it adds greatly to my productivity. I use it all the time, and tend to regard it as “Just there and working perfectly” usually without thinking of the arduous contributions being made behind the scenes. I guess one only becomes aware of this when something isn’t quite right. This is rare with MacPorts, which means that it is even easier to take for granted. I really appreciate all the work that the designers and maintainers of the system do, and thank you for your labours. Sincere best wishes David ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts missing links
> On 11 Sep 2016, at 23:22, Ryan Schmidtwrote: > > On my system I see the contents of that directory are provided by the > following ports: > > $ port provides /opt/local/etc/select/python3/* > /opt/local/etc/select/python3/base is provided by: python3_select > /opt/local/etc/select/python3/none is provided by: python3_select > /opt/local/etc/select/python3/python33 is provided by: python33 > /opt/local/etc/select/python3/python34 is provided by: python34 > /opt/local/etc/select/python3/python35 is provided by: python35 > > What do you get if you run that "port provides" command? I get % port provides /opt/local/etc/select/python3/* /opt/local/etc/select/python3/current is not provided by a MacPorts port.] >> A final point, that I hope is not out-of-place. On my system >>> port select —list llvm >> >> responds with >>> Available versions for llvm: >>> mp-llvm-3.5 >>> none (active) >> and you have told me that “mp-llvm-3.5” is not the name of a port. > > That's correct. The name of the port is llvm-3.5. The name of its llvm select > group entry is mp-llvm-3.5. > >> I do not understand the issues involved and their ramifications, so I may be >> saying something stupid, but it seems to me, as a naive user, that this >> reveals a rather bad design fault in “port select”. An "available version" >> should either be “none” or the true name of an installed port. I realize >> that resources to fix things are scarce, but could the ability to choose a >> random name at least be acknowledged as bad practice, and could a ticket be >> provided for work to be done so that this behaviour becomes impossible? > > I think we don't consider this to be a design fault, but a feature. In other > words, it was not a mistake that the select group entry can differ from a > port; it was a deliberate decision to allow that. As has been pointed out, we > want to be able to select things that are part of macOS and are not provided > by a port. Yes, Brandon Allbery explained this in an email prior to this one of yours. I hadn’t at all realized the existence of this feature, which is clearly a good idea. > I agree that some of the select group entry names we've chosen are not > optimal in the way in which they differ from the name of the port they > provide. It might be a pain to fix that at this late date. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts missing links
Thanks very much for all your work on my issue: much appreciated. However, it’s looking like too much manual work, and also somewhat hazardous, at least to me as a non-expert. Moreover, I have no confidence that everything will be consistent, even if I successfully and correctly manually delete a number of symlinks, regular files and directories from /opt/local. Rather than spend more time on the problem, I will now move /opt/local to /opt/local.old and start again from scratch. It will be nice to have a clean installation that I don’t need to work on. I'm hoping that everything I need will install without error messages, but maybe that is overoptimistic. I will avoid using “port select” on my new installation, until I get the go-ahead that the problems have been researched and sorted. I’m not sure if I am allowed to put my name on some kind of cc list for the ticket, since I’m not intending to work on the problem, but only want to know when it has gone away. Possibly I misunderstand, but your earlier emails seem to imply that you feel that the only problem with “select” in MacPorts is the creation of symlinks that are not deleted when uninstalling. However, I do not believe this is the whole story. For example, my command > port installed ‘*python*3*’ was answered > “None of the specified ports is installed”. Nevertheless the directory /opt/local/etc/select/python3 remains on my system as useless clutter and there is no obvious way to delete it except manually, which ought to be a “No-no". This has nothing to do with symlinks. A final point, that I hope is not out-of-place. On my system > port select —list llvm responds with > Available versions for llvm: > mp-llvm-3.5 > none (active) and you have told me that “mp-llvm-3.5” is not the name of a port. I do not understand the issues involved and their ramifications, so I may be saying something stupid, but it seems to me, as a naive user, that this reveals a rather bad design fault in “port select”. An "available version" should either be “none” or the true name of an installed port. I realize that resources to fix things are scarce, but could the ability to choose a random name at least be acknowledged as bad practice, and could a ticket be provided for work to be done so that this behaviour becomes impossible? Best wishes David ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts missing links
On 11 Sep 2016, at 14:41, Lawrence Velázquez <lar...@macports.org> wrote: > >> On Sep 11, 2016, at 4:13 AM, David Epstein <david.epst...@warwick.ac.uk> >> wrote: >> >> For those few interested in this thread, and who have not followed so far, >> the relevant line of output from >> “port select —summary” was >>> llvm none mp-llvm-3.5 none >> >> I think that this is a either a bug in “port select —summary” or a >> misinterpretation of the output from >> “port select —summary”. >> >> In contrast, here is what “port installed” thinks: >>> port installed mp-livm-3.5 >> gives >>> None of the specified ports are installed. > > Port names and select entries need not match. The "mp-llvm-3.5" select entry > corresponds to the "llvm-3.5" port. > > vq Thanks for clearing up my misconception/misinterpretation of the output from “port select —summary”. Is there a port command that would have given me this information? David ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts missing links
livm was my error due to poor eyesight. It should have been llvm all the time. > On 11 Sep 2016, at 14:55, Sinan Karasu <si...@bozuk.org> wrote: > > I don’t get the correspondence between “llvm” and “livm” in your posts. Is it > a typo, or are there really two different ports? > >> On Sep 11, 2016, at 1:13 AM, David Epstein <david.epst...@warwick.ac.uk> >> wrote: >> >>> livm > ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts missing links
I hope that I’m believed when I say that I’m extremely careful never to operate on /opt/local except via port. I do use programs like unix find and unix ls that are not supposed to change anything. Trying to demistify the line from the output of “port select —summary” > llvm none mp-llvm-3.5 none I did the following > sudo find /opt/local/ -type f -exec egrep -l llvm {} \; -print | egrep select > | tee llvm and found the following files > /opt/local//etc/select/llvm/base > /opt/local//etc/select/llvm/mp-llvm-3.5 > /opt/local//var/macports/registry/portfiles/gcc_select-0.1_8/402c19e245d305006c81d326c0b60409d53996d6b33cd8b23ff9e19d473410ff-1587/Portfile > /opt/local//var/macports/registry/portfiles/llvm_select-1.0_0/d46f373920a0c44fe0fa99cfec9bd161b316451d185d5ac62ed2a86da86a748e-733/Portfile > /opt/local//var/macports/registry/portfiles/llvm_select-2_0/1843b74f59af89e60f61d519191491ca9a751228d95f1379b167336de9b6ba4e-731/Portfile > /opt/local//var/macports/sources/rsync.macports.org/release/ports/multimedia/HandBrake/files/0011-MP-libav-Respect-our-compiler-selection-on-Darwin-i3.patch > /opt/local//var/macports/sources/rsync.macports.org/release/ports/sysutils/gcc_select/files/llvm-gcc42 > /opt/local//var/macports/sources/rsync.macports.org/release/ports/sysutils/gcc_select/Portfile > /opt/local//var/macports/sources/rsync.macports.org/release/ports/sysutils/llvm_select/files/base > /opt/local//var/macports/sources/rsync.macports.org/release/ports/sysutils/llvm_select/Portfile Whether that would help debug the erroneous behaviour of “port select —summary” or not, I leave in the hands of more knowledgeable and competent MacPorters. I can either live with this lack of consistency in my /opt/local files or I can erase /opt/local and start again, or maybe there is a third choice. I would welcome advice from the list. Best wishes David Epstein ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts missing links
> On 10 Sep 2016, at 23:05, Brandon Allbery <allber...@gmail.com> wrote: …snip... > "port select --summary" reports as "none" in that case because the file > describing the previously selected option was removed and therefore is not a > valid setting. More to the point, if the options do not include a > MacPorts-installed one, then you can safely assume you do not have any > related port installed. For reference, your summary reports only one setting > for which a MacPorts port is installed: llvm 3.5 (mp-llvm-3.5) for llvm. For those few interested in this thread, and who have not followed so far, the relevant line of output from “port select —summary” was > llvm none mp-llvm-3.5 none I think that this is a either a bug in “port select —summary” or a misinterpretation of the output from “port select —summary”. In contrast, here is what “port installed” thinks: > port installed mp-livm-3.5 gives > None of the specified ports are installed. I checked with unix: > sudo find /opt/local -name "*livm*" -print gave a null response, so this isn’t even a broken symlink If I was more confident, I would submit a bug report. If someone else feels like doing this, I can cooperate by running other commands on my system and reporting the results to the “someone else”. David Epstein ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts missing links
> On 10 Sep 2016, at 23:10, Lawrence Velázquez <lar...@macports.org> wrote: … snip … >>> Did you uninstall python27? >> >> I think so. The ls -l command above does not find /opt/local/bin/python*, >> except for symbolic links. >> What port command could I give to make sure? > > "port installed python27 and active” Confusingly this gets an answer that is readily misinterpreted, namely > None of the specified ports are installed. In contrast > port installed python27 does not (inadvertently) deceive: it gives > The following ports are currently installed: > python27 @2.7.11_2 …snip… >> I ran “port select —summary” as you suggested and got the response >> >> Name Selected Options >> === >> cython none none >> gccnone none >> ipythonnone none >> ipython2 none none >> ipython3 none none >> llvm none mp-llvm-3.5 none >> nosetests none none >> pipnone none >> python none python26-apple python27-apple none >> python2none python26-apple python27-apple none >> python3none none …snip… > What you could try is explicitly setting and then unsetting: > > sudo port select --set python python27-apple I tried this and got: > Selecting 'python27-apple' for 'python' failed: symlink: > /opt/local/etc/select/python/current -> python27-apple: file already exists So then I did > ls -l /opt/local/etc/select/python/current and got > lrwxr-xr-x 1 root admin 8 9 Jun 19:13 > /opt/local/etc/select/python/current@ -> python27 This seems to me to indicate a bug in “port select —summary”. Firstly, it seems to answer incorrectly for inactive ports, like python27 in my case. I would have expected “port select —summary” to give python27 as an option. Secondly, it seems to incorrectly and indirectly imply that python26-apple and python27-apple are installed, which I think was your interpretation, but they aren’t installed, as I have checked with the “port installed” command. It does feel as though I will, with the help of the list, be able to clean up my ports: I had been thinking that I would have to delete everything in /opt/local and start again. David Epstein ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts missing links
> On 10 Sep 2016, at 23:13, Lawrence Velázquezwrote: > … snip … > Run this: > > find -L /opt/local -type l > > This will print any broken symlinks in your MacPorts prefix. Email the output > to this list, and we can tell you what you can safely delete. > > vq I ran the suggested find command and double checked that all the entries are broken symlinks. Ideally I would like to get rid of all of them, but safely. From my point of view, the danger is that these filenames occur in some different list in /opt/local, unknown to me, and that this list would be corrupted if I simply delete the broken symlinks using /bin/rm . /opt/local/bin/2to3 /opt/local/bin/2to3-3 /opt/local/bin/idle /opt/local/bin/idle3 /opt/local/bin/iptest /opt/local/bin/iptest2 /opt/local/bin/ipython /opt/local/bin/ipython2 /opt/local/bin/pip /opt/local/bin/pydoc /opt/local/bin/pydoc3 /opt/local/bin/python /opt/local/bin/python-config /opt/local/bin/python3 /opt/local/bin/python3-config /opt/local/bin/python3m /opt/local/bin/python3m-config /opt/local/bin/pythonw /opt/local/bin/pyvenv /opt/local/bin/smtpd.py /opt/local/etc/select/ipython/current /opt/local/etc/select/ipython2/current /opt/local/etc/select/pip/current /opt/local/etc/select/python/current /opt/local/etc/select/python3/current /opt/local/lib/libpng.la /opt/local/libexec/qt4/include/QtCLucene /opt/local/libexec/qt4/include/QtDesignerComponents /opt/local/libexec/qt4/Library/Frameworks/QtCLucene.framework/Headers /opt/local/Library/Frameworks/Python.framework/Headers /opt/local/Library/Frameworks/Python.framework/Python /opt/local/Library/Frameworks/Python.framework/Resources /opt/local/Library/Frameworks/Python.framework/Versions/Current /opt/local/man/man1/ipython.1 /opt/local/man/man1/ipython2.1 /opt/local/man/man1/python.1 /opt/local/man/man1/python3.1 /opt/local/share/man/man1/ipython.1 /opt/local/share/man/man1/ipython2.1 /opt/local/share/man/man1/python.1 /opt/local/share/man/man1/python3.1 ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts missing links
Thanks for your help: > On 10 Sep 2016, at 19:38, Lawrence Velázquez <lar...@macports.org> wrote: > >> On Sep 10, 2016, at 1:42 PM, David Epstein <david.epst...@warwick.ac.uk> >> wrote: >> >> I gave the command: >> >> ls -l /opt/local/bin/py* >> and the system replied: >> >>> lrwxr-xr-x 1 root wheel 23 9 Jun 19:13 /opt/local/bin/pydoc@ -> >>> /opt/local/bin/pydoc2.7 >>> lrwxr-xr-x 1 root wheel 23 9 Jun 17:19 /opt/local/bin/pydoc3@ -> >>> /opt/local/bin/pydoc3.5 >>> lrwxr-xr-x 1 root wheel 24 9 Jun 19:13 /opt/local/bin/python@ -> >>> /opt/local/bin/python2.7 >>> lrwxr-xr-x 1 root wheel 31 9 Jun 19:13 /opt/local/bin/python-config@ -> >>> /opt/local/bin/python2.7-config >>> lrwxr-xr-x 1 root wheel 24 9 Jun 17:19 /opt/local/bin/python3@ -> >>> /opt/local/bin/python3.5 >>> lrwxr-xr-x 1 root wheel 31 9 Jun 17:19 /opt/local/bin/python3-config@ >>> -> /opt/local/bin/python3.5-config >>> lrwxr-xr-x 1 root wheel 25 9 Jun 17:19 /opt/local/bin/python3m@ -> >>> /opt/local/bin/python3.5m >>> lrwxr-xr-x 1 root wheel 32 9 Jun 17:19 /opt/local/bin/python3m-config@ >>> -> /opt/local/bin/python3.5m-config >>> lrwxr-xr-x 1 root wheel 25 9 Jun 19:13 /opt/local/bin/pythonw@ -> >>> /opt/local/bin/pythonw2.7 >>> lrwxr-xr-x 1 root wheel 25 9 Jun 17:19 /opt/local/bin/pyvenv@ -> >>> /opt/local/bin/pyvenv-3.5 > > Those are symlinks created by "port select". Presumably you set up the > python, python2, and python3 select groups at some point. > >> You will see that none of the files on the righthand side of the arrow -> >> appears on any lefthand side. I tried “port provides” on both lefthand and >> righthand sides and received error messages from port such as >>> /opt/local/bin/pydoc2.7 does not exist. > > Did you uninstall python27? I think so. The ls -l command above does not find /opt/local/bin/python*, except for symbolic links. What port command could I give to make sure? What port command can I give to extirpate remnants of an uninstalled port, if there are any remnants? >> and >>> /opt/local/bin/pydoc is not provided by a MacPorts port. > > Right, because that file was created by "port select" and not a port. > >> How do I get rid of the symbolic links, other than using /bin/rm, something >> I have been told never to do? >> >> How can I find all hanging links like this in /opt? Presumably there is a >> clever formula using unix find. > > Try running "port select --summary" (although I'm not sure whether this > feature has been released). It will list the select groups on your system and > their current settings. If any of those settings corresponds to a port you > have uninstalled, you should be able to remove the symlinks with I ran “port select —summary” as you suggested and got the response Name Selected Options === cython none none gccnone none ipythonnone none ipython2 none none ipython3 none none llvm none mp-llvm-3.5 none nosetests none none pipnone none python none python26-apple python27-apple none python2none python26-apple python27-apple none python3none none I do not want to rely on my memory of which of these I have uninstalled. I need to be told by a reliable program. What would happen if I gave one of your commands below, with argument a port that was still installed? Since I do not yet know the answer to that question, I will refrain for the moment from issuing any of these commands. My guess is that only the symbolic link would be removed, leaving the true file in place, but I would like to be sure before I take any action. > sudo port select --set python none > sudo port select --set python2 none > sudo port select --set python3 none > etc etc etc > >> I wonder what causes this kind of problem? I cannot remember any of my port >> processes terminating incorrectly. I have lately been uninstalling >> python-related ports, because I had too many different versions of python on >> my machine, and I was getting confused. > > The symlinks created by "port select" are not modified if the selected port > is subsequently deactivated or uninstalled. I think there is an open ticket > about this, but I can't find it at the moment. > > vq ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
MacPorts missing links
I gave the command: ls -l /opt/local/bin/py* and the system replied: > lrwxr-xr-x 1 root wheel 23 9 Jun 19:13 /opt/local/bin/pydoc@ -> > /opt/local/bin/pydoc2.7 > lrwxr-xr-x 1 root wheel 23 9 Jun 17:19 /opt/local/bin/pydoc3@ -> > /opt/local/bin/pydoc3.5 > lrwxr-xr-x 1 root wheel 24 9 Jun 19:13 /opt/local/bin/python@ -> > /opt/local/bin/python2.7 > lrwxr-xr-x 1 root wheel 31 9 Jun 19:13 /opt/local/bin/python-config@ -> > /opt/local/bin/python2.7-config > lrwxr-xr-x 1 root wheel 24 9 Jun 17:19 /opt/local/bin/python3@ -> > /opt/local/bin/python3.5 > lrwxr-xr-x 1 root wheel 31 9 Jun 17:19 /opt/local/bin/python3-config@ -> > /opt/local/bin/python3.5-config > lrwxr-xr-x 1 root wheel 25 9 Jun 17:19 /opt/local/bin/python3m@ -> > /opt/local/bin/python3.5m > lrwxr-xr-x 1 root wheel 32 9 Jun 17:19 /opt/local/bin/python3m-config@ -> > /opt/local/bin/python3.5m-config > lrwxr-xr-x 1 root wheel 25 9 Jun 19:13 /opt/local/bin/pythonw@ -> > /opt/local/bin/pythonw2.7 > lrwxr-xr-x 1 root wheel 25 9 Jun 17:19 /opt/local/bin/pyvenv@ -> > /opt/local/bin/pyvenv-3.5 You will see that none of the files on the righthand side of the arrow -> appears on any lefthand side. I tried “port provides” on both lefthand and righthand sides and received error messages from port such as > /opt/local/bin/pydoc2.7 does not exist. and > /opt/local/bin/pydoc is not provided by a MacPorts port. How do I get rid of the symbolic links, other than using /bin/rm, something I have been told never to do? How can I find all hanging links like this in /opt? Presumably there is a clever formula using unix find. I wonder what causes this kind of problem? I cannot remember any of my port processes terminating incorrectly. I have lately been uninstalling python-related ports, because I had too many different versions of python on my machine, and I was getting confused. David Epstein ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
uninstalling gimp
It took me a long time to uninstall gimp. I tried port list gimp and got the reply gimp @2.8.14 graphics/gimp Was I supposed to realise from this reply that I needed to give the command sudo port uninstall gimp2 ?? I initially tried sudo port uninstall gimp and the command completed without comment or response. Is this difficulty special to gimp, or is there some MacPorts convention or rule that I don’t know about? Thanks David Epstein ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
problem with selfupdate
Here is the response I had to sudo port -v selfupdate --- Updating MacPorts base sources using rsync rsync: failed to connect to rsync.macports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-42/rsync/clientserver.c(105) [receiver=2.6.9] Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs Exit code: 10 Error: Error synchronizing MacPorts sources: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed One possible explanation that occurs to me is that I am connecting to the Internet from behind some kind of firewall. However, that is just wild conjecture. But it is true that I’m not at the usual place from where I have in the past successfully run selfupdate without a problem. Maybe someone more knowledgeable than I am can say what they think, and let me know if there is a workaround. Thanks David Epstein ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
request change in macports documentation about downloading xcode.
Could the advice about downloading Xcode please be slightly improved? I spent a few hours last night battling to get Macports reinstalled last night, with continual errors. I restarted the process from scratch at least 2 times. Finally I started writing to this forum about my woes, and decided I needed to tell people which version of xcode I was using. It was only at that point that I realized that, although I had downloaded the latest version of Xcode, as instructed, nevertheless it needed Xcode to be launched before it would work correctly. (Apple was requiring some modification of Xcode before launching xcode and needed admin permission to do so.) Magic—all errors previously reported by macports went away. Could you add to the Macports instructions that Xcode should be launched at least once before doing anything within Macports itself? Thanks. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: request change in macports documentation about downloading xcode.
I’m using Xcode 5.1.1 (5B1008) on OSX 10.9.2. Yes, you are right: I carelessly ignored the instruction to run xcode-select —install”, thereby giving myself unnecessary grief. On 25 Apr 2014, at 10:42, Ryan Schmidt ryandes...@macports.org wrote: On Apr 25, 2014, at 04:39, David Epstein wrote: Could the advice about downloading Xcode please be slightly improved? I spent a few hours last night battling to get Macports reinstalled last night, with continual errors. I restarted the process from scratch at least 2 times. Finally I started writing to this forum about my woes, and decided I needed to tell people which version of xcode I was using. It was only at that point that I realized that, although I had downloaded the latest version of Xcode, as instructed, nevertheless it needed Xcode to be launched before it would work correctly. (Apple was requiring some modification of Xcode before launching xcode and needed admin permission to do so.) Magic—all errors previously reported by macports went away. Could you add to the Macports instructions that Xcode should be launched at least once before doing anything within Macports itself? Xcode varies greatly by version. Which version are you using, on which OS X version? “New” versions of Xcode (starting some time during Lion, IIRC) require accepting the license agreement before the command line tools will work. Launching Xcode would prompt you to do that, but you can also do it at the command line, which is what our instructions show. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: webkit error
On 4 Dec 2013, at 12:06, Ryan Schmidt ryandes...@macports.org wrote: On Dec 4, 2013, at 05:16, David Epstein wrote: I'm using MacOsX 10.8.5 with Macports base version 2.2.1. There seem to be tickets related to webkit-gtk, but I'm too ignorant to understand whether they are saying anything relevant to me. On giving the command sudo port upgrade outdated first a whole lot of installation and upgrading was done. At the end I got the following error message:. Error: webkit-gtk is not supported for this installation of MacPorts. It requires libc++ be selected as your C++ runtime. Please use webkit-gtk-2.0 instead Error: org.macports.configure for port webkit-gtk returned: unsupported configuration Please see the log file for port webkit-gtk for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_webkit-gtk/webkit-gtk/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets I then tried the following command sudo port install webkit-gtk-2.0 and got --- Computing dependencies for webkit-gtk-2.0 Error: Unable to execute port: Can't install webkit-gtk-2.0 because conflicting ports are installed: webkit-gtk I don't use any of this, but presumably programs, that I do use, need these packages. Presumably. Let’s find out for sure. What’s the output of: port installed depends:webkit-gtk I get H2:~% port installed depends webkit-gtk The following ports are currently installed: webkit-gtk @2.0.4_1+video (active) Does this mean that I have no other ports that depend on webkit-gtk? Maybe I installed a port X that needed webkit-gtk at the time of installation, but an upgraded version of X no longer needs webkit-gtk. I am very about what I install, and normally only install programs that I actually need and use. Maybe webkit-gtk-2.0 is sufficient for those ports. Should I ignore these error messages, or try to do something about them? You cannot ignore these errors; you must resolve the problem. What is libc++ and what is C++ runtime? A C++ runtime is a library that programs that were written in C++ use. libc++ is the default C++ runtime on Mavericks and later, and libstdc++ is the default on Mountain Lion and earlier. Thanks for the explanation. Should I select libc++ as my C++ runtime”? Probably not. How do I do this? Install MacPorts base from trunk and edit the relevant setting in macports.conf. I don’t recommend this. Would other programs continue to work if I did this? You would have to uninstall and reinstall all ports, and hope that none of them use any of the operating system’s C++ libraries. I don’t recommend this. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: webkit error
On 4 Dec 2013, at 13:08, Ryan Schmidt ryandes...@macports.org wrote: On Dec 4, 2013, at 06:48, David Epstein wrote: On 4 Dec 2013, at 12:06, Ryan Schmidt wrote: On Dec 4, 2013, at 05:16, David Epstein wrote: I don't use any of this, but presumably programs, that I do use, need these packages. Presumably. Let’s find out for sure. What’s the output of: port installed depends:webkit-gtk I get H2:~% port installed depends webkit-gtk The following ports are currently installed: webkit-gtk @2.0.4_1+video (active) No: port installed depends:webkit-gtk Sorry: now I get H2:~% port installed depends:webkit-gtk The following ports are currently installed: gimp2 @2.8.6_3+help_browser+python27 gimp2 @2.8.8_0+help_browser+python27 gimp2 @2.8.10_0+help_browser+python27 (active) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: webkit error
On 4 Dec 2013, at 14:31, Ryan Schmidt ryandes...@macports.org wrote: On Dec 4, 2013, at 08:02, David Epstein wrote: On 4 Dec 2013, at 13:08, Ryan Schmidt wrote: On Dec 4, 2013, at 06:48, David Epstein wrote: On 4 Dec 2013, at 12:06, Ryan Schmidt wrote: On Dec 4, 2013, at 05:16, David Epstein wrote: I don't use any of this, but presumably programs, that I do use, need these packages. Presumably. Let’s find out for sure. What’s the output of: port installed depends:webkit-gtk I get H2:~% port installed depends webkit-gtk The following ports are currently installed: webkit-gtk @2.0.4_1+video (active) No: port installed depends:webkit-gtk Sorry: now I get H2:~% port installed depends:webkit-gtk The following ports are currently installed: gimp2 @2.8.6_3+help_browser+python27 gimp2 @2.8.8_0+help_browser+python27 gimp2 @2.8.10_0+help_browser+python27 (active) Ok, so gimp2 is the only port you have installed that needs webkit-gtk. From “port -v deps gimp2” I see that it does not have a hard dependency on “port:webkit-gtk”, but rather on “path:lib/pkgconfig/webkit-1.0.pc:webkit-gtk”, which webkit-gtk-2.0 can also satisfy. So the solution is: sudo port -f deactivate webkit-gtk sudo port install webkit-gtk-2.0 thanks a lot. That worked fine. Then I did the following sudo port -vy upgrade outdated Password: --- Computing dependencies for gimp2. For gimp2: skipping org.macports.main (dry run) .. and skipping org.macports.archivefetch .. and skipping org.macports.fetch .. and skipping org.macports.checksum .. and skipping org.macports.extract .. and skipping org.macports.patch .. and skipping org.macports.configure .. and skipping org.macports.build .. and skipping org.macports.destroot .. and skipping org.macports.install .. and skipping org.macports.main .. and skipping org.macports.clean Skipping deactivate gimp2 @2.8.10_0+help_browser+python27 (dry run) Skipping activate gimp2 @2.8.10_1+help_browser+python27 (dry run) So, should I run sudo port upgrade outdated? I tried port search gimp2@2.8.10_0+help_browser+python27 and got the report No match, which puzzles me. Why is it wanting to deactivate a port that isn't there? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
rmtrash
Here is a record of what I typed and the response H2:~% port search rmtrash rmtrash @0.3.3_2 (sysutils) move the file to OS X's Trash H2:~% sudo port install sysutils Error: Port sysutils not found Can someone enlighten me on what the situation is with rmtrash? The above two port commands seem to contradict each other, or am I misinterpreting? Thanks David ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Errors building gcc44 under MacOsX
Ryan Schmidt-24 wrote: The fact that you clearly have a 64-bit Mac, and that zlib was nevertheless installed 32-bit, and on MacPorts 1.8 or earlier, suggests zlib was in fact installed a long time ago, when you were running Leopard or earlier, perhaps on a previous machine whose disk was migrated to this one, or restored to this one from a backup, and that you did not subsequently successfully uninstall your old ports and rebuild them. At least not zlib. But I would be surprised if zlib were the only port affected. Right, as usual, Ryan. I had expunged from my mind a certain painful experience that entailed restoring from a backup. Thanks for the help. -- View this message in context: http://old.nabble.com/Errors-building-gcc44-under-MacOsX-tp32395987p32401450.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Errors building gcc44 under MacOsX
I run MacOsX 10.6.8 on a MacBook Pro. The System Profiler says: Model Name: MacBook Pro Model Identifier: MacBookPro8,2 Processor Name: Intel Core i7 Processor Speed: 2.2 GHz Number of Processors: 1 Total Number of Cores:4 L2 Cache (per Core): 256 KB L3 Cache: 6 MB Memory: 8 GB Boot ROM Version: MBP81.0047.B0E SMC Version (system): 1.69f1 Serial Number (system): C02FP475DF91 Hardware UUID:6DA5EF38-F18A-5578-80DD-396EAB563725 Here is the error message from port: sudo port install gcc44 --- Computing dependencies for gcc44 --- Fetching archive for gcc44 --- Attempting to fetch gcc44-4.4.6_0.darwin_10.x86_64.tgz from http://packages.macports.org/gcc44 --- Fetching gcc44 --- Verifying checksum(s) for gcc44 --- Extracting gcc44 --- Configuring gcc44 --- Building gcc44 Error: Target org.macports.build returned: shell command failed (see log for details) Log for gcc44 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc44/gcc44/main.log Error: Status 1 encountered during processing. To report a bug, see http://guide.macports.org/#project.tickets I was actually trying to install octave under macports. This called for gcc44, and then it stumbled. Maybe I should install it some other way. Thanks for any help. David Epstein Here are the last lines of the main.log file referred to in the error message. I hope this includes everything of importance. I tried to upload the whole of main.log to Nabble, but Nabble said it was too big. Also, I wasn't sure whether uploading to Nabble was the right thing to do: :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc44/gcc44/work/build/./prev-gcc/xgcc -B/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc44/gcc44/work/build/./prev-gcc/ -B/opt/local/x86_64-apple-darwin10/bin/ -O2 -g -D_FORTIFY_SOURCE=0 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual -Wold-style-definition -Wc++-compat -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -o jcf-dump java/jcf-dump.o java/jcf-io.o java/jcf-depend.o java/jcf-path.o java/win32-host.o java/zextract.o errors.o version.o ggc-none.o intl.o \ :info:build -lz ../libcpp/libcpp.a -liconv ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a :info:build ld: warning: ignoring file /opt/local/lib/libz.dylib, file was built for unsupported file format which is not the architecture being linked (x86_64) :info:build Undefined symbols for architecture x86_64: :info:build _inflateInit2_, referenced from: :info:build _read_zip_member in jcf-io.o :info:build _inflate, referenced from: :info:build _read_zip_member in jcf-io.o :info:build _inflateEnd, referenced from: :info:build _read_zip_member in jcf-io.o :info:build ld: symbol(s) not found for architecture x86_64 :info:build collect2: ld returned 1 exit status :info:build make[3]: *** [jcf-dump] Error 1 :info:build make[3]: *** Waiting for unfinished jobs :info:build /usr/bin/ranlib: file: libbackend.a(insn-peep.o) has no symbols :info:build /usr/bin/ranlib: file: libbackend.a(loop-doloop.o) has no symbols :info:build /usr/bin/ranlib: file: libbackend.a(vmsdbgout.o) has no symbols :info:build /usr/bin/ranlib: file: libbackend.a(xcoffout.o) has no symbols :info:build ranlib -c libbackend.a :info:build ranlib: file: libbackend.a(insn-peep.o) has no symbols :info:build ranlib: file: libbackend.a(loop-doloop.o) has no symbols :info:build ranlib: file: libbackend.a(vmsdbgout.o) has no symbols :info:build ranlib: file: libbackend.a(xcoffout.o) has no symbols :info:build rm gfortran.pod gcc.pod :info:build make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc44/gcc44/work/build/gcc' :info:build make[2]: *** [all-stage2-gcc] Error 2 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc44/gcc44/work/build' :info:build make[1]: *** [stage2-bubble] Error 2 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc44/gcc44/work/build' :info:build make: *** [bootstrap] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc44/gcc44/work/build' :info:build shell command cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc44/gcc44/work/build /usr/bin/make -j8 -w bootstrap BOOT_CFLAGS=-O2 -g -D_FORTIFY_SOURCE=0 STAGE1_CFLAGS=-O2 -fkeep-inline-functions -D_FORTIFY_SOURCE=0 -std=gnu89 returned error 2 :error:build
Re: Errors building gcc44 under MacOsX
Brandon Allbery wrote: On Sun, Sep 4, 2011 at 10:00, David Epstein david.epst...@warwick.ac.ukwrote: :info:build ld: warning: ignoring file /opt/local/lib/libz.dylib, file was built for unsupported file format which is not the architecture being linked (x86_64) This is the key error. Check the zlib port; is it installed for x86-64? thanks for your help, but I'm out of my depth. Can I be sure that my chip is indeed x86-64? How can I check the zlib port? I did port info zlib and got zlib @1.2.5 (archivers) Variants: universal Description: zlib is designed to be a free, general-purpose, legally unencumbered, lossless data-compression library for use on virtually any computer hardware and operating system. Homepage: http://www.zlib.net/ Platforms:darwin, freebsd License: zlib Maintainers: land...@macports.org, ryandes...@macports.org, openmaintai...@macports.org Is this the only version of zlib available on MacPorts? How can I get hold of a version of zlib that will work with my chip's instruction set? Thanks David -- View this message in context: http://old.nabble.com/Errors-building-gcc44-under-MacOsX-tp32395987p32397394.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Errors building gcc44 under MacOsX
Jeremy Lavergne wrote: How can I check the zlib port? This will tell you more about the zlib you have installed, including architecture: port -v installed zlib I get only The following ports are currently installed: zlib @1.2.5_0 (active) which is less information than I get from port info zlib Neither command tells me anything about x86-64. -- View this message in context: http://old.nabble.com/Errors-building-gcc44-under-MacOsX-tp32395987p32397449.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Errors building gcc44 under MacOsX
Jeremy Lavergne wrote: You must be running an old version of MacPorts then. Have you considered updating it `port selfupdate`? I get: $ port -v installed zlib The following ports are currently installed: zlib @1.2.5_0 (active) platform='darwin 10' archs='x86_64' That's an interesting difference, and does seem to reflect a difference in 'port'. I have indeed run 'sudo port selfupdate' today. It says I am running version 2.0.2. Is that what you are running? I also did 'sudo port upgrade outdated'. When I installed Mac Os X 10.6, I did, as recommended, restart MacPorts from nothing, but maybe something has gone mysteriously wrong despite my care. I hope I won't have to delete everything and start again. It takes so long to rebuild everything. I tried to uninstall zlib, wanting to reinstall it, but there are a lot of ports that depend on zlib, so it refused to uninstall. Should I use -f on zlib or will that make everything break? -- View this message in context: http://old.nabble.com/Errors-building-gcc44-under-MacOsX-tp32395987p32397518.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
stat
Is there a gnu version of stat? I have a version of stat on my Mac, provided I suppose by Apple, in /usr/local/bin/stat, but I wanted a version that would have a good chance of being available on Linux platforms. I thought that a Macports version would most likely be a gnu version, if it exists. I tried looking for stat in this newsgroup, but there didn't seem to be anything appropriate. I also tried port search stat and got lots of irrelevant hits. Is there a better way of searching? Thanks David -- View this message in context: http://old.nabble.com/stat-tp31486375p31486375.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
gfmt and editing of system files
I just installed Leopard (was on Tiger). Then I did sudo port selfupdate which succeeded. I also did some cleaning up, in the course of which I lost gfmt that I use all the time. Q1. The puzzle for me is: how do I find out which port in Macports contains gfmt? Q2. Which system files am I supposed to edit at this point? For example 'man port' no longer finds 'port', so I suppose the search path for man is not including /opt/local/man Q3. Is there an info file for port? I can't find any. Thanks David Epstein ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
restore_ports.tcl
Having recently upgraded from MacOsX 10.4.11 to 10.5.8, and run into trouble with updating my MacPorts installation, Ryan Schmidt kindly pointed me to the web page http://trac.macports.org/wiki/Migration This all worked fine, and the script restore_ports.tcl, available on that page, worked without complaint. Thank you everyone. I did however wonder what was the reasoning behind leaving an apparently random selection of the ports in an inactive state. The output from the script shows that some ports are first activated and then, immediately afterwards, deactivated. David -- View this message in context: http://old.nabble.com/restore_ports.tcl-tp28664574p28664574.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
xorg-libice
I have just installed Leopard 10.5.8, and then I did sudo port upgrade outdated. This ran into an error on xorg-libice, and so I ran sudo port clean --all xorg-libice, followed by sudo port -d upgrade xorg-libice, with the following result: Hottie:~% sudo port clean --all xorg-libice --- Cleaning xorg-libice Hottie:~% sudo port -d upgrade xorg-libice | tee ~/tmp/portlibice DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/xorg-libice DEBUG: epoch: in tree: 0 installed: 0 DEBUG: xorg-libice 1.0.6_0 exists in the ports tree DEBUG: xorg-libice 1.0.4_0 is the latest installed DEBUG: xorg-libice 1.0.4_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/xorg-libice DEBUG: OS Platform: darwin DEBUG: OS Version: 9.8.0 DEBUG: Mac OS X Version: 10.5 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Requested variant darwin is not provided by port xorg-libice. DEBUG: Requested variant i386 is not provided by port xorg-libice. DEBUG: Requested variant macosx is not provided by port xorg-libice. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/pkgconfig DEBUG: epoch: in tree: 0 installed: 0 DEBUG: pkgconfig 0.23_1 exists in the ports tree DEBUG: pkgconfig 0.23_1 is the latest installed DEBUG: pkgconfig 0.23_1 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/pkgconfig DEBUG: OS Platform: darwin DEBUG: OS Version: 9.8.0 DEBUG: Mac OS X Version: 10.5 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Requested variant darwin is not provided by port pkgconfig. DEBUG: Requested variant i386 is not provided by port pkgconfig. DEBUG: Requested variant macosx is not provided by port pkgconfig. DEBUG: No need to upgrade! pkgconfig 0.23_1 = pkgconfig 0.23_1 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/xorg-xtrans DEBUG: epoch: in tree: 0 installed: 0 DEBUG: xorg-xtrans 1.2.5_0 exists in the ports tree DEBUG: xorg-xtrans 1.2.5_0 is the latest installed DEBUG: xorg-xtrans 1.2.5_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/xorg-xtrans DEBUG: OS Platform: darwin DEBUG: OS Version: 9.8.0 DEBUG: Mac OS X Version: 10.5 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: 'universal_variant no' specified, so not adding the default universal variant DEBUG: Requested variant darwin is not provided by port xorg-xtrans. DEBUG: Requested variant i386 is not provided by port xorg-xtrans. DEBUG: Requested variant macosx is not provided by port xorg-xtrans. DEBUG: No need to upgrade! xorg-xtrans 1.2.5_0 = xorg-xtrans 1.2.5_0 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/xorg-xproto DEBUG: epoch: in tree: 0 installed: 0 DEBUG: xorg-xproto 7.0.16_0 exists in the ports tree DEBUG: xorg-xproto 7.0.16_0 is the latest installed DEBUG: xorg-xproto 7.0.16_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/xorg-xproto DEBUG: OS Platform: darwin DEBUG: OS Version: 9.8.0 DEBUG: Mac OS X Version: 10.5 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure.
syntax for uninstalling. Can I use a regex?
1. What is the syntax for finding all installed ports whose name contains tex? Will this include both active and inactive ports? I tried port search installed tex, but I think it treated both installed and tex as search strings. 2. How do I uninstall a whole lot of ports simultaneously? And does uninstall include removing all the associated bits and pieces, like the dist files? When I try sudo port uninstall texlive, the system replies Error: port uninstall failed: Registry error: texlive not registered as installed. Nevertheless there are huge numbers of files in /opt/local with texlive as part of the path name. What is the procedure for finding out the names involving texlive which ARE registered as installed? Once I know that, I want to find out how to use a regex to uninstall all of them simultaneously. Thanks for any help. David -- View this message in context: http://old.nabble.com/syntax-for-uninstalling.-Can-I-use-a-regex--tp27735428p27735428.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: syntax for uninstalling. Can I use a regex?
Brandon Allbery wrote: May I suggest reading man port in a terminal window? Thanks a lot for the patient replies from Joshua and Brandon. I did in fact spend quite a lot of time studying man port before writing to the forum. I'm sure the manual page is very clear to anyone who already knows most of the commands. The replies have been a big help, but it seems that I'm still not 100% through the thicket. I am in /opt/local and here is what happened. Are the files or directories listed supposed to remain permanently in my file system? sudo port clean --all name:texlive Password: --- Cleaning texlive --- Cleaning texlive_base --- Cleaning texlive_texmf-docs --- Cleaning texlive_texmf-full --- Cleaning texlive_texmf-minimal Tottie:/1local% find . -name *texlive* -print ./var/macports/receipts/texlive_texmf-minimal ./var/macports/software/texlive_texmf-minimal ./var/macports/sources/rsync.macports.org/release/ports/tex/texlive ./var/macports/sources/rsync.macports.org/release/ports/tex/texlive_base ./var/macports/sources/rsync.macports.org/release/ports/tex/texlive_base/files/patch-texk_texlive_Makefile_in ./var/macports/sources/rsync.macports.org/release/ports/tex/texlive_texmf-docs ./var/macports/sources/rsync.macports.org/release/ports/tex/texlive_texmf-full ./var/macports/sources/rsync.macports.org/release/ports/tex/texlive_texmf-minimal Tottie:/1local% port installed texlive None of the specified ports are installed. I would be very grateful for further comments. David -- View this message in context: http://old.nabble.com/syntax-for-uninstalling.-Can-I-use-a-regex--tp27735428p27735876.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: syntax for uninstalling. Can I use a regex?
Here's what I get: Tottie:/1local% port installed texlive* The following ports are currently installed: texlive_texmf-minimal @2007_2 (active) Tottie:/1local% sudo port uninstall *texlive_texmf-minimal* Password: --- Deactivating texlive_texmf-minimal @2007_2 --- Uninstalling texlive_texmf-minimal @2007_2 Tottie:/1local% sudo port clean --all name:texlive Password: --- Cleaning texlive --- Cleaning texlive_base --- Cleaning texlive_texmf-docs --- Cleaning texlive_texmf-full --- Cleaning texlive_texmf-minimal Tottie:/1local% !find find . -name *texlive* -print ./var/macports/sources/rsync.macports.org/release/ports/tex/texlive ./var/macports/sources/rsync.macports.org/release/ports/tex/texlive_base ./var/macports/sources/rsync.macports.org/release/ports/tex/texlive_base/files/patch-texk_texlive_Makefile_in ./var/macports/sources/rsync.macports.org/release/ports/tex/texlive_texmf-docs ./var/macports/sources/rsync.macports.org/release/ports/tex/texlive_texmf-full ./var/macports/sources/rsync.macports.org/release/ports/tex/texlive_texmf-minimal Tottie:/1local% port installed texlive* None of the specified ports are installed. Does this mean there is an error in the port, or have I done the wrong thing yet again? How can I safely get rid of these files? David -- View this message in context: http://old.nabble.com/syntax-for-uninstalling.-Can-I-use-a-regex--tp27735428p27736242.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
texlive_base failed to build
I'm aware that there is a bug report out on texlive_base, but is there a work-around? I'm rather desperate, as I stupidly trashed my copy of tetex before trying to install texlive. As a result none of the tex family programs are available to me, and I use them all the time. I tried the version of the final command you see below at the end of my error message, that I found in one of the trac files, but it just reported multiple symbol definitions. Could someone help me out here? I'm out of my depth. Thanks very much. Should I start again with a port clean command? In desperation, I downloaded MacTex (not via MacPorts), and the installation seemed to go OK. But when I tried to use it, I got an error message that /opt/local/bin/pdflatex didn't exist. I was surprised by this unexpected interaction between MacPorts and MacTex. I then tried port search pdflatex and was told texshop. But when I successfully did a MacPorts port of texshop, pdflatex still wasn't there. How can I find a port which will give me a copy of /opt/local/bin/pdflatex? Here is the error I got from trying to build texlive_base --- Building texlive_base Error: Target org.macports.build returned: shell command cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_texlive_base/work/texlive_base-2007 make all returned error 2 Command output: make[2]: Nothing to be done for `all'. make all-recursive Making all in data make[4]: Nothing to be done for `all'. Making all in src make[4]: Nothing to be done for `all'. make[4]: Nothing to be done for `all-am'. make[2]: Nothing to be done for `all'. make[2]: Nothing to be done for `all'. make[2]: Nothing to be done for `all'. make[2]: Nothing to be done for `all'. make[2]: Nothing to be done for `all'. make[2]: Nothing to be done for `all'. make[2]: Nothing to be done for `all'. make[2]: Nothing to be done for `all'. make[2]: Nothing to be done for `all'. make[2]: Nothing to be done for `all'. make[2]: Nothing to be done for `all'. make[2]: Nothing to be done for `all'. make[2]: Nothing to be done for `all'. make[2]: Nothing to be done for `all'. cd gui; make CC='/usr/bin/gcc-4.0' CFLAGS='-O2 ' libgui.a make[3]: `libgui.a' is up to date. /bin/sh ../libtool --mode=link /usr/bin/gcc-4.0 -o xdvi-xaw.bin -L/opt/local/lib browser.o dvi-draw.o dvi-init.o dvisel.o encodings.o events.o filehist.o font-open.o gf.o hypertex.o image-magick.o mime.o my-snprintf.o my-vsnprintf.o pagehist.o pk.o print-internal.o psdps.o psgs.o psheader.o psnews.o read-mapfile.o search-internal.o special.o string-utils.o tfmload.o util.o vf.o xdvi.o xserver-info.o x_util.o ./gui/libgui.a ../../libs/t1lib/libt1.a ../../libs/t1lib/../type1/libtype1.a -L/opt/local/lib -lXaw -lXmu -lXt -lSM -lICE -lXp -lXext -lXpm -lX11 -liconv ../kpathsea/libkpathsea.la -lm /usr/bin/gcc-4.0 -o xdvi-xaw.bin browser.o dvi-draw.o dvi-init.o dvisel.o encodings.o events.o filehist.o font-open.o gf.o hypertex.o image-magick.o mime.o my-snprintf.o my-vsnprintf.o pagehist.o pk.o print-internal.o psdps.o psgs.o psheader.o psnews.o read-mapfile.o search-internal.o special.o string-utils.o tfmload.o util.o vf.o xdvi.o xserver-info.o x_util.o -L/opt/local/lib ./gui/libgui.a ../../libs/t1lib/libt1.a ../../libs/t1lib/../type1/libtype1.a -lXaw -lXmu -lXt -lSM -lICE -lXp -lXext -lXpm -lintl -lc -lX11 -lXau -lXdmcp -liconv ../kpathsea/.libs/libkpathsea.a -lm /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: can't locate file for: -lXaw collect2: ld returned 1 exit status make[2]: *** [xdvi-xaw.bin] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1 Error: The following dependencies failed to build: texlive_base -- View this message in context: http://www.nabble.com/texlive_base-failed-to-build-tp22153627p22153627.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: texlive_base failed to build
Perry Lee-2 wrote: On Feb 22, 2009, at 4:17 PM, David Epstein wrote: In desperation, I downloaded MacTex (not via MacPorts), and the installation seemed to go OK. But when I tried to use it, I got an error message that /opt/local/bin/pdflatex didn't exist. I was surprised by this unexpected interaction between MacPorts and MacTex. I then tried port search pdflatex After installing MacTex, did you run pdflatex from a new shell or from a preexisting one? If it's the latter case, bash may be using a hashed location. You can make it forget by typing `hash -r`. As far as I know, MacTex's pdflatex is located at /usr/texbin/pdflatex. Maybe I should reinstall MacTex. I have no texbin in /usr/. But this is probably off-topic. Is there a user forum for MacTex? I didn't try running pdflatex. I tried to typeset using TexShop, which I opened by clicking on the TexShop icon. I use tcsh and not bash. David -- View this message in context: http://www.nabble.com/texlive_base-failed-to-build-tp22153627p22153834.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
comparing a possibly altered file with the original
I have done a very small amount of editing of some configuration files in /opt/local, and I suddenly realize that I should have been keeping a record, because upgrading the port will delete my customizations. A specific file I have changed is texmf.cnf in the teTex package, but I probably only deleted one or two comment characters. What is the simplest way to compare the version of the file that I now have in /opt/local with the version of the file that I originally downloaded on installation? I want a method that is safe, with no danger of overwriting my current setup. Thanks David -- View this message in context: http://www.nabble.com/comparing-a-possibly-altered-file-with-the-original-tp22087551p22087551.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: comparing a possibly altered file with the original
Rainer Müller-4 wrote: David Epstein wrote: What is the simplest way to compare the version of the file that I now have in /opt/local with the version of the file that I originally downloaded on installation? I want a method that is safe, with no danger of overwriting my current setup. Run a 'port destroot portname' and then compare the file in $(port work portname)/work/destroot/ with the one in prefix. I tried the command port work teTex and got a null response, so i'm not sure what this means. Where will the new version of teTex be downloaded to by the command port destroot teTex? What do you mean by the one in prefix? Thanks David -- View this message in context: http://www.nabble.com/comparing-a-possibly-altered-file-with-the-original-tp22087551p22089238.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: comparing a possibly altered file with the original
Rainer Müller-4 wrote: David Epstein wrote: I tried the command port work teTex and got a null response, so i'm not sure what this means. The command only works after you ran 'port destroot'. Where will the new version of teTex be downloaded to by the command port destroot teTex? That's what 'port work tetex' will tell you. I hope this posting won't arrive twice. I wrote a response, but I'm not sure whether I sent it, so I'm trying again. sudo port destroot teTex worked without comment. port work teTex gave the response /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_teTeX/work Note that this ends with work. When I did ls -alR on this directory, I got drwxr-xr-x 3 root admin 102 Feb 19 00:11 ./ drwxr-xr-x 3 root admin 102 Feb 19 00:11 ../ -rw-r--r-- 1 root admin0 Feb 19 00:11 .macports.teTeX.state So I have been unable to follow Rainer's advice. David -- View this message in context: http://www.nabble.com/comparing-a-possibly-altered-file-with-the-original-tp22087551p22092055.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
manual changes in /opt/local
I learned from a bad experience that manual changes to files in /opt/local are a bad idea. For one thing, new versions of ports are quite likely to overwrite such changes. It was worse for me: the whole MacPorts arrangement stopped working. updmap is a command that comes with the teTex package. (Side question: how would I be able to find this out if I recalled only updmap and not teTex? Another side question: is there a way of finding out which commands the package teTex will install in /opt/local/bin, without actually installing it?) To get back to my main question: man updmap says updmap reads a configuration file, updmap.cfg(5) and I'm assuming updmap.cfg is supposed to be edited by hand---it's a text file. Problem 1: editing by hand a file in /opt/local. Is this wise? Is there any alternative? Will the file be overwritten by a later port? Prolem 2: % slocate updmap.cfg /opt/local/share/texmf-dist/web2c/updmap.cfg /opt/local/var/macports/software/teTeX/3.0_5/opt/local/share/texmf-dist/web2c/updmap.cfg so there are two files updmap.cfg files. How do I know which one to edit? Or should I be editing yet another copy? There are a couple of other configuration files in /opt/local that I have edited by hand. I have also done something I don't quite remember about getting some daily maintenance program or perhaps daily updating of some database to work. So what about the overwriting problem? I would like to know what other MacPorts users do. Thanks David -- View this message in context: http://www.nabble.com/manual-changes-in--opt-local-tp22056767p22056767.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
structure and names of directories in /opt/local
Can someone say something about the general structure of /opt/local. For example, what kind of material goes into share, and why is it called share? Who is sharing it? I recognize src as source, but what is var about? Thanks David -- View this message in context: http://www.nabble.com/structure-and-names-of-directories-in--opt-local-tp22052170p22052170.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: R GUI
Andrei Tchijov wrote: Why bother with Mac port when R ppl have native mac gui? I really wanted to find out how to search using port. Jesse Hamner showed how to remove the regular expression part from the clutches of port, so that the output from port list can be dealt with using standard Unix facilities. In retrospect, this is the obvious approach. port list R* can't do what we want, can it? The shell tries to expand R* to match a file in the current directory, and otherwise exits with No match. If one shields R* from the shell with quote marks, for example, then one gets a list of all ports starting with R or r, and there are too many of them for comfort. David -- View this message in context: http://www.nabble.com/R-GUI-tp21054535p21057934.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
R GUI
Does Macports have a port for the GUI for R, the statistical computing program? Is it in fact possible to have a Macport supplying a MacOsX GUI (not necessarily R) that is invoked by double-clicking on an icon? My inability to use the port search facility efficiently became evident on this issue, since my search for the R-gui failed miserably. port search R brings in every port with an r in its name. man port advertises that one can use regular expressions in the search, but fails to point to a particular set of regular expressions, ignoring the fact that there are many standard collections of basic regular expressions, each likely to have a different way of indicating word boundaries. I tried port search \R\ and also port search \bR\b, and was told there are no matches, even through port info R works. Nor could I figure out how to make the matching case-sensitive. So, if anyone can give me a hint on port search regular expressions, that would be helpful. Thanks David -- View this message in context: http://www.nabble.com/R-GUI-tp21054535p21054535.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: R GUI
Chris Janton wrote: On 2008-12-17 , at 10:46 , David Epstein wrote: port list R* can't do what we want, can it? The shell tries to expand R* to match a file in the current directory, and otherwise exits with No match. If one shields R* from the shell with quote marks, for example, then one gets a list of all ports starting with R or r, and there are too many of them for comfort. f...@mac:~:125 $ port list R* R @2.8.0 math/R That's running from trunk - so MacPorts version is f...@mac:~:126 $ port MacPorts 1.8.0 Entering interactive mode... (help for help, quit to quit) [Users/face] ^D Goodbye On my *old* system f...@x:face:123 $ port MacPorts 1.600 Entering interactive mode... (help for help, quit to quit) [Users/face] ^D Goodbye f...@x:face:124 $ port list R* f...@x:face:125 $ Looks like you need a newer version of port ;-) I have version 1.700 of MacPorts, under MacOsX 10.4.11, and when I do sudo port selfupdate, I'm told I am already up-to-date. This discussion is assuming a complexity that I didn't at first suspect. I found to my surprise that bash and tcsh interpret port list R* differently. bash seems to pass the R* argument unaltered to port. But tcsh attempts an immediate expansion of R* before handing over to port. I am still unable to track down the other difference, in that on my machine, the argument following port list seems to be dealt with in a case-insensitive manner, and on Chris's machine seems to be dealt with in a case-sensitive manner. Using interactive mode for port simplifies by removing potentially complex interactions with the shell. However, for me, the case-insensitivity remains. Perhaps this is due to some different configuration setting. Or maybe it's a difference between Leopard and Tiger. Since, thanks to this thread, I now have several ways of dealing with these searches efficiently, I don't think it's worthwhile investigating the matter further. However, if someone knows why there's this difference, without having to spend time on it, it would be interesting to know the answer. David -- View this message in context: http://www.nabble.com/R-GUI-tp21054535p21062507.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
More than one version of a port installed.
On doing port installed, I found many examples like this: tcl @8.5.4_0 tcl @8.5.5_0 (active) The first would not allow an uninstall because of dependencies. Is there anyway to reasonably clean up the situation so that I end up with only one version (the latest) of each port? But I suppose that wouldn't work because some port may insist on a particular outdated version of a package it depends on. So what's the best one can do in this direction with not too much manual work? By the way, I installed the most recent version of port, so any advice should be in the light of that. I enjoyed the fact that port selfupdate no longer produces large amounts of seemingly irrelevant output. Very nice and clean. Thanks so much for all the work---much appreciated. David -- View this message in context: http://www.nabble.com/More-than-one-version-of-a-port-installed.-tp21006096p21006096.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: More than one version of a port installed.
David Epstein wrote: On doing port installed, I found many examples like this: tcl @8.5.4_0 tcl @8.5.5_0 (active) The first would not allow an uninstall because of dependencies. Is there anyway to reasonably clean up the situation so that I end up with only one version (the latest) of each port? But I suppose that wouldn't work because some port may insist on a particular outdated version of a package it depends on. So what's the best one can do in this direction with not too much manual work? By the way, I installed the most recent version of port, so any advice should be in the light of that. I enjoyed the fact that port selfupdate no longer produces large amounts of seemingly irrelevant output. Very nice and clean. Thanks so much for all the work---much appreciated. David I did further cleaning up of my Macports files, and these annoying duplicates went away. So maybe my original question is a non-question, or maybe the situation I described is occasionally possible. David -- View this message in context: http://www.nabble.com/More-than-one-version-of-a-port-installed.-tp21006096p21006381.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: More than one version of a port installed.
Joshua Root-8 wrote: David Epstein wrote: On doing port installed, I found many examples like this: tcl @8.5.4_0 tcl @8.5.5_0 (active) The first would not allow an uninstall because of dependencies. Is there anyway to reasonably clean up the situation so that I end up with only one version (the latest) of each port? But I suppose that wouldn't work because some port may insist on a particular outdated version of a package it depends on. So what's the best one can do in this direction with not too much manual work? The incorrect complaining about dependents is fixed in MacPorts 1.7. Ports can't currently depend on particular versions of other ports, so you should be able to remove the old version with: sudo port uninstall tcl @8.5.4_0 or, to remove all inactive versions: sudo port uninstall inactive - Josh Great!! I wondered why I suddenly stopped getting those error messages. Thanks again. D -- View this message in context: http://www.nabble.com/More-than-one-version-of-a-port-installed.-tp21006096p21006434.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Error upgrading xrender on Panther
Jeremy Huddleston-5 wrote: Can you please see: http://trac.macports.org/ticket/17429#comment: I think if you pull in xorg-libX11 first, it'll be fine, but I need someone to test that first... I just tried sudo port upgrade installed (I should have said outdated instead of installed, but nothing seemed to go wrong) and I hit this xrender problem. I looked at the conversation over the ticket, but didn't understand much of it. Also, I was surprised to find that the bug report was closed, because that would indicate to me that the problems with porting xrender have been removed. But I am continuing to get exactly the same errors as those originally reported. How should one interpret a bug closed message? I run Mac Os X 10.4.11, so I should have changed the name of the thread from Panther to Tiger, but I didn't know how to do that. Could someone post advice on how to proceed, directed at uneducated users? Thanks very much. I would have tried installing xorg-libX11, except that Jeremy says, in the email I quote, that the solution is untested, and, furthermore, the discussion on the ticket seems a little equivocal. Furthermore, I saw the comment in that discussion that installing xorg-libX11 brings in a lot of other stuff, so I don't want to do it, unless it's necessary. -- View this message in context: http://www.nabble.com/Error-upgrading-xrender-on-Panther-tp20758046p21009181.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
sudo port upgrade all
I mistakenly did sudo port upgrade all, instead of sudo port upgrade installed, and left my machine for 24 hours. It seems that a huge amount of stuff was installed, which I now want to get rid of. The first point I will make is that this has happened to other users before, as one can see by searching the list for port upgrade all, and port should not allow this to happen without making sure that the reader knows what he/she is doing. I was working with the default version of sources.conf. Please point me to a link specifying the procedure to be followed when requesting an improvement to MacPorts. I wonder if anyone has time or interest to provide this additional protection to naive users? Secondly I would welcome some helpful suggestions about how to recover from this situation. I want to identify the unnecessary installs, and uninstall them. I don't want to use -f, for fear of damaging my existing installation. Unless there is a way of detecting dates of installation using some feature of port, the most hopeful route for me seems to be to use Unix find. However, I don't understand the file structure of /opt/local well enough. How can I construct a find command that will get me only new installs, with only one hit per install? What I am talking about here is the fact that there are many files associated with each install, and I don't want a separate find hit for each of these files. Assuming that I can construct a list of unwanted ports, I can uninstall everything in the list, except that dependencies will prevent this. If I pass uninstall commands repeatedly over the list, what happens when it hits ports that have already been uninstalled? Or is there a better way. Again, I don't want to use force. Finally, does port uninstall (if successful) remove ALL the files associated with an install, or is some debris left that needs to be further cleaned? thanks for your help in my predicament. David -- View this message in context: http://www.nabble.com/sudo-port-upgrade-all-tp20716578p20716578.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: loader error, uninstall fails
Bryan Blackburn-4 wrote: On Mon, Oct 20, 2008 at 02:26:45PM -0700, David Epstein said: [...] sudo port install exiv2 then gave me exactly the same linker/loader errors as before. I think that looks the same as ticket #16728: http://trac.macports.org/ticket/16728 There's a possible workaround listed there if you feel like trying it, though I believe that workaround shouldn't be needed with a new version of MacPorts. Bryan Are you saying that a new version of MacPorts is imminent? If it's not too complicated to explain, why might that work around the workaround? David -- View this message in context: http://www.nabble.com/loader-error%2C-uninstall-fails-tp20053716p20084145.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: loader error, uninstall fails
Bryan Blackburn-4 wrote: [..snip..] I think that looks the same as ticket #16728: http://trac.macports.org/ticket/16728 There's a possible workaround listed there if you feel like trying it, though I believe that workaround shouldn't be needed with a new version of MacPorts. Bryan The workaround you refer to looks pretty simple to implement. Before I try it, are there any hazards associated to the port edit and port build commands for exiv2? Will I have to remember to do anything special in the future when the problem gets fixed? Is the port build command a substitute for port install? Finally, is there a standard way to request to be put on a cc list when there is any contribution to discussion on the ticket to which Bryan refers? thanks David -- View this message in context: http://www.nabble.com/loader-error%2C-uninstall-fails-tp20053716p20084402.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: loader error, uninstall fails
Ryan Schmidt-24 wrote: Looks like you have a copy of gcc 4.2.3 installed in /usr/local. Things installed in /usr/local often conflict with MacPorts so it's not recommended to have anything in /usr/local while using MacPorts. To see if this is the problem, rename /usr/local to /usr/local-off, clean the port you were having trouble with, and try installing it again. I successfully installed Xcode2.5. Thanks for explaining that I couldn't use Xcode3.x on MacOsX10.4.11. I renamed /usr/local to /usr/local-off sudo port install exiv2 then gave me exactly the same linker/loader errors as before. So I seem to be stymied, unless I move to Leopard on my laptop. I haven't yet tried to install exiv2 on my G4 PCC. David -- View this message in context: http://www.nabble.com/loader-error%2C-uninstall-fails-tp20053716p20079120.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
loader error, uninstall fails
While trying to install gimp, I had problems with exiv2. So first I did sudo port clean --all exiv2 Is this the correct command for removing all exiv2 files? This worked without complaint. I then tried to install exiv2 on its own, with the following results---I've collected together standard output and standard error resulting from the sudo port install exiv2 command. Then I get loader/linker errors. I'm weak on interpreting compiler errors, but the trouble seems to be clashing or overlapping versions of libgcc in the Apple hierarchy. I'm out of my depth (which is pretty shallow at the best of times). Is this a bug in the exiv2 port? Thanks David sudo port install exiv2 --- Fetching exiv2 --- Attempting to fetch exiv2-0.17.1.tar.gz from http://www.exiv2.org/ --- Verifying checksum(s) for exiv2 --- Extracting exiv2 --- Configuring exiv2 --- Building exiv2 with target all Error: Target org.macports.build returned: shell command cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_exiv2/work/exiv2-0.17.1 make all returned error 2 Command output: /usr/bin/g++-4.0 -O2 -Wall -Wcast-align -Wpointer-arith -Wformat-security -Wmissing-format-attribute -Woverloaded-virtual -W -MMD -I. -I/opt/local/include -DEXV_LOCALEDIR=\/opt/local/share/locale\ -I../xmpsdk/include -c value.cpp -fno-common -DPIC -o .libs/value.o /usr/bin/g++-4.0 -O2 -Wall -Wcast-align -Wpointer-arith -Wformat-security -Wmissing-format-attribute -Woverloaded-virtual -W -MMD -I. -I/opt/local/include -DEXV_LOCALEDIR=\/opt/local/share/locale\ -I../xmpsdk/include -c value.cpp -o value.o /dev/null 21 /usr/bin/g++-4.0 -O2 -Wall -Wcast-align -Wpointer-arith -Wformat-security -Wmissing-format-attribute -Woverloaded-virtual -W -MMD -I. -I/opt/local/include -DEXV_LOCALEDIR=\/opt/local/share/locale\ -I../xmpsdk/include -c version.cpp -fno-common -DPIC -o .libs/version.o /usr/bin/g++-4.0 -O2 -Wall -Wcast-align -Wpointer-arith -Wformat-security -Wmissing-format-attribute -Woverloaded-virtual -W -MMD -I. -I/opt/local/include -DEXV_LOCALEDIR=\/opt/local/share/locale\ -I../xmpsdk/include -c version.cpp -o version.o /dev/null 21 /usr/bin/g++-4.0 -O2 -Wall -Wcast-align -Wpointer-arith -Wformat-security -Wmissing-format-attribute -Woverloaded-virtual -W -MMD -I. -I/opt/local/include -DEXV_LOCALEDIR=\/opt/local/share/locale\ -I../xmpsdk/include -c properties.cpp -fno-common -DPIC -o .libs/properties.o /usr/bin/g++-4.0 -O2 -Wall -Wcast-align -Wpointer-arith -Wformat-security -Wmissing-format-attribute -Woverloaded-virtual -W -MMD -I. -I/opt/local/include -DEXV_LOCALEDIR=\/opt/local/share/locale\ -I../xmpsdk/include -c properties.cpp -o properties.o /dev/null 21 /usr/bin/g++-4.0 -O2 -Wall -Wcast-align -Wpointer-arith -Wformat-security -Wmissing-format-attribute -Woverloaded-virtual -W -MMD -I. -I/opt/local/include -DEXV_LOCALEDIR=\/opt/local/share/locale\ -I../xmpsdk/include -c xmp.cpp -fno-common -DPIC -o .libs/xmp.o /usr/bin/g++-4.0 -O2 -Wall -Wcast-align -Wpointer-arith -Wformat-security -Wmissing-format-attribute -Woverloaded-virtual -W -MMD -I. -I/opt/local/include -DEXV_LOCALEDIR=\/opt/local/share/locale\ -I../xmpsdk/include -c xmp.cpp -o xmp.o /dev/null 21 /usr/bin/g++-4.0 -O2 -Wall -Wcast-align -Wpointer-arith -Wformat-security -Wmissing-format-attribute -Woverloaded-virtual -W -MMD -I. -I/opt/local/include -DEXV_LOCALEDIR=\/opt/local/share/locale\ -I../xmpsdk/include -c xmpsidecar.cpp -fno-common -DPIC -o .libs/xmpsidecar.o /usr/bin/g++-4.0 -O2 -Wall -Wcast-align -Wpointer-arith -Wformat-security -Wmissing-format-attribute -Woverloaded-virtual -W -MMD -I. -I/opt/local/include -DEXV_LOCALEDIR=\/opt/local/share/locale\ -I../xmpsdk/include -c xmpsidecar.cpp -o xmpsidecar.o /dev/null 21 ../libtool --mode=link /usr/bin/g++-4.0 -L/opt/local/lib -L../xmpsdk/src -o libexiv2.la basicio.lo bmpimage.lo canonmn.lo convert.lo cr2image.lo crwimage.lo datasets.lo error.lo exif.lo futils.lo fujimn.lo gifimage.lo ifd.lo image.lo iptc.lo jp2image.lo jpgimage.lo makernote.lo makernote2.lo metadatum.lo minoltamn.lo mrwimage.lo nikonmn.lo olympusmn.lo orfimage.lo panasonicmn.lo pngimage.lo pngchunk.lo psdimage.lo rafimage.lo sigmamn.lo pentaxmn.lo sonymn.lo tags.lo tgaimage.lo tiffcomposite.lo tiffimage.lo tiffparser.lo tiffvisitor.lo types.lo value.lo version.lo properties.lo xmp.lo xmpsidecar.lo -rpath /opt/local/lib -version-info 4:1:0 -L/opt/local/lib -lintl -L/opt/local/lib -liconv -lc -R/opt/local/lib -Wl,-framework -Wl,CoreFoundation -L/opt/local/lib -liconv -R/opt/local/lib -lz -lexpat -lxmpsdk /usr/bin/g++-4.0 -dynamiclib -single_module -flat_namespace -undefined suppress -o .libs/libexiv2.4.0.1.dylib .libs/basicio.o .libs/bmpimage.o .libs/canonmn.o .libs/convert.o .libs/cr2image.o .libs/crwimage.o .libs/datasets.o .libs/error.o .libs/exif.o .libs/futils.o .libs/fujimn.o .libs/gifimage.o .libs/ifd.o .libs/image.o .libs/iptc.o .libs/jp2image.o .libs/jpgimage.o .libs/makernote.o
pango 1.22.0 requires glib 2.17.3 or later but you have glib 2.16.5.
My error message must have been dealt with somewhere in the list, possibly many times, but I haven't been able to find it. I was trying to install gimp: sudo port install gimp Eventually I got the error message Target org.macports.configure returned: pango 1.22.0 requires glib 2.17.3 or later but you have glib 2.16.5. I tried sudo port deactivate glib, which resulted in Password: --- Deactivating glib Error: port deactivate failed: Registry error: glib not registered as installed active. Help would be appreciated. David -- View this message in context: http://www.nabble.com/pango-1.22.0-requires-glib-2.17.3-or-later-but-you-have-glib-2.16.5.-tp20009218p20009218.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
detex
Is there a macport of detex? This is a program that removes TeX control sequences and comments from files. I thought it was part of the teTeX distribution, and there is a port of teTex. Does anyone know how I can get hold of this? Should I do it outside /opt/local? Thanks David -- View this message in context: http://www.nabble.com/detex-tp16078108p16078108.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: libtool woes
Ryan Schmidt-24 wrote: unable to infer tagged configuration when trying to build apache2 is already filed: http://trac.macosforge.org/projects/macports/ticket/13653 ...[snip]... Both tickets include lots of discussion. The apache2 ticket includes patches which someone said worked. Neither maintainer has responded to the tickets. Looks like it's time for someone else to commit the fixes. Probably not me, since I'm not experiencing the issue. As an inexperienced MacPorter, I would like advice on what to do, in view of my need for apache2. Possible strategies: 1) Wait for someone to put the advertised patches into the official macport distribution. 2) Install the advertised patches. (Are there instructions somewhere for how to do this?) 3) Try rebuilding libtool. (But won't port object to deleting libtool because other packages depend on it?) Pointer to relevant online advice?? David -- View this message in context: http://www.nabble.com/libtool-woes-tp15248567p15258474.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Problem installing apache2
sudo port -d selfupdate this passed, but with some warning messages that I might try cleaning up some directory or directories manually; I paid no attention to this As apache2 was giving me trouble, I then did sudo port clean --all apache2 --- this worked sudo port install apache2 --- error messages below Can anyone tell me what is going wrong, and, more to the point, how to fix it? Thanks a lot David --- Fetching apache2 --- Attempting to fetch httpd-2.2.6.tar.bz2 from http://www.apache.org/dist/httpd --- Verifying checksum(s) for apache2 --- Extracting apache2 --- Applying patches to apache2 --- Configuring apache2 --- Building apache2 with target all Error: Target org.macports.build returned: shell command cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6 make all returned error 2 Command output: Making all in srclib Making all in os Making all in unix /opt/local/share/apr-1/build/libtool --silent --mode=compile /usr/bin/gcc-4.0 -I/opt/local/include -O2 -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp -I/opt/local/include -I. -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/os/unix -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/server/mpm/prefork -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/http -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/filters -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/proxy -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/generators -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/mappers -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/database -I/opt/local/include/apr-1 -I/opt/local/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/server -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/proxy/../generators -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/ssl -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/dav/main -prefer-non-pic -static -c unixd.c touch unixd.lo libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' make[3]: *** [unixd.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 Error: Status 1 encountered during processing. -- View this message in context: http://www.nabble.com/Problem-installing-apache2-tp14639067p14639067.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
aspell and missing file with en-US
I get this error message with aspell aspell -t -c cfs.tex Error: No word lists can be found for the language en_US. What do I need to download, to make the error message go away? Does anyone know of tutorial pages for aspell? I'm finding it hard to get used to the commands (Headaches are: getting British English?, how to maintain one's own dictionary, etc.) thanks [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/aspell-and-missing-file-with-en-US-tf4626126.html#a13210096 Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: texinfo doesnt function
This discussion has been way above my head. Can someone just give me the bottom line: I cannot get info to work. Here is some output: hottie:~/1ActualSubmission% which info /opt/local/bin/info hottie:~/1ActualSubmission% info info info: dir: No such file or directory Can someone tell me whether this means that info is currently unusable? info coreutils ls gives a similar response, namely info: dir: No such file or directory. Same for info coreutils. I'm not pushing for work to be done on this, because I'm sure everyone is busy on more important business, but does the previous mail exchanged on this matter mean that someone is going to try to fix this? Thanks [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/texinfo-doesnt-function-tf4596286.html#a13176994 Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
port of fmt?
Gnu's version of fmt contains a feature that I need, and which is not available from /usr/bin/fmt. I tried port search fmt and got no relevant hits. Is this available under MacPorts? If not how could I request it for the future? Thanks [EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Trying to update the slocate database
My first command: slocate slocate slocate: fatal error: Could not find user database '/opt/local/var/db/slocate/slocate.db': No such file or directory My second command: which slocate /opt/local/bin/slocate My third command: sudo /opt/local/etc/daily.slocate Rebuilding slocate database: slocate: fatal error: load_file: Could not open file: /opt/local/etc/updatedb.conf: No such file or directory Can anyone help me get slocate going? Where is updatedb.conf supposed to come from, and why wasn't it installed when I installed slocate? TIA, [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Trying-to-update-the-slocate-database-tf4606431.html#a13153315 Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Horrible problems after moving /opt/local aside
Following advice, I moved /opt/local aside and I have since been having horrible problems. I use latex and gv a lot. It turned out that latex was in the old /opt/local (now /opt/ local.old) and I wasn't sure how to access it. I copied /opt/ local.old/bin/{selected items that seemed to belong to tex} to the new /opt/local/bin. That seems to work, but will probably go wrong when other files from the tex hierarchy are needed. Then I tried sudo port install gv and got the following response: Script started on Wed Oct 10 20:07:56 2007 hottie:/2bin% sudo port install gv --- Staging freetype into destroot Error: Target org.macports.destroot returned: shell command cd / opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_print _freetype/work/freetype-2.3.5 make install DESTDIR=/opt/local/ var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_print _freetype/work/destroot returned error 2 Command output: ./builds/unix/mkinstalldirs /opt/local/var/macports/ build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_print _freetype/work/destroot/opt/local/lib \ /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_print _freetype/work/destroot/opt/local/lib/pkgconfig \ /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_print _freetype/work/destroot/opt/local/include/freetype2/freetype/config \ /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_print _freetype/work/destroot/opt/local/include/freetype2/freetype/cache \ /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_print _freetype/work/destroot/opt/local/bin \ /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_print _freetype/work/destroot/opt/local/share/aclocal ./builds/unix/libtool --mode=install /opt/local/bin/ginstall - c \ /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_print _freetype/work/freetype-2.3.5/objs/libfreetype.la /opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_print _freetype/work/destroot/opt/local/lib ./builds/unix/libtool: line 1: /opt/local/bin/gsed: No such file or directory ./builds/unix/libtool: line 1: /opt/local/bin/gsed: No such file or directory *** Warning: inferring the mode of operation is deprecated. *** Future versions of Libtool will require --mode=MODE be specified. ./builds/unix/libtool: line 1: /opt/local/bin/gsed: No such file or directory ./builds/unix/libtool: line 1: /opt/local/bin/gsed: No such file or directory ./builds/unix/libtool: line 1: /opt/local/bin/gsed: No such file or directory ./builds/unix/libtool: line 1: /opt/local/bin/gsed: No such file or directory ./builds/unix/libtool: line 1: /opt/local/bin/gsed: No such file or directory : install: `.' must be an absolute directory name Try ` --help --mode=install' for more information. make: *** [install] Error 1 Error: The following dependencies failed to build: ghostscript fontconfig freetype Error: Status 1 encountered during processing. hottie:/2bin% exit What do I do now? Please keep it simple, if you can. [EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Horrible problems after moving /opt/local aside
Paul Beard-2 wrote: On 10/10/07, David Epstein [EMAIL PROTECTED] wrote: What do I do now? Please keep it simple, if you can. for i in gv latex coreutils with_default_names; do port -vc install $i; done You really will be better off rebuilding them all from scratch for a couple of reasons: 1. you'll have the newest versions and b. the ports will be managed so you'll get upgrades and dependency issues taken care of. -- Paul Beard / www.paulbeard.org/ So I don't have to use sudo on the port install? When I tried your command, I got: for i in gv latex coreutils with_default_names; do port -vc install $i; done Error: Unable to execute port: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_gv/work/.macports.gv.state is not writable - check permission on port directory Error: Port latex not found Error: Unable to execute port: can't create directory /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutils_coreutils: permission denied Error: Port with_default_names not found What about all my error messages when I tried to port install gv? Why will they not show up again with your formula? Thanks [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Horrible-problems-after-moving--opt-local-aside-tf4602915.html#a13143713 Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Horrible problems after moving /opt/local aside
Paul Beard-2 wrote: On 10/10/07, David Epstein [EMAIL PROTECTED] wrote: What do I do now? Please keep it simple, if you can. for i in gv latex coreutils with_default_names; do port -vc install $i; done You really will be better off rebuilding them all from scratch for a couple of reasons: 1. you'll have the newest versions and b. the ports will be managed so you'll get upgrades and dependency issues taken care of. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] I successfully installed coreutils. I don't know what you mean by with_default_names. sudo port install gv continues to give the mass of error messages that I reported in my first posting in this thread. port search tex| grep -v text gives lots of hits, but it's not clear to me from the response what the name of the package should be in sudo port install I tried sudo port install tex and it replied no such package Thanks for any help [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Horrible-problems-after-moving--opt-local-aside-tf4602915.html#a13144203 Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Horrible problems after moving /opt/local aside
Ryan Schmidt-24 wrote: Ok, so freetype wanted to use /opt/local/bin/gsed but it doesn't exist. I don't have /opt/local/bin/gsed on my system either, and freetype builds just fine. (I imagine for me it's finding and using the system sed, /usr/bin/sed.) Perhaps you had gsed in your old /opt/ local and somehow freetype picked up on that. I don't see how though. Please make a new Terminal window and try it again. sudo port clean --work freetype sudo port install freetype If you get the same error, then do it again with debug output and show it to us. sudo port clean --work freetype sudo port -dv install freetype Sigh of relief!! When deadlines loom, one doesn't necessarily do the right thing. I have been trying too many things to be clear about what happened, but, anyway your clean command seems to have been what I was failing to do, after my original sin of putting stuff into /opt/local/bin from /opt/local.old/bin. I have managed now to install some of the things gv depends on, which is a big advance, but I haven't yet had a go at gv. I decided that since there might be various junk lying around, I should install the dependencies one at a time, starting each with a clean. Anyway, I feel I am now a long way forward, knowing about the clean. Question: would it have worked just to clean gv, or would gv dependencies have remained dirty? I hope I'm now doing following a reasonable strategy, but I've still clearly got a lot to learn. [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Horrible-problems-after-moving--opt-local-aside-tf4602915.html#a13144553 Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: unregistered files/modules
Ryan Schmidt-24 wrote: A-ha! Revelation! You have things in /opt/local that did not come from MacPorts!...[snip]... MacPorts likes to be in almost complete control of its prefix, likes to know what's in it. (It's fine to keep some config files there, but having other software there that MacPorts doesn't know about is not ok.) Paul's advice is good -- move /opt/local out of the way. However, you cannot move a directory into itself. So, try mv /opt/ local /opt/local-old I'll move /opt/local aside, as you and Paul Beard suggest. But I have the impression that quite a number of non-macports packages want to be placed in /opt/local, and even do so without asking permission. So this could conflict with what you say about MacPorts wanting to keep /opt/local/ to itself. I have certainly been advised by people who know a lot more about software than I do, that downloaded software should go into /opt/local/. [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/unregistered-files-modules-tf4586448.html#a13129554 Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
unregistered files/modules
I have just started using Macports and I wonder how to get round the following annoying problem. Each port that I download complains about a number of files (between 5 and 35) that are unregistered. The install stops at every single error and aborts. As a result, I have a great deal of manual work, deleting these unregistered files, having to restart the install each time. Moreover, using root privileges to delete the unregistered files creates unpleasant opportunities for typos. I had a glance at the macports-users archive, but couldn't find an index. I tried Google, but couldn't find any sensible leads on this. I read man port, but it's unclear to me exactly what each option does, and I'm concerned that I'll do the wrong thing. 1. Where can I find a fuller explanation of the options to port than that given by man port? 2. How should I proceed in the light of the difficulties explained in the first paragraph? 3. I am tempted to download the entire Darwinports/Macports tree, but it looks as though this would take ages even without the manual work described above. Comments on these 3 points would be welcome. Thanks a lot David Epstein ([EMAIL PROTECTED]) ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: unregistered files/modules
On 8 Oct 2007, at 08:50, Ryan Schmidt wrote: On Oct 8, 2007, at 02:37, David Epstein wrote: I have just started using Macports and I wonder how to get round the following annoying problem. Each port that I download complains about a number of files (between 5 and 35) that are unregistered. The install stops at every single error and aborts. As a result, I have a great deal of manual work, deleting these unregistered files, having to restart the install each time. Moreover, using root privileges to delete the unregistered files creates unpleasant opportunities for typos. I had a glance at the macports-users archive, but couldn't find an index. I tried Google, but couldn't find any sensible leads on this. I read man port, but it's unclear to me exactly what each option does, and I'm concerned that I'll do the wrong thing. 1. Where can I find a fuller explanation of the options to port than that given by man port? 2. How should I proceed in the light of the difficulties explained in the first paragraph? 3. I am tempted to download the entire Darwinports/Macports tree, but it looks as though this would take ages even without the manual work described above. Comments on these 3 points would be welcome. The entire ports tree is already downloaded to your computer. I believe it's usually in /opt/local/var/macports/sources/ rsync.macports.org/release/ports. That's just the portfiles and some patches, not the distribution source archives of each port. Please show us the exact error messages you're getting, and what command you've typed to receive it. I can't reproduce these errors. I tried installing one or two additional packages and they went through without complaint. Luckily a small amount of evidence survives from my xterm's memory and here it is: hottie:~% sudo port install gnupg --- Activating gnupg 1.4.7_0 Error: Target org.macports.activate returned: Image error: /opt/local/ share/locale/locale.alias already exists and does not belong to a registered port. Unable to activate port gnupg. Error: Status 1 encountered during processing. hottie:~% sudo rm -i /opt/local/share/locale/locale.alias remove /opt/local/share/locale/locale.alias? y hottie:~% sudo port install gnupg --- Activating gnupg 1.4.7_0 --- Cleaning gnupg I think I would have had to rm and restart about 50 times during installation of gnupg, but fortunately I was able to remove a whole lot of files at once, using Unix * wildcard. Don't like using wildcards when I'm root. Since not one single package I have installed has reported that it is up to date, it looks as though I should do something like sudo port install all, shouldn't I? David [EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: unregistered files/modules
Paul Beard-2 wrote: On 10/8/07, David Epstein [EMAIL PROTECTED] wrote: Error: Target org.macports.activate returned: Image error: /opt/local/ share/locale/locale.alias already exists and does not belong to a registered port. what does port provides /opt/local/share/locale/locale.alias tell you? it says it's unregistered or unassociated with any installed port, so I don't think anything will be revealed. Have you installed anything manually (ie, from source w/o MacPorts) on this system? If you haven't got anything /opt/local that isn't owned by MacPorts, you can use port -f install gnupg to override any of the issues you're seeing. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] Thanks to everyone for very helpful comments. The whole set-up was very mysterious, and has now become much clearer. The material in /opt/local/ was installed by a programmer. I have no idea how he did it, but it was a long time ago, maybe before Darwinports was really up and running, let alone Macports. So macports is refusing to delete these files under automation, and that's obviously the right thing for port to do unless there is a special flag. It is still not clear to me what will happen if I give a command like port -f install gnupg. Practically NOTHING in my large /opt/local comes from MacPorts, so Paul is suggesting that I should therefore not use -f. But that's exactly WHY I want to use -f. A number of my programs in /opt/local just don't work on my new Intel Mac, so I have to upgrade. What are the dangers of using -f? Would it help me, in view of the fact that the files I want to delete do not come from MacPorts? Or would MacPorts still refuse to delete? I don't like the idea of using a force command without knowing fairly well what damage it might do. You can see why I'm not happy with the output from man port which explains -f as force mode (ignore state file). I don't know what state file means, and man doesn't say whether port's actions are confined to files installed by MacPorts. There must be documentation that says what state file means---could a kind person direct me to it? Thanks very much. David Epstein [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/unregistered-files-modules-tf4586448.html#a13105766 Sent from the MacPorts - Users mailing list archive at Nabble.com. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users