Bug 1296296 - COPR salt is missing 2014.7.5 rpms
Summary: COPR salt is missing 2014.7.5 rpms
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Copr
Classification: Community
Component: frontend
Version: unspecified
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-06 20:22 UTC by Ken Decoteau
Modified: 2016-01-27 12:58 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-01-27 12:58:55 UTC
Embargoed:


Attachments (Terms of Use)

Description Ken Decoteau 2016-01-06 20:22:54 UTC
Description of problem: copr/salt appears to be missing all 2014.7.5 el6 RPM's


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


How reproducible: Currently reproducible. (Packages missing.) 


Steps to Reproduce:
1. add saltstack-copr el6 repo to yum 
2. attempt to search for duplicate packages of salt-minion or salt


Actual results:
Nothing found for 2014.7.5 

Expected results:
=========================================== N/S Matched: salt-minion ===========================================
salt-minion-2014.7.5-1.el6.noarch : Client component for Salt, a parallel remote execution system

  Name and summary matches only, use "search all" for everything.

Additional info:

Worked as of earlier this week.

Comment 1 Miroslav Suchý 2016-01-27 12:58:55 UTC
1) Can you be more descriptive please?
   What is copr/salt or saltstack-copr?
   Can I assume that you speak about 
   https://copr.fedorainfracloud.org/coprs/saltstack/salt/
   and x86_64 builds?:
   https://copr-be.cloud.fedoraproject.org/results/saltstack/salt/epel-6-x86_64/

2) Note that we delete old builds of the same name:
   From:
   https://fedorahosted.org/copr/wiki/UserDocs#Howlongdoyoukeepthebuilds
How long do you keep the builds?
We keep the last successful build from each package indefinitely. All other builds (old packages, failed builds) are deleted after 14 days.


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