Page MenuHomeSolus

Closed, WontfixPublic



Use-case: Tarsnap is a cloud storage solution that allows you to make backups from the command line with an emphasis on encryption.

Is it open source?: Yes, see license below:

Redistribution and use in source and binary forms, without modification,
is permitted for the sole purpose of using the "tarsnap" backup service
provided by Tarsnap Backup Inc.

Git repo: DataDrake: Devs say not to use git.
@WhoeverChangedThis: I won't accept it if the tarball doesn't come from git.

Related Objects

Mentioned In
T4364: tarsnap
Mentioned Here
D3477: Initial commit

Event Timeline

DataDrake triaged this task as Low priority.Aug 20 2017, 6:18 PM
DataDrake updated the task description. (Show Details)
DataDrake moved this task from Backlog to Accepted For Inclusion on the Package Requests board.

Here it says the following:

"While the Tarsnap code itself has not been released under an open source license, some of the "reusable components" have been published separately under a BSD license..."

This is the license they use. Doesn't permit modification.

DataDrake updated the task description. (Show Details)Jan 3 2018, 6:20 PM
DataDrake moved this task from Accepted For Inclusion to Backlog on the Package Requests board.
DataDrake added a subscriber: DataDrake.

We need to make sure their custom license isn't in violation of GPL compliance before this can be included.

ICA3DaR5 added a comment.EditedJan 7 2018, 2:28 PM

Well it doesn't allow modification.

These are the freedoms necessary for Free Software:

  • The freedom to run the program as you wish, for any purpose (freedom 0).
  • The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.
  • The freedom to redistribute copies so you can help your neighbor (freedom 2).
  • The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.

Therefore, this is a proprietary license.

That has nothing to do with whether or not the license is GPL compatible.

ICA3DaR5 removed a subscriber: ICA3DaR5.Jan 8 2018, 1:58 PM

I checked the tarball of tarsnap. It bundled the following source packages:

  • bsdtar: BSD license
  • libarchive: BSD license
  • libcperciva: BSD license
  • scryptenc: BSD license
  • bash completion scripts: permissive custom license

I checked tarsnap's Makefile as well as the ldd result of the compiled binary. It dynamically links to:

There is no GPL code used, as far as I can see. Please let me know if there is any other possible compliance issues to look for.

Are the licensing issues with this resolved? I have this packaged and ready to submit if they have. I had a quick conversation with cperciva on IRC earlier and he had this to say.

[14:25] <UMonad> I'm trying to get tarsnap packaged for Solus and was wondering what SPDX license I should use (also am I allowed to package tarsnap?)
[14:26] <UMonad> More accurately: what SPDX licence identifier I should use
[14:38] <UMonad> The reason being that Solus requires an SPDX licence identifier in order to package code.
[14:39] <@cperciva> UMonad: yes, you can package tarsnap
[14:39] <@cperciva> UMonad: let me look up SPDX...
[14:39] <UMonad> This is the link I'm looking at:
[14:42] <@cperciva> UMonad: hmm, that seems to be a list of open source licenses but doesn't include any "not open source software" category
[14:45] <@cperciva> UMonad: the package.yml(5) man page says "this should in most cases be a recognzied SPDX license name", so maybe tarsnap just isn't one of those cases?
[14:48] <UMonad> @cperciva: hmm. I see other proprietary programs (discord specifically) are using "Distributable". would this be ok?
[14:52] <@cperciva> UMonad: sounds right to me :-)

I created an initial package here: D3477

DataDrake closed this task as Wontfix.Oct 20 2018, 5:21 PM

Closing due to license restrictions and removing from repo to comply with those restrictions.