[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dkms needs a pre-depends entry (Policy 3.5)



On Sat, 2010-07-17 at 16:49 +0100, Julien Cristau wrote:
> On Sat, Jul 17, 2010 at 17:41:26 +0200, Giuseppe Iuculano wrote:
> 
> > Setting up nvidia-kernel-dkms (195.36.24-4) ...
> > Loading new nvidia-195.36.24 DKMS files...
> > Traceback (most recent call last):
> >   File "/usr/bin/lsb_release", line 26, in <module>
> >     import lsb_release
> > ImportError: No module named lsb_release
> > Traceback (most recent call last):
> >   File "/usr/bin/lsb_release", line 26, in <module>
> >     import lsb_release
> > ImportError: No module named lsb_release
> > First Installation: checking all kernels...
> > Building only for 2.6.32-5-amd64
> > Traceback (most recent call last):
> >   File "/usr/bin/lsb_release", line 26, in <module>
> >     import lsb_release
> > ImportError: No module named lsb_release
> > Traceback (most recent call last):
> >   File "/usr/bin/lsb_release", line 26, in <module>
> >     import lsb_release
> > 
> This looks to me like a missing dependency on lsb-release in
> nvidia-kernel-dkms, not in dkms.  And I don't understand why a
> Pre-Depends would be necessary anywhere.  Care to explain?

The postinst for nvidia-kernel-dkms invokes dkms, which invokes
lsb_release.  lsb_release hasn't been configured at this point so its
module has not been installed for the default Python version.  But I
agree that there is no need for Pre-Depends.

I also wonder whether a distribution package of dkms really needs to use
lsb_release at all.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: