From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] trouble downgrading systemd and virtual/udev
Date: Wed, 25 Sep 2013 22:35:57 -0500 [thread overview]
Message-ID: <CADPrc82Xsbb6-vambk6gpOByv2PPQZ9UX21Pg4Mrg3XeGRKJOg@mail.gmail.com> (raw)
In-Reply-To: <87mwn0xp66.fsf@nyu.edu>
On Wed, Sep 25, 2013 at 10:00 PM, <gottlieb@nyu.edu> wrote:
> On Wed, Sep 25 2013, Canek Peláez Valdés wrote:
>
>> On Wed, Sep 25, 2013 at 5:24 PM, <gottlieb@nyu.edu> wrote:
>>> I want to downgrade systemd from 207-r2 to 204 (highest stable).
>>>
>>> I currently have virtual/udev-206-r2 installed, which prevents
>>> systemd-204.
>>>
>>> OK. So I need to downgrade virtual/udev to 200.
>>>
>>> I thought
>>> emerge -1 =virtual/udev-200 =sys-apps/systemd-204
>>> would do it. But this failed (see below) and suggested masking
>>> might help.
>>>
>>> So I added package.mask/systemd, which contains
>>> >=virtual/udev-201
>>> >=sys-apps/systemd-205
>>> and then issued the same emerge as above.
>>> But this also failed (see below).
>>> What incantation do I need?
>>
>> Don't mask anything, just make sure that systemd (both virtual/ and
>> sys-apps/) is not on package.keywords.
>
> This system is ~amd64 (I should have said that earlier).
Yeah. If you are in ~amd64, why do you want to downgrade systemd?
> I don't believe there is a virtual/systemd package.
> Did you mean virtual/udev?
Yes, sorry.
> If so, I would create
> /etc/portage/package.accept_keywords/systemd
> and put in it two lines
> -~sys-apps/systemd
> -~virtual/udev
>
> Correct?
No, I thought you were in amd64, not ~amd64. If you are in ~amd64,
putting things in /etc/portage/package.keywords should be useless.
Mixing amd64 and ~amd64 is not supported; it usually works if you are
in amd64, and you only keyword some select packages: that's the way I
use GNOME 3.8, soon 3.10, in an otherwise stable system. The other way
around (being ~amd64, and trying to force downgrade of some packages)
sounds rather convoluted to me. I think it would be rather difficult.
You can try; since you are in ~amd64 you *need* to mask the latest
versions of both systemd and virtual/udev, the ones you do not want.
But I would not be surprised if it doesn't work: if *ALL* the system
is ~amd64, the probability of something forcibly pulling the latest
versions of *anything* increases dramatically. The block could be
impossible to solve.
If you are trying to downgrade systemd for the problems related to
GNOME and logind in 206, I'm happy to report that version 207
(available since Sep 14) solves everything; at least in my desktop and
laptop. You should try it.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
next prev parent reply other threads:[~2013-09-26 3:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 22:24 [gentoo-user] trouble downgrading systemd and virtual/udev gottlieb
2013-09-26 1:04 ` [gentoo-user] " walt
2013-09-26 2:48 ` gottlieb
2013-09-26 1:30 ` [gentoo-user] " Canek Peláez Valdés
2013-09-26 3:00 ` gottlieb
2013-09-26 3:35 ` Canek Peláez Valdés [this message]
2013-09-26 15:41 ` gottlieb
2013-09-26 5:00 ` Samuli Suominen
2013-09-26 5:35 ` Canek Peláez Valdés
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=CADPrc82Xsbb6-vambk6gpOByv2PPQZ9UX21Pg4Mrg3XeGRKJOg@mail.gmail.com \
--to=caneko@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