[Pkg-lustre-maintainers] Status of 1.6.2 packaging?

Goswin von Brederlow brederlo at informatik.uni-tuebingen.de
Thu Sep 20 14:41:18 UTC 2007


Niklas Edmundsson <Niklas.Edmundsson at hpc2n.umu.se> writes:

> On Thu, 13 Sep 2007, Goswin von Brederlow wrote:
>
>> I would update dpkg or supply the subsitution variable manually.
>
> I changed binary:Version to Source-Version, it worked much better
> although I suspect there is some difference in some case. If there
> isn't a very good reason for using binary:Version I would suggest
> changing it to Source-Version for back-compatibility reasons.
>
> Building the thing then went fine. However, I have a few packaging
> bugs to report:
>
> linux-patch-lustre should depend on dpatch. There are possibly similar
> dependency issues with lustre-source (quilt/dpatch).

I will check a build on a clean chroot. I always test in the chroot
where I compile the lustre debs themself and then quilt and dpatch are
present already among other things.

> lustre-source seems to install the modules to the wrong directory,
> ie. if uname -r says 2.6.18-lustre-amd64-k8-smp the modules gets put
> in /lib/modules/2.6.18 which isn't too bright.
>
> I submitted a kludge for this back in february, the problem was that
> in 2.6.18 UTSNAME only contains the kernel version, so the lustre
> module install target puts them in the wrong directory. In any case,
> the patch looked like this:
>
> -------------------8<-----------------------------
> Index: debian/rules
> ===================================================================
> --- debian/rules        (revision 135)
> +++ debian/rules        (working copy)
> @@ -256,6 +256,10 @@
>         dh_clean -k
>         $(MAKE) -C lustre-$(VERSION)
>         $(MAKE) -C lustre-$(VERSION)  install DESTDIR=$(CURDIR)/debian/$(PKGNAME
> )
> +       # Kludge to make modules end up in the right place, UTSNAME only
> +       # contains kernel version in 2.6.18 so lustre module install puts them
> +       # in the wrong place currently.
> +       -mv -f $(CURDIR)/debian/$(PKGNAME)/lib/modules/2.6.?? $(CURDIR)/debian/$(PKGNAME)/lib/modules/$(KVERS)

Hmm. I thought this was to make modules for 2.6.18.8 not appear in
2.6.18 and as lustre does that (no longer) I removed the cludge a
short while back. Seems I was wrong. I will figure out something
better that checks if a move is neccessary or not. I can't stand the
error message.

MfG
        Goswin



More information about the Pkg-lustre-maintainers mailing list