Re: "Broken files found, but all associated ports are not in the index" error
On Dec 16, 2021, at 02:55, Greg Earle wrote: > > On a 2010 Mac Pro running macOS Mojave 10.14.6, I'm getting this: > > -- > [0:48] nightowl:/ % sudo port upgrade outdated > Nothing to upgrade. > ---> Scanning binaries for linking errors > ---> Found 2 broken files, matching files to ports > Warning: No port p5.26-net-ssleay found in the index; can't rebuild > ---> Broken files found, but all associated ports are not in the index and > so cannot be rebuilt. > > [0:49] nightowl:/ % port installed p5.26-net-ssleay > The following ports are currently installed: > p5.26-net-ssleay @1.900.0_0 (active) > > [0:50] nightowl:/ % port info p5.26-net-ssleay > Error: Port p5.26-net-ssleay not found > -- > > Tried to remove it but it didn't like that: > > -- > [0:52] nightowl:/ % sudo port uninstall p5.26-net-ssleay > Note: It is not recommended to uninstall/deactivate a port that has > dependents as it breaks the dependents. > The following ports will break: > p5.26-io-socket-ssl @2.68.0_0 > p5.26-http-tiny @0.76.0_0 > p5.26-io-socket-ssl @2.69.0_0 > p5.26-io-socket-ssl @2.70.0_0 > p5.26-io-socket-ssl @2.71.0_0 > Continue? [y/N]: N > ---> Cleaning p5.26-net-ssleay > -- > > Is there anything I can do about it? I still have a ton of p5.26-* and > p5.28-* ports installed, as well as p5.30-*. > > -- > [0:54] nightowl:/ % sudo port installed | grep p5.26 | wc -l > 134 I recommend uninstalling all p5.26 ports. Use p5.28 equivalents instead.
Re: Cannot build libb2
On Dec 15, 2021, at 14:25, Dave Horsfall wrote: > On Fri, 10 Dec 2021, Ryan Schmidt wrote: > >> The "-arch x86_64 -arch i386" in the log does seem to indicate MacPorts >> is doing a universal build. The ways that could happen: >> >> * You specified +universal on the command line > > Nope... > >> * You specified +universal in variants.conf > > Nope... > >> * You installed a port that, because it does not support your machine's >> native architecture, requires its dependencies to be installed >> universal. > > Could be; how do I tell which variants were used by what? If you are installing a port that indicates, for example, that it only supports i386, and it depends on other ports, then MacPorts must install those other ports universal for i386 and x86_64. If it did not, then you would only have an x86_64 version of them, which wouldn't be sufficient for whichever port it is that only supports i386. To discover which of your installed ports fit that description, you could run: port -qv installed | grep -Ev 'archs=.*noarch|x86_64' >> If libb2 does not build universal, then that is certainly something we >> should fix. A bug has already been filed about it: >> >> https://trac.macports.org/ticket/64148 > > Thanks; I'll try the suggested fix, but... > >> If you want to explore why libb2 is building universal when you don't >> intend that, show us what command you ran and the output. Specifically, >> we'd want to know which port you are trying to install or upgrade when >> libb2 gets build universal. > > It was no more than my weekly "port selfupdate; port upgrade outdated" > etc. Great, so one of your outdated ports, or one of its dependencies, is causing libb2 to build universal. We'd need to see the output of your commands, possibly with debug output, to know which one, if the above `port -qv installed ...` command doesn't provide the answer. > Looks like I forgot to run it under "script", but when I tried again it > now mysteriously works, so I dunno... Chalk it up to a "heisenbug", I > guess (I hate those). If you selfupdated or synced before trying again, then your success is expected, since I fixed the problem as indicated in #64148.
Re: Files and Folders access
I have had two similar issues, but with Catalina. One where Gimp (from the Gimp website, not Macports) would not save a file to my Desktop and the other where Apple’’s Screenshot facility (Command-Shift-4) would not save to it, although it had always done so automatically in High Sierra and earlier O/Ss. I got onto Apple Support’s chat line about the first, and they suggested to upgrade my Gimp, which I did and it worked. The failure to save a screenshot to my Desktop actually occurred during the chat with Apple, but I was unable to investigate at the time. A day later I wanted to take a screenshot and send it by email. Same problem. All the usual Unix permissions on my Desktop seemed fine, but there is a new extension called “com.apple.macl” which works some kind of magic (ls -@ld ~/Desktop to see it). Nothing I did at the command-line could fix the problem with my Desktop. Eventually I found the “approved” method of making my own Desktop accessible to me again. 1. Bring up a Finder window. 2. in the left-hand column, right-click on “Desktop” and select “Get Info” from the popup menu. 3. Scroll to the bottom of the Info window and click on the tiny “lock” icon. 4. When requested, enter your Admin password. 5. Click on “+”. A window listing Users and Groups should appear. 6. Select one (e.g. yourself). This should now appear in the Info window’s list, with Privilege “Read only". 7. Click on the Privilege and select “Read & Write” from the popup list. 8. Click on the little “lock” again, to close it. Not exactly “intuitive”… I would say. Also Apple’s action regarding my Desktop, when it installed Catalina for me, is rather like a builder calling at my house to do some work, then changing the lock on my front door in the process, not telling me about this and then not leaving me a new key. I believe Apple’s intentions are still good, but they are becoming careless of their users’ interests. That works against them because I thought at first that they are becoming like IBM in the "bad old days” of the 60s and 70s. I thought they were trying to “influence" me to use only Apple products on my computer. Re Gimp, I now have Gimp 2.10.28 from Gimp’s website. It has been upgraded to follow Apple’s latest security protocol. The first time I asked it to save to my Desktop, I got a dialog box asking permission and requiring an Admin password. After that it has been fine and is now on the list of “approved” applications in System Preferences->Security and Privacy->Privacy->Files and Folders. Hope some of this helps. Ian Wadham. > On 17 Dec 2021, at 4:33 am, Lenore Horner wrote: > > I’m still struggling with letting Inkscape (I think Gimp too) installed via > MacPorts to be able to open files. I’ve searched the mailing list archive > for the last year for any mention of this and found zip so apparently I’m > particularly incompetent. Here’s what I’ve tried. > > Big Sur 11.6 > MacPorts base 2.7.1 > Just updated the tree and all anything listed as outdated. > inkscape-app @0.92_1, inkscape @0.92.5_9_x11, and xorg-server @1.20.11_1 > installed and active > r > In Apple -> System Preferences -> Security and Privacy -> Files and Folders I > cannot do any thing even having unlocked with an admin password. > In Apple -> System Preferences -> Security and Privacy -> Full Disk Access I > have given the following access the following: > Inkscape (the terminal app found with Show Contents in the Inkscape.app file > in my MacPorts folder) > Xquartz > Terminal > X11.app > Inkscape.app (the Inkscape icon in the MacPorts folder) > > I’ve shut down and restarted the computer and I’m still getting "Could not > read the contents of Desktop” and a parallel complaint for Documents. I know > that a dialog box should pop up asking for my permission to access my > Desktop, Documents, etc. folder and that those dialogs not popping up is a > known (and unfixible I think) issue. I thought granting full disk access was > the only known work-around, but full disk access to what? > > I have, by the way also tried the dmg from the Inkscape website for version > 1.1.1. I don’t get error messages with it, but it also can’t open a file > (spinning beachball of death). So that’s not good either. > > Thanks, > Lenore
Re: Files and Folders access
Lenore Horner writes: > [1:text/plain Show] > > > [2:text/html Hide Save:noname (7kB)] > > I’m still struggling with letting Inkscape (I think Gimp too) installed via > MacPorts to be able to open files. I’ve searched the mailing list archive > for the last > year for any mention of this and found zip so apparently I’m particularly > incompetent. Here’s what I’ve tried. > > Big Sur 11.6 > MacPorts base 2.7.1 > Just updated the tree and all anything listed as outdated. > inkscape-app @0.92_1, inkscape @0.92.5_9_x11, and xorg-server @1.20.11_1 > installed and active > r > In Apple -> System Preferences -> Security and Privacy -> Files and Folders I > cannot do any thing even having unlocked with an admin password. > In Apple -> System Preferences -> Security and Privacy -> Full Disk Access I > have given the following access the following: > Inkscape (the terminal app found with Show Contents in the Inkscape.app file > in my MacPorts folder) > Xquartz > Terminal > X11.app > Inkscape.app (the Inkscape icon in the MacPorts folder) > > I’ve shut down and restarted the computer and I’m still getting "Could not > read the contents of Desktop” and a parallel complaint for Documents. I know > that a dialog box should pop up asking for my permission to access my > Desktop, Documents, etc. folder and that those dialogs not popping up is a > known > (and unfixible I think) issue. I thought granting full disk access was the > only known work-around, but full disk access to what? > > I have, by the way also tried the dmg from the Inkscape website for version > 1.1.1. I don’t get error messages with it, but it also can’t open a file > (spinning > beachball of death). So that’s not good either. > > Thanks, > Lenore Hi Lenore, I don't know if this is the **proper** way to do it, but after running Inkscape via the launcher, `ps ux | grep -i inkscape` shows Inkscape is being executed via `/bin/sh`. Giving `/bin/sh` full disk access allows it to open files in the Documents folder, but presumably this allows pretty well all applications to access the entire disk, somewhat subverting the entire privacy mechanism. Hopefully, someone knows of a better way. Similarly, granting the Terminal application access to the Documents folder allows you to execute the inkscape binary from `/usr/local/bin` and open documents in the Documents folder, with the advantage of being able to reduce the scope of access. All, far from intuitive. Cheers, Frank
Files and Folders access
I’m still struggling with letting Inkscape (I think Gimp too) installed via MacPorts to be able to open files. I’ve searched the mailing list archive for the last year for any mention of this and found zip so apparently I’m particularly incompetent. Here’s what I’ve tried. Big Sur 11.6 MacPorts base 2.7.1 Just updated the tree and all anything listed as outdated. inkscape-app @0.92_1, inkscape @0.92.5_9_x11, and xorg-server @1.20.11_1 installed and active r In Apple -> System Preferences -> Security and Privacy -> Files and Folders I cannot do any thing even having unlocked with an admin password. In Apple -> System Preferences -> Security and Privacy -> Full Disk Access I have given the following access the following: Inkscape (the terminal app found with Show Contents in the Inkscape.app file in my MacPorts folder) Xquartz Terminal X11.app Inkscape.app (the Inkscape icon in the MacPorts folder) I’ve shut down and restarted the computer and I’m still getting "Could not read the contents of Desktop” and a parallel complaint for Documents. I know that a dialog box should pop up asking for my permission to access my Desktop, Documents, etc. folder and that those dialogs not popping up is a known (and unfixible I think) issue. I thought granting full disk access was the only known work-around, but full disk access to what? I have, by the way also tried the dmg from the Inkscape website for version 1.1.1. I don’t get error messages with it, but it also can’t open a file (spinning beachball of death). So that’s not good either. Thanks, Lenore
"Broken files found, but all associated ports are not in the index" error
On a 2010 Mac Pro running macOS Mojave 10.14.6, I'm getting this: -- [0:48] nightowl:/ % sudo port upgrade outdated Nothing to upgrade. ---> Scanning binaries for linking errors ---> Found 2 broken files, matching files to ports Warning: No port p5.26-net-ssleay found in the index; can't rebuild ---> Broken files found, but all associated ports are not in the index and so cannot be rebuilt. [0:49] nightowl:/ % port installed p5.26-net-ssleay The following ports are currently installed: p5.26-net-ssleay @1.900.0_0 (active) [0:50] nightowl:/ % port info p5.26-net-ssleay Error: Port p5.26-net-ssleay not found -- Tried to remove it but it didn't like that: -- [0:52] nightowl:/ % sudo port uninstall p5.26-net-ssleay Note: It is not recommended to uninstall/deactivate a port that has dependents as it breaks the dependents. The following ports will break: p5.26-io-socket-ssl @2.68.0_0 p5.26-http-tiny @0.76.0_0 p5.26-io-socket-ssl @2.69.0_0 p5.26-io-socket-ssl @2.70.0_0 p5.26-io-socket-ssl @2.71.0_0 Continue? [y/N]: N ---> Cleaning p5.26-net-ssleay -- Is there anything I can do about it? I still have a ton of p5.26-* and p5.28-* ports installed, as well as p5.30-*. -- [0:54] nightowl:/ % sudo port installed | grep p5.26 | wc -l 134 -- Thanks, - Greg
