(Sorry for resend, my auto-complete chose the wrong mailing list and I hit Enter too fast. :-( ) Hi all, I'm wondering how to tackle an issue with the crash utility and its eppic extension. I'd like to build crash-eppic as a subpackage of eppic, because that's where the source code is maintained by upstream these days. The trouble is that crash-eppic is now a subpackage of the crash package, which is at version 7.1.5. There is no versioned release of eppic, but the upstream maintainer told me that the next versioned release would be 4.0, so I can safely use a bogus version of 3.99.$something for the libeppic package. I'm unsure what to do about the version of crash-eppic. If it inherits the version number from eppic, it would be downgraded from 7.1.5 to 3.99.$something. I assume this is a problem for Tumbleweed. If I keep 7.1.5 as the version number, then it's a completely arbitrary one - it would merely indicate the last crash version where the extension was built from the incorrect sources. I could probably change the version if I name the package differently, but "crash-eppic" is in fact the perfect name, as there are other crash extensions named "crash-something". FTR Fedora doesn't seem to package crash extensions... Any ideas are welcome! Petr T P.S. Some background if you want to ask how we ended up in this situation: Originally, the eppic extension was part of the upstream crash tarball. Consequently, crash-eppic was built as a subpackage of the crash package. At some point, upstream development of eppic was split off (see https://github.com/lucchouina/eppic). This repo now contains the library (which is also used by other projects, e.g. makedumpfile) and the crash extension code. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org