upack Issues

Issues Overview

30	2.2.2	closed	Update upack to add audit-based properties to packages
upack.exe should include the JSON properties listed under "Additional Audit-based Properties (Optional)" documented here: https://inedo.com/support/documentation/various/universal-packages/universal-feeds-package-ref/package-format#repackage - anytime a package is created with the `pack` or `repack` command, these properties should be added to the manifest unless a new argument `--no-audit` is supplied - add optional `--note` argument that populates the `createdReason` (not `creatednReason` as doc'd obviously, we'll fix the docs)
33	2.2.2	closed	Re-organize source code
The source code for this project should follow this structure from the repository root: ``` /src/dotnet/ - upack.sln -upack.nuspec -upack/.cs /src/go/.go .gitattributes .gitignore LICENSE README.md VERIFICATION.md ```
32	2.2.2	closed	Add "metadata" command that formats a remote package's metadata
This command should output metadata as key/value pairs to stdout. Here is the spec/docs that should also be added to the README: ### metadata Displays metadata for a remote ProGet universal package. upack metadata «package» [«version»] --source=«source» [--file=«file»] - `package` - Package name and group, such as group/name. - `version` - Package version. If not specified, the latest version is retrieved. - `source` - URL of a upack API endpoint. - `file` - The metadata file to display relative to the .upack root; the default is upack.json.
31	2.2.2	closed	FIX: Repack error
Repacking a package that has been repacked throws: ``` Unhandled Exception: System.ArgumentException: Argument is not a JToken. at Newtonsoft.Json.Linq.JContainer.EnsureValue(Object value) at Newtonsoft.Json.Linq.JContainer.System.Collections.IList.Add(Object value) at Inedo.ProGet.UPack.Repack.d__48.MoveNext() ```
26	2.2.0	open	Add "repack" Command
This is documented in the 1.2.0 of the Universal Package, and should add the appropriate entry to the repackageHistory node repack [DisplayName("package")] [Description("Path of a valid .upack file.")] [PositionalArgument(0)] public string Package { get; set; } [DisplayName("newVersion")] [Description("Version of repackaged package.")] [PositionalArgument(1)] public string Version { get; set; } [DisplayName("newGroup")] [Description("Group of repackaged package.")] [ExtraArgument] public string Group { get; set; } [DisplayName("newName")] [Description("Name of repackaged package.")] [ExtraArgument] public string Name { get; set; } [DisplayName("targetDirectory")] [Description("Directory where the .upack file will be created. If not specified, the current working directory is used.")] [ExtraArgument] public string TargetDirectory { get; set; } [DisplayName("note")] [Description("Comment or note about the repackaging; this will be written as the 'reason'.")] [ExtraArgument] public string TargetDirectory { get; set; }
27	2.2.0	closed	Add "hash" and "verify" commands [idea in progress]
hash - given a upack file, writes a sha1 hash to the console verify - something Perhaps we should ad this to the other coammdns as well? like a --verify or something to check a hash against a file
25	2.2.0	closed	Change "metadata" to "manifest" on "pack" command
We should have an alias for "metadata" for backwards compatibility
7	2.1.0	closed	Local registry (cache)

6	2.1.0	closed	Modify Go implementation to match C# argument parsing

5	2.1.0	closed	Machine package registry
- C# implementation - [ ] `upack install` caching - [ ] `upack list` - Go implementation - [ ] `upack install` caching - [ ] `upack list`
16	2.1.0	closed	Add --perserve-timestamps option to upack install and upack unpack

15	2.1.0	closed	[Windows version] upack install fails if it takes more than 100 seconds.

12	2.1.0	closed	Support "upack help commandname" as an alias of "upack commandname --help"

11	2.1.0	closed	FIX: upack crashes on timestamps with time zones in the local package registry