Bug 1045090

Summary: [abrt] fedup: download.py:133:setup_repos:ValueError: need more than 1 value to unpack
Product: [Fedora] Fedora Reporter: Edgar Civil <ecivil>
Component: fedupAssignee: Will Woods <wwoods>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: tflink, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/616b1255e1e7eb99f48afed5ad0823a7a69788dd
Whiteboard: abrt_hash:33078ead799926a6fd6c0fba4d50a85dd70c3898
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-18 11:19:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description Edgar Civil 2013-12-19 15:11:34 UTC
Version-Release number of selected component:
fedup-0.7.3-4.fc19

Additional info:
reporter:       libreport-2.1.10
cmdline:        /usr/bin/python /usr/bin/fedup --network 20 --repo fedora-release
executable:     /usr/bin/fedup
kernel:         3.11.10-200.fc19.x86_64
runlevel:       N 5
type:           Python
uid:            0

Truncated backtrace:
download.py:133:setup_repos:ValueError: need more than 1 value to unpack

Traceback (most recent call last):
  File "/usr/bin/fedup", line 181, in <module>
    main(args)
  File "/usr/bin/fedup", line 93, in main
    repos=args.repos)
  File "/usr/bin/fedup", line 48, in setup_downloader
    repos=repos)
  File "/usr/lib/python2.7/site-packages/fedup/download.py", line 133, in setup_repos
    (repoid, url) = repo.split('=',1)
ValueError: need more than 1 value to unpack

Local variables in innermost frame:
mirrorurl: 'https://mirrors.fedoraproject.org/metalink?repo=fedora-install-$releasever&arch=$basearch'
repos: [('add', 'fedora-release'), ('add', 'default-installrepo=@https://mirrors.fedoraproject.org/metalink?repo=fedora-install-$releasever&arch=$basearch')]
progressbar: <fedup.textoutput.RepoProgress instance at 0x1669c68>
repo: 'fedora-release'
callback: <fedup.textoutput.RepoCallback object at 0x1663810>
action: 'add'
self: <fedup.download.FedupDownloader object at 0x1663fd0>

Comment 1 Edgar Civil 2013-12-19 15:11:38 UTC
Created attachment 839022 [details]
File: backtrace

Comment 2 Edgar Civil 2013-12-19 15:11:41 UTC
Created attachment 839023 [details]
File: environ

Comment 3 Will Woods 2014-01-23 20:59:26 UTC
Not sure what you were trying to do with the '--repo' argument here.
Perhaps you meant --instrepo, or --addrepo? See 'fedup --help' for info.

Either way, this traceback should be fixed by this commit:

  https://github.com/wgwoods/fedup/commit/471b7c7

This should be fixed in the next fedup release.

Comment 4 Fedora Update System 2014-06-04 16:47:34 UTC
fedup-0.8.1-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/fedup-0.8.1-1.fc19

Comment 5 Fedora Update System 2014-06-04 16:49:00 UTC
fedup-0.8.1-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/fedup-0.8.1-1.fc20

Comment 6 Fedora Update System 2014-06-05 04:23:36 UTC
Package fedup-0.8.1-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fedup-0.8.1-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-7085/fedup-0.8.1-1.fc19
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2014-08-15 02:43:35 UTC
fedup-0.8.1-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2014-10-29 21:12:46 UTC
fedup-0.9.0-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/fedup-0.9.0-1.fc19

Comment 9 Fedora Update System 2014-11-03 18:05:37 UTC
fedup-0.9.0-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/fedup-0.9.0-2.fc19

Comment 10 Fedora Update System 2014-11-05 03:57:32 UTC
fedup-0.9.0-2.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora End Of Life 2015-01-09 22:40:48 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 12 Fedora End Of Life 2015-02-18 11:19:24 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.