I demand that Gabor Gombas may or may not have written... [snip] > How do you want to handle one-arch-only binNMUs? binNMUs change > changelog.Debian.gz, so > - you can't upgrade just the architecture that was binNMUed without > changelog.Debian.gz becoming invalid for the other arches [snip]
I think that this'll just have to be accepted - ignore the binNMU versioning when comparing versions for co-installation, but take the docs from the highest-numbered binNMU. I don't know how a binNMU for one architecture followed by a binNMU for another is handled, but it seems reasonable to me that the newer one will have to include the changelog from the older one and, therefore, must have a higher version number. Otherwise, which binNMU changelog entry you get is a matter of chance, and entries may even be lost in later uploads. -- | Darren Salt | linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Output less CO2 => avoid boiling weather. TIME IS RUNNING OUT *FAST*. When you go out to buy, don't show your silver. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]