Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 06/08/15 11:04, Roland Kammerer wrote:
> On Wed, Aug 05, 2015 at 03:34:49PM +0100, Matthew Vernon wrote:
>> Hi,
>>
>> I needed to build the drbd 8.4.6 kernel module for my Debian stable
>> ("jessie") boxes. As a result of which, I found 2 bugs:
>>
>> 1) the built drbd module package ends up depending on drbd8-utils, which
>> is now incorrect - that should be drbd-utils.
>
> Not really. If you build debian packages from drbd-utils, you also get a
> transitional drbd8-utils package (which 'Depends:' on drbd-utils). I
> guess an '|'-dependency would not hurt. I will think about that.
A |-dependency would mean that one wouldn't have to install the
transitional drbd8-utils package (which isn't otherwise necessary).
>> 2) the drbd8-module-source_8.4.6-1_all.deb isn't actually buildable -
>> module-assistant auto-install drbd8
>> fails to build drbd_buildtag.c
>>
>> The source package doesn't contain .git (obviously, it's not a git
>> checkout), but nor does it contain .drbd_git_revision nor
>> drbd_buildtag.c.
>
> The easiest way is to clone the repo and then do a:
> "make prepare_release" and then continue with the resulting
> drbd-8.4.6-debian.tar.gz tarball (which contains
> drbd-8.4.6/drbd/.drbd_git_revision).
>
> In general you have 3 options:
> - Become a customer, we know how to build packages.
> - Use a release tarball (or generate one).
> - Directly from git: you are on your own and we expect that you know
> what you are doing.
I was following the instructions here:
https://drbd.linbit.com/users-guide/s-build-deb.html
Which lead me to believe that clone, checkout relevant tag, run
dpkg-buildpackage ought to work...
Thanks,
Matthew