Downloads:
292,438
Downloads of v 3.18.0:
47
Last Update:
15 Sep 2021
Package Maintainer(s):
Software Author(s):
Tags:
protoc protobuf foss cross-platform- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Protocol Buffers
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
292,438
Downloads of v 3.18.0:
47
Maintainer(s):
Software Author(s):
Protocol Buffers
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
This package was rejected on 20 Oct 2021. The reviewer chocolatey-ops has listed the following reason(s):
Protocol Buffers (a.k.a., protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data.
This is chocolatey package for the prebuilt Protocol Buffers Compiler.
Features
- Flexible, efficient, automated mechanism for serializing structured data – think XML, but smaller, faster, and simpler.
- Define how you want your data to be structured once, then use special generated source code to easily write and read your structured data to and from a variety of data streams and using a variety of languages.
- Update your data structure without breaking deployed programs that are compiled against the "old" format.
Copyright 2008 Google Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.
* Neither the name of Google Inc. nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Code generated by the Protocol Buffer compiler is owned by the owner
of the input file used when generating it. This code is not
standalone and requires a support library to be linked with it. This
support library is itself covered by the above license.
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
The zip file have been downloaded from the github release page on <https://github.com/protocolbuffers/protobuf/releases>
and can be verified like this:
1. Download the following:
32-bit zip file: <https://github.com//protocolbuffers/protobuf/releases/download/v3.18.0/protoc-3.18.0-win32.zip>
64-bit zip file: <https://github.com//protocolbuffers/protobuf/releases/download/v3.18.0/protoc-3.18.0-win64.zip>
2. You can use one of the following methods to obtain the checksum
- Use powershell function 'Get-Filehash'
- Use chocolatey utility 'checksum.exe'
checksum type: sha256
checksum32: EBEDFE374DD2953FE67F09C19A8DD8346252429CC587456BC5DF43C65C527059
checksum64: 222ECF84ACDAACF2883B95FD83E14F1B3FFB8598F92AD8F595A90E8FD0A8FEB8
File 'LICENSE' is obtained from <https://github.com/protocolbuffers/protobuf/blob/master/LICENSE>
md5: 463D25D036A9FFD5E451108366E356A3 | sha1: 851B20495E8EBCB1A98512E9F06FA954BE9F61A1 | sha256: EBEDFE374DD2953FE67F09C19A8DD8346252429CC587456BC5DF43C65C527059 | sha512: B0A060F812E92913192E88D7A168CCCBD02813F124420895942ABDF71B18E78F532FFD11D48E3F0E74DA4A450961E8E02A4EA2375A9703532466F133EBE11421
md5: 1223F7238555182708AC45856EAF8809 | sha1: 8BEBADE04D5BD7A05855EE0D90B1A93FB983EADB | sha256: 222ECF84ACDAACF2883B95FD83E14F1B3FFB8598F92AD8F595A90E8FD0A8FEB8 | sha512: 271048B68DB66DE049EA7644A2BEBF65DEC76433CC42E75114CA979389B949388830B6B08E27447BAA1561761364D4E27924F285228222B2B02E135C4E584F7A
No results available for this package. We are building up results for older packages over time so expect to see results. If this is a new package, it should have results within a day or two.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
Protocol Buffers 26.1.0 | 7462 | Thursday, March 28, 2024 | Approved | |
Protocol Buffers 26.0.0 | 3957 | Wednesday, March 13, 2024 | Approved | |
Protocol Buffers 25.3.0 | 5685 | Friday, February 16, 2024 | Approved | |
Protocol Buffers 25.2.0 | 7430 | Wednesday, January 10, 2024 | Approved | |
Protocol Buffers 25.1.0 | 6485 | Thursday, November 16, 2023 | Approved | |
Protocol Buffers 25.0.0 | 4204 | Thursday, November 2, 2023 | Approved | |
Protocol Buffers 24.4.0 | 4503 | Wednesday, October 4, 2023 | Approved | |
Protocol Buffers 24.3.0 | 5981 | Friday, September 8, 2023 | Approved | |
Protocol Buffers 24.2.0 | 1641 | Saturday, August 26, 2023 | Approved | |
Protocol Buffers 24.1.0 | 1501 | Saturday, August 19, 2023 | Approved | |
Protocol Buffers 24.0.0 | 1964 | Wednesday, August 9, 2023 | Approved | |
Protocol Buffers 23.4.0 | 20189 | Friday, July 7, 2023 | Approved | |
Protocol Buffers 23.3.0 | 5362 | Thursday, June 15, 2023 | Approved | |
Protocol Buffers 23.2 | 3652 | Friday, May 26, 2023 | Approved | |
Protocol Buffers 23.1 | 1861 | Wednesday, May 17, 2023 | Approved | |
Protocol Buffers 23.0 | 1229 | Tuesday, May 9, 2023 | Approved | |
Protocol Buffers 22.4 | 953 | Friday, May 5, 2023 | Approved | |
Protocol Buffers 22.3 | 2965 | Thursday, April 13, 2023 | Approved | |
Protocol Buffers 22.2 | 5354 | Saturday, March 11, 2023 | Approved | |
Protocol Buffers 22.1 | 687 | Wednesday, March 8, 2023 | Approved | |
Protocol Buffers 22.0 | 2617 | Friday, February 17, 2023 | Approved | |
Protocol Buffers 21.12 | 14420 | Friday, December 16, 2022 | Approved | |
Protocol Buffers 3.20.2 | 14028 | Thursday, September 15, 2022 | Approved | |
Protocol Buffers 3.20.1 | 15109 | Friday, April 22, 2022 | Approved | |
Protocol Buffers 3.20.0 | 1405 | Saturday, March 26, 2022 | Approved | |
Protocol Buffers 3.19.4 | 33348 | Friday, January 28, 2022 | Approved | |
Protocol Buffers 3.19.3 | 848 | Tuesday, January 11, 2022 | Approved | |
Protocol Buffers 3.19.2 | 420 | Thursday, January 6, 2022 | Approved | |
Protocol Buffers 3.19.1 | 2152 | Friday, October 29, 2021 | Approved | |
Protocol Buffers 3.19.0 | 593 | Thursday, October 21, 2021 | Approved | |
Protocol Buffers 3.18.1 | 868 | Tuesday, October 5, 2021 | Approved | |
Protocol Buffers 3.17.3 | 8401 | Tuesday, June 8, 2021 | Approved | |
Protocol Buffers 3.17.2 | 603 | Thursday, June 3, 2021 | Approved | |
Protocol Buffers 3.17.1 | 475 | Monday, May 24, 2021 | Approved | |
Protocol Buffers 3.17.0 | 514 | Thursday, May 13, 2021 | Approved | |
Protocol Buffers 3.16.0 | 443 | Friday, May 7, 2021 | Approved | |
Protocol Buffers 3.15.8 | 1059 | Thursday, April 8, 2021 | Approved | |
Protocol Buffers 3.15.7 | 300 | Saturday, April 3, 2021 | Approved | |
Protocol Buffers 3.15.6 | 14403 | Friday, March 12, 2021 | Approved | |
Protocol Buffers 3.15.5 | 467 | Friday, March 5, 2021 | Approved | |
Protocol Buffers 3.15.4 | 232 | Thursday, March 4, 2021 | Approved | |
Protocol Buffers 3.15.3 | 339 | Friday, February 26, 2021 | Approved | |
Protocol Buffers 3.15.2 | 220 | Wednesday, February 24, 2021 | Approved | |
Protocol Buffers 3.15.1 | 94 | Saturday, February 20, 2021 | Approved | |
Protocol Buffers 3.15.0 | 1320 | Friday, February 19, 2021 | Approved | |
Protocol Buffers 3.14.0 | 2082 | Thursday, December 3, 2020 | Approved | |
Protocol Buffers 3.12.3 | 14783 | Wednesday, June 3, 2020 | Approved | |
Protocol Buffers 3.12.2 | 840 | Wednesday, May 27, 2020 | Approved | |
Protocol Buffers 3.12.1 | 781 | Thursday, May 21, 2020 | Approved | |
Protocol Buffers 3.12.0 | 1110 | Saturday, May 16, 2020 | Approved | |
Protocol Buffers 3.12.0-rc-2 | 163 | Wednesday, May 13, 2020 | Approved | |
Protocol Buffers 3.12.0-rc-1 | 148 | Monday, May 4, 2020 | Approved | |
Protocol Buffers 3.11.4 | 17500 | Saturday, February 15, 2020 | Approved | |
Protocol Buffers 3.11.3 | 420 | Monday, February 3, 2020 | Approved | |
Protocol Buffers 3.11.2 | 778 | Saturday, December 14, 2019 | Approved | |
Protocol Buffers 3.11.1 | 372 | Tuesday, December 3, 2019 | Approved | |
Protocol Buffers 3.11.0 | 342 | Tuesday, November 26, 2019 | Approved | |
Protocol Buffers 3.11.0-rc-2 | 174 | Saturday, November 23, 2019 | Approved | |
Protocol Buffers 3.11.0-rc-1 | 192 | Thursday, November 21, 2019 | Approved | |
Protocol Buffers 3.10.1 | 547 | Wednesday, October 30, 2019 | Approved | |
Protocol Buffers 3.10.0 | 709 | Thursday, October 3, 2019 | Approved | |
Protocol Buffers 3.9.2 | 309 | Monday, September 30, 2019 | Approved | |
Protocol Buffers 3.8.0 | 2789 | Friday, June 7, 2019 | Approved | |
Protocol Buffers 3.6.1 | 13774 | Monday, September 24, 2018 | Approved | |
Protocol Buffers 3.6.0 | 9060 | Wednesday, July 25, 2018 | Approved | |
Protocol Buffers 3.5.1 | 3649 | Monday, March 19, 2018 | Approved | |
Protocol Buffers 3.2.0 | 11155 | Monday, April 3, 2017 | Approved | |
Protocol Buffers 3.1.0 | 1329 | Thursday, November 3, 2016 | Approved | |
Protocol Compiler 2.6.1 | 1009 | Friday, April 17, 2015 | Approved |
-
- chocolatey-core.extension (≥ 1.3.3)
Ground Rules:
- This discussion is only about Protocol Buffers and the Protocol Buffers 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 Protocol Buffers, 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.
chocolatey-community (maintainer) on 15 Sep 2021 18:10:52 +00:00:
User 'chocolatey-community' (maintainer) submitted package.
chocolatey-ops (reviewer) on 15 Sep 2021 18:47:11 +00:00:
protoc 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.
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.
chocolatey-ops (reviewer) on 15 Sep 2021 19:00:18 +00:00:
protoc has failed automated package testing (verification).
Please visit https://gist.github.com/6aac3e4890adfb00e7a53953aeff877d for details.
The package status will be changed and will be waiting on your next actions.
chocolatey-ops (reviewer) on 05 Oct 2021 18:48:20 +00:00:
We've found protoc v3.18.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
chocolatey-ops (reviewer) on 20 Oct 2021 18:52:29 +00:00:
Unfortunately there has not been progress to move protoc v3.18.0 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.
Status Change - Changed status of package from 'submitted' to 'rejected'.