branch orphan packages #95
Comments
By curiosity, when do we drop orphaned packages? After branching? In other words, is it really logical to branch a package that has no-one to maintain it? |
On Thu, Oct 23, 2014 at 06:25:10AM -0700, Pierre-Yves Chibon wrote:
Previously orphaned packages were retired shortly before branching, but |
Ok, tagging as easyfix as this is a one-line patch :) |
I would like to fix this bug. I have already setup pkgdb2. Can you guide me as how to solve this bug? |
@ghost-script cool, thanks for stepping up. The fix is a single line change, on the part of the code cloning a branch into another one. Feel free to check the file |
@pypingou i read the file pkgd2_branch.py and follwed the trail to add_branch() method in A Fix might be to check for 'Approved' or 'Orphaned' packages. |
Added check for 'Orphaned' packages while cloning to new branch.
Merged, thus this ticket is fixed, thanks @ghost-script ! |
Packages Fedora Branched without a branch for Fedora Branched cause an error when getting maintainer information. However, this should never happen: fedora-infra/pkgdb2#95
pulseaudio-equalizer has no F21 branch, but a master and F20/F19 branches, probably because it was not branched since it is orphaned:
https://admin.fedoraproject.org/pkgdb/package/pulseaudio-equalizer/
https://admin.fedoraproject.org/pkgdb/admin/log/?package=pulseaudio-equalizer
However, it is still shipped in F21, therefore there should be a branch.
The text was updated successfully, but these errors were encountered: