On Tue, Jul 01, 2014 at 04:38:16PM +0200, Thijs Kinkhorst wrote:
> The responses from the systemd maintainers are indeed on the terse side,
> but I can imagine that your style of bug reporting does not invite our
> volunteers to spend more time on it.
This is not a question of spending time. An upgrade broke functionality
and purging systemd fixed this issue. That does not mean that it is a
bug in systemd, but it surely is a bug somewhere, be it the dependencies
(if systemd-shim is needed, why was it not installed during the upgrade?)
or the code of some other package.
Now, time is limited, but "I don't have time right now" is certainly not
a reason to close a bug within three hours.
Or, taking a different perspective: now that the issue is known, what is
done to prevent another user from hitting the very same issue in the
future?
Thomas
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140701152012.GA4890@t61
