emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#54659: closed ([PATCH 0/2] Periodically delete build logs)


From: GNU bug Tracking System
Subject: bug#54659: closed ([PATCH 0/2] Periodically delete build logs)
Date: Mon, 04 Apr 2022 21:18:02 +0000

Your message dated Mon, 04 Apr 2022 23:17:04 +0200
with message-id <87v8vor1kf.fsf_-_@gnu.org>
and subject line Re: bug#54659: [PATCH 0/2] Periodically delete build logs
has caused the debbugs.gnu.org bug report #54659,
regarding [PATCH 0/2] Periodically delete build logs
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
54659: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=54659
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH 0/2] Periodically delete build logs Date: Thu, 31 Mar 2022 23:20:38 +0200
Hi!

We’ve been accumulating cruft in /var/guix/log/drvs for too long,
time to do something about it!

Thoughts?

Ludo’.

Ludovic Courtès (2):
  services: Add 'log-cleanup-service-type'.
  services: Add 'log-cleanup' service to '%base-services' for build
    logs.

 doc/guix.texi          | 39 +++++++++++++++++++++++++++++++
 gnu/services/admin.scm | 53 +++++++++++++++++++++++++++++++++++++++++-
 gnu/services/base.scm  |  6 +++++
 3 files changed, 97 insertions(+), 1 deletion(-)


base-commit: 53b04339fe521f486d3017930a419d5ca8a6cffd
-- 
2.34.0




--- End Message ---
--- Begin Message --- Subject: Re: bug#54659: [PATCH 0/2] Periodically delete build logs Date: Mon, 04 Apr 2022 23:17:04 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Hi,

Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> skribis:

> This might be very nitpicky, but I think we should leave expiry
> undefined so that the default of 6 months is applied.  This way, if
> there's a future decision that all logs should probably kept e.g. for
> only 3 months, there is just one place to edit rather than two.

In the end I followed your suggestion and pushed as
e692dc632cbb0e6d21ed6f09f4c7f52391802cfb.

Thanks!

Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]