[wp-trac] [WordPress Trac] #60398: WordPress 6.4.3 MacOS/Linux Compressed Zip plugin archives "Incompatible Archive" on upload

[WordPress Trac]

#60398: WordPress 6.4.3 MacOS/Linux Compressed Zip plugin archives "Incompatible
Archive" on upload
-------------------------------------------------+-------------------------
 Reporter:  Endymion00                           |       Owner:
                                                 |  peterwilsoncc
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  6.4.4
Component:  Upload                               |     Version:  6.4.3
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing has-patch has-unit-    |     Focuses:
  tests fixed-major dev-reviewed commit          |
-------------------------------------------------+-------------------------

Comment (by costdev):

 @adegans If the ZIP uploads fine for you (if not, see if @room34's comment
 above works for you), then it should work fine for the users, which points
 to something going on in between you providing the ZIP, and them uploading
 it.

 Do you know if the users were downloading the ZIP using Safari? If so,
 they may need to uncheck
 [https://core.trac.wordpress.org/ticket/60398#comment:41 this box] because
 Safari unpacks ZIPs by default, meaning the users may be re-ZIPping using
 the UI.

 -----

 > “your opinion doesn’t count because you’re not a committer” and it
 implies that your minds can’t be changed by the likes of the peons merely
 using WordPress.

 Your opinion counts, as does everyone else's in this ticket. Our minds can
 be changed with new information. We're not better than you, we just have
 the added responsibility of making a decision. We consider your opinion,
 the impact on you and your users, the reach of an issue, available
 workarounds, whether sites go down/files get deleted/databases become
 corrupted, other fixes available to bundle, the availability of a release
 squad, whether releasing a new WordPress version containing only this
 bugfix sets a negative or unsustainable precedent, as well as any context-
 specific factors.

 -----

 > Yup - Very poorly, almost like they don’t want to fix this.

 [https://core.trac.wordpress.org/ticket/60398#comment:56 That's not the
 case]. I've put a lot of time into investigation trying to ensure the fix
 was the correct one, alongside other contributors and committers.

 To be clear: The fix will be in WordPress 6.5. The discussion is about
 whether a 6.4.x minor release is issued containing only this fix.

 We have multiple factors to consider, and the opinions of those affected
 are of course a big part of that. We have a responsibility to make the
 right decision as we see it at the time. We read and consider every
 comment in context, and we discuss - publicly, as above - a comment and
 whether it changes the circumstances influencing a decision.

 > To me, that just shows that everyone who offers plugins and themes
 outside of their channels does not matter

 No one in the WordPress project, committer or otherwise, thinks that.
 Extenders matter regardless of where they offer their extensions from. I
 also offer plugins outside of the WordPress.org channel. My day job (I
 volunteer to WordPress Core) as an agency developer means I also feel the
 impact of this issue. That doesn't change my responsibility as a Committer
 to consider all factors (actually makes it a bit harder in this case 😅).

 -----

 The decision about releasing this fix in a 6.4.x minor ''can'' change. As
 we've already factored existing information into the current decision, a
 different decision requires new information.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/60398#comment:94>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform