[Pkg-dkms-maint] dkms needs a pre-depends entry (Policy 3.5)
Ben Hutchings
ben at decadent.org.uk
Sat Jul 17 16:09:03 UTC 2010
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-dkms-maint/attachments/20100717/0e143e10/attachment-0001.pgp>
More information about the Pkg-dkms-maint
mailing list