Re: force rebuild a port
Riccardo Mottola via macports-users writes: > Hi! > > suppose I want to rebuild a port, but it has no version update. > 1) e.g. rev-upgrade shows it to be rebuild but "port outdated" doesn't > show it. > 2) Or I want to rebuild it with a different compiler. > > How can I do? "port upgrade X" will do nothing because X is not outdated. > "port upgrade --force X" will upgrade all dependencies, which is a > little too much... > > 1) in my case has issues because it wants to rebuild many packages and > starts with one that breaks, so it never gets to the next one. > I tried using "-p" but apparently it is not respected for "port -p > rev-upgrade" and still dies. > > Riccardo > What I sometimes did is to restart the port all over: port installed crancyport (to see which variants have been used) port -f uninstall crancyport maybe port clean --all crancyport port install crancyport -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
XCode 15.1 and macports?
Does anyone know if it is safe to use XCode 15.1 with macports? -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: Quartz no longer launching when an X application is invoked
Chris Jones writes: > Users should not need to do *anything* to get DISPLAY correctly set. > Anything you have in your personal environment configuration should be > removed. If you aren't getting DISPLAY set with the correct launchd > socket by default then you must have something that is interfering with > this. I removed that line and rebooted, and lo and behold, DISPLAY got properly set and the X server started up automatically when I launced an X11 program. Thanks for reminding us, Chris. > > On 04/12/2023 2:15 pm, Pieter van Oostrum wrote: >> On my machine I have: >> export DISPLAY=$(launchctl getenv DISPLAY) >> I don't know if that is the canonical way to do it but for me it works. > -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: Quartz no longer launching when an X application is invoked
On my machine I have: export DISPLAY=$(launchctl getenv DISPLAY) I don't know if that is the canonical way to do it but for me it works. -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: perl --version is not at perl5.36 but at perl5.34 yet both are listed as active
Kenneth Wolcott writes: > Hi; > > I'm confused about what Perl I have installed vi MacPorts and what > is active and what I can use. > [snip] > I apparently don't understand enough about how to use "port select" > even after several readings. > > On a slightly off-topic question, I'm still trying to replace all > "universal" ports with aarch64 ports (native) and when I install > and/or upgrade, I always specify "-s". I've only had one problem (so > far) with this. > > Thanks, > Ken Wolcott After sudo port install perl5 +perl5_36 I get: ~ $ perl --version This is perl 5, version 36, subversion 1 (v5.36.1) built for darwin-thread-multi-2level -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: Error with 'port -vst install'
Clemens Lang writes: > Hi, > > On Fri, Oct 07, 2022 at 09:16:50PM +0200, Pieter van Oostrum wrote: >> Although your suggestion solved the problem for me, I have another >> followup. >> >> I found this ticket, which describes the same problem: >> https://trac.macports.org/ticket/53435 It is six years old and it is >> marked as fixed, but now it seems to have cropped up again. Some kind >> of regression, maybe? > > Thanks for checking, but I can't see a regression here. The MacPorts > port still has destroot.keepdirs set for this directory, and I confirmed > that the MacPorts 2.7.2 package for Monterey contains the directory with > the expected permissions. > > I'm not sure why they were not correct on your system, but it doesn't > seem to be caused by something that's very common. I did some tests: 1) I moved /opt/local/var/macports/sip-workaround out of the way and then ran sudo port -f selfupdate --no-sync This reinstalled the macports base and a new sip-workaround was created with permissions 777. So far so good. However, 2) When I had already a sip-workaround with the wrong permissions (e.g.755), and I run then sudo port -f selfupdate --no-sync the permissions of sip-workaround are not changed. So if you had once installed a macports base that had the bug I mentioned, and a sip-workaround with default permissions had been created later, you're stuck with it. I suppose this is what had happened on my machine. This looks like a kind of bug to me. -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: Error with 'port -vst install'
Clemens Lang writes: > Hi, > > On Thu, Oct 06, 2022 at 01:55:10PM +0200, Pieter van Oostrum wrote: >> It fails to create the directory >> '/opt/local/var/macports/sip-workaround/502/usr'. In fact on a >> previous run it failed to create >> '/opt/local/var/macports/sip-workaround/502' and then I created that >> directory manually. And then it fails at the next level. I don't like >> to create the whole directory structure manually. Is there anything >> else I can do, or is this actually a bug? > > That's unexpected. You should be able to just completely delete > /opt/local/var/macports/sip-workaround/502 and try again. If that > doesn't work, make sure that the permissions for > /opt/local/var/macports/sip-workaround are drwxrwxrwt, i.e. chmod 1777. Although your suggestion solved the problem for me, I have another followup. I found this ticket, which describes the same problem: https://trac.macports.org/ticket/53435 It is six years old and it is marked as fixed, but now it seems to have cropped up again. Some kind of regression, maybe? With kind regards, Pieter van Oostrum -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: Error with 'port -vst install'
Clemens Lang writes: > Hi, > > On Thu, Oct 06, 2022 at 01:55:10PM +0200, Pieter van Oostrum wrote: >> It fails to create the directory >> '/opt/local/var/macports/sip-workaround/502/usr'. In fact on a >> previous run it failed to create >> '/opt/local/var/macports/sip-workaround/502' and then I created that >> directory manually. And then it fails at the next level. I don't like >> to create the whole directory structure manually. Is there anything >> else I can do, or is this actually a bug? > > That's unexpected. You should be able to just completely delete > /opt/local/var/macports/sip-workaround/502 and try again. If that > doesn't work, make sure that the permissions for > /opt/local/var/macports/sip-workaround are drwxrwxrwt, i.e. chmod 1777. Hi Clemens, That did the trick. With kind regards, Pieter van Oostrum > > HTH, > Clemens -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Error with 'port -vst install'
I'm preparing an upgrade for a port that I maintain (fricas). I have made a private upgrade in a local directory, and the normal install succeeds. However, in preparation of th Pull Request I tried 'sudo port -vst install' and this fails with a permission error in the extraction phase. ``` Executing: cd "/opt/local/var/macports/build/_Users_pieter_Projects_MACPORTS_math_fricas/fricas/work" && /usr/bin/bzip2 -dc '/opt/local/var/macports/distfiles/fricas/fricas-1.3.8-full.tar.bz2' | /usr/bin/tar -xf - sip_copy_proc: mkdir(/opt/local/var/macports/sip-workaround/502/usr): Permission denied Command failed: cd "/opt/local/var/macports/build/_Users_pieter_Projects_MACPORTS_math_fricas/fricas/work" && /usr/bin/bzip2 -dc '/opt/local/var/macports/distfiles/fricas/fricas-1.3.8-full.tar.bz2' | /usr/bin/tar -xf - Exit code: 128 ``` It fails to create the directory '/opt/local/var/macports/sip-workaround/502/usr'. In fact on a previous run it failed to create '/opt/local/var/macports/sip-workaround/502' and then I created that directory manually. And then it fails at the next level. I don't like to create the whole directory structure manually. Is there anything else I can do, or is this actually a bug? -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: No user or group to remove on macOS Catalina
"chilli.names...@gmail.com" writes: > To uninstall macports entirely, I use the three commands below in a script > (which I assume I got > from the manual, but it's been awhile, I do not recall), but they work just > as well one at a time: > > sudo port -vfp uninstall --follow-dependencies installed > > sudo port -vfp uninstall all > > sudo rm -rf /opt/local /Library/Tcl/macports* You may also have to add sudo rm -rf /Applications/Macports -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: Debugging restore_ports.tcl
Eric Gallager via macports-users writes: > On Mon, Feb 8, 2021 at 1:03 PM Ryan Schmidt wrote: >> >> >> >> On Feb 7, 2021, at 20:59, Eric Gallager wrote: >> >> > When restore_ports.tcl gets stuck building its list of ports to >> > restore, is there a way to get it to tell you which ports exactly it's >> > failing to process? i.e., which ports to remove from your myports.txt >> > to get it to continue? >> >> I don't know. In what way is it getting stuck? > > It's the part on the Troubleshooting section of the wiki page where it says: > > If you see an "infinite loop" error message, such as this: > > Error: we appear to be stuck, exiting... > infinite loop > while executing > "sort_ports $portList" > invoked from within > "set operationList [sort_ports $portList]" > (file "./restore_ports.tcl" line 285) > > it indicates that the script has a list of ports to install, and it > can't figure out which of the ports to install next. > > https://trac.macports.org/wiki/Migration#Troubleshooting > > The workaround it suggests to deal with this issue is "to reduce your > list of ports to install, until it no longer has a dependency cycle," > but it doesn't say exactly HOW to go about choosing which ports to > remove from the list in order to reduce its length. > My myports.txt file has 6147 lines in it. I don't know where to begin with it. The usual way of tackling these kinds of problems is "bisecting". Divide the list in two halves, and try each of these separately. If a half fails, then divide it in two halves again, etc. -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: Xcode for old Macbook Pro
Dave Horsfall writes: > I think I've asked this question before, but I cannot find the response(s). > > Where can I find Xcode for an oldish MacBook Pro (13", Mid 2010) running > Sierra 10.12.6 (I've been told by the dealer that it cannot run High > Sierra, and when I tried it on an older MacBook it was a disaster). There are people who say you can upgrade to High Sierra, and then use XCode 10. https://apple.stackexchange.com/questions/356210/how-to-upgrade-xcode-9-to-xcode-10-1-in-mac-os-sierra-10-12-6-16g1815 -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: qt5-qtwebengine on macOS 10.13, Xcode version
Davide Liessi writes: > I could remove py-pyqt-webengine from frescobaldi's dependencies (two > components would stop working, but the rest would continue) and > suggest in the latter's notes to install the former in order to get > full functionality, but I would prefer to keep it. Sigil also depends on py-pyqt-webengine, and I had to switch to XCode 10 on my MacOS 10.13.6 High Sierra MacBook Pro to get it working. -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: [MacPorts-announce] MacPorts 2.6.4 has been released
Dave Horsfall writes: > On Sat, 14 Nov 2020, Joshua Root wrote: > >> The MacPorts Project is pleased to announce the release of version >> 2.6.4. This is a bugfix release with small changes only. See the >> ChangeLog [1] for the list of changes. > > Which reminds me: OK on latest (and last) Sierra, on an early MacBook > Pro (13", mid-2010); I'm not sure if I want to try High Sierra yet (the > upgrade failed twice for various reasons on the earlier MacBook, which > is now dead in the water). > > It is a testament to my confidence in the MacPorts developers that I am > willing to upgrade right away :-) I've got 2.6.4 on High Sierra without problems. -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: macports-users Digest, Vol 163, Issue 13
Murray Eisenberg writes: > On17 Mar 2020 17:17:37 +0100, Pieter van Oostrum > wrote: > > Date: Tue, > From: Pieter van Oostrum > To: macports-users@lists.macports.org > Subject: Re: macports-users Digest, Vol 163, Issue 12 > Message-ID: > Content-Type: text/plain > > Murray Eisenberg writes: > > I did that: used mode 755 for directories, mode 644 for files there. > > Still, same error Unable to execute port: Could not open file: > /Users/murray/macports/ > myports/kde/ > okular/Portfile > > Did you get this to work with your own version of a port already > included in MacPorts? > > Yes, I do this regularly. Never had a problem. > My working mode is: I have a clone of the git repository, but for the > ports I am working on, I > make a copy of the Portfile and other relevant files in a shadow > directory, but only for those > ports. > > But 'could not open file' sounds like a protection issue. > What happens when you execute the shell command? > > sudo cat /Users/murray/macports/myports/kde/okular/Portfile > > By the way, another way is to go to the directory > /Users/murray/macports/myports/kde/okular > > and execute the command 'sudo port install' (i.e. without port name). It > should install the > port in that directory. > -- > > Command "sudo cat /Users/murray/macports/myports/kde/okular/Portfile" _does_ > type out the file > contents > > However, cd to that okulr directory and executing “sudo port install” there > once again gives the > same error "Unable to execute port: Could not open file: > /Users/murray/macports/myports/kde/okular > /Portfile”. OK, I guess that the difference is that I have my home directory with mode 755, and you probably have 700. With that setting macports cannot access anything in your files. If you find 755 risky, you could use 711 for all directories up to your repository. -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: macports-users Digest, Vol 163, Issue 12
Murray Eisenberg writes: > I did that: used mode 755 for directories, mode 644 for files there. > > Still, same error Unable to execute port: Could not open file: > /Users/murray/macports/myports/kde/ > okular/Portfile > > Did you get this to work with your own version of a port already included in > MacPorts? Yes, I do this regularly. Never had a problem. My working mode is: I have a clone of the git repository, but for the ports I am working on, I make a copy of the Portfile and other relevant files in a shadow directory, but only for those ports. But 'could not open file' sounds like a protection issue. What happens when you execute the shell command? sudo cat /Users/murray/macports/myports/kde/okular/Portfile By the way, another way is to go to the directory /Users/murray/macports/myports/kde/okular and execute the command 'sudo port install' (i.e. without port name). It should install the port in that directory. -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: installing patched okular: cannot open Portfile
Ken Cunningham writes: > gives error: > > Unable to execute port: Could not open file: > /Users/murray/macports/myports/kde/okular/Portfile > > Could it still be a permissions or ownership issue? > > It is a permissions error. Although Chris and others seem to make this work, > it has never worked > for me to put a macports repo in my home folder. I don’t know why, and I gave > up trying to fix it. > > Just put it in /Users/Shared/MacPorts or, what I do, is put them all in /opt > (but then you have to > be careful with sudo, which I always am). > Very strange. I have been using this construction for years. I have all my directories in my private repository with mode 755, and the files 644. -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: installing patched okular: cannot open Portfile
Murray Eisenberg writes: > The cited instructions at trac.macports.org do change the name. > > And if I do _not_ change the name, then how will command “sudo port install > okular” know to use > the modified port, inside my home tree, instead of the distributed one? You can give it a higher revision number. -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: Wxmaxima not linking to Maxima
Ian Veltman writes: > I have circa 2011 macbook air running High Sierra 10.13.6. used Macports to > install Wxmaxima: > Wxmaxima doesn't link to Maximaseems to be a problem with other attempts > to install > wxmaxima...any solution? > > Is your maxima at /opt/local/maxima or in another location? -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
Re: /opt/local/share/info/dir
Pieter van Oostrum writes:
> I noticed that on my computer /opt/local/share/info/dir hasn't been
> updated for a couple of months although I installed several ports with
> info files. My /opt/local/share/info/dir has dat Nove. 7, and several
> *.info files in /opt/local/share/info/ are not in the dir file. Even
> some files older than that aren't included.
>
> For example the gdb port was installed on Oct 22, but ggdb.info* files
> are present in /opt/local/share/info/, but it is not in the dir file.
> There is, however, an older entry
> * Gdb: (gdb). The GNU debugger.
> which is no longer functional.
>
> Should the install procedure not automatically update the dir file? Or
> must I do something special to get it updated?
I investigated this a bit more, and found the cause:
The Portfile for gdb renames the info files from gdb.info to ggdb.info in
post-destroot:
foreach info [glob -tails -directory ${destroot}${prefix}/share/info g*] {
move ${destroot}${prefix}/share/info/${info}
${destroot}${prefix}/share/info/g${info}
}
but the entry for gdb in dir is
* Gdb: (gdb)
So this then becomes a dangling pointer.
I see 3 possible solutions:
1) Just leave the files as they are, i.e. gdb.info. That seems to what grep
does: it keeps grep.info, not ggrep.info.
2) Update dir to accurately reflect the new file name,
e.g. something like
'install-info --info-dir=${destroot}${prefix}/share/info/ --entry="* Gdb:
(ggdb). The GNU debugger."
${destroot}${prefix}/share/info/ggdb.info'
Then probably the useless entry (gdb) should be deleted with 'install-info
--delete'.
3) Patch the direntry in gdb.texi, that determines what comes in dir:
@direntry
* Gdb: (gdb). The GNU debugger.
* gdbserver: (gdb) Server.The GNU debugging server.
@end direntry
Change gdb to ggdb.
--
Pieter van Oostrum
www: http://pieter.vanoostrum.org/
PGP key: [8DAE142BE17999C4]
Re: Git question
Gerben Wierda writes: > If I produce a pull request and I’m rebuffed because of an error I make, I > need to go back to > testate of the official repository before proceeding again. At such a point > my own clone is both > commits ahead and commits behind the official repository. I need to lose my > commits (as I am > rebuffed by macports maintainers if I have multiple ‘working’ commits in my > pull request). So, I > need to reset my clone to the current state of the official repository. Always make your own modifications on a new branch that you create locally, and then push to your github repository. In this way you can keep your master branch in synch with the upstream repository both on your computer and your own github repository without conflicts. Only when you have made changes in an area where master is also changed you will have to merge these changes into your own branch before you can commit/push them. -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
/opt/local/share/info/dir
I noticed that on my computer /opt/local/share/info/dir hasn't been updated for a couple of months although I installed several ports with info files. My /opt/local/share/info/dir has dat Nove. 7, and several *.info files in /opt/local/share/info/ are not in the dir file. Even some files older than that aren't included. For example the gdb port was installed on Oct 22, but ggdb.info* files are present in /opt/local/share/info/, but it is not in the dir file. There is, however, an older entry * Gdb: (gdb). The GNU debugger. which is no longer functional. Should the install procedure not automatically update the dir file? Or must I do something special to get it updated? -- Pieter van Oostrum www: http://pieter.vanoostrum.org/ PGP key: [8DAE142BE17999C4]
