i wanted to upgrade from 12.3 to 13.1. However, on the upgrading procedure, I thought that this would most likely delete the Intel Fortran I have and which I got for free, but it is no more free!!! So, in other words I do not want this to happen. However, I had already started the upgrading and now I am stuck with some apps from 12.3 and some from 13.1. I definitely need some good advice! Here is the current situation:
linux-yrfz:/home/vasilis # zypper lr
| Alias | Name | Enabled | Refresh
—±----------------------------±----------------------------------------±--------±-------
1 | download.opensuse.org-Extra | openSUSE BuildService - KDE:Extra | No | No
2 | download.opensuse.org-KDE3 | openSUSE BuildService - KDE:KDE3 | No | No
3 | download.opensuse.org-Wine | openSUSE BuildService - Wine CVS Builds | No | No
4 | ftp.gwdg.de-suse | Packman Repository | No | No
5 | google-earth | google-earth | Yes | Yes
6 | packman-13.1 | packman | Yes | Yes
7 | repo-13.1-non-oss | openSUSE-13.1 Non-OSS | Yes | No
8 | repo-13.1-oss | openSUSE-13.1 OSS | Yes | No
9 | repo-13.1-update-non-oss | openSUSE-13.1 Updates Non-OSS | Yes | Yes
10 | repo-13.1-update-oss | openSUSE-13.1 Updates OSS | Yes | Yes
11 | repo-debug-update | openSUSE-12.3-Update-Debug | No | No
12 | repo-debug-update-non-oss | openSUSE-12.3-Update-Debug-Non-Oss | No | No
13 | repo-non-oss | openSUSE-12.3-Non-Oss | No | No
14 | repo-oss | openSUSE-12.3-Oss | No | No
15 | repo-source | openSUSE-12.3-Source | No | No
16 | repo-update | openSUSE-12.3-Update | No | No
17 | repo-update-non-oss | openSUSE-12.3-Update-Non-Oss | No | No
On Sun, 12 Apr 2015 22:36:01 +0000, vpappasmet wrote:
> i wanted to upgrade from 12.3 to 13.1. However, on the upgrading
> procedure, I thought that this would most likely delete the Intel
> Fortran I have and which I got for free, but it is no more free!!! So,
> in other words I do not want this to happen. However, I had already
> started the upgrading and now I am stuck with some apps from 12.3 and
> some from 13.1. I definitely need some good advice! Here is the current
> situation:
First rule of doing an upgrade - make sure you have a backup.
Do you still have the installation package you got initially? (For stuff
like that, I /always/ save the installation package, because you never
know when something might go wrong with it).
First, in the openSUSE world, you should know there is a big difference between “upgrade” which changes your system from one major version to another and “update” which merely updates packages and components but you retain the same major version. So, if you are running 12.3 and “upgrade” then you will change versions, ie to 13.1 or 13.2. But, if you “update” then you stay at 12.3 while packages and components may change.
You probably need more information about your Intel Fortran app…
How was it originally installed?
Is source still available?
It looks like you disabled instead of removed your 12.3 repos… It’s likely though that the original paths to 12.3 repos don’t work anymore. If you can gain access to anyone’s 12.3 repo, you probably can reverse your upgrade and go back to 12.3 with a “zypper dup”
You also don’t describe what the state and status of your machine is… Is your machine fully upgraded to 13.2? Interrupted? And, have you tested your Fortran app?
On 2015-04-13 00:36, vpappasmet wrote:
>
> Hello all,
>
> i wanted to upgrade from 12.3 to 13.1. However, on the upgrading
> procedure, I thought that this would most likely delete the Intel
> Fortran I have and which I got for free, but it is no more free!!!
On the contrary, a system upgrade, contrary to a fresh install, does not
delete applications that you installed separately. There is danger only
when the application comes in an RPM, and there is another RPM in the
new release that nominally replaces or obsoletes it. Or it contains an
rpm with files with the same name and location as your application.
If it is something that you installed from a tgz, a binary, it is
probably safe.
I have applications in my system that have been untouched for a decade
or more…
However, before you attempt any such upgrade, you MUST HAVE A GOOD BACKUP.
Thank you all for the replies. I understand the importance of a very good backup, but just because i installed it a while ago, I had completely forgotten about it. And the truth is that I hardly remember how to do this again…At the moment, Fortran and Linux work fine, but every time I reboot, I get a message for updating some apps from version 13.1.
So, it seems that the only solution for now (at least until I finish my Phd and do not need urgently Fortran any more ) is to go back to 12.3.
My version is the following:
Linux 3.7.10-1.45-desktop
openSUSE 12.3 (Dartmouth) (x86_64)
> So, it seems that the only solution for now (at least until I finish my
> Phd and do not need urgently Fortran any more ) is to go back to
> 12.3.
I don’t see why.
At this point, the procedure for going in any direction is a zypper dup,
adjusting the repos to the target version. However, a downgrade is not a
tested procedure, your system could badly break in unknown ways, or
perhaps not.
In your place, I would make an image backup (clonezilla, dd…), plus a
full file backup (rsync), then go ahead with the upgrade. If your
fortran disappears, you still have the files in the second backup. If
that does not work, you can go to the state you are now by recovering
the image backup.
On Mon, 13 Apr 2015 19:16:02 +0000, vpappasmet wrote:
> Thank you all for the replies. I understand the importance of a very
> good backup, but just because i installed it a while ago, I had
> completely forgotten about it. And the truth is that I hardly remember
> how to do this again…At the moment, Fortran and Linux work fine, but
> every time I reboot, I get a message for updating some apps from version
> 13.1.
>
> So, it seems that the only solution for now (at least until I finish my
> Phd and do not need urgently Fortran any more ) is to go back to
> 12.3.
> My version is the following:
>
> Linux 3.7.10-1.45-desktop openSUSE 12.3 (Dartmouth) (x86_64)
Just be aware that you’re not receiving any security updates, so practice
safe computing on the network.
You might also take a look at using gcc’s fortran compiler - it should
work just as well (unless you have a specific reason you need to use the
Intel compiler).
You might also contact Intel to see if they will send you the
installation files again. Usually when software companies make
something available for free, those who take advantage of the offer are
given a way to obtain the installation files again if they need to.
That sounds great. I presume I need the Clonezilla Live (burn ISO, etc) for the image backup. For the rsync, I had a look in the forum, but I am not sure I got the process. There are many different options. Any guidance?
And what hendersj also suggested, contacting Intel, is also a good idea I had not thought of. I will do that, too, just in case.
Well there aer many backup option Clonezilla is a good one
rsync is just a fancy copy program that checks to see if files have changes and only copy changed one. Great general back method. There are several GUI’s that use rsync as a back end I like Luckybackup myself. The first backup take a good long time since all have to be copied but then only changed files are copied.
On 2015-04-14 20:36, vpappasmet wrote:
>
> That sounds great. I presume I need the Clonezilla Live (burn ISO, etc)
> for the image backup.
Yep.
(I recommended both types of backups to be on the safe side. An image is
easier to restore, and a file by file backup gives you access to any
single file, separately)
> For the rsync, I had a look in the forum, but I am
> not sure I got the process. There are many different options. Any
> guidance?
On 2015-04-15 23:06, vpappasmet wrote:
>
> So, do you think that this would work:
>
> rsync --archive --acls --xattrs --hard-links
> --stats --human-readable
> --exclude={"/dev/","/proc/","/sys/","/tmp/","/run/-media/vasilis/Phd-","/mnt/","/media/","/lost+found"}
> -/var/run/media/vasilis/Phd-/backup
I can’t say just by looking. I’d have to try and see what it does.
Hi, I have used the following command:
linux-yrfz:/home/vasilis # rsync -abHpEX --exclude={"/dev/","/proc/","/sys/","/tmp/","/run/media/vasilis/Phd","/mnt/","/media/","/lost+found"} /var/run/media/vasilis/Phd/backup
please ignore my previous post (not sure how to delete it, if I can). I managed to do the rsync, although I am not sure if everything I might need (in case sth goes wrong with my upgrading) is there. As you will see, I have excluded some files, as that was suggested in some forums. Was that a right choice or not?
Here is what I used:
On 2015-04-27 21:56, vpappasmet wrote:
>
> Hi all,
>
> please ignore my previous post (not sure how to delete it, if I can). I
> managed to do the rsync, although I am not sure if everything I might
> need (in case sth goes wrong with my upgrading) is there. As you will
> see, I have excluded some files, as that was suggested in some forums.
> Was that a right choice or not?
> Here is what I used:
>
>
> Code:
> --------------------
> linux-yrfz:/home/vasilis # rsync -avzbHpEXh --progress --exclude={"/dev/","/proc/","/sys/","/tmp/","/run/media/vasilis/Phd","/mnt/","/media/","/lost+found"} /home/vasilis /var/run/media/vasilis/Phd/backup
> --------------------
Yes, I think it is correct.
Anyway, you can look yourself at the copy.
I don’t remember if we said so before, but the backup media should be a
Linux filesystem, otherwise the file attributes are not copied.
I read a trick recently for this, from nrickert. I’ll copy it here:
mount --bind / /somewhere
> and then backup “/mnt”. The bind mount does not contain those virtual
> file systems such as “/proc” so I would be avoiding that problem. When
> done, I would unmount.
What I don’t know is other “disks” would be included or not. I haven’t
tried.
You backup what is in /somewhere. And that includes of course all the mount points that are there (because you “see” all that is also in /), but as long as nothing is mounted in those directories (like /somewhere/proc and /somewhere/home) they are empty and thus nothing is (can be) copied from there.
That is what the “trick” does, isolating the file system (and nothing but that file system) from it’s natural environment.
> Code:
> --------------------
> > >
> > mount --bind / /somewhere
> >
> --------------------
>>>
>>
>>> and then backup “/mnt”. The bind mount does not contain those virtual
>>> file systems such as “/proc” so I would be avoiding that problem. When
>>> done, I would unmount.
>>
>> What I don’t know is other “disks” would be included or not. I haven’t
>> tried.
> You backup what is in /somewhere. And that includes of course all the
> mount points that are there (because you “see” all that is also in /),
> but as long as nothing is mounted in those directories (like
> /somewhere/proc and /somewhere/home) they are empty and thus nothing is
> (can be) copied from there.
>
> That is what the “trick” does, isolating the file system (and nothing
> but that file system) from it’s natural environment.
minas-tirith:~ # mkdir /somewhere
minas-tirith:~ # mount --bind / /somewhere
minas-tirith:~ # tree /somewhere/proc
/somewhere/proc
└── bus
└── usb
2 directories, 0 files
minas-tirith:~ #
minas-tirith:~ # ls /somewhere/home
minas-tirith:~ #
) is to go back to 12.3.