On Tue, May 09, 2006 at 10:33:44AM -0700, Thomas Bushnell BSG wrote: > Alberto Maurizi <moim@augh.net> writes: > > Package: gnucash > > Version: 1.8.12-8 > > Severity: grave > > Justification: renders package unusable > > below is the result of > > $ gnucash &> gnuchas.log > > hope this helps. > Thank you for your bug report; the bug is actually in an X package and > not in gnucash. > A suggested workaround can be found at bugs.debian.org/365403. A workaround with the side-effect that anyone with a FontPath of /usr/lib/X11/fonts/foo will be unable to see those fonts in /usr/X11R6/lib/X11/fonts/foo, though. The packages implicated in this transition include xfonts-encodings, xfonts-base, xfonts-tipa, libfontenc1, xserver-xorg, xnest, vnc4server, and xvfb. The first three are packages that provide (or provided) font encodings; the last five are packages which I know reference the encodings via a hard-coded path. (There may be others; tightvncserver and vncserver explicitly do *not* reference the encodings directory, AFAICT.) The two options are: to force all of these packages to be kept in sync, which can only be achieved by adding multiple versioned conflicts à la x11-common; or to expose the encodings in both the old and new locations during a complete stable release cycle as a transitional period. The latter option *should* only require versioned dependencies, but if the transitional support is provided by making /usr/X11R6/lib/fonts/encodings a symlink, that would require the same sort of versioned conflicts as x11-common (though on a much smaller scale, since there are only two packages providing files in this directory). Hmm, does the encoding provided by xfonts-tipa even *work*? It looks like /usr/X11R6/lib/X11/fonts/encodings/encodings.dir belongs to the xfonts-base package, so there's no way for xfonts-tipa to register a new encoding? If *that's* true, then the easiest upgrade path may be: - xfonts-base Depends: xfonts-encodings (so that packages which previously depended on xfonts-base for the encodings are satisfied) - xfonts-base ships a /usr/X11R6/lib/X11/fonts/encodings/encodings.dir that uses absolute paths to point to all of the encoding data in /usr/share/fonts/X11/encodings (??) - xfonts-tipa gets ignored because it doesn't actually work Also, given that libfontenc1 references the encodings directly, is a versioned dependency from libfontenc1 to xfonts-encodings appropriate? This would parallel the dependency of xserver-common on xfonts-base in previous versions, I think. Thoughts, XSF? Will an encodings.dir containing absolute paths actually work? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature