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

Bug#571924: kdebindings not binNMUable



Hi,

kdebindings is binNMUable very well. The bug you report has a slightly 
different source.

debian/control contains:
Package: python-kde4
Depends: ${shlibs:Depends}, ${python:Depends}, ${misc:Depends}, 
 python-qt4 (>= ${python-qt4:Version}), python-qt4 (<< ${python-qt4:Version}+~), 
 python-sip4 (>= ${python-sip4:Version}), python-sip4 (<< ${python-sip4:Version}+~)

python-qt4:Version and python-sip4:Version are filled in debian/rules 
by:
 echo "python-qt4:Version="`dpkg -l python-qt4  | tail -1 | awk '{print $$3}'` >> debian/python-kde4.substvars
 echo "python-sip4:Version="`dpkg -l python-sip4  | tail -1 | awk '{print $$3}'` >> debian/python-kde4.substvars
 echo "python-qt4:Version="`dpkg -l python-qt4  | tail -1 | awk '{print $$3}'` >> debian/python-kde4-dev.substvars
 echo "python-sip4:Version="`dpkg -l python-sip4  | tail -1 | awk '{print $$3}'` >> debian/python-kde4-dev.substvars

That's perfectly fine, as long we ignore the fact that the sip4 packages 
were renamed to sip in 4.10-1.
kdebinding Build-Depends on sip4 (>= 4.7.8), python-sip4-dev (>= 4.7.8), 
which pulls python-sip-dev and therefor python-sip.
No python-sip4 to check it's version, and voila, we have <none> in 
there.

To fix this bug, one would need to:
1. Build-Depend on python-sip-dev (the sip4 package is gone/empty)
2. Replace the Depends of python-kde4 with unversioned sip packages
3. Check the version of the unversioned sip packages in debian/rules (or 
   use dh_sip here, which is new)

Regards
Evgeni

-- 
Bruce Schneier can read and understand Perl programs.



Reply to: