Release source tarballs lack a top-level directory
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
Research direction
Start by locating the release source-tarball packaging or archive-generation workflow; the issue does not name a file or entry point. Compare its output with the GitHub tag archive and check how the release version is used in archive paths. Done means future source tarballs extract into one version-named top-level directory while retaining the source files.
Written by the indexing model from the issue text.
Description
The release source tarballs (e.g. VeraCrypt_1.26.29_Source.tar.bz2) extract their contents directly into the current directory (contrib/, doc/, src/, ...) instead of into a single top-level directory such as VeraCrypt_1.26.29/.
Most distribution build systems expect a tarball to unpack into one directory named after the project and version. Without it, packagers have to override the unpack step. This came up in the OpenWrt package review: https://github.com/openwrt/packages/pull/30597#discussion_r4133028379
Could future release tarballs contain a top-level directory? git archive --prefix=VeraCrypt_$VERSION/ ... (or tar --transform) would do it. For reference, the GitHub tag archive for VeraCrypt_1.26.29 already has a top-level directory and the same 1706 files as the release tarball.
- Dominant language
- C
- Stars
- 11.7k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 28
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from veracrypt/VeraCrypt
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 5/5 Over a week Newbie friendliness 32/100
veracrypt/VeraCrypt#1995 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
veracrypt/VeraCrypt#1993 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
veracrypt/VeraCrypt#1991 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
veracrypt/VeraCrypt#1989 · 1 comment ·
Maintainers usually reply within 1 day
All issues in veracrypt/VeraCrypt
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug game: 01008BA02525A000 ios
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
area/ysql kind/bug priority/medium status/awaiting-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yugabyte/yugabyte-db#37523 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
ly05010419/MacNativeGames#2079 ·
Maintainers usually reply within 1 day