[X2Go-Dev] Bug#1344: Versioning in the launchpad ppa

[Jens Reyer]

Package: launchpad.net

Hi,

the version of e.g. nx-libs in the X2Go nightly PPA at
https://launchpad.net/~x2go is technically lower than the one in the
official Ubuntu Bionic (18.04) archive:

$ dpkg --compare-versions 2:3.5.99.16-0~201811100633~ubuntu18.04.1 gt
2:3.5.99.16-1 && echo "ppa version is bigger" || echo "ppa version is
smaller"
ppa version is smaller

This would be correct if they had the same "upstream" content, so that
the official package has precedence over the PPA one. However I assume
that the nightly PPA ships newer "upstream" functionality. You may
reflect this by changing the versioning to something like this
(increase the upstream versioning part before the Debian revision -0):

2:3.5.99.16+201811100633-0~ubuntu18.04.1

$ dpkg --compare-versions 2:3.5.99.16+201811100633-0~ubuntu18.04.1 gt
2:3.5.99.16-1 && echo "ppa version is bigger" || echo "ppa version is
smaller"
ppa version is bigger

Otherwise I have to "downgrade" the packages, in order to use the
nightly builds instead of the older official Ubuntu bionic ones. For
this to work I currently use apt pinning:

$ cat /etc/apt/preferences.d/x2go-ppa
Package: *
Pin: release o=LP-PPA-x2go
Pin-Priority: 1010

Thanks
jre

[X2Go Bug Tracking System]

close -1

Bug #1344 [launchpad.net] Versioning in the launchpad ppa
Marked Bug as done

tags -1 not-a-bug

Bug #1344 {Done: Mike Gabriel <***@das-netzwerkteam.de>} [launchpad.net] Versioning in the launchpad ppa
Added tag(s) not-a-bug.

[Ulrich Sibiller]

On Mon, Nov 19, 2018 at 4:05 PM Mike Gabriel

Control: close -1
Control: tags -1 not-a-bug
Hi Jens,

Post by Jens Reyer
$ cat /etc/apt/preferences.d/x2go-ppa
Package: *
Pin: release o=LP-PPA-x2go
Pin-Priority: 1010

This is exactly the way to do it.
Closing this bug as a not-a-bug report.

I don't really get it. What is the sense in adding a ppa to your
system when you need additional steps to get the packages from there!?
This is counter-intuitive! If a user adds the ppa he/she/it states
his/her/its will to use packages from there, so why ignoring that user
wish?

Uli

[Jens Reyer]

Am Mo., 19. Nov. 2018 um 16:20 Uhr schrieb Ulrich Sibiller

Post by Ulrich Sibiller
On Mon, Nov 19, 2018 at 4:05 PM Mike Gabriel

Control: close -1
Control: tags -1 not-a-bug

Post by Jens Reyer
$ cat /etc/apt/preferences.d/x2go-ppa
Package: *
Pin: release o=LP-PPA-x2go
Pin-Priority: 1010

This is exactly the way to do it.
Closing this bug as a not-a-bug report.

I don't really get it. What is the sense in adding a ppa to your
system when you need additional steps to get the packages from there!?
This is counter-intuitive! If a user adds the ppa he/she/it states
his/her/its will to use packages from there, so why ignoring that user
wish?

I basically agree with Uli, except that I'd only prefer newer versions
from the PPA over those from the Ubuntu archive (which should be the
case for nightly).
Or with other words: I assume you update the upstream source in the
orig.tar for the nightlies, then you should also change the upstream
version.

[Mike Gabriel]

Hi,

Post by Jens Reyer
Am Mo., 19. Nov. 2018 um 16:20 Uhr schrieb Ulrich Sibiller

Post by Ulrich Sibiller
On Mon, Nov 19, 2018 at 4:05 PM Mike Gabriel

Control: close -1
Control: tags -1 not-a-bug

Post by Jens Reyer
$ cat /etc/apt/preferences.d/x2go-ppa
Package: *
Pin: release o=LP-PPA-x2go
Pin-Priority: 1010

This is exactly the way to do it.
Closing this bug as a not-a-bug report.

I don't really get it. What is the sense in adding a ppa to your
system when you need additional steps to get the packages from there!?
This is counter-intuitive! If a user adds the ppa he/she/it states
his/her/its will to use packages from there, so why ignoring that user
wish?

I basically agree with Uli, except that I'd only prefer newer versions
from the PPA over those from the Ubuntu archive (which should be the
case for nightly).
Or with other words: I assume you update the upstream source in the
orig.tar for the nightlies, then you should also change the upstream
version.

The orig tarballs are indeed Git snapshots and the code base is newer
than the upstream release number given. In fact, the package version
contains the Git revision hash (shortened) and from that you can
derive what code is actually shipped in the package.

The overall idea is to have an easy upgrade path when you want to
return from nightly builds (test test test) back to a stable release
build.

Mike

[Mike Gabriel]

Hi Uli,

Post by Ulrich Sibiller
On Mon, Nov 19, 2018 at 4:05 PM Mike Gabriel

Control: close -1
Control: tags -1 not-a-bug
Hi Jens,

Post by Jens Reyer
$ cat /etc/apt/preferences.d/x2go-ppa
Package: *
Pin: release o=LP-PPA-x2go
Pin-Priority: 1010

This is exactly the way to do it.
Closing this bug as a not-a-bug report.

I don't really get it. What is the sense in adding a ppa to your
system when you need additional steps to get the packages from there!?
This is counter-intuitive! If a user adds the ppa he/she/it states
his/her/its will to use packages from there, so why ignoring that user
wish?
Uli

It is a versioning topic. As long as we have not released a new
upstream version, the nx-libs nightly packages we built for Arctica /
X2Go are always strictly below the released package versions
officially shipped in the distro.

So, you need to enforce that the nightly builds are preferred over the
distro's nx-libs. This is wanted (by me).

And yes, it is counter intuitive for PPAs. This results from X2Go's
nx-libs 3.6.x branch simply being synced over from Github.

Mike

[Jens Reyer]

Hi Mike,

Am Di., 20. Nov. 2018 um 10:07 Uhr schrieb Mike Gabriel

Post by Mike Gabriel
Hi Uli,

Post by Ulrich Sibiller
On Mon, Nov 19, 2018 at 4:05 PM Mike Gabriel

Control: close -1
Control: tags -1 not-a-bug
Hi Jens,

Post by Jens Reyer
$ cat /etc/apt/preferences.d/x2go-ppa
Package: *
Pin: release o=LP-PPA-x2go
Pin-Priority: 1010

This is exactly the way to do it.
Closing this bug as a not-a-bug report.

I don't really get it. What is the sense in adding a ppa to your
system when you need additional steps to get the packages from there!?
This is counter-intuitive! If a user adds the ppa he/she/it states
his/her/its will to use packages from there, so why ignoring that user
wish?
Uli

It is a versioning topic. As long as we have not released a new
upstream version, the nx-libs nightly packages we built for Arctica /
X2Go are always strictly below the released package versions
officially shipped in the distro.
So, you need to enforce that the nightly builds are preferred over the
distro's nx-libs. This is wanted (by me).
And yes, it is counter intuitive for PPAs. This results from X2Go's
nx-libs 3.6.x branch simply being synced over from Github.

Then maybe this can be documented on (at least) this page (including
the apt preferences snippet):
https://launchpad.net/~x2go/+archive/ubuntu/ppa

Greets and thanks again
jre