[gentoo-user] trouble downgrading systemd and virtual/udev

[gentoo-user] trouble downgrading systemd and virtual/udev

[gottlieb]

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?

thanks,
allan



=========== output from emerge without package.mask/systemd =========

livecd package.mask # emerge -1 =virtual/udev-200  =sys-apps/systemd-204

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild     UD ] sys-apps/systemd-204 [207-r2] USE="acl firmware-loader gudev introspection keymap%* kmod pam policykit tcpd -audit -cryptsetup -doc -gcrypt -http -lzma -openrc -python -qrcode (-selinux) -static-libs% {-test} -vanilla -xattr (-filecaps%*)" ABI_X86="(-32%) (-64%*) (-x32%)" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7" 2,136 kB
[nomerge       ] gnome-base/gnome-3.6.2:2.0  USE="bluetooth cdr cups extras fallback -accessibility" 
[nomerge       ]  gnome-base/gnome-shell-3.6.3.1  USE="bluetooth i18n networkmanager systemd" PYTHON_TARGETS="python2_7 -python2_6" 
[nomerge       ]   net-wireless/gnome-bluetooth-3.6.1:2/11  USE="introspection -debug -sendto" 
[nomerge       ]    app-mobilephone/obexd-0.46  USE="eds usb -nokia -server" 
[nomerge       ]     dev-libs/openobex-1.5  USE="bluetooth usb -debug -irda -syslog" 
[nomerge       ]      virtual/libusb-0-r1  ABI_X86="(64) -32 (-x32)" 
[nomerge       ]       dev-libs/libusb-compat-0.1.5-r2  USE="-debug -examples -static-libs" ABI_X86="(64) -32 (-x32)" 
[nomerge       ]        virtual/libusb-1-r1:1  ABI_X86="(64) -32 (-x32)" 
[nomerge       ]         dev-libs/libusbx-1.0.17:1  USE="udev -debug -doc -examples -static-libs {-test}" ABI_X86="(64) -32 (-x32)" 
[nomerge       ]          virtual/udev-206-r2  USE="gudev introspection kmod (-selinux) -static-libs" ABI_X86="(64) -32 (-x32)" 
[nomerge       ]           sys-fs/udev-207  USE="acl firmware-loader gudev introspection kmod openrc -doc (-selinux) -static-libs" ABI_X86="(64) -32 (-x32)" 
[ebuild  N     ]            sys-fs/udev-init-scripts-26  5 kB
[ebuild  N     ]           sys-fs/udev-207  USE="acl firmware-loader gudev introspection kmod openrc -doc (-selinux) -static-libs" ABI_X86="(64) -32 (-x32)" 2 kB
[ebuild     UD ]    virtual/udev-200 [206-r2] USE="gudev hwdb%* introspection keymap%* kmod (-selinux) -static-libs" ABI_X86="(-32%) (-64%*) (-x32%)" 0 kB
[blocks B      ] sys-apps/systemd ("sys-apps/systemd" is blocking sys-fs/udev-207)
[blocks B      ] sys-fs/udev ("sys-fs/udev" is blocking sys-apps/systemd-207-r2, sys-apps/systemd-204)

Total: 4 packages (2 downgrades, 2 new), Size of downloads: 2,142 kB
Conflict: 2 blocks (2 unsatisfied)

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

virtual/udev:0

  (virtual/udev-200::gentoo, ebuild scheduled for merge) pulled in by
    =virtual/udev-200[gudev] required by (dev-libs/libgusb-0.1.6::gentoo, installed)
    (and 27 more with the same problem)

  (virtual/udev-206-r2::gentoo, installed) pulled in by
    >=virtual/udev-200[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_x86_32(-)?,abi_x86_64(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?] required by (dev-libs/libusbx-1.0.17::gentoo, installed)
    >=virtual/udev-206-r2 required by (sys-fs/udev-207::gentoo, ebuild scheduled for merge)


It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.


 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (sys-fs/udev-207::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-fs/udev-206-r2[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_x86_32(-)?,abi_x86_64(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,gudev?,introspection?,kmod?,selinux?,static-libs?] (>=sys-fs/udev-206-r2[abi_x86_64(-),abi_x86_64(-),gudev,introspection,kmod]) required by (virtual/udev-206-r2::gentoo, installed)

  (sys-apps/systemd-204::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-apps/systemd-44 required by (x11-misc/colord-1.0.3::gentoo, installed)
    >=sys-apps/systemd-31 required by (gnome-extra/gnome-screensaver-3.6.1::gentoo, installed)
    =sys-apps/systemd-204
    sys-apps/systemd required by (sys-auth/polkit-0.112-r1::gentoo, installed)
    sys-apps/systemd required by (sys-apps/dbus-1.6.14::gentoo, installed)
    >=sys-apps/systemd-186 required by (sys-apps/accountsservice-0.6.34::gentoo, installed)
    >=sys-apps/systemd-31 required by (gnome-base/gnome-settings-daemon-3.6.4::gentoo, installed)
    >=sys-apps/systemd-200[gudev?,introspection?,keymap(+)?,kmod?,selinux?,static-libs(-)?] (>=sys-apps/systemd-200[gudev,introspection,keymap(+),kmod]) required by (virtual/udev-200::gentoo, ebuild scheduled for merge)
    >=sys-apps/systemd-39 required by (media-sound/pulseaudio-4.0::gentoo, installed)
    >=sys-apps/systemd-186[pam] required by (gnome-base/gdm-3.6.2-r1::gentoo, installed)
    >=sys-apps/systemd-44-r1[pam] required by (sys-auth/pambase-20120417-r2::gentoo, installed)
    >=sys-apps/systemd-38 required by (gnome-extra/gnome-system-monitor-3.6.1::gentoo, installed)
    sys-apps/systemd required by (gnome-base/gvfs-1.14.2::gentoo, installed)
    >=sys-apps/systemd-31 required by (gnome-base/gnome-control-center-3.6.3-r1::gentoo, installed)
    >=sys-apps/systemd-197 required by (sys-fs/udisks-2.1.1::gentoo, installed)
    >=sys-apps/systemd-183 required by (gnome-base/gnome-session-3.6.2-r2::gentoo, installed)
    >=sys-apps/systemd-31 required by (gnome-base/gnome-shell-3.6.3.1::gentoo, installed)
    >=sys-apps/systemd-183 required by (net-misc/networkmanager-0.9.8.4::gentoo, installed)
    >=sys-apps/systemd-200 required by (sys-power/upower-0.9.21::gentoo, installed)


For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked

livecd package.mask # 

=========== output from emerge with package.mask/systemd =========

livecd package.mask # emerge -1 =virtual/udev-200  =sys-apps/systemd-204

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild     UD ] sys-apps/systemd-204 [207-r2] USE="acl firmware-loader gudev introspection keymap%* kmod pam policykit tcpd -audit -cryptsetup -doc -gcrypt -http -lzma -openrc -python -qrcode (-selinux) -static-libs% {-test} -vanilla -xattr (-filecaps%*)" ABI_X86="(-32%) (-64%*) (-x32%)" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7" 2,136 kB
[nomerge       ] gnome-base/gnome-3.6.2:2.0  USE="bluetooth cdr cups extras fallback -accessibility" 
[nomerge       ]  gnome-base/gnome-shell-3.6.3.1  USE="bluetooth i18n networkmanager systemd" PYTHON_TARGETS="python2_7 -python2_6" 
[nomerge       ]   net-wireless/gnome-bluetooth-3.6.1:2/11  USE="introspection -debug -sendto" 
[nomerge       ]    app-mobilephone/obexd-0.46  USE="eds usb -nokia -server" 
[nomerge       ]     dev-libs/openobex-1.5  USE="bluetooth usb -debug -irda -syslog" 
[nomerge       ]      virtual/libusb-0-r1  ABI_X86="(64) -32 (-x32)" 
[nomerge       ]       dev-libs/libusb-compat-0.1.5-r2  USE="-debug -examples -static-libs" ABI_X86="(64) -32 (-x32)" 
[nomerge       ]        virtual/libusb-1-r1:1  ABI_X86="(64) -32 (-x32)" 
[nomerge       ]         dev-libs/libusbx-1.0.17:1  USE="udev -debug -doc -examples -static-libs {-test}" ABI_X86="(64) -32 (-x32)" 
[nomerge       ]          virtual/udev-206-r2  USE="gudev introspection kmod (-selinux) -static-libs" ABI_X86="(64) -32 (-x32)" 
[nomerge       ]           sys-fs/udev-207  USE="acl firmware-loader gudev introspection kmod openrc -doc (-selinux) -static-libs" ABI_X86="(64) -32 (-x32)" 
[ebuild  N     ]            sys-fs/udev-init-scripts-26  5 kB
[ebuild  N     ]           sys-fs/udev-207  USE="acl firmware-loader gudev introspection kmod openrc -doc (-selinux) -static-libs" ABI_X86="(64) -32 (-x32)" 2 kB
[ebuild     UD ]    virtual/udev-200 [206-r2] USE="gudev hwdb%* introspection keymap%* kmod (-selinux) -static-libs" ABI_X86="(-32%) (-64%*) (-x32%)" 0 kB
[blocks B      ] sys-apps/systemd ("sys-apps/systemd" is blocking sys-fs/udev-207)
[blocks B      ] sys-fs/udev ("sys-fs/udev" is blocking sys-apps/systemd-207-r2, sys-apps/systemd-204)

Total: 4 packages (2 downgrades, 2 new), Size of downloads: 2,142 kB
Conflict: 2 blocks (2 unsatisfied)

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

virtual/udev:0

  (virtual/udev-200::gentoo, ebuild scheduled for merge) pulled in by
    =virtual/udev-200[gudev] required by (dev-libs/libgusb-0.1.6::gentoo, installed)
    (and 27 more with the same problem)

  (virtual/udev-206-r2::gentoo, installed) pulled in by
    >=virtual/udev-200[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_x86_32(-)?,abi_x86_64(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?] required by (dev-libs/libusbx-1.0.17::gentoo, installed)
    >=virtual/udev-206-r2 required by (sys-fs/udev-207::gentoo, ebuild scheduled for merge)


It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.


 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (sys-fs/udev-207::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-fs/udev-206-r2[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_x86_32(-)?,abi_x86_64(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,gudev?,introspection?,kmod?,selinux?,static-libs?] (>=sys-fs/udev-206-r2[abi_x86_64(-),abi_x86_64(-),gudev,introspection,kmod]) required by (virtual/udev-206-r2::gentoo, installed)

  (sys-apps/systemd-204::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-apps/systemd-44 required by (x11-misc/colord-1.0.3::gentoo, installed)
    >=sys-apps/systemd-31 required by (gnome-extra/gnome-screensaver-3.6.1::gentoo, installed)
    =sys-apps/systemd-204
    sys-apps/systemd required by (sys-auth/polkit-0.112-r1::gentoo, installed)
    sys-apps/systemd required by (sys-apps/dbus-1.6.14::gentoo, installed)
    >=sys-apps/systemd-186 required by (sys-apps/accountsservice-0.6.34::gentoo, installed)
    >=sys-apps/systemd-31 required by (gnome-base/gnome-settings-daemon-3.6.4::gentoo, installed)
    >=sys-apps/systemd-200[gudev?,introspection?,keymap(+)?,kmod?,selinux?,static-libs(-)?] (>=sys-apps/systemd-200[gudev,introspection,keymap(+),kmod]) required by (virtual/udev-200::gentoo, ebuild scheduled for merge)
    >=sys-apps/systemd-39 required by (media-sound/pulseaudio-4.0::gentoo, installed)
    >=sys-apps/systemd-186[pam] required by (gnome-base/gdm-3.6.2-r1::gentoo, installed)
    >=sys-apps/systemd-44-r1[pam] required by (sys-auth/pambase-20120417-r2::gentoo, installed)
    >=sys-apps/systemd-38 required by (gnome-extra/gnome-system-monitor-3.6.1::gentoo, installed)
    sys-apps/systemd required by (gnome-base/gvfs-1.14.2::gentoo, installed)
    >=sys-apps/systemd-31 required by (gnome-base/gnome-control-center-3.6.3-r1::gentoo, installed)
    >=sys-apps/systemd-197 required by (sys-fs/udisks-2.1.1::gentoo, installed)
    >=sys-apps/systemd-183 required by (gnome-base/gnome-session-3.6.2-r2::gentoo, installed)
    >=sys-apps/systemd-31 required by (gnome-base/gnome-shell-3.6.3.1::gentoo, installed)
    >=sys-apps/systemd-183 required by (net-misc/networkmanager-0.9.8.4::gentoo, installed)
    >=sys-apps/systemd-200 required by (sys-power/upower-0.9.21::gentoo, installed)


For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked

livecd package.mask # 

[gentoo-user] Re: trouble downgrading systemd and virtual/udev

[walt]

On 09/25/2013 03: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?
> 
> thanks,
> allan

> [blocks B      ] sys-apps/systemd ("sys-apps/systemd" is blocking sys-fs/udev-207)
> [blocks B      ] sys-fs/udev ("sys-fs/udev" is blocking sys-apps/systemd-207-r2, sys-apps/systemd-204)

These conflicts are often so confusing that I emerge -C both of the
blocking packages and then re-run the emerge that I really want.

In your particular case, if you actually remove both of those packages
your machine will not be bootable until you successfully emerge the
older versions (obviously) so I strongly recommend using quickpkg to
save both packages before removing them.

Then, if the worst happens and you can't install the older versions
you can re-install the saved binary packages with emerge -K.

Another officially unapproved workaround I use when really frustrated
is to bypass "emerge" completely and do this instead:

#ebuild /usr/portage/sys-apps/systemd/systemd-204.ebuild merge

Sometimes it works :)

Re: [gentoo-user] Re: trouble downgrading systemd and virtual/udev

[gottlieb]

On Wed, Sep 25 2013, walt wrote:

> On 09/25/2013 03: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?
>> 
>> thanks,
>> allan
>
>> [blocks B ] sys-apps/systemd ("sys-apps/systemd" is blocking
>> sys-fs/udev-207)
>> [blocks B ] sys-fs/udev ("sys-fs/udev" is blocking
>> sys-apps/systemd-207-r2, sys-apps/systemd-204)
>
> These conflicts are often so confusing that I emerge -C both of the
> blocking packages and then re-run the emerge that I really want.
>
> In your particular case, if you actually remove both of those packages
> your machine will not be bootable until you successfully emerge the
> older versions (obviously) so I strongly recommend using quickpkg to
> save both packages before removing them.
>
> Then, if the worst happens and you can't install the older versions
> you can re-install the saved binary packages with emerge -K.

Right, thanks.  Note that sys-fs/udev is not on my system, the conflict
occurs because portage wants to emerge it.  I am trying to downgrade the
virtual udev.

I tried your suggestion as follows

* quickpkg'ed
    sys-app/systemd   virtual/udev   sys-app/gentoo-system-integration

* unmerged all three

* merged the desired virtual/udev version with --nodeps
  (it wouldn't work without --nodeps)

* tried to emerge the desired versions of the other two
  (without using --nodeps)

This last step fails because it seems (assuming I am reading the emerge
tree output correctly, see below) that dev-libs/lubusbx-1.0.17:1 requires
virtual/udev-206.

But I don't see that version dependence in the ebuild.  Moreover this is
the only version of libusbx in the tree so (again assuming I am reading
the tree correctly) this says that gnome 3.6 requires
virtual/udev-206-r2, which seems strange.  Indeed, canek has said that
gnome has trouble with systemd-206 (which virtual/udev-206 would bring
it).

So I did the emerge -K you suggested and am back where I started.

Any help would be appreciated.

> Another officially unapproved workaround I use when really frustrated
> is to bypass "emerge" completely and do this instead:
>
> #ebuild /usr/portage/sys-apps/systemd/systemd-204.ebuild merge
>
> Sometimes it works :)

I am hoping not to have to do that (or emerge --nodeps).

allan

================================================================

livecd package.mask # emerge -1 --ask  =sys-apps/gentoo-systemd-integration-1 =sys-apps/systemd-204

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild  N     ] sys-apps/gentoo-systemd-integration-1  0 kB
[ebuild  N    #]  sys-apps/systemd-207-r2  USE="acl filecaps firmware-loader gudev introspection kmod pam policykit tcpd -audit -cryptsetup -doc -gcrypt -http -lzma -openrc -python -qrcode (-selinux) {-test} -vanilla -xattr" ABI_X86="(64) -32 (-x32)" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7" 0 kB
[ebuild  N     ] sys-apps/systemd-204  USE="acl firmware-loader gudev introspection keymap kmod pam policykit tcpd -audit -cryptsetup -doc -gcrypt -http -lzma -openrc -python -qrcode (-selinux) -static-libs {-test} -vanilla -xattr" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7" 2,136 kB
[nomerge       ] gnome-base/gnome-3.6.2:2.0  USE="bluetooth cdr cups extras fallback -accessibility" 
[nomerge       ]  gnome-base/gnome-shell-3.6.3.1  USE="bluetooth i18n networkmanager systemd" PYTHON_TARGETS="python2_7 -python2_6" 
[nomerge       ]   net-wireless/gnome-bluetooth-3.6.1:2/11  USE="introspection -debug -sendto" 
[nomerge       ]    app-mobilephone/obexd-0.46  USE="eds usb -nokia -server" 
[nomerge       ]     dev-libs/openobex-1.5  USE="bluetooth usb -debug -irda -syslog" 
[nomerge       ]      virtual/libusb-0-r1  ABI_X86="(64) -32 (-x32)" 
[nomerge       ]       dev-libs/libusb-compat-0.1.5-r2  USE="-debug -examples -static-libs" ABI_X86="(64) -32 (-x32)" 
[nomerge       ]        virtual/libusb-1-r1:1  ABI_X86="(64) -32 (-x32)" 
[nomerge       ]         dev-libs/libusbx-1.0.17:1  USE="udev -debug -doc -examples -static-libs {-test}" ABI_X86="(64) -32 (-x32)" 
[ebuild     U #]          virtual/udev-206-r2 [200] USE="gudev introspection kmod (-selinux) -static-libs (-hwdb%*) (-keymap%*)" ABI_X86="(64%*) -32% (-x32)" 0 kB
[nomerge       ] virtual/udev-206-r2 [200] USE="gudev introspection kmod (-selinux) -static-libs (-hwdb%*) (-keymap%*)" ABI_X86="(64%*) -32% (-x32)" 
[nomerge       ]  sys-fs/udev-207  USE="acl firmware-loader gudev introspection kmod openrc -doc (-selinux) -static-libs" ABI_X86="(64) -32 (-x32)" 
[ebuild  N     ]   sys-fs/udev-init-scripts-26  5 kB
[ebuild  N     ]  sys-fs/udev-207  USE="acl firmware-loader gudev introspection kmod openrc -doc (-selinux) -static-libs" ABI_X86="(64) -32 (-x32)" 2 kB
[blocks B      ] sys-apps/systemd ("sys-apps/systemd" is blocking sys-fs/udev-207)
[blocks B      ] sys-fs/udev ("sys-fs/udev" is blocking sys-apps/systemd-204)

Total: 6 packages (1 upgrade, 5 new), Size of downloads: 2,142 kB
Conflict: 2 blocks (2 unsatisfied)

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

sys-apps/systemd:0

  (sys-apps/systemd-207-r2::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-apps/systemd-206-r4 required by (sys-apps/gentoo-systemd-integration-1::gentoo, ebuild scheduled for merge)

  (sys-apps/systemd-204::gentoo, ebuild scheduled for merge) pulled in by
    =sys-apps/systemd-204

virtual/udev:0

  (virtual/udev-200::gentoo, installed) pulled in by
    =virtual/udev-200 required by (net-misc/dhcpcd-6.1.0::gentoo, installed)
    (and 26 more with the same problem)

  (virtual/udev-206-r2::gentoo, ebuild scheduled for merge) pulled in by
    >=virtual/udev-200[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_x86_32(-)?,abi_x86_64(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?] required by (dev-libs/libusbx-1.0.17::gentoo, installed)
    >=virtual/udev-206-r2 required by (sys-fs/udev-207::gentoo, ebuild scheduled for merge)


It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.


 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (sys-fs/udev-207::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-fs/udev-206-r2[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_x86_32(-)?,abi_x86_64(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,gudev?,introspection?,kmod?,selinux?,static-libs?] (>=sys-fs/udev-206-r2[abi_x86_64(-),abi_x86_64(-),gudev,introspection,kmod]) required by (virtual/udev-206-r2::gentoo, ebuild scheduled for merge)


For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked


The following mask changes are necessary to proceed:
 (see "package.unmask" in the portage(5) man page for more details)
# required by sys-apps/gentoo-systemd-integration-1
# required by =sys-apps/gentoo-systemd-integration-1 (argument)
# /etc/portage/package.mask/systemd:
=sys-apps/systemd-207-r2
# required by x11-misc/colord-1.0.3[udev]
# required by gnome-base/gnome-control-center-3.6.3-r1[colord]
# required by gnome-base/gnome-shell-3.6.3.1
# required by app-admin/eselect-gnome-shell-extensions-20120911
# required by gnome-extra/gnome-shell-extensions-3.6.2
# required by @selected
# required by @world (argument)
# /etc/portage/package.mask/systemd:
=virtual/udev-206-r2

NOTE: The --autounmask-keep-masks option will prevent emerge
      from creating package.unmask or ** keyword changes.

Use --autounmask-write to write changes to config files (honoring
CONFIG_PROTECT). Carefully examine the list of proposed changes,
paying special attention to mask or keyword changes that may expose
experimental or unstable packages.
livecd package.mask # 

Re: [gentoo-user] trouble downgrading systemd and virtual/udev

[Canek Peláez Valdés]

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. Then uninstall virtual/udev,
downgrade systemd (just "emerge sys-apps/systemd") and then emerge
again virtual/udev. The correct version should be emerged.

Nothing in the tree (AFAICS) depends on >=virtual/udev-206, so it shoud be fine.

Regards
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

Re: [gentoo-user] trouble downgrading systemd and virtual/udev

[gottlieb]

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).
I don't believe there is a virtual/systemd package.
Did you mean virtual/udev?

If so, I would create
  /etc/portage/package.accept_keywords/systemd
and put in it two lines
  -~sys-apps/systemd
  -~virtual/udev

Correct?

thanks,
allan

Re: [gentoo-user] trouble downgrading systemd and virtual/udev

[Canek Peláez Valdés]

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

Re: [gentoo-user] trouble downgrading systemd and virtual/udev

[gottlieb]

On Wed, Sep 25 2013, Canek Peláez Valdés wrote:

> On Wed, Sep 25, 2013 at 10:00 PM,  <gottlieb@nyu.edu> wrote:
>> On Wed, Sep 25 2013, Canek Peláez Valdés wrote:
>>
>>> 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).
>
>> I would create
>>   /etc/portage/package.accept_keywords/systemd
>> and put in it two lines
>>   -~sys-apps/systemd
>>   -~virtual/udev
>>
> No, I thought you were in amd64, not ~amd64. If you are in ~amd64,
> putting things in /etc/portage/package.keywords should be useless.

Actually that is not correct.  Note the - before the ~.  I read man
portage and found out about this (see below).  It mentions running
mostly stable and mostly unstable.

> 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.

It is true that the primary reason for my using testing is for gnome-3.
My long term goal is to go to stable for my main system.  But, of
course, that takes quite a bit of time to let the unstable packages die
off (or quite a bit of effort to force the downgrades).

> 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.

I am running sys-apps/systemd-207-r2.  Booting has become MUCH worse.
I will send details to you off list.

thanks again for your continual help,
allan

================ man portage extract ================

      package.accept_keywords and package.keywords
             Per-package  ACCEPT_KEYWORDS.   Useful  for  mixing
             unstable packages in with a normally stable  system
             or  vice versa.  This will allow ACCEPT_KEYWORDS to
             be augmented for a single package.

[snip]

             Example:
             # always use unstable libgd
             media-libs/libgd ~x86
             # only use stable mplayer
             media-video/mplayer -~x86

Re: [gentoo-user] trouble downgrading systemd and virtual/udev

[Samuli Suominen]

On 26/09/13 04:30, 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. Then uninstall virtual/udev,
> downgrade systemd (just "emerge sys-apps/systemd") and then emerge
> again virtual/udev. The correct version should be emerged.
>
> Nothing in the tree (AFAICS) depends on >=virtual/udev-206, so it shoud be fine.

wrong.

 >=sys-apps/hwids-20130717-r1 requires >=virtual/udev-206


>
> Regards
>

Re: [gentoo-user] trouble downgrading systemd and virtual/udev

[Canek Peláez Valdés]

On Thu, Sep 26, 2013 at 12:00 AM, Samuli Suominen <ssuominen@gentoo.org> wrote:
> On 26/09/13 04:30, 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. Then uninstall virtual/udev,
>> downgrade systemd (just "emerge sys-apps/systemd") and then emerge
>> again virtual/udev. The correct version should be emerged.
>>
>> Nothing in the tree (AFAICS) depends on >=virtual/udev-206, so it shoud be
>> fine.
>
>
> wrong.
>
>>=sys-apps/hwids-20130717-r1 requires >=virtual/udev-206

I thought Allan was running ~amd64, as I explained later. Nothing in
stable (again, AFAICS) depends on >=virtual/udev-206.

But Allan, then perhaps if you mask the unstable versions of hwids,
you would be able to downgrade systemd.

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México