Bug#307749: gettext-base: ligettextpo.so.0.1.0, in the wrong package?
Package: gettext-base Version: 0.14.1-10 Severity: serious Justification: incomplete dependencies Tags: sid sarge The package blender recently failed to build on hppa due to a strange gettext-related error: http://buildd.debian.org/fetch.php?pkg=blenderver=2.36-1arch=hppastamp=1115183059file=logas=raw Tracking this down, it appears that /usr/lib/libgettextpo.so is contained in the 'gettext' package, whereas /usr/lib/libgettextpo.so.0.1.0 is contained in the 'gettext-base' package; and /usr/lib/libgettextsrc-0.14.x.so and /usr/lib/libgettextlib-0.14.x.so are also contained in the 'gettext' package. This means that: - the library /usr/lib/libgettextpo.so.0.1.0 in gettext-base is not usable without also installing the gettext package, yet there is no dependency from gettext-base - gettext (and probably shouldn't be) - such a dependency would need to be strictly versioned, because ABI changes in libgettextsrc or libgettextlib break the runtime dependency (as happened here). The right fix is probably to move all the libraries into a single package, with an appropriate Replaces: line; I imagine gettext, rather than gettext-base, is the right package, since no one's complained about gettext-base being broken before now. This bug affects both 0.14.1-10 in sarge and 0.14.4-1 in sid, and probably needs to be fixed separately for each version on account of the freeze. Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#307749: gettext-base: ligettextpo.so.0.1.0, in the wrong package?
On Thu, 5 May 2005, Steve Langasek wrote: Package: gettext-base Version: 0.14.1-10 Severity: serious Justification: incomplete dependencies Tags: sid sarge The package blender recently failed to build on hppa due to a strange gettext-related error: http://buildd.debian.org/fetch.php?pkg=blenderver=2.36-1arch=hppastamp=1115183059file=logas=raw Tracking this down, it appears that /usr/lib/libgettextpo.so is contained in the 'gettext' package, whereas /usr/lib/libgettextpo.so.0.1.0 is contained in the 'gettext-base' package; and /usr/lib/libgettextsrc-0.14.x.so and /usr/lib/libgettextlib-0.14.x.so are also contained in the 'gettext' package. [ Big Oops! ] This means that: - the library /usr/lib/libgettextpo.so.0.1.0 in gettext-base is not usable without also installing the gettext package, yet there is no dependency from gettext-base - gettext (and probably shouldn't be) - such a dependency would need to be strictly versioned, because ABI changes in libgettextsrc or libgettextlib break the runtime dependency (as happened here). The right fix is probably to move all the libraries into a single package, with an appropriate Replaces: line; I imagine gettext, rather than gettext-base, is the right package, since no one's complained about gettext-base being broken before now. I mostly agree. libgettextpo should be in gettext, not in gettext-base. Actually, this is what the PACKAGING document in the source recommends. [ By all the libraries I suppose you mean libgettextpo*, as libasprintf should still be kept in gettext-base ]. This bug affects both 0.14.1-10 in sarge and 0.14.4-1 in sid, and probably needs to be fixed separately for each version on account of the freeze. Actually, I was going to ask for 0.14.4-1 to be included in testing, as it does not contain any changes from 0.14.1-10 which are unsuitable for testing. There are several reasons why I would like to see 0.14.x in testing: * It is still a 0.14.x release (no major changes). * It contains the upstream Solomonic bug fix for the gettext.sh issue. In 0.14.2 and later, gettext.sh is both an executable shell script (honoring --help and --version) and a shell library function and it's not in /usr/share/gettext anymore. I would really dislike shipping /usr/share/gettext/gettext.sh in a stable release, as that would make people to believe that it's ok to hardcode it. * Lot of files have relaxed licensing terms. * The Debian diff is clean again. No autoconf/automake junk added to the diff. This will surely make life easier to everybody if there is a need to upload it again to fix security bugs, for example. So: Could I please fix this in unstable and ask release managers (i.e. you :-) to propagate to testing afterwards? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307749: gettext-base: ligettextpo.so.0.1.0, in the wrong package?
Hi. gettext_0.14.4-2, just uploaded for unstable, fails to build from source on at least the following archs: mipsel hppa sparc arm mips The error is always the same: jikes-classpath: Depends: classpath but it is not going to be installed Seems like a serious bug somewhere, but not in gettext, who just assumes that their build dependencies may be installed. [ Hmm, I wish autobuilders ran sarge for packages that are going to be part of sarge, at least during the freeze ]. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307749: gettext-base: ligettextpo.so.0.1.0, in the wrong package?
On Thu, May 05, 2005 at 07:03:52PM +0200, Santiago Vila wrote: gettext_0.14.4-2, just uploaded for unstable, fails to build from source on at least the following archs: mipsel hppa sparc arm mips The error is always the same: jikes-classpath: Depends: classpath but it is not going to be installed Seems like a serious bug somewhere, but not in gettext, who just assumes that their build dependencies may be installed. This is because gcc-3.3 is currently FTBFS in unstable. :/ [ Hmm, I wish autobuilders ran sarge for packages that are going to be part of sarge, at least during the freeze ]. Well, if you'd care to upload getext 0.14.1-11 to testing-proposed-updates, that can be arranged :) (And we can consider 0.14.4-2 afterwards.) -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#307749: gettext-base: ligettextpo.so.0.1.0, in the wrong package?
Seems like a serious bug somewhere, but not in gettext, who just assumes that their build dependencies may be installed. This is because gcc-3.3 is currently FTBFS in unstable. :/ [ Hmm, I wish autobuilders ran sarge for packages that are going to be part of sarge, at least during the freeze ]. Well, if you'd care to upload getext 0.14.1-11 to testing-proposed-updates, that can be arranged :) (And we can consider 0.14.4-2 afterwards.) Ok, I'll upload a 0.14.1-11 release to testing-proposed-updates. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
