[pkg-bacula-devel] libs3 - status

[Mario Pranjic]

søn. 29. nov. 2020 kl. 17:31 skrev Sven Hartge <sven at svenhartge.de>:

> On 27.11.20 21:18, Mario Pranjic wrote:
> Sorry to say, but that repository won't work.
>
> Hi Sven!

I am aware it is useless as it is now. I would be very much surprised this
"dirty work" is the way to go. :)
When I asked Leo about it, he said just to hammer to master branch. So I
did.


> Please familiarize yourself with the way gbp  works.
>
> In short: You need three branches, all created and maintained by gbp.
>
> 1) upstream, containing the unpackages and unmodified upstream source.
>
> 2) pristine-tar, containing the data for the pristine-tar tool
>
> 3) debian/unstable, containing the branch the package is finally build from
>
> Any changes to the source must be done by using quilt as patch tool, you
> cannot *ever* change any file outside of debian/ directly.
>
> Have a look at the main bacula repository on how this is done. (Note:
> here the branch "debian/unstable" is still called "master", but that is
> being deprecated by now.)
>

Thanks for guidelines! :)
I will take care of it. Of course, I might get stuck and ask for help.
Hopefully, not too much.

But, out of curiosity... What is to be done after branches are set? If I
understood correctly, this libs3 doesn't properly use debian control and
rules files, but, instead, doeas stuff with it's own makefile.
That is not the way it is supposed to be?

Best regards,

Mario.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-bacula-devel/attachments/20201129/2d23829e/attachment.html>