Hi Alexander! Re-adding the BTS, please keep it in the loop if you are replying questions that could be important (in this case the difference with similar software is). On Sun, 13 May 2012 02:16:23 +0200, Alexander Golovko wrote: > On Fri, 11 May 2012 10:46:02 +0200, Luca Capello wrote: >> Given that upstream uses Git as well, please see the git-buildpackage >> documentation and use debian as the debian-branch: >> >> <https://honk.sigxcpu.org/piki/projects/git-buildpackage/> > > Hmm, it look like something slihtly different from debian/ and quilt > patches. I'm not understand yet, how to use it correctly. debian/ (and quilt patches) is how to manage a Debian package, take it as a sort of Debian-only DVCS, while git-buildpackage is a system to manage the Debian-packaging workflow. This has been discussed quite extensively during the last period on the mailing list, e.g.: <mid:87y5p1u15p.fsf@gismo.pca.it> <http://lists.alioth.debian.org/pipermail/pkg-bacula-devel/2012-May/000177.html> >>> * Package name : webacula >>> Version : 5.5.1-1 >>> Upstream Author : Yuri Timofeev <tim4dev@gmail.com> >>> * URL : http://webacula.sourceforge.net/ >> >> How this is related to the two other web interfaces present in the >> upstream Bacula Git repository? >> >> - bacula-web >> <http://www.bacula.org/git/cgit.cgi/bacula/tree/gui/bacula-web> >> <http://www.bacula-web.org/> > > This is monitoring-only (like reportula). > I think, that we can package it in the future, when will have some > more time. Thank you for the explanation. >> >> - bweb >> <http://www.bacula.org/git/cgit.cgi/bacula/tree/gui/bweb> > > bweb can show info about bacula and start restore jobs too, but > webacula look more pretty, imho. Again, thank you. My questions were driven by the fact that the above web interfaces are present in the official upstream Git repository, while webacula is not. >>> Changes since the last upload: >>> >>> * Initial release (Closes: #614554). >> >> I would say that you should close this bug as well ;-) > > Should i close it now or only after package will be builded and > uploaded? I would add both numbers to the line above, so when the package will be uploaded both bugs are *automatically* closed. Thx, bye, Gismo / Luca
Attachment:
pgprMn8XV90Lq.pgp
Description: PGP signature