Le mercredi 13 février 2013 à 12:58 -0800, Dan Mashal a écrit :
On Feb 13, 2013 10:58 AM, "Lennart Poettering" mzerqung@0pointer.de wrote:
On Wed, 13.02.13 02:44, Dan Mashal (dan.mashal@gmail.com) wrote:
Please can we test this on rawhide first if anything? I'm pretty
sure a lot
of thing are still ck dependant. We are still trying to catch up
to systemd.
So, in contrast to the esound discussion I do not sense too much opposition to me just retiring CK. So I'd probably do that in
Rawhide
next week or so. CK would hence disappear in F19, but would give everybody time until the branch or freeze or so to fix their
packages...
Lennart
-- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Sorry if I sound ignorant but:
No. I meant fedora 20 rawhide. What is the problem with keeping it?
Are we just trying to break something different every time we release a new version of Fedora?
Regardless, do you know exactly what depends on consolekit and what doesn't? Have you gone through every package?
That's a valid concern. While the list of packages requiring consolekit are quite small ( ie, 3 packages, 1 being a shell script with support to disable ck ), we cannot really check those using the dbus interface in a exhaustive way.
However, I have already removed consolekit on my F18 without any notable issue, so I do not think any breakage would be blocking. We have the whole F19 cycle to find and detect the few packages needing fix.