Notices: This section not yet converted to new layout. Download stats are rolling back out.

Amazing Marvin

Package test results have failed.

This package was rejected on 1/20/2019. The reviewer gep13 has listed the following reason(s):

d_w (maintainer) on 12 Jan 2019 21:31:36 +00:00:

User 'd_w' (maintainer) submitted package.

chocolatey-ops (reviewer) on 12 Jan 2019 22:06:52 +00:00:

amazingmarvin 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...
  • The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Description should be sufficient to explain the software. Please fill in the description with more information about the software. Feel free to use use markdown. 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

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 12 Jan 2019 22:44:14 +00:00:

amazingmarvin 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/e50668d6168a55faf02ca23749436785 for details.
This is an FYI only. There is no action you need to take.

d_w (maintainer) on 12 Jan 2019 23:01:10 +00:00:

User 'd_w' (maintainer) submitted package.

chocolatey-ops (reviewer) on 12 Jan 2019 23:37:08 +00:00:

amazingmarvin 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...
  • The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. 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

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 13 Jan 2019 00:39:54 +00:00:

amazingmarvin 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/8b232bccc6e5dbb849f20dcbf261a457 for details.
This is an FYI only. There is no action you need to take.

d_w (maintainer) on 13 Jan 2019 08:32:50 +00:00:

User 'd_w' (maintainer) submitted package.

chocolatey-ops (reviewer) on 13 Jan 2019 09:04:21 +00:00:

amazingmarvin 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...
  • The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. 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

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 13 Jan 2019 09:08:05 +00:00:

amazingmarvin 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/0c74dfce3dfc08a7307fbec622c6b9f5 for details.
This is an FYI only. There is no action you need to take.

gep13 (reviewer) on 14 Jan 2019 08:59:28 +00:00:

Since this is a new package submission, can we please get a licenseUrl added to the nuspec?

d_w (maintainer) on 15 Jan 2019 17:03:08 +00:00:

I couldn't find any information about licensing info for that app, but I asked authors about that.

gep13 (reviewer) on 16 Jan 2019 07:27:14 +00:00:

That is great. If you hear anything back from them, can you add that into the next package version?
Status Change - Changed status of package from 'submitted' to 'approved'.

d_w (maintainer) on 17 Jan 2019 18:29:30 +00:00:

@gep13:
Yes, I have a icon/license url and updated link, but I am unable to cpush:

Failed to process request. 'A package with id 'amazingmarvin' and version '1.36.1.0' already exists and cannot be modified.'.
The remote server returned an error: (409) Conflict..

How can I force to reupload package?

gep13 (reviewer) on 17 Jan 2019 19:38:00 +00:00:

Status Change - Changed status of package from 'approved' to 'submitted'.

gep13 (reviewer) on 17 Jan 2019 19:38:34 +00:00:

I have set the package state back to submitted, which should allow you to push the package again.

Thanks

d_w (maintainer) on 19 Jan 2019 10:24:33 +00:00:

User 'd_w' (maintainer) submitted package.

chocolatey-ops (reviewer) on 19 Jan 2019 10:59:55 +00:00:

amazingmarvin 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...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. 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

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 19 Jan 2019 11:30:53 +00:00:

amazingmarvin has failed 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/98149fb28d6a0a62eaac26d824fe25a0 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

d_w (maintainer) on 19 Jan 2019 13:43:27 +00:00:

Now, there's a newer version - please let me update that one ;)

gep13 (reviewer) on 19 Jan 2019 14:26:10 +00:00:

Sorry, I am not sure if I follow. Do you want me to reject this package version, in favour of a new one?

d_w (maintainer) on 19 Jan 2019 19:47:42 +00:00:

Yes, please

gep13 (reviewer) on 20 Jan 2019 11:12:56 +00:00:

Rejecting as per maintainer request.
Status Change - Changed status of package from 'submitted' to 'rejected'.


Marvin incorporates principles from behavioral psychology to help you beat procrastination, feel in control and finish your todo list.

Files

Hide
  • icon.png
  • tools\chocolateyinstall.ps1 Show
    $ErrorActionPreference = 'Stop';
    
    $packageName= 'amazingmarvin'
    $toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
    $url        = 'http://amazingmarvin.s3-website-us-east-1.amazonaws.com/MarvinSetup.exe'
    
    $packageArgs = @{
      packageName   = $packageName
      unzipLocation = $toolsDir
      fileType      = 'EXE'
      url           = $url
      softwareName  = 'amazingmarvin*'
      checksum      = '524C13903FAD3C8B9428B6580D4CE31DEE3613C0B5C278E59D5F0201DC11C9FB'
      checksumType  = 'sha256'
      silentArgs    = '/S'
      validExitCodes= @(0)
    }
    
    Install-ChocolateyPackage @packageArgs

Virus Scan Results

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.

Dependencies

This package has no dependencies.

Package Maintainer(s)

Software Author(s)

  • Amazing Marvin

Tags

Version History

Version Downloads Last updated Status

Discussion for the Amazing Marvin Package

Ground rules:

  • This discussion is only about Amazing Marvin and the Amazing Marvin 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 Amazing Marvin, 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
Chocolatey.org uses cookies to enhance the user experience of the site.
Ok