https://bugzilla.redhat.com/show_bug.cgi?id=1517477
Jack <damnedyankee(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |damnedyankee(a)gmail.com
--- Comment #17 from Jack <damnedyankee(a)gmail.com> ---
(In reply to Kyle Marek from comment #16)
> Still applies in Fedora 29.
Indeed. I just attempted to run Jenkins on a fresh F29 install and got the
same:
[j~]$ wget minibox:8080
--2019-02-07 10:09:23-- http://minibox:8080/
Resolving minibox (minibox)... 192.168.1.243, fe80::bdf6:8a4c:b40c:e5fc
Connecting to minibox (minibox)|192.168.1.243|:8080... connected.
HTTP request sent, awaiting response... 500 Server Error
2019-02-07 10:09:23 ERROR 500: Server Error.
[j~]$
So, I did "dnf remove jenkins", then the following:
99 sudo wget -O /etc/yum.repos.d/jenkins.repo
http://pkg.jenkins-ci.org/redhat-stable/jenkins.repo
100 sudo rpm --import https://jenkins-ci.org/redhat/jenkins-ci.org.key
101 sudo dnf -y install java #java is a dependency...you may or may not need
this.
102 sudo dnf -y install jenkins
103 sudo systemctl enable jenkins
104 sudo systemctl start jenkins
105 sudo cat /var/lib/jenkins/secrets/initialAdminPassword
Hope this helps.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1668215
Bug ID: 1668215
Summary: javamail update causes broken dependencies in Fedora
29
Product: Fedora
Version: 29
Status: NEW
Component: javamail
Assignee: mizdebsk(a)redhat.com
Reporter: mattias.ellert(a)physics.uu.se
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
jkang(a)redhat.com, mefoster(a)gmail.com,
mizdebsk(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The javamail update in Fedora 29 is uninstallable due to broken dependencies:
$ LANG=en_US.UTF-8 dnf --refresh update
Adobe Systems Incorporated 2.7 kB/s | 2.9 kB 00:01
EGI-trustanchors 2.1 kB/s | 2.5 kB 00:01
Fedora Modular 29 - x86_64 46 kB/s | 28 kB 00:00
Fedora Modular 29 - x86_64 - Updates 39 kB/s | 26 kB 00:00
Fedora 29 - x86_64 - Updates 30 kB/s | 28 kB 00:00
Fedora 29 - x86_64 112 kB/s | 28 kB 00:00
RPM Fusion for Fedora 29 - Free - Updates 7.9 kB/s | 9.1 kB 00:01
RPM Fusion for Fedora 29 - Free 18 kB/s | 10 kB 00:00
skype (stable) 2.7 kB/s | 2.9 kB 00:01
Dependencies resolved.
Problem: cannot install both javamail-1.6.3-2.module_2663+c0acbe74.noarch and
javamail-1.5.2-8.fc29.noarch
- package axiom-1.2.14-3.fc29.noarch requires mvn(javax.mail:mail), but none
of the providers can be installed
- cannot install the best update candidate for package
javamail-1.5.2-8.fc29.noarch
- cannot install the best update candidate for package
axiom-1.2.14-3.fc29.noarch
- package javamail-1.5.2-7.module_2512+68251d4e.noarch is excluded
- package javamail-1.5.2-8.fc29.noarch is excluded
================================================================================
Package Arch Version Repository Size
================================================================================
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
javamail noarch 1.6.3-2.module_2663+c0acbe74 updates-modular 683 k
Transaction Summary
================================================================================
Skip 1 Package
Nothing to do.
Complete!
Version-Release number of selected component (if applicable):
javamail-1.6.3-2.module_2663+c0acbe74.noarch
How reproducible:
Always
Steps to Reproduce:
1. Try to update javamail in Fedora 29 while having a package requiring
mvn(javax.mail:mail) is installed
2. The update fails because the new javamail version no longer provides
mvn(javax.mail:mail)
Actual results:
Update fails
Expected results:
Update successful
Additional info:
Several packages in Fedora 29 requires mvn(javax.mail:mail):
$ LANG=en_US.UTF-8 dnf repoquery --whatrequires 'mvn(javax.mail:mail)'
Last metadata expiration check: 0:04:22 ago on Tue 22 Jan 2019 09:21:40 AM CET.
axiom-0:1.2.14-3.fc29.noarch
axis2-0:1.7.7-2.fc29.noarch
jenkins-core-0:1.651.3-8.fc29.noarch
jets3t-0:0.9.3-9.fc29.noarch
restlet-jse-0:2.3.1-8.fc29.noarch
subethasmtp-0:3.1.7-13.fc29.noarch
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1346528
Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|jenkins-remoting-3.24 is |jenkins-remoting-3.29 is
|available |available
--- Comment #27 from Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> ---
Latest upstream release: 3.29
Current version/release in rawhide: 2.62.3-1.fc26
URL: https://github.com/jenkinsci/remoting
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/1444/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1516064
Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|gradle-5.2.0-RC1 is |gradle-5.2.0 is available
|available |
--- Comment #23 from Upstream Release Monitoring <upstream-release-monitoring(a)fedoraproject.org> ---
Latest upstream release: 5.2.0
Current version/release in rawhide: 4.4.1-1.fc30
URL: http://www.gradle.org/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/6088/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1604442
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ON_QA |CLOSED
Fixed In Version| |jibx-1.2.6-13.fc29
Resolution|--- |ERRATA
Last Closed| |2019-02-01 01:58:51
--- Comment #7 from Fedora Update System <updates(a)fedoraproject.org> ---
jibx-1.2.6-13.fc29 has been pushed to the Fedora 29 stable repository. If
problems still persist, please make note of it in this bug report.
--
You are receiving this mail because:
You are on the CC list for the bug.