public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ben Skeggs <darktama@iinet.net.au>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] modular X - 7.0 RC1
Date: Fri, 21 Oct 2005 01:46:48 +1100	[thread overview]
Message-ID: <1129819609.14140.5.camel@disoft-dc> (raw)
In-Reply-To: <4357432E.2020009@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

Am Donnerstag, den 20.10.2005, 00:11 -0700 schrieb Donnie Berkholz:
> Thanks to the dedicated work of Joshua Baergen and me, you've got just
> what you asked for -- newer X than even money can buy. Pound on it, test
> it, break it, and file bugs. Let us know how it works.
> 
I had some issues updating xorg-server on amd64, it turns out
eselect-opengl was pointing /usr/include/GL/glxproto.h towards the emul
headers.  Which, don't contain some changes needed for the later modular
builds.  I filed bug #109922 about this issue.

Apart from that, everything I had installed for modular updated
successfully.

The only issue I've encountered so far is that XKB appears to be
completely broken for me.  I can't quite track down why at this stage.

Thanks guys for the quick work in updating the ebuilds!
Ben.

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-10-20 14:53 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-20  7:11 [gentoo-dev] modular X - 7.0 RC1 Donnie Berkholz
2005-10-20  8:37 ` Simon Strandman
2005-10-20 12:55   ` [gentoo-dev] " Duncan
2005-10-20 12:37 ` [gentoo-dev] " Spider (D.m.D. Lj.)
2005-10-20 13:26 ` Dan Armak
2005-10-20 14:41   ` Olivier Crête
2005-10-20 15:23   ` Mike Williams
2005-10-20 15:49     ` Dan Armak
2005-10-20 15:28   ` Luca Barbato
2005-10-20 15:54     ` Dan Armak
2005-10-20 18:43       ` Donnie Berkholz
2005-10-20 19:25         ` Dan Armak
2005-10-20 19:31           ` Donnie Berkholz
2005-10-20 19:35           ` Diego 'Flameeyes' Pettenò
2005-10-20 19:35             ` Ciaran McCreesh
2005-10-20 19:42             ` Donnie Berkholz
2005-10-20 19:57               ` Mike Frysinger
2005-10-20 20:01               ` Diego 'Flameeyes' Pettenò
2005-10-20 20:13                 ` Mike Owen
2005-10-20 20:19                 ` Donnie Berkholz
2005-10-20 21:40             ` Carsten Lohrke
2005-10-20 22:17               ` Alec Warner
2005-10-20 18:58       ` Matthijs van der Vleuten
2005-10-20 19:16         ` Dan Armak
2005-10-20 19:48           ` Kevin F. Quinn
2005-10-20 19:54             ` Dan Armak
2005-10-20 21:24               ` Alec Joseph Warner
2005-10-20 21:08             ` Chris Gianelloni
2005-10-20 19:49           ` Kevin F. Quinn
2005-10-20 18:37   ` Donnie Berkholz
2005-10-20 19:08     ` Dan Armak
2005-10-20 19:17       ` Donnie Berkholz
2005-10-20 19:44         ` Dan Armak
2005-10-20 20:22           ` Donnie Berkholz
2005-10-20 21:06         ` Chris Gianelloni
2005-10-20 21:14           ` Dan Armak
2005-10-20 21:37           ` Donnie Berkholz
2005-10-20 14:46 ` Ben Skeggs [this message]
2005-10-20 15:28   ` Herbie Hopkins
2005-10-20 15:55     ` Ben Skeggs
2005-10-20 15:58 ` Dan Armak
2005-10-20 18:39   ` Donnie Berkholz
2005-10-23  4:04 ` [gentoo-dev] " R Hill

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1129819609.14140.5.camel@disoft-dc \
    --to=darktama@iinet.net.au \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox