Guys, this issue has been fixed in F24's PackageKit (libhif actually). -Igor Gnatenko On May 27, 2016 8:33 AM, "Dan Book" <gri...@gmail.com> wrote:
> On Fri, May 27, 2016 at 2:17 AM, Nico Kadel-Garcia <nka...@gmail.com> > wrote: > >> On Thu, May 26, 2016 at 1:03 PM, Gerald B. Cox <gb...@bzb.us> wrote: >> > >> > On Thu, May 26, 2016 at 3:02 AM, Michal Luscon <mlus...@redhat.com> >> wrote: >> >> >> >> This might have been caused by >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1259865 >> >> >> >> . >> >> >> >> Michal >> > >> > >> > Yes, Kevin mentioned that and it is in the other thread (corebird). I'm >> > just wondering if this is something that will be resolved >> > with the upgrade to F24. >> >> Just don't use "dnf autoremove" it is not, and cannot be, your friend >> except to perhaps provide a *guideline*, of removable packages. Never >> run it without manual review of the target packages. >> > > For whatever reason, autoremove is the default behavior of dnf unless you > disable clean_requirements_on_remove, so you can expect this issue to hit > new users. > > -- > devel mailing list > devel@lists.fedoraproject.org > https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org > >
-- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
