Re: When to make packeges "dnf protected"

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

 



On Sat, Dec 3, 2016 at 1:10 PM, Rolf Fokkens <rolf@xxxxxxxxxxxxxx> wrote:
> Hi all,
>
> As the maintainer of bcache-tools I ran into the situation that a collegue
> accidentally removed bcache-tools, resulting in a system that failed to boot
> after installing and using a new kernel. dnf logs showed that the package
> had been erased, with a bunch of other packages. It happened 3 weeks ago,
> and the colleague did not recall what he actually did at that time.
>
> I'm considering to make bcache-tools protected (by including a config file
> in the package in /etc/dnf/protected.d/) to prevent accidental erasure of
> the package. Is this the proper way to prevent this situation?
>

I would recommend making this a separate subpackage, and having that
package recommended by the main one. It ultimately needs to be
possible to be able to remove it, so making the specific file
removable via a subpackage is the way to go for that.



-- 
真実はいつも一つ!/ Always, there's only one truth!
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [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