obsolete

texlive-2016-48.20160520.fc28 and texlive-base-20170520-38.fc28

FEDORA-2018-300a2ceaab created by spot 6 years ago for Fedora 28

Add fvextra, make pythontex require it explicitly.

This update has been submitted for testing by spot.

6 years ago
User Icon pdestefa commented & provided feedback 6 years ago
karma

During install of package, I get this error:

================================================================================================================ Package Arch Version Repository Size ================================================================================================================ Upgrading: texlive noarch 6:2016-48.20160520.fc28 @commandline 36 k texlive-base x86_64 7:20170520-38.fc28 @commandline 931 k

Transaction Summary

Upgrade 2 Packages

Total size: 967 k Is this ok [y/N]: y Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Error: Transaction check error: file /usr/share/texmf from install of texlive-base-7:20170520-38.fc28.x86_64 conflicts with file from package R-core-3.4.4-1.fc28.x86_64

Error Summary

Also, after upgrade, I still get this error from pdflatex: ! LaTeX Error: File `fvextra.sty' not found.

This update has been pushed to testing.

6 years ago

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

6 years ago
User Icon basilrabi commented & provided feedback 6 years ago
karma

Works for me.

@pdestefa, you should remove R first then update texlive. There were some file conflicts in R prior to version R-3.5.0-4.fc28 and the work around is just to re-install R-3.5.0-4.fc28 after installing texlive. I think in your case, texlive was not successfully updated due to a file conflict from an old version of R.

User Icon imabug provided feedback 6 years ago
karma

I did remove R to install the package, but that didn't solve the problem with fvextra.sty missing. Did you really test it? I did.

@pdestefa : The texlive-2016-48.20160520.fc28 package has a new texlive-fvextra subpackage, which Provides: tex(fvextra.sty). The texlive-base-20170520-38.fc28 package (which generates the texlive-pythontex subpackage) has been changed so that texlive-pythontex has an explicit Requires: tex(fvextra.sty).

Your log shows you upgrading texlive and texlive-base. Try upgrading texlive-pythontex (it should pull in texlive-fvextra as a dependency).

Ah! Okay, I didn't understand what the text in this update meant. I found an update package on updates-testing.

However, my MWE still will not build, although the error is not related to fvextra, now. Since I only changed -pythontex and -fvextra pkgs, I'm worried one of them introduced some new problem. I see this now:

...
 [1{/usr/share/texlive/texmf-dist/fonts/map/pdftex/updmap/pdftex.map}]
[2] (./standalone.aux)
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 0+438/600 --dpi 438 txsys
mktexpk: don't know how to create bitmap font for txsys.
mktexpk: perhaps txsys is missing from the map file.
kpathsea: Appending font creation commands to missfont.log.
 )
!pdfTeX error: pdflatex (file txsys): Font txsys at 438 not found
 ==> Fatal error occurred, no output PDF file produced!
==

... So, poking around a bit, I became suspicious of mktexpk and looked into updmap. I had some old .texlive/ directories, which I deleted, and I reran updmap systemwide. Does that sound right?

My MWE now builds and seems to look okay, although I'm worried why I had to rebuild the updmap.

This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes

6 years ago

This update has been obsoleted by texlive-base-20170520-39.fc28.

6 years ago

Please log in to add feedback.

Metadata
Type
bugfix
Karma
1
Signed
Content Type
RPM
Test Gating
Autopush Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Thresholds
Minimum Karma
+1
Minimum Testing
7 days
Dates
submitted
6 years ago
in testing
6 years ago
BZ#1590621 pythontex requires fvextra.sty but doesn't include it and package doesn't require it
0
0

Automated Test Results