Bug 1371107 - Packages in the copr disappeared
Summary: Packages in the copr disappeared
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Copr
Classification: Community
Component: backend
Version: unspecified
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-29 10:53 UTC by Michal Pryc
Modified: 2016-08-30 14:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-30 06:45:34 UTC
Embargoed:


Attachments (Terms of Use)

Description Michal Pryc 2016-08-29 10:53:14 UTC
Description of problem:

We are using packages stored in the copr repository for our CI system.

Currently we've noticed that some of the packages were removed/silently disappeared from the copr repository.

They are still listed in the metadata, but it's impossible to install them.

Looks like it affects packages that has newer version available and the older versions were removed. We need both old and new version to be available to satisfy different dependency requirements.

Note that this was working fine for couple of months so far, so something on the Copr side is wrong imo.

Examples:

1:

https://copr.fedorainfracloud.org/coprs/abregman/el7-rhos9-test-deps/package/python-tox/

python-tox-2.1.1 is not available for installation, python-tox-2.3.1 is fine.

2:
https://copr.fedorainfracloud.org/coprs/abregman/el6-rhos5-test-deps/package/pyflakes/

It's not possible to install pyflakes-0.7.3

Comment 1 clime 2016-08-30 06:45:34 UTC
Answers are inline.

(In reply to Michal Pryc from comment #0)
> Description of problem:
> 
> We are using packages stored in the copr repository for our CI system.
> 
> Currently we've noticed that some of the packages were removed/silently
> disappeared from the copr repository.
> 
> They are still listed in the metadata, but it's impossible to install them.

At least for case number 1:, the package python-tox-2.1.1 is not present in repodata. Haven't checked 2: so far.

> Looks like it affects packages that has newer version available and the
> older versions were removed. We need both old and new version to be
> available to satisfy different dependency requirements.

This is not a bug. See https://fedorahosted.org/copr/wiki/UserDocs#Howlongdoyoukeepthebuilds

Comment 2 Michal Pryc 2016-08-30 07:53:04 UTC
(In reply to clime from comment #1)
> Answers are inline.
> 
> (In reply to Michal Pryc from comment #0)
> > Description of problem:
> > 
> > We are using packages stored in the copr repository for our CI system.
> > 
> > Currently we've noticed that some of the packages were removed/silently
> > disappeared from the copr repository.
> > 
> > They are still listed in the metadata, but it's impossible to install them.
> 
> At least for case number 1:, the package python-tox-2.1.1 is not present in
> repodata. Haven't checked 2: so far.
> 
> > Looks like it affects packages that has newer version available and the
> > older versions were removed. We need both old and new version to be
> > available to satisfy different dependency requirements.
> 
> This is not a bug. See
> https://fedorahosted.org/copr/wiki/UserDocs#Howlongdoyoukeepthebuilds

This wasn't the case for us for the last 6+ months (it's first time we observed packages being removed).

Is there an option to disable such cleanup for a specific user? This is really big issue for us to have package versions disappear.

Comment 3 clime 2016-08-30 14:32:58 UTC
(In reply to Michal Pryc from comment #2)
> This wasn't the case for us for the last 6+ months (it's first time we
> observed packages being removed).

We were replacing the script and it took quite some time.
 
> Is there an option to disable such cleanup for a specific user? This is
> really big issue for us to have package versions disappear.

Yes, there is, luckily. In the newest versions, if you are so-called COPR admin, you can create a persistent project which cannot be deleted nor any build from it. The steps are: 

1) Create a new bugzilla as RFE asking to me you or any of your colleagues an admin (just a boolean in COPR db). You can also ask us to make an existing project persistent or you can create a new one after becoming an admin.

2) That's it. The persistent project will not be touched by the auto-prunning script.

Comment 4 clime 2016-08-30 14:35:29 UTC
(In reply to clime from comment #3)
> 1) Create a new bugzilla as RFE asking to me you or any of your colleagues
asking to *make*. Sorry.


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