Bug 533024 - --location and --srpm do not work as intended
Summary: --location and --srpm do not work as intended
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-utils
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-04 18:07 UTC by Michael S.
Modified: 2014-01-21 23:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-04 22:01:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michael S. 2009-11-04 18:07:46 UTC
Description of problem:
using --location and --srpm do not show the expected result when used at the same time. I would expect to use this to get the srpm url only, while it show the package and its srpm url.

Version-Release number of selected component (if applicable):
yum-utils-1.1.23-3.fc12.noarch

How reproducible:
always

Steps to Reproduce:
1. $ repoquery --location  --srpm couchdb

Actual results:
ftp://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/development/i386/os//Packages/couchdb-0.10.0-2.fc12.i686.rpm
ftp://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/development/source/SRPMS//couchdb-0.10.0-2.fc12.src.rpm

( srpm and binary rpm )

Expected results:

just the srpm

Additional info:
if I disable the src repo in yum, it still give the binary rpm, instead of a error message.

Comment 1 seth vidal 2009-11-04 22:01:20 UTC
yep - that's not right. And now it's fixed.

Took me a bit of time to track down where this was going wrong.
http://yum.baseurl.org/gitweb?p=yum-utils.git;a=commitdiff;h=39b581cc96d26d623544c17303804088d3fd939c

it's committed upstream.

Comment 2 Fedora Update System 2009-11-07 06:56:24 UTC
yum-utils-1.1.24-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/yum-utils-1.1.24-1.fc12


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