UNSTARCH(1)

πŸ“¦
version 2.4.42 Β· 5 versions
, in ubuntu resolute, ubuntu stonking

✨ UNSTARCH β€” the manual page ✨

okay bestie, gather round, because this is unstarch, version 2.4.42+dfsg, and she is that girl πŸ’…


πŸ’– NAME πŸ’–

unstarch β€” the manual page for unstarch 2.4.42+dfsg. she unstuffs your starch archives, she reads their metadata, she verifies their whole vibe. iconic behaviour, honestly πŸŽ€


πŸ¦‹ DESCRIPTION πŸ¦‹

literally just unstarch bestie. no notes.

πŸ“š citation πŸ“š

if you're gonna cite her (and you SHOULD, she's a published queen πŸ‘‘), here's the receipts:

🏷️ the lore 🏷️

  • binary version: 2.4.42 (typical) (extracts archive version: 2.2.0 or older)
  • authors: Alex Reynolds and Shane Neph 🫢

🌸 USAGE 🌸

here's the whole shape of her, no cap:

unstarch [ <chromosome> ]  [ --elements |
--elements-max-string-length |
       --bases | --bases-uniq | --has-duplicates | --has-nested | --list
       | --list-json | --list-chromosomes | --archive-timestamp | --note
       | --archive-version | --is-starch | --signature |
       --verify-signature ] <starch-file>

πŸŽ€ Modifiers πŸŽ€

  • <chromosome> β€” optional, bestie. either it unarchives chromosome-specific records out of the starch archive file, or it restricts whatever operator you picked so it only acts on that chromosome (think chr1, chrY, etc.). your call πŸ’…

🧚 Process Flags 🧚

  • --elements β€” shows the total element count for the archive. if you handed over a <chromosome>, then the result shows the element count for that chromosome instead. slay.
  • --elements-max-string-length β€” shows the maximum string length across all elements in <chromosome>, if you specified one. if you did not specify a <chromosome>, the maximum string length is shown across all chromosomes. periodt.
  • --bases, --bases-uniq β€” show total and unique base counts, respectively, for the archive. if a <chromosome> is specified, the count is specific to that chromosome, if available. iykyk πŸ“
  • --has-duplicate-as-string, --has-duplicate β€” shows whether there's one or more duplicate elements in the specified chromosome, either as a numerical value (1/0) or as a string value (true/false). if no <chromosome> is specified, the value tells you whether there's one or more duplicate elements across all chromosome records.
  • --has-nested-as-string, --has-nested β€” shows whether there's one or more nested elements in the specified chromosome, either as a numerical value (1/0) or as a string value (true/false). if no <chromosome> is specified, the value tells you whether there's one or more nested elements across all chromosome records. (the original says "one ore more" and honestly? relatable typo, we respect her πŸ’€)
  • --list β€” lists the archive metadata (output comes in text format, very demure). if a chromosome is specified, the attributes of that given chromosome are what get shown.
  • --list-json, --list-json-no-trailing-newline β€” lists the archive metadata, but make it JSON ✨
  • --list-chr, --list-chromosomes β€” lists all chromosomes, or just the specified one, in the starch archive (works like "bedextract --listchr"). if you specify a <chromosome> that is not in the output list, nothing is returned. ghosted, basically πŸ‘»
  • --note β€” shows the descriptive note, if available.
  • --signature β€” displays the Base64-encoded SHA-1 data integrity signature for the specified <chromosome>, or the signatures of the metadata plus all available chromosomes if <chromosome> is left unspecified.
  • --verify-signature β€” verifies the data integrity of the specified <chromosome>, or the integrity of all available chromosomes if <chromosome> is unspecified. trust but verify, bestie 🫢
  • --archive-timestamp β€” shows the archive creation timestamp (in ISO 8601 format).
  • --archive-type β€” shows the archive compression type.
  • --archive-version β€” shows the archive version.
  • --is-starch β€” tests whether <starch-file> is a valid archive and prints 0/1 (false/true) to standard output. heads up: unstarch will also return a nonzero error code if the input file is not a valid archive.
  • --version β€” shows the binary version.
  • --help β€” shows this usage message. hi, that's this. you're here πŸ’–

🌈 SEE ALSO 🌈

the full documentation for unstarch is maintained as a Texinfo manual. if the info and unstarch programs are properly installed at your site, then this command:

info unstarch

should give you access to the complete manual. go read the extended cut, she ate πŸ“–βœ¨


and that's the whole page, bestie!! this was unstarch version 2.4.42+dfsg, dated August 2025. go unarchive something and be the main character you were born to be πŸ’…πŸ‘‘πŸ¦‹

πŸ“¦ where this page comes from