Bug 485396 - /usr/sbin/semanage: Port tcp/5347 already defined
Summary: /usr/sbin/semanage: Port tcp/5347 already defined
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 0.4
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jan Pazdziora
QA Contact: Miroslav Suchý
URL:
Whiteboard:
Depends On:
Blocks: space05
TreeView+ depends on / blocked
 
Reported: 2009-02-13 10:29 UTC by Miroslav Suchý
Modified: 2009-09-17 07:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-17 07:10:21 UTC
Embargoed:


Attachments (Terms of Use)

Description Miroslav Suchý 2009-02-13 10:29:36 UTC
Description of problem:
When I upgrade package jabberd-selinux I got following message:
  Updating       : scdb                                            [25/61]
  Updating       : jabberd-selinux                                 [26/61]
/usr/sbin/semanage: Port tcp/5347 already defined
  Updating       : eventReceivers                                  [27/61]


Version-Release number of selected component (if applicable):
Spacewalk 0.4

How reproducible:
done once

Steps to Reproduce:
1. Install jabberd-selinux
2. Upgrade to newer version
  
Actual results:
/usr/sbin/semanage: Port tcp/5347 already defined

Expected results:
no message

Additional info:

Comment 1 Jan Pazdziora 2009-02-25 12:24:17 UTC
Fix in Spacewalk repo, 0a2b2d6dc3c9651343ba1a5e26707cb3da12e279, tagged as jabberd-selinux-1.4.0-5.

Comment 2 Jan Pazdziora 2009-03-12 15:56:35 UTC
Reverted in 0e6cc5cf44892bd0897932303c61f009e3b25fa4 and done again in 4ac8e4589ccef0d1b54236d7096f030fca4b5244.

Comment 3 Jan Pazdziora 2009-04-01 06:36:23 UTC
With Spacewalk 0.5 released, moving ON_QA.

Comment 4 Jesus M. Rodriguez 2009-04-14 14:13:04 UTC
Spacewalk 0.5 released.

Comment 5 Miroslav Suchý 2009-09-17 07:10:21 UTC
Spacewalk 0.5 has been released for long time ago.


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