Downloads:

3,729

Downloads of v 3.2.0:

47

Last Update:

05 Aug 2020

Published Date:

05 Aug 2020

Reviewed Date:

02 Sep 2020

Reviewer:

gravatar

Package Maintainer(s):

Software Author(s):

  • Adrian Georgescu

Tags:

blink sip phone calls telephony softphone admin

Blink

(Maintainer responded, waiting for review/Maintainer update)

3.2.0 | Updated: 05 Aug 2020

Downloads:

3,729

Downloads of v 3.2.0:

47

Published:

05 Aug 2020

Reviewed:

02 Sep 2020

Reviewer:

gravatar

Maintainer(s):

Software Author(s):

  • Adrian Georgescu

Blink 3.2.0

(Maintainer responded, waiting for review/Maintainer update)

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test


Validation Testing Passed


Verification Testing Failed

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.

chocolatey-ops (reviewer) on 28 Jul 2020 12:13:51 +00:00:

blink 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.

  • In the ReleaseNotes element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL 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 28 Jul 2020 13:54:08 +00:00:

blink 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/21d4ac8e5cf2361c37f0cd23489f305b 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.

chocolatey-ops (reviewer) on 30 Jul 2020 16:46:30 +00:00:

blink 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.

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 30 Jul 2020 18:29:50 +00:00:

blink 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/a0351a460e194b528dfcdf52218962fd 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.

tunisiano (maintainer) on 30 Jul 2020 20:11:23 +00:00:

Stuck on KB2919355
Auto Verification Change - Verification tests have been set to rerun.

chocolatey-ops (reviewer) on 30 Jul 2020 21:54:40 +00:00:

blink 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/964177d1cc0fcee6f3f507bed11edd79 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.

tunisiano (maintainer) on 31 Jul 2020 10:03:36 +00:00:

User 'tunisiano' (maintainer) submitted package.

chocolatey-ops (reviewer) on 31 Jul 2020 10:34:55 +00:00:

blink 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.

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.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 31 Jul 2020 19:05:53 +00:00:

blink 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/547e24591edf0b43cec0702df46c03b8 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.

tunisiano (maintainer) on 05 Aug 2020 19:00:46 +00:00:

I have something weird here...
WARNING: Exit code '1' was considered valid by script, but not as a Chocolatey success code. Returning '0'.
after the installation of DotNet3.5 v3.5.20160716 [Approved]
and the script seems blocked ... nothing other after this...
I've tested with another windows 2012 R2 and i have the same...
On windows 10 it's OK, as it' not needed.

tunisiano (maintainer) on 05 Aug 2020 19:17:55 +00:00:

User 'tunisiano' (maintainer) submitted package.

chocolatey-ops (reviewer) on 05 Aug 2020 19:50:59 +00:00:

blink 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.

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.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 05 Aug 2020 21:27:24 +00:00:

blink 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/d4313dc0f72d383f53346bd7d2eb40d3 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.

tunisiano (maintainer) on 05 Aug 2020 21:28:30 +00:00:

I've made a mistake (copy/paste) of the version of a depedency...
the correction (and working version) is ready to be pushed on my git, if i don't do anything, it will be pushed at 4:15pm UTC+2
But one of the depedencies isn't up-to-date and of course, not working (bonjour), so i've asked the maintainer to update it, and set a reminder in a week if he doesn't answer to ask admins to add me.

tunisiano (maintainer) on 05 Aug 2020 21:31:15 +00:00:

Message : Chocolatey v0.10.15 Attempting to push blink.3.2.0.nupkg to https://push.chocolatey.org An error has occurred. It's possible the package version already exists on the repository. (39.44s)

tunisiano (maintainer) on 05 Aug 2020 23:07:07 +00:00:

User 'tunisiano' (maintainer) submitted package.

chocolatey-ops (reviewer) on 05 Aug 2020 23:43:07 +00:00:

blink 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.

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.

  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 06 Aug 2020 00:08:04 +00:00:

blink 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/eaca240e4603478d238f805d98a7c113 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.

tunisiano (maintainer) on 06 Aug 2020 10:02:43 +00:00:

The depedency seems not visible by the verifier, but the link is OK?
https://chocolatey.org/packages/bonjour/2.0.2.0
I've asked the maintainer to update it because it's not the latest one, but the 2.0.2.0 should be found...
Do you have an idea?
Thank you

AdmiringWorm (reviewer) on 31 Aug 2020 07:33:39 +00:00:

Auto Verification Change - Verification tests have been set to rerun.

chocolatey-ops (reviewer) on 31 Aug 2020 12:16:48 +00:00:

blink 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/05d625d8e7f6c5bae1cf6bedfa125621 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.

tunisiano (maintainer) on 31 Aug 2020 13:11:34 +00:00:

This one fails because the bonjour dependency seems broken

gep13 (reviewer) on 01 Sep 2020 07:08:46 +00:00:

Can you help me out here with what you mean? Are you saying that you are first going to work on getting the bonjour package working? And then we can come back here and look at this package?

tunisiano (maintainer) on 01 Sep 2020 10:01:34 +00:00:

Yes, exactly, but i'm currently stuck with bonjour.
i don't find a way to update it correctly.

gep13 (reviewer) on 02 Sep 2020 06:35:11 +00:00:

Ok, well let's continue the discussion about Bonjour elsewhere, as this doesn't feel like the right place to do it.

Have you asked for help/assistance on the Gitter room? How about documenting the current state of the package in a GitHub issue, and hopefully folks will be able to jump in and help with it.

tunisiano (maintainer) on 18 Sep 2020 07:15:47 +00:00:

Now that the Bonjour package is approved, this one should be working
Auto Verification Change - Verification tests have been set to rerun.

chocolatey-ops (reviewer) on 18 Sep 2020 10:54:54 +00:00:

blink 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/a1c412fcbd7aff3340c724f54c723c19 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.

tunisiano (maintainer) on 18 Sep 2020 15:38:26 +00:00:

It needs a reboot, but it works in my chocolatey-test-environment

Description

Blink is the best real-time communications client using SIP protocol. You can use it with many SIP providers, on the LAN using Bonjour and SIP2SIP free service.

Features

  • Voice and Video
  • IM and Presence
  • File Transfers
  • Screen Sharing
  • Conferencing

Wiki
Source code repository

Package-specific issue

If this package isn't up-to-date for some days, Create an issue

Support me on Patreon


tools\blink.exe
tools\chocolateyInstall.ps1
$packageName        = $env:ChocolateyPackageName
$installerType      = 'exe'
$silentArgs         = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-'
$validExitCodes     = @(0)
$toolsPath          = Split-Path $MyInvocation.MyCommand.Definition
$url                = Join-Path $toolsPath 'blink.exe'
$checksum           = '88a14a67916a3700d98b6deede1a5f689d6f9674e29da14caf76d7e80f183470'
$checksumType       = 'sha256'

$packageArgs = @{
    packageName     = $packageName
    fileType        = $installerType
    url             = $url
    silentArgs      = $silentArgs
    validExitCodes  = $validExitCodes
    softwareName    = "$packageName*"
    checksum        = $checksum
    checksumType    = $checksumType
}

Install-ChocolateyPackage @packageArgs
tools\chocolateyUninstall.ps1

$packageName = $env:ChocolateyPackageName
$fileType = 'exe'
$silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-'
$validExitCodes = @(0)
$osBitness = Get-ProcessorBits
if ($osBitness -eq 64) {
  $unPath = 'HKLM:SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall'
} else {
  $unPath = 'HKLM:SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall'
}
$unString = (Get-ItemProperty $unPath\* | Select-Object DisplayName, UninstallString | Where-Object {$_.DisplayName -like "$packageName*"}).UninstallString
Uninstall-ChocolateyPackage "$packageName" "$fileType" "$silentArgs" "$unString" -validExitCodes $validExitCodes
tools\LICENSE.txt
Copyright 2010-2020 AG Projects (http://ag-projects.com)

License: GPL-3+

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 3 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
    GNU General Public License for more details.

    For a copy of the license see https://www.gnu.org/licenses/gpl.html
tools\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The installer have been downloaded from the GitHub mirror and can be verified like this:

1. Download the following installer(s):

x86: https://blink.sipthor.net/download.phtml?download&os=nt

2. You can use one of the following methods to obtain the checksum(s):
  - Use powershell function 'Get-Filehash'
  - Use chocolatey utility 'checksum.exe'

checksumtype: sha256
checksum32: 88a14a67916a3700d98b6deede1a5f689d6f9674e29da14caf76d7e80f183470

The included 'LICENSE.txt' file have been obtained from:
https://github.com/AGProjects/blink-qt/blob/master/LICENSE

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
Blink 3.2.0 47 Wednesday, August 5, 2020 Responded
Blink 0.9.1.2 377 Friday, February 20, 2015 Approved
blink 0.8.2.20140609 600 Monday, June 9, 2014 Unknown
blink 0.8.1.20140424 341 Thursday, April 24, 2014 Unknown
blink 0.7.0.2014031501 372 Saturday, March 15, 2014 Unknown
blink 0.7.0 361 Saturday, March 15, 2014 Unknown

Software

Changelog
Development Notes
Development ToDo

Package


Discussion for the Blink Package

Ground Rules:

  • This discussion is only about Blink and the Blink 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 Blink, 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