Bug#229725: tetex-base: Missing conflicts

[frank@kuesterei.ch (Frank Küster)]

Hilmar Preusse <hille42@web.de> schrieb:

> On 26.01.04 Clint Adams (schizo@debian.org) wrote:
>> 
>> > You're right, that was rubbish. Are there any other ideas than a
>> > conflicts on arabtex<=3.10-5? 
>> 
>> Is there another way to have arabtex upgrade first?
>> 
> Document it in the Release notes? Very inconvenient I know.

What will be the exact outcome of

Conflicts: arabtex <= 3.10-5 ?

Wouldn't it be that apt detects that it cannot upgrade tetex-* this
time, keeps it and all depending packages back, and upgrades
arabtex. After that we have two possible cases. By chance I talked about
this with my Application Manager, and he said he thought case 1 would
occur:

1. Either, without asking for user input, it apt runs dpkg again with
   the remaining packages, including tetex and its depending packages
   (and nastily ask debconf questions a second time)

2. Or it will do nothing, leaving the user with the choice of angrily
   hitting his monitor or hitting his keyboard to repeat the apt-get
   dist-upgrade command.

In case 1, I would prefer to use the Conflicts: It's automatic, although
prompting is done twice. In case 2, we would have to say something in
the release notes anyway, so we could think about doing only this.

Comments?

Bye, Frank
-- 
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie