Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update on Debian doesn't update libqtkeychain0 #1605

Closed
ghost opened this issue Mar 23, 2014 · 12 comments
Closed

Update on Debian doesn't update libqtkeychain0 #1605

ghost opened this issue Mar 23, 2014 · 12 comments
Assignees

Comments

@ghost
Copy link

ghost commented Mar 23, 2014

Hi,

after pushing the libqtkeychain0 from version 0.20140128 to 0.3 the libqtkeychain0 package is not updated to 0.3. It seems Debian/Ubuntu sees version 0.20140128 as a higher version and a manual "downgrade" to 0.3 is needed.

@dragotin
Copy link
Contributor

@DeepDiver1975, @hefee : do you have an idea how to get out here?

@hefee
Copy link
Contributor

hefee commented Mar 24, 2014

Mmmh well, the problem is that in the debian version world is 0.20140128-1 > 0.3-0. So apt wants to install 0..20140128-1 instead of 0.3-0.
You can fix this, it you set libqtkeychain0 (<< 0.20140128) to owncloud-client to make sure, that owncloud-client don't want this version.

@guruz
Copy link
Contributor

guruz commented Jun 5, 2014

Is this something @jnweiger wanted to look at?

@guruz guruz added the Bug label Jun 5, 2014
@jnweiger jnweiger changed the title [packaging] Update on Debian doesn't update libqtkeychain0 Update on Debian doesn't update libqtkeychain0 Sep 4, 2014
@jnweiger
Copy link
Contributor

jnweiger commented Sep 4, 2014

Maybe it helps, if we add this to owncloud-client?
Requires: libqtkeychain0 = 0.3 | libqtkeychain0 >= 0.20140128

Deb packaging has the '|' as a logical -- I'd assume it can be exploited for this.

@jnweiger
Copy link
Contributor

we have libqtkeychain0 = 0.4 meanwhile, the above suggestion does not work.
Debian does not allow a logical AND that is needed here. Negations and groups are also not supported.
Wontfix. sorry.

@ghost
Copy link
Author

ghost commented Jan 27, 2015

@jnweiger

What about just adding a conflict to libqtkeychain0 0.20140128?

I think that was never an "official" version number and only provided by the OBS repository:

https://packages.debian.org/search?keywords=libqtkeychain0

@jnweiger
Copy link
Contributor

Good idea. Not sure if that helps the solver to look again for another version -- but better than nothing.

@jnweiger
Copy link
Contributor

I see libqtkeychain0 0.20140128 only in private playgrounds on obs. The case is moot.
Adding Conflicts as suggested and closing.

@ghost
Copy link
Author

ghost commented Jan 27, 2015

Hi,

yes, the 0.20140128 was only available in the public OBS repositories one year ago. There are probably not many systems out there which are still having this installed so the conflicts is probably more than enough.

@ArcTanH
Copy link

ArcTanH commented Feb 5, 2015

I can't remember where I got v 0.20140128 from, but I had this installed on Linux Mint (based on Ubuntu 14.04LTS).

Marking this package as conflict leads to the confusing situation where apt tells me

Die folgenden Pakete haben unerfüllte Abhängigkeiten:
 owncloud-client : Kollidiert mit: libqtkeychain0 (= 0.20140128) aber 0.20140128 soll installiert werden

which translates as

The following packages have unmet dependencies:
 owncloud-client : Collides with libqtkeychain0 (= 0.20140128) but 0.20140128 is requested ''to be installed''

Manual install of libqtkeychain0=0.4 solved this, though.

@ghost
Copy link
Author

ghost commented Feb 5, 2015

Hi,

Manual install of libqtkeychain0=0.4 solved this, though.

unfortunately thats the only possible solution to fix such broken installations. 0.20140128 is still seen newer as the (really newer) 0.4.

@jnweiger
Copy link
Contributor

jnweiger commented Feb 5, 2015

Maybe this help to make the solver prefer 0.4 over 0.20140128 ?

Replaces: libqtkeychain0 (= 0.20140128)
Breaks:   libqtkeychain0 (= 0.20140128)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants