Hi all, Due to popular demand, here are thoughts about when to upload to unstable:
The previous revision had some serious packaging bugs, and I was glad it was only uploaded to experimental. The next revision is also targeted at experimental to let the packaging bugs “settle down” before too large an audience is exposed to them. In general, it would be nice to use experimental regularly to let new features “cook” if this does not interfere too much with other people’s work. Others can speed this up by trying out unreleased packaging [1] and reporting bugs or success. Another consideration is more important now, though: dpkg uses lzma and should use liblzma in the future to handle LZMA-compressed packages in the archive. This means that having xz-lzma conflict with lzma, as it did in the last revision, will not work. Ideally, I would like to see LZMA-compressed packages tested and working well with XZ Utils before it goes to unstable. But if that doesn’t happen soon it will not be a show-stopper, since there are no LZMA-compressed packages in the archive. v4.999.9beta looks good enough for the public, so I’m not waiting on 5.0. The upshot for mupen64plus is that if you are planning an upload for this week using liblzma0, you would probably have to target it at experimental. :( Hope that clarifies things a bit, Jonathan [1] development repository: http://git.debian.org/?p=collab-maint/xz.git APT repository with snapshots for testing: <http://collab-maint.alioth.debian.org/xz-utils/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
