|
Bugzilla – Full Text Bug Listing |
| Summary: | Spurious error about outdated zypp patch | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Michal Svec <msvec> |
| Component: | YaST2 | Assignee: | Stefan Schubert <schubi> |
| Status: | RESOLVED FIXED | QA Contact: | Stanislav Visnovsky <visnov> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aj, andreas.hanke, ast, dmacvicar, forgotten_mbQyAD5r4K, hmuelle, mvidner, suse-beta |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
screenshot
screenshot relevant y2logs zyppdb y2logs fill full zypp debug output you screenshot |
||
|
Description
Michal Svec
2006-06-20 13:08:58 UTC
Created attachment 90603 [details]
screenshot
Created attachment 90604 [details]
screenshot
Created attachment 90607 [details]
relevant y2logs
Created attachment 90608 [details]
zyppdb
The second screenshot (attachment #90604 [details]) is from someone else, just for illustration it also happens itw. Logs and zyppdb are relevant to the first screenshot.
The problem is that the current "big patch" is called libzypp and the earlier ones were called zypp. We should release a newer big libzypp patch that obsoletes (automatically) the older libzypp and (explicitly) the even older zypp patches. Michal L, I believe this is the same problem that you reported to maso on Jun 11. (to test, extract /var/lib/zypp/db/patches/df12dc65c0bc455fbd3d0ddd95a8fe22 from comment 4) Fixed How is this supposed to be fixed? I still experience the problem (comment #2). I can see the "libzypp update" in my list of patches for installation in YOU, but I still get this error (I haven't run the update though). Harald, the patches on the update servers do not contain any information about obsoleting the old patch. Stano, could you provide a snippet how to obsolete a patch in our zypp-metadata? Jiri, please, help here. You can specify it exactly the same way as in case of packages: <rpm:obsoletes> <rpm:entry kind="patch" name="patch-xxx-1234"/> </rpm:obsoletes> I'm just not sure about the rpm: prefix... BTW this should be done for both of the above reported patches ... Still the same.
I can confirm there is now obsoletes in the downloaded patch:
<rpm:obsoletes>
<rpm:entry kind="patch" name="patch-zypp-1310"/>
</rpm:obsoletes>
But it doesn't change the behavior, I still get that error.
BTW that error refers to patch:zypp-1310-0.noarch if that matters.
I am willing to fix the internal test-repo again, but someone of the developers has to tell me what needs to go into the patch. Michal could you try again? I changed the obsoletes on my own, some trial and error:
<rpm:obsoletes>
<rpm:entry kind="patch" name="patch-zypp epoch="0" ver="1310" rel="0" flags="EQ""/>
</rpm:obsoletes>
I expect obosoletes should have the same "scheme" as requires if versions are used. It is completely untested.
Jiri, does it look correct to you?
No, it does not, quoting int the rpm:entry tag is incorrect. Correct should be <rpm:entry kind="patch" name="patch-zypp" epoch="0" ver="1310" rel="0" flags="EQ"/> If it still doesn't work, let's have a look at the parser's and solver's logs... Still the same. I don't know who is the best contact for providing the correct "obsoletion" snippet. Jiri, could you investigate and provide the snippet or reassign the bug to the best suited person? Please try again Michal, I missed comment#21 and fixed the type Jiri found. Sorry for inconvenience. Created attachment 96850 [details]
y2logs fill full zypp debug output
According to Stano Schubi could know more ... I have not looked in the logfiles, but Harald you are obsoleting patch "patch-zypp". The screenshot of comment means the patch with the name "zypp". So please take the correct name. This is what I have in the patch-libzypp-1839.xml:
<rpm:obsoletes>
<rpm:entry kind="patch" name="zypp" epoch="0" ver="1310" rel="0" flags="EQ"/>
</rpm:obsoletes>
However, I still get the same error.
And now I need the logfiles again;-): Could you please start export ZYPP_FULLLOG=1; yast2 online_udpate in a xterm and reproduce the error ? Please attach the logfiles /var/log/YaST2/* ( at least /var/log/YaST2/y2log ) Thanks Seems to be OK now, strange :-) Will check again next week. Created attachment 97619 [details]
you screenshot
I do not have that error any more. The patch seems to be selected for removal (see the screenshot), if that's an intended behavior.
A patch will be obsoleted by another. Thats OK. Do you see the deleted patch again after you commit and restart YOU ? I could see twice libzypp update (and some other remnants, but not the patch to be deleted neither the error message. So this seems to be fixed. OK, thank you for your help Michael. Duncan, it works;-) |