Bug 393371
Summary: | yum-security generates Python traceback while updating tetex | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andre Robatino <robatino> |
Component: | yum-utils | Assignee: | Seth Vidal <skvidal> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | pmatilai, tim.lauridsen |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 3.2.8-2 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-03-11 12:45:29 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andre Robatino
2007-11-20 22:42:10 UTC
what version of yum are you using here? yum-3.2.7-1.fc8 I was fully updated before the latest batch of updates which didn't include yum, so it was the same version when running "yum --security update". is this still happening or reproducible on yum 3.2.8 in f8? Note that I'm using presto, which I later found doesn't provide the security metadata, so I stopped trying to use --security after that, so don't know. But it's possible that my problem was due to some kind of bad interaction with presto. okay, I'm going to to close this bug for now. If you find out that's not true, re-open this bug or open a new one. thanks |