Page 2 of 2 FirstFirst 12
Results 11 to 20 of 20

Thread: suseRegister error

  1. #11
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,723
    Blog Entries
    20

    Default Re: suseRegister error

    The red packages mean either:

    1. They are installed but no longer exist in any of the enabled repositories.

    2. They are installed but the available package is older than the one installed

    If you view by the versions tab in software manager, it should become clear to you. A package that fits option 1 will show only the installed package with no other choices.

    For option 2 you should see a combination of radio buttons and package version that can be toggled as required.
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  2. #12

    Default Re: suseRegister error

    Quote Originally Posted by caf4926 View Post
    The red packages mean either:

    1. They are installed but no longer exist in any of the enabled repositories.

    2. They are installed but the available package is older than the one installed

    If you view by the versions tab in software manager, it should become clear to you. A package that fits option 1 will show only the installed package with no other choices.

    For option 2 you should see a combination of radio buttons and package version that can be toggled as required.
    Makes perfect sense. Thank you!

  3. #13
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,723
    Blog Entries
    20

    Default Re: suseRegister error

    Quote Originally Posted by wiyosaya View Post
    Makes perfect sense. Thank you!
    To someone who obviously has some in good measure, so it should.
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  4. #14
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: suseRegister error

    On 02/22/2012 04:06 AM, wiyosaya wrote:
    > I consider myself
    > a relative Linux novice, but I have quite a few years of Windows
    > c/c++/c# experience that likely give me an edge over less knowledgeable
    > users, and that Linux knowledge was enough to solve this problem given
    > everyone's input from this thread.


    believe it or not, _sometimes_ a broad and long Windows background is an
    overall minus--unless willing to listen and pay attention to the
    differences...

    for example, about once a month we get a new guy in who will NOT rest
    until he has 'fixed' his memory leak (when all is well)...

    --
    DD
    What does DistroWatch write about YOU?: http://tinyurl.com/SUSEonDW

  5. #15
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: suseRegister error

    On 2012-02-22 04:06, wiyosaya wrote:

    > I upgraded by downloading the .iso file and burning a DVD.


    So, you have done an "offline upgrade". That was one of my questions. There
    is another one. :-)

    > In thinking
    > about this more, I may have preferred that the upgrade process present
    > me with the package summary without my having to explicitly press a
    > button to see it. There could always be a "proceed with upgrade" button
    > on such a summary for people who would rather not review the package
    > manifest. Even so, that might not have helped. See below...


    It is better to review the manifest.


    > robin_listas;2442359 Wrote:


    >> Did you review yet the rpmorig and rpmnew files?


    My guess is "no".

    >> I can help you further, but not unless you answer.

    > I appreciate your willingness to help. You have already provided all
    > the help I needed as I solved the problem.


    Then go ahead and read the documentation for that type of upgrade. I wrote
    it, in fact. O:-)

    <http://en.opensuse.org/SDBffline_upgrade>

    You need to pay attention to the steps to do after the upgrade: those red
    packages are a reason.


    > One final question. When I searched for suseRegister in the Software
    > Manager, the installed version appeared in red. What does that red color
    > indicate?


    Go to the version tab. You will also see a version in parenthesis (above).
    If there is one, you have to update that package. If there is none, you
    have to add a repo that contains it or consider removal.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.4 x86_64 "Celadon" at Telcontar)

  6. #16

    Default Re: suseRegister error

    So, you have done an "offline upgrade". That was one of my questions. There
    is another one. :-)


    > In thinking
    > about this more, I may have preferred that the upgrade process present
    > me with the package summary without my having to explicitly press a
    > button to see it. There could always be a "proceed with upgrade" button
    > on such a summary for people who would rather not review the package
    > manifest. Even so, that might not have helped. See below...


    It is better to review the manifest.

    That is what I am implying. IMHO, might it be better to place the information cited directly in the eyes of the user performing the upgrade, rather than leave it up to the user to have to take an action to see that information? That way, it is clearly presented to the user as important information. Then if the user dismisses it, it is their responsibility if things did not work.

    IMHO, not presenting the information is a sign to the upgrade user that "all is well" and there are no other things to consider. What I suggest is a slightly different way of thinking. Linux attracts a wide range of users, and some of those users are not that technically astute. Presenting something like this to the user sends, IMHO, a message to that user that the information is important; without that information being brought to the attention of the user, the user may get a sense that "all is well" and not bother to look. Case in point - me.


    > robin_listas;2442359 Wrote:


    >> Did you review yet the rpmorig and rpmnew files?


    My guess is "no".

    Good guess! Being someone who does not have a wide-ranging knowledge of Linux, I did not know those files exist, and much less, where to find them. It would be wonderful if you would enlighten me on where to find them - then again, am I beyond the point where reviewing the information would make a difference?

    I was also taken aback by the initial comments of a potentially botched system and having to do a reinstall. IMHO, in the Windows world too often reinstallation is presented as the only choice, and part of the time, it does not solve any problems. IMHO, a reinstall should only be suggested as a last resort. What looked like a mess in my case seems like a situation where a few tweaks resolved most of the issues.

    Please do not take these comments as my beating up on you. My intent is to help the process. Often I have found that people in the open-source community do not take the time to respond to questions, or are indignant about doing so. Your offer of your valuable time is much appreciated, and I intend to follow the subsequent steps outlined in your "Offline Upgrade" procedure.

    I see Linux as being so very close to the "commercial quality" of Windows - though I know that some would say that Windows has no commercial quality at all. The finer details can, as I see it, make all the difference in the world. I think Linux can become something that is generally as easy to install and use as Windows, but at this point, I think it still takes some technical skills to use and maintain it - and I see that as a hindrance to wider acceptance of Linux.


    >> I can help you further, but not unless you answer.

    > I appreciate your willingness to help. You have already provided all
    > the help I needed as I solved the problem. lol!


    Then go ahead and read the documentation for that type of upgrade. I wrote
    it, in fact. O:-)

    <http://en.opensuse.org/SDB:Offline_upgrade>

    You need to pay attention to the steps to do after the upgrade: those red
    packages are a reason.


    Thank you. I intend to follow those steps. The link had a smilie in it, and was therefore unusable, however, I managed to find it using the search. SDB:Offline upgrade - openSUSE - I'm disabling smilies in this post so smilies will not interfere with the link.


    > One final question. When I searched for suseRegister in the Software
    > Manager, the installed version appeared in red. What does that red color
    > indicate?


    Go to the version tab. You will also see a version in parenthesis (above).
    If there is one, you have to update that package. If there is none, you
    have to add a repo that contains it or consider removal.


    How do I find the appropriate repos?

    Thanks again for your help.

  7. #17

    Default Re: suseRegister error

    Quote Originally Posted by DenverD View Post
    On 02/22/2012 04:06 AM, wiyosaya wrote:
    > I consider myself
    > a relative Linux novice, but I have quite a few years of Windows
    > c/c++/c# experience that likely give me an edge over less knowledgeable
    > users, and that Linux knowledge was enough to solve this problem given
    > everyone's input from this thread.


    believe it or not, _sometimes_ a broad and long Windows background is an
    overall minus--unless willing to listen and pay attention to the
    differences...

    for example, about once a month we get a new guy in who will NOT rest
    until he has 'fixed' his memory leak (when all is well)...
    To me, Linux is a completely different animal than windows. In some respects, it has become more Windows like from the user perspective, but what lies underneath is the heart of any OS.

    Most of the time, I'm willing to listen - even if it is something that I don't want to hear.

    Thanks again for your help.

  8. #18
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: suseRegister error

    On 2012-02-22 17:26, wiyosaya wrote:

    > That is what I am implying. IMHO, might it be better to place the
    > information cited directly in the eyes of the user performing the
    > upgrade, rather than leave it up to the user to have to take an action
    > to see that information? That way, it is clearly presented to the user
    > as *important information*. Then if the user dismisses it, it is their
    > responsibility if things did not work.


    The thing is, an upgrade in Linux needs some expertise. You have to know
    things.

    >> robin_listas;2442359 Wrote:

    >
    >>> Did you review yet the rpmorig and rpmnew files?

    >>
    >> My guess is "no".

    >
    > Good guess! Being someone who does not have a wide-ranging knowledge of
    > Linux, I did not know those files exist, and much less, where to find
    > them. It would be wonderful if you would enlighten me on where to find
    > them - then again, am I beyond the point where reviewing the information
    > would make a difference?


    The link I gave explains it :-)

    ....

    > I see that as a hindrance to wider acceptance of Linux.


    Mind you, I do not say that Windows is the worst thing in creation, or
    things of that sort ;-) - in fact, I say Windows is good, it works for
    many. Its simply that I prefer Linux as better for my needs. Stable, safe,
    cheaper, many things.

    But we don't put the kind of money Microsoft puts into testing things, or
    designing for ease of use. We don't have it. Things are simply a best
    effort under the circumstances.


    >> <http://en.opensuse.org/SDBffline_upgrade>
    >>
    >> You need to pay attention to the steps to do after the upgrade: those
    >> red packages are a reason.

    >
    > Thank you. I intend to follow those steps. The link had a smilie in it,
    > and was therefore unusable, however, I managed to find it using the
    > search. 'SDBffline upgrade - openSUSE'
    > (http://en.opensuse.org/SDBffline_upgrade) - I'm disabling smilies in
    > this post so smilies will not interfere with the link.


    I did not put that smiley, believe me. Even now I don't see it this side of
    "the wall". Something you may not know: this forum has an nntp gateway that
    allow people like me to participate using thunderbird or other text news
    clients - instead of a web browser.

    I have to remind myself that sometimes things I write can get garbled at
    the other side.

    >> Go to the version tab. You will also see a version in parenthesis
    >> (above). > If there is one, you have to update that package. If there is none,
    >> you have to add a repo that contains it or consider removal.

    >
    > How do I find the appropriate repos?


    That's a good question.

    You go to the openSUSE page, click on the "get it" big link, and on the top
    you see a search box; enter there whatever package you need and you will
    get a list of repos. Which are appropriate and which not, is a matter of
    experience and personal preferences.

    If you search for "suseRegister" there is one, but I don't think it is a
    needed package. I think you mentioned another one, but I haven't seen where
    you posted it, now.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.4 x86_64 "Celadon" at Telcontar)

  9. #19

    Cool Re: suseRegister error

    The last steps described in SDB:Offline upgrade - openSUSE though tedious, went smoothly.

    What I did was the following:

    1. Set a repository location to the distribution repository. Is there any reason I should not use this location as a repository?
    2. Ran zypper up
    3. An online update through SuSE Online Update
    4. Resolved the conf file problems - which were trivial. This was the tedious part as there were about 8 of them and none had significant changes.


    Other repositories, like the update repository, were already set by the installation.

    I still have two packages that appear in red, one is a cups printer driver - I know the source for that, and the other, IIRC, is something that does not sound important.

    BTW - that the "tunctl" rpm is not in the DVD distribution is, I think, a bug or at least a symptom of another bug. tunctl is, however, in the distribution repository. tunctl is required for sysconfig, and if someone did either of a DVD install or a traditional upgrade and got an error similar to what I got and then chose to uninstall everything, they would have created themselves a big problem. In either of the two scenarios, DVD Install or "traditional upgrade," my guess is that the problem may not show up until some unsuspecting user tries to run the software manager which is what happened in my case.

    I am not sure what version of openSuSE added tunctl, so maybe this "bug" would only apply to ancient versions like mine at 11.0 when upgrading. If this is the only reason that an 11.0 -> 12.1 update is not supported, I think that is unfortunate; however, I suspect that it is more related to the fact that 11.0 is no longer supported.

    Since tunctl is in the distribution repository, someone performing an "Online Install" or "Online Upgrade" from 11.0 -> 12.1 would likely not run into the same problem.

    The last thing I had to do was update my Iptables script as it was dropping spoofed IPV4 private network addresses in the "nat" table - (a rule widely accepted in previous versions of Iptables). The correct table to do this in, with new versions of Iptables, is now the "mangle" table.

    If there are others out there who have hesitated to update 11.0, from my experience, it is possible.

    Thanks again to all who replied.

  10. #20
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: suseRegister error

    On 2012-02-24 17:56, wiyosaya wrote:
    >
    > The last steps described in 'SDBffline upgrade - openSUSE'
    > (http://en.opensuse.org/SDBffline_upgrade) though tedious, went
    > smoothly.


    Good :-)


    > What I did was the following:
    >
    >
    > - Set a repository location to 'the distribution repository'
    > (http://download.opensuse.org/distrib...repo/oss/suse/). Is
    > there any reason I should not use this location as a repository?


    I do not know. Let me see, I have...

    Code:
    
    > 5 | repo-non-oss               | openSUSE-12.1-Non-Oss              | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/12.1/repo/non-oss/                                    |
    > 6 | repo-oss                   | openSUSE-12.1-Oss                  | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/12.1/repo/oss/                                        |
    It is almost the same. I think they point in fact to the same thing.

    > - Ran zypper up
    > - An online update through SuSE Online Update


    Yep, that's one of the methods, at least when there are few repos. If not,
    things get complicated.

    > - Resolved the conf file problems - which were trivial. This was the
    > tedious part as there were about 8 of them and none had significant
    > changes.


    Yes, it depends on each installation. In my case, I get dozens of them. If
    you change local configuration files chances are you get that problem when
    upgrading. If you don't do configuration changes, just use the new file.


    > BTW - that the "tunctl" rpm is not in the DVD distribution is, I think,
    > *a bug* or at least a symptom of another bug. tunctl is, however, in the
    > distribution repository. tunctl is required for sysconfig, and if
    > someone did *either of* a DVD install or a traditional upgrade and got
    > an error similar to what I got and then chose to uninstall everything,
    > they would have created themselves a big problem. In either of the two
    > scenarios, DVD Install or "traditional upgrade," my guess is that the
    > problem may not show up until some unsuspecting user tries to run the
    > software manager which is what happened in my case.


    That package is online, if it is not in the DVD then indeed it is not
    upgraded and has to be taken care later, as I mention in that wiki page. I
    have reported as bug that sort of thing, in general, but I doubt anything
    is done.

    The solution is to activate the online repos during the offline upgrade
    procedure (yes, I see the contradiction). The problem is that in that case
    the online repos take precedence and everything is downloaded, even if it
    is in the DVD, wasting time and bandwidth.


    You can report as bug in bugzilla that the tunctl package should be in the
    dvd. But of course, the DVD will not be remastered, but perhaps a note can
    be added to the release notes.


    > I am not sure what version of openSuSE added tunctl, so maybe this
    > "bug" would only apply to ancient versions like mine at 11.0 when
    > upgrading. If this is the only reason that an 11.0 -> 12.1 update is not
    > supported, I think that is unfortunate; however, I suspect that it is
    > more related to the fact that 11.0 is no longer supported.


    No, that upgrade is not supported simply because it is a big jump, more
    than two versions. A jump of 11.0 to 11.2 would be "supported" (IMO), I
    mean, should work, but you can not report bugs on it. It /was/ supported,
    it is not /now/.

    I don't know if I explained myself sufficiently :-?



    > Since tunctl is in the distribution repository, someone performing an
    > "Online Install" or "Online Upgrade" from 11.0 -> 12.1 would likely not
    > run into the same problem.


    True, but they would get into other problems. A zypper dup over more than
    one version is more problematic than an offline upgrade of the same jumps.


    > The last thing I had to do was update my Iptables script as it was
    > dropping spoofed IPV4 private network addresses in the "nat" table - (a
    > rule widely accepted in previous versions of Iptables). The correct
    > table to do this in, with new versions of Iptables, is now the "mangle"
    > table.


    Ah, yes, that sort of things happen in updates of any kind, your changes
    can be obsoleted.


    > If there are others out there who have hesitated to update 11.0, from
    > my experience, it is possible.


    :-)

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.4 x86_64 "Celadon" at Telcontar)

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •