[opensuse-support] huge zypperdup backlog
My laptop crashed almost two months ago and I just got it up again. 'zypper dup' produces over 7000 files to update ending in a long list of file conflicts, if I abort all the download time was a waste but if I press on I get an unbootable system. What can I do WITHOUT reinstalling? -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* ksusup@trixtar.org <ksusup@trixtar.org> [08-29-20 17:26]:
My laptop crashed almost two months ago and I just got it up again. 'zypper dup' produces over 7000 files to update ending in a long list of file conflicts, if I abort all the download time was a waste but if I press on I get an unbootable system. What can I do WITHOUT reinstalling?
got it up to what? long list of "file conflicts" ?? press on "I" ?? what system are you running? are you on the left or right side of the street in front of your house? the sun is in front or back? Please have a good day. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Sat, 29 Aug 2020 17:34:33 -0400 Patrick Shanahan <paka@opensuse.org> wrote:
try these: got it up and running long, like maybe more than 10 press on, as in continue running tw which is the ONE where it is advised to use zypper dup and not yast (last I heard) the street for mortals is behind my house and if I come from one direction then my drive/runway is on my left, else on my right in the summer the sun rises in the left-front (northeast) quadrant, flies around to the right to set in the left rear (northwest) quadrant cognitive issues? how many fingers do you see? ~~^~~
Please have a good day.
no problemo, pilgrim -- If DIY were a religion, hmmmm... I just made it one -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* ksusup@trixtar.org <ksusup@trixtar.org> [08-29-20 19:32]:
depends on where I look.
ah John Wayne but little to help you with your 'dup' problems. I believe I will take a shower. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 29/08/2020 23.20, ksusup@trixtar.org wrote:
My laptop crashed almost two months ago and I just got it up again. 'zypper dup' produces over 7000 files to update ending in a long list of file conflicts, if I abort all the download time was a waste but if I press on I get an unbootable system. What can I do WITHOUT reinstalling?
What is the current situation? Did you complete the "zypper dup"? What exactly means "unbootable", what messages do you get? -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On Sun, 30 Aug 2020 03:40:49 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
It's working fine, being a reversion to an image created with dd before the laptop died, I've recovered it with dd 3 times since.
Did you complete the "zypper dup"?
The first time I chickened out, that IS the advised wisdom, to NOT continue with file conflict warnings. Then I completed it once just to see what would come loose or blow up. That's when I got the huge conflicting files thingie, didn't even read it, just went for it.
What exactly means "unbootable", what messages do you get?
Don't remember, didn't get to that graphical login and 'systemctl isolate graphical.target' didn't do it either, no response to a kdm command, the gdm command went in but just locked the terminal up too. So I dd'd back the image again. Then I did an update with Yast knowing that it's a ffederal crime but only for packages that had kernel in them, same result. dd back the backup immage again. Since then I've updated just some mozilla stuff withg Yast to see how their incompatible-profiles disgrace would pan out, and then copied over the relevant folders from my up-to-date-desktop, no problems so far. I re-tried the command just to see if I had typoed something (after a smartass remark on the list) but the command was good and it even coughed up a signature or checksum warning so it got a Cntl-C. The laptop also had a Leap-15.1 in it, won't even bother with that one, life's too precious :) For what it's worth, couldn't the file conflict test be run BEFORE the huge downloads? I mean that DL took like 3 hours and there's no way I'm going to repeat it unless I know it's going to work, which is why I posted actually. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 30/08/2020 04.34, ksusup@trixtar.org wrote:
Ah, so you updated then reverted using the backup.
Then it did boot fine. It failed to initialize the graphic mode. Different thing.
no response to a kdm command, the gdm command went in but just locked the terminal up too. So I dd'd back the image again. Then I did an update with Yast knowing that it's a ffederal crime but only for packages that had kernel in them, same result. dd back the backup immage again. Since then I've updated just some mozilla stuff withg Yast to see how their incompatible-profiles disgrace would pan out, and then copied over the relevant folders from my up-to-date-desktop, no problems so far. I re-tried the command just to see if I had typoed something (after a smartass remark on the list) but the command was good and it even coughed up a signature or checksum warning so it got a Cntl-C. The laptop also had a Leap-15.1 in it, won't even bother with that one, life's too precious :)
For what it's worth, couldn't the file conflict test be run BEFORE the huge downloads? I mean that DL took like 3 hours and there's no way I'm going to repeat it unless I know it's going to work, which is why I posted actually.
Apparently not. But the downloaded packages should still be there, I don't see why download them again, unless you delay and they change again. The only way to help is that you post the file conflict - mind, a file conflict, not a package conflict. And if then you go ahead and it fails, you have to post the error messages. Before doing that, you could do: zypper lr --details > somefile.txt and then attach that somefile.txt to your reply here. Do not paste it in the email, just attach the file. Different thing. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On Sun, 30 Aug 2020 12:35:05 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
yes, the idea being to have a working system, whatever the method, whoever the sacrifice :)
not after three reversions from backup but I'll try that next time i.e. see if an 'outside' folder specified in yast to save and keep dl'd files also works with zypper.
yeh, I know, I keep thinking this is usenet -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 30/08/2020 13.22, ksusup@trixtar.org wrote:
Right.
Ah, the restore, I forgot. The downloaded packages would be in /var/cache/zypp/packages. You can place that on another partition (symlink) or disk.
No, I say attach because the lines will be long and I do not want them to wrap, which makes reading them very difficult. You can also do: zypper lr --details | susepaste -n "My Name" -t "repo lst" -e 40320 and paste here the link it produces. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Am 29.08.20 um 23:20 schrieb ksusup@trixtar.org:
My laptop crashed almost two months ago and I just got it up again. 'zypper dup' produces over 7000 files to update ending in a long list of file conflicts, if I abort all the download time was a waste but if I press on I get an unbootable system. What can I do WITHOUT reinstalling?
file conflicts are normally only if you have enabled other repos (as example home repos) as carlos wrote, are you sure "file conflicts" or "package" conflict (missing dependencies)? i suggest: before zypper dup, check what repos you have enabled. maybe disable some, and or post here. also before dup, make a "rpmconfigcheck" even if you have not done ever before. and check/merge all the config files (ore use the new one). if all config files are now ok and rpmconfigcheck will give no output any more, check if system still reboot. check if all is running well. now start with dup, check the PACKAGE conflicts exactly, i write them normally on a second computer or paper down (if its are not to much, if to much, use the log file) and later on with yast will take manually care oft it. if FILE conflicts you have to chose what package is more important (or remove the package who did the conflict. MOST important, AFTER dup finished, BEFORE reboot make again "rpmconfigcheck" and check/merge all the config files (ore use the new one). it depends when your last update was, during this year the /etc/nsswitch.conf file has changed and this has lead into a system not booting into graphical enviorement. simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 30/08/2020 14.51, Simon Becherer wrote:
Am 29.08.20 um 23:20 schrieb ksusup@trixtar.org:
...
MOST important, AFTER dup finished, BEFORE reboot make again "rpmconfigcheck" and check/merge all the config files (ore use the new one).
I use "meld oldconfig newconfigfiles". Of course, I have to install meld in advance.
Right. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On Sun, 30 Aug 2020 14:51:07 +0200 Simon Becherer <simon@becherer.de> wrote:
It's NOT dependencies, those are handled BEFORE the downloads. For example there might be a conflict with some package part/product originating in a packman package that is different from one originating in a distro package. The thing is that at this point zypper leaves me only two options i.e. to continue or to abort.
i suggest: before zypper dup, check what repos you have enabled. maybe disable some, and or post here.
this is easy enough, here are the repos currently enabled in yast (in addition to packman being designated to restrict applicable packages to that repo). http://download.opensuse.org/tumbleweed/repo/non-oss/ http://download.opensuse.org/tumbleweed/repo/oss/ http://download.opensuse.org/update/tumbleweed/ http://packman.inode.at/suse/openSUSE_Tumbleweed/ https://download.nvidia.com/opensuse/tumbleweed
now start with dup,
i'll try another run later today, I can maybe copy out any conflict list
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Am 30.08.20 um 16:12 schrieb ksusup@trixtar.org:
It's NOT dependencies, those are handled BEFORE the downloads. For example there might be a conflict with some package part/product originating in a packman package that is different from one originating in a distro package. The thing is that at this point zypper leaves me only two options i.e. to continue or to abort.
ok. now we understand. so we need the list of files / packages with that conflicting files.
this look good. but if you get a system without graphic because of nvidia, i am out here... throwing away my nvidia card loooooong time in past.......
i'll try another run later today, I can maybe copy out any conflict list
have you done the rpmconfigcheck ????????? -> to make sure the problem is not from this point. simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Am 30.08.20 um 17:35 schrieb ksusup@trixtar.org:
mh.... 1) .rpmsave is older than the original you where using, so do NOT use the rpmsave. instead delet them or move them to a other directory. 2) nsswitch.conf you could (as far as i know) using the rpm new -> copy the .conf to a save place and rename the rpm.new to .rpm (and this is the file who may have destroyed the boot of your system, renaming it should solve this problem (-> do not forget to do this also AFTER dup) 3) for all the other .rpmnew YOU have to compare it with the original. i use midnight commander (mc) for this - but there are many (and maybe better) programms for this. you need one of the programms who has 2 panels and highlight what is different in the files. then you must chose what is correct for your system. that is not always trivial, i know. postfix will (i think) fail if you only rename and use the new file. (there are specific setup data for your system inside. but do not fear, a lot of times only in comment lines are changes.) so a good help is to look inside the files and if you see some things like your hostname or some other know specifig data for your system, then you could not only use the new one. ... by the way, i have NOT done this for my tumbleweed systems about 2 years and most whas fine. now i recogniced if i do this every time i make a dup, you have only a couple of files, and from this couple of files most are easy to find out what is good.
here i could not help. but this should be corrected, if the driver is to old, it will not work with new kernel after update.
then # zypper dup ..and the download has started.
one of the problems is that at this point I'm already more involved than I want to or am qualified be (whatwith handling the rpmconfigcheck results).
i am sorry, this is live... posibility 1) do not use tumbleweed. use leap posibility 2) learn a little bit to let it moving. - i am also only a user and until the beginning of this year i have never made a rpmconfigcheck. -> but using suse/opensuse since suse 9.2
simoN www.becherer.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Sun, 30 Aug 2020 18:28:00 +0200 Simon Becherer <simon@becherer.de> wrote:
it's now up to 2500/7826 file downloads, initially it was supposed tobe 7100 or so 'I'll be back' when it gets to show 'conflicts' -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 30/08/2020 18.28, Simon Becherer wrote:
I assume ksusup@ sent you Simon the reply off-list, because I do not see it.
That alone could explain why the system did boot but failed to start graphic mode.
This is unreadable.
since I have no idea what to do about these i renamed them all including the entire texmf folder, no more rpmconfig returns :)
Well, this a dangerous move. It is important to handle properly each an everyone of the lines resulting from rpmconfigcheck. If you (ksusup@) don't know what to do, do nothing. Now you (ksusup@) probably have a texmf breakage as well, and I would recommend installing it again.
What I do is copy both the file in service and the *rpm* file to a backup directory. There can not be several "*rpm*" files of the same config file. If there are, it means the admin (you, (ksusup@)) neglected to do you job long ago. Then I do, for example: meld /etc/postfix/master.cf.rpmnew /etc/postfix/master.cf & which opens a double panel editor that compares the proposed new file with the active file. What I do is copy from rpmnew to active the new entries that *I consider* should be there, and remove from the active file the lines that *I consider* should not be there. I, the admin, have to do the decisions. This is the job of the admin, and it is not trivial, but it is important. Finally, I would delete /etc/postfix/master.cf.rpmnew (remember I keep a backup). In the case of an .rpmsave it means that the update made use directly of the new file, and renamed your original (ksusup@) copy. If you never altered that confinguration, the thing to do is trivial: just delete the .rpmsave file. If you did some change, well, reactivate those with meld. (ksusup@), you panicked too fast with .exmf
I would abort at this moment and run "zypper ref --force". If you get the same message with the zypper dup, do a "zypper clean", refresh and try again. If the error keeps, stop, and try another day. And ask here. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On Sun, 30 Aug 2020 18:28:00 +0200 Simon Becherer <simon@becherer.de> wrote:
I don't have a choice it's the onboard video, and I haven't had that much trouble with nvidia, have their aftermarket card on my desktop. The only reason I really need it is to run google-earth which wouldn't work without it the last time I noticed
well, I'll be... zypper dup got to the end of the giga download, I expected the same giga-yards long conflicting files list ...but no, nothing, it just took off and started installing right away after the downloads, i'll see if it boots. Meanwhile rpmconfigcheck which returned nothing just before running zypper now returns a new list of files /etc/chrony.conf.rpmnew /etc/fonts/conf.d/30-metric-aliases.conf.rpmsave /etc/localtime.rpmnew /etc/postfix/master.cf.rpmnew /etc/sane.d/dll.conf.rpmnew /etc/sudoers.rpmnew -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Sun, 30 Aug 2020 19:30:05 -0400 ksusup@trixtar.org wrote:
Everything went fine, but no graphic login. During the zypoper run when the caution came up about the checksums the nvidia repo got dumped. That could be a factor, I'll be off the laptop until tomorrow. When I get back on it it'll be in runlevel 3 and no internet. I might meanwhile download the latest dvd and then update the laptop using it, maybe I should have done that in the first place. systemctl isolate graphic.target operation refused... systemctl status graphic.target graphic.target could not be found -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 31/08/2020 02.34, ksusup wrote:
On Sun, 30 Aug 2020 19:30:05 -0400 ksusup@trixtar.org wrote:
That the proprietary Nvidia driver doesn't load after an update is "expected" and you must learn to deal with it on your own. There was a warning about it somewhere in the description of Tumbleweed somewhere. Reinstallation from DVD may or may not solve it. So, issues. No internet, why? Are you using network manager? If that is so, there are text mode utilities to use network manager. Many nmcli or nmtui. Test graphics mode. Use "startx" in one of the consoles. It may say something about permissions, but it tells you in the message what file to edit to get permissions (/etc/permissions.local). When you get past this error, then it will print the actual error with the graphics. On another post I posted material to read. Your quicker bet would be to remmove the proprietary driver and revert to the nouveau or open driver, and later reset the proprietary repository if you want. I don't have an nvidia card on this computer, so I can't look what exactly to do. Basically uninstall the nvidia rpm, and then perhaps remove the xorgconfigsomething file if it is still there, and reboot. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
dead thread, I just plugged-in a 250gb samsung dssi into this laptop and am installing Slackware, Debian, Leap-15.2 and TW on it. The formwer disk-1 is now reformatted disk-2 data thanks for the help -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 30/08/2020 16.12, ksusup@trixtar.org wrote:
On Sun, 30 Aug 2020 14:51:07 +0200 Simon Becherer <simon@becherer.de> wrote:
...
Nonono. I told you to run certain command and attach or susepaste the result. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On Sun, 30 Aug 2020 20:50:45 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
yes, yes, I forgot 'zypper lr --details > somefile.txt' there are too many chiefs here and only one indian :) the download is just completing, the nvidia repo got auto axed for some techincal problem
On 30/08/2020 21.43, ksusup@trixtar.org wrote:
:-) Ok, I don't see any problem with your repos, plain enough. You might want to lower the priority number of the packman repo somewhat, to 80, say.
the download is just completing, the nvidia repo got auto axed for some techincal problem
Well, graphical mode may fail when it finishes. You have to options: to remove completely the nvidia proprietary driver and go for nouveau, or install the proprietary driver again. Like others, I got tired of nvidia and installed an ATI card instead. <https://en.opensuse.org/SDB:NVIDIA> -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 29/08/2020 23.20, ksusup@trixtar.org wrote:
My laptop crashed almost two months ago and I just got it up again. 'zypper dup' produces over 7000 files to update ending in a long list of file conflicts, if I abort all the download time was a waste but if I press on I get an unbootable system. What can I do WITHOUT reinstalling?
May I suggest you redefine your name in the mail program something like: "some name" <somemail@domain.some> ? The "some name" doesn't have to be your real name, just how you prefer we address you. That way, when we reply to you the first line will contain your assumed name, not your mail address. And it will display that way in the mail list web archive. At least, in most cases. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
participants (5)
-
Carlos E. R.
-
ksusup
-
ksusup@trixtar.org
-
Patrick Shanahan
-
Simon Becherer