|
Bugzilla – Full Text Bug Listing |
| Summary: | yast package manager does not show correct package versions (log redirects) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Trango Towers <trango> |
| Component: | YaST2 | Assignee: | Jan Kupec <jkupec> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | casualprogrammer, mvidner |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Trango Towers
2007-01-27 16:00:20 UTC
BTW... I get very often the problem indicated in bug239372. Is there a conncection between these 2 bugs ? What versions? What dialog? What part of that dialog? Did you check the "Versions" tab what versions are installed, elected as candidate (that will be installed if you set that package to update or install)? What connection do you see to bug #239372? I have reproduced the problem. It is outdated metadata, which seems to be the same problem like in bug 238095. This is nasty, getting such problems as bugs. Christoph, can we come up with something better? Jano, perhaps we should log the redirects (302 Moved Temporarily) so that we can better diagnose such problems and pinpoint the outdated server. Martin, I think, looking redirects on the user-side makes a lot of sense, to be able to better debug those kind of problems. In addition to that, we already log redirectos on our side. We are currently working hard improving the overall situation. One solution might be to not redirect requests for metadata files. Jano, try to log the redirects please. Marius, i see curl_easy_perform() doesn't tell anything about redirects, it only reports errors. Do you know of a way how to detect a redirect within MediaCurl without making major changes to the code? If not, i'll investigate deeper. AFAIK there is no option it in curl to log redirects only except of export ZYPP_MEDIA_CURL_DEBUG=1 (or 2) enabling curl (header) logging in general. The only possibility would IMO be to disable following in curl and to follow them manually. Then perhaps we do not need to modify code and it is just enough to document the debugging variables such as ZYPP_MEDIA_CURL_DEBUG at http://en.opensuse.org/Debugging_YaST. Done. closed by accident Martin, how do these redirects work? I mean how is the target location chosen? If there's no guarantee that the redirects will lead into a synced source, then we should indeed just disable them. That is a question for the maintainers of software.opensuse.org. According to bug 238095 comment 11 they are already disabled for metadata. So if adding logging would mean much work or risk introducing new bugs then I think that we do not need to log the redirects after all. At least until we get a new splash of bug reports :) *** Bug 251275 has been marked as a duplicate of this bug. *** Logging redirects is not an option here - we can't dig in the logs each time we get bugs like these just to close them with a "this is because redirects to mirrors that are not in sync" comment. *** This bug has been marked as a duplicate of bug 238095 *** |