Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1836642 - Epic not working
Summary: Epic not working
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: epic
Version: 32
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Vitezslav Crhonek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-17 15:14 UTC by Jan ONDREJ
Modified: 2020-05-29 04:09 UTC (History)
1 user (show)

Fixed In Version: epic-2.10.8-2.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-29 04:09:00 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jan ONDREJ 2020-05-17 15:14:36 UTC 
Description of problem:
Epic is not working on Fedora 32.
First character from all messages is stripped.
Also my nick is stripped on screen, not on server.
Unable to send messages to channel, not sure why.

Version-Release number of selected component (if applicable):
epic-2.10.8-1.fc32.x86_64

How reproducible:
always

Steps to Reproduce:
1. connect to any server
2. try to communicate

Actual results:
Also getaddrinfo(<UNKNOWN>): No address associated with hostname
Ack.  The server says your userhost is [<UNKNOWN>] and I can't figure out the
  IPv4 address of that host! You won't be able to use /SET
  DCC_USE_GATEWAY_ADDR ON with this server connection!this is displayed:
Adding DCC_USE_GATEWAY_ADDR doesn't help.

Additional info:
Trying to recompile epic5 on Fedora. This works, but should be compiled with -fPIC and -fcommon on gcc10. At least -fPIC is required, not sure if -fcommon too.

Is there any chance to use epic5 in Fedora 32?
Comment 1 Vitezslav Crhonek 2020-05-19 08:23:59 UTC 
Reproduced, thank you for the bug report.

Add epic5 - I don't think so - the package has been retired on 2015-07-30, because no
one volunteered to maintain it. Initial package review is available here:
https://bugzilla.redhat.com/show_bug.cgi?id=950824
Comment 2 Jan ONDREJ 2020-05-19 08:28:46 UTC 
Thanks. Do we really need a different package for epic5?

Currently I am using epic5 compiled from source and works well with all my scripts.
Didn't seen any changes.
But if you can fix problems on epic4, then I will revert to it again.
Comment 3 Fedora Update System 2020-05-20 12:12:51 UTC 
FEDORA-2020-d07633c43a has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-d07633c43a
Comment 4 Vitezslav Crhonek 2020-05-20 12:21:00 UTC 
It should work fine now, please try the update. It seems that changes made by upstream in 2.10.8
release broke the package. I reverted them by patch to avoid another increase of epoch.

If you think that Fedora users would benefit from epic5 availability, you can create COPR
repository with it - https://copr.fedorainfracloud.org/
Comment 5 Jan ONDREJ 2020-05-20 12:30:52 UTC 
Thanks for quick fix. Works well.
I am not interested to maintain or use epic5, if Fedora's package will work well.
Comment 6 Fedora Update System 2020-05-21 05:23:29 UTC 
FEDORA-2020-d07633c43a has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-d07633c43a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-d07633c43a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2020-05-29 04:09:00 UTC 
FEDORA-2020-d07633c43a has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.