On Sat, 8 Dec 2018 08:12:54 +0800 gustavo panizzo <g...@debian.org> wrote: > On Fri, Dec 07, 2018 at 11:06:01AM +0100, Axel Beckert wrote: > >Hi, > > >> leap second [2], > > > >Never noticed that despite having uptimed installed on more or less > >all my Debian systems for more like 15 years or so. You're breaking my > >tradition!!1!eleventy! ;-) > > > > I understand how you feel, I've used uptimed on all my systems for the > past 10 years. > > In the usecase were uptimes shines(servers) there is almost no reason to > no use tuptime [1] > > On boards, were usually run from SD, you want to minimize disk > writes, uptimed won't let you remount the filesystem as RO. > With tuptime you'll need to hack a bit to remount RW every now and > then, or run it just before shutting down, but is more manageable. > > > On laptops uptimed is buggy, tuptime is not. > > If you wanna build something on top of the uptime data, tuptime gives > you a sqlite db which is better that parse /var/spool/uptime/records [2] > > If you wanna "extend" tuptime you just need yo hack the Python script. > > I really don't see a situation where uptimed is better than tuptime. > > > >> and general bugginess that hasn't been solved in years [3] > > > >That one I noticed. But as the severity states, it's minor (but > >admittedly annoying). > > > >> Ricardo (tuptime upstream and Debian maintainer) has agreed to add a > >> note to tuptime's long description about uptimed (for people doing > >> `apt-cache search uptimed`) and a migration script [4] > > > >Actually for some reason, I thought the import of the uptimed database > >is done by default if present. I probably misread that addition to the > >package description. > > > >> I'll submit a patch to Buster release notes regarding the removal. > > > >Maybe there should be a transitional package from uptimed to tuptime > >which actually calls that migration script. (For that it needs to be > >packaged uncompressed and not under /usr/share/doc/. Will file bug > >reports for these two things later today.) > > > > No, I don't think tuptime should replace uptimed, their CLI is > different, tuptime pulls Python. > > tuptime could run the import script on postinst (I'd provide a patch if > Ricardo agrees with the idea and implementation), but it should not > Breaks/Conflicts/Replaces uptimed in case > someone wants to keep using uptimed after upgrading to Buster. [3]
It seems like it's not for sure this should be removed right now. Axel: are you willing to take over as maintainer? I see there is a new upstream release. Perhaps this bug should be put on hold for now? If you agree, please add a moreinfo tag. That takes it out of the regular processing que. Scott K
