Dnia 2012-05-22, wto o godzinie 14:10 +0200, Andreas Beckmann pisze: > Package: python-pyopencl-headers > Version: 2011.2+git20120508-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'testing'. > It installed fine in 'testing', then the upgrade to 'unstable' fails > because it tries to overwrite files that are owned by other packages > without declaring a Breaks/Replaces relation. > > See policy 7.6 at > http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces > > >From the attached log (scroll to the bottom...): > > Selecting previously unselected package python-pyopencl-headers. > Unpacking python-pyopencl-headers (from > .../python-pyopencl-headers_2011.2+git20120508-1_all.deb) ... > dpkg: error processing > /var/cache/apt/archives/python-pyopencl-headers_2011.2+git20120508-1_all.deb > (--unpack): > trying to overwrite '/usr/include/pyopencl/pyopencl-ranluxcl.cl', which is > also in package python-pyopencl 2011.2-1 > > Should I put Breaks/Replaces: python-pyopencl (<< 2011.2.2+git20120508-1) or Breaks/Replaces: python-pyopencl (<< ${source:Version})? Policy 7.6 uses hard-coded version, but many packages put ${source:Version} into debian/control. What is advised?
Regards. -- Tomasz Rybak GPG/PGP key ID: 2AD5 9860 Fingerprint A481 824E 7DD3 9C0E C40A 488E C654 FB33 2AD5 9860 http://member.acm.org/~tomaszrybak
signature.asc
Description: This is a digitally signed message part
