jadetex needs to conflict with older tetex-base
Bug #7683 reported by
Debian Bug Importer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jadetex (Debian) |
Fix Released
|
Unknown
|
|||
jadetex (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
Automatically imported from Debian bug report #266630 http://
Changed in jadetex: | |
status: | Unknown → Fix Released |
To post a comment you must log in.
Message-ID: <email address hidden> 8859-1? q?Frank_ K=FCster? =)
Date: Wed, 18 Aug 2004 15:41:08 +0200
From: <email address hidden> (=?iso-
To: Ruslan Batdalov <email address hidden>
Cc: <email address hidden>
Subject: Re: tetex-base: This version should conflict with old jadetex
--=-=-= Transfer- Encoding: quoted-printable
Content-Type: text/plain; charset=iso-8859-1
Content-
clone 264319 -1
reassign 264319 tetex-bin
reassign -1 jadetex
severity 264319 important
severity -1 important
tags 264319 pending
tags -1 patch
stop
Ruslan Batdalov <email address hidden> wrote:
> Package: tetex-base
> Version: 2.0.2-9
> Severity: normal
>
> When I tried to upgrade tetex to new version
> dpkg couldn't finish configuration process. Error
> occured during generation of jadetex and pdf jadetex
> formats. After upgrading jadetex package from 3.12-2
> to 3.13-1 all works correctly. This version of tetex-base=20
> seems to conflict with old jadetex.
This error shows up upon every dist-upgrade from woody, and needs a
further "dpkg --configure -a" to be resolved.=20
The problem is that recent tetex-bin, even the fixed one that creates
latex.fmt as well as latex.efmt, cannot be configured as long as the
conffiles of woody's jadetex are still there. But jadetex's conffiles
are only updated in the configure phase, and configuration is delayed
until tetex-bin is configured.
What needs to be done is that dpkg/apt have to be forced to remove
jadetex, upgrade tetex-bin, and reinstall jadetex again.
We have the same problem with tetex-base and tetex-bin; it is resolved
by a versioned Conflicts in both packages:
Package: tetex-base
Conflicts: ... tetex-bin (<=3D 2.0.2-15)
Package: tetex-bin
Conflicts: ... tetex-base (<=3D 2.0.2a-1)
dist-upgrade is happy with this, in the end both packages are installed
and upgraded.
We will introduce a Conflicts of tetex-bin with jadetex (<< 3.13-2) in
the next upload. But we also need a Conflicts of jadetex with tetex-bin
(<=3D 2.0.2-17). Just increasing the version number of the Dependency is
not sufficient, as I tested.=20
Furthermore, in the tetex-* setup, apt can choose whether it temporarily
removes tetex-bin or tetex-base, but if jadetex is installed, we need to
force it to remove tetex-base, not tetex-bin. This is because if
tetex-bin is removed, this is done before jadetex is removed, and
therefore jadetex's prerm will fail (not finding kpsewhich and
update-fmtutil). The way to force removal of tetex-base, instead
tetex-bin, is to have a versioned conflicts against tetex-base.=20
Yes, I know, Policy discourages using versioned conflicts - but this is
one of the "almost never" cases, unless we want to force people to=20
dpkg --configure -a.
Attached is the necessary patch,
regards, Frank
--=20
Frank K=FCster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie
--=-=-= Disposition: attachment; filename= jadetex. diff Transfer- Encoding: quoted-printable
Content-Type: text/plain; charset=iso-8859-1
Content-
Content-
diff -u jadetex- 3.13.orig/ debian/ changelog jadetex- 3.13/debian/ changelog 3.13.orig/ debian/ changelog Wed Aug 18 15:25:08 2004 3.13/debian/ changelog Wed Aug 18 15:27:...
--- jadetex-
+++ jadetex-