Downloads:

19

Downloads of v 1.6:

19

Last Update:

19 Nov 2020

Published Date:

19 Nov 2020

Reviewed Date:

20 Nov 2020

Reviewer:

gravatar

Package Maintainer(s):

Software Author(s):

  • Dec Software

Tags:

lzip7z 7zip 7-zip 7z lz

lzip7z (Install)

(Waiting for Maintainer to take corrective action)

1.6 | Updated: 19 Nov 2020

Downloads:

19

Downloads of v 1.6:

19

Published:

19 Nov 2020

Reviewed:

20 Nov 2020

Reviewer:

gravatar

Maintainer(s):

Software Author(s):

  • Dec Software

lzip7z (Install) 1.6

(Waiting for Maintainer to take corrective action)

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.

  • Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
  • This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
  • You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
  • There are also no guarantees that it will be approved.

There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.

zverev-iv (maintainer) on 23 Oct 2020 18:39:11 +00:00:

User 'zverev-iv' (maintainer) submitted package.

chocolatey-ops (reviewer) on 23 Oct 2020 19:11:33 +00:00:

lzip7z has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
    • docsUrl - points to the location of the wiki or docs of the software
    • mailingListUrl - points to the forum or email list group for the software
    • bugTrackerUrl - points to the location where issues and tickets can be accessed
    • projectSourceUrl - points to the location of the underlying software source

chocolatey-ops (reviewer) on 23 Oct 2020 22:13:46 +00:00:

lzip7z has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/10c5d5577bf1f2963d91ee6db40da9c2 for details.
This is an FYI only. There is no action you need to take.

mwallner (reviewer) on 16 Nov 2020 20:42:53 +00:00:

Hi,
you're using ConvertFrom-Json in your chocolateyinstall.ps1 - this function unfortunately is not available in PowerShell v2 - which should be the baseline for all packages on the community repostiory.
could you please move the content from packageArgs.json and define a $packageArgs = @{} or similar?
thanks!

zverev-iv (maintainer) on 16 Nov 2020 21:27:08 +00:00:

Hi, but see other my approved packages - half of it uses the same method. + Powershell v2 is used only in unsupported versions of Windows (7 and 2008)

mwallner (reviewer) on 18 Nov 2020 06:33:03 +00:00:

Hi,
the moderation process unfortunately isn't a perfect science. when moderating package we've got guidelines and rules to follow. See moderation requirements one of the points stated there is that the Chocolatey scripts should be able to run on POSH v2.
If one package passes by one moderator doesn't mean it will pass by another, we unfortunately are not able to catch each and every issue.
If the application in question would not be intended to run on 'older' OS versions that'd be a reason to still go forward, given that the cmdlet in question is available since POSH v3, yet I have to inform you that both Windows 7 and Server 2012r2 still do have extended business support until 2023.
Is there a specific reason you want to keep the installation URLs and Checksums in an external file?
I'd suggest you simply but them in a map like this:

$packageArgs = @{
          "url"= "https://www.tc4shell.com/binary/Lzip.zip"
          "checksum"= "839b684384701e4b55a96e351517dc3c97ed727dfc834d96569d02aa2e5baa70"
         "checksumType"= "sha256"
          "url64bit"= "https://www.tc4shell.com/binary/Lzip.zip"
         "checksum64"= "839b684384701e4b55a96e351517dc3c97ed727dfc834d96569d02aa2e5baa70"
         "checksumType64"= "sha256"
}

that way, you can even leave the rest of your code, just remove the ConvertFrom-Json.

zverev-iv (maintainer) on 18 Nov 2020 18:26:29 +00:00:

Hello!
First of all, thank you for your time.

  1. I have re-read the rules for creating packages and found only:
    Note: Please maintain compatibility with Posh v2. Not every OS we support is on Posh v2 (nor does OOB come with Posh v3 +). It's best to work with the widest compatibility of all available systems.
    To put it simply, I believe that "must use Posh v2" is not required for package creation.

  2. Installation URLs and Checksums in my mind are in the package metadata, not part of working code.
    Hardcoded metadata makes code less reusable, and leads to more human errors in general.

  3. In the future, I would like to implement my own auto-update for my packages.
    I have read about the Automatic Package Updater Module (AU), but I didn't like it for these reasons:
    3.1.AU only works with Posh v5 (for patching code written in Posh v2?)
    3.2. AU parses code with Regex and then patches it. - I find this to not be the best method due to the facts that:
    3.2.1. It's Regex (unreadable by design)
    3.2.2. It's code patching. I don't want something (my hands, or any automation) to change code only for URL and checksum updates. (Do I need to commit to those changes? Git log will be less usable.)

  4. I believe that today Posh v2 is overrated because:
    4.1. Over the course of 5 years, a method of validation was never released - https://github.com/chocolatey/package-validator/issues/1
    4.2. Windows PowerShell 2.0 was deprecated in August 2017 - https://docs.microsoft.com/en-us/powershell/scripting/windows-powershell/starting-the-windows-powershell-2.0-engine
    4.3. Posh v3 works on Windows 7, Server 2012, and 2008/R2. Only XP, Vista, and Server 2003 are incompatible.

Based on this, I have determined that metadata should be stored in a separate file in a deserializable form (like JSON), that can be generated with any popular programming language.
The only foreseeable loss in this situation is a loss of compatibility with Posh v2.

mwallner (reviewer) on 19 Nov 2020 11:39:38 +00:00:

Unfortunately we can't approve the package unless the comments I mentioned previously are addressed.

I'd suggest you implement the changes I recommended as they do not break the functionality of this (and your other) package(s) and the community could benefit from it.

Whatever you can do in PowerShell you can do in a Chocolatey package ... inside your organization. The Community Repository has rules and standards that we follow as a public feed for the benefit of the many and not the few.

  • This package requires the ConvertFrom-Json cmdlet which was introduced in PS v3 - so there is no PS v2 compatibility;
  • It causes the moderator more work to have to check these files separately (you need to make sure there is a checksum for example. as the presence of one is not checked as yet);
  • It goes against standard practice - this may not be explicitly stated but we have over 100k packages and the VAST majority of those have the same format where those details are in the chocolateyInstall.ps1 so I would suggest it's implicit;
  • When you run choco new it produces a chocolateyInstall.ps1 file that should be used as a template as far as possible;
  • It breaks some of the tools we have that expect those values in that file;

If you want to discuss the guidelines/rules for creating packages this is not the right place, please feel free to create a GitHub issue.

zverev-iv (maintainer) on 19 Nov 2020 14:41:49 +00:00:

User 'zverev-iv' (maintainer) submitted package.

chocolatey-ops (reviewer) on 19 Nov 2020 15:17:30 +00:00:

lzip7z has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
    • docsUrl - points to the location of the wiki or docs of the software
    • mailingListUrl - points to the forum or email list group for the software
    • bugTrackerUrl - points to the location where issues and tickets can be accessed
    • projectSourceUrl - points to the location of the underlying software source

mwallner (reviewer) on 20 Nov 2020 05:37:07 +00:00:

great, POSH v2 compatibility achieved. (1/5 done)
now you just need to consider the other 4/5 points I stated in order to get this approved.

I get where you're coming from. Separating the metadata from code makes sense.
Yet we have to keep things consistent across the community repository as far as possible, even if this is not the best design possible - for now it's the one we stick with.

chocolatey-ops (reviewer) on 21 Nov 2020 03:01:36 +00:00:

lzip7z has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/d1937202e326490865a9d21c349291a6 for details.
This is an FYI only. There is no action you need to take.

Description

Lzip7z is a small plugin for the popular 7-Zip archiver. You can use Lzip7z to open, modify, or create .lz archives that are widely used on Unix-like systems.


tools\chocolateybeforemodify.ps1
$ErrorActionPreference = 'Stop';

$installed = Get-Content -Path $env:ChocolateyPackageFolder\tools\installed.csv -Raw | ConvertFrom-Csv -Delimiter ';'

$spliter = "path to executable:"
$7zLocation = "$(Split-Path -parent ((7z --shimgen-noop | Select-String $spliter) -split $spliter | ForEach-Object Trim)[1])"
$installLocation = "$(Join-Path $7zLocation "Formats")"

Write-Output "Remove libraries"
ForEach($file in $installed) {
  Remove-Item "$(Join-Path $installLocation $file.Name)" -Force
}
 Write-Output "Remove completed"
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';

$meta = Get-Content -Path "$($env:ChocolateyPackageFolder)\tools\packageArgs.csv" -Raw
$packageArgs = @{}
(ConvertFrom-Csv $meta -Delimiter ';').psobject.properties | ForEach-Object { $packageArgs[$_.Name] = $_.Value }

$filename = if ((Get-OSArchitectureWidth 64) -and $env:chocolateyForceX86 -ne $true) {
       Split-Path $packageArgs["url64bit"] -Leaf }
else { Split-Path $packageArgs["url"] -Leaf }

$packageArgs["packageName"] = "$($env:ChocolateyPackageName)"
$packageArgs["fileFullPath"] = "$(Join-Path (Split-Path -parent $MyInvocation.MyCommand.Definition) $filename)"

$archiveLocation = Get-ChocolateyWebFile @packageArgs
$extractLocation = "$(Join-Path (Split-Path -parent $archiveLocation) "Formats")"

$spliter = "path to executable:"
$7zLocation = "$(Split-Path -parent ((7z --shimgen-noop | Select-String $spliter) -split $spliter | ForEach-Object Trim)[1])"
$installLocation = "$(Join-Path $7zLocation "Formats")"

Write-Output "Install libraries"

New-Item -ItemType directory -Path $installLocation -Force | Out-Null
Get-ChocolateyUnzip -FileFullPath $archiveLocation -Destination $extractLocation | Out-Null
if ((Get-OSArchitectureWidth 64) -and $env:chocolateyForceX86 -ne $true) {
       $extractLocationArch = Join-Path $extractLocation '*.64.dll'
} else {
       $extractLocationArch = Join-Path $extractLocation '*.32.dll'
}

Get-ChildItem -Recurse $extractLocationArch | Select-Object Name | ConvertTo-Csv -Delimiter ';' | Out-File $env:ChocolateyPackageFolder\tools\installed.csv
Copy-Item "$($extractLocationArch)" "$($installLocation)" -Recurse -Force
Copy-Item "$(Join-Path $extractLocation '*.ini')" "$($installLocation)" -Recurse -Force

Write-Output "Install completed"
tools\packageArgs.csv
#TYPE System.Management.Automation.PSCustomObject
"url";"checksum";"checksumType";"url64bit";"checksum64";"checksumType64"
"https://www.tc4shell.com/binary/Lzip.zip";"839b684384701e4b55a96e351517dc3c97ed727dfc834d96569d02aa2e5baa70";"sha256";"https://www.tc4shell.com/binary/Lzip.zip";"839b684384701e4b55a96e351517dc3c97ed727dfc834d96569d02aa2e5baa70";"sha256"

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
lzip7z (Install) 1.6 19 Thursday, November 19, 2020 Waiting for Maintainer gravatar

Current version

Plugin version: 1.6
Distribution package release date: 10 Dec 2017

Discussion for the lzip7z (Install) Package

Ground Rules:

  • This discussion is only about lzip7z (Install) and the lzip7z (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or lzip7z (Install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus