public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xorg-x11 screwup
Date: Mon, 03 Jul 2006 07:05:19 +0800	[thread overview]
Message-ID: <1151881520.517.7.camel@bunyip> (raw)
In-Reply-To: <44A82B99.7060809@gentoo.org>

yes I hit it too - back before it hit stable.  It seemed that going xorg
modular is a one way trip as you cant remove modular xorg easily unless
you keep an independent record of every package installed.  I was pissed
because modular didnt work and I couldnt uninstall it!  Eventually
updates caught up with and fixed the problem, but in the meantime I had
an unusable system.  I realised the problem when I coulnt even downgrade
from 7.1 to 7.0 - this loss of control is a major pita with modular X.

BillK


On Sun, 2006-07-02 at 13:24 -0700, Donnie Berkholz wrote:
> Bo Ørsted Andresen wrote:
> > When user upgrades to modular X.org there is a block that requires him to 
> > remove xorg-x11-6.8*. Then the user upgrades, reboots and finds out there is 
> > something wrong. So he downgrades. But when downgrading there is no block 
> > requiring him to remove modular X first. So he merges xorg-x11-6.8 which 
> > overwrites a *LOT* of modular X files like e.g. startx and only unmerges 
> > xorg-x11-7.0 which is a very small package. Now the user decides to upgrade 
> > again so he unmerges xorg-x11-6.8 again and it removes all the files but 
> > portage still thinks modular X is installed except of xorg-x11-7*. So when he 
> > emerges xorg-x11-7* that package is the only one which is remerged...
> 
> That's a definite possibility. But I don't _think_ everyone encountering
> this problem has hit it, although I could be wrong.
> 
> Thanks,
> Donnie
> 
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-07-02 23:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-02 15:24 [gentoo-user] xorg-x11 screwup Matthew R. Lee
2006-07-02 19:19 ` Donnie Berkholz
2006-07-02 20:17   ` Bo Ørsted Andresen
2006-07-02 20:24     ` Donnie Berkholz
2006-07-02 20:29       ` Bo Ørsted Andresen
2006-07-02 23:05       ` W.Kenworthy [this message]
2006-07-03  3:31         ` Nick Rout
2006-07-03  5:30         ` Graham Murray
2006-07-03  7:12           ` Donnie Berkholz
2006-07-03 21:37           ` Nick Rout
2006-07-04 16:29             ` Re[2]: " Robert Cernansky
2006-07-04 16:54               ` Bo Ørsted Andresen
2006-07-04 17:11               ` Re[2]: " Alan McKinnon
2006-07-04 17:44                 ` Re[4]: " Robert Cernansky
2006-07-04 20:45                 ` Neil Bothwick
2006-07-05  3:37                   ` Nick Rout
2006-07-05  7:52                     ` Neil Bothwick
2006-07-02 20:39   ` Bo Ørsted Andresen
2006-07-02 20:53     ` Donnie Berkholz
2006-07-02 21:00       ` Bo Ørsted Andresen
2006-07-02 21:39         ` Matthew R. Lee
2006-07-02 21:45           ` Donnie Berkholz
2006-07-02 22:01           ` Bo Ørsted Andresen
2006-07-03 22:22           ` Matthew R. Lee

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=1151881520.517.7.camel@bunyip \
    --to=billk@iinet.net.au \
    --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