Thanks for this report.

 texlive-collection-basic includes (among loads of binaries/man pages):
/usr/share/man/man1/ps2eps.1.xz     for texlive
/usr/share/man/man1/ps2frag.1.xz    ?
/usr/share/man/man1/ps2pk.1.xz      for texlive
/usr/share/man/man1/psjoin.1.xz     *** in psutils pkg
/usr/share/man/man1/pslatex.1.xz    ?
/usr/share/man/man1/psutils.1.xz    *** in psutils pkg

 $ urpmf /usr/bin/ps2eps
texlive:/usr/bin/ps2eps
 $ urpmf /usr/bin/ps2frag   ?
[nothing]
 $ urpmf /usr/bin/ps2pk
texlive:/usr/bin/ps2pk
 $ urpmf /usr/bin/psjoin
psutils:/usr/bin/psjoin
 $ urpmf /usr/bin/pslatex   ?
[nothing]

 $ urpmq -l texlive | grep /bin/ps
/usr/bin/ps2eps
/usr/bin/ps2pk
 but texlive itself provides no man pages.

 $ urpmq -l psutils | grep /bin/ps
/usr/bin/psbook
/usr/bin/psjoin     ***
/usr/bin/psnup
/usr/bin/psresize
/usr/bin/psselect
/usr/bin/pstops
 $ urpmq -l psutils | grep /man1/ps
/usr/share/man/man1/psbook.1.xz
/usr/share/man/man1/psjoin.1.xz    ***
/usr/share/man/man1/psnup.1.xz
/usr/share/man/man1/psresize.1.xz
/usr/share/man/man1/psselect.1.xz
/usr/share/man/man1/pstops.1.xz
/usr/share/man/man1/psutils.1.xz   ***

So it looks simply that (as Giuseppe pointed) texlive-collection-basic should not include the two man pages highlightedn those being in pkg psutils with the binaries.

Assigning this to Marc for the SRPM.

URL: texlive-collection-basic => (none)
Assignee: bugsquad => mageia

that will be a huge update for just removing 2 man-pages :(

I have both packages installed and wonder why I did not get a warning during install.

fixed in cauldron, should we really push this update for mga8?

Yes, why not?

just because it is a big package and everyone has to download this again for just removing 2 manpages out of it.

Well, I think it's worthwhile even if big files are involved. The problem is not just cosmetic about some missed manpage, or that a manpage is better belonging to one package instead of another, but of installation conflicts, as both packages are pretty common.

Updated texlive package to correct a packaging bug:
two man-page files belonging to psutils were added in this package.

========================

Updated packages in core/updates_testing:
========================


texlive-fonts-asian-20200406-7.mga8.noarch.rpm
texlive-collection-basic-20200406-7.mga8.noarch.rpm
texlive-context-20200406-7.mga8.noarch.rpm
texlive-fonts-sources-20200406-7.mga8.noarch.rpm
texlive-texmf-20200406-7.mga8.noarch.rpm
texlive-fontsextra-20200406-7.mga8.noarch.rpm
texlive-dist-20200406-7.mga8.noarch.rpm
texlive-doc-20200406-7.mga8.noarch.rpm

SRPM:
texlive-texmf-20200406-7.mga8.src.rpm

Assignee: mageia => qa-bugs

Tested in a VirtualBox Plasma guest. psutils had already been installed before this test, so the man pages in question were already there. Used drakrpm to get a list of the man pages installed with psutils, to check all of them.

Used drakrpm to look at the packages included with texlive-collection-basic, and confirmed that two psutils man pages had been included. I installed the rpms and dependencies, with no installation issues.

Used qarepo to download the proposed rpms, then used drakrpm to examine the man pages list in texlive-collection-basic, finding that the psutils man pages were no longer there. 

Went through with the update, then checked /usr/share/man/man1 to be sure that the psutils man pages had not been removed. I found two psutils man pages that were now  gone: psjoin.1.xz and psutils.1.xz.

Those pages, being part of the psutils rpm, should still be there. Simply taking the two packages off the list is OK for new installs, but for existing installs it will break psutils when the old texlive packages are removed.

CC: (none) => andrewsfarm

Sending this and Bug 29414 back until this issue can be solved properly.

Assignee: qa-bugs => mageia
Keywords: feedback => (none)

We stopped supporting Mageia 8 almost 8 months ago 
https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/

That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not.

If this particular bug did not get fixed for Mageia 8, then we do regret that.

If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field.

If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing
Mageia is a community project, meaning that we, the users, make Mageia together.

The more active contributors we have, the more bug reports will get fixed.
Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D

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