Bug 1659667 - aeskulap became broken with Centos 7.6
Summary: aeskulap became broken with Centos 7.6
Alias: None
Product: Fedora
Classification: Fedora
Component: dcmtk
Version: 29
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Igor Gnatenko
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-12-15 00:08 UTC by Greg Ennis
Modified: 2018-12-19 11:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-12-19 11:08:36 UTC
Type: Bug

Attachments (Terms of Use)

Description Greg Ennis 2018-12-15 00:08:12 UTC
Sorry I put this in the dcmtk category because aeskalup was missing in the listing. 

Aeskulap became unavailable after the upgrade from Centos 7.5 to 7.6.

I had difficulty with the use of it with error messages returned when trying to access dicom images from a pac server.

I discovered it was no longer in the epel repositories when I did a yum remove of the package with the intent to do a yum install of the package. Upon performing the latter command aeskulap was not searchable, and I could not reinstall it.

I could not find it in the 'retired' list of epel.

Could you identify if you are going start including this.  I have an urgent problem in being able to use. it.

Thank you for your work!!!!!

Greg Ennis

Comment 1 Greg Ennis 2018-12-15 21:54:39 UTC
Looks like dcmtk is also involved :


I have several desktops using aeskulap and dcmtk which makes me hope that this problem can be remedied soon.  If there is anything I can to to asssit I am motivated to do so.

Greg Ennis

Comment 2 Greg Ennis 2018-12-18 20:45:15 UTC
After continuing to do some research on this I was mistaken about aeskulap being from EPEL, it had come from nux-dextop.  Please accept my apologies.

However, the upgrade from Centos 7.5 to 7.6 did break aeskulap.  I will contact the maintainers of nux-dextop.

Thank you,

Greg Ennis

Comment 3 Igor Raits 2018-12-19 11:08:36 UTC
What is expected from Fedora?

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