Bug 752428 - Traceback when updating
Summary: Traceback when updating
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-presto
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jonathan Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-09 13:34 UTC by Tom Atkinson
Modified: 2015-01-12 11:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-12 11:32:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tom Atkinson 2011-11-09 13:34:39 UTC
Description of problem:

I get the following backtrace when attempting to update:

Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 309, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 223, in main
    return_code = base.doTransaction()
  File "/usr/share/yum-cli/cli.py", line 526, in doTransaction
    problems = self.downloadPkgs(downloadpkgs, callback_total=self.download_callback_total_cb) 
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1951, in downloadPkgs
    self.plugins.run('predownload', pkglist=pkglist)
  File "/usr/lib/python2.7/site-packages/yum/plugins.py", line 184, in run
    func(conduitcls(self, self.base, conf, **kwargs))
  File "/usr/lib/yum-plugins/presto.py", line 620, in predownload_hook
    enabled_repos = xpostreposetup_hook(conduit, repos, reposize)
  File "/usr/lib/yum-plugins/presto.py", line 558, in xpostreposetup_hook
    mdsize = int(active_repo.repoXML.getData("prestodelta").size)
TypeError: int() argument must be a string or a number, not 'NoneType'


Version-Release number of selected component (if applicable):
yum-3.4.3-5.fc16.noarch
yum-presto-0.7.1-1.fc16.noarch


Steps to Reproduce:
1. yum -y update
  

Additional info:
This is a private repo on CentOS5. Works normally with F15 clients.

Appears to be related to this recent change: https://fedorahosted.org/presto/changeset/52537418cf675bf121e5476c64b9676c0120d6ca

Comment 1 Tom Atkinson 2011-11-10 10:23:52 UTC
OK, so I am using a version of createrepo that supports presto data but doesn't provide the size.

createrepo-0.9.7-4_13.el5

<data type="prestodelta">
  <checksum type="sha">c3eb493fca660508d157cd99bc1e1062a85d1bef</checksum>
  <timestamp>1320912850</timestamp>
  <open-checksum type="sha">f1d2c12a9d48839af0f6a2c1e79aaf22f0a8410c</open-checksum>
  <location href="repodata/c3eb493fca660508d157cd99bc1e1062a85d1bef-prestodelta.xml.gz"/>
</data>

Can we catch the exception properly to handle this case?

Comment 2 Stas Sergeev 2012-11-20 09:46:17 UTC
I am also having this with a 3-rd party repos under
Fedora-17.
yum-presto-0.7.3-1.fc17.noarch

Comment 3 Jonathan Dieter 2012-11-20 10:21:14 UTC
My apologies, I'd somehow let this slip off my plate.  Let me see what I can do with this.

Comment 4 Fedora End Of Life 2013-01-16 22:48:30 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-14 01:19:19 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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

Comment 6 Jonathan Dieter 2013-02-14 06:54:19 UTC
Reopening as this is still a valid bug.

Comment 7 Fedora End Of Life 2013-04-03 19:23:40 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 8 Fedora End Of Life 2015-01-09 21:53:50 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 9 Jonathan Dieter 2015-01-12 11:32:59 UTC
Ok, this was fixed at some point, but I forgot to close the bug.  Apologies.


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