public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
Date: Wed, 24 Jun 2009 09:25:34 -0500	[thread overview]
Message-ID: <58965d8a0906240725w3e7b7998rd707ac19ff64aaaa@mail.gmail.com> (raw)
In-Reply-To: <5bdc1c8b0906231706s3c140069rdbb9822e9b29699f@mail.gmail.com>

On Tue, Jun 23, 2009 at 7:06 PM, Mark Knecht<markknecht@gmail.com> wrote:
> Is xorg-server-1.1.1 completely gone and I'm hosed? I'm not finding it
> on my my machine. The only variations on that theme seem to be in
> /var/db/pkg. No tar files, just other programming junk.

http://sources.gentoo.org/ is your friend :) Specifically:

http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo-x86/x11-base/xorg-server/xorg-server-1.1.1-r5.ebuild

Every ebuild that has ever been in portage is available on CVS or via
the web viewcvs interface above. You'll probably need the patches for
this version from
http://sources.gentoo.org/viewcvs.py/gentoo-x86/x11-base/xorg-server/files/?hideattic=0
as well as whatever other split-ebuilds may be required to support
this version. It looks like it was obsoleted and deleted from the main
portage tree almost 2 years ago.

Download them, put them in your local overlay, mask newer-than-1.1
versions in your /etc/portage/* and hopefully your problem will be
solved. :)



      parent reply	other threads:[~2009-06-24 14:25 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 23:20 [gentoo-user] xorg-server-1.5 update/old kernel+old fglrx Mark Knecht
2009-06-23 23:27 ` [gentoo-user] " Nikos Chantziaras
2009-06-23 23:40   ` Mark Knecht
2009-06-23 23:53     ` Mark Knecht
2009-06-24  0:06       ` Mark Knecht
2009-06-24  0:16         ` Nikos Chantziaras
2009-06-24  0:27           ` Mark Knecht
2009-06-24  0:33             ` Nikos Chantziaras
2009-06-24  0:42               ` Mark Knecht
2009-06-24  1:32                 ` Neil Bothwick
2009-06-24  3:13                   ` Mark Knecht
2009-06-24  5:55                     ` Dale
2009-06-24  0:29         ` Nikos Chantziaras
2009-06-24  0:37           ` Mark Knecht
2009-06-24  1:46             ` Dale
2009-06-24  1:14         ` Keith Dart
2009-06-24  1:28         ` Neil Bothwick
2009-06-24  1:42           ` Mark Knecht
2009-06-24  7:46             ` Neil Bothwick
2009-06-24 20:17               ` Mark Knecht
2009-06-24 20:29                 ` Neil Bothwick
2009-06-24 20:32                 ` Alan McKinnon
2009-06-25  0:08                 ` Adam Carter
2009-06-25  0:46                   ` Mark Knecht
2009-06-25  0:59                     ` Nikos Chantziaras
2009-06-25  1:25                       ` Mark Knecht
2009-06-25  1:04                     ` Adam Carter
2009-06-25  1:07                       ` Nikos Chantziaras
2009-06-25  1:15                         ` Adam Carter
2009-06-25  1:27                       ` Mark Knecht
2009-06-25  1:51                         ` Nikos Chantziaras
2009-06-25  2:33                           ` Mark Knecht
2009-06-25  8:47                         ` bn
2009-06-25 17:42                           ` Mark Knecht
2009-06-24  9:21           ` Peter Humphrey
2009-06-24 14:25         ` Paul Hartman [this message]

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=58965d8a0906240725w3e7b7998rd707ac19ff64aaaa@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --cc=gentoo-user@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