Bug 32249 - We don't package lot of texlive complements
Summary: We don't package lot of texlive complements
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Marc Krämer
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-05 20:30 CEST by katnatek
Modified: 2023-09-11 08:57 CEST (History)
0 users

See Also:
Source RPM: texlive
CVE:
Status comment:


Attachments

Description katnatek 2023-09-05 20:30:12 CEST
Description of problem:

I try to fix bug#28938 , but not found nothing in the build flow that make that ten first items in the help of lyx don't works, searching in other specs i see that suse's spec (https://build.opensuse.org/package/view_file/openSUSE:Leap:15.5:Update/lyx/lyx.spec?expand=1) recommends texlive complements not packaged by mageia.

Not sure but as some of them are marked as "Some stuff needed for LyX's documentation" his absence could be the root cause of the bug

If is required i open a bug for each module but are a lot.
katnatek 2023-09-05 20:31:19 CEST

Blocks: (none) => 28938

Comment 1 Lewis Smith 2023-09-05 21:25:57 CEST
Thank you for the report, and your research.
Please do NOT open a bug for each texlive-* Recommends.

Looking at that other bug, your comment 7
 https://bugs.mageia.org/show_bug.cgi?id=28938#c7
mentions many texlive Recommends named 'texlive-*'. It seems that in offering texlive (very basic), we should offer all of it...

Assigning to Marc who nurses texlive (which looks to be the the cause of that related bug).

Component: New RPM package request => RPM Packages
Source RPM: (none) => texlive
Assignee: bugsquad => mageia
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=28938

Comment 2 katnatek 2023-09-09 21:04:05 CEST
Marc Krämer , help me to see the difference between mageia packaging of texlive and other distros so i can focus on all updmap [ERROR] on installing lyx (https://bugs.mageia.org/attachment.cgi?id=12715)

CountriesOfEurope.map could be a bad configuration in /usr/share/texmf-dist/web2c/updmap.cfg (texlive-texmf-20220321-12.mga9.src.rpm) the file in mageia is lowercase and is part of texlive-dist

droid.map is not provide by mageia, provided in other distros in texlive-droid
morisawa.map  is not provide by mageia, provided in other distros as texlive-ptex but i think in mageia could be part of texlive-fonts-asian


other .map are part of texlive-fonts-asian ,texlive-context so no problem

I will asume that texlive in mageia is, as long as i found, as complete as in any other distro with the exception of the cases above
Comment 3 Marc Krämer 2023-09-10 12:13:03 CEST
If these files are not found, only a few things may get broken. But this is not essential. I regulary run latex (pdftex). So lyx will run as well, with or without these files. And e.g. asian language is only needed, if you really want them. Otherwise you can skip them. Please don't make lyx require all texlive stuff. Only the basics should be inclueded, and otherwise the user should/must install the packages missing for lyx.
Comment 4 katnatek 2023-09-11 00:40:56 CEST
(In reply to Marc Krämer from comment #3)
> If these files are not found, only a few things may get broken. But this is
> not essential. I regulary run latex (pdftex). So lyx will run as well, with
> or without these files. And e.g. asian language is only needed, if you
> really want them. Otherwise you can skip them. Please don't make lyx require
> all texlive stuff. Only the basics should be inclueded, and otherwise the
> user should/must install the packages missing for lyx.

I was thinking in split a package with the optional requieres but not feel are too much, BTW my spec i just a suggestion and mageia's packager can take other direction and make enhances.

about texlive-droid and texlive-ptex packaging i respect whatever be the final decision
Comment 5 katnatek 2023-09-11 00:43:07 CEST
Remove the block status due comment#3

Blocks: 28938 => (none)

Comment 6 Marc Krämer 2023-09-11 08:57:25 CEST
I am closing this bug, as nothing is to be done.

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.