all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Kehayias <john.kehayias@protonmail.com>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: guix-devel@gnu.org, Julien Lepiller <julien@lepiller.eu>
Subject: Re: GitLab to plans to delete dormant projects
Date: Sat, 06 Aug 2022 21:57:07 +0000	[thread overview]
Message-ID: <MO5mzik_zCmoEvReFWFB5vDD6Z2F9ugyVni5YhrNn2Pl8jmqeWO347_lynAFpLC67mI7ZCWLN8VG-ezZWY7Xz4jJTaUZV708ovEqOzgoUoA=@protonmail.com> (raw)
In-Reply-To: <87o7wxpliy.fsf@laura>

Hi all,

------- Original Message -------
On Saturday, August 6th, 2022 at 9:08 AM, Olivier Dion via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> wrote:

>
>
> Hi,
>
> Following this article https://lwn.net/Articles/903858/, GitLab is
> planning to start deleting project that were idle for > 12 months.
>
> Many packages origin in Guix use an url to a GitLab project. What are
> the consequence of such deletion on Guix reproducibility? Will it
> affects the time-machine?
>

I think having good backup and archival plans are great, so not to dissuade anyone on this, but as an update here looks like GitLab has walked back on this:

https://www.theregister.com/2022/08/05/gitlab_reverses_deletion_policy/

John


  parent reply	other threads:[~2022-08-06 21:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06 13:08 GitLab to plans to delete dormant projects Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-08-06 14:34 ` Maxime Devos
2022-08-06 14:41 ` Julien Lepiller
2022-08-06 14:50   ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-08-07 21:09     ` Ludovic Courtès
2022-08-06 21:57 ` John Kehayias [this message]
2022-08-17 16:41 ` zimoun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='MO5mzik_zCmoEvReFWFB5vDD6Z2F9ugyVni5YhrNn2Pl8jmqeWO347_lynAFpLC67mI7ZCWLN8VG-ezZWY7Xz4jJTaUZV708ovEqOzgoUoA=@protonmail.com' \
    --to=john.kehayias@protonmail.com \
    --cc=guix-devel@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=olivier.dion@polymtl.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.