On Sun 30 Dec 2018 at 16:02:17 +0100, Andrea Borgia wrote:
> Il 30/12/18 15:48, Roberto C. Sánchez ha scritto:
>
>
> > I would leave the bug report open. If it is a problem, the maintainer
> > may add the example back to the package. If it was removed by upstream
> > or there was some other intentional reason for the removal, he is likely
> > to comment on it and close the report.
>
> There is an extremely minor difference between the old example and the
> current service definition: the former had "fstrim -av" (all fs) and the
> latter has "fstrim -Av" (fstab only). Might be relevant, might be not.
There is probably no need for an example file now that #889668 is closed.
Incidentally - you opened the report, so you can close it; especially if
you think it will save someone some work.
> > To do such and such, refer to such and such example. As of util-linux
> > version 1.2.3.4.5.6-7 this example is no longer provided. An
> > alternate approach is blah blah blah. Or refer to an older version of
> > the package for the referenced example.
> >
> > Anyhow, you get the idea.
>
> Unfortunately, I have no clue precisely when the change happened since the
> system was upgraded from stable to testing to support the new Ryzen CPU.
>From the changelog:
util-linux (2.31.1-0.3) unstable; urgency=medium
* Non-maintainer upload.
* Install fstrim.timer and fstrim.service without enabling it by default
(for now), see discussion in #732054 (Closes: #889668)
-- Laurent Bigonville <bi...@debian.org> Wed, 14 Feb 2018 10:32:51 +0100
> Anyhow, I do get the idea: once I'm registered logged in, I'll try to be as
> specific as possible.
>From the wiki:
> sudo cp /usr/share/doc/util-linux/examples/fstrim.{service,timer}
> /etc/systemd/system
Adding:
Not needed on buster because......
would look to fit the bill.
--
Brian.
