hello dear all
i did a update from opensuse 12.3 to 13.1 how to verify the process and the success
how to check the version that is runnnig now on the system ?
Which command can be used to check this!?
love to hear from you!
I hope you mean
zypper dup
and that is assuming your repos were configured appropriately first.
Once complete, you can verify package consistency with
zypper ve
On 2013-12-22 22:06, dilbertone wrote:
>
> hello dear all
>
> i did a update from opensuse 12.3 to 13.1 how to verify the process and
> the success
You can not “zypper-up from 12.3 to 13.1”. You mandatorily have to use “zypper dup” for this.
I hope you read the instructions for the system upgrade first.
> how to check the version that is runnnig now on the system ?
>
> Which command can be used to check this!?
cat /etc/os-release
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))
Note that thee is a known bug that when you use zypper dup the name in the grub menu stays at 12.3 even though all went well and you are really running 13.1 It can be corrected in Yast-boot section just change the name string
hello Robin dear Deano and gogalthorp,
many many thanks for the quick reply.
martin@linux-70ce:~>
martin@linux-70ce:~> export LANG=en_US.UTF-8
see what i get back for zypper ve
martin@linux-70ce:~> zypper ve
Loading repository data...
Reading installed packages...
The following NEW packages are going to be installed:
kernel-default kernel-firmware
The following package is going to be REMOVED:
microcode_ctl
2 new packages to install, 1 to remove.
Overall download size: 57.3 MiB. After the operation, additional 174.9 MiB will be used.
Some of the dependencies of installed packages are broken. In order to fix these dependencies, the following actions need to be taken:
Root privileges are required to fix broken package dependencies.
hmm i donno what i have to do with that? Do i take some certain steps to get some more updates or can i leave this out.
Are the steps that are mentioned above necessary or not!!?
BTW - see the resulst for - cat /etc/os-release
martin@linux-70ce:~> cat /etc/os-release
NAME=openSUSE
VERSION="13.1 (Bottle)"
VERSION_ID="13.1"
PRETTY_NAME="openSUSE 13.1 (Bottle) (i586)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:13.1"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://opensuse.org/"
ID_LIKE="suse"
martin@linux-70ce:~>
well i guess that i was successful in upgrading the system to version 13.1
any more ideas regarding this upgrade / update !?
On 2013-12-22 23:16, dilbertone wrote:
>
> hello Robin dear Deano and gogalthorp,
>
> many many thanks for the quick reply.
It is not “zypper ve”, nor “zypper up”. I repeat, it is “zypper dup”. DUP!
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))
Yes, upgrade with
zypper dup
The ‘zypper ve’ is usually used to pick up any inconsistencies with package installs and updates. (I’m not sure that it could handle rectifying a badly upgraded OS though.)
On 2013-12-23 10:16, deano ferrari wrote:
> The ‘zypper ve’ is usually used to pick up any inconsistencies with
> package installs and updates. (I’m not sure that it could handle
> rectifying a badly upgraded OS though.)
It can’t. The packages can be consistent, but still bad.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))
I doubt that somehow. I’ve never been in the situation of a badly upgraded system, but I would find it hard to believe that in this situation ‘zypper ve’ would report the installed packages as consistent, (although I could quite understand that it would be beyond the capabilities of the resolver to correct the situation.)
hello dear robin hello dear all
see the results …:
martin@linux-70ce:~> cat /etc/os-release
NAME=openSUSE
VERSION="13.1 (Bottle)"
VERSION_ID="13.1"
PRETTY_NAME="openSUSE 13.1 (Bottle) (i586)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:13.1"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://opensuse.org/"
ID_LIKE="suse"
martin@linux-70ce:~>
guess that all went nice
greetings
On 2013-12-23 23:56, dilbertone wrote:
> guess that all went nice
No.
Not till you do “zypper dup” and it says “nothing to do”.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))
On 2013-12-23 21:16, deano ferrari wrote:
>
> robin_listas;2610882 Wrote:
>>
>>
>> It can’t. The packages can be consistent, but still bad.
>>
> I doubt that somehow. I’ve never been in the situation of a badly
> upgraded system, but I would find it hard to believe that in this
> situation ‘zypper ve’ would report the installed packages as consistent,
> (although I could quite understand that it would be beyond the
> capabilities of the resolver to correct the situation.)
Ok, yes, the resolver would not be able to correct the situation, or it would already have corrected
it during the update phase.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))