starred/sharpcompress
1
0
Fork 0
mirror of https://github.com/adamhathcock/sharpcompress.git synced 2026-02-12 13:35:11 +00:00
Code Issues 975 Packages Projects Releases 22 Wiki Activity

[PR #206] [MERGED] Zip64 extending information and ZipReader #895

New Issue
Open
opened 2026-01-29 22:18:05 +00:00 by claunia · 0 comments
claunia commented 2026-01-29 22:18:05 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/adamhathcock/sharpcompress/pull/206
Author: @markryd
Created: 1/25/2017
Status: ✅ Merged
Merged: 1/25/2017
Merged by: @adamhathcock

Base: master ← Head: zip64-extraction

📝 Commits (2)

  • 839b3ab Add support for zip64 extended information field
  • a8c3a74 Add support for zip64 to ZipReader

📊 Changes

6 files changed (+119 additions, -5 deletions)

View changed files

📝 src/SharpCompress/Common/Zip/Headers/DirectoryEntryHeader.cs (+20 -2)
📝 src/SharpCompress/Common/Zip/Headers/LocalEntryHeader.cs (+13 -0)
📝 src/SharpCompress/Common/Zip/Headers/LocalEntryHeaderExtraFactory.cs (+77 -1)
📝 src/SharpCompress/Common/Zip/StreamingZipHeaderFactory.cs (+1 -1)
📝 src/SharpCompress/Common/Zip/ZipFilePart.cs (+1 -1)
📝 test/SharpCompress.Test/Zip/ZipReaderTests.cs (+7 -0)

📄 Description

This PR adds support for reading the zip64 extended information field, which wasn't required for my previous test files, but probably is required in general for zip64 archives (the tripping point in my testing was new files starting beyond the 4Gb point of my archive).

Adding this support also instantly fixed the trouble I was having with ZipReader support, so that has been included.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/adamhathcock/sharpcompress/pull/206 **Author:** [@markryd](https://github.com/markryd) **Created:** 1/25/2017 **Status:** ✅ Merged **Merged:** 1/25/2017 **Merged by:** [@adamhathcock](https://github.com/adamhathcock) **Base:** `master` ← **Head:** `zip64-extraction` --- ### 📝 Commits (2) - [`839b3ab`](https://github.com/adamhathcock/sharpcompress/commit/839b3ab0cf0c0d198a2fc6fda25d18c026857c9b) Add support for zip64 extended information field - [`a8c3a74`](https://github.com/adamhathcock/sharpcompress/commit/a8c3a7439ed5173aff0a5a07aa84a6a9606709db) Add support for zip64 to ZipReader ### 📊 Changes **6 files changed** (+119 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `src/SharpCompress/Common/Zip/Headers/DirectoryEntryHeader.cs` (+20 -2) 📝 `src/SharpCompress/Common/Zip/Headers/LocalEntryHeader.cs` (+13 -0) 📝 `src/SharpCompress/Common/Zip/Headers/LocalEntryHeaderExtraFactory.cs` (+77 -1) 📝 `src/SharpCompress/Common/Zip/StreamingZipHeaderFactory.cs` (+1 -1) 📝 `src/SharpCompress/Common/Zip/ZipFilePart.cs` (+1 -1) 📝 `test/SharpCompress.Test/Zip/ZipReaderTests.cs` (+7 -0) </details> ### 📄 Description This PR adds support for reading the zip64 extended information field, which wasn't required for my previous test files, but probably is required in general for zip64 archives (the tripping point in my testing was new files starting beyond the 4Gb point of my archive). Adding this support also instantly fixed the trouble I was having with ZipReader support, so that has been included. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-29 22:18:05 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
duplicate
enhancement
feedback requested
not bug
pull-request
Mirrored from GitHub Pull Request
 question
up for grabs
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/sharpcompress#895
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?