libcdio 0.83 had a licensing problem. So we packaged a GIT snapshot. On October version 0.90 was released, but nobody noticed. The problem is that between 0.83 and 0.90 the API was changed. Now you find software that uses things like #if LIBCDIO_VERSION_NUM >= 90 To use the old or the new API. But our GIT snapshot defines LIBCDIO_VERSION_NUM as 84. I am not in any way its maintainer and I have no more knowledge about it than anybody else. So I can't really give any good argument to upgrade or not upgrade. What should we do? - Don't touch anything Let Packman and users who compile its own software feel the pain of having to patch all the software that checks LIBCDIO_VERSION_NUM - Patch our current GIT snapshot to report version 90 Even if it's a GIT snapshot in theory it has been well tested during the development of 12.3. I don't know if there were more API changes between our snapshot and 0.90 - Update our package to 0.90 Less than one month to test it. $ osc whatdependson openSUSE:12.3 libcdio standard i586 libcdio : bundle-lang-gnome-extras cdio-utils clementine gstreamer-0_10-plugins-ugly gstreamer-plugins-ugly gvfs libcddb-utils libcdio-paranoia pragha qmmp vcdimager xine-lib xmms2 Opinions? Stanislav, you are set as maintainer and bugowner. Is that info up to date? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org