Add Bacula fork Bareos to repository

Bug #1280149 reported by André Bauer
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bareos (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Last new Bacula version is 1 year old now. Development seems kind of dead: http://www.bacula.org/git/cgit.cgi/bacula/

Most of the developers switched to Bareos ( https://www.bareos.org/en/ ). Bareos is a 100% open source fork of the backup project from bacula.org. The fork is in development since late 2010, it has a lot of new features. The source has been published on github, licensed AGPLv3.

Bareos can be used as a drop in replacement of Bacula.

Ubuntu packages for Ubuntu 12.04 are available @ http://download.bareos.org/bareos/release/latest/xUbuntu_12.04/
Should not be a big issue to make some for newer Ubuntu releases too...

André Bauer (monotek)
affects: mysql-dfsg-5.1 (Ubuntu) → bacula (Ubuntu)
description: updated
André Bauer (monotek)
description: updated
description: updated
Revision history for this message
Kern Sibbald (kern) wrote : Bug 1280149] [NEW] Add Bacula fork Bareos to repository

Although it is true that the git repo has not been updated for some time,
there is a good reason, for more information, please see www.bacula.org
-> News.
There is indeed a fork of Bacula, but that fork has only *one* former Bacula
developer. Although, like other open source projects, developers come and
go, I have been contacted by a number of former and current Bacula
developers and they all remain with Bacula. I would appreciate it if
people who make incorrect statements such as "Most of the
devlopers [sic] switched to the Bareos" would take the time to investigate
or simply look at the Bacula website before making such comments.

You should realize that the Bareos fork has some serious problems,
including copyright violations and alleged theft of proprietary code, so
though anyone is free to download and use the Bareos release, you
you will be downloading code that may contain code that Bareos
has no right to release.

On the other hand, Bacula's copyright is held by the Free Software
Foundation, Europe, and I can assure you that all code in Bacula is
used by written permission. Bacula has been under development
for 14 years now and will continue so in the future at a pace that
is faster than any fork that is created by one person in secret
over a 3 year period.

There will be another release of Bacula in the March-April time frame,
which will have a lot of new features, many planned well before the
fork. If you are the interested in the saga of the Bareos
fork, please see the new Bacula website (under development) at:

   http://blog.bacula.org

Revision history for this message
Kern Sibbald (kern) wrote :

Although it is true that the Bacula git repo has not been updated for some time,
there is a good reason, for more information, please see:

  http://www.bacula.org -> News

There is indeed a fork of Bacula, but that fork has only *one* former Bacula
developer. Although, like other open source projects, developers come and
go, I have been contacted by a number of former and current Bacula
developers and they all remain with Bacula. I would appreciate it if
people who make incorrect statements such as "Most of the
devlopers [sic] switched to the Bareos" would take the time to investigate
or simply look at the Bacula website before making such comments.

You should realize that the Bareos fork has some serious problems,
including copyright violations and alleged theft of proprietary code, so
though anyone is free to download and use the Bareos release, you
you will be downloading code that may contain code that Bareos
has no right to release.

On the other hand, Bacula's copyright is held by the Free Software
Foundation, Europe, and I can assure you that all code in Bacula is
used by written permission. Bacula has been under development
for 14 years now and will continue so in the future at a pace that
is faster than any fork that is created by one person in secret
over a 3 year period.

There will be another release of Bacula in the March-April time frame,
which will have a lot of new features, many planned well before the
fork. If you are the interested in the saga of the Bareos
fork, please see the new Bacula website (under development) at:

   http://blog.bacula.org

Kern Sibbald
Bacula Project Manager

Revision history for this message
Robie Basak (racb) wrote :

Since this is a request to package a new upstream source, this bug should be against Ubuntu generally, not against the existing bacula package in Ubuntu.

I am triaging this bug from a neutral perspective. However, anybody working on this in Ubuntu should note that that Bacula Systems SA alleges that this upstream source (Bareos) contains non-free software with no appropriate licence and claims that a lawsuit was filed in December 2013 to resolve the matter. Source: http://www.baculasystems.com/blog/bacula-systems-sa-files-lawsuit-against-bareos-gmbh-co-kg

tags: added: needs-packaging
affects: bacula (Ubuntu) → ubuntu
Changed in ubuntu:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Maik Außendorf (maik-aussendorf) wrote :

All code in Bareos is 100% open source and licensed AGPL.

Regarding the sue: Bacula Systems claimed that 20 lines of code in our stable releases were used unlawfully. We contest that but have immediately removed any code in question to remove any uncertainty from users or partners.

Please read our full statement here:
http://www.bareos.org/en/news/items/lawsuite-between-bacula-systems-sa-and-bareos-gmbh-co-kg-copy.html

Revision history for this message
André Bauer (monotek) wrote :

In the meantime the laswsuite was settled:

http://www.baculasystems.com/blog/bacula-systems-and-bareos-settle-lawsuit

Bareos 14.2.1 is in Ubuntu 15.04 repos now:

http://packages.ubuntu.com/search?keywords=bareos&searchon=names&suite=all&section=all

Imho this bug can be closed.

André Bauer (monotek)
Changed in ubuntu:
status: Triaged → Fix Released
affects: ubuntu → bareos (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.