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

Bug#460559: tetex-extra: aptitude remove tetex-extra fails



reassign 460559 tex-common
retitle 460559 Needs to conflict with etch's version of the tetex packages
clone 460559 -1
reassign -1 texlive-base-bin
retitle -1 manpages of updmap, fmtutil and texconfig should refer to TeX-on-Debian docs
severity 460559 serious
severity 460559 normal
thanks

Paul Menzel <pm.debian@googlemail.com> wrote:

> Am Sonntag, den 03.02.2008, 18:44 +0100 schrieb Frank Küster:
>> Paul Menzel <pm.debian@googlemail.com> wrote:
>> 
>> > I finally found [1] and the /usr/share/texmf-tetex (or texlive – I do
>> > not remember and I do not have access to the computer now) was not in my
>> > paths either. 
>> 
>> And you upgraded from an old machine to unstable, right?
>
> If I remember correctly the machine was using unstable all the time. I
> just had not done an sudo aptitude safe-upgrade for over a year and was
> still using the tetex packages.

Hm, which paths did you have in TEXMFDIST before you made the change? If
it was only /usr/share/texmf-tetex, than it's the problem I described,
just not with upgrades from stable_n to stable_n+2, but within unstable
- and I wouldn't care much about that.

However, from the info in your first mail it seems to me that the
problem was that you only had the new path,
/usr/share/texmf-texlive. That means you had already upgraded
tex-common, but the old tetex-extra still installed. This is something
that can still happen to anyone upgrading from etch to lenny. 

It seems we need to bump the Conflicts line in tex-common from

Conflicts: tetex-base (<= 3.0-3), tetex-bin (<= 3.0-4)

to

Conflicts: tetex-base (<= 2007), tetex-bin (<= 2007)

But before doing that, I'd like to do some testing first.

>> Any ideas how we could have helped you find that info?
>
> I did not find it with google.
>
> If the output in the updmap logfile had a reference like „read the
> files /usr/share/doc/tex-common/TeX-on-Debian*” I might have found it.

Hm, well, I think looking into /usr/share/doc/$package should be the
first thing on a Debian system, much prior to searching with Google. 

You've already found that the problem has to to with updmap, which is in
the tetex-bin package. 

$ ls /usr/share/doc/tetex-bin/
NEWS.Debian.gz	README.Developers  changelog.Debian.experimental.gz  changelog.gz
README.Debian	TODO.Debian	   changelog.Debian.gz		     copyright

Both README.Debian and NEWS.Debian point you to TeX-on-Debian.* 

> Also a note in the warning running updmap-sys --edit which finds a
> modified configuration file (and recommends to delete it, if I remember
> correctly) might have helped.

You used --syncwithtrees, and that give a very generic information which
is not Debian-specific, and the script cannot guess that you have a
Debian-specific problem.  The manpages, however, (and maybe the output of --edit,
that's right) should mention the documentation in tex-common. (Cloning
the bug and reassigning to texlive-base-bin).

Regards, Frank
-- 
Frank Küster
Debian Developer (teTeX/TeXLive)



Reply to: