On Wed, Feb 24, 2016 at 09:57:13 +0100, chrysn wrote: > hi kristof, > > On Wed, Feb 24, 2016 at 09:05:16AM +0100, Kristof Csillag wrote: > > Lately, xrandr has been updated to v1.5: > > > > user@host:~$ xrandr --version > > xrandr program version 1.5.0 > > Server reports RandR version 1.5 > > > > arandr doesn't like that at all: > > thanks for spotting this, i'm working on getting out the fix. > > > If this can't be fixed easily, then at a versioned dependency > > should be added to the package. (It still won't be usable for sid, > > but at least ppl will know.) > > unfortunately, xrandr isn't released with its own version, and i missed > the news about 1.5 being out. > > julien, do you see any way from packaging side how i could declare a > dependency on "xrandr << 1.5"? splitting out xrandr into its own > versioned package would be quite some work for just one versioned > dependency. would a "Provides: xrandr-1.5" be an option? > ewww. I don't think xrandr's output is really suitable for machine consumption. Can't you use the libXrandr API directly?
As for your question, the right thing at this point is probably to add Breaks against current versions of arandr to x11-xserver-utils. What version of arandr is likely to have that issue fixed? Cheers, Julien
