Updater error libqoauth1.x86_64 conflict.

English Applications
#1

I keep getting this error.

PackageKit Error dep-resolution-failed: patch:choqok-3320.noarch conflicts with libqoauth1.x86_64

When I go to the YAST software manager and search for libqoauth1.x86_64 it doesn’t hit on anything. What gives here?

#2

the package is called just “libqoauth1”. i’ve had the same thing just the other day. all you should do is reinstall this package from the update repo.

this - as root - should do the job, but of course you can also use the software manager:

# zypper in --force --from repo-update libqoauth1
#3

I have reinstalled libqoauth1 but still get the error. I can’t even find this choqok-3320.noarch file in my updates repository on that computer.

Whom ever is in charge of seeing this stuff will update seems to have screwed up if they can’t even get the name of that libqoauth1 file right. I am tired of seeing this file in the updater applet and not being able to resolve it.

This is how people start ignoring updates. Things that will not properly install and hassles caused in getting them to work right lead them to ignore important security updates. All they see is that one error and a notifier that always says they have updates and that file that will not install so they just ignore the notifier.

I don’t have a Twitter account so I don’t care about this file anyway.

#4

could anyone re-check my terminal command?

# zypper in --force --from repo-update libqoauth1

from the update repo? could you provide

zypper info libqoauth1

the thing is, it’s a bug reported to choqok (which resides in the default repo) but the changes where actually made in libqoauth1

This is how people start ignoring updates. Things that will not properly install and hassles caused in getting them to work right lead them to ignore important security updates. All they see is that one error and a notifier that always says they have updates and that file that will not install so they just ignore the notifier.

I don’t have a Twitter account so I don’t care about this file anyway.

how about removing libqoauth1? there arn’t a lot of programs using it so chances are good you actually don’t need it.

#5

Well I know what the problem is now.

Information for package libqoauth1:

Repository: @System
Name: libqoauth1
Version: 1.0.1-0.pm.3.1
Arch: x86_64
Vendor: http://packman.links2linux.de
Installed: Yes
Status: up-to-date
Installed Size: 78.0 KiB
Summary: OAuth Library for Qt Applications
Description: 
QOAuth is a Qt-based C++ implementation of an interface to services using OAuth
authorization scheme.

Something I have installed from packman requires it. Priority for packman is 90 meaning this file will not be over written may a priority 99 update.

Seems I’ll just have to wait for the packman packager to catch up.

#6

Packman has nothing to catch up, it has the latest version of qoauth. You are offered this “update” only because of different versioning schemes between Packman and openSUSE.

Yes, the “patches” concept has its problems… it’s a shame that PackageKit, and so the update applet, only support it. Personally I just removed the applet and manually run “zypper up” once a day.

#7

I would forget to check and I am uncomforable wiht zypper and the CLI in general on my general use computer.

Is there a way to blackhole choqok-3320.noarch so it doesn’t show up as an avialable update?

#8

i wasn’t able to. tried to lock both choqok and libqoauth1 but that did not work. like i said, i managed to disable this message only by installing libqoauth1 from the update-repo

#9

In the end, I just let choqok install which brought in libqoauth1. After the patch installed, I just removed choqok.

#10

Looks like I’ll be ignoring that **** persistent message.

I mean why the heck is something like that installed anyway? Twitter is so superficial. Why does it have it’s hooks in my OS?

#11

Well I don’t want to install it from the update repo and with my priority setting on both of my machines I have packman at 90. That machine gives me that message, this machine never complained about that file. I am just going to put up wiht the complaint and keep ignoring that file.

Twitter is so superficial anyway. Why does it have hooks in my OS to begin with?

Thanks for the replies.