Bug#780155: ITP: baculum -- Baculum WebGUI tool for Bacula Community program
On 09.03.2015 22:57, Cameron Norman wrote:
> On Mon, Mar 9, 2015 at 2:13 PM, gani <marcin.haba@bacula.pl> wrote:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Marcin Haba <marcin.haba@bacula.pl>
>>
>> * Package name : baculum
>> Version : 7.0+git20150208
>> Upstream Author : Marcin Haba <marcin.haba@bacula.pl>
>> * URL : http://www.bacula.org/
>> * License : AGPLv3
>> Programming Lang: PHP
>> Description : Baculum WebGUI tool for Bacula Community program
>
> I see you linked to the bacula.org homepage for this package. Am I
> correct in saying that what you are packaging can be found here:
>
> http://www.bacula.org/git/cgit.cgi/bacula/tree/gui
>
> if so there seems to already be packaging (outside of Debian) that
> uses the bweb name for the package.
> If not, would you mind clarifying which GUI tool for Bacula this is
> with a link to a homepage and / or git repo?
Hello,
Bweb tool in Bacula Community has been removed from bacula-gui release
archive from version 7.0.x. From the same version 7.0 has introduced
Baculum tool to bacula-gui archive.
Here is Baculum in Bacula Git repository:
http://www.bacula.org/git/cgit.cgi/bacula/tree/gui/baculum?h=Branch-7.0
>> - is it a dependency for another package?
>>
>> Yes, it is. Baculum uses external toolset - PRADO Framework.
>> Additionally Baculum uses external JavaScript libraries.
>
> Actually those are the dependencies of this project. The question is
> if this package is a dependency of another package (in the same way
> PRADO is a dependency of this package).
OK. Thank you for clarification. I was thinking that question is about
general packages/projects. In Debian I have not seen PRADO Framework in
packages, similar as Opentip JavaScript library and Flotr2 library. They
are Baculum dependencies that I wrote up in debian/copyright in Baculum
deb metadata file.
I have seen libjs-flotr, but probably it is older version of Flotr2
project. I need to check it.
>> - how do you plan to maintain it?
>> After each Bacula and Baculum release I plan to build Baculum deb and rpm
>> packages for community. From deb packages I am going to build also for Debian.
>>
>> - inside a packaging team?
>> I am not sure about packaging team. I have never been packages maintainer.
>
> You should probably maintain it inside the Debian Bacula Team. This
> will make it easier to find a sponsor (which I will get to) and help
> if need be.
OK. It is fine for me.
>> - do you need a sponsor?
>> No. I do not.
>
> You mentioned that you have never made Debian packages before. Thus,
> you are not a Debian developer and need a debian developer to review
> and then upload the packages for you. This is what a sponsor is. You
> need a sponsor.
I did not say that I have never made Debian packages before. I just have
never been packages maintainer. Anyway, from that what I read and
understood, sponsor is person that prepares build packages instead of
me. If I am wrong, I am sorry, Lately I read a lot of different texts in
Internet.
I prepared Baculum project on Launchpad for Ubuntu as PPA project.
Best regards.
Marcin Haba
>
> --
> Cameron Norman
>
Reply to: