| Summary: | {WISH}Open a copr page for mageia.org | ||
|---|---|---|---|
| Product: | Websites | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | Other | Assignee: | Atelier Team <atelier-bugs> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | davidwhodgins, lovaren |
| Version: | trunk | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://docs.pagure.org/copr.copr/ | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Kristoffer Grundström
2023-02-24 21:26:00 CET
I personally have my own copr repo: https://copr.fedorainfracloud.org/coprs/umeaman/ CC:
(none) =>
lovaren I'm not in favour of it. Packages from other sources will make debugging of bug reports more difficult. CC:
(none) =>
davidwhodgins I'd like to ask what the use of copr in the official repos is if it's not supposed to be used. No pun intended at all by asking, but I find it to be a great way of growing Mageia beyond its limits. Whatever bug one might get there's a discuss field on the actual repo page and you also provide an upstream link. You even get live build logs. For instance, here's a package that I successfuly built for Mageia: https://copr.fedorainfracloud.org/coprs/umeaman/python3-django-redis/ If the packages have mga8 or mga9 in the package names, they must not be distributed to others. What you do for personal use is your business. If they are distributed to others, they will waste time of bug squad and others, if they happen to interfere with packages that are provided by Mageia. If you report bugs, make sure you include in every bug report that third party packages are installed. The copr packages are intended for users to be able to create packages, but they must not have package names that make them look like they are packages that have been distributed by Mageia. Debugging problems with Mageia supplied packages is difficult enough. When a user encounters a problem, especially when upgrading from one release to the next, having packages from sources other then Mageia makes it even more difficult. If the package names makes it look like they are Mageia packages it can waste a lot of time during bug analysis. It's a problem we've encountered before, where packages that were not qa tested by Mageia or distributed by Mageia, but had .mga# in the names caused bugs, and wasted time for bug squad, qa, and packagers involved in trying to figure out the cause. |