Re: Package maintainer docs: Package Retirement: `git rm` all files in the other branches

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



przemek klosowski via devel kirjoitti 17.6.2021 klo 6.21:

On 6/16/21 6:26 PM, Kevin Kofler via devel wrote:
Otto Urpelainen wrote:
Also, if the intent is to get rid of the package completely, should not
adding it to fedora-obsolete-packages be required as well?
Why? Adding working packages to fedora-obsolete-packages forces removing
them from users' machines just because they are no longer in the repository.
That is a major disservice to the users. fedora-obsolete-packages makes
sense to use only when having the package still present actually breaks
something (and I personally think that it is unhelpful even in that case,
that is really what dnf --allowerasing is for, at least when we are talking
about package-level conflicts).

This is correct from the strict OS packaging point of view, but I think we should be concerned about the accumulation of detritus: packages that broke over time and simply do not work any more, for example like this one

Note that the documentation in question is not about normal package retirement, it is about the case where "there are special factors at work, like licensing issues, or package being removed completely from Fedora". That is quite muddy, but it is clear that the procedure is only intended for some special case where it is considered important to somehow erase the whole package, end-of-life releases and all.

The only example that is given are "licensing issues" with no explanation. I imagine what is meant is that it turns out that package useful-app is packaged in Fedora, then later it turns out it actually it has a proprietary license and Fedora has no right to distribute it. So distribution is ceased by removing the package from all channels, including end-of-life releases. In this case, the question is, is Fedora also obliged to do a recall the copies that were already illegally distributed. Obsoleting it would help with that.

Another case I could imagine would be that a package is found to contain malware, in which case I suppose it would be a good idea to attempt to remove it from as many installations as possible.

From documentation point of view, the problem is that a large and complicated topic is just hinted at when describing a different procedure.

Anyhow, since the obsoletes part is unclear and it was my own invention anyhow, I edited the page a bit to just say that it should be considered in that situation.

Otto
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux