[opensuse] Strange error when attempting to upgrade system.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm attempting to upgrade my 11.4 system to 13.1. I get the following message, just before displaying the "Installation Settings" screen: The installed product is not compatible with the product on the installation media. If you try to update using the current installation media, the system may not start some applications may not run properly. I don't know what this means. The installed system is 64 bits, and so is the upgrade media, the 13.1, 64bit, big DVD on a USB stick, which I have already used for other successful installs. I made the choice to "add online repos before installation", and both oss and non-oss are selected. I connected the network cable and it is recognized. Suspect problem #1: / is reiserfs / is ext2 You can not install 13.1 fresh on a reiserfs partition. You can not even format a partition as reiserfs. It might be that, so I would have to first migrate the partition type to ext4. But 13.1 makes no warning when I select that partition for upgrade. Suspect problem #2: The warning is about upgrading 11.4 to 13.1, the jump is large. But both at Evergreen versions. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlLJz6wACgkQtTMYHG2NR9UvqACff5g4WnxvocluLw2FGAw00DY/ G2wAn0Q18jhaNuRsDu7+Yk7sWP2SatR3 =uc8b -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Вс, 05/01/2014 в 22:33 +0100, Carlos E. R. пишет:
Hi,
I'm attempting to upgrade my 11.4 system to 13.1. I get the following message, just before displaying the "Installation Settings" screen:
The installed product is not compatible with the product on the installation media. If you try to update using the current installation media, the system may not start some applications may not run properly.
Does 11.4 have /etc/os-release?
I don't know what this means. The installed system is 64 bits, and so is the upgrade media, the 13.1, 64bit, big DVD on a USB stick, which I have already used for other successful installs.
I made the choice to "add online repos before installation", and both oss and non-oss are selected. I connected the network cable and it is recognized.
Suspect problem #1:
/ is reiserfs / is ext2
You can not install 13.1 fresh on a reiserfs partition. You can not even format a partition as reiserfs. It might be that, so I would have to first migrate the partition type to ext4. But 13.1 makes no warning when I select that partition for upgrade.
Suspect problem #2:
The warning is about upgrading 11.4 to 13.1, the jump is large. But both at Evergreen versions.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Пн, 06/01/2014 в 03:43 -0300, Cristian Rodríguez пишет:
El 06/01/14 02:49, Andrey Borzenkov escribió:
Does 11.4 have /etc/os-release?
I do not think so. it appeared along systemd .
That could be a reason (without checking yast logs). Cursory glance on 13.1 suggests that it only checks /etc/os-release for currently installed version. Carlos, try adding /etc/os-release (copy from 12.3 or 13.1 and replace version and release name appropriately). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-01-06 08:12, Andrey Borzenkov wrote:
В Пн, 06/01/2014 в 03:43 -0300, Cristian Rodríguez пишет:
El 06/01/14 02:49, Andrey Borzenkov escribió:
Does 11.4 have /etc/os-release?
I do not think so. it appeared along systemd .
That could be a reason (without checking yast logs). Cursory glance on 13.1 suggests that it only checks /etc/os-release for currently installed version. Carlos, try adding /etc/os-release (copy from 12.3 or 13.1 and replace version and release name appropriately).
Too late. I converted the root partition from reiserfs to ext4 (I would eventually have to do it, so why not now?), and tried again the upgrade. Same warning box. I ignored the warning and proceeded with the upgrade, no problems (well, an unrelated one with grub). I have done others upgrades recently of other versions, but this is the only 11.4 I tried. If the yast logs were automatically saved to the hard disk, and you tell me what to look for, I will look. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
On 2014-01-06 06:49, Andrey Borzenkov wrote:
Does 11.4 have /etc/os-release?
It should not look for that file. Anyway, I'll look at the backup - the laptop is already upgraded, no problems. Telcontar:/mnt/Ext/Erebor_2/Portatil_entero_2/rsync_root/etc # ls os-release ls: cannot access os-release: No such file or directory Telcontar:/mnt/Ext/Erebor_2/Portatil_entero_2/rsync_root/etc # ls *SuSE* SuSE-brand SuSE-release capi.conf.SuSEconfig.saved SuSEconfig: Telcontar:/mnt/Ext/Erebor_2/Portatil_entero_2/rsync_root/etc # -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
El 06/01/14 10:45, Carlos E. R. escribió:
On 2014-01-06 06:49, Andrey Borzenkov wrote:
Does 11.4 have /etc/os-release?
It should not look for that file.
Yes, it should, os-release replaces the old method..the only supported upgrade path is from 12.3, anything else assumes that you know exactly what you are doing. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-01-06 16:53, Cristian Rodríguez wrote:
El 06/01/14 10:45, Carlos E. R. escribió:
On 2014-01-06 06:49, Andrey Borzenkov wrote:
Does 11.4 have /etc/os-release?
It should not look for that file.
Yes, it should, os-release replaces the old method..the only supported upgrade path is from 12.3, anything else assumes that you know exactly what you are doing.
Wrong. The "zypper dup" method supports only the previous version. The DVD upgrade method has always supported several versions. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLK1nQACgkQtTMYHG2NR9VM7wCcDQUIYGzJbgYd7gTwbfINcgfn 2JkAnRvFk1pI5bE1rb2upT34B3ftU+ls =gcn5 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Mon, 06 Jan 2014, Carlos E. R. wrote:
On 2014-01-06 16:53, Cristian Rodríguez wrote:
El 06/01/14 10:45, Carlos E. R. escribió:
On 2014-01-06 06:49, Andrey Borzenkov wrote:
Does 11.4 have /etc/os-release?
It should not look for that file.
Yes, it should, os-release replaces the old method..the only supported upgrade path is from 12.3, anything else assumes that you know exactly what you are doing.
Wrong.
The "zypper dup" method supports only the previous version.
Wrong. BTDT. e.g. 12.1->12.3, 11.2(32bit)->11.4(64bit) ... I might try 12.1->13.1 ;) But such Upgrades are *not* supported and I know what I'm doing and I can repair a botched upgrade by booting from the unpacked DVD-image where not even rpm works due to being 64bit but only 32bit libs still installed... And I do _not_ advise doing such upgrades. -dnh --
Make a software that is foolproof, and someone will make a better fool. Make a software that is foolproof, and only fools will want to use it. Since software cannot be foolproof, we should get rid of the the fools. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Jan 8, 2014 at 11:03 AM, David Haller
On Mon, 06 Jan 2014, Carlos E. R. wrote:
On 2014-01-06 16:53, Cristian Rodríguez wrote:
El 06/01/14 10:45, Carlos E. R. escribió:
On 2014-01-06 06:49, Andrey Borzenkov wrote:
Does 11.4 have /etc/os-release?
It should not look for that file.
Yes, it should, os-release replaces the old method..the only supported upgrade path is from 12.3, anything else assumes that you know exactly what you are doing.
Wrong.
The "zypper dup" method supports only the previous version.
Wrong. BTDT. e.g. 12.1->12.3, 11.2(32bit)->11.4(64bit) ... I might try 12.1->13.1 ;)
13.1 has at least 2 known packages that you need to have patched prior to zypper dup from 12.3. So, at least for me, and definitely for Evergreen official, zypper dup to 13.1 should be proceeded by updating to 12.3 and running "zypper patch". Given the logical distance from 11.4 to 13.1, I don't even know if I would try a direct upgrade via DVD. Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-01-08 23:38, Greg Freemyer wrote:
Given the logical distance from 11.4 to 13.1, I don't even know if I would try a direct upgrade via DVD.
It works fine, despite the error. IMHO, it is simply a bug in the version recognition code of the DVD. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLN1HcACgkQtTMYHG2NR9VUSwCaA/VShlK7MtNCps7+NV9ffiPS nNIAn392ge0vbB6J4yBm+uDxv7pr2jE6 =DHmR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-01-08 17:03, David Haller wrote:
The "zypper dup" method supports only the previous version.
Wrong.
Not wrong. The "zypper dup" method only supports, officially, an upgrade from the previous version (even if it might work). There was a statement by Stephan Kulow saying that on 2010-12-08. There is no such similar statement regarding the dvd upgrade method, to my knowledge. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLN1AQACgkQtTMYHG2NR9XSkgCgjKknkLl2wqAXCyXAbgJrFYUD zMcAn2JGVitULK13l/y20RolLexPSMiQ =sKPq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello Carlos, On Wed, 08 Jan 2014, Carlos E. R. wrote:
On 2014-01-08 17:03, David Haller wrote:
The "zypper dup" method supports only the previous version.
Wrong.
Not wrong.
Language problem.
The "zypper dup" method only supports, officially, an ^^^^^^^^^^
upgrade from the previous version (even if it might work). There was a statement by Stephan Kulow saying that on 2010-12-08. There is no such similar statement regarding the dvd upgrade method, to my knowledge.
'zypper' (and yast2, though that's more tedious) supports (as in "it works") upgrading from e.g. 12.1 to 12.3. (open)SuSE does not "support" it (as in "we claim you can do that without problems"). (open)SuSE always said "we (try) to support upgrading from the previous version. With anything else, you're on your own". Could well have been Coolo who said that officially already in the last millennium. And that was the policy since I know SuSE i.e. 5.3. All upgrade mechanisms were only "officially" supported ONLY from the previous version. But it often *does* work, I dare to say even "usually" if skipping only one version and the init-system is not exchanged (sysv -> systemd! *ARGH*, that _DOES_ goes beyond zypper's abilities[0]), so the tools (zypper) do support it. It's just not supported (officially by the distribution). And AFAIR a cross-arch upgrade like I did was never supported, not even from a previous or even the same distribution version. But what the heck: this is how I tend do do it: - rsync / (/old) to a empty partition (say: /new) - adjust /new/etc/grub/* to point to the new partition and /etc/zypp/repos.d/* to point to the new distro-version (and BTW: I do NOT disable external repos like packman, I'd just have to remember to reinstall e.g. all the packman stuff, which is esp. tedious for packages that depend on stuff only in packman, so a "switch to this Repo" does not suffice, as you have to uninstall packages during upgrade due to missing dependencies[1]). - test-boot /new - run zypper clean, ref, dup - test-boot /new - fix anything amiss - run zypper clean, ref, dup - fix anything amiss (on such upgrades, the first zypper dup might miss stuff) - if all went well: *tada*, else start from scratch or do a "fresh-install" instead of an upgrade ;) - eventually clean /old, to be used as /new for the next upgrade ;) Of course, there's extra work if you have a ton of packages taboo'ed/locked as I have :) $ zypper ll | wc -l 3774 *yikes* ;) (that's all the mono/csharp stuff, desktop-indexing and a BIG selection of other stuff. Yes, I searched for that crap during installation, taboo'ed it, breaking packages, and good riddance!). All that makes a 'zypper dup' quite "interesting" though *hrhrhr*. Well, I know what I'm doing and e.g. on the 12.3 install for my mother[2!] I kept those locks/breaks to the absolute minimum ... -dnh [0] did a 12.1(sysv) -> 12.3(systemd) test. *ARGH* Some stuff worked. But there was still a lot to be fixed. [1] e.g. Pkg_A needs Lib_B (both only in packman). If you disable packman for the upgrade, you have to uninstall both packages in the process. And remember to reinstall Pkg_A after the upgrade, which will pull in Lib_B again. Now, I got a lot more than just one package not in the OSS/non-OSS Repos. Making a list of those packages is tedious. And it does work wonderfully just upgrading with those external Repos enabled (e.g. Packman). Of course, you MUST check before the upgrade, that the Repo for the to-be-upgraded-to version is up-to-date and contains what you need. E.g. the nvidia-driver (cue the delay of the packages for 13.1)... If something's amiss, you should delay the upgrade or disable the repo and switch to alternative packages (e.g. nv/nouveau). [2!] a Win-XP user up to then, 68 years at the time, but user of opensource like seamonkey, oOO, Gimp etc. and little else for years, I showed her some basics (and mightily irritated her by first showing WindowMaker), and she's quite happy now using XFCE. There's some issues with k3b and other minor stuff, that I could not yet talk her through fixing via phone (because I have no idea what's actually wrong). BTW: I made it extra clear upon the introduction, that it all works basically the same as Winders, it just looks a bit different and has different labels in some places. Stuff like that depends a lot on the "client". I've got a friend who's been using Win for years and still has trouble using it. For added fun, that friend has got a "gotta buy gadgets" reflex. Like a "Radio world-receiver" from Sony with the worst user-interface ever[3]. And whatnot. [3] I'm good at manuals. I understood sendmail's .cf just by reading the manual and doing some experiments (documented on the german ML years ago). But the interface of that Radio-gadget- from-hell and its manual had me almost giving up. And e.g. with the Android Phone she bought last year, I did not even need a manual ... ;) IKEA stuff? Easypeasy. That Sony radio? To hell with it! The worst was, it wasn't even "fun" broken, like some other $asian cruft, but all very serious and in proper english/german... Scary actually. And again: the user-interface of the actual radio was the real nightmare. The manual did help eventually. But not without major headaches because of the UI. And I have no idea if that radio-from-hell was ever put to its intended use ... And I don't want to ask, fearing I may get asked to "get it to work" or some such ... -- William, tell me somethin'. Have you come because you need my help to save a certain distressin' damsel? Or... rather a damsel in distress? Either one... -- Jack Sparrow, Pirates of the Carribean: At World's End -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 1/8/2014 8:02 PM, David Haller wrote:
*yikes* ;) (that's all the mono/csharp stuff, desktop-indexing and a BIG selection of other stuff. Yes, I searched for that crap during installation, taboo'ed it, breaking packages, and good riddance!).
On the other hand, Desktop Indexing FINALLY works, and works well, after 3 or 5 years of taboo-ing it myself, I've finally come to rely on it for my daily work flow. Need to find every program that uses a certain header file or references a certain data element? Its Instant. An there is no discernible load imposed on my machine, even when I check out a boat-load of code from our repository to work on. Wonder full. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Wed, 08 Jan 2014, John Andersen wrote:
On 1/8/2014 8:02 PM, David Haller wrote:
*yikes* ;) (that's all the mono/csharp stuff, desktop-indexing and a BIG selection of other stuff. Yes, I searched for that crap during installation, taboo'ed it, breaking packages, and good riddance!).
On the other hand, Desktop Indexing FINALLY works, and works well, after 3 or 5 years of taboo-ing it myself, I've finally come to rely on it for my daily work flow.
Need to find every program that uses a certain header file or references a certain data element? Its Instant. An there is no discernible load imposed on my machine, even when I check out a boat-load of code from our repository to work on. Wonder full.
Hm. That does sound interesting. What indexer / backend / frontend are you using? And can in be configured to index only specific directories? -dnh -- It's a bird.. It's a plane.. No, it's KernelMan, faster than a speeding bullet, to your rescue. Doing new kernel versions in under 5 seconds flat.. -- Linus, in the announcement for 1.3.27 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 1/10/2014 12:42 PM, David Haller wrote:
Hello,
On Wed, 08 Jan 2014, John Andersen wrote:
On 1/8/2014 8:02 PM, David Haller wrote:
*yikes* ;) (that's all the mono/csharp stuff, desktop-indexing and a BIG selection of other stuff. Yes, I searched for that crap during installation, taboo'ed it, breaking packages, and good riddance!).
On the other hand, Desktop Indexing FINALLY works, and works well, after 3 or 5 years of taboo-ing it myself, I've finally come to rely on it for my daily work flow.
Need to find every program that uses a certain header file or references a certain data element? Its Instant. An there is no discernible load imposed on my machine, even when I check out a boat-load of code from our repository to work on. Wonder full.
Hm. That does sound interesting. What indexer / backend / frontend are you using? And can in be configured to index only specific directories?
-dnh
I'm simply using what comes with KDE4. Nepomuk indexing, turning on all options (documents, audio, images, source code, ebooks, etc) and selecting folder structures using the "Customeize Folders option). This is all set up (per user) in the Configure Desktop menu entry of KDE. As for what is used in the backend, its whatever Neopmuk uses. I believe it is virtuoso but I can't even remember when/how that was set up. It has nepolukstorage and nepomukservice running as well as mysqld. If watching top, I'll see nepomuxindexer jump up if I change any files, none of the others seem to take any resource at all. I also gain (but really haven't used much) the ratings option for images and music, etc. (This enables 1-5 "star" rating in Dolphin file manager, as well as tagging). I do use the tagging and add comment for some things such as software modules I'm working on that I need to review, etc. I just tag them (you can create tags as you go, and add comments via the side panel in Dolphin. You can then search by comments, (I use key words, etc). (These comments are not embedded in the document, they reside in the indexing system. The only crazy and annoying thing is the full text search ONLY WORKS if you are sitting in ANY directory that is selected for indexing. If you start a full text search from a non-indexed directory it just does nothing, and gives no errors. This is maddening. (you might just as well set your entire ~/ tree to be indexed and use the exclusions tab to prevent indexing of any .iso files or such. You can include or exclude any file types. But as long as you looking at an indexed directory in Dolphin, you can search the full text all documents (or a subset) that are located anywhere on your system. Not just the current directory. Its amazingly powerful, and FINALLY useable in KDE 4.11.? It never seems to impose any significant load. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Fri, 10 Jan 2014, John Andersen wrote:
On 1/10/2014 12:42 PM, David Haller wrote:
On Wed, 08 Jan 2014, John Andersen wrote:
On the other hand, Desktop Indexing FINALLY works, and works well, after 3 or 5 years of taboo-ing it myself, I've finally come to rely on it for my daily work flow.
Need to find every program that uses a certain header file or references a certain data element? Its Instant. An there is no discernible load imposed on my machine, even when I check out a boat-load of code from our repository to work on. Wonder full.
Hm. That does sound interesting. What indexer / backend / frontend are you using? And can in be configured to index only specific directories?
I'm simply using what comes with KDE4.
Nepomuk indexing, turning on all options (documents, audio, images, source code, ebooks, etc) and selecting folder structures using the "Customeize Folders option).
Thanks for the info! -dnh -- Fabricati diem, pvnc. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Andrey Borzenkov -
Carlos E. R. -
Carlos E. R. -
Cristian Rodríguez -
David Haller -
Greg Freemyer -
John Andersen