Re: Please test gzip -9n - related to dpkg with multiarch support
Ian Jackson <firstname.lastname@example.org> writes:
> Russ Allbery writes ("Re: Please test gzip -9n - related to dpkg with multiarch support"):
>> Another possible solution is to just give any package an implicit Replaces
>> (possibly constrained to /usr/share/doc) on any other package with the
>> same name and version and a different architecture. This isn't as
>> defensive, in that it doesn't catch legitimate bugs where someone has made
>> a mistake and the packages contain different contents, but it also solves
>> the binNMU issue (well, "solves"; the changelog will randomly swap back
>> and forth between the packages, but I'm having a hard time being convinced
>> this is a huge problem).
> Well, it does mean that you might be lacking important information
> because the other changelog wouldn't be present on the system.
> One thing which no-one yet seems to have suggested is to have
> multiarch:same packages put the changelog in a filename which is
> distinct for each architecture. (It wouldn't have to be the triplet;
> the shorter Debian arch would do.) Perhaps there are obvious reasons
> (which I have missed) why this is a terrible idea, but it seems to me
> that it's something we should consider.
Or dpkg could do that for you. At least for files in /usr/share/doc when
there is a collision.