Comments

560 Comments
karma

Tested jgit to confirm it launches properly and that it's usage in the git test suite is successful (this includes jgit daemon, jgit gc, and jgit --version calls). Thanks @mbooth!

BZ#1709624 jgit fails to launch due to missing org.springframework.boot.loader.JarLauncher class

Fixes FTI issue of gradle on 32bit systems.

Well, now I have ;-)

No worries, that's why I'm monitoring them :)

Did you see: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/GJDOBY5B3D26IGGE5J24GNVCHZPP4ZLL/ ? (just to confirm)

@pingou -- Thanks for the info. This is the first time I've encountered such an automatically created update.

@mbooth The rawhide updates are directly created in a "Testing" state, so there is no need to submit them for testing :)

If they pass their tests, they will directly go to "Stable" (which happened here) and if they do not pass their tests, you can either fix the code, the tests or waive the test results to unblock the update. Basically, there is no need to do anything in bodhi w/ rawhide :) (you can just use it for its UI and its information :))

Works great again! Thank you!

BZ#1699035 error enabling pomodoro gnome shell extension via gnome-tweaks or firefox
BZ#1699809 Version 0.15.1 is avaiable
karma

Works

@mscheiff Then please file a bug against 'fedora-comps' which is where dnf groups are defined: https://pagure.io/fedora-comps/

I think the problem is caused by the fact that eclipse-recommenders is still a required package in the package group "Fedora Eclipse":

sudo dnf groupinfo "Fedora Eclipse"
Last metadata expiration check: 4:30:38 ago on Mon 15 Apr 2019 09:33:15 CEST.

Group: Fedora Eclipse
 Description: Integrated Development Environments based on Eclipse.
 Mandatory Packages:
   eclipse-cdt
   eclipse-jdt
 Default Packages:
   eclipse-abrt
   eclipse-cdt-docker
   eclipse-dltk-mylyn
   eclipse-dltk-sh
   eclipse-egit
   eclipse-egit-github
   eclipse-egit-mylyn
   eclipse-epp-logging
   eclipse-linuxtools-changelog
   eclipse-linuxtools-docker
   eclipse-linuxtools-gcov
   eclipse-linuxtools-gprof
   eclipse-linuxtools-javadocs
   eclipse-linuxtools-libhover
   eclipse-linuxtools-perf
   eclipse-linuxtools-rpm-editor
   eclipse-linuxtools-systemtap
   eclipse-linuxtools-vagrant
   eclipse-linuxtools-valgrind
   eclipse-mpc
   eclipse-mylyn-context-cdt
   eclipse-mylyn-context-java
   eclipse-mylyn-context-pde
   eclipse-mylyn-tasks-bugzilla
   eclipse-mylyn-tasks-trac
   eclipse-mylyn-tasks-web
   eclipse-mylyn-versions-cvs
   eclipse-mylyn-versions-git
   eclipse-mylyn-versions-subclipse
   eclipse-packagekit
   eclipse-pde
   eclipse-pydev
   eclipse-pydev-mylyn
   eclipse-recommenders
   eclipse-subclipse
   eclipse-usage
 Optional Packages:
   eclipse-anyedit
   eclipse-avr
   eclipse-cdt-arduino
   eclipse-cdt-llvm
   eclipse-cdt-parsers
   eclipse-cdt-qt
   eclipse-checkstyle
   eclipse-color-theme
   eclipse-dltk-ruby
   eclipse-dltk-tcl
   eclipse-dtp
   eclipse-eclemma
   eclipse-epic
   eclipse-findbugs
   eclipse-m2e-antlr
   eclipse-m2e-apt
   eclipse-m2e-buildhelper
   eclipse-m2e-core
   eclipse-m2e-cxf
   eclipse-m2e-egit
   eclipse-m2e-maven-dependency-plugin
   eclipse-m2e-mavenarchiver
   eclipse-m2e-mavendev
   eclipse-m2e-modello
   eclipse-m2e-plexus
   eclipse-m2e-sisu
   eclipse-m2e-sourcelookup
   eclipse-m2e-takari
   eclipse-m2e-tycho
   eclipse-m2e-wtp
   eclipse-moreunit
   eclipse-mylyn-builds-hudson
   eclipse-pdt
   eclipse-photran
   eclipse-quickrex
   eclipse-testng
   eclipse-webtools-dali
   eclipse-webtools-javaee
   eclipse-webtools-servertools
   eclipse-webtools-sourceediting

For httpcomponents-client, I created ticket https://bugzilla.redhat.com/show_bug.cgi?id=1699852

needed by the eclipse-recommenders

But eclipse-recommenders is obsoleted by this Eclipse update so I don't think it's related at all.

Yes, please file bugs against the affected components -- it seems like Eclipse is no longer what is preventing you from upgrading.

@mbooth Yes, that's true for the httpcomponents-client. This package is not related to eclipse-recommenders. But the two maven-resolver are only needed by the eclipse-recommenders package (at least for my installation).

sudo repoquery --whatrequires httpcomponents-client-cache --installed
eclipse-epp-logging-0:2.0.7-5.fc29.noarch

sudo repoquery --whatrequires maven-resolver-transport-file --installed
eclipse-recommenders-0:2.5.4-2.fc29.noarch

sudo repoquery --whatrequires maven-resolver-transport-http --installed
eclipse-recommenders-0:2.5.4-2.fc29.noarch

Shall I open 2 tickets nevertheless?

@mscheiff Your command updates more than just Eclipse -- please file a separate bug against the "httpcomponents-client" and "maven-resolver" components.

Here's the output of sudo dnf system-upgrade download --refresh --releasever=30 --setopt='module_platform_id=platform:f30' --enablerepo=updates-testing-modular --enablerepo=updates-testing

in a better readable format

Error: 
 Problem 1: problem with installed package httpcomponents-client-cache-4.5.5-5.fc29.noarch
  - package httpcomponents-client-cache-4.5.6-3.fc30.noarch requires mvn(org.apache.httpcomponents:httpclient) = 4.5.6, but none of the providers can be installed
  - httpcomponents-client-cache-4.5.5-5.fc29.noarch does not belong to a distupgrade repository
  - package httpcomponents-client-4.5.6-3.fc30.noarch is excluded
 Problem 2: problem with installed package maven-resolver-transport-file-1:1.1.1-3.fc29.noarch
  - package maven-resolver-transport-file-1:1.3.1-2.fc30.noarch requires mvn(org.apache.maven.resolver:maven-resolver-spi) = 1.3.1, but none of the providers can be installed
  - maven-resolver-transport-file-1:1.1.1-3.fc29.noarch does not belong to a distupgrade repository
  - package maven-resolver-spi-1:1.3.1-2.fc30.noarch is excluded
 Problem 3: problem with installed package maven-resolver-transport-http-1:1.1.1-3.fc29.noarch
  - package maven-resolver-transport-http-1:1.3.1-2.fc30.noarch requires mvn(org.apache.maven.resolver:maven-resolver-util) = 1.3.1, but none of the providers can be installed
  - maven-resolver-transport-http-1:1.1.1-3.fc29.noarch does not belong to a distupgrade repository
  - package maven-resolver-util-1:1.3.1-2.fc30.noarch is excluded
karma

Did not work for me... I'm now getting:

Error: Problem 1: problem with installed package httpcomponents-client-cache-4.5.5-5.fc29.noarch - package httpcomponents-client-cache-4.5.6-3.fc30.noarch requires mvn(org.apache.httpcomponents:httpclient) = 4.5.6, but none of the providers can be installed - httpcomponents-client-cache-4.5.5-5.fc29.noarch does not belong to a distupgrade repository - package httpcomponents-client-4.5.6-3.fc30.noarch is excluded Problem 2: problem with installed package maven-resolver-transport-file-1:1.1.1-3.fc29.noarch - package maven-resolver-transport-file-1:1.3.1-2.fc30.noarch requires mvn(org.apache.maven.resolver:maven-resolver-spi) = 1.3.1, but none of the providers can be installed - maven-resolver-transport-file-1:1.1.1-3.fc29.noarch does not belong to a distupgrade repository - package maven-resolver-spi-1:1.3.1-2.fc30.noarch is excluded Problem 3: problem with installed package maven-resolver-transport-http-1:1.1.1-3.fc29.noarch - package maven-resolver-transport-http-1:1.3.1-2.fc30.noarch requires mvn(org.apache.maven.resolver:maven-resolver-util) = 1.3.1, but none of the providers can be installed - maven-resolver-transport-http-1:1.1.1-3.fc29.noarch does not belong to a distupgrade repository - package maven-resolver-util-1:1.3.1-2.fc30.noarch is excluded

karma

Works for me. No regressions noted compared to previous version.