Hi everyone,
I just stumbled over a nasty bug, but I'm not sure if it is a bug that is limited to X2Go, or if Debian/apt/dpkg is at fault here.
Situation: I would like to upgrade a system from wheezy to jessie. This system is running X2Go stable.
Step 1: s/wheezy/jessie/ in sources.list
Step 2: apt-get update
Step 3: Try any of the following:
apt-get install x2goserver # when it's already present in # it's wheezy incarnation apt-get upgrade
apt-get dist-upgrade
and you will see that all X2Go packages remain in their wheezy state.
Step 4: Force the installation of the exact version of x2goserver.
apt-get -t jessie install x2goserver=4.0.1.19-0x2go2+git20150608.1064+jessie.main.1
And tadaa, we get a hint at what's going on:
Reading package lists... Building dependency tree... Reading state information... The following packages were automatically installed and are no longer required: libfile-readbackwards-perl libglib1.2ldbl libgtk1.2 libgtk1.2-common libmozjs24d libnet-daemon-perl libnx-x11 libplrpc-perl libtommath0 xulrunner-24.0 Use 'apt-get autoremove' to remove them. Suggested packages: x2goserver-compat x2goserver-fmbindings x2goserver-pyhoca The following packages will be REMOVED: x2goserver-extensions x2goserver-printing x2goserver-xsession The following packages will be DOWNGRADED: x2goserver 0 upgraded, 0 newly installed, 1 downgraded, 3 to remove and 782 not upgraded. Need to get 85.5 kB of archives. After this operation, 360 kB disk space will be freed. Do you want to continue [Y/n]?
apt-get believes it is DOWNGRADING even though we're actually trying to perform an update.
Looking at the version numbers given...
4.0.1.19-0x2go2+git20150608.1064+jessie.main.1 4.0.1.19-0x2go2+git20150608.1064+wheezy.main.1
... it becomes obvious - apt does a numerical/alphabetic sort, and the only difference in those two version strings is "jessie" vs. "wheezy", with the "w" in wheezy being "higher" than the "j" in jessie.
Is this something we can fix on our own, by using numeric release numbers (7 for wheezy, 8 for jessie), or is this actually a bug that needs to be reported upstream, because maybe apt shouldn't act that way, and "latch" onto the release name instead of adding it to the numerical/alphabetic sort?
If it is entirely our own bug, what should I file it against? Picking out a particular package doesn't seem to make sense, they will all be affected. Do we have a meta-category for that?
Kind Regards, Stefan (now heading to bed after banging my head against the wall for the last 3 hours or so)
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243