Bug 1369392
Summary: | package not listed in project page | ||
---|---|---|---|
Product: | [Community] Copr | Reporter: | Vasiliy G Tolstov <v.tolstov> |
Component: | frontend | Assignee: | clime |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | clime, v.tolstov |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-12 17:05:05 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Vasiliy G Tolstov
2016-08-23 09:35:39 UTC
What info i need to provide to speedup resolving this issue? Packages with no builds yet are not currently displayed in the package table but they should appear after you build them for the first time. It's not a serious issue I would say for quick/hot fixing to be required but it is still a bug to be fixed. But how can i build package that not listed? In builds i can create new build, but page again need to enter srpm or something else. But i'm already have spec file... ??? (In reply to Vasiliy G Tolstov from comment #3) > But how can i build package that not listed? In builds i can create new > build, but page again need to enter srpm or something else. > But i'm already have spec file... You can submit a build that generates the package and it will be automatically associated with the package based on name comparison (COPR package name and the name part of the srpm filename are compared). Or better, you can use copr-cli command line tool to be able to build the package directly from its definition. There is a command copr-cli build-package --name <pkgname> <projectname> that you can use. copr-cli build-package usage: copr [-h] [--debug] [--config CONFIG] {list,create,modify,delete,build,buildpypi,buildgem,buildtito,buildmock,status,download-build,cancel,watch-build,add-package-tito,edit-package-tito,add-package-pypi,edit-package-pypi,add-package-mockscm,edit-package-mockscm,add-package-upload,edit-package-upload,add-package-urls,edit-package-urls,add-package-rubygems,edit-package-rubygems,list-packages,get-package,delete-package,reset-package} I don't have build-package subcommand copr-cli buildmock --scm-url https://github.com/vtolstov/fedora-vtolstov.git --spec ostree/ostree.spec atomic can't import package because it does not go to subdir when search for sources hm i think that i need repo per package... via cli i'm able to add package and build. but issue is present - before i can ran first build, in packages i dont see anything. It will take time to get the fix into production so that it _actually_ works as expected. Thanks! copr-frontend-1.101-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-acf014bf51 copr-frontend-1.101-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-5a3cdc5801 copr-frontend-1.101-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-b1155f62d6 New copr-frontend version has been released. Thanks copr-frontend-1.101-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-5a3cdc5801 copr-frontend-1.101-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-b1155f62d6 copr-frontend-1.101-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-acf014bf51 I don't have copr-frontend installed =). Does it deployed already on copr.fedorainfracloud.org? (In reply to Vasiliy G Tolstov from comment #21) > I don't have copr-frontend installed =). Does it deployed already on > copr.fedorainfracloud.org? Yes :). copr-frontend-1.101-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report. copr-frontend-1.101-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. copr-frontend-1.101-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report. |