FEDORA-2018-692ec0f693 created by catanzaro 2 years ago for Fedora 29
obsolete

Update to 2.58.0

This update has been submitted for testing by catanzaro.

2 years ago

This update has been pushed to testing.

2 years ago
User Icon adamwill commented & provided feedback 2 years ago
karma

Evo seems OK with this glib-networking plus gnutls 3.6.3.

BZ#1623471 Spurious connection errors: "Server did not return a valid TLS certificate"
User Icon kparal commented & provided feedback 2 years ago

Unfortunately, it seems that i686 build is missing from updates-testing:

 Problem: glib-networking-2.57.90-1.fc29.i686 has inferior architecture
  - cannot install both glib-networking-2.58.0-1.fc29.x86_64 and glib-networking-2.57.90-1.fc29.x86_64
  - cannot install both glib-networking-2.57.90-1.fc29.x86_64 and glib-networking-2.58.0-1.fc29.x86_64
  - cannot install the best update candidate for package glib-networking-2.57.90-1.fc29.i686
  - cannot install the best update candidate for package glib-networking-2.57.90-1.fc29.x86_64

Have a look: https://dl.fedoraproject.org/pub/fedora/linux/updates/testing/29/Everything/x86_64/Packages/g/

I think we've hit https://pagure.io/releng/issue/7071 again.

This can't be installed if you have glib-networking.i686 already, or you need to remove it (e.g. using --allowerasing), which in turn removes e.g. steam (in my case).

User Icon kparal provided feedback 2 years ago
karma

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

2 years ago
User Icon adamwill commented & provided feedback 2 years ago
User Icon kalev commented & provided feedback 2 years ago

I don't think this should warrant a -1 karma: we actually need the karma so that it can get pushed to stable and get properly multilibbed (multilib is working in stable repos, but apparently somewhat broken in testing).

User Icon kparal commented & provided feedback 2 years ago
karma

Good point. If the multilib issue will be fixed once pushed to stable, I'm happy giving it +1 karma. Just please make sure the autopush is disabled, before we're clear this is really the way to go.

User Icon kalev commented & provided feedback 2 years ago

If I understand this right, the issue here is that pungi doesn't "see" the package that is supposed to pull in glib-networking because it comes from a different repo (the stable repo), so it thinks glib-networking is a leaf package and doesn't make it multilib.

The way it's suppsosed to work is that all -devel packages are multilibbed by pungi, so libsoup-devel is multilib, which pulls in libsoup, which in turn pulls in glib-netowkring, making it too multilib. However, libsoup-devel and libsoup aren't in the testing repo so it all falls apart. They are of course in the base repo and it all should work correctly once pushed to stable.

User Icon renault commented & provided feedback 2 years ago
karma

No regressions found

This update has been submitted for batched by adamwill.

2 years ago

This update has been submitted for stable by adamwill.

2 years ago

This update has been obsoleted by glib-networking-2.58.0-2.fc29.

2 years ago
User Icon danieljamesscott commented & provided feedback 2 years ago

I'm getting a similar problem now with 2.60.2-1.fc30

 Problem: glib-networking-2.60.1-2.fc30.i686 has inferior architecture
  - cannot install both glib-networking-2.60.2-1.fc30.x86_64 and glib-networking-2.60.1-2.fc30.x86_64
  - cannot install both glib-networking-2.60.1-2.fc30.x86_64 and glib-networking-2.60.2-1.fc30.x86_64
  - cannot install the best update candidate for package glib-networking-2.60.1-2.fc30.i686
  - cannot install the best update candidate for package glib-networking-2.60.1-2.fc30.x86_64
User Icon anonymous commented & provided feedback 2 years ago

For me this seems to be a problem in Fedora 30 with the latest glib-networking-2.60.2-1 not allowing concurrent installations of the i686 and x86_64 versions. The application that is needing these libs is steam (like Comment . There doesn't seem to be a x86_64 version available but this might be a time to switch to the flatpak version that is available to free up this library conflict if this is an intentional new restriction.

User Icon catanzaro commented & provided feedback 2 years ago

This is an F29 update from eight months ago that was never even pushed to stable. It's not the cause of your problems.

User Icon danieljamesscott commented & provided feedback 2 years ago

So I should open a new bug against this package?

User Icon catanzaro commented & provided feedback 2 years ago

Yes.


Please login to add feedback.

Metadata
Type
bugfix
Karma
3
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
2 years ago
in testing
2 years ago
BZ#1623471 Spurious connection errors: "Server did not return a valid TLS certificate"
0
0

Automated Test Results