Bug 1259654

Summary: fedpkg update fails
Product: [Fedora] Fedora EPEL Reporter: Dave Love <dave.love>
Component: bodhiAssignee: Luke Macken <lmacken>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: el6CC: lmacken, pfrields, rbean
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-02 23:23:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
fix for el6 none

Description Dave Love 2015-09-03 09:42:05 UTC
Description of problem:

"fedpkg update" fails with the following, which doesn't look the same as any
other reports.  I seem to have the latest available packages.  I don't know if this is actually a python-fedora problem -- reporting against the command that failed.

$ fedpkg update
/usr/lib/python2.6/site-packages/fedpkg/cli.py:169: DeprecationWarning: Commands._hash_file is deprecated and will be removed eventually.
    Please use Commands.lookasidecache.hash_file instead.
  hash = self.cmd._hash_file('bodhi.template', 'sha1')
Traceback (most recent call last):
  File "/usr/bin/bodhi", line 537, in <module>
    main()
  File "/usr/bin/bodhi", line 194, in main
    bodhi = BodhiClient(opts.bodhi_url, username=opts.username, debug=opts.verbose)
  File "/usr/lib/python2.6/site-packages/fedora/client/bodhi.py", line 85, in BodhiClient
    base_url = 'https://{}/'.format(urlparse(response.url).netloc)
ValueError: zero length field name in format
Could not generate update request: Command 'bodhi --new --release el6 --file bodhi.template scalasca-2.2.2-2.el6 --username loveshack' returned non-zero exit status 1

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

bodhi-client-0.9.13-2.el6.noarch
python-fedora-0.5.5-1.el6.noarch

Comment 1 Ralph Bean 2015-09-04 19:51:36 UTC
Sorry about this.  Just pushed a patch upstream:  https://github.com/fedora-infra/python-fedora/pull/141

Comment 2 Fedora Update System 2015-09-06 17:08:29 UTC
scalasca-2.2.2-2.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7965

Comment 3 Dave Love 2015-09-06 17:17:48 UTC
Created attachment 1070754 [details]
fix for el6

Thanks, but it still fails.  I managed a checkin after applying the attached patch too.

Comment 4 Dave Love 2015-09-06 17:25:08 UTC
Oops.  I obviously copied the wrong bug number into the trial update request.
That should have been under 1174290.

Comment 5 Fedora Update System 2015-09-06 17:50:42 UTC
python-fedora-0.5.6-1.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update python-fedora'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7936

Comment 6 Fedora Update System 2015-09-08 01:00:32 UTC
scalasca-2.2.2-2.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update scalasca'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7965

Comment 7 Kevin Kofler 2015-09-08 02:52:33 UTC
> Oops.  I obviously copied the wrong bug number into the trial update
> request. That should have been under 1174290.

Then you need to edit the update (in the Bodhi web interface) to fix it.

Comment 8 Fedora Update System 2015-10-02 23:23:24 UTC
python-fedora-0.5.6-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.