In the latest update (1/18) for MikTeX 2.9 , Ly1 is apparrently
broken. MikTeX is requesting a missing file from it and stops.

After trial and error, a workaround is to hit cancel and enter.  The
compilation is OK in spite of the error.

Roy <rbethel@mitre.org> writes:

> In the latest update (1/18) for MikTeX 2.9 , Ly1 is apparrently
> broken. MikTeX is requesting a missing file from it and stops.
>
> After trial and error, a workaround is to hit cancel and enter.  The
> compilation is OK in spite of the error.

the ly1 bundle has been updated in tex live, too, and a trivial test
shows no problem.

could you show code that fails for you under miktex?  (i've old miktex
versions, and installing 2.9 for this is more time than i have
available...)
-- 
Robin Fairbairns, Cambridge
my address is @cl.cam.ac.uk, regardless of the header.  sorry about that.

On Jan 19, 11:43=A0am, Robin Fairbairns <r...@warp.cl.cam.ac.uk> wrote:
> Roy <rbet...@mitre.org> writes:
> > In the latest update (1/18) for MikTeX 2.9 , Ly1 is apparrently
> > broken. MikTeX is requesting a missing file from it and stops.
>
> > After trial and error, a workaround is to hit cancel and enter. =A0The
> > compilation is OK in spite of the error.
>
> the ly1 bundle has been updated in tex live, too, and a trivial test
> shows no problem.
>
> could you show code that fails for you under miktex? =A0(i've old miktex
> versions, and installing 2.9 for this is more time than i have
> available...)
> --
> Robin Fairbairns, Cambridge
> my address is @cl.cam.ac.uk, regardless of the header. =A0sorry about tha=
t.

Robin,

Thank you for your interest.  The TexFile.tex is a technical article
using Elsiever's  elsarticle.cls (based on LaTeX article.cls) which
uses tx font. It worked fine until the latest update. All I did was
very minor editing (I think). I don't think the error can be isolated
in the source *.tex.

This is the output of TexFile.log in "error mode"  x <enter> (produces
error) as opposed to just <enter> (produces no error).

LaTeX Font Info:    Try loading font information for U+psy on input
line 64.

("C:\Program Files\MiKTeX 2.9\tex\latex\psnfss\upsy.fd"
File: upsy.fd 2001/06/04 font definitions for U/psy.
)
! Font U/psy/m/n/10=3Dpsyr at 10.0pt not loadable: Metric (TFM) file not
found.
<to be read again>
                   relax
l.64 {\Pifont{psy}
                  }


The find error in WinEdt takes you to  line 64 in pifont.sty.  I had
no clue that pifont.sty was ever called even in "no error mode".
MikTex tries to (re-?)install ly1. I unstalled and installed ly1. No
difference. I also hit all the MiKTeX refresh buttons.


{\Pifont{pzd}}
{\Pifont{psy}}          <<---   Line 64 in pifont.sty
\endinput
%%
%% End of file `pifont.sty'.


I will try the same file on my non-updated (non-corrupted?) MikTeX
system at home.


Roy

Roy <rbethel@mitre.org> writes:

> On Jan 19, 11:43�am, Robin Fairbairns <r...@warp.cl.cam.ac.uk> wrote:
>> Roy <rbet...@mitre.org> writes:
>> > In the latest update (1/18) for MikTeX 2.9 , Ly1 is apparrently
>> > broken. MikTeX is requesting a missing file from it and stops.
>>
>> > After trial and error, a workaround is to hit cancel and enter. �The
>> > compilation is OK in spite of the error.
>>
>> the ly1 bundle has been updated in tex live, too, and a trivial test
>> shows no problem.
>>
>> could you show code that fails for you under miktex? �(i've old miktex
>> versions, and installing 2.9 for this is more time than i have
>> available...)
>
> Thank you for your interest.  The TexFile.tex is a technical article
> using Elsiever's  elsarticle.cls (based on LaTeX article.cls) which
> uses tx font. It worked fine until the latest update. All I did was
> very minor editing (I think). I don't think the error can be isolated
> in the source *.tex.
>
> This is the output of TexFile.log in "error mode"  x <enter> (produces
> error) as opposed to just <enter> (produces no error).
>
> LaTeX Font Info:    Try loading font information for U+psy on input
> line 64.
>
> ("C:\Program Files\MiKTeX 2.9\tex\latex\psnfss\upsy.fd"
> File: upsy.fd 2001/06/04 font definitions for U/psy.
> )
> ! Font U/psy/m/n/10=psyr at 10.0pt not loadable: Metric (TFM) file not
> found.
> <to be read again>
>                    relax
> l.64 {\Pifont{psy}
>                   }

psyr appears in miktex (pre-latest upgrade) both as part of package
(?) ly1 and package symbol.  today it seems only to be in symbol.

if that interpretation (of mine) is right, you might get resolution by
loading package symbol, too.

(note i don't know what the things you install files with, in miktex,
are called -- i've used "package", which seems reasonable.)

> I will try the same file on my non-updated (non-corrupted?) MikTeX
> system at home.

what you now have, i think, is not so much "corrupt" as "differently
arranged".  of course, it's easy for the likes of me, with more disc
space available than i know what do with and no bandwidth constraints
-- so i don't mind having two copies of things.  as a result i am
always able to run my tex live and miktex systems as full installs.
-- 
Robin Fairbairns, Cambridge
my address is @cl.cam.ac.uk, regardless of the header.  sorry about that.

On Jan 19, 3:11=A0pm, Robin Fairbairns <r...@slogin-serv3.cl.cam.ac.uk>
wrote:
> Roy <rbet...@mitre.org> writes:
> > On Jan 19, 11:43=A0am, Robin Fairbairns <r...@warp.cl.cam.ac.uk> wrote:
> >> Roy <rbet...@mitre.org> writes:
> >> > In the latest update (1/18) for MikTeX 2.9 , Ly1 is apparrently
> >> > broken. MikTeX is requesting a missing file from it and stops.
>
> >> > After trial and error, a workaround is to hit cancel and enter. =A0T=
he
> >> > compilation is OK in spite of the error.
>
> >> the ly1 bundle has been updated in tex live, too, and a trivial test
> >> shows no problem.
>
> >> could you show code that fails for you under miktex? =A0(i've old mikt=
ex
> >> versions, and installing 2.9 for this is more time than i have
> >> available...)
>
> > Thank you for your interest. =A0The TexFile.tex is a technical article
> > using Elsiever's =A0elsarticle.cls (based on LaTeX article.cls) which
> > uses tx font. It worked fine until the latest update. All I did was
> > very minor editing (I think). I don't think the error can be isolated
> > in the source *.tex.
>
> > This is the output of TexFile.log in "error mode" =A0x <enter> (produce=
s
> > error) as opposed to just <enter> (produces no error).
>
> > LaTeX Font Info: =A0 =A0Try loading font information for U+psy on input
> > line 64.
>
> > ("C:\Program Files\MiKTeX 2.9\tex\latex\psnfss\upsy.fd"
> > File: upsy.fd 2001/06/04 font definitions for U/psy.
> > )
> > ! Font U/psy/m/n/10=3Dpsyr at 10.0pt not loadable: Metric (TFM) file no=
t
> > found.
> > <to be read again>
> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0relax
> > l.64 {\Pifont{psy}
> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 }
>
> psyr appears in miktex (pre-latest upgrade) both as part of package
> (?) ly1 and package symbol. =A0today it seems only to be in symbol.
>
> if that interpretation (of mine) is right, you might get resolution by
> loading package symbol, too.
>
> (note i don't know what the things you install files with, in miktex,
> are called -- i've used "package", which seems reasonable.)
>
> > I will try the same file on my non-updated (non-corrupted?) MikTeX
> > system at home.
>
> what you now have, i think, is not so much "corrupt" as "differently
> arranged". =A0of course, it's easy for the likes of me, with more disc
> space available than i know what do with and no bandwidth constraints
> -- so i don't mind having two copies of things. =A0as a result i am
> always able to run my tex live and miktex systems as full installs.
> --
> Robin Fairbairns, Cambridge
> my address is @cl.cam.ac.uk, regardless of the header. =A0sorry about tha=
t.- Hide quoted text -
>
> - Show quoted text -


Robin,

Thanks.  You hit the nail on the head.  The state of my understanding
is that I know what and how but not why.

In the latest MiKTeX update (1/20), I got "No updates available". I
double checked to be sure the problem still persisted. I then did some
digging.

In  C:\Program Files\MiKTeX 2.9\fonts\tfm\adobe\ly1\,  psyr.tfm is, in
fact, missing. I then installed the symbol package and hit all the
refresh buttons.

psyr.tfm is now present in  C:\Program Files\MiKTeX 2.9\fonts\tfm\adobe
\symbol\ and, in fact, is the only file. LaTeX now compiles with no
problems. Game over. Apparently (but I wouldn't bet the farm), this
satisfied LaTeX in the search for the file.

How and why did this happen for what should be a straightforward
update to a working system?

Roy <rbethel@mitre.org> writes:

> On Jan 19, 3:11�pm, Robin Fairbairns <r...@slogin-serv3.cl.cam.ac.uk>
> wrote:
>> psyr appears in miktex (pre-latest upgrade) both as part of package
>> (?) ly1 and package symbol. �today it seems only to be in symbol.
>>
>> if that interpretation (of mine) is right, you might get resolution by
>> loading package symbol, too.
>
> Thanks.  You hit the nail on the head.  The state of my understanding
> is that I know what and how but not why.
>
> In the latest MiKTeX update (1/20), I got "No updates available". I
> double checked to be sure the problem still persisted. I then did some
> digging.
>
> In  C:\Program Files\MiKTeX 2.9\fonts\tfm\adobe\ly1\,  psyr.tfm is, in
> fact, missing. I then installed the symbol package and hit all the
> refresh buttons.
>
> psyr.tfm is now present in  C:\Program Files\MiKTeX 2.9\fonts\tfm\adobe
> \symbol\ and, in fact, is the only file. LaTeX now compiles with no
> problems. Game over. Apparently (but I wouldn't bet the farm), this
> satisfied LaTeX in the search for the file.
>
> How and why did this happen for what should be a straightforward
> update to a working system?

who knows?  (apart from christian schenk, who maintains miktex, that
is.)

i would guess he thought it would be a trivial change, resulting in
one less file on a "standard" system ... since he hadn't imagined that
there would be people who _didn't_ have "symbol" (14 small files only)
loaded.
-- 
Robin Fairbairns, Cambridge
my address is @cl.cam.ac.uk, regardless of the header.  sorry about that.

On Jan 24, 11:08=A0am, Robin Fairbairns <r...@slogin-serv3.cl.cam.ac.uk>
wrote:
> Roy <rbet...@mitre.org> writes:
> > On Jan 19, 3:11=A0pm, Robin Fairbairns <r...@slogin-serv3.cl.cam.ac.uk>
> > wrote:
> >> psyr appears in miktex (pre-latest upgrade) both as part of package
> >> (?) ly1 and package symbol. =A0today it seems only to be in symbol.
>
> >> if that interpretation (of mine) is right, you might get resolution by
> >> loading package symbol, too.
>
> > Thanks. =A0You hit the nail on the head. =A0The state of my understandi=
ng
> > is that I know what and how but not why.
>
> > In the latest MiKTeX update (1/20), I got "No updates available". I
> > double checked to be sure the problem still persisted. I then did some
> > digging.
>
> > In =A0C:\Program Files\MiKTeX 2.9\fonts\tfm\adobe\ly1\, =A0psyr.tfm is,=
 in
> > fact, missing. I then installed the symbol package and hit all the
> > refresh buttons.
>
> > psyr.tfm is now present in =A0C:\Program Files\MiKTeX 2.9\fonts\tfm\ado=
be
> > \symbol\ and, in fact, is the only file. LaTeX now compiles with no
> > problems. Game over. Apparently (but I wouldn't bet the farm), this
> > satisfied LaTeX in the search for the file.
>
> > How and why did this happen for what should be a straightforward
> > update to a working system?
>
> who knows? =A0(apart from christian schenk, who maintains miktex, that
> is.)
>
> i would guess he thought it would be a trivial change, resulting in
> one less file on a "standard" system ... since he hadn't imagined that
> there would be people who _didn't_ have "symbol" (14 small files only)
> loaded.
> --
> Robin Fairbairns, Cambridge
> my address is @cl.cam.ac.uk, regardless of the header. =A0sorry about tha=
t.- Hide quoted text -
>
> - Show quoted text -

What even makes it stranger is that at home the symbol package is
installed and the ly1 package is missing. Both home and work now are
fine. I am not sure if ly1 is (anymore?) part of the standard
distribution. MiKTeX 2.9 was installed last fall on both home and
work. At this point, I have no explanation.

Roy

Am Mon, 24 Jan 2011 16:08:50 +0000 schrieb Robin Fairbairns:

>> How and why did this happen for what should be a straightforward
>> update to a working system?
 
> who knows?  (apart from christian schenk, who maintains miktex, that
> is.)

I haven't checked in this case. But sometimes when (MikTeX)-packages
are rearranged miktex can get confused and looks for a file in the
wrong package. In this cases it often helps 
- to synchronize the repository database (in the menu in the package
manager)
- to update the FNDB in user + admin mode. 


-- 
Ulrike Fischer 

I have the exact same problem. I installed MikTex 2.9 on a fresh
system
and got the "l.64 {\Pifont{psy}" error mentioned by Roy, and could not
work around it other than uninstalling 2.9 and installing 2.8.
MikTeX 2.9 is obviously broken...
This is on W7x64pro.

On Jan 19, 7:26=A0pm, Roy <rbet...@mitre.org> wrote:
> On Jan 19, 11:43=A0am, Robin Fairbairns <r...@warp.cl.cam.ac.uk> wrote:
>
> > Roy <rbet...@mitre.org> writes:
> > > In the latest update (1/18) for MikTeX 2.9 , Ly1 is apparrently
> > > broken. MikTeX is requesting a missing file from it and stops.
>
> > > After trial and error, a workaround is to hit cancel and enter. =A0Th=
e
> > > compilation is OK in spite of the error.
>
> > the ly1 bundle has been updated in tex live, too, and a trivial test
> > shows no problem.
>
> > could you show code that fails for you under miktex? =A0(i've old mikte=
x
> > versions, and installing 2.9 for this is more time than i have
> > available...)
> > --
> > Robin Fairbairns, Cambridge
> > my address is @cl.cam.ac.uk, regardless of the header. =A0sorry about t=
hat.
>
> Robin,
>
> Thank you for your interest. =A0The TexFile.tex is a technical article
> using Elsiever's =A0elsarticle.cls (based on LaTeX article.cls) which
> uses tx font. It worked fine until the latest update. All I did was
> very minor editing (I think). I don't think the error can be isolated
> in the source *.tex.
>
> This is the output of TexFile.log in "error mode" =A0x <enter> (produces
> error) as opposed to just <enter> (produces no error).
>
> LaTeX Font Info: =A0 =A0Try loading font information for U+psy on input
> line 64.
>
> ("C:\Program Files\MiKTeX 2.9\tex\latex\psnfss\upsy.fd"
> File: upsy.fd 2001/06/04 font definitions for U/psy.
> )
> ! Font U/psy/m/n/10=3Dpsyr at 10.0pt not loadable: Metric (TFM) file not
> found.
> <to be read again>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0relax
> l.64 {\Pifont{psy}
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 }
>
> The find error in WinEdt takes you to =A0line 64 in pifont.sty. =A0I had
> no clue that pifont.sty was ever called even in "no error mode".
> MikTex tries to (re-?)install ly1. I unstalled and installed ly1. No
> difference. I also hit all the MiKTeX refresh buttons.
>
> {\Pifont{pzd}}
> {\Pifont{psy}} =A0 =A0 =A0 =A0 =A0<<--- =A0 Line 64 in pifont.sty
> \endinput
> %%
> %% End of file `pifont.sty'.
>
> I will try the same file on my non-updated (non-corrupted?) MikTeX
> system at home.
>
> Roy

OppfinnarJocke <oppfinnarjocke@gmail.com> writes:

> I have the exact same problem. I installed MikTex 2.9 on a fresh
> system
> and got the "l.64 {\Pifont{psy}" error mentioned by Roy, and could not
> work around it other than uninstalling 2.9 and installing 2.8.
> MikTeX 2.9 is obviously broken...
> This is on W7x64pro.

we (ctan) have mirrored new miktex stuff since this originally arose; so
presumably the problem hasn't been addressed.  i take it that no-one has
bothered to mention this on the miktex support list? -- it's what i
suggested, and it's obvious, now, that christian doesn't read
comp.text.tex...
-- 
Robin Fairbairns, Cambridge
my address is @cl.cam.ac.uk, regardless of the header.  sorry about that.

Am Tue, 08 Feb 2011 09:23:03 +0000 schrieb Robin Fairbairns:

 
>> I have the exact same problem. I installed MikTex 2.9 on a fresh
>> system
>> and got the "l.64 {\Pifont{psy}" error mentioned by Roy, and could not
>> work around it other than uninstalling 2.9 and installing 2.8.
>> MikTeX 2.9 is obviously broken...
>> This is on W7x64pro.
> 
> we (ctan) have mirrored new miktex stuff since this originally arose; so
> presumably the problem hasn't been addressed.  i take it that no-one has
> bothered to mention this on the miktex support list? -- it's what i
> suggested, and it's obvious, now, that christian doesn't read
> comp.text.tex...

Well I checked the files in the miktex-packages: psyr.tfm is in the
symbol package (but not in the ly1 package). I also deinstalled ly1
+ symbol and tried a small document and the symbol package with
psyr.tfm was installed without problem on the fly. 

If the file moved (or was removed) from ly1 package, then it is
quite possible that some installations gets confused and look for
the file at the wrong place. But there is nothing miktex can do
about it, the users have to synchronize their repositories databases
and update the FNDB's -- and if they have multiuser setups they will
probably have to do it as admin + and as user (I wish more users
would install simply in their account as single user, this would
avoid a lot confusion).


-- 
Ulrike Fischer 

Ulrike Fischer <news3@nililand.de> writes:

> Am Tue, 08 Feb 2011 09:23:03 +0000 schrieb Robin Fairbairns:
>  
>>> I have the exact same problem. I installed MikTex 2.9 on a fresh
>>> system
>>> and got the "l.64 {\Pifont{psy}" error mentioned by Roy, and could not
>>> work around it other than uninstalling 2.9 and installing 2.8.
>>> MikTeX 2.9 is obviously broken...
>>> This is on W7x64pro.
>> 
>> we (ctan) have mirrored new miktex stuff since this originally arose; so
>> presumably the problem hasn't been addressed.  i take it that no-one has
>> bothered to mention this on the miktex support list? -- it's what i
>> suggested, and it's obvious, now, that christian doesn't read
>> comp.text.tex...
>
> Well I checked the files in the miktex-packages: psyr.tfm is in the
> symbol package (but not in the ly1 package). I also deinstalled ly1
> + symbol and tried a small document and the symbol package with
> psyr.tfm was installed without problem on the fly. 

i suggested the op (the original op) should load the symbol package, and
we didn't hear again.

> If the file moved (or was removed) from ly1 package, then it is
> quite possible that some installations gets confused and look for
> the file at the wrong place. But there is nothing miktex can do
> about it, the users have to synchronize their repositories databases
> and update the FNDB's -- and if they have multiuser setups they will
> probably have to do it as admin + and as user (I wish more users
> would install simply in their account as single user, this would
> avoid a lot confusion).

the problem is people who don't have full installs -- in particular
those who don't have symbol.

_i_ thought that miktex would either load the relevant package for you,
or ask you to do so, but this evidently isn't the case in these users'
systems.  perhaps i should avoid responding on miktex matters ... wdyt?
-- 
Robin Fairbairns, Cambridge
my address is @cl.cam.ac.uk, regardless of the header.  sorry about that.

Am Tue, 08 Feb 2011 11:18:54 +0000 schrieb Robin Fairbairns:

>> If the file moved (or was removed) from ly1 package, then it is
>> quite possible that some installations gets confused and look for
>> the file at the wrong place. But there is nothing miktex can do
>> about it, the users have to synchronize their repositories databases
>> and update the FNDB's -- and if they have multiuser setups they will
>> probably have to do it as admin + and as user (I wish more users
>> would install simply in their account as single user, this would
>> avoid a lot confusion).
 
> the problem is people who don't have full installs -- in particular
> those who don't have symbol.

If a package/file is simply missing (like psyr.tfm after I
deinstalled the packages) it will be installed on-the-fly when a
document request it. 

Problems start when packages are reorganisized: Then the local
database which contains the description of the contents of the
packages can get out of sync. If miktex thinks that the file has
been installed with package A and the file is moved to package B it
can happen that miktex neither find it nor installs it on-the-fly.
This problems can also arise if you have a full install. 


-- 
Ulrike Fischer 

On Feb 8, 6:50=A0am, Ulrike Fischer <ne...@nililand.de> wrote:
> Am Tue, 08 Feb 2011 11:18:54 +0000 schrieb Robin Fairbairns:
>
> >> If the file moved (or was removed) from ly1 package, then it is
> >> quite possible that some installations gets confused and look for
> >> the file at the wrong place. But there is nothing miktex can do
> >> about it, the users have to synchronize their repositories databases
> >> and update the FNDB's -- and if they have multiuser setups they will
> >> probably have to do it as admin + and as user (I wish more users
> >> would install simply in their account as single user, this would
> >> avoid a lot confusion).
> > the problem is people who don't have full installs -- in particular
> > those who don't have symbol.
>
> If a package/file is simply missing (like psyr.tfm after I
> deinstalled the packages) it will be installed on-the-fly when a
> document request it.
>
> Problems start when packages are reorganisized: Then the local
> database which contains the description of the contents of the
> packages can get out of sync. If miktex thinks that the file has
> been installed with package A and the file is moved to package B it
> can happen that miktex neither find it nor installs it on-the-fly.
> This problems can also arise if you have a full install.
>
> --
> Ulrike Fischer

Robin,

I did follow your advice and confirmed your's and Ulrike's
observations.  Check Jan. 21 and Jan. 25.

It appears that whatever the symptons, the cure is to have symbol
installed and sync'ed. I don't know why it was on my home system but
not my office.

I would be curious (but not enough to actually try this) to see what
would happen on a clean install of 2.9 today.

Now, if only a fire could be lit under STIX. :)

Roy