Bug#197954: tetex-base: Upgrade failure in testing with removal of pxfonts (and description of work around)
Hi,
On Thu, Jul 17, 2003 at 04:45:04PM +0900, Atsuhito Kohda wrote:
> From: Hilmar Preusse <hille42@web.de>
> Subject: Bug#197954: tetex-base: Upgrade failure in testing with removal of pxfonts (and description of work around)
> Date: Thu, 3 Jul 2003 23:56:03 +0200
>
> > > Only quick investigation but I guess changing a debconf habdling of
> > > obsolete updmap might fix this.
> > >
> > > It now does; ask a user to remove old updmap or no and remove it if
> > > a user answers yes (default).
> > >
> > > So change it like; replace it with empty file and note a user that
> > > old updmap was replaced with empty file for smooth upgrading.
> > >
> > ...and after all send a message to the user, that updmap is obsolete
> > now and can be removed? Sounds OK.
>
> I investigated this a bit more carefully and thought
> that this would make tetex's script very ugly and inclined
> to think this should be fixed with pxfonts.
>
> It is very easy for pxfonts to fix this. I think
> it is better to leave this bug to pxfonts.
I don't know for sure how this could be done without breaking the upgrade
process. Maybe I'm wrong, but wouldn't this require to upgrade pxfonts
before tetex-base? But since tetex-base (2.0.2-4) Conflicts (and Replaces)
with pxfonts, you can't upgrade to a new version without deinstalling
tetex-base first (or Hold it).
Maybe an empty pxfonts package could be created and the Conflicts: pxfonts
in tetex-base should be removed or replaced with Conflicts: pxfonts (<<
1.0+1-5). I think something like this has been done before, e.g. with
fileutils 5.0-5, coreutils 5.0-5.
Another thing: No one has answered to the last two paragraphs of my initial
post (changed conffiles, Provides: pxfonts). Any opinions about that?
Regards,
Mike Dornberger
Reply to: