Re: [gentoo-user] What does emerge status R mean?
On 5/14/21 6:07 PM, Jack wrote: On 5/14/21 3:54 AM, n952162 wrote: Why does portage want to build this: [ebuild R ] x11-apps/xmodmap-1.0.10::gentoo 0 KiB given this, already installed: /var/db/pkg/x11-apps/xmodmap-1.0.10/xmodmap-1.0.10.ebuild and these on my binary server (which is apparently not working properly for reasons I'm trying to track down): binpkgs/x11-apps/xmodmap-1.0.10.tbz2 distfiles/xmodmap-1.0.10.tar.bz2 When I remove these options, it doesn't want to anymore: # --changed-use \ # --changed-deps \ # --newuse \ # --backtrack=100 \ # --deep \ Which option was it, I wonder, which triggered the build, and would it bring me anything? My guess is that one of the USE flags changed. Compare which USE flags is it currently installed with and which it wants for the reinstall. It might even be that a USE flag changed in the ebuild, even if it won't actually change what gets installed. (--changed-use vs --new-use) There are no use flags defined for any of the packages I did a random check for, either on the server or the client. I am worried that it is as you say: that the ebuild has a change of USE flags, which, of course, has nothing to do with me, the user. I wish dearly that I could find a print out of the reasons why a package is rejected, listing new and old USE flags, for example.
Re: [gentoo-user] What does emerge status R mean?
On 5/14/21 8:11 PM, Neil Bothwick wrote: On Fri, 14 May 2021 11:54:30 +0200, n952162 wrote: Why does portage want to build this: [ebuild R ] x11-apps/xmodmap-1.0.10::gentoo 0 KiB given this, already installed: /var/db/pkg/x11-apps/xmodmap-1.0.10/xmodmap-1.0.10.ebuild and these on my binary server (which is apparently not working properly for reasons I'm trying to track down): binpkgs/x11-apps/xmodmap-1.0.10.tbz2 distfiles/xmodmap-1.0.10.tar.bz2 When I remove these options, it doesn't want to anymore: # --changed-use \ # --changed-deps \ # --newuse \ # --backtrack=100 \ # --deep \ Which option was it, I wonder, which triggered the build, and would it bring me anything? --changed-use would show the changed USE flag in the output, so it is probably --changed-deps. The emerge man page explains just what the flag does. I haven't been able to find that display yet. I have found this: * Messages for package virtual/dev-manager-0-r2: * emerge --keep-going: virtual/dev-manager-0-r2 dropped because it requires * sys-apps/busybox[mdev] Is this what you're referring to? In one build, I have tons of these, but in a way that's confusing me now, they refer to packages that seem to have been inexplicably dropped. Incidentally, there is no point in using --newuse and --changed-use, the former is a superset of the latter. I'd use only --changed-use to avoid unnecessary rebuilds. That's useful, thank you.
Re: [gentoo-user] What does emerge status R mean?
On 5/15/21 7:24 AM, Dan Egli wrote: The R status means REBUILD. Usually, if it's an @world it's pulling that in because something about that package changed and so it needs to rebuild it. The --noreplace option would block that if portage didn't think it was needed. Based on your options, I'd say that it's probably a USE flag was changed. I don't use binpkgs myself, preferring to compile except in certain circumstances (can we say RUST!?) that I need to use a -bin variant. You can try without it, but I recommend leaving your change-use and newuse flags in place and letting the system rebuild xmodmap. Yes, thank you, but neither the server nor the client have any USE flags for that package defined. And the package has to be pretty stable by now ;-)
Re: [gentoo-user] What does emerge status R mean?
On Sun, 16 May 2021 11:11:54 +0200, n952162 wrote: > > My guess is that one of the USE flags changed. Compare which USE > > flags is it currently installed with and which it wants for the > > reinstall. It might even be that a USE flag changed in the ebuild, > > even if it won't actually change what gets installed. (--changed-use > > vs --new-use) > > > There are no use flags defined for any of the packages I did a random > check for, either on the server or the client. I am worried that it is > as you say: that the ebuild has a change of USE flags, which, of course, > has nothing to do with me, the user. As already stated, any USE flag changes would appear in the emerge output, this is most likely caused by --changed-deps. Try with --changed-use but without --changed-deps to see. -- Neil Bothwick Dance like no-one's watching. / Encrypt like everyone is. pgpITUt4N7BzI.pgp Description: OpenPGP digital signature
Re: [gentoo-user] What does emerge status R mean?
On 5/16/21 11:23 AM, Neil Bothwick wrote: On Sun, 16 May 2021 11:11:54 +0200, n952162 wrote: My guess is that one of the USE flags changed. Compare which USE flags is it currently installed with and which it wants for the reinstall. It might even be that a USE flag changed in the ebuild, even if it won't actually change what gets installed. (--changed-use vs --new-use) There are no use flags defined for any of the packages I did a random check for, either on the server or the client. I am worried that it is as you say: that the ebuild has a change of USE flags, which, of course, has nothing to do with me, the user. As already stated, any USE flag changes would appear in the emerge output, this is most likely caused by --changed-deps. Try with --changed-use but without --changed-deps to see. I have introduced that into my build script. But, if it's as you say, the one is a subset of the other, it should have no effect on the output, right?
Re: [gentoo-user] What does emerge status R mean?
On Sun, 16 May 2021 11:26:37 +0200, n952162 wrote: > >> There are no use flags defined for any of the packages I did a random > >> check for, either on the server or the client. I am worried that it > >> is as you say: that the ebuild has a change of USE flags, which, of > >> course, has nothing to do with me, the user. > > As already stated, any USE flag changes would appear in the emerge > > output, this is most likely caused by --changed-deps. Try with > > --changed-use but without --changed-deps to see. > > > > > I have introduced that into my build script. But, if it's as you say, > the one is a subset of the other, it should have no effect on the > output, right? > --changed-use is a subset of --newuse. --changed-deps is separate. -- Neil Bothwick Runtime Error: Out of funny taglines! pgpvdcHgZRthR.pgp Description: OpenPGP digital signature
Re: [gentoo-user] What does emerge status R mean?
n952162 wrote: > On 5/15/21 7:24 AM, Dan Egli wrote: >> The R status means REBUILD. Usually, if it's an @world it's pulling >> that in because something about that package changed and so it needs >> to rebuild it. The --noreplace option would block that if portage >> didn't think it was needed. Based on your options, I'd say that it's >> probably a USE flag was changed. I don't use binpkgs myself, >> preferring to compile except in certain circumstances (can we say >> RUST!?) that I need to use a -bin variant. You can try without it, but >> I recommend leaving your change-use and newuse flags in place and >> letting the system rebuild xmodmap. >> >> > Yes, thank you, but neither the server nor the client have any USE flags > for that package defined. And the package has to be pretty stable by > now ;-) > > > > All packages have USE flags defined somewhere even if you haven't defined any yourself. Some are defined in profiles, some are defined elsewhere. When I do updates, I see changes to USE flags all the time that were changed by the profile, the maintainer in the ebuild or somewhere else. After all, if a package doesn't have the USE flags defined somewhere, emerge won't know what USE flags to include or exclude support for. Dale :-) :-)
Re: [gentoo-user] What does emerge status R mean?
On 5/16/21 11:28 AM, Neil Bothwick wrote: On Sun, 16 May 2021 11:26:37 +0200, n952162 wrote: There are no use flags defined for any of the packages I did a random check for, either on the server or the client. I am worried that it is as you say: that the ebuild has a change of USE flags, which, of course, has nothing to do with me, the user. As already stated, any USE flag changes would appear in the emerge output, this is most likely caused by --changed-deps. Try with --changed-use but without --changed-deps to see. I have introduced that into my build script. But, if it's as you say, the one is a subset of the other, it should have no effect on the output, right? --changed-use is a subset of --newuse. --changed-deps is separate. Ah, I oversaw that. Ah. why would I want to have --changed-deps anyway? That suddenly seems silly. It's unfortunate, if there's no explanatory display if a package got disqualified for that reason.
Re: [gentoo-user] What does emerge status R mean?
On 5/16/21 12:01 PM, Dale wrote: n952162 wrote: On 5/15/21 7:24 AM, Dan Egli wrote: The R status means REBUILD. Usually, if it's an @world it's pulling that in because something about that package changed and so it needs to rebuild it. The --noreplace option would block that if portage didn't think it was needed. Based on your options, I'd say that it's probably a USE flag was changed. I don't use binpkgs myself, preferring to compile except in certain circumstances (can we say RUST!?) that I need to use a -bin variant. You can try without it, but I recommend leaving your change-use and newuse flags in place and letting the system rebuild xmodmap. Yes, thank you, but neither the server nor the client have any USE flags for that package defined. And the package has to be pretty stable by now ;-) All packages have USE flags defined somewhere even if you haven't defined any yourself. Some are defined in profiles, some are defined elsewhere. When I do updates, I see changes to USE flags all the time that were changed by the profile, the maintainer in the ebuild or somewhere else. After all, if a package doesn't have the USE flags defined somewhere, emerge won't know what USE flags to include or exclude support for. Dale :-) :-) But if I don't specify that I want something specific, why should portage say, this package has internal differences to the old package, I better not install it?
Re: [gentoo-user] What does emerge status R mean?
On Sun, 16 May 2021 12:49:26 +0200 n952162 wrote: > On 5/16/21 11:28 AM, Neil Bothwick wrote: > > On Sun, 16 May 2021 11:26:37 +0200, n952162 wrote: > > > There are no use flags defined for any of the packages I did a random > check for, either on the server or the client. I am worried that it > is as you say: that the ebuild has a change of USE flags, which, of > course, has nothing to do with me, the user. > >>> As already stated, any USE flag changes would appear in the emerge > >>> output, this is most likely caused by --changed-deps. Try with > >>> --changed-use but without --changed-deps to see. > >>> > >>> > >> I have introduced that into my build script. But, if it's as you say, > >> the one is a subset of the other, it should have no effect on the > >> output, right? > >> > > --changed-use is a subset of --newuse. --changed-deps is separate. > > > > > Ah, I oversaw that. > > Ah. why would I want to have --changed-deps anyway? That suddenly seems > silly. > > It's unfortunate, if there's no explanatory display if a package got > disqualified for that reason. > > If you want to have a binhost, then --changed-deps will become "necessary" at some point. Let me draw you a picture, where a binhost would fail to provide the correct package: - Binhost builds on day 1 package XYZ - computer that would merge with packages from binhost is NOT updated - the dependencies are changed on day 2 - Binhost does NOT rebuild, because you do not have --changed-deps enabled on day 2 - Computer that merges from the binhost is updated on day 2 but will NOT use the binary package from binhost, because the dependencies do not match There are flags to ignore dependency mismatches, but the default would just not use the binary package. Cheers Andreas
Re: [gentoo-user] What does emerge status R mean?
On 5/16/21 12:49 PM, n952162 wrote: On 5/16/21 11:28 AM, Neil Bothwick wrote: On Sun, 16 May 2021 11:26:37 +0200, n952162 wrote: There are no use flags defined for any of the packages I did a random check for, either on the server or the client. I am worried that it is as you say: that the ebuild has a change of USE flags, which, of course, has nothing to do with me, the user. As already stated, any USE flag changes would appear in the emerge output, this is most likely caused by --changed-deps. Try with --changed-use but without --changed-deps to see. I have introduced that into my build script. But, if it's as you say, the one is a subset of the other, it should have no effect on the output, right? --changed-use is a subset of --newuse. --changed-deps is separate. Ah, I oversaw that. Ah. why would I want to have --changed-deps anyway? That suddenly seems silly. It's unfortunate, if there's no explanatory display if a package got disqualified for that reason. Okay, the point is, there's some package on my system that doesn't match what the new version of the depending package requires? Or, just that there's a dependency change at all? If the former, but there's a old version of the needed packet, will portage link with the old version?
Re: [gentoo-user] What does emerge status R mean?
On Sun, 16 May 2021 05:01:18 -0500 Dale wrote: > n952162 wrote: > > On 5/15/21 7:24 AM, Dan Egli wrote: > >> The R status means REBUILD. Usually, if it's an @world it's pulling > >> that in because something about that package changed and so it needs > >> to rebuild it. The --noreplace option would block that if portage > >> didn't think it was needed. Based on your options, I'd say that it's > >> probably a USE flag was changed. I don't use binpkgs myself, > >> preferring to compile except in certain circumstances (can we say > >> RUST!?) that I need to use a -bin variant. You can try without it, but > >> I recommend leaving your change-use and newuse flags in place and > >> letting the system rebuild xmodmap. > >> > >> > > Yes, thank you, but neither the server nor the client have any USE flags > > for that package defined. And the package has to be pretty stable by > > now ;-) > > > > > > > > > > All packages have USE flags defined somewhere even if you haven't > defined any yourself. Some are defined in profiles, some are defined > elsewhere. When I do updates, I see changes to USE flags all the time > that were changed by the profile, the maintainer in the ebuild or > somewhere else. After all, if a package doesn't have the USE flags > defined somewhere, emerge won't know what USE flags to include or > exclude support for. > > Dale > > :-) :-) > I t hink you are confusing enabled USE flags, with package USE flags. A package can have 0 USE flags (e.g. x11-apps/xmodmap, and many more). Enabled USE flags on the other hand are defined by user config files and profiles and by the package itself (i.e. they could be enabled by default). So there can very well be packages that have 0 USE flags, and xmodmap is one of them. The "problem" here is most probably a changed dependency. The dependencies (as defined in the ebuild) under which the package was built on the binhost have changed in the meantime in the ebuild file (without a revbump/version bump), and if the binhost has not enabled the flag "--changed-deps", it did not update the package to the new dependencies. If you really want to debug this, you could do a diff of the files /var/db/pkg/x11-apps/xmodmap-1.0.10/xmodmap-1.0.10.ebuild /usr/portage/x11-apps/xmodmap/xmodmap-1.0.10.ebuild (or whatever your portage root directory is, I'm still using /usr/portage). That diff should be on the binhost! Cheers Andreas
Re: [gentoo-user] What does emerge status R mean?
On 5/16/21 12:53 PM, Andreas Fink wrote: On Sun, 16 May 2021 12:49:26 +0200 n952162 wrote: On 5/16/21 11:28 AM, Neil Bothwick wrote: On Sun, 16 May 2021 11:26:37 +0200, n952162 wrote: There are no use flags defined for any of the packages I did a random check for, either on the server or the client. I am worried that it is as you say: that the ebuild has a change of USE flags, which, of course, has nothing to do with me, the user. As already stated, any USE flag changes would appear in the emerge output, this is most likely caused by --changed-deps. Try with --changed-use but without --changed-deps to see. I have introduced that into my build script. But, if it's as you say, the one is a subset of the other, it should have no effect on the output, right? --changed-use is a subset of --newuse. --changed-deps is separate. Ah, I oversaw that. Ah. why would I want to have --changed-deps anyway? That suddenly seems silly. It's unfortunate, if there's no explanatory display if a package got disqualified for that reason. Trying to comprehend here... If you want to have a binhost, then --changed-deps will become "necessary" at some point. Let me draw you a picture, where a binhost would fail to provide the correct package: - Binhost builds on day 1 package XYZ(i.e. server updates from internet) - computer that would merge with packages from binhost is NOT updated(client does NO emerge on that day) - the dependencies are changed on day 2(i.e. XYZ is emerged onto server, with changed dependencies in the ebuild) - Binhost does NOT rebuild, because you do not have --changed-deps enabled on day 2*(what is "Binhost" here? The --changed-deps is specified on the client)* - Computer that merges from the binhost is updated on day 2 but will NOT use the binary package from binhost, because the dependencies do not match There are flags to ignore dependency mismatches, but the default would just not use the binary package. Cheers Andreas What does changed-deps mean, actually? --changed-deps [ y | n ] Tells emerge to replace installed packages for which the corresponding ebuild dependencies have changed since the packages were built. ... I presume it means that a package needed XYZ before, but now needs XYZZ. If I don't specify --changed-deps, that I might get a run-time resolution problem. Or, does it mean that the package specified XYZ.1 in an excess of precision and the new version specifies XYZ.3? I just ran into this: --binpkg-changed-deps [ y | n ] Tells emerge to ignore binary packages for which the corresponding ebuild dependencies have changed since the packages were built. In order to help avoid issues with resolving inconsistent dependencies, this option is auto- matically enabled unless the --usepkgonly option is enabled. Behavior with respect to changed build-time dependencies is controlled by the --with-bdeps option. But I haven't figured out what it means yet. In particular, what all the stated implications mean.
Re: [gentoo-user] What does emerge status R mean?
On Sun, 16 May 2021 13:14:26 +0200 n952162 wrote: > On 5/16/21 12:53 PM, Andreas Fink wrote: > > On Sun, 16 May 2021 12:49:26 +0200 > > n952162 wrote: > > > >> On 5/16/21 11:28 AM, Neil Bothwick wrote: > >>> On Sun, 16 May 2021 11:26:37 +0200, n952162 wrote: > >>> > >> There are no use flags defined for any of the packages I did a random > >> check for, either on the server or the client. I am worried that it > >> is as you say: that the ebuild has a change of USE flags, which, of > >> course, has nothing to do with me, the user. > > As already stated, any USE flag changes would appear in the emerge > > output, this is most likely caused by --changed-deps. Try with > > --changed-use but without --changed-deps to see. > > > > > I have introduced that into my build script. But, if it's as you say, > the one is a subset of the other, it should have no effect on the > output, right? > > >>> --changed-use is a subset of --newuse. --changed-deps is separate. > >>> > >>> > >> Ah, I oversaw that. > >> > >> Ah. why would I want to have --changed-deps anyway? That suddenly seems > >> silly. > >> > >> It's unfortunate, if there's no explanatory display if a package got > >> disqualified for that reason. > >> > >> > > Trying to comprehend here... > > > If you want to have a binhost, then --changed-deps will become > > "necessary" at some point. Let me draw you a picture, where a binhost > > would fail to provide the correct package: > > - Binhost builds on day 1 package XYZ(i.e. server updates from internet) > > - computer that would merge with packages from binhost is NOT > > updated(client does NO emerge on that day) > > - the dependencies are changed on day 2(i.e. XYZ is emerged onto server, > > with changed dependencies in the ebuild) > > - Binhost does NOT rebuild, because you do not have --changed-deps > > enabled on day 2*(what is "Binhost" here? The --changed-deps is > > specified on the client)* > > - Computer that merges from the binhost is updated on day 2 but will > > NOT use the binary package from binhost, because the dependencies do > > not match > > There are flags to ignore dependency mismatches, but the default would > > just not use the binary package. > > > > Cheers > > Andreas > > > What does changed-deps mean, actually? > > --changed-deps [ y | n ] > Tells emerge to replace installed packages for which > the corresponding > ebuild dependencies have changed since the packages were > built. ... > > I presume it means that a package needed XYZ before, but now needs > XYZZ. If I don't specify --changed-deps, that I might get a run-time > resolution problem. Changed dependencies means any change in the *.ebuild file with respect to the variables DEPEND/BDEPEND/RDEPEND/PDEPEND, e.g. version of a dependent package has changed, new package was added as dependency, a package was removed as dependency. All are dependency changes. If the changed *.ebuild file is commited to the portage tree WITHOUT a version-bump/revision-bump, then emerge would NOT rebuild the package, unless --changed-deps is given as an argument. > > Or, does it mean that the package specified XYZ.1 in an excess of > precision and the new version specifies XYZ.3? > > I just ran into this: > > --binpkg-changed-deps [ y | n ] > Tells emerge to ignore binary packages for which the > corresponding ebuild > dependencies have changed since the packages were built. > In order to help > avoid issues with resolving inconsistent dependencies, > this option is auto- > matically enabled unless the --usepkgonly option is > enabled. Behavior with > respect to changed build-time dependencies is controlled > by the --with-bdeps > option. > > But I haven't figured out what it means yet. In particular, what all > the stated implications mean. > This would be the option to ignore dependency mismatches of what the binary package claims its dependencies are (which you could see in $PKGDIR/Packages), and what the resolved dependencies are according to the *.ebuild file as portage is seeing it right now. Cheers Andreas
Re: [gentoo-user] What does emerge status R mean?
On 5/16/21 2:24 PM, Andreas Fink wrote: On Sun, 16 May 2021 13:14:26 +0200 n952162 wrote: On 5/16/21 12:53 PM, Andreas Fink wrote: On Sun, 16 May 2021 12:49:26 +0200 n952162 wrote: On 5/16/21 11:28 AM, Neil Bothwick wrote: On Sun, 16 May 2021 11:26:37 +0200, n952162 wrote: There are no use flags defined for any of the packages I did a random check for, either on the server or the client. I am worried that it is as you say: that the ebuild has a change of USE flags, which, of course, has nothing to do with me, the user. As already stated, any USE flag changes would appear in the emerge output, this is most likely caused by --changed-deps. Try with --changed-use but without --changed-deps to see. I have introduced that into my build script. But, if it's as you say, the one is a subset of the other, it should have no effect on the output, right? --changed-use is a subset of --newuse. --changed-deps is separate. Ah, I oversaw that. Ah. why would I want to have --changed-deps anyway? That suddenly seems silly. It's unfortunate, if there's no explanatory display if a package got disqualified for that reason. Trying to comprehend here... If you want to have a binhost, then --changed-deps will become "necessary" at some point. Let me draw you a picture, where a binhost would fail to provide the correct package: - Binhost builds on day 1 package XYZ(i.e. server updates from internet) - computer that would merge with packages from binhost is NOT updated(client does NO emerge on that day) - the dependencies are changed on day 2(i.e. XYZ is emerged onto server, with changed dependencies in the ebuild) - Binhost does NOT rebuild, because you do not have --changed-deps enabled on day 2*(what is "Binhost" here? The --changed-deps is specified on the client)* - Computer that merges from the binhost is updated on day 2 but will NOT use the binary package from binhost, because the dependencies do not match There are flags to ignore dependency mismatches, but the default would just not use the binary package. Cheers Andreas What does changed-deps mean, actually? --changed-deps [ y | n ] Tells emerge to replace installed packages for which the corresponding ebuild dependencies have changed since the packages were built. ... I presume it means that a package needed XYZ before, but now needs XYZZ. If I don't specify --changed-deps, that I might get a run-time resolution problem. Changed dependencies means any change in the *.ebuild file with respect to the variables DEPEND/BDEPEND/RDEPEND/PDEPEND, e.g. version of a dependent package has changed, new package was added as dependency, a package was removed as dependency. All are dependency changes. If the changed *.ebuild file is commited to the portage tree WITHOUT a version-bump/revision-bump, then emerge would NOT rebuild the package, unless --changed-deps is given as an argument. Or, does it mean that the package specified XYZ.1 in an excess of precision and the new version specifies XYZ.3? I just ran into this: --binpkg-changed-deps [ y | n ] Tells emerge to ignore binary packages for which the corresponding ebuild dependencies have changed since the packages were built. In order to help avoid issues with resolving inconsistent dependencies, this option is auto- matically enabled unless the --usepkgonly option is enabled. Behavior with respect to changed build-time dependencies is controlled by the --with-bdeps option. But I haven't figured out what it means yet. In particular, what all the stated implications mean. This would be the option to ignore dependency mismatches of what the binary package claims its dependencies are (which you could see in $PKGDIR/Packages), and what the resolved dependencies are according to the *.ebuild file as portage is seeing it right now. Cheers Andreas Thank you.
Re: [gentoo-user] What does emerge status R mean?
On Sun, 16 May 2021 11:21:03 +0200, n952162 wrote: > > --changed-use would show the changed USE flag in the output, so it is > > probably --changed-deps. The emerge man page explains just what the > > flag does. > > > I haven't been able to find that display yet. I have found this: Try adding --tree to your options. -- Neil Bothwick Sometimes too much to drink is not enough. pgpqxRJvc3Wu2.pgp Description: OpenPGP digital signature
[gentoo-user] Problems with LyX and xetex-2021
Hello to everyone,
since upgrading my ~arch system to TeXLive-2021 I'm having problems using
XeLaTeX to compile LyX documents. Has someone else experienced this issue? I'd
like to file a bug report about it, but before doing so I'd like to be sure
that there isn't something wrong with my system.
Below you'll find the details of my problem.
Thanks in advance
Stefano
DETAILS
When I use LyX to create a PDF using XeLaTeX from the attached test.lyx file
(using the default LaTeX (XeTeX) -> PDF (XeTeX) converter), I get an error
dialog with the following text:
The external program
xelatex
finished with an error. It is recommended you fix the cause of the external
program's error (check the logs).
As far as I can see, the log (attached as log_from_lyx) don't mention any
error, except for the generic (at least to my eyes) line
"Error 256 (driver return code) generating output;"
near the end.
Trying to obtain a better error message, I exported the LyX file as a XeLaTeX
file using the File/Export LaTeX (xetex) menu entry and run xelatex on it. Of
course, it failed, but this time the log (in the log_from_xelatex attachment)
contains a more meaningful message:
"xdvipdfmx:fatal: Cannot proceed without .vf or "physical" font for PDF
output..."
Unfortunately, I'm not expert enough in the inner works of (xe)latex to
understand this message. I tried searching google for it but didn't find
anything useful. However, looking at the tex file generated by LyX (the
test.tex attachment), I noticed the line
\usepackage[T1]{fontenc}
which seemed strange to me, as I thought that the fontenc package shouldn't be
used with XeLaTeX. Indeed, after commenting this line, xelatex successfully
created the correct PDF.
This problem has almost certainly been caused by switching texlive and the
related packages from 2020 to 2021, since on another computer where I masked
the 2021 version of app-text/texlive-core, app-text/texlive and all packages
in category dev-texlive, everything works correctly.
test.lyx
Description: application/lyx
%% LyX 2.3.6.1 created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[twoside,italian]{article}
\usepackage[T1]{fontenc}
\usepackage[a4paper]{geometry}
\geometry{verbose,tmargin=2cm,bmargin=2cm,lmargin=2cm,rmargin=2cm}
\usepackage{setspace}
\setstretch{1.3}
\usepackage{babel}
\begin{document}
TEST
\end{document}
This is XeTeX, Version 3.141592653-2.6-0.93 (TeX Live 2021 Gentoo Linux)
(preloaded format=xelatex 2021.5.8) 16 MAY 2021 19:29
entering extended mode
restricted \write18 enabled.
%&-line parsing enabled.
**test.tex
(./test.tex
LaTeX2e <2020-10-01> patch level 4
L3 programming layer <2021-02-18>
(/usr/share/texmf-dist/tex/latex/base/article.cls
Document Class: article 2020/04/10 v1.4m Standard LaTeX document class
(/usr/share/texmf-dist/tex/latex/base/size10.clo
File: size10.clo 2020/04/10 v1.4m Standard LaTeX file (size option)
)
\c@part=\count175
\c@section=\count176
\c@subsection=\count177
\c@subsubsection=\count178
\c@paragraph=\count179
\c@subparagraph=\count180
\c@figure=\count181
\c@table=\count182
\abovecaptionskip=\skip47
\belowcaptionskip=\skip48
\bibindent=\dimen138
) (/usr/share/texmf-dist/tex/latex/base/fontenc.sty
Package: fontenc 2020/08/10 v2.0s Standard LaTeX package
LaTeX Font Info:Trying to load font information for T1+lmr on input line 11
2.
(/usr/share/texmf-dist/tex/latex/lm/t1lmr.fd
File: t1lmr.fd 2009/10/30 v1.6 Font defs for Latin Modern
)) (/usr/share/texmf-dist/tex/latex/geometry/geometry.sty
Package: geometry 2020/01/02 v5.9 Page Geometry
(/usr/share/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2014/10/28 v1.15 key=value parser (DPC)
\KV@toks@=\toks15
) (/usr/share/texmf-dist/tex/generic/iftex/ifvtex.sty
Package: ifvtex 2019/10/25 v1.7 ifvtex legacy package. Use iftex instead.
(/usr/share/texmf-dist/tex/generic/iftex/iftex.sty
Package: iftex 2020/03/06 v1.0d TeX engine tests
))
\Gm@cnth=\count183
\Gm@cntv=\count184
\c@Gm@tempcnt=\count185
\Gm@bindingoffset=\dimen139
\Gm@wd@mp=\dimen140
\Gm@odd@mp=\dimen141
\Gm@even@mp=\dimen142
\Gm@layoutwidth=\dimen143
\Gm@layoutheight=\dimen144
\Gm@layouthoffset=\dimen145
\Gm@layoutvoffset=\dimen146
\Gm@dimlist=\toks16
) (/usr/share/texmf-dist/tex/latex/setspace/setspace.sty
Package: setspace 2011/12/19 v6.7a set line spacing
) (/usr/share/texmf-dist/tex/generic/babel/babel.sty
Package: babel 2021/03/03 3.55 The Babel package
(/usr/share/texmf-dist/tex/generic/babel/babel.def
File: babel.def 2021/03/03 3.55 Babel common definitions
\babel@savecnt=\count186
\U@D=\dimen147
\l@babelnohyphens=\language10
(/usr/share/texmf-dist/tex/generic/babel/xebabel.def (/usr/share/texmf-dist/tex
/generic/babel/txtbabel.def))
\bbl@readstream=\read2
)
\bbl@dirlevel=\count187
(/usr/share/texmf-dist/tex/generic/babel-italian/italian.ldf
Language: italian 2020/05/21 v.1.4.04 Italian support for the babel system
\it@lettering=\count
