[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#706114: xfonts-utils: insufficient zlib1g dependency



On 2013-04-25 10:39, Guillem Jover wrote:
> On Wed, 2013-04-24 at 22:06:55 -0400, Michael Gilbert wrote:
>>> So the dependencies are correct. The only problem is due to
>>> gsfonts-x11 postinst's script calling:
>>>
>>>   update-fonts-dir
>>>   → mkfontdir
>>>     → mkfontscale
>>>
>>> While the new xfonts-utils package has been unpacked, but not
>>> configured. This is either a problem in xfonts-utils's
>>> update-fonts-dir, or in debhelper's dh_installxfonts support inserting
>>> those snippets.
>>
>> In terms of getting this fixed quickly for wheezy, couldn't that be
>> addressed with a "Pre-Depends: xfonts-utils" in gsfonts-x11?
> 
> That would only solve the problem for gsfonts-x11, but not for
> anything else using dh_installxfonts. I think, to be safe the hack
> would need to be applied to xfonts-utils's dependencies, which is all

The reason for this suboptimal upgrade order is probably

Package: zlib1g
Breaks: ..., texlive-binaries (<< 2009-12)

and instead of deconfiguring texlive-binaries apt delays installation of
the new zlib1g, breaking some unpacked and not yet configured packages.

> kinds of ugly, but at least should always work, at the cost of
> complicating the upgrade path.
> 
> I guess the correct solution though, is to change update-fonts-* and
> any other script in xfonts-utils calling mkfont* from other maintainer
> scripts, to only run if xfonts-utils itself is configured or being
> configured, and calling these through xfonts-utils maintainer scripts
> too, so that if xfonts-utils and something else using it like gsfonts-x11
> are both unpacked on the same run, the actual update-fonts-* executions
> will be delayed until xfonts-utils is itself configured, at which point
> the scripts should be able to run. I don't think this would be much
> more difficult to prepare.

Sounds like a job for triggers (but there is currently a dpkg bug that
causes it to run triggers for packages that are not configured (or their
dependencies are not)

Andreas


Reply to: