> From: "James Hogarth" <james.hogarth@xxxxxxxxx> > On 18 Jan 2016 06:33, "Igor Gnatenko" < i.gnatenko.brain@xxxxxxxxx > wrote: > > > > I hope Heiko Adams and Reindl Harald should co-operate and write usable and > > bug free package manager. > > > > Related to topic: Please prepare full list of bugs which you think critical > > for you and write to each how to reproduce it. > > > > P.S. autoremove works here fine (fresh 23). > > > The autoremove reference might be the well known issue with packagekit, not > dnf, that is not marking packages as installed rather than dependencies. > > The default dnf configuration is autoremove so that doesn't then know that > have been specifically installed rather than just unneeded dependencies of > something else and then helpfully tries to remove them... > > Note this is a result of a packagekit bug not dnf. > > On a side note it'd be nice if pk just called out to dnf so that they have a > common backend which would prevent behaviour like this and would result in > sharing a history database as well. 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]. > From: "Reindl Harald" <h.reindl@xxxxxxxxxxxxx> > Am 18.01.2016 um 00:48 schrieb Kevin Fenzi: > > Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote: > > > > ...snip... > > > >> "dnf update *.rpm" is the way which has to work > > > > Why? It works fine as a install. It's installing a new kernel, since > > kernels can have many versions installed at a time it makes more sense > > for it to be a install than an upgrade (which would imply that the old > > version would be removed). > > why? > > because you don't type "dnf install kernel" instead "dnf upgrade" and > "kernel-headers" *is never installed* in multiple versions > > >>>> https://bugzilla.redhat.com/show_bug.cgi?id=1271676 > >>> > >>> This seems like a matter of taste. If you want to keep yearly logs, > >>> set your logrotate that way. > >> > >> AFAIR the config files are not config noreplace" > > > > The spec seems to have: > > %config(noreplace) %{_sysconfdir}/logrotate.d/%{name} > > well, give it a try, but for many years you had yum-logs for the > complete year rotated once on the begin of a new year - package updates > are not that often and don#t flood logs like some systemd things Then I am closing this bug, thanks for cooperation. Honza [1] https://bugzilla.redhat.com/show_bug.cgi?id=1222812#c23 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1259865 [3] http://dnf.baseurl.org/2015/10/26/mark-command-usecase/ -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
