Bug#420356: Package not binNMU-able

Daniel Baumann daniel at debian.org
Sat Apr 21 19:55:45 UTC 2007


Package: cyrus-sasl2
Severity: serious

Hi Maintainers,

thank you for your work on the cyrus-sasl2 packages. However, your
package is not binNMU safe because of wrong used depends declarations.

There are two proper ways of handling it correctly:

0. Old-school: foo (>= ${Source-Version})

1. New-school: foo (= ${Source:Version}) or (= ${Binary:Version})
depending on the package type/relation.

but you use a wrong one, namely foo (= ${Source-Version}). That has the
effect, that e.g. the libsasl2 transitional package doesn't work if a
binNMU was scheduled, which is atm the case:

---snip---
The following packages have unmet dependencies:
  libsasl2: Depends: libsasl2-2 (= 2.1.22.dfsg1-8+b1) but 2.1.22.dfsg1-9
is to be installed
---snap---

Please use *either* old-school *or* new-school, but *not* current one.

Thanks,
Daniel

-- 
Address:        Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:          daniel.baumann at panthera-systems.net
Internet:       http://people.panthera-systems.net/~daniel-baumann/




More information about the Pkg-cyrus-sasl2-debian-devel mailing list