|
Bugzilla – Full Text Bug Listing |
| Summary: | opensuse updater doesn't install a patch | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Marco Pallotta <pallotta> |
| Component: | libzypp | Assignee: | Jan Kupec <jkupec> |
| Status: | RESOLVED INVALID | QA Contact: | Duncan Mac-Vicar <dmacvicar> |
| Severity: | Minor | ||
| Priority: | P4 - Low | CC: | barrybham, bmiller, pallotta, pekka.korolainen, signups, thomas9999, ulrich.reeg |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
zypper log written during the "update"
Zypper.log |
||
|
Description
Marco Pallotta
2007-11-26 12:59:45 UTC
Created attachment 184715 [details]
zypper log written during the "update"
I had the same problem. After running zypper in the commandline to try and get some update logs, the problem went away. Zypper told me it was going to downgrade amarok though! *** Bug 344685 has been marked as a duplicate of this bug. *** Obviously zypper doesn't install selected patches in the interactive mode without showing an error message. Jano, can you help? I have the same problem, I've tried to disable the update repository, check for new updates and after that I've enabled the repository again, this work but when I reboot I have the same problem (sigh), the problem however is with amarok patch 4492-0. (In reply to comment #4 from Thomas Goettlicher) > Obviously zypper doesn't install selected patches in the interactive mode > without showing an error message. Jano, can you help? The only case where zypper refused to install selected patches i saw was when it stated that the patch 'is already installed' (e.g. a broken patch). But we already use the --force in the updaters, right? Marco (or Marco :O) Can you please attach zypper.log (once again) if you still have the problem? The above attachment is gone. Also, are you sure you always get _the same_ patch? Isn't it a different version each time? Thanx. I have this problem no more because I reinstalled the O.S. (obviously for other reason than this problem :-)) So I have no more zypper.log. Tomas Richard or Marco Stornelli can you upload your zypper.log (you said us that you have the same problem)? Created attachment 187137 [details]
Zypper.log
I have installed my openSuse two times. The first time without online update and everything worked fine. Two weeks ago (for other problem) I have installed the distribution again but this time with online update during the installation phase, now I have this problem :(, somebody can confirm it? I hope this information can be worth. Marco, I cannot confirm it. My installations were always made without online update during install phase. Thanx Marco(s) :O) Unfortunately it will probably have to wait until January, as i leave for a vacation now. In the meantime, please try also to use the --force (zypper install --force -t patch <patchname>) as suggested in Comment #6 and see if you can get rid of the patch then. See you in January! I tried the zypper command (zypper install --force -t patch amarok). It seems that zypper install the patch because I run the command again zypper tell me something like: "Do you want to remove the patch?". The updater however doesn't work and after a "check now" command, the zypper tell me again if I want install the patch. It seems that when I run the updater it clears some information. Ok, see you in January! Hello, I still have this same problem, has there been any advances in figuring out the problem? I did zypper install --force -t patch amarok twice, once without suse-updater running and other time with it running. First time zypper wanted said it'll install a NEW patch, second time it was going to DELETE a patch. Anyhoo, this didn't change anything. suse-updater still wants to update it to 4492-0. (In reply to comment #7 from Marco Pallotta) > I have this problem no more because I reinstalled the O.S. (obviously for other > reason than this problem :-)) So I have no more zypper.log. > Tomas Richard or Marco Stornelli can you upload your zypper.log (you said us > that you have the same problem)? > Hello, as stated in my second reply, i got rid of the problem with running zypper in the commandline to get some kind of logging. I'm not that experienced with linux yet so.. The only thing i did was running zypper without any parameters (after alot of tries with the gui). It told me it was going to downgrade amarok, zypper continued and after the problem was gone and i didn't get any notices anymore. (In reply to comment #14 from Thomas Richard) > (In reply to comment #7 from Marco Pallotta) > > I have this problem no more because I reinstalled the O.S. (obviously for other > > reason than this problem :-)) So I have no more zypper.log. > > Tomas Richard or Marco Stornelli can you upload your zypper.log (you said us > > that you have the same problem)? > > > > Hello, > > as stated in my second reply, i got rid of the problem with running zypper in > the commandline to get some kind of logging. I'm not that experienced with > linux yet so.. > The only thing i did was running zypper without any parameters (after alot of > tries with the gui). It told me it was going to downgrade amarok, zypper > continued and after the problem was gone and i didn't get any notices anymore. > Hi Thomas, perhaps you are right! Yesterday I ran zypper some times with some parameters (patch-check, patch-info..) and this morning (when I turn on my pc) everything works fine! I wonder why this problem happens. The happiness is gone....today the updater tell me that there are new updates and there is also the amarok patch 4492-0 (!!) and now I have again the same problem (sigh). (In reply to comment #14 from Thomas Richard) > (In reply to comment #7 from Marco Pallotta) > > I have this problem no more because I reinstalled the O.S. (obviously for other > > reason than this problem :-)) So I have no more zypper.log. > > Tomas Richard or Marco Stornelli can you upload your zypper.log (you said us > > that you have the same problem)? > > > > Hello, > > as stated in my second reply, i got rid of the problem with running zypper in > the commandline to get some kind of logging. I'm not that experienced with > linux yet so.. > The only thing i did was running zypper without any parameters (after alot of > tries with the gui). It told me it was going to downgrade amarok, zypper > continued and after the problem was gone and i didn't get any notices anymore. > Hello Thomas, could you please write me the exact command that you typed in? (zypper......) thanks Ulrich (In reply to comment #17 from Ulrich Reeg) > Hello Thomas, > > could you please write me the exact command that you typed in? (zypper......) > > thanks > Ulrich > Hey Ulrich, I just ran: sudo zypper without any paramaters. I got lucky and the problem disappeared. Never seen it again and i can't seem to reproduce it. Greetings Thomas Hello to all, think I got rid of the problem. Doesn't seem to be a real "bug", but just a mistake in setting up the system. I had got more problems. Another update failed (python...) and an alert appeared that something with a repository "openSUSE/Education:/..." (or so) was wrong. I know very little about SuSe Linux, but I tried to find out which repositories are listed in my system. So I ran yast and found that only one (main oss) was marked. That seemed wrong and I then put ticks against all listed repositories that seemed to be useful. After the next update routine I had a green SuSE-logo in the controll-bar and it now says "Keine Aktualisierungen verfügbar" (no updates avvailable) Hope the thing will not return! Ulrich Hi Gentlemen, I am having the same problem. It is nothing but a minor annoyance at this time. I have read through this thread and have tried all the resolvables(zypper, repo selection) and so on. I do continue to get the amarok update patch 4492-0 error as above. I even did the voodoo dance last night and it _still_ won't go away! I did scrape the logs and found no specific errors related to this message. I'm all ears... Thanks! bm *** Bug 359607 has been marked as a duplicate of this bug. *** Comments #12 and #13 suggest that the problem was/is in the metadata of the amarok patches for openSUSE 10.3 and/or conflicts with data from other repositories. Nevertheless, it is now irrelevant as the dependency resolver changed a lot for 11.0, so i'm closing this bug now. Please open a new report if something similar happens in 11.0, thanx! |