Bug 683489 - fedpkg build is giving xml.parsers.expat.ExpatError
Summary: fedpkg build is giving xml.parsers.expat.ExpatError
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-packager
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-09 14:56 UTC by Michal Fojtik
Modified: 2013-01-10 06:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-07 22:40:27 UTC
Type: ---


Attachments (Terms of Use)

Description Michal Fojtik 2011-03-09 14:56:05 UTC
Description of problem:

"fedpkg build" is giving me this output:


[mfojtik@patashnik f14]$ fedpkg build
Building rubygem-sinatra-1.2.0-1.fc14 for dist-f14-updates-candidate
Created task: 2897215
Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=2897215
Watching tasks (this may be safely interrupted)...
2897215 build (dist-f14-updates-candidate, /rubygem-sinatra:0e363f9ee66c609beac4c727982e946d27efda78): open (x86-18.phx2.fedoraproject.org)
  2897216 buildSRPMFromSCM (/rubygem-sinatra:0e363f9ee66c609beac4c727982e946d27efda78): open (x86-13.phx2.fedoraproject.org)
Could not watch build: <class 'xml.parsers.expat.ExpatError'>

Version-Release number of selected component (if applicable):

Name        : fedora-packager
Arch        : noarch
Version     : 0.5.5.0
Release     : 2.fc14
Size        : 69 k
Repo        : installed
From repo   : updates
Summary     : Tools for setting up a fedora maintainer environment
URL         : https://fedorahosted.org/fedora-packager
License     : GPLv2+
Description : Set of utilities useful for a fedora packager in setting up their
            : environment.

How reproducible:

Do a 'fedpkg build'

Comment 1 Jesse Keating 2011-03-21 18:14:42 UTC
That's something coming from koji, a hiccup in the koji network perhaps.

Can you repeat this?

fedpkg did the right thing, it caught the error and gave it to the user as opposed to just doing a traceback.  Not sure what more we can do here.


Note You need to log in before you can comment on or make changes to this bug.