PR#6845: Explaining why we unblock pkgs on epel build tag - releng

releng

#6845 Explaining why we unblock pkgs on epel build tag

Merged 6 years ago by kellin. Opened 6 years ago by mohanboddu.

mohanboddu/releng block-retired-epel-comment into master

Explaining why we unblock pkgs on epel build tag

Mohan Boddu • 6 years ago

a704481

scripts/block_retired.py

file modified

		`@@ -222,6 +222,9 @@`
		`cmd = ["block-pkg", tag] + packages`
		`catch_koji_errors(cmd)`

		`+ #If a package moves from EPEL to RHEL it can only be built if it is unblocked`
		`+ #in the epel build tag. Therefore unblock all retired EPEL packages in the`
		`+ #built tag since it does not hurt if the package does not move to RHEL.`
		`if epel_build_tag:`
		`cmd = ["unblock-pkg", epel_build_tag] + packages`
		`catch_koji_errors(cmd)`

mohanboddu commented 6 years ago

Signed-off-by: Mohan Boddu mboddu@redhat.com

till commented 6 years ago

I would reword the comment like this:

If a package moves from EPEL to RHEL it can only be built if it is unblocked in the epel build tag. Therefore unblock all retired EPEL packages in the built tag since it does not hurt if the package does not move to RHEL.