Hi Using the current yum in Fedora 17 (yum-3.4.3-28.fc17.noarch) i see some unwanted progress information when using the yum API with a custom download progress handler.
Steps to reproduce. $sudo yum clean all $sudo python test2.py (attached test script) I get this output Loaded plugins: langpacks, presto PROGRESS: repomd7CWtcQtmp.xml : 0 PROGRESS: repomd7CWtcQtmp.xml : 100 PROGRESS: fedora/metalink : 0 PROGRESS: fedora/metalink : 100 PROGRESS: repomdvZrc7etmp.xml : 0 PROGRESS: repomdvZrc7etmp.xml : 100 PROGRESS: repomdWIzigptmp.xml : 0 PROGRESS: repomdWIzigptmp.xml : 100 PROGRESS: repomdywREQ6tmp.xml : 0 PROGRESS: repomdywREQ6tmp.xml : 100 PROGRESS: repomdG7sBgTtmp.xml : 0 PROGRESS: repomdG7sBgTtmp.xml : 100 PROGRESS: repomd1PBJK7tmp.xml : 0 PROGRESS: repomd1PBJK7tmp.xml : 100 PROGRESS: repomd1gFH7qtmp.xml : 0 PROGRESS: repomd1gFH7qtmp.xml : 100 PROGRESS: repomdO8V1Qmtmp.xml : 0 PROGRESS: repomdO8V1Qmtmp.xml : 100 PROGRESS: repomd1a8I8gtmp.xml : 0 PROGRESS: repomd1a8I8gtmp.xml : 100 PROGRESS: repomd0bmCMxtmp.xml : 0 PROGRESS: repomd0bmCMxtmp.xml : 100 PROGRESS: repomdEJncWStmp.xml : 0 PROGRESS: repomdEJncWStmp.xml : 100 PROGRESS: repomdMBkcwFtmp.xml : 0 PROGRESS: repomdMBkcwFtmp.xml : 100 PROGRESS: updates/metalink : 0 PROGRESS: updates/metalink : 100 PROGRESS: repomdKGZZdDtmp.xml : 0 PROGRESS: repomdKGZZdDtmp.xml : 100 (1/5): fedora-yumex/primary_db | 2.9 kB 00:00 (2/5): fedora-cinnamon/primary_db | 15 kB 00:00 (3/5): fedora-xfce-4.10/primary_db | 114 kB 00:01 (4/5): updates/primary_db | 5.0 MB 00:04 (5/5): fedora/primary_db | 14 MB 00:11 (1/8): google-chrome/primary | 1.4 kB 00:00 (2/8): google-musicmanager/primary | 1.0 kB 00:00 (3/8): google-talkplugin/primary | 1.5 kB 00:00 (4/8): Dropbox/primary | 1.5 kB 00:00 (5/8): rpmfusion-free/primary_db | 403 kB 00:00 (6/8): rpmfusion-nonfree-updates/primary_db | 60 kB 00:00 (7/8): rpmfusion-free-updates/primary_db | 157 kB 00:00 (8/8): rpmfusion-nonfree/primary_db | 138 kB 00:00 PROGRESS: fedora/group_gz : 0 PROGRESS: fedora/group_gz : 100 PROGRESS: rpmfusion-free/group_gz : 0 PROGRESS: rpmfusion-free/group_gz : 100 PROGRESS: rpmfusion-free-updates/group_gz : 0 PROGRESS: rpmfusion-free-updates/group_gz : 100 PROGRESS: rpmfusion-nonfree/group_gz : 0 PROGRESS: rpmfusion-nonfree/group_gz : 100 PROGRESS: rpmfusion-nonfree-updates/group_gz : 0 PROGRESS: rpmfusion-nonfree-updates/group_gz : 100 PROGRESS: updates/group_gz : 0 PROGRESS: updates/group_gz : 100 PKG: nautilus-dropbox PKG: nautilus-dropbox-debuginfo PKG: nautilus-dropbox PKG: nautilus-dropbox-debuginfo PKG: ocaml-xmlrpc-light-devel PKG: opensm-libs PKG: ogdi-devel PKG: ocaml-cryptokit-devel PKG: ocaml-SDL-devel PKG: ocaml-lwt-devel The (1/1) -> (8/8) is not supposed to be there, when using a custom download progress handler. It must be the work on parallel download there has changed something there gives some unexpected results. Is there something else there need to be set other than YumBase.repos.setProgressBar( dnlcb ) to use a custom download callback handler ? Tim
test2.py
Description: Binary data
_______________________________________________ Yum-devel mailing list Yum-devel@lists.baseurl.org http://lists.baseurl.org/mailman/listinfo/yum-devel
