How to setup debian/control to force updating a library?

**YannBuntu** · December 17th, 2012

This question is aimed at PPA/packages maintainers.

I have a PPA with 2 packages:

mypackage (currently version 1~ppa1~quantal)
mypackagelib (currently version 1~ppa1~quantal)

Currently, the control file of mypackage has:

Code:

Depends: mypackagelib

I want to update the 2 packages to version '2' (mypackage version 2 and mypackagelib version 2).

How can I make sure that 'mypackagelib' will also be updated when the user updates 'mypackage' ?

FYI, changing the 'Depends' field to:

Code:

Depends: mypackagelib (>= 2)

does NOT work, and returns the following error:

Code:

mypackage : Depends: mypackagelib (>= 2) but mypackagelib-2~ppa1~quantal is to be installed

Please see http://askubuntu.com/questions/22972...ting-a-library

**mc4man** · December 17th, 2012

in the control file using
Package: boot-repair
Architecture: all
Depends: boot-sav (>= ${binary:Version}),
${misc

epends}
....ect
seems to work fine (or Depends: boot-sav (= ${binary:Version}),

Also don't know why not upping the version in /debian/changelog like
3.198 or whatever

**YannBuntu** · December 17th, 2012

Thanks Mcman for having looked at this.

The problem is the '~' of the ppa version.
See http://askubuntu.com/questions/22972...ting-a-library

Depends: boot-sav (>= ${binary:Version}) is a good workaround.

[SOLVED]

**Bachstelze** · December 17th, 2012

Just to clarify: the problem basically is that when comparing package verison numbers, X~Y is considered LOWER than X. This is why you get

Code:

mypackage : Depends: mypackagelib (>= 2) but mypackagelib-2~ppa1~quantal is to be installed

because you want >= 2, but what you have is 2~something, which is < 2.

**mc4man** · December 17th, 2012

Well good it's back - when i decide to set up my new laptop (lenovo 580y, win7, some interesting partitioning, hdd + a cache ssd) I figure I'll likely end up needing your app