| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
|
|
|
| |
Package-Manager: portage-2.0.51.20-r4
|
|
|
|
| |
Package-Manager: portage-2.0.51.20-r4
|
|
|
|
| |
Package-Manager: portage-2.0.51.20-r4
|
|
|
|
|
|
| |
--use-old' again.
Package-Manager: portage-2.0.51.20-r4
|
|
|
|
| |
Package-Manager: portage-2.0.51.20-r4
|
|
|
|
| |
Package-Manager: portage-2.0.51.20-r4
|
|
|
|
| |
Package-Manager: portage-2.0.51.20-r4
|
|
|
|
| |
Package-Manager: portage-2.0.51.20-r4
|
|
|
|
|
|
| |
exiting by doing nothing. Cleaned up --help output.
Package-Manager: portage-2.0.51.20-r4
|
|
|
|
| |
Package-Manager: portage-2.0.51.20-r4
|
|
|
|
|
|
| |
by default. You can use --impl-headers to use the ones from the specific implementation. No longer mess with nvidia tls as that's handled by the nvidia-glx ebuild instead. We just need to worry about libGL and libGLcore.
Package-Manager: portage-2.0.51.20-r4
|
|
|
|
|
| |
Package-Manager: portage-2.0.51.20-r4
Package-Manager: portage-2.0.51.20-r4
|
| |
|
| |
|
| |
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
|
|
|
|
|
| |
I'm trying to keep these two in parallel so I'm applying it to both. Caught by sekretarz.
Package-Manager: portage-2.0.51.19
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
|
|
|
|
|
| |
symlink causes major font slowdowns and seems to be some sort of migration artifact.
Package-Manager: portage-2.0.51.19
|
|
|
|
|
|
| |
that were committed upstream: 0440_all_6.8.0-support-cymotion-master-and-ibm-space-saver-keyboards.patch, 0485_all_6.8.0-afb-cfb-dlloader-fixes.patch, 0487_all_6.8.2-add-relocation-type-10-to-elfloader.patch, 2000_all_6.8.0-fb-convert-rgb-to-bgr-when-needed.patch, 5135_all_6.8.1-r128-ppc-vgaaccess.patch, 5160_all_6.8.1-benh-radeon-ppc-fixes-v2.patch, 5170_all_6.8.1.904-radeon-add-bioshotkeys-option.patch, 5180_all_6.8.2-back-out-extra-radeonsetfblocation.patch, 5190_all_6.8.2-radeon-render-byteswap.patch, 5200_all_6.8.0-newport-accel-v4.patch, 9355_all_6.7.99.2-xorgconfig-fontdir-fixes-v2.patch, 9370_all_6.8.1.904-fix-duplicate-cfb-symbols-v2.patch, 9375_all_6.8.1.904-fix-duplicate-mfb-symbols.patch, 9930_all_6.8.0-xpm-secfix-CAN-2005-0605.patch. Update some patches to reflect changes, such as 9360_all_6.7.99.2-ppc64-support-updates-v3.patch. Also drop 9180_all_4.3.0-xcursorgen-check-malloc-return.patch, which just caused a different kind of error. Drop the patched-in evdev driver (patches 9000-9003), because upstream now supplies its own, different evdev driver. (#67578) Drop 0350_all_4.2.0-vt7.patch, which has poor rationale and doesn't work very well.
Package-Manager: portage-2.0.51.19
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
|
|
|
|
|
| |
xorg-x11 version in portage.
Package-Manager: portage-2.0.51.19
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
|
|
|
|
|
| |
other OS's.
Package-Manager: portage-2.0.51.19
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
| |
|
|
|
|
|
|
| |
Add 0487_all_6.8.2-add-relocation-type-10-to-elfloader.patch: Add another relocation type to the ELF loader. (#82039) Add 5137_all_6.8.2-fix-r128-undefined-write-depth.patch: Fix direct rendering on R128 because of undefined WRITE_DEPTH. (#82705) Add 9003_all_6.8.2-lnx-evdev-keyboard-dont-grab.patch: Don\'t grab the keyboard, so combo keyboard/mice work. (#80685) Add 9913_all_6.8.2-cfbgc-gcc4.patch, 9914_all_6.8.2-mmx-gcc4.patch and 9915_all_6.8.2-radeon-gcc4.patch: GCC4 compile fixes. (fd.o #2750) Add 9920_all_6.8.2-fix-write-combining.patch: Fix case where a smaller write-combining region blocks write-combining setting of the whole frame buffer. Fix bug in wc setting code when regions are first splitted and setting of write-combining then fails. (#82735) Fix find(1) syntax in xfs init script. (#86890) Install release notes. (#82791) Add s3 and vesa drivers on alpha. (#81728) ebegin() uses shouldn\'t contain trailing periods.
Package-Manager: portage-2.0.51.19
|
| |
|
|
|
|
| |
Package-Manager: portage-2.0.51-r15
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
| |
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
| |
|
| |
|
| |
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
|
|
|
|
|
| |
was a security bug so there was some time pressure involved. I figured it's better to stable this sooner so we can save a compile for people who don't sync every day.
Package-Manager: portage-2.0.51.19
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
|
|
|
|
|
| |
forced to stay until arm, hppa, ia64 stable xorg-x11-6.8.2-r1.
Package-Manager: portage-2.0.51.19
|
|
|
|
|
|
| |
2.2 kernels. So, 2.2 kernels are no longer supported.
Package-Manager: portage-2.0.51.19
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|
|
|
|
|
|
| |
>=freetype-2.1.8, which I need to discuss with the maintainers, and this can't wait.
Package-Manager: portage-2.0.51.19
|
|
|
|
| |
Package-Manager: portage-2.0.51.19
|