Page 1 of 1

Planned transition: xserver

Posted: Sat Jan 09, 2016 3:10 am
by machinebacon
The transition of X-related packages and their dependencies will start in the next days:
https://release.debian.org/transitions/ ... r1.18.html

One way of getting through this without problems is to simply wait until the transition is over.

The other way is to monitor closely what is going to be replaced and removed.
Manually removing those xserver-xorg-video-*** packages that are anyway not used by your system (this will remove the meta-package xorg, and that's okay) can bring you through the transition quicker. Experience has shown that the xserver-xorg-video-siliconmotion package is lagging behind.

Just to clarify: this is a planned transition, so problems with regards to X that you are experiencing before 2016 Jan. 9 are not necessarily related to the affected packages.

Re: Planned transition: xserver

Posted: Sat Jan 09, 2016 8:53 am
by vic
Thanks for the warning. :)

Re: Planned transition: xserver

Posted: Sat Jan 09, 2016 9:36 am
by Snap
Thanks, bacon.

Re: Planned transition: xserver

Posted: Sat Jan 09, 2016 11:57 am
by dkeg
Looks like I'm prepped already. I still have

Code: Select all

The following packages have been kept back:
   xserver-common (1.17.2-1.1 => 1.17.3-2)
   xserver-xorg (7.7+7 => 7.7+12)
   xserver-xorg-core (1.17.2-1.1 => 1.17.3-2)
So I'm not seeing anything when I upg

Re: Planned transition: xserver

Posted: Sat Jan 09, 2016 1:19 pm
by machinebacon
^ nope, the transition will be 1.18, not 1.17.x

Re: Planned transition: xserver

Posted: Wed Jan 27, 2016 2:18 pm
by vic
Looks like it is time. Lots ox X stuff to be removed today. Time to have a little patience.

http://forum.siduction.org/index.php?topic=6032.0

Re: Planned transition: xserver

Posted: Wed Jan 27, 2016 5:21 pm
by machinebacon
Yes, thanks vic, a lot of red: https://release.debian.org/transitions/ ... r1.18.html

Seriously, do not dist-upgrade ;~)

I make this a global sticky for now.

Re: Planned transition: xserver

Posted: Wed Jan 27, 2016 6:33 pm
by simgin
^ Thanks Julius, red dawn arising, and heh, I checked the collisions.
They are more red than the chinese flag. Looks like it will plain old just NOT work with virtualbox et al. o.O
Where is my nuclear shelter :D

Re: Planned transition: xserver

Posted: Thu Jan 28, 2016 4:01 pm
by vic
Just finished with a d-u on BREAK!, no x stuff were to be removed so I went through with it. Rebooted and things looks ok. :) But when i checked my vanilla Debian install it still wanted to remove a handful of x packages. So I decided to wait and follow that up during the weekend.

Re: Planned transition: xserver

Posted: Sat Jan 30, 2016 7:52 am
by vic
Did a d-u on my plain Debian installs, one 32 and one 64bit. They both rebooted fine. So far, so good...

Re: Planned transition: xserver

Posted: Sat Jan 30, 2016 8:17 am
by darry1966
dist-upgrade of an old Popcorn install - no problems.

Re: Planned transition: xserver

Posted: Sun Jan 31, 2016 6:23 am
by franksinistra
the d-u will break mplayer or mpv when using Intel graphics card, found it the hard way last night.

Re: Planned transition: xserver

Posted: Sun Jan 31, 2016 11:52 am
by machinebacon
Frank, do you have a bug report number of that?

Re: Planned transition: xserver

Posted: Sun Jan 31, 2016 2:44 pm
by dkeg
this is getting 'fun'

Code: Select all

The following packages have been kept back:
   init (1.24 => 1.27)
   init-system-helpers (1.24 => 1.27)
   surf (0.6-1 => 0.7-1)
   sysvinit-utils (2.88dsf-59.2 => 2.88dsf-59.3)
   xserver-common (1.17.2-1.1 => 1.18.0-3)
   xserver-xorg (7.7+7 => 7.7+13)
   xserver-xorg-core (1.17.2-1.1 => 1.18.0-3)
   xserver-xorg-input-evdev (2.9.2-1 => 2.10.1-1)
   xserver-xorg-input-mouse (1.9.1-1 => 1.9.1-1+b1)
   xserver-xorg-input-synaptics (1.8.2-1 => 1.8.3-1+b1)
   xserver-xorg-input-vmmouse (13.1.0-1 => 13.1.0-1+b1)
   xserver-xorg-video-all (7.7+12 => 7.7+13)
   xserver-xorg-video-ati (7.6.1-1 => 7.6.1-1+b1)
   xserver-xorg-video-cirrus (1.5.3-1 => 1.5.3-1+b1)
   xserver-xorg-video-fbdev (0.4.4-1+b3 => 0.4.4-1+b4)
   xserver-xorg-video-intel (2.99.917-2 => 2.99.917+git20160127-1)
   xserver-xorg-video-mach64 (6.9.5-1 => 6.9.5-1+b1)
   xserver-xorg-video-mga (1.6.4-1+b1 => 1.6.4-1+b2)
   xserver-xorg-video-neomagic (1.2.9-1 => 1.2.9-1+b1)
   xserver-xorg-video-nouveau (1.0.12-1 => 1.0.12-1+b1)
   xserver-xorg-video-r128 (6.10.0-1 => 6.10.0-1+b1)
   xserver-xorg-video-radeon (7.6.1-1 => 7.6.1-1+b1)
   xserver-xorg-video-savage (2.3.8-1 => 2.3.8-1+b1)
   xserver-xorg-video-sisusb (0.9.6-2+b3 => 0.9.6-2+b4)
   xserver-xorg-video-tdfx (1.4.6-1+b1 => 1.4.6-1+b2)
   xserver-xorg-video-trident (1.3.7-1+b1 => 1.3.7-1+b2)
   xserver-xorg-video-vesa (2.3.4-1 => 2.3.4-1+b1)
   xserver-xorg-video-vmware (13.1.0-2 => 13.1.0-2+b1)

Re: Planned transition: xserver

Posted: Sun Jan 31, 2016 2:50 pm
by ivanovnegro
What a mess. Now I understand Pidsley a bit. :)
franksinistra wrote:the d-u will break mplayer or mpv when using Intel graphics card, found it the hard way last night.
Wouldn't be the first time. It already happened a year ago or something with mplayer2.

Re: Planned transition: xserver

Posted: Sun Jan 31, 2016 4:59 pm
by franksinistra
MB: no, i don't know. Honestly i'm not even sure if it's because of xserver transition (for the lack of similar hardware at my disposal). Perhaps it only affects my i965, anyway i'll test it again tomorrow on different hardware just to make sure.

^ and mpv too i believe, but it's only for opengl backend iIrc


EDIT: apparently the current mpv/mplayer issue is only affecting me when only using default (opengl) backend on X. Switching to vo=vaapi fixed it. Ah well... at least it worked.

EDIT2: ah apparently it was a configuration issue, been around since novmber on amd/ati cards. Used to be no problem on intel cards until recent transition. Fixed. Reference : https://bugs.debian.org/cgi-bin/bugrepo ... bug=803498