latest updates break MikTeX 2.8
coo...@nospamverizon.net
Seems like one of the packages breaks something - now, whenever I try to
compile something (which worked minutes before I applied the updates),
I'm prompted to install a 'missing package' (ifxetex) which in fact
isn't missing. Even a manual uninstall/re-install of ifxetex doesn't fix it.
coo...@nospamverizon.net
MikTeX package manager has options to (i) install on the fly, (ii)
install after asking, or (iii) don't ask/don't tell. If I select option
(iii), compilation is just fine. However, if I use (i) it
downloads/installs ifxetex ever time I compile, of if I use (ii) it
prompts me to install manually.
Something is definitely broken - I'll guess that something in latest
version of ifxetex isn't playing nice with MikTeX package manager (or
some such).
coo...@nospamverizon.net
Brute force solution - reinstalled MikTeX from scratch, seemed to
solve the problem. This would imply that the problem was not due to the
recent updates (per se), but with a locally corrupted FNDB (which may
have resulted from the updates).
Manuel Collado
> On 9/15/2010 1:39 PM, coo...@NOSPAMverizon.net wrote:
>> Just applied the latest (Sep 14) updtaes to MikTeX from the CTAN repo.
>> Seems like one of the packages breaks something - now, whenever I try to
>> compile something (which worked minutes before I applied the updates),
>> I'm prompted to install a 'missing package' (ifxetex) which in fact
>> isn't missing. Even a manual uninstall/re-install of ifxetex doesn't fix
>> it.
IIRC, I've seen this problem when MikTeX has been installed from an
administrator account, and later used from a regular (limited) user account.
>
> Brute force solution - reinstalled MikTeX from scratch, seemed to solve
> the problem. This would imply that the problem was not due to the recent
> updates (per se), but with a locally corrupted FNDB (which may have
> resulted from the updates).
Perhaps trying to install the package from an administrator account is
enough. And do not forget to rebuild the package database after install.
--
Manuel Collado - http://lml.ls.fi.upm.es/~mcollado
Skander
> El 15/09/2010 21:05, cooc...@NOSPAMverizon.net escribió:
I have the same problem with fontspec - I will try to see if an
administrative install helps.
Ulrike Fischer
> I have the same problem with fontspec - I will try to see if an
> administrative install helps.
In the miktex mailing list someone solved the problem by rebuilding
the FNDB as admin _and_ as user.
Multiuser setups are difficult: the "admin"-data and the "user"-data
can get out of sync and confused. If you are facing problems with
constant reinstalls it is a good idea to update the FNDB and the
repositories in both modes.
You should also be aware that if you install as user (eg. with
on-the-fly-installation) you should also update as user or the new
versions are never seen.
I always install miktex as single user. This saves a lot of
troubles.
--
Ulrike Fischer
Skander
Just to summarize - I also updated every package in Miktex that had an
update (except bidi, which has certain issues) last week. Since the
update, every time I try to compile something with fontspec, it asks
me to install it.
Thinking it might be an administrative/non-administrative thing, I
just now (after several system restarts since the update, btw) went in
to the administrator package manager, and found that fontspec wasn't
listed as installed (in spite of having installed it several times via
the compilation process). I then installed it, and tried compiling - I
still am asked to install fontspec. Then I ran a FNDB update as admin,
that didn't help - still asked to install fontspec. I then checked the
non-admin package manager, which also listed fontspec as being
installed. Tried compiling again, still getting prompted. I then ran a
FNDB update from the non-admin dialog - and now it seems to work for
some reason! Not sure what happened exactly, but this has never
happened with previous updates.
Mathieu 2L
I had the same problem after an update today, with the package
ifxetex ; never happened before.
On 16 sep, 16:09, Skander <amagi...@gmail.com> wrote:
> I then ran a
> FNDB update from the non-admin dialog - and now it seems to work for
> some reason!
This solution also seems to work for me ; previously, I installed/
uninstalled it under admin account, without forgetting to run the RNDB
every time, with no success) ; I always work under the admin account
(MiKTeX is not installed as single user) so I would have never thought
of using the non-admin maintenance... thanks !
Szabolcs Horvát
>
> I always install miktex as single user. This saves a lot of
> troubles.
>
I was not aware that this was possible with MiKTeX 2.8. I would have
done this otherwise. Probably it's not the default installation option,
which is a pity because I'd expect that on most computers only a single
person uses MiKTeX (or everyone user of that computer has admin access,
if there's more than one).
Ulrike Fischer
> On 2010.09.16. 15:58, Ulrike Fischer wrote:
>>
>> I always install miktex as single user. This saves a lot of
>> troubles.
>>
>
> I was not aware that this was possible with MiKTeX 2.8.
Well the installation should have asked you:
http://docs.miktex.org/2.8/manual/ch02s02.html#basic-shared
> I would have done this otherwise. Probably it's not the default installation option,
No, at least not if you install as admin. I always install in the
restricted user account in which I want to use miktex and there
"single user" is the only available option and so naturally the
default.
> which is a pity because I'd expect that on most computers only a single
> person uses MiKTeX
Well even if only one person is using the pc/miktex the computer
nowadays (should) have at least two accounts: admin and user (for
everyday use). A "single user" installation in the admin account is
not really useful in such a setup.
The miktex installer is doing the right thing: Installation for all
users if started as admin and installation "only for me" if started
in a user account.
--
Ulrike Fischer