#11979 Some questions about man-pages-ko in koji
Closed: Fixed by jnsamyak. Opened by pwu.

The man-pages-ko package is retired, and the man-pages-l10n package
provides the sub package now.
And the man-pages-ko source package disappears in the repo.

Just run the following command, it seems the man-pages-ko source package is not blocked in koji.

$ koji list-pkgs --show-blocked  --package man-pages-ko
...
man-pages-ko            f39                                      pwu            
man-pages-ko            f38-Beta                                 pwu            
man-pages-ko            f40                                      pwu            
man-pages-ko            f39-Beta                                 pwu            
man-pages-ko            f41                                      pwu            

Is the current status of man-pages-ko okay?


i think this is somewhat similar to issue #11980 where the packages were retired from dist-git but did not get blocked on koji and PDC properly!

Metadata Update from @jnsamyak:
- Issue tagged with: low-gain, low-trouble, ops

@pwu, so just to confirm it should be retired properly for f40 and rawhide right?

Yes, I think the man-pages-ko package should be retired for f40 and rawhide.

Actually this package is retired by @ljavorsk .

Yes, I've retired this package using fedpkg retire is there something else I should have done?

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

Hello folks,

No this was an issue where several packages weren't retired, so i manually adjusted this
This should be now blocked from Koji and PDC EOL is also adjusted!

man-pages-ko            f40                                      pwu             [BLOCKED]
man-pages-ko            f39-Beta                                 pwu            
man-pages-ko            f41                                      pwu             [BLOCKED]
man-pages-ko            f40-Beta                                 pwu         

if there are any other issues please let me know!

Thanks for fixing this issue!

Metadata Update from @jnsamyak:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata