Downloads of v 1.30:


Last Update:

01 Feb 2015

Package Maintainer(s):

Software Author(s):

  • D. Richard Hipp


chocolatey fossil scm sqlite

Fossil SCM

This is not the latest version of Fossil SCM available.

  • 1
  • 2
  • 3

1.30 | Updated: 01 Feb 2015



Downloads of v 1.30:


Software Author(s):

  • D. Richard Hipp

  • 1
  • 2
  • 3
Fossil SCM 1.30

This is not the latest version of Fossil SCM available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files


To install Fossil SCM, run the following command from the command line or from PowerShell:


To upgrade Fossil SCM, run the following command from the command line or from PowerShell:


To uninstall Fossil SCM, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade fossil -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade fossil -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure fossil installed
    name: fossil
    state: present
    version: 1.30
    source: STEP 3 URL

See docs at

chocolatey_package 'fossil' do
  action    :install
  version  '1.30'
  source   'STEP 3 URL'

See docs at

    Name: fossil,
    Version: 1.30,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller fossil
   Name     = 'fossil'
   Ensure   = 'Present'
   Version  = '1.30'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'fossil':
  provider => 'chocolatey',
  ensure   => '1.30',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install fossil version="1.30" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved by moderator ferventcoder on 10 Feb 2015.


Fossil is a cross-platform server that runs on Linux, BSD derivatives, Mac and Windows. It is capable of performing distributed version control, bug tracking, wiki services, and blogging. The software has a built-in web interface, which reduces project tracking complexity and promotes situational awareness. A user may simply type "fossil ui" from within any check-out and Fossil automatically opens the user's web browser in a page that gives detailed history and status information on that project.

# Virtual Package
write-host -foregroundColor YELLOW "NOTICE: Uninstall also fossil.portable package with command 'CUNINST fossil.portable' to complete uninstall"

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
Fossil SCM 2.15.2 76 Tuesday, June 15, 2021 Approved
Fossil SCM 2.15.1 108 Friday, April 30, 2021 Approved
Fossil SCM 2.15 138 Saturday, March 27, 2021 Approved
Fossil SCM 2.14 167 Wednesday, January 20, 2021 Approved
Fossil SCM 2.13 364 Sunday, November 1, 2020 Approved
Fossil SCM 2.12.1 215 Saturday, August 22, 2020 Approved
Fossil SCM 2.12 82 Sunday, August 16, 2020 Approved
Fossil SCM 2.11.1 202 Tuesday, June 9, 2020 Approved

Fossil v 1.30 (2015-01-19 11:29:00)

Key changes in this release include:

  • Added the fossil bundle command.
  • Added the fossil purge command.
  • Added the fossil publish command.
  • Added the fossil unpublished command.
  • Enhance the /tree webpage to show the age of each file with the option to sort by age.
  • Enhance the /brlist webpage to show additional information about each branch and to be sortable by clicking on column headers.
  • Add support for Docker. Just install docker and type "sudo docker run -d -p 8080:8080 nijtmans/fossil" to get it running.
  • Add the fossil fusefs DIRECTORY command that mounts a Fuse Filesystem at the given DIRECTORY and populates it with read-only copies of all historical check-ins. This only works on systems that support FuseFS.
  • Add the administrative log that records all configuration.
  • Added the /sitemap webpage.
  • Added the /bloblist web page.
  • Let fossil new no longer create an initial empty commit by default. The first commit after checking out an empty repository will become the initial commit.
  • Added the fossil all dbstat and fossil all info commands.
  • Update SQLite to version 3.8.8.
  • Added the --verily option to the fossil clean command.
  • Add the "autosync-tries" setting to control the number of autosync attempts before returning an error.
  • Added a compile-time option (--with-miniz) to build using miniz instead of zlib. Disabled by default.
  • Support customization of commands and webpages, including the ability to add new ones, via the "TH1 hooks" feature. Disabled by default. Enabled via a compile-time option.
  • Add the [checkout], [render], [styleHeader], [styleFooter], [trace], [getParameter], [setParameter], [artifact], and [globalState] commands to TH1, primarily for use by TH1 hooks.
  • Automatically adjust the width of command-line timeline output according to the detected width of the terminal.
  • Prompt the user to optionally fix invalid UTF-8 at check-in.
  • Added a line-number toggle option to the /info and /artifact pages.
  • Most commands now issue errors rather than silently ignoring unrecognized command-line options.
  • Use full 40-character SHA1 hashes (instead of abbreviations) in most internal URLs.
  • The "ssh:" sync method on windows now uses "plink.exe" instead of "ssh" as the secure-shell client program.
  • Prevent a partial clone when the connection is lost.
  • Make the distinction between 301 and 302 redirects.
  • Allow commits against a closed check-in as long as the commit goes onto a different branch.
  • Improved cache control in the web interface reduces unnecessary requests for common resources like the page logo and CSS.
  • Fix a rare and long-standing sync protocol bug that would silently prevent the sync from running to completion. Before this bug-fix it was sometimes necessary to do "fossil sync --verily" to get two repositories in sync.
  • Add the files_of_checkin virtual table - useful for ad hoc queries in the fossil sql interface, and also used internally.
  • Added the "$secureurl" TH1 variable for use in headers and footers.
  • (Internal:) Add the ability to include resources as separate files in the source tree that are converted into constant byte arrays in the compiled binary. Use this feature to store the Tk script that implements the --tk diff option in a separate file for easier editing.
  • (Internal:) Implement a system of compile-time checks to help ensure the correctness of printf-style formatting strings.
  • Fix CVE-2014-3566, also known as the POODLE SSL 3.0 vulnerability.
  • Numerous documentation fixes and improvements.
  • Other obscure and minor bug fixes - see the timeline for details.
Discussion for the Fossil SCM Package

Ground Rules:

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