home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.suse      Suse is actually not that bad      138,051 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 136,744 of 138,051   
   Carlos E.R. to bad sector   
   Re: yast inop after packman-repo   
   01 Mar 19 02:01:15   
   
   From: robin_listas@es.invalid   
      
   On 01/03/2019 01.49, bad sector wrote:   
   > On 2/28/19 5:59 PM, Carlos E.R. wrote:   
   >> On 28/02/2019 23.47, bad sector wrote:   
   >>> On 2/28/19 6:58 AM, Carlos E.R. wrote:   
   >>>> On 28/02/2019 04.08, bad sector wrote:   
   >>>>> On 2/27/19 9:45 PM, Carlos E.R. wrote:   
   >>>>>> On 28/02/2019 01.29, bad sector wrote:   
   >>>>>>>   
   >>>>>>> i ran the packmam-repo routine with yast on my g73 laptop   
   >>>>>>>   
   >>>>>>> the only adjustments made were those required to satisfy   
   >>>>>>> dependancy issues (quite a few actually) including uninstalling   
   >>>>>>> ruby-(2.5 i think)   
   >>>>>>   
   >>>>>> Oh gosh :-(   
   >>>>>>   
   >>>>>> And now YaST will not work.   
   >>>>>>   
   >>>>>>> now multuimedia works ok but when i try to run yast i get   
   >>>>>>>   
   >>>>>>> 'Failed to load Module 'Packages' due to:   
   >>>>>>>     Failed to load Module 'SpaceCalculation'due to:   
   >>>>>>>     cannot load such file --   
   >>>>>>>     storage Caller:   
   >>>>>>> /usr/lib64/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in   
   >>>>>>> 'require'   
   >>>>>>>   
   >>>>>>> trying to run yast ncurses same deal   
   >>>>>>>   
   >>>>>>> how can i install only the missing package off the net?   
   >>>>>>   
   >>>>>> Ruby of the correct version is critical for YaST.   
   >>>>>   
   >>>>> so one might presume that yast would throw a dependancy fit, which   
   >>>>> somehow it didn't   
   >>>>   
   >>>> No such feature. You are root, you are god.   
   >>>   
   >>> I run yast as root, yes, but i haven't seen the old option to just   
   >>> ignore dependancies for a very long time now   
   >>>   
   >>> and regardless, as i selected the removal of said ruby in about fifty   
   >>> dependancy-resolution option lists nowhere was there mention of Yast   
   >>> needing it   
   >>   
   >> You are god on your Linux system, you know it all.   
   >   
   > What planet are you on?  I know maybe 5% of it.   
      
   Sigh. You misunderstand.   
      
   I'm telling you that YaST will not oversee what you do. If you decide to   
   remove ruby it will not tell you that this will destroy yast.   
      
   You are god, you *must* know what you are doing.   
      
   >   
   >   
   >   
   >> You order "delete   
   >> ruby", and yast will just do it. It will only tell you about   
   >> dependencies, but you satisfied them.   
   >   
   > it told me about dependencies of OTHER packages ONLY, upon selecting   
   > delete ryby-2.5 it shopuld have spit out another one to the effcet that   
   > Yast needs ruby-2.5, which it did not   
      
   Of course it doesn't. You fulfilled the dependencies (deleting ruby), so   
   as far as YaST is concerned, everything is correct. Shoot your own foot,   
   not my problem. You know what you are doing, you are my god.   
      
   You don't like it? Go ahead, tell the YaST devs. We told them similar   
   things decades ago, they are not going to change...   
      
   Linux is not as forgiving as Windows. You *must* know what you do.   
      
      
   >>>>>> If you are using Leap 15.0 ruby has to be   
   >>>>>> "ruby-2.5-lp150.1.5.x86_64",   
   >>>>>> not any other.   
   >>>>>   
   >>>>> forgot to mention it's TW   
   >>>>   
   >>>> Ah, then I don't know the correct versions.   
   >>>>   
   >>>> My virtualized install of TW is not working, I can't check.   
   >>>   
   >>> I tried a 'zypper dup' but zypper gave me no option to not install the   
   >>> nouveau video driver which would knock out my requirement for the nvidia   
   >>> driver (so i aborted zypper)   
   >>   
   >> Wrong. Install it. First the nouveau, and in a different action, install   
   >> again the nvidia driver.   
   >   
   > Last time I let zypper install nouveau I ended up with an unusable system   
   >   
   > I'm runing zypper dup again, it will likely create another unusable   
   > system, and them I will again recover the backup copy of the working   
   > partition.   
      
   Well, if you insist on fighting the system, shit happens.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca