FreeBSD Port: x11-servers/xorg-server

[Patrick Powell]

On 09/22/14 23:50, Kevin Oberman wrote:
> On Mon, Sep 22, 2014 at 9:19 PM, William A. Mahaffey III <wam at hiwaay.net>
> wrote:
>
>> On 09/22/14 16:38, Patrick Powell wrote:
>>
>>> On 09/21/14 16:52, William A. Mahaffey III wrote:
>>>
>>>> On 09/21/14 18:12, Robert_Burmeister wrote:
>>>>
>>>>> William A. Mahaffey III wrote
>>>>>
>>>>>> On 09/21/14 11:41, Robert_Burmeister wrote:
>>>>>>
>>>>>>> On 13.09.2014 22:10, Robert Burmeister wrote:
>>>>>>>>>>> FreeBSD 10.1 i386
>>>>>>>>>>> xorg-server 1.12.4_9,1 and 1.12.4_1,1
>>>>>>>>>>> Still don't have mouse support after upgrade from 1.12.4_8,1
>>>>>>>>>>>
>>>>>>>>>> [  1786.822] (EE) Failed to load module "mouse" (module does not
>>>>>>>>> exist,
>>>>>>>>> 0)
>>>>>>>>>
>>>>>>>> Have you installed x11-drivers/xf86-input-mouse?
>>>>>>>>
>>>>>>>>> [  1786.825] (EE) Failed to load module "kbd" (module does not
>>>>>>>>> exist,
>>>>>>>>> 0)
>>>>>>>>>
>>>>>>>> And x11-drivers/xf86-input-keyboard?
>>>>>>>> _______________________________________________
>>>>>>>>
>>>>>>> Installing x11-drivers/xf86-input-mouse and
>>>>>>> x11-drivers/xf86-input-keyboard
>>>>>>> fixed the problem, however, I don't understand why upgrading
>>>>>>> from xorg-server 1.12.4_8,1 to xorg-server 1.12.4_9,1
>>>>>>> would require new drivers, or lose the ones it had.
>>>>>>>
>>>>>>> I would think these drivers would/should be a dependency for
>>>>>>> xorg-server
>>>>>>> in the Ports system...
>>>>>>> _______________________________________________
>>>>>>>
>>>>>> I have had that same problem verbatim the last 2 x-server upgrades I
>>>>>> did, & that was the fix, (re?)install the kbd & mouse drivers. I
>>>>>> (pkg-)upgraded this A.M., no such issues ....
>>>>>> ----------------------------------------------------------------------
>>>>>>
>>>>> Even more interesting...
>>>>> x11-drivers/xf86-input-mouse and x11-drivers/xf86-input-keyboard
>>>>> have xorg-server as a dependency, and so cannot be a circular
>>>>> dependency.
>>>>>
>>>>> I'm guessing that the mouse and keyboard drivers got deleted as
>>>>> dependents
>>>>> of
>>>>> xorg-server during the upgrade, but there are no dependencies in my
>>>>> desktop
>>>>> build
>>>>> process that require that they be put back, even through a complete
>>>>> system
>>>>> recompile.
>>>>>
>>>>> I'm thinking 'x11-drivers/xorg-drivers' and 'x11/xorg-minimal' should be
>>>>> bumped
>>>>> when xorg-server is upgraded.
>>>>>
>>>>> (When my current recompile is done, I will check that my xorg-drivers
>>>>> didn't
>>>>> get removed as well.)
>>>>>
>>>>
>>>> I am using pkg, no ports, no recompiling .... FBSD 9.3, BTW ....
>>>>
>>>>
>>>>   Just a thought - check to make sure that the x11-drivers/xf86-input-keyboard
>>> port on the PKGng server you are using  was actually rebuilt for the new
>>> version of  xorg-server. I had this problem a couple of weeks ago and the X
>>> log file hinted that the keyboard driver was not compatible with the
>>> version of xorg-server.  At the time I thought that this was due to a lag
>>> in the PKGng server building the new drivers so I compiled and installed
>>> the x11-drivers/xf86-input-keyboard.  The problem went away.
>>>
>>> This appears to be the same sort of issue. Perhaps the driver(s) are not
>>> getting rebuilt for the new version of xorg-server?  Or perhaps this is
>>> related to packages on the 'with_new_xorg' PKGng server versus packages on
>>> the standard PKGng server?
>>> _______________________________________________
>>> freebsd-x11 at freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-x11
>>> To unsubscribe, send any mail to "freebsd-x11-unsubscribe at freebsd.org"
>>>
>>>
>> Would that (drivers not getting rebuilt right) be a pkg problem or an X11
>> problem (or something else) ? Just checking ....
>>
>>
>> --
>>
>>          William A. Mahaffey III
>
> It's a ports issue. The ports system (which is used by pkg) depends on
> incrementing version numbers to tell when a port has been updated and needs
> to be rebuilt or when a port needs updating because a dependency has been
> updated in a way that affects the port.  The former is typically the result
> of a change to a port that changes hte version number. The later is a bump
> of the PORT_REVISION to indicate to the ports system that some change that
> did not come from a change upstream, but local to FreeBSD requires a port
> rebuild.
>
> In this case, it does not work. The actual version number has not changed
> as the upstream version has not changed. PORT_REVISION would result in the
> ports being rebuilt, but that does not play with the definition of
> WITH_NEW_XORG. I somehow needs to be bumped when any system sets
> WITH_NEW_XORG and I don't see any way in hte current structure to do this.
> It is the result of having two parallel ports trees.
>
> One possible fix is to have code in the Makefile to check WITH_NEW_XORG
> and, if it is defined, use a different PORT_REVISION. If the old Xorg
> driver gets a bump of PORT_REVESION, the new one would, as well, but I
> don't see any reason this could not be done as both numbers are in the same
> Makefile and should be only a few lines apart. something like:
> . if defined(WITH_NEW_XORG)
> PORT_REVISION=2
> . else
> PORT_REVISION=1
> . endif
>
> This may break the index, so I'm not sure it would work as simply as this,
> but I bet it could be made to work,
> --
> R. Kevin Oberman, Network Engineer, Retired
> E-mail: rkoberman at gmail.com
> _______________________________________________
> freebsd-x11 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-x11
> To unsubscribe, send any mail to "freebsd-x11-unsubscribe at freebsd.org"
>
I can't check this out right now,  BUT are the keyboard/mouse drivers on 
the WITH_NEW_XORG
repo server built correctly?   If that is the case then you can force 
PKG to fetch them from that REPO
and then you can (using some magic I don't understand, setting something 
in the comment field) force
PKG to always fetch from this repo.

I have a plan B on this,  which is to have a 'repo search order' 
capability added to PKG.
IF you search the WITH_NEW_XORG repo first,  THEN search the standard repo
AND if you have two packages with the same version, etc, then you get it 
from the first
repository you searched.

If the packages on the WITH_NEW_XORG server have the same version/etc as 
the packages on the
standardard server BUT they have been built with NEW_XORG then this 
should work.

I think.  Perhaps.  Maybe. This idea may be bogus.