How to tell which version of a application is running

[Xen]

Ralf Mardorf schreef op 18-04-2017 15:36:

> https://help.ubuntu.com/community/PinningHowto#Examples , to avoid that
> an upgrade damages your install.

So I checked that pinning page (thank you),

which suggests adding "APT::Default-Release "xenial";"

to something like /etc/apt/apt.conf.d/01ubuntu  (on debian it is 
/etc/apt/apt.conf.d/70debconf)

to avoid having to comment out the Yakkety line again, and it works very 
well I guess (on Debian it does).

So I would suggest that to you as well Chris.

Then you can install versions from Yakkety directly using:

apt-get install -t yakkety <package name>



But not all is so easy. As an alternative to "pinning" (which is what 
the above is) (in a certain sense that's all you need) it suggests 
building a source package from a different distribution in this way:

apt-get -b source -t yakkety <package name>

However when I try it on Debian (8, Jessie) for "lvm2" from "-t stretch" 
I run into all sorts of issues.

Even without pinning anything, it says:

"Selected version '2.02.168-2' (stretch) for lvm2
The following packages have unmet dependencies:
  dh-systemd : Depends: debhelper (>= 9.20160709) but it is not going to 
be installed
E: Build-dependencies for lvm2 could not be satisfied."

And then apt-cache policy debhelper says:

"debhelper:
   Installed: 9.20150101+deb8u2
   Candidate: 10.2.5
   Version table:
      10.2.5 0
         500 http://mirror.transip.net/debian/debian/ stretch/main amd64 
Packages
      10.2.5~bpo8+1 0
         100 http://mirror.transip.net/debian/debian/ 
jessie-backports/main amd64 Packages
  *** 9.20150101+deb8u2 0
         500 http://mirror.transip.net/debian/debian/ jessie/main amd64 
Packages
         500 http://security.debian.org/ jessie/updates/main amd64 
Packages
         100 /var/lib/dpkg/status"

It won't even install something from jessie-backports.

Then if I do "apt-get build-dep -t stretch lvm2"

It will try to remove half my system including systemd, so that is not a 
very smart thing to do :p.

So getting upgraded build-dependencies for lvm2 is just pretty much 
impossible.

However installing lvm2 from stretch will just update libc6 and a bunch 
of other things but not much.

So once more (this was just a test) installing a version from a 
higher-up distribution release seems much more doable than compiling 
stuff yourself.

> This kind of backport doesn't work always.

It works for lvm2 on Xenial to Yakkety though.

It will probably work for lvm2 from Jessie to Stretch.

So in this case the wiki gives a "better advice" that is just 
unworkable...


In any case, advice to Chris (and myself): add

APT::Default-Release "xenial";

to a file like /etc/apt/apt.conf.d/01ubuntu

so you won't need to comment-out the Yakkety line anymore.

That way you'll have a more persistent configuration.