opensSUSE-2013-262 - systemd: re-add persistent network rules

Since upgrading to openSUSE 12.3 (Dartmouth) (x86_64) with Linux 3.7.10-1.1-desktop and KDE 4.10.00 “release1” on an AMD Athlon 64 Processor 3200+, I’m constantly being told that I need to update by re-adding these rules, but, when I try to do it, Apper or zypper tells me

A package dependency could not be found.

Whichever means I use, I get the explanation

libudev0-182-4.33.1.x86_64 requires udev = 182-4.33.1, but this requirement cannot be provided

zypper and YaST2 go on to tell me

deleted providers: udev-182-4.33.1.x86_64
Following actions will be done:
 downgrade of libudev0-182-4.33.1.x86_64 to libudev0-182-3.1.1.x86_64

This is followed by the best part of four hundred other changes, or I’m offered the alternatives

Solution 2: do not install patch:openSUSE-2013-262-1.noarch

Till now, this has seemed a better option, but Apper tells me

This update is important as it may solve critical problems.
For more information about bugs fixed by this update please visit this website:
• https://bugzilla.novell.com/show_bug.cgi?id=809843

maintenance@xxxxxxxxxxxx Message-id: 20130327160507.37BB932183@maintenance.suse.de on the other hand gives this choice a Rating: low, which I presume is unimportant, though it also gives the References: #809843, and goes on to advise

This update fixes the following issue for systemd:
- bnc#809843: udev: re-add persistent network rules (bnc#809843).
- rebase all patches, ensure that they apply properly.

Finally I’m offered

Solution 3: break libudev0-182-4.33.1.x86_64 by ignoring some of its dependencies

I’m guessing that I may have a repository problem, but don’t know what it might be. I don’t like Solutions 1 or 3, but am told I shouldn’t choose 2 either, and it’s blocking updates. Does anybody know what I should do?

show us the output from


zypper lr -d


PC: oS 12.3 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.0 | GTX 650 Ti
ThinkPad E320: oS 12.3 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.2 | HD 3000
HannsBook: oS 12.3 x86_64 | SU4100@1.3GHz | 2GB | KDE 4.10.0 | GMA4500

are you sure you used zypper DUP and not zypper UP?

i had to downgrade libudev0 to 182-3.1.1 while upgrading. could you give us the output of the following? note: --dry-run does everything but install the package, it does not alter your system

zypper in libudev0-182-3.1.1.x86_64 --oldpackage --dry-run

and then please give us a list of your repos:

zypper repos -d

and also what updates are available:

zypper list-updates
zypper list-patches
#  | Alias                        | Name                               | Enabled | Refresh | Priority | Type   | URI                                                                 | Service
---+------------------------------+------------------------------------+---------+---------+----------+--------+---------------------------------------------------------------------+--------
 1 | Packman Repository           | Packman Repository                 | Yes     | Yes     |   99     | rpm-md | http://packman.inode.at/suse/12.2/                                  |        
 2 | SuSE                         | VideoLAN                           | Yes     | Yes     |   99     | rpm-md | http://download.videolan.org/pub/vlc/SuSE/12.3/                     |        
 3 | google-chrome                | Google-Chrome                      | Yes     | Yes     |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64                 |        
 4 | google-earth                 | Google-Earth                       | Yes     | Yes     |   99     | rpm-md | http://dl.google.com/linux/earth/rpm/stable/x86_64                  |        
 5 | libdvdcss repository         | libdvdcss Repository               | Yes     | Yes     |   99     | rpm-md | http://opensuse-guide.org/repo/12.3/                                |        
 6 | openSUSE-12.2-1.6            | openSUSE-12.2-1.6                  | No      | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/openSUSE-stable/repo/oss/ |        
 7 | openSUSE-12.3                | openSUSE-12.3                      | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/openSUSE-stable/repo/oss/ |        
 8 | openSUSE-12.3-Non-OSS        | openSUSE-12.3-Non-OSS              | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/12.3/repo/non-oss/        |        
 9 | openSUSE-12.3-OSS            | openSUSE-12.3-OSS                  | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/12.3/repo/oss/            |        
10 | openSUSE-12.3-Update         | openSUSE-12.3-Update               | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/12.3/                           |        
11 | openSUSE-12.3-Update-Non-OSS | openSUSE-12.3-Update-Non-OSS       | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/12.3-non-oss/                   |        
12 | repo-debug                   | openSUSE-12.3-Debug                | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/debug/distribution/12.3/repo/oss/      |        
13 | repo-debug-update            | openSUSE-12.3-Update-Debug         | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/debug/update/12.3/                     |        
14 | repo-debug-update-non-oss    | openSUSE-12.3-Update-Debug-Non-Oss | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/debug/update/12.3-non-oss/             |        
15 | repo-source                  | openSUSE-12.3-Source               | No      | Yes     |   99     | yast2  | http://download.opensuse.org/source/distribution/12.3/repo/oss/     |  

repo 1 is for 12.2 while you seem to run 12.3 given the rest of the repos
why do you have repo 7? (same for repo 6 but that is not active, why not
delete it)
in addition but unrelated to your problem note that the videolan repo is
not really compatible with packman and can introduce problems with
multimedia

so I would change repo 1 to point to packman 12.3 and remove repo 7,
then you need to investigate what packages you have from that repo as I
suspect this is where the incompatibility comes from (but I do not know
for sure)


PC: oS 12.3 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.0 | GTX 650 Ti
ThinkPad E320: oS 12.3 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.0 | HD 3000
HannsBook: oS 12.3 x86_64 | SU4100@1.3GHz | 2GB | KDE 4.10.0 | GMA4500

I didn’t use zypper to update from 12.2 to 12.3, though I can’t remember whether I did use Apper of YaST Control Center > Software > Online Update. For this network rules update I’ve been responding to Apper.

Loading repository data...
Reading installed packages...                                                                                                                                                      
'-dry-run' is not a package name or capability.

I didn’t enter -dry-run, but have tried --dry-run twice with the same result.

I think I just posted this, but am happy to try again with your command if you tell me I’m mistaken.

Loading repository data...
Reading installed packages...
S | Repository           | Name             | Current Version | Available Version | Arch  
--+----------------------+------------------+-----------------+-------------------+-------
v | openSUSE-12.3-Update | findutils        | 4.5.10-10.1.1   | 4.5.10-10.4.1     | x86_64
v | openSUSE-12.3-Update | libudev-mini1    | 195-13.14.1     | 195-13.18.1       | x86_64
v | openSUSE-12.3-Update | systemd          | 195-13.14.1     | 195-13.18.1       | x86_64
v | openSUSE-12.3-Update | systemd-32bit    | 195-13.14.1     | 195-13.18.1       | x86_64
v | openSUSE-12.3-Update | systemd-sysvinit | 195-13.14.1     | 195-13.18.1       | x86_64
v | openSUSE-12.3-Update | udev-mini        | 195-13.14.1     | 195-13.18.1       | x86_64
Loading repository data...
Reading installed packages...

Repository           | Name              | Version | Category    | Status | Summary                                        
---------------------+-------------------+---------+-------------+--------+------------------------------------------------
openSUSE-12.3-Update | openSUSE-2013-262 | 1       | recommended | needed | systemd: re-add persistent network rules       
openSUSE-12.3-Update | openSUSE-2013-312 | 1       | recommended | needed | systemd: Several fixes                         
openSUSE-12.3-Update | openSUSE-2013-343 | 1       | recommended | needed | findutils: make updatedb ignore btrfs snapshots

A stupid oversight now corrected

It was a reminder of what openSUSE originally supplied, which I thought could do no harm while disabled. My output from zypper lr -d is now

#  | Alias                        | Name                               | Enabled | Refresh | Priority | Type   | URI                                                                 | Service
---+------------------------------+------------------------------------+---------+---------+----------+--------+---------------------------------------------------------------------+--------
 1 | Packman Repository           | Packman Repository                 | Yes     | Yes     |   99     | rpm-md | http://packman.inode.at/suse/12.3/                                  |        
 2 | SuSE                         | VideoLAN                           | Yes     | Yes     |   99     | rpm-md | http://download.videolan.org/pub/vlc/SuSE/12.3/                     |        
 3 | google-chrome                | Google Chrome                      | Yes     | Yes     |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64                 |        
 4 | google-earth                 | Google Earth                       | Yes     | Yes     |   99     | rpm-md | http://dl.google.com/linux/earth/rpm/stable/x86_64                  |        
 5 | libdvdcss repository         | libdvdcss Repository               | Yes     | Yes     |   99     | rpm-md | http://opensuse-guide.org/repo/12.3/                                |        
 6 | openSUSE-12.3                | Stable openSUSE                    | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/openSUSE-stable/repo/oss/ |        
 7 | openSUSE-12.3-Non-OSS        | openSUSE-12.3 Non-OSS              | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/12.3/repo/non-oss/        |        
 8 | openSUSE-12.3-OSS            | openSUSE-12.3 OSS                  | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/12.3/repo/oss/            |        
 9 | openSUSE-12.3-Update         | openSUSE-12.3 Update               | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/12.3/                           |        
10 | openSUSE-12.3-Update-Non-OSS | openSUSE-12.3 Update Non-OSS       | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/12.3-non-oss/                   |        
11 | repo-debug                   | openSUSE-12.3 Debug                | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/debug/distribution/12.3/repo/oss/      |        
12 | repo-debug-update            | openSUSE-12.3 Update Debug         | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/debug/update/12.3/                     |        
13 | repo-debug-update-non-oss    | openSUSE-12.3 Update Debug Non-OSS | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/debug/update/12.3-non-oss/             |        
14 | repo-source                  | openSUSE-12.3 Source               | No      | Yes     |   99     | yast2  | http://download.opensuse.org/source/distribution/12.3/repo/oss/     |

I’d be sorry to lose VideoLAN, which I’ve found better than the other possibilities I’ve tried, so would appreciate any other solutions to that problem.

I’m far from happy with the consequences of my upgrade, so would welcome any advice on how to pinpoint and correct problems.

On 2013-04-14 18:36, peterichardavis wrote:
>> Since upgrading to openSUSE 12.3 (Dartmouth) (x86_64) with Linux
>> 3.7.10-1.1-desktop and KDE 4.10.00 “release1” on an AMD Athlon 64

On 2013-04-15 13:46, peterichardavis wrote:
> brian_j;2547661 Wrote:
>> are you sure you used zypper DUP and not zypper UP?

> I didn’t use zypper to update from 12.2 to 12.3, though I can’t remember
> whether I did use Apper of YaST Control Center > Software > Online
> Update. For this network rules update I’ve been responding to Apper.

You can not do a system upgrade to 12.3 using yast nor apper. The only
tool to do an online zypper upgrade is “zypper dup”.

The documentation is this:

Online upgrade
method

Chapter 16. Upgrading the System and System Changes

You will have to read the documentation and repeat the entire procedure.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

I omitted to mention that I used YaST2 to make another attempt at the update, but with basically the same result, though the first proposed solution included a small fraction of the number of changes.

Where your libudev0 you have now I cannot tell you, the libudev0 for
12.3 is libudev0-182-3.1.1
so choose the option

> downgrade of libudev0-182-4.33.1.x86_64 to libudev0-182-3.1.1.x86_64

which is offered to you and hope for the best, if another
incompatibility is found report back, then we can try to resolve one
after the other in the hopefully correct way.

The fact remains that I used one of them to update 12.2 and ended up with what appears to be a messy 12.3. (I’ve been wondering for days why you stopped responding to that news in response to the thread I started in Install/Boot/Login.)

As you seem to be telling me that I achieved the impossible, I find it hard to imagine how I’d undo it, however much I’d like to. I certainly can’t think why I’d want to repeat what happened, but, if you can tell me how to undo it, I’ll be glad to have the opportunity to use the correct procedure when I’m ready to do it.

I tried that in YaST2, and got more similar results, and could see myself in a never-ending series of incompatibilities. In view of the post by robin_listas, I thought I’d try zypper, with the following result:

Loading repository data...
Reading installed packages...

The following package updates will NOT be installed:
  amarok aqbanking aqbanking-lang ffmpeg gstreamer-0_10 gstreamer-0_10-plugin-gnomevfs gstreamer-0_10-plugins-base gstreamer-0_10-plugins-good gstreamer-plugins-base 
  gstreamer-plugins-base-lang hwinfo k3b liba52-0 libavcodec54 libavdevice54 libavfilter3 libavformat54 libavresample0 libavutil51 libcdio14 libfaac0 libfaad2 libgstapp-0_10-0 
  libgstbasecamerabinsrc-0_10-23 libgstbasevideo-0_10-23 libgstcodecparsers-0_10-23 libgstinterfaces-0_10-0 libgstphotography-0_10-23 libgstreamer-0_10-0 
  libgstsignalprocessor-0_10-23 libgstvdp-0_10-23 libgudev-1_0-0 libiso9660-8 libmjpegutils-2_0-0 libmp3lame0 libopencore-amrnb0 libopencore-amrwb0 libpostproc52 libquicktime0 
  libsox2 libstrigi0 libswresample0 libswscale2 libtwolame0 libvlc5 libvlccore5 libxine2 libxine2-pulse libxvidcore4 mjpegtools sox strigi udev vlc vlc-aout-pulse vlc-codecs 
  vlc-gnome vlc-noX vlc-qt xf86-input-evdev xf86-input-joystick xf86-input-keyboard xf86-input-mouse xf86-input-synaptics xf86-input-vmmouse xf86-input-void xf86-input-wacom 
  xf86-video-ark xf86-video-ast xf86-video-ati xf86-video-chips xf86-video-cirrus xf86-video-dummy xf86-video-fbdev xf86-video-geode xf86-video-glint xf86-video-i128 
  xf86-video-intel xf86-video-mach64 xf86-video-mga xf86-video-neomagic xf86-video-nv xf86-video-qxl xf86-video-r128 xf86-video-savage xf86-video-siliconmotion xf86-video-sis 
  xf86-video-tdfx xf86-video-tga xf86-video-v4l xf86-video-vesa xf86-video-vmware xf86-video-voodoo xorg-x11-driver-video-nouveau xorg-x11-server yast2-hardware-detection 

The following packages are going to be upgraded:
  gstreamer-0_10-plugins-bad gstreamer-0_10-plugins-bad-lang gstreamer-0_10-plugins-ugly gstreamer-0_10-plugins-ugly-orig-addon libavcodec52 libavfilter1 libavformat52 
  libavutil50 libgstapp-0_10-0-32bit libgstapp-1_0-0 libgstaudio-1_0-0 libgstinterfaces-0_10-0-32bit libgstpbutils-1_0-0 libgstreamer-0_10-0-32bit libgstriff-1_0-0 
  libgsttag-1_0-0 libgstvideo-1_0-0 libpostproc51 libswscale0 libudev-mini1 libxine2-codecs systemd systemd-32bit systemd-sysvinit udev-mini wine-mp3 

26 packages to upgrade.
Overall download size: 8.5 MiB. After the operation, additional 8.3 KiB will be used.
Continue? [y/n/?] (y): 

Which way should I go?

If /home is a partition on its own, I would do a fresh install if I were
you and format / but leave /home intact (of course do a backup of /home
first in any case).
I think it is less effort to reinstall your programs and the additional
repos you need compared to the effort involved in trying to repair the
system package by package.


PC: oS 12.3 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.0 | GTX 650 Ti
ThinkPad E320: oS 12.3 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.0 | HD 3000
HannsBook: oS 12.3 x86_64 | SU4100@1.3GHz | 2GB | KDE 4.10.0 | GMA4500

i wrote it wrong, it’s the other way round:


zypper in --oldpackage --dry-run libudev0-182-3.1.1.x86_64

theres the online update tool that AFAIR can do a system upgrade. never used it myself though. however, AFAIK apper is just updating. so its rather important to know what you did.

could you run

zypper dup

and give the output. be sure not to press enter or to type “yes”. you can cancel with “n” “no” or strg+c

On 2013-04-15 17:26, peterichardavis wrote:
>
> robin_listas;2547927 Wrote:

>> You can not do a system upgrade to 12.3 using yast nor apper. The only
>> tool to do an online zypper upgrade is “zypper dup”.

> The fact remains that I used one of them to update 12.2 and ended up
> with what appears to be a messy 12.3. (I’ve been wondering for days why
> you stopped responding to that news in response to the thread I started
> in Install/Boot/Login.)

A funeral service, helping a friend in trouble. Some times real life
interferes with Internet life. I will have a look as time permits.

So, the machine where you talk about “Welcome to emergency mode!” is
this same machine? If it is, you have first to solve this problem, and
then handle the other one.

I wish I had known about this broken system upgrade, it would have
explained things :frowning:

> robin_listas;2547927 Wrote:
>> The documentation is this:
>>
>> ’ Online upgrade
>> method’ (http://en.opensuse.org/SDB:System_upgrade)
>> ’
>> Chapter 16. Upgrading the System and System Changes’
>> (http://tinyurl.com/93uemsr)
>>
>> You will have to read the documentation and repeat the entire
>> procedure.

> As you seem to be telling me that I achieved the impossible, I find it
> hard to imagine how I’d undo it, however much I’d like to. I certainly
> can’t think why I’d want to repeat what happened, but, if you can tell
> me how to undo it, I’ll be glad to have the opportunity to use the
> correct procedure when I’m ready to do it.

It is almost impossible to undo, unless you use btrfs and undo points
(or however they are called). It also is possible to downgrade a version
using zypper dup, but the procedure is not supported, not even
documented. Up to you.

You have to go ahead.

Basically, set up the repositories as that “SDB:System_upgrade” article
says, and then do the zypper dup. That is, do the system online upgrade
method, with a starting point that is somewhat messed.

An alternative, is to use this method instead:

Offline upgrade
method

using the 12.3 DVD.

The other alternative is a fresh install on top, of course. This keeps
all your home files, if you are using a separate home partition, but
destroys all system configs and data.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Retrieving repository 'Packman Repository' metadata .........................................................................................................................[done]
Building repository 'Packman Repository' cache ..............................................................................................................................[done]
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: libgudev-1_0-0-182-4.33.1.x86_64 requires libudev0 = 182-4.33.1, but this requirement cannot be provided
  deleted providers: libudev0-182-4.33.1.x86_64
 Solution 1: Following actions will be done:
  deinstallation of libgudev-1_0-0-182-4.33.1.x86_64
  architecture change of upower-0.9.19-2.1.1.x86_64 to upower-0.9.19-2.1.1.i586
  install upower-0.9.19-2.1.1.i586 despite the inferior architecture
  install libupower-glib1-0.9.19-2.1.1.i586 despite the inferior architecture
  architecture change of udisks2-2.0.0-5.4.1.x86_64 to udisks2-2.0.0-5.4.1.i586
  install udisks2-2.0.0-5.4.1.i586 despite the inferior architecture
  install libatasmart4-0.19-2.1.1.i586 despite the inferior architecture
  install libudisks2-0-2.0.0-5.4.1.i586 despite the inferior architecture
  architecture change of udisks-1.0.4-11.1.1.x86_64 to udisks-1.0.4-11.1.1.i586
  install udisks-1.0.4-11.1.1.i586 despite the inferior architecture
  install sg3_utils-1.33-5.1.1.i586 despite the inferior architecture
  architecture change of libnm-glib4-0.9.6.4-5.6.1.x86_64 to libnm-glib4-0.9.6.4-5.6.1.i586
  install libnm-glib4-0.9.6.4-5.6.1.i586 despite the inferior architecture
  architecture change of gvfs-backends-1.14.2-2.1.2.x86_64 to gvfs-backends-1.14.2-2.1.2.i586
  install gvfs-backends-1.14.2-2.1.2.i586 despite the inferior architecture
  architecture change of gstreamer-0_10-plugins-good-0.10.31-6.1.5.x86_64 to gstreamer-0_10-plugins-good-0.10.31-6.1.5.i586
  deinstallation of gimp-2.8.2-3.1.2.x86_64
  architecture change of PackageKit-0.8.7-4.5.1.x86_64 to PackageKit-0.8.7-4.5.1.i586
  install PackageKit-0.8.7-4.5.1.i586 despite the inferior architecture
  architecture change of NetworkManager-0.9.6.4-5.6.1.x86_64 to NetworkManager-0.9.6.4-5.6.1.i586
  install NetworkManager-0.9.6.4-5.6.1.i586 despite the inferior architecture
  architecture change of ModemManager-0.6.0.0-3.1.1.x86_64 to ModemManager-0.6.0.0-3.1.1.i586
  install ModemManager-0.6.0.0-3.1.1.i586 despite the inferior architecture
  architecture change of libatasmart4-0.19-2.1.1.x86_64 to libatasmart4-0.19-2.1.1.i586
  deinstallation of gimp-plugins-python-2.8.2-3.1.2.x86_64
  architecture change of libudisks2-0-2.0.0-5.4.1.x86_64 to libudisks2-0-2.0.0-5.4.1.i586
  architecture change of libupower-glib1-0.9.19-2.1.1.x86_64 to libupower-glib1-0.9.19-2.1.1.i586
  architecture change of sg3_utils-1.33-5.1.1.x86_64 to sg3_utils-1.33-5.1.1.i586
  architecture change of libgpod-tools-0.8.2-12.1.1.x86_64 to libgpod-tools-0.8.2-12.1.1.i586
  install libgpod-tools-0.8.2-12.1.1.i586 despite the inferior architecture
 Solution 2: do not install libudev0-182-3.1.1.x86_64
 Solution 3: do not install libudev0-182-3.1.1.x86_64
 Solution 4: break libgudev-1_0-0-182-4.33.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/4/c] (c):

That looks similar to, if not the same as, the choices I got from YaST2.

Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Loading repository data...
Reading installed packages...
Computing distribution upgrade...

Problem: libgudev-1_0-0-195-13.11.1.x86_64 requires libudev1 = 195-13.11.1, but this requirement cannot be provided
  uninstallable providers: libudev1-195-13.11.1.i586[openSUSE-12.3]
                   libudev1-195-13.11.1.x86_64[openSUSE-12.3]
                   libudev1-195-13.11.1.i586[openSUSE-12.3-OSS]
                   libudev1-195-13.11.1.x86_64[openSUSE-12.3-OSS]
 Solution 1: keep obsolete libgudev-1_0-0-182-4.33.1.x86_64
 Solution 2: deinstallation of libudev-mini1-195-13.14.1.x86_64
 Solution 3: break libgudev-1_0-0-195-13.11.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c] (c):

Does that help?

On 2013-04-16 18:46, peterichardavis wrote:

> Code:
> --------------------
> Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See ‘man zypper’ for more information about this command.
> Loading repository data…
> Reading installed packages…
> Computing distribution upgrade…
>
> Problem: libgudev-1_0-0-195-13.11.1.x86_64 requires libudev1 = 195-13.11.1, but this requirement cannot be provided
> uninstallable providers: libudev1-195-13.11.1.i586[openSUSE-12.3]
> libudev1-195-13.11.1.x86_64[openSUSE-12.3]
> libudev1-195-13.11.1.i586[openSUSE-12.3-OSS]
> libudev1-195-13.11.1.x86_64[openSUSE-12.3-OSS]
> Solution 1: keep obsolete libgudev-1_0-0-182-4.33.1.x86_64
> Solution 2: deinstallation of libudev-mini1-195-13.14.1.x86_64
> Solution 3: break libgudev-1_0-0-195-13.11.1.x86_64 by ignoring some of its dependencies
>
> Choose from above solutions by number or cancel [1/2/3/c] (c):
> --------------------
> Does that help?

You have not read the links I gave you.

Notice the “Warning” in the first line of the code section above: it is
very important.

My recommendation, in few words, is to remove all repositories (or at
least disable), except oss, non-oss, update, and update non-oss, for
12.3, then do the zypper dup.

After that is done, you add back multimedia following the advice in the
multimedia forum stickies.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

seems like there is at least libudev1 i586 installed, not x86_64… so you’ve got mixed architectures. did you already try a “solution” somewhere?

could you run:

zypper info libudev1 | grep Arch

if it says

Arch: i586

try to run:

zypper in --force libudev1.x86_64

if that succeeds without warning or dependency hell try again:

zypper in --oldpackage --dry-run libudev0-182-3.1.1.x86_64

if not, error messages please

edit: and also:

rpm -qa | grep i586

and while you’re at it, please post the whole list of

rpm -qa

at http://paste.opensuse.org/ and give us the link

On 2013-04-17 03:46, brian j wrote:
> seems like there is at least libudev1 i586 installed, not x86_64… so
> you’ve got mixed architectures. did you already try a “solution”
> somewhere?

He has a mixture of packages from 12.2 and 12.3 from a bad upgrade. That
was clear on another post. It is not possible to attempt repair
individual libraries, there can be many more.

He either does a full, clean, dup to 12.3, or he does a detailed query
to find the wrong packages and change those one by one.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

a mixture of packages of different releases isn’t that bad. had that with nearly every upgrade and was able to fix it. thing is, i was wondering why zypper wanted and arch change. now i know. thats the real problem and that has to be fixed before zypper dup.