Bug 436821 - Install problem: Missing XML/LibXML/SAX/Parser.pm
Summary: Install problem: Missing XML/LibXML/SAX/Parser.pm
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-XML-SAX
Version: rawhide
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Stepan Kasal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-10 17:30 UTC by Horst H. von Brand
Modified: 2008-03-27 08:07 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-03-27 08:07:04 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Error message on updating (1.39 KB, application/octet-stream)
2008-03-10 17:30 UTC, Horst H. von Brand 		no flags Details
View All

Description Horst H. von Brand 2008-03-10 17:30:44 UTC 
Description of problem:
Updating to today's rawhide I got the attached error message. The package checks
out clean (rpm -V).

Version-Release number of selected component (if applicable):
perl-XML-SAX-0.16-5.fc9.noarch

How reproducible:
Only on upgrading, installing the package again gives no messages.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Horst H. von Brand 2008-03-10 17:30:44 UTC 
Created attachment 297471 [details]
Error message on updating
Comment 2 Marcela Mašláňová 2008-03-21 10:02:18 UTC 
I can't reproduce it. I updated it from perl-XML-SAX-0.16-4.fc9.noarch to
perl-XML-SAX-0.16-5.fc9.noarch and nothing had happened.

Do you from which version did you update?
Comment 3 Horst H. von Brand 2008-03-27 00:03:20 UTC 
Nope, no record of the earlier perl-XML-SAX in /var/log/yum.log*

In any case, I have updated this machine daily most of the time. Unless
something blocked its update, it must have been the latest version before that.

Sorry not to be able to help more.
Comment 4 Marcela Mašláňová 2008-03-27 08:07:04 UTC 
I'm sorry, but I can't reproduce it. I've already checked the spec file, but
everything looks fine.
Note You need to log in before you can comment on or make changes to this bug.