Modify

Opened 5 months ago

Closed 5 months ago

Last modified 5 months ago

#23782 closed defect (fixed)

Missing universal and Intel builds for macOS

Reported by: remigiusz.zetkowski+josm@… Owned by: team
Priority: normal Milestone:
Component: Installer MacOS Version: tested
Keywords: Cc:

Description

I noticed on Github that since build 19127 there are no universal and Intel builds in assets, 6 items less in general. Is this a bug or planned deprecation for Intel machines?

I hope that status report is not required in this case, otherwise please let me know.

Attachments (0)

Change History (5)

comment:1 by remigiusz.zetkowski+josm@…, 5 months ago

Just after creating the ticket, I noticed there's an issue with notarization: https://github.com/JOSM/josm/actions/runs/9691788219/job/26743914915

comment:2 by taylor.smock, 5 months ago

FML. I think this is similar to #23125. This might be something we need to put on a calendar or something.

Conducting pre-submission checks for JOSM_21_arm64.zip and initiating connection to the Apple notary service...
Error: HTTP status code: 403. A required agreement is missing or has expired. This request requires an in-effect agreement that has not been signed or has expired. Ensure your team has signed the necessary legal agreements and that they are not expired.

I hope that status report is not required in this case, otherwise please let me know.

Nope. Not required since the problem is not in JOSM core and you gave sufficient information to figure out what the problem is.

I'll ping Thomas on IRC to see if he knows anything.

comment:3 by taylor.smock, 5 months ago

Resolution: fixed
Status: newclosed

The notarization issue should be fixed now. I'm currently rerunning the mac actions.

comment:4 by remigiusz.zetkowski+josm@…, 5 months ago

Great, thank you!

As for creating a calendar event - if the issue was that a new agreement had to be accepted, this might not be reliable. AFAIK, Apple tends to update the agreement at different times, sometimes twice within a year. Perhaps the job should fail in this case because a proper, full release cannot happen? Just a thought, you know your process way better than I do.

comment:5 by taylor.smock, 5 months ago

The jobs do fail. It is just that I don't pay much attention to the GitHub CI stuff.

I should go through the GH CI and fix all the problems.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.