I am owner of easymock3 and I don't have any objections, please block it. Thanks.

retired and blocked in f20+

Please follow https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life next time and retire it in packagedb.

First of all, I didn't ask to retire the package, only block it in Koji.
Secondly, easymock should not be blocked, easymock3 should. Please unretire and unblock easymock and block easymock3.

Replying to [comment:3 mizdebsk]:

First of all, I didn't ask to retire the package, only block it in Koji.
Secondly, easymock should not be blocked, easymock3 should. Please unretire and unblock easymock and block easymock3.

Sorry, this has been fixed. However it does not make sense to block the package but not retire it in packagedb, especially because you also addded a dead.package file to GIT. Can you tell me a valid reason for this?

Replying to [comment:4 till]:

Replying to [comment:3 mizdebsk]:

First of all, I didn't ask to retire the package, only block it in Koji.
Secondly, easymock should not be blocked, easymock3 should. Please unretire and unblock easymock and block easymock3.

Firstly I am neither the owner of the package nor admin so I cannot retire it myself. I communicated with package owner to retire it.

Blocking is important from technical point of view -- it allows us to test if the new package set works correctly or not, either sirectly in koji by running scratch builds or by testing next rawhide compose. Retirement is not important from technical POV and can be delayed.

Besides that delay may be advantageous because if it turns out that this package is required after all it can be simply brought back to life by unblocking in Koji and reverting git commit -- without new package review. Retired packages need review before unretirement (if they are retired long enough, that is).

Keeping packages in an inconsistent state creates unneccessary work, because maintainers tend to forget to properly retire packages. See the different messages on fedora-devel about several kind of inconsistent packages. To test whether the package works, you should not need the package to be blocked, because if you use proper Obsoletes/Provides, the package should never be installed or pulled into buildroots. Actually, blocking the package makes it harder to test, because you will not notice bad obsoletes/provides.