On Friday, July 18, 2014 01:03:57 Andreas Cadhalpun wrote: > On 18.07.2014 00:32, Scott Kitterman wrote: > > On July 17, 2014 6:22:14 PM EDT, Andreas Cadhalpun <[email protected]> wrote: > >> Hi Scott, > >> > >> The commit message sounds as if you wanted to add > >> (>= ${source:Version}), but you added (= ${source:Version}). > >> This is not binNMU-safe, so it should be change either to >= or to > >> binary:Version. > >> > >> Best regards, > >> Andreas > > > > Equals source version is binNMU safe, isn't it? > > It is not [1]: > * declaring dependency between 2 arch: any packages: ${binary:Version} > > In a binNMU the binary version is incremented, but the source version > stays the same, so the packages will become uninstallable. > > > It could be >= though. > > I don't know what you intended, or why you added it, but this should be > safe. > > Best regards, > Andreas > > 1: https://wiki.debian.org/binNMU
It took me a bit of thinking it through, bit I got your point now. My goal was to make sure if you upgraded to a new upstream release of clamav/clamav- daemon/clamav-milter you upgraded clamav-freshclam too. Fixed now. It's just as well. It turns out the wrap-and-sort ate the Packages line for clamav-milter from debian/control and I didn't notice it when I reviewed the diff. I filed a bug about that, but the BTS is being slow about giving me the number for it. Thanks, Scott K _______________________________________________ Pkg-clamav-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-clamav-devel
