Control: reassign -1 util-linux 2.25.2-5 Control: severity -1 normal I still disagree with critical:
- If the hardware clock is so broken that at the next boot it has an earlier time than on the previous boot/ntpdate, then writing it once more at shutdown isn't going to entirely fix this problem, as it will again go sufficiently wrong if you don't reboot immediately but after some time. - Second, this doesn't "break" fsck: fsck already correctly notices that the last write time is in the future and handles that appropriately; at least that's what the original reporter mentioned. Also, under sysvinit and upstart it is util-linux which does the hwclock <-> sysclock dance, thus reassigning this. We shouldn't put this logic into different packages for different init systems. I also disagree this should be done in the first place. But I don't want to put myself into eternal wars and "who shouds the loudest wins", so I'll keep this bug open and won't make any further Severity: adjustments. Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
