Package: g-wrap Version: 1.9.9-1 Severity: serious Justification: Policy 8.1
apt-get upgrade installs g-wrap 1.9.9 but "holds back" guile-g-wrap. This is due to libgwrap-runtime transitioning from SONAME 0 to 2. However, because of a change in the contents of g-wrap, even upgrading g-wrap without touching the other dependencies (the default apt action) causes gnucash to break. (The changelog for 1.9.9 claims that gnucash needs no longer to depend on g-wrap but until gnucash can be rebuilt without g-wrap the changes in g-wrap cause gnucash to break. Was 1.9.9 tested with gnucash prior to adding this claim to the changelog?) Installing guile-g-wrap 1.9.9 only compounds the problem. GnuCash cannot build against g-wrap 1.9.9. It would have been better if g-wrap was renamed for 1.9.9 such that it was not selected by apt as a candidate for upgrade or had the dependencies modified in such a way that g-wrap 1.9.9 cannot be installed alongside libgwrap-runtime0 or guile-g-wrap (<< 1.9.9). Currently, to use gnucash, users must pin g-wrap to the version in testing. In 'normal' library transitions, all transitioning packages are held back until such time as all the installed reverse dependencies have migrated to the new API. By not renaming g-wrap, code using the new API gets installed without the library. The result is that unless g-wrap is reverted to the version in testing, gnucash will not start. If guile-g-wrap is upgraded (bringing in the new library with the new API), gnucash seg faults. The summary is that g-wrap should have required the installation of the new API in order to be upgraded which would, in turn, have held back g-wrap AND the new libraries until such time as a fixed version of gnucash can be uploaded. I'm making this RC so that users in testing do not have their gnucash installations broken by this failure to migrate all g-wrap packages in one transition. I appreciate that the g-wrap package is not a 'library' in the traditional sense of that word but in this case, the breakage is caused by upgrading g-wrap and would have been avoided if g-wrap followed Policy and transitioned in a way that users "don't get filename clashes if you try to install different versions of the combined shared libraries package". As it is unlikely that g-wrap 1.9.9 could be installed alongside g-wrap 1.9.6, then IMHO the g-wrap binary should only be upgraded if the rest of the installed g-wrap packages can also be upgraded. Overall, a Conflicts: guile-g-wrap (<< 1.9.9) may be required here so that g-wrap is not installed on any system where gnucash is also installed until such time as gnucash can use guile-g-wrap 1.9.9. Once gnucash is able to build again, gnucash can also then conflict with g-wrap (>> 1.9.6) until the problems with 1.9.9 are resolved. I'll be filing an appropriate bug in gnucash just as soon as I work out how and why gnucash fails to work with g-wrap 1.9.9. -- System Information: Debian Release: lenny/sid APT prefers experimental APT policy: (500, 'experimental'), (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.22-1-powerpc Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages g-wrap depends on: ii guile-1.8 1.8.2+1-2 The GNU extension language and Sch ii guile-library 0.1.5-1 Library of useful Guile modules Versions of packages g-wrap recommends: ii indent 2.2.9-9 C language source code formatting pn libgwrap-runtime-dev <none> (no description available) Since starting reportbug, I have installed: ii libgwrap-runtime-dev 1.9.9-1 but gnucash still seg faults. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
