[tex-live] problem with tlmgr update

[Jukka Salmi]

Hello,

some minutes ago I updated a TL 2009 (pretest) system.  After having
updated texlive.infra (from 14857 to 14881), I remembered that there was
a backup option and turned that on:

  $ tlmgr option showall
  [...]
  Directory for backups (backupdir): (not set)
  Number of backups to keep (autobackup): (not set)
  [...]
  $ sudo tlmgr option backupdir /opt/texlive/2009/backups
  tlmgr: setting option backupdir to /opt/texlive/2009/backups.
  $ sudo tlmgr option autobackup 1
  tlmgr: setting option autobackup to 1.

While updating the other packages, tlmgr complained about not being able
to remove the packages:

  $ sudo tlmgr update --all
  tlmgr: package repository http://ftp.klid.dk/ftp/texlive/tlnet
  Asana-Math: package not present, cannot remove
  [1/10, ??:??/??:??] update: Asana-Math (13926 -> 14874) ... done
  algorithms: package not present, cannot remove
  [2/10, 06:51/06:56] update: algorithms (13530 -> 14871) ... done
  context: package not present, cannot remove
  [3/10, 44:32/45:48] update: context (14842 -> 14879) ... done
  dvipdfmx: package not present, cannot remove
  [4/10, 01:09/02:58] update: dvipdfmx (14829 -> 14880) ... done
  keycommand: package not present, cannot remove
  [5/10, 01:09/03:00] update: keycommand (14353 -> 14875) ... done
  makeplot: package not present, cannot remove
  [6/10, 01:08/03:03] update: makeplot (13530 -> 14876) ... done
  mkgrkindex: package not present, cannot remove
  [7/10, 01:07/03:05] update: mkgrkindex (14450 -> 14873) ... done
  pdftex-def: package not present, cannot remove
  [8/10, 01:08/03:09] update: pdftex-def (13293 -> 14877) ... done
  pstricks: package not present, cannot remove
  [9/10, 01:15/03:29] update: pstricks (13614 -> 14872) ... done
  texlive-scripts: package not present, cannot remove
  [10/10, 00:00/02:33] update: texlive-scripts (14858 -> 14882) ... done
  tlmgr: package log updated at /opt/texlive/2009/texmf-var/web2c/tlmgr.log
  [...]

I don't know whether these complains are caused by the tlmgr update or
by enabling backups.  However, what does tlmgr complain about exactly?
The packages in question were present before the update, are still
installed after the update, and everything seems to work fine...  Any
hints?


Regards, Jukka

-- 
This email fills a much-needed gap in the archives.