Description of problem:
  semanage import is able to import port rules fine as long as port isn't already defined.
  But if try run again (with port -D to delete all first) get error stating port is already defined.


Version-Release number of selected component (if applicable):
  # rpm -qf $(which semanage)
  policycoreutils-python-utils-2.9-16.el8.noarch


How reproducible:
  100%


Steps to Reproduce:
  1. Add custom port definition with semanage
  2. semanage export to file
  3. semanage import file from #2


Actual results:
  # semanage port -D
  # semanage port -a -t http_cache_port_t -r s0 -p tcp 3024

  # semanage export | grep -w port
  port -D
  port -a -t http_cache_port_t -r 's0' -p tcp 3024

  # echo -e "port -D\nport -a -t http_cache_port_t -r 's0' -p tcp 3024"  | semanage import
  ValueError: Port tcp/3024 already defined
  # echo $?
  1


Expected results:

  As the import has delete, it should not get "already defined" error.
  So expected result is should not have to manully delete them before doing import.

  # semanage port -D
  # echo -e "port -D\nport -a -t http_cache_port_t -r 's0' -p tcp 3024"  | semanage import
  # echo $?
  0


Additional info:
  Issue is present in fedora too (works first time, fails once defined)

  # rpm -qf $(which semanage)
  policycoreutils-python-utils-3.3-1.fc35.noarch
  # semanage port -D
  # echo -e "port -D\nport -a -t http_cache_port_t -r 's0' -p tcp 3024"  | semanage import
  # echo -e "port -D\nport -a -t http_cache_port_t -r 's0' -p tcp 3024"  | semanage import
  ValueError: Port tcp/3024 already defined



  Am able to run the delete and create that fails on import successfully on command line
  # semanage port -D ; semanage port -a -t http_cache_port_t -r s0 -p tcp 3024
  # echo $?
  0