Packages - BigSur

[Fortune]

@dustbro said in Packages - BigSur:

@Fortune It ended up being a network permissions issue for me. I've actually ditched my M1 machine started making universal binaries with an Intel rig.

Hmm, it looks like the Whitebox Packages has some bugs on M1 machines then. On Intel no issues but on M1, this thing happens.

[Dan Korneff]

Hmm, it looks like the Whitebox Packages has some bugs on M1 machines then. On Intel no issues but on M1, this thing happens.

Same thing happend to me. I reached out to the dev and he sent me a link to an M1 version of Packages. Same result. Even when I compiled plugs on M1 I had to use my intel rig to create installers.

[Dan Korneff]

@Lindon I haven't had as much luck as @d-healey making automatic Universal Binaries. For 1, I have to deselect arm64e in projucer. It's for iOS apps and for some reason it keeps my projects from compiling. Then I have to adjust a few settings in Xcode... maybe I can make a quick video of what I'm doing.

[Fortune]

@dustbro said in Packages - BigSur:

Hmm, it looks like the Whitebox Packages has some bugs on M1 machines then. On Intel no issues but on M1, this thing happens.

Same thing happend to me. I reached out to the dev and he sent me a link to an M1 version of Packages. Same result.

That sounds pretty annoying :/

Even when I compiled plugs on M1 I had to use my intel rig to create installers.

When I compile the universal binaries on M1 Monterey, I can't make an installer of them with Intel Catalina Xcode 10.2, right?

[Dan Korneff]

When I compile the universal binaries on M1 Monterey, I can't make an installer of them with Intel Catalina Xcode 10.2, right?

I don't see why not. I'm not sure that Packages on an Intel machine cares whether or not the contents are M1 compatible.

[DanH]

@d-healey can you install Xcode 12.2 on Mojave?

[d.healey]

@DanH I don't know, see what version in the app store.

[orange]

@Fortune I've come across the same issue and I've contacted the developer. I got the below answer:

I would suggest to check the POSIX permissions in the Terminal and in the payload of the project. And also compare the working .pkg to the not working .pkg using Pacifist.

IMHO this issue is not about the individual machine's permissions, it's more like the Packages specific issue. Any thoughts?

[DanH]

@orange I had some issues with the latest packages update and rolled back to the previous one and was fine again. 1.2.9 works fine for me.

[orange]

@DanH I will try, thanks!

[DanH]

@orange let me know if you need the installer

[orange]

@DanH I am checking the installer v1.2.8 is available but I can't find v1.2.9 :/

[DanH]

@orange 1.2.8 should be fine, let me see if I still have 1.2.9

[orange]

@DanH I've tried v1.2.9, unfortunately the same thing.

[DanH]

@orange doh!

[orange]

@orange Ok, as the developer suggested, I think the issue is about the POSIX permissions. After adjusting the POSIX permissions, apparently that fixed the issue.

EDIT: "Others" should not have Write permission. So it should be like this => drwxrwxr-x

---

Not working permission:

---

Working permissions: