Mike Williams wrote:
One of my packages (librmagick-ruby) recently stopped working (details left intentionally vague). I believe this was due to a change in one of the libraries it depends on. In any case, rebuilding against an updated sid install got it working again, without any source changes required. In other words, my source package is fine; it's just the i386 binary package that is bogus.I suspect that users of my package are going to be hit by this, too.Q. Is there an easy way for me for get an updated i386 package into the archive, without incrementing the revision-number?
The way I had this explained to me, it's deliberately impossible to update a package without incrementing some version number... reason being that it would be impossible for anybody to tell which was the "real" updated version.
Example:User has version (2.33-1) installed, which is broken. You upload a "new" 2.33-1 that's been fixed... but now the package system doesn't know which 2.33-1 is the "real" one.
Best to just increment the revision number and say in the changelog "rebuilt because of a broken library upgrade" or something along those lines, I imagine.
Somebody may very well have another idea, but that's how I heard it.