composer archive fails with 2.4.5

[speedupmate]

Summary (*)

since magento2 is managed with composer then developers expect that all composer functionality is supported . Currently composer archive (https://getcomposer.org/doc/03-cli.md#archive) fails on newly created project when tar or tar.gz format is specified

Examples (*)

composer archive --format=tar
Creating the archive into ".".

In PharArchiver.php line 65:
                                                                                                                                                                                                
  tar-based phar "/tmp/composer_archive62fab83c2db35.tar" cannot be created, filename "dev/tests/acceptance/tests/_data/adobe-base-image-long-name-image-long-name-image-long-name-image-long-  
  name-image-long-name-image-long-name-image-long-name-image-long-name-image-long-name.jpg" is too long for tar file format                                                                     
                                                                                                                                                                                               
archive [-f|--format FORMAT] [--dir DIR] [--file FILE] [--ignore-filters] [--] [<package> [<version>]]

Proposed solution

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users with no workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [*] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @speedupmate. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[engcom-Hotel]

Hello @speedupmate,

Thanks for the report & contribution!

We have tried to reproduce the issue in the below Magento versions:

• Magento 2.4.4
• Magento 2.4.5
• Magento 2.4-develop

And the issue is reproducible for us. It seems the cause of this issue is the long file name and internally Tar command accepts file names below 99 characters.

Please refer to the below screenshot for reference:

Hence confirming the issue.

Thanks