IABSD.fr/xenocara

Branch :


Log

Author Commit Date CI Message
af3df7cd 2020-01-04 17:58:47 Update to libxkbfile 1.1.0. Tested by krw@ and naddy@
a72dcdf2 2020-01-04 17:57:39 Update to libXvMC 1.0.12. Tested by krw@ and naddy@
10e0196f 2020-01-04 17:56:26 Update to libXi 1.7.10. Tested by krw@ and naddy@
bc231106 2020-01-04 17:55:16 Uppdate to libX11 1.6.9. Tested by krw@ and naddy@
59640628 2020-01-04 17:53:16 Update to xorgproto 2019.2. Tested by krw@ and naddy@
e2ed9db4 2019-12-29 08:55:02 update
150aa6e9 2019-12-29 08:54:02 Update to xterm 351. tested and ok solene@ jca@
d9164a6c 2019-12-24 12:15:09 update
fa95a5c1 2019-12-24 12:14:28 Update to makedepend 1.0.6
0cfba462 2019-12-24 10:27:51 Update to xrdb 1.2.0
307acfa8 2019-12-14 15:00:54 update
6fa14ff2 2019-12-14 14:57:44 Update to libXfont2 2.0.4
4cc19552 2019-12-14 14:44:26 Update to font/util 1.3.2
7b215e57 2019-12-14 14:43:17 Update to font/encodings 1.0.5
94493e31 2019-12-12 06:08:12 update
9a532c54 2019-12-12 06:05:17 Update to X server 1.20.6. Tested by naddy@
529ec772 2019-12-07 03:10:09 regen
d3074235 2019-12-07 03:09:41 build Mesa with _ISOC11_SOURCE for c11 visibility autoconf function tests run without --std and have c11 visibility timespec_get(3), a c11 function is found this way. With gcc < 4.6 Mesa will build with --std=gnu99 with clang it will build with --std=c99 and timespec_get() will no longer be visibile. Further complicating things gcc 4.2 does not recognise --std=c11. This was not noticed on linux as they build with _GNU_SOURCE which among other things gives c11 visibility even with --std=c99. discussed with millert@
ed32a454 2019-12-04 09:53:47 xenodm uses the libc authentication layer incorrectly. fix by markus or millert Reported by Qualys
5886ab52 2019-12-04 02:26:36 Constrain honouring of path-related environment variables based upon issetugid(), not just the sloppy uid != euid test. gid != egid cases can occur also. Part of 6.6/009_mesaxlock.patch.sig and 6.5/020_mesaxlock.patch.sig From Qualys, ok
4f8bdea8 2019-12-03 17:44:29 disable opengl and mesa functionality from matthieu, ok jsg
a404f03d 2019-11-27 10:26:56 update
f42e66cb 2019-11-27 10:26:12 update to GLU 9.0.1 Among other minor changes this adds a stddef.h include for NULL required to build with Mesa 19.2 headers.
58ce6ad3 2019-11-27 02:22:35 update
b6729d75 2019-11-27 02:18:51 sync
94e5bba0 2019-11-27 02:17:47 Merge libdrm 2.4.100
a628e08e 2019-11-27 02:09:48 Import libdrm 2.4.100
974a8190 2019-11-23 14:31:41 update
7b53c812 2019-11-20 21:34:30 update
76ee08e8 2019-11-20 03:13:04 Call shmget() with permission 0600 instead of 0777 From Brian Paul 02c3dad0f3b4d26e0faa5cc51d06bc50d693dcdc in mainline Mesa "A security advisory (TALOS-2019-0857/CVE-2019-5068) found that creating shared memory regions with permission mode 0777 could allow any user to access that memory. Several Mesa drivers use shared- memory XImages to implement back buffers for improved performance. This path changes the shmget() calls to use 0600 (user r/w). Tested with legacy Xlib driver and llvmpipe."
1d6efe8e 2019-11-06 05:46:51 Tested a Logitech Webcam C930e which has 17 frame sizes but video(1) only supports 16 today. Bump the array to 32 which makes 1920x1080 work on this device as well. OK deraadt
96afcbe7 2019-10-28 19:38:47 Stop calling chmod() in cache update code. These calls are useless to toxic and come in the way of adding pledge to applications (would require 'fattr' which is quite wide). Discussed with deraadt, millert and jcs. Submitted upstreams too.
1e2269ec 2019-10-26 09:39:43 update
04984710 2019-10-26 09:37:25 Update to xf86-video-ati 19.10.0. tested by jsg@
0999e029 2019-10-26 09:36:38 Update to xf86-video-amdgpu 19.1.0. Tested by mortimer@ and jsg@
402f773f 2019-10-19 16:46:35 update
81f8815d 2019-10-19 16:39:49 Remove references to xman(1). Noticed by Alfred Morgan, thanks.
7bf4fec6 2019-10-13 06:48:12 update
35220e47 2019-09-15 12:31:08 Add modesetting driver as a fall-back when appropriate such that we can use it when running withour root privileges which prevents us from scanning the PCI bus. This makes startx(1)/xinit(1) work again on modern systems with inteldrm(4), radeondrm(4) and amdgpu(4). In some cases this will result in using a different driver than with xenodm(4) which may expose issues (e.g. when we prefer the intel Xorg driver) or loss of acceleration (e.g. older cards supported by radeondrm(4)). ok jsg@, matthieu@
92537e29 2019-09-13 19:11:23 Fix build with gcc3 which doesn't support symbol visibility. Reposrted and tested by aoyama@
425917ac 2019-09-10 19:17:29 update
5c70e5c2 2019-09-10 19:14:51 sync
bee0fbcd 2019-09-10 19:13:54 Update to freetype 2.10.1. Tested by semarie@ and naddy@
b96f6505 2019-09-10 19:09:14 MFC: randrproto: Fix missing #undef RRLease fixes build with gcc3. Problem noticed and fix confirmed by aoyama@
8a365451 2019-09-05 14:03:08 Fix gcc3 specific error. The diff is based on latest upstream change. suggested by jsg@, tested on luna88k by me, ok by jsg@ and matthieu@
cb4de3d9 2019-08-28 08:04:03 sync
4126f048 2019-08-28 08:03:10 build xf86-video-amdgpu on arm64 ok kettenis@ patrick@
86f7c2fd 2019-08-28 08:01:48 enable radeonsi and llvm on arm64 ok kettenis@ patrick@
2b9ab627 2019-08-24 16:39:33 update
cddeeb9f 2019-08-24 02:12:17 intel: Add support for Comet Lake From Anuj Phogat 82f6a746e8b47fb6e3f96d7f5f69973f50eec9ca in mesa master
5e779230 2019-08-24 01:20:16 sync i965 pci ids with xserver git master ok matthieu@
38e2fafc 2019-08-24 01:15:31 remove duplicate ids added by patch in xserver 1.20.5 update ok matthieu@
4f845b25 2019-08-15 18:06:41 update
13cff909 2019-08-15 18:06:02 Remove apps unlinked from the build several months ago.
73599d9e 2019-08-15 17:59:13 Update to xwininfo 1.1.5
6993267f 2019-08-15 17:52:58 Update to xprop 1.2.4
ef2032d6 2019-08-15 17:51:00 Update to xmodmap 1.0.10
354ece09 2019-08-15 17:48:05 Update to xmore 1.0.3
69458bc6 2019-08-15 17:43:42 Update to xlsatoms 1.1.3
fd47a85b 2019-08-15 17:40:56 Update to xlogo 1.0.5
8c7b0d02 2019-08-15 17:38:24 Update to xinput 1.6.3
f0f73ad1 2019-08-15 17:33:48 Update to xfd 1.1.3
8ac46feb 2019-08-15 17:31:43 Update to xev 1.2.3
a1d3d5c3 2019-08-15 17:29:01 Remove empty file also removed upstreams.
ecd7f987 2019-08-15 17:27:05 Update to xcompmgr 1.1.8
dc746421 2019-08-15 17:19:52 Update to xclock 1.0.9
18000292 2019-08-15 17:13:47 Update to xcalc 1.1.0
27457449 2019-08-15 17:11:34 Update to xbiff 1.0.4
aa6a2ecb 2019-08-15 17:09:24 Update to xbacklight 1.2.3
3c491892 2019-08-15 17:03:49 Update to x11perf 1.6.1
5c7f6f0f 2019-08-15 17:03:15 Update to setxkbmap 1.3.2
6d205384 2019-08-15 17:02:20 Update to sessreg 1.1.2
38d58539 2019-08-15 17:01:12 Update to mkfontscale 1.2.1. This version got merged with mkfontdir.
3910490a 2019-08-15 16:57:57 Update to fontstosfnt 1.0.5
2542268d 2019-08-15 16:56:00 Update to bitmap 1.0.9
b9bedc77 2019-08-15 16:23:33 Provide better xsession examples. exec the window manager last. Convert user's example to /bin/sh. Remove xman for example.
6a5cb530 2019-08-15 16:17:16 Remove xman and olwm (not available from ports anymore) from menu
3fd1c696 2019-08-15 16:15:04 Remove xman from utilities menu.
1e4dc55a 2019-08-15 14:48:45 Don't prune duplicate modes there. This function removes too many modes, causing trouble with the vesa driver at least. Problem reported by semarie@. Thanks.
7a992bbe 2019-08-15 12:11:36 Retire xman(1). It's totally broken (requires MLINKS which we removed long ago, relies on the old man.conf(5) format we stopped supporting long ago, Alfred Morgan reported additional bugs on bugs@, ...), it reimplements man(1) in a very poor way, and it lacks many useful features that man(1) in an xterm(1) readily provides, so fixing it would be a waste of time. matthieu@ deraadt@ krw@ agree with the direction.
2bcb96d9 2019-08-13 18:45:38 Because cwm warps the pointer during a client move (to stay within the client), there's a window of time where an expose or enternotify event will get generated for a lower client; use a hammer and drain events after keyboard move/resize, until such a time that cwm doesn't warp the pointer. Behavior noticed by kn. ok kn@
ba4d949d 2019-08-12 00:52:36 Fix regression from r1.107 (lost a return); kettenis@ pointed out the high potential for a use-after-free (true!) where kn@ ran into the regression using an app that actually exercised the XGrabPointer() failure path.
3a6045e4 2019-08-08 12:28:09 replace obsoleted xf86{,Un}BlockSIGIO() calls by input_{,un}lock() for xserver 1.20. No functional change.
2aeb2bf6 2019-08-08 12:23:34 Adapt Block and Wakeup handlers prototypes to X server 1.20. No functional change.
c0e6abce 2019-08-08 12:04:36 Adapt Block and Wakeup handlers prototypes to X server 1.20. No functional change.
77671420 2019-08-04 15:21:02 sync
056243b3 2019-08-04 13:47:51 regen after xtrans 1.4.0 update.
14a4895e 2019-08-04 13:44:46 missed README -> README.md conversion in previous
ccf7349d 2019-08-04 13:37:42 update
9563e10e 2019-08-04 13:36:02 Update to libXft 2.3.3
c6568d85 2019-08-04 13:35:29 update to libICE 1.0.10
a400859a 2019-08-04 13:34:52 Update to libX11 1.6.8 riding the major bump caused by xtrans 1.4.0
85da565e 2019-08-04 13:33:46 Update to libxtrans 1.4.0. Major bumps for libX11 and libICE. no objections from naddy@, espie@ and ajacoutot@
2e187972 2019-08-04 13:25:20 Update to libXdmcp 1.1.3
d719f7f3 2019-08-03 17:19:54 Remove one more file that is no longer part of upstream tarballs. Missed in previous commit.
95df71af 2019-08-03 16:56:01 Remove files that are no longer part of upstream tarballs. They accumulated over releases for various reasons. No build change.
f7aa5430 2019-07-27 10:35:56 sync
b085b224 2019-07-27 08:05:17 update
a77e9959 2019-07-27 07:57:06 Update to xserver 1.20.5. Tested by jsg@
14e30ce5 2019-07-27 07:49:57 Compatibility with xserver 1.20 reminded by jsg@