On Seg, 2016-01-18 at 07:37 -0500, Neal Gompa wrote: > On Mon, Jan 18, 2016 at 7:27 AM, Jonathan Wakely > <jwakely@xxxxxxxxxxxxxxxxx> wrote: > > On 18/01/16 07:05 -0500, Honza Šilhan wrote: > > > > > > yes, autoremoval issue could be either caused by bad packaging > > > [1] or when > > > you are > > > installing packages via yum or packagekit [2]. We are working on > > > better > > > integration > > > between DNF and PK so this could be fixed soon. At the meantime > > > use this > > > workaround [3]. > > > > > > It's a *terrible* workaround though. "Make a note of everything > > that > > gets installed using PK and then as root run dnf to mark them as > > userinstalled". A better workaround is "Don't use PK to install > > things, use DNF". Why bother using PK at all if you then have to go > > and run DNF commands for the same packages? You might as well just > > use > > DNF. > > > > Honestly, I wonder why we didn't just have PackageKit have a DNF > backend directly, instead. https://bugzilla.redhat.com/show_bug.cgi?id=1256108 except that don't found any bug . > It seems like we created some very weird > problems by having two independent package managers that can't even > talk to each other. Maybe we should just tell people to use yumex- > dnf, > since it just calls DNF APIs through dnfdaemon, and I believe those > transactions remain in sync. > > Doing things like having PK shell out to call dnf mark just makes > things really odd. -- Sérgio M. B. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
