-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Steve Langasek wrote:
> Well, except that a) using apt to install the new package would > automatically handle this upgrade case for you That requires me to setup my own apt repository though (and README.Debian talks about using dpkg). > (and there are binary > nvidia-kernel-legacy packages in the archive for 2.6.15-1), Yes, but this is in regards to the -source package whose sole purpose is for building modules for custom built kernels. > So you have a point that > this could be improved, but it doesn't look like the current behavior of the > package is wrong from a policy compliance perspective. Agreed. It was somewhat of a knee-jerk bug report... My bitching about policy was a bit premature. :) > Versioned conflicts and replaces are both supported. So probably the best > option would be Er, yeah. I guess I was thinking of versioned Provides... > > Package: nvidia-kernel-legacy-#KVERS# > Conflicts: nvidia-kernel-#KVERS# > Replaces: nvidia-kernel-#KVERS# (<< 1.0.7664-0) > > or, pick some other upper cap for the replaces: that seems appropriate. Agreed. Cheers, - -Mike -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEB3Gl7ZPKKRJLJvMRAitJAJ4qrWtyQyOBV2KzvdP/icWxbEX+ZwCeIWKI crfco3454PNRkKuq/gs9Ws8= =uJVD -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
