Lately the upgrades offered doing a 'zypper dup' come with numerous
problems. Choices made with 4 problems generate 6 or more as I start over again with different choices.
Most of the problems generated deal with "xxxx" needs "yyyy" which cannot
be provided. Why set forth an upgrade when a dependency cannot be
provided? I hesitate to use the "Break it" option, since in many cases I
do not know what the package is doing.
I usually select either "Keep the obsolete" or "deinstall." Deinstalling then creates problems with other packages using the (to be) deinstalled package as a dependency.
I've had "Tumbleweed" since 7/2020 and regular "zypper dup(s)" have been mostly straight forward. It seems that this year, beginning in March,
these problems have intensified.
Sometimes I wish a choice was given: (x)Don't upgrade this if it will generate a problem. The (c) option Cancels the whole upgrade so nothing
gets upgraded.
A second wish would be every (upgrade) package checks all it's
dependencies to see if they are available before being offered.
Any wise counsel?
Lately the upgrades offered doing a 'zypper dup' come with numerous
problems. Choices made with 4 problems generate 6 or more as I start over again with different choices.
Most of the problems generated deal with "xxxx" needs "yyyy" which cannot
be provided. Why set forth an upgrade when a dependency cannot be
provided? I hesitate to use the "Break it" option, since in many cases I
do not know what the package is doing.
I usually select either "Keep the obsolete" or "deinstall." Deinstalling then creates problems with other packages using the (to be) deinstalled package as a dependency.
I've had "Tumbleweed" since 7/2020 and regular "zypper dup(s)" have been mostly straight forward. It seems that this year, beginning in March,
these problems have intensified.
Sometimes I wish a choice was given: (x)Don't upgrade this if it will generate a problem. The (c) option Cancels the whole upgrade so nothing
gets upgraded.
A second wish would be every (upgrade) package checks all it's
dependencies to see if they are available before being offered.
Any wise counsel?
Paul
Paul R Schmidtbleicher wrote:
Lately the upgrades offered doing a 'zypper dup' come with numerous
problems. Choices made with 4 problems generate 6 or more as I start over
again with different choices.
Most of the problems generated deal with "xxxx" needs "yyyy" which cannot
be provided.-a Why set forth an upgrade when a dependency cannot be
provided? I hesitate to use the "Break it" option, since in many cases I
do not know what the package is doing.
I usually select either "Keep the obsolete" or "deinstall."-a Deinstalling >> then creates problems with other packages using the (to be) deinstalled
package as a dependency.
I've had "Tumbleweed" since 7/2020 and regular "zypper dup(s)" have been
mostly straight forward.-a It seems that this year, beginning in March,
these problems have intensified.
Sometimes I wish a choice was given: (x)Don't upgrade this if it will
generate a problem. The (c) option Cancels the whole upgrade so nothing
gets upgraded.
A second wish would be every (upgrade) package checks all it's
dependencies to see if they are available before being offered.
Any wise counsel?
Paul
Is YaST2 -> Software -> Online Update useable under Tumbleweed?
Question: have you added repos to the defaults?
Extra repos can be a source of problems.
On Sun, 7 May 2023 03:32:32 +0200, Carlos E.R wrote:
Question: have you added repos to the defaults?
Extra repos can be a source of problems.
I have the default repositories and have added:
(1) Packman
(2) Brave (which only seem to service the "Brave Browser)
Also, it seems most of the problem packages seem somehow related to KDE stuff. "libkPim5Libk.....*"It is not normal.
Thus far, I have chosen to avoid updating. I'll give it some time.
On Tue, 9 May 2023 22:09:43 +0200, Carlos E.R. wrote:Hi
*If you wish, you can upload your repo list to susepaste and thus we
can *have a look:
*zypper lr --details | susepaste -n "Paul RS" -t "repo list" -e 40320
*Then post the resulting link here.
https://susepaste.org/a4a16f223ef3
On 10 May 2023 00:52:20 GMT
Paul R Schmidtbleicher <paulrs@foxinternet.net> wrote:
On Tue, 9 May 2023 22:09:43 +0200, Carlos E.R. wrote:Hi
*If you wish, you can upload your repo list to susepaste and thus we
can *have a look:
*zypper lr --details | susepaste -n "Paul RS" -t "repo list" -e 40320
*Then post the resulting link here.
https://susepaste.org/a4a16f223ef3
That site is dead, use the https://paste.opensuse.org/ link
Lately the upgrades offered doing a 'zypper dup' come with numerous
problems. Choices made with 4 problems generate 6 or more as I start
over again with different choices.
Paul
On 7 May 2023 00:25:23 GMT, Paul R Schmidtbleicher wrote:
Lately the upgrades offered doing a 'zypper dup' come with numerous
problems. Choices made with 4 problems generate 6 or more as I start
over again with different choices.
Paul
OK, I'm back! With too many frustrations, I've stayed away for a few
days.
Upon return, I discovered I was being offered 1260+ upgrades. (Maybe something in there would solve earlier - seemingly unresolvable -
problems.
My first 'zupper dup' revealed there were now 8 problems (from original 4 problems days ago). The first two dealt with moving packages from
'packman' to 'opensuse.' These were the 1st option. I chose it.
I then decided to try BLINDLY using Option 1 for the other 6 problems.
Now I had 8 new problems. I did the same with these next 8 problems. It returned 4 new problems. I followed the same Option 1 choices. That took
me back to 8 new problems; then 7 new problems, then 4 new problems, then
3, and finally 2 new problems. Choosing Option 1 every time with these
last two problems, I finally got to the "GO-AHEAD" screen and now 1550+ upgrades. I said "YES" (Do it)
NOTE: I had no idea what I was doing, what I was deleting, nor what I was substituting.
At this point I was figuring: (1) I would save the Home Directory; (2)
Take note of my "Bread & Butter" programs; (3) Download the newest TW DVD; and do a blank HD upgrade of TW if things all fell apart.
Well, upon 'shutdown -r now' my login came up, my desktop screen, and upon checking my "Bread & Butter" programs, they all were working. Haven't
tried anything else though . . . .
I AM NOT NECESSARILY RECOMMENDING THIS, BUT THUS FAR IT WORKED FOR ME.
I assumed BLINDLY that possibly Option 1 was either the simplest, first thought of, or maybe the best option (???). (At one point in my early frustrations (4 problems) I tried the "breaking option," but discarded it when it produced 10 new problems.
So, for you wonderful 'Linux helpers' thanks for taking the time to
consider my frustrations. - TIME WILL TELL WHEN I GET THE NEXT BATCH OF SUGGESTED UPGRADES how my 'Blind Option 1' choices worked.
Grateful Thanks,
Paul
Paul R Schmidtbleicher wrote:
On 7 May 2023 00:25:23 GMT, Paul R Schmidtbleicher wrote:
Have you tested your Audio and Video capabilities? If you have been switching packages from Packman, that is where problems are liable to
occur.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 63 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 492987:55:02 |
| Calls: | 840 |
| Files: | 1,302 |
| D/L today: |
4 files (5,837K bytes) |
| Messages: | 266,214 |