Bug 1439284 - Jenkins is build with dom4j 1.6.1-27 but 2.0.0-1 is installed
Summary: Jenkins is build with dom4j 1.6.1-27 but 2.0.0-1 is installed
Alias: None
Product: Fedora
Classification: Fedora
Component: jenkins
Version: 27
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Michal Srb
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2017-04-05 15:21 UTC by David Hill
Modified: 2018-11-30 20:03 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-11-30 20:03:28 UTC
Type: Bug

Attachments (Terms of Use)

Description David Hill 2017-04-05 15:21:38 UTC
Description of problem:
Jenkins is build with dom4j 1.6.1-27 but 2.0.0-1 is installed

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

How reproducible:

Steps to Reproduce:
1. Update to latest dom4j

Actual results:
Breaks jenkins

Expected results:
Doesn't break jenkins.

Additional info:

Comment 1 Jan Kurik 2017-08-15 07:41:05 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 2 Gwyn Ciesla 2017-12-27 16:17:53 UTC
A simple rebuild doesn't seem to do the trick, and updating to 1.658 introduces build issues.

Comment 3 David Hill 2017-12-27 16:33:52 UTC
I still get this issue with FC28 / rawhide.

Comment 4 David Hill 2017-12-27 16:53:51 UTC
Well, it looks like I forgot to exclude dom4j from my last update and now it looks like jenkins is working properly ...  Is it fixed ?


Comment 5 Gwyn Ciesla 2017-12-27 17:01:34 UTC
I locally built that dom4j for f27, upgraded, restarted jenkins, no effect. Same jenkins.

Comment 6 David Hill 2017-12-28 20:56:32 UTC
You can forget comment #4 as I was looking at the wrong place... this is still an issue.

Comment 7 Christian Buchegger 2017-12-30 22:21:59 UTC
This is possibly caused by: https://bugzilla.redhat.com/show_bug.cgi?id=1529892

Comment 8 Ben Cotton 2018-11-27 16:54:13 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Ben Cotton 2018-11-30 20:03:28 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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