Bug 2155877 - File conflict with man-pages-ko
Summary: File conflict with man-pages-ko
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: man-pages-ko
Version: rawhide
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Peng Wu
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F38FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2022-12-22 17:44 UTC by Adam Williamson
Modified: 2022-12-30 06:20 UTC (History)
7 users (show)

Fixed In Version: man-pages-ko-20050219-43.fc38
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-30 06:20:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2022-12-22 17:44:30 UTC
The new build of psmisc - 23.6-1.fc38 - has a file conflict with man-pages-ko; both carry /usr/share/man/ko/man1/killall.1.gz , and the two are not identical. Either they should be identical, or the file should only be in one package or the other. Can you please work this out with Peng Wu, the man-pages-ko maintainer? Thanks.

This is an automatic Final blocker per criterion "There must be no errors in any package on the release-blocking images which cause the package to fail to install" and https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Automatic_blockers "File conflicts between two packages on a release-blocking DVD-style (offline installer) image without an explicit Conflicts: tag (failures of QA:Testcase_Mediakit_FileConflicts)".

Comment 1 Peng Wu 2022-12-30 03:20:54 UTC
I think I can remove the man page killall.1.gz from the man-pages-ko package.

Comment 2 Fedora Update System 2022-12-30 06:19:25 UTC
FEDORA-2022-1e8b101a75 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1e8b101a75

Comment 3 Fedora Update System 2022-12-30 06:20:44 UTC
FEDORA-2022-1e8b101a75 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


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